NETW420 REPORT
Cisco Network Management System
NETW-420 Enterprise Network Mgmt
Professor
Introduction
Cisco uses the International Organization for Standardization network management model which defines five functional areas of Network management. The model consists of Fault Management, Configuration Management, Performance Management, Security Management, and Accounting Management. In this paper we will cover the models five functional areas.
Fault Management Fault management detects, logs, notifies users of, and tries to automatically fix network problems to keep the network running effectively. Fault management is perhaps the most widely implemented of the ISO network management elements. The reason is because faults can cause downtime or unacceptable network degradation. Fault Management uses a network management platform deployed in an enterprise infrastructure that consists of multivendor network elements. Network management platforms can be viewed as the main console for network operations in detecting faults in the infrastructure. The platform receives and processes events from network elements in the network. Events from servers and other critical resources can also be forwarded to a management platform. A standard management platform consists of Network discovery, Topology mapping of network elements, Event handler, and Performance data collector and graphed.
Configuration Management Configuration management monitors network and system configuration information so that the effects on network operation of various versions of hardware and software elements can be tracked and managed. With the increase in network devices, it is critical to be able to accurately identify the location of a network device. A detailed description meaningful to those tasked with dispatching resources when a network problem occurs should provide accurate location information. Making certain to have available contact information of the person or department
NETW-420 Enterprise Network Mgmt
Professor
Introduction
Cisco uses the International Organization for Standardization network management model which defines five functional areas of Network management. The model consists of Fault Management, Configuration Management, Performance Management, Security Management, and Accounting Management. In this paper we will cover the models five functional areas.
Fault Management Fault management detects, logs, notifies users of, and tries to automatically fix network problems to keep the network running effectively. Fault management is perhaps the most widely implemented of the ISO network management elements. The reason is because faults can cause downtime or unacceptable network degradation. Fault Management uses a network management platform deployed in an enterprise infrastructure that consists of multivendor network elements. Network management platforms can be viewed as the main console for network operations in detecting faults in the infrastructure. The platform receives and processes events from network elements in the network. Events from servers and other critical resources can also be forwarded to a management platform. A standard management platform consists of Network discovery, Topology mapping of network elements, Event handler, and Performance data collector and graphed.
Configuration Management Configuration management monitors network and system configuration information so that the effects on network operation of various versions of hardware and software elements can be tracked and managed. With the increase in network devices, it is critical to be able to accurately identify the location of a network device. A detailed description meaningful to those tasked with dispatching resources when a network problem occurs should provide accurate location information. Making certain to have available contact information of the person or department
References: All reference material was taken from: Cisco (2007, July 11). Network Management System: Best Practices White Paper. Retrieved September 8, 2014. http://www.cisco.com/c/en/us/support/docs/availability/high-availability/15114-NMS-bestpractice.html#networkmanage