Computer Networking - Network Management - Notes | ECPE 177, Study notes of Computer Systems Networking and Telecommunications

Material Type: Notes; Class: Computer Networking; Subject: Electrcl & Computer Engr; University: University of the Pacific; Term: Unknown 1989;

Typology: Study notes

Pre 2010

Uploaded on 08/18/2009

koofers-user-wjc
koofers-user-wjc 🇺🇸

10 documents

1 / 4

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Network Management
Network management is the collection of tasks performed to maximize availability, performance, security and
control of a network and its resources. The International Organization for Standardization (ISO) Network
Management Forum has divided network management into five functional areas:
1. Fault Management
2. Configuration Management
3. Performance Management
4. Accounting Management
5. Security Management
Each of these functional areas has its own set of requirements, and an effective network management
product should be able to perform in each area.
1. Fault Management
Fault management is the process of identifying and correcting network problems, otherwise known as faults.
Faults typically manifest themselves as transmission errors or failures in the equipment or interfaces. Faults
result in unexpected downtime, performance degradation and loss of data. Generally, fault conditions need to
be resolved as quickly as possible.
Comprehensive fault management is the most important task in network management. Fault management
tools can help increase the reliability of the network by quickly identifying the fault, and then help initiate the
recovery process. The first step is to identify the fault, isolate the cause of the fault, and then correct the fault.
In the simplest case, an alarm is detected, and a maintenance technician is dispatched to locate and resolve
the fault at the suspect location. Using more advanced tools, the network manager may be able to go many
steps further to isolate and correct a fault from the manager location, and then return the network to normal
operation without any users being aware of the failure.
The reporting of faults also falls under fault management. Universally recognized colors such as red, green,
and yellow can be used to indicate the status of a device - red for device in error, green for device with no
error, and yellow for device with a minor error or possible error. Graphical presentations of a network map
and front panels of the equipment are also used by the network manager to indicate status and operation of
devices in the network.
2. Configuration Management
Configuration management deals with the initialization, modification, and shutdown of a network. Networks
are continually changing as devices are added, removed, reconfigured, and updated. These changes may be
intentional, such as adding a new server to the network, or path related, such as a fiber cut between two
devices resulting in a rerouted path. If a network is to be turned off, then a graceful shutdown in a prescribed
sequence is performed as part of the configuration management process.
The process of configuration management involves identifying the network components and their
connections, collecting each device's configuration information, and defining the relationship between
network components. In order to perform these tasks, the network manager needs topological information
about the network, device configuration information, and control of the network components.
3. Performance Management
Performance management involves measuring the performance of a network in terms of utilization,
1
pf3
pf4

Partial preview of the text

Download Computer Networking - Network Management - Notes | ECPE 177 and more Study notes Computer Systems Networking and Telecommunications in PDF only on Docsity!

Network Management

Network management is the collection of tasks performed to maximize availability, performance, security and control of a network and its resources. The International Organization for Standardization (ISO) Network Management Forum has divided network management into five functional areas:

  1. Fault Management
  2. Configuration Management
  3. Performance Management
  4. Accounting Management
  5. Security Management Each of these functional areas has its own set of requirements, and an effective network management product should be able to perform in each area. 1. Fault Management Fault management is the process of identifying and correcting network problems, otherwise known as faults. Faults typically manifest themselves as transmission errors or failures in the equipment or interfaces. Faults result in unexpected downtime, performance degradation and loss of data. Generally, fault conditions need to be resolved as quickly as possible. Comprehensive fault management is the most important task in network management. Fault management tools can help increase the reliability of the network by quickly identifying the fault, and then help initiate the recovery process. The first step is to identify the fault, isolate the cause of the fault, and then correct the fault. In the simplest case, an alarm is detected, and a maintenance technician is dispatched to locate and resolve the fault at the suspect location. Using more advanced tools, the network manager may be able to go many steps further to isolate and correct a fault from the manager location, and then return the network to normal operation without any users being aware of the failure. The reporting of faults also falls under fault management. Universally recognized colors such as red, green, and yellow can be used to indicate the status of a device - red for device in error, green for device with no error, and yellow for device with a minor error or possible error. Graphical presentations of a network map and front panels of the equipment are also used by the network manager to indicate status and operation of devices in the network. 2. Configuration Management Configuration management deals with the initialization, modification, and shutdown of a network. Networks are continually changing as devices are added, removed, reconfigured, and updated. These changes may be intentional, such as adding a new server to the network, or path related, such as a fiber cut between two devices resulting in a rerouted path. If a network is to be turned off, then a graceful shutdown in a prescribed sequence is performed as part of the configuration management process. The process of configuration management involves identifying the network components and their connections, collecting each device's configuration information, and defining the relationship between network components. In order to perform these tasks, the network manager needs topological information about the network, device configuration information, and control of the network components. 3. Performance Management Performance management involves measuring the performance of a network in terms of utilization,

throughput, error rates, and response times. With performance management information, a network manager can reduce or prevent network overcrowding and inaccessibility. This helps provide a more consistent level of service to users on the network. This form of management looks at the percentage of utilization of devices to help in improving and balancing the throughput of traffic in all parts of a network. Typically, some devices are more highly utilized than others. Performance monitoring give qualitative and time relevant information on the health and performance of devices so that underutilized devices are more utilized, and overtaxed devices are less utilized. In a well- balanced network with healthy components, the error rates for packets traversing the network are down and response times are shortened. It is typical for performance management to work in conjunction with fault and configuration management. For example, a monitored device interface that exhibits a slowly increasing error rate can be verified by an alarm query, and could then be reconfigured and bypassed before the fault affects traffic.

4. Accounting Management Accounting management involves tracking each individual user's use of network resources for the purposes of billing and resource allocation. This type of information helps a network manager allocate the right kind of resources to users, as well as develop a plan for network growth. With the same information, the cost of transmitting messages across the network can be computed and billed to the user if the traffic was revenue bearing. This type of management involves monitoring the login and logoff records, and checking the network usage to determine a user's use of the network. In addition, access privileges and usage quotas can be established and checked against actual for accounting information. 5. Security Management Security management deals with ensuring overall security of the network, including protecting sensitive information through the control of access points to that information. Sensitive information is any data that an organization wants to secure, such as research documents, payroll data, and sales and inventory figures. Security management controls access to the network devices and sensitive information through the use of devices such as passwords. This management also controls the form of sensitive data using methods such as encryption. Of course, security management also includes protecting the network from internal and external malicious users. Network Management Standards Typical networks are becoming increasingly more complex, and are usually built with products provided by many different vendors. Managing these networks is increasingly more difficult, involving multiple management tools and protocols to support different proprietary devices on the network. As a result, managers are demanding open systems solutions that use industry-accepted standards to reduce the number of different management systems. At the same time, vendors that comply with published standards can be assured that their products will interoperate together in a network. Standards bodies have recently issued network management standards provide what vendors and network managers both need. The Internet Architecture Board (IAB), which is responsible for networking technology and protocols for the TCP/IP internetworking community, has created a standard network management protocol. These protocols are documented as RFCs (Request for Comments). The IAB recommends the Simple Network Management Protocol (SNMP) for use as a common network management protocol with TCP/IP-based networks. TCP/IP networks are the most popular types of network. SNMP, described by RFC 1157, became a full Internet Standard in May 1990, and is now in widespread use. Virtually every vendor of network equipment such as computers, workstations, bridges, routers, and hubs offer SNMP. Because of its widespread use as an open systems standard, new classes of equipment (for example, microwave radios) also support SNMP.

RFC 1157, A Simple Network Management Protocol : defines the protocol and architecture used to manage the MIB and its contents; RFC 1155, Structure and Identification of Management Information for TCP/IP-based networks : describes how the MIB is defined; RFC 1213, Management Information Base for Network Management of TCP/IP-based Internets: MIB-II : describes the contents of the MIB. SNMP is an application layer protocol that is part of the Transmission Control Protocol/ Internet Protocol (TCP/IP) protocol suite. It is intended to operate over the User Datagram Protocol (UDP). The management station communicates management information using SNMP, which is implemented on top of the UDP and IP protocols, and a data link protocol such as Ethernet. Likewise, the agent also must also implement the SNMP, UDP, and IP protocols. SNMP has several key features that are important to understand. It is a transaction-based and datagram- oriented protocol. The protocol dictates that an action gets a response that ends the transaction. The response is a datagram or packet of bytes of prescribed size and format. Action by the management station, such as a GET command, will result in a datagram response from the agent. If the transmission fails to reach its destination address, (after a time-out) the management station will retransmit again. SNMP has a strong focus on Configuration and Fault management. It has fewer features for Security management; therefore, most SNMP management systems concentrate on alarm and status reporting, and use other methods for security. In addition, traps sent by the agent to the management station are less reliable than GET responses because the UDP protocol is used. UDP does not guarantee delivery of the message. An alarm notification or trap from a faulty device may be lost because the datagram failed to reach the management station. SNMP has many strong points in spite of the limitations mentioned above. Any vendor supporting SNMP must be aware of these limitations, and work around them to make their products competitive. SNMP is widely used by a number of vendors and its wide scale implementation makes it a de facto protocol for network management.