After the implementation phase, each network needs to be maintained at proper parameters by monitoring and management tools and processes. This section will cover the basic techniques used to deploy solid network management solutions.
Network Management Essentials
Simple Network Management Protocol
The network management system is usually based on the Simple Network Management Protocol (SNMP), which is a TCP/IP Application Layer protocol that uses IP within UDP. SNMP is used to share management information between network devices, usually between a management workstation and routers, switches, or other devices, as illustrated in Figure 2.11 below.
Figure 2.11 – Network Management Using SNMP
SNMP has evolved over the years and has now reached version 3 (SNMPv3). Network designers should demand that every environment uses SNMPv3, instead of the older unsecured SNMP versions 1 and 2, because of the advanced security features it provides. SNMP is used by network administrators and engineers to accomplish the following:
- Control network performance
- Troubleshoot
- Plan scalable enterprise solutions and intelligent services
SNMP accesses detailed information in Management Information Bases (MIBs) and it uses SNMP agents. The MIB is an object-oriented hierarchical database system stored locally on the network device. An example of a MIB entry is 1.3.6.1.2.1.2.2.1.20.0, with 1 being the root of the MIB tree and 0 being the final leaf.
The SNMP agent is used to send and receive information from the device to the Network Management Station (NMS), and vice versa. In order to do that, different types of SNMP messages are used. The NMS will run some kind of network management software (e.g., CiscoWorks) that retrieves and displays the SNMP information in a Graphical User Interface (GUI) format. The displayed information is used for controlling, troubleshooting, and planning.
Another SNMP concept is represented by community strings, which is the access control method. A community is a password that controls what group of people has access to certain information on the device.
The managed device contains the SNMP agent and the MIB that stores all the information. Different types of messages are used in order to get information from the NMS to/from the managed device (i.e., the monitored device), as shown below in Figure 2.12.
Figure 2.12 – SNMP Messages
The first message is called the Get Request. This is sent to the managed device when the NMS wants to get a specific MIB variable from the SNMP agent that runs on that device. The Get Next Request information is used to return the next object in the list after the Get Request message returns a value. The Get Bulk message works only in SNMPv3 environments, and it can be used to retrieve a large chunk of data (e.g., an entire table), reducing the need to have to use many Get Request and Get Next Request messages. This in turn reduces the overhead on bandwidth utilization on the link.
The Set Request message is sent by the NMS and is used to set a MIB variable on the agent. The Get Response message is the response from the SNMP agent to the NMS Get Request, Get Next Request, or Get Bulk messages.
A Trap is used by the SNMP agent to transmit unsolicited alarms to the NMS when certain conditions occur (e.g., device failures, state changes, or parameter modifications). Different thresholds can be configured on the managed device for different parameters (e.g., disk space, CPU utilization, memory utilization, or bandwidth utilization), and Traps are sent when the defined thresholds are reached. SNMPv3 introduced another message called the Inform Request. This is similar to a Trap message and is what a managed device will send to the NMS as an acknowledgement to other messages.
SNMPv3 provides the following security levels:
- NoAuthNoPriv: No authentication and no privacy mechanisms
- AuthNoPriv: Authentication (MD5, SHA) but no privacy mechanisms
- AuthPriv: The highest level of security; uses authentication (MD5, SHA) and privacy (DES)
Remote Network Monitoring
Remote Network Monitoring (RMON) is actually a management information base that allows you to monitor LAN traffic in the network environment proactively. It tracks individual data packets, and the number and size of those packets, as well as broadcast packets, network utilization, errors, and statistics.
RMON agents run on various network devices, such as routers, switches, or servers. If you do not want to run RMON on those specific devices because of the overhead, you can configure special RMON workstations as probes on specific network segments. RMON offers the possibility to diagnose faults within the LAN, which allows network tuning and planning for growth and utilization.
RMON is implemented in two versions, RMON 1 and RMON 2. RMON 2 is the most recent version and it offers more functionalities. RMON 1 operates only at the Physical and Data Link Layers, so it must be used only to probe, tune, plan, and search for faults on hubs (at the Physical Layer) and switches (at the Data Link Layer). RMON 2 provides much more functionality and can be used for Network Layer (Layer 3) applications, as well as for Layers 4 through 7. RMON 2 can also monitor database servers, exchange servers, e-mail, and web traffic.
NetFlow
A better solution to RMON in a Cisco environment is to use the proprietary solution called NetFlow. NetFlow is a monitoring and measurement technology that is superior to a simple SNMP/RMON solution, providing much more detail on the data that passes through a specific interface. NetFlow scales to a large number of interfaces and this makes it a great enterprise solution.
NetFlow is also a great solution for service providers because it supports customer service programs, and uses popular data warehousing and data mining solutions that are critical for competitive vendor offerings (e.g., flexible accounting and billing that can consider application usage, the time of day, the bandwidth utilization, or QoS elements). NetFlow is also a great tool for network scalability planning and overall analysis, as it can help lower the organization’s TCO.
The NetFlow management architecture (Figure 2.13) consists of the following components:
- NetFlow data export service
- NetFlow flow collector service
- NetFlow data analysis
Figure 2.13 – NetFlow Management Architecture
Data export service is at the top of the three-tier NetFlow architecture. This is where the data warehousing and data mining solutions occur. It captures the accounting statistics for traffic on the networking devices and it uses UDP to export data. This is a three-part process, which includes the following:
- Data switching
- Data export
- Data aggregation
The data is then exported to the second tier, the NetFlow flow collector service. At this level, using servers and workstations, you can complete actions such as data collection, data filtering, aggregation, data storage, and file system management using existing or third-party file systems.
Network data analysis is at the lowest tier, at the Access Layer. At this level, you can use network planning tools, overall network analysis tools, and accounting and billing tools, and you can export data to various database systems or Excel spreadsheets.
Cisco Discovery Protocol
Cisco Discovery Protocol (CDP) is a proprietary Cisco protocol that operates at Layer 2 (Data Link) between Cisco devices. Its main job is to summarize information it discovers about directly connected routers, switches, or other Cisco devices. The Cisco devices themselves do not forward any CDP frames to their other neighbors because their role is to share device information only between directly connected devices.
CDP is media and protocol independent, and it operates with TCP/IP, IPX, or AppleTalk. It can also run across different media types, such as LANs, ATM, and Frame Relay networks. Running CDP on external Internet connections is not recommended due to security issues (i.e., you should not expose information about your devices to outside users). In addition, it should not be configured on links going to non-Cisco devices because it is unnecessary.
Running the “show cdp neighbor” command on a device will give CDP-related information such as the following:
- MAC address of the directly connected neighbor
- Local interface connecting to that particular neighbor
- Information about the device type (router, switch, or other)
- Device platform/mode
- Port numbers

