|
|
This chapter contains information on the following system management topics:
Simple Network Management Protocol (SNMP) is an application-layer protocol that allows an SNMP manager, such as a network management system (NMS), and an SNMP agent on the managed device to communicate. Remote Monitoring (RMON) allows you to see the activity on network nodes. By using RMON in conjunction with the SNMP agent on the Cisco 6400, you can monitor traffic through network devices, segment traffic that is not destined for the Cisco 6400, and create alarms and events for proactive traffic management.
For a complete description of SNMP, SNMP Management Information Bases (MIBs), and how to configure SNMP, see the "Configuring Simple Network Management Protocol (SNMP)" chapter of the "Cisco IOS System Management" part of the Cisco IOS Configuration Fundamentals Configuration Guide.
To identify and download MIBs supported by the Cisco 6400, go to the Cisco MIB website on Cisco.com at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
The SNMPv3 Proxy Forwarder feature enables all NSP and NRP-2 components of the Cisco 6400 system to be managed as one functional entity. With the Proxy Forwarder feature enabled, the NSP:
 |
Note The SNMPv3 Proxy Forwarder feature was introduced in Cisco IOS Releases 12.1(4)DB and 12.1(4)DC for the node route processor 2 (NRP-2). The feature is not supported in earlier releases or by the node route processor 1 (NRP-1). |
To configure the Proxy Forwarder feature, complete the following tasks:
To enable the NSP to act as the proxy forwarder for the NRP-2s in the Cisco 6400 chassis, enter the following NSP commands in global configuration mode:
| Command (Entered on the NSP) | Purpose | |
|---|---|---|
| Step 1 | ||
| Step 2 | Configures a new user to an SNMPv3 group. Make sure that you use the same groupname in Steps 1 and 2. |
|
| Step 3 | ||
| Step 4 |
When you complete the previous steps, the NSP automatically generates snmp-server user and snmp-server group commands in the configuration.
Each time the NSP reloads or you insert an NRP-2 into the chassis, the NSP automatically generates snmp-server engineID commands in the configuration.
|
Note Do not modify or delete the automatically generated commands, because doing so may prevent SNMP from working properly. |
In the following example, the NSP is configured to act as the proxy forwarder:
The previous commands cause the NSP to automatically generate the following commands:
To configure the NRP-2 to communicate with the NSP as the proxy forwarder, complete the following steps in global configuration mode:
When you complete the previous steps, the NRP-2 automatically generates snmp-server user and snmp-server group commands in the configuration.
If you do not select any specific types of traps, the NRP-2 also automatically generates snmp-server enable traps commands to specify all available types of traps.
|
Note Do not modify or delete the automatically generated commands, because doing so may prevent SNMP from working properly. |
In the following example, the NRP-2 is configured to allow the NSP to act as the proxy forwarder:
The previous commands cause the NRP-2 to automatically generate the following commands:
To verify successful configuration of the SNMPv3 Proxy Forwarder feature, use the more system:running-config EXEC command. On both the NSP and NRP-2, check that you properly configured the commands described in the previous tasks.
Also check that the automatically generated commands correctly appear on both the NSP and NRP-2 running configurations. On the NSP, the three automatically generated commands that include an IP address are generated for every active NRP-2 in the chassis. The other automatically generated commands are created only once, regardless of the number of active NRP-2s installed in the chassis.
The Remote Monitoring (RMON) option makes individual nodal activity visible and allows you to monitor all nodes and their interaction on a LAN segment. RMON, used in conjunction with the SNMP agent in the NSP, allows you to view traffic that flows through the switch as well as segment traffic not necessarily destined for the switch. Combining RMON alarms and events with existing MIBs allows you to choose where proactive monitoring will occur.
RMON can be very data and processor intensive. Users should measure usage effects to ensure that router performance is not degraded by RMON and to minimize excessive management traffic overhead. Native mode is less intensive than promiscuous mode.
The Cisco 6400 supports both RMON and ATM RMON.
For a complete description of the RMON MIB agent specification, and how it can be used in conjunction with SNMP to monitor traffic using alarms and events, see the "Configuring RMON Support" section of the "Cisco IOS System Management" part of the Cisco IOS Configuration Fundamentals Configuration Guide.
For a complete description and configuration information for ATM RMON on the NSP, see the "Configuring ATM Accounting and ATM RMON" chapter of the ATM Switch Router Software Configuration Guide.
Alarms on the NSP help to monitor equipment and identify the cause of physical system problems within the central office (CO). There are three levels of alarms: minor, major, and critical, and there are many sources of alarm conditions. Temperature thresholds are the only alarm source that you can configure, but alarms can be triggered by card failure, SONET APS failures, and NRP failures.
The Cisco 6400 includes environmental monitoring hardware and a digital thermometer that measures the temperature of the intake airflow and the temperature at the hottest part of the chassis. Temperature thresholds for each alarm type and location are automatically set, based on empirically determined values that vary depending on the number and type of boards inserted in the chassis. In addition to the automatically set thresholds, you can set your own thresholds for minor and major temperature alarms. You can also disable the minor and major temperature alarms. You cannot, however, change the threshold for or disable critical alarms.
To set thresholds for the minor and major temperature alarms at the two monitored locations, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
Specifies thresholds for the intake and core major and minor alarms in degrees Celsius. |
To disable the minor or major temperature alarms for either monitored location, use the no form of the facility-alarm command.
In the following example, the major core temperature alarm is set to 35°C:
In the following example, the minor intake temperature alarm is disabled:
To check the temperature thresholds, use the show facility-alarm status EXEC command, described in the next section.
To display the status of current major and minor alarms and the settings of all user-configurable alarm thresholds, use the following EXEC command:
You can use the clear facility-alarm EXEC command to reset the external alarm relays and stop an auditory alarm indication. However, the alarm cause and LED indication may still be in effect, and the alarm can be viewed with the show facility-alarm status EXEC command until the alarm is cleared at the source. To clear the source of an alarm, you must specify the source as either the secondary CPU, one of the power entry modules (PEMs), or any device installed in the specified slot or subslot.
Clearing the source of an alarm is useful for:
The Cisco 6400 remembers the type of card originally installed in each slot or subslot, and removing a card activates an alarm.
To clear the specified alarm, reset the alarm contacts, and remove the source of the alarm, use the following EXEC command:
|
Note If all interfaces on an NLC or NRP are shut down prior to card removal (using the shutdown interface command), the Cisco 6400 will not generate an alarm. |
The following example shows how to clear all current external alarm relays:
Suppose you have an NRP-1 in slot 2. Removing the NRP-1 and inserting an OC-12 NLC will generate an alarm. The following example shows how to clear the alarm:
To verify that you cleared the alarms, use the show facility-alarm status EXEC command.
Posted: Mon Jun 23 14:23:04 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.