Setup guide

6-4
Cisco 6400 Software Setup Guide
OL-1183-04
Chapter6 SNMP, RMON, and Alarm Configuration
Remote Monitoring
Verifying the SNMPv3 Proxy Forwarder
To verify successful configuration of the SNMPv3 Proxy Forwarder feature, use the
moresystem: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.
Remote Monitoring
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
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.
Configuring Temperature Threshold Alarms
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.