E business solutions l07-netman
?Download as PPT, PDF?
0 likes?326 views
Network management is important for proactively detecting failures, monitoring traffic and resources, detecting misconfigurations, and monitoring service level agreements and intrusions. It involves managing elements like the enterprise network, servers, databases, applications, and remote access. Common network management frameworks include fault, configuration, performance, security, accounting, and more. Effective network management must address the challenges of interconnected yet separately managed systems across the IT infrastructure. It relies on agents that monitor devices and report to a central network management system which stores data and provides alerts and reports. Key protocols for communication include SNMP while newer approaches involve web-based management.
E business solutions l07-netman
- 1. Network Management A Network is a complex mixture of hardware and software technologies linked by networking technologies
- 2. Desktop Admin LAN Infrastructure Net Mgmt WAN Net Mgmt
- 3. Reasons for Network Management Proactively detecting failures of equipment before the users are aware. Monitoring traffic to aid in resource deployment Detecting mis-configured elements Monitoring for SLA¡¯s Intrusion Detection
- 4. ?
- 5. Distributed IT Infrastructure Architecture Define the Components? Servers & Networks that connect Servers to each other & to the clients they serve No right/wrong way to divide processes/responsibility System Administration: Mgmt of Clients, servers, OS¡¯s & NOS¡¯s that allow computers to communicate Enterprise Network Management
- 6. Elements of IT Infrastrucuture that must be managed Enterprise network LAN Management Server Management Desktop Management Database Management Application Management Remote Access Management
- 7. OSI Network Management Framework Fault Management Configuration Management Performance Management Security Management Accounting Management
- 8. TMN Model Telecommunication Management Network standards from ITU Business Management Service Management Network Management Element Management
- 9. IT Infrastructure Management A Challenge as IT Infrastructure is made up of a combination of separately managed and Monitored Elements Different management tools often do not interoperate or share Data
- 10. ?
- 11. Architecture Agents are S/W that runs on networking devices to monitor and report Must be compatible with the NMS NMS Compiles, Displays, Reports and Alarms Stores data in a Database Database has an Index and standardised field definitions = MIB Fields within MIBs known as Objects
- 12. From: SUN Solstice TMN manager White Paper
- 13. Protocols Protocol used to communicate between agents & NMS is SNMP Management traffic can be up to 30% Affects network you are monitoring Now available: Distributed Management sub-NMSs
- 14. Protocols New: Web Based Management = WBEM uses HMMP - Hypermedia Management protocol Replace SNMP and DMI? Advantages: Common Interfaces for all devices NMS is Platform Independent
- 15. RMON Remote Monitoring RMON Probes - An Agent that collects and reports performance statistics to an NMS
- 16. Network Analysers Ie Sniffer, Lanwatch Monitor at a single point on a network Can display data from most of the OSI layer separately I do not consider Physical layer testers such as cable scanners, signal quality monitors, BERT testers.
- 17. References Goldman Chapter 12 Kurose & Ross Stallings Chapter 19 Tanenbaum Chapter 7.3
Editor's Notes
- #2: A network is a collection of data paths between computers. The computers, typically called servers and clients, use these data paths to exchange information. Network messages containing the information flow from a source computer to one or more destination computers. Each computer has a network address that devices consisting of networking hardware and software use to route a message to a destination. Physical cables comprise some network data paths, while wireless radio links comprise others. Various agreed-upon protocols define the addressing scheme as well as the content (layout) of each message. Because some protocols encapsulate other protocols, a network has multiple layers, defined as per the OSI Model.
- #3: Types of Network managemet: There is overlap Red: Administration of Nodes ( End-Points) Microsoft back Office ¡° Facilitates the delivery of meaningful information to desktop PC's¡± - limited to PC world- NT4 etc. Attachmate Netwizard - Only sees endpoints- controls applications on them, need a netwizard agent on each node. Blue; Lan Network management: Monitoring status of devices on network: concentrates on Network performance Can see end nodes.: HP Openview; IBM Netview, Tivoli Green: WAN network management: as Blue but seperate. AND: Analysis of a particular segment of network: analysing faults: sniffer, Lanwatch; Network management products use networking-oriented protocols to measure such metrics as message activity (i.e., traffic), server activity, client activity and network device activity, for the local network, for remote networks and for the connections between the local and remote networks."
- #4: Changing nature of traffic on Networks with Convergence and VoIP Pro-active or Reactive? "Via management protocols, network management products might monitor such details as server CPU utilization, server memory utilization, server hard disk utilization, server available free disk space, network traffic levels, network device utilization and whether each connection is healthy or broken. Protocols and industry standards are important because the network's devices, computers, operating systems and other components are typically a diverse, heterogeneous set of corporate infrastructure assets purchased from different manufacturers at different times."
- #5: Consolidated Service desk - In helpdesk function Reduce console clutter
- #7: Plessey NM system for packet switch network: Configuration tool Loader SERF Diagnostics Distributed Database Management Enterprise Database Management
- #8: Enterprise Net Mgmt: More than ¡±Is Network Available?¡± - - Now look to QOS Especially with VoIP happening. - - Traffic Shaping - A la 3COM lecture. These are ¡° Arbitrary¡± -- Technology applies to multiple categories categories are interdependent. Fault mgmt: Monitoring of system state: receipt & processing of alarms, diagnosis user help desk? Config management: Accurate description of network components, Control of remote config Peformance mgmt: Quality of Service: Bottlenecks: Measure performance, produce reports: Capacity planning and pro-active performance planning Security Management: Intrusion detection: authentication of users: encryption Accounting management: ¡°Not who's guilty!¡± Record usage stats: Chargeback: Allocation & monitoring of quotas.
- #9: TMN standards organised according to focus areas: Architecture: Functional requirements: Protocols, conformance Business mgmt: High level: strategic business & financial planning Service mgmt: focus on implementation support, & mgmt of telecommunications services to meet above. Network mgmt: end-to-end mgmt of network infrastrucuture that will be delivering services of above: Functionality Vendor Independent Element mgmt: Vendor dependent; Somwhere along the line we get into Service level Agreements Need tools to monitor these - Visual uptime from Visual netwroks - Vital suite from Lucent Most NM S/W gives uptime of individual components
- #10: Hit this later with SNMP Tools: HP Openview, IBM Netview, Tivoli. Sniffer
- #12: Get MIB for your product & incorporate it into NMS database MIBS from suppliers for the network tool
- #14: SNMP came about in TCP/IP SNMP 2 developed, never implemented, then a couple of other versions, now SNMP3, This has security elements of SNMP2 restored after their loss in other variants. SNMP3 has: Used with other protocols reduce network traffic by combining pieces of information Segment large networks NMS to NMS comms Allows remote configuration Multiple agents/device - monitoring different things AirVision : Home server/ Cluster Managers
- #15: WBEM out of IETF also supposed to support the Applications management aspect. Microsoft WMI. DMTF has struggled to get vendors to conform to DMI
- #16: Set thresholds, report when they are exceeded. Cannot collect data regarding WAN Performance Unix boxes;
- #17: Sniffer for fixing probs. Used at a local level.