How To Configure Rmon On Cisco Me 2600X On Ios 2.5A (Cisco) With A Network Monitor On A Network Device (Network) On A Pnet (Network Monitor) On An Ip

Transcription

1 Remote Network Monitoring and Alarm Troubleshooting This chapter describes remote network monitoring (RMON) and alarm troubleshooting. RMON Procedures, page 1 Understanding RMON, page 1 Alarm Troubleshooting, page 4 RMON Procedures To configure RMON using Cisco IOS commands, complete the following procedures: Configuring RMON Settings, on page 2 Displaying RMON Status, on page 3 Understanding RMON RMON is a standard monitoring feature that allows various network agents and console systems to exchange network monitoring data. RMON provides you with comprehensive network-fault diagnosis, planning, and performance-tuning information. You can use the RMON feature with the Simple Network Management OL

2 Configuring RMON Settings Remote Network Monitoring and Alarm Troubleshooting Protocol (SNMP) agent in the switch to monitor all the traffic flowing among switches on all connected LAN segments as shown in the figure below. Figure 1: Remote Monitoring Example Default RMON Configuration RMON is disabled by default; no alarms or events are configured. Configuring RMON Settings 1. enable 2. configure terminal 3. rmon alarm number variable interval {delta absolute} rising-threshold value [event-number] falling-threshold value [event-number] [owner string] 4. rmon event number [log] [trap community] [description string] [owner string] 5. exit Step 1 Command or Action enable Purpose Enables privileged EXEC mode. 2 OL

3 Remote Network Monitoring and Alarm Troubleshooting Displaying RMON Status Step 2 Command or Action Switch# enable configure terminal Purpose Enter your password if prompted. Enters global configuration mode. Step 3 Switch# configure terminal l rmon alarm number variable interval {delta absolute} rising-threshold value [event-number] falling-threshold value [event-number] [owner string] Switch(config)# rmon alarm 10 ifentry delta rising-threshold 15 1 falling-threshold 0 owner user1 Sets a RMON alarm on a MIB object. This example configures RMON alarm number 10. The alarm monitors the MIB variable ifentry.20.1 once every 20 seconds until the alarm is disabled, and checks the change in the rise or fall of the variable. If the ifentry.20.1 value shows a MIB counter increase of 15 or more, such as from to , the alarm is triggered. The alarm in turn triggers event number 1, which is configured with the rmon event command. The possible events include a log entry or an SNMP trap. If the ifentry.20.1 value changes by 0, the alarm is reset and can be triggered again. Step 4 rmon event number [log] [trap community] [description string] [owner string] Switch(config)# rmon event 1 log trap eventtrap description "High ifouterrors" owner user Adds or removes an event in the RMON event table that is associated with an RMON event number. This example creates RMON event number 1, which is defined as High ifouterrors, and generates a log entry when the event is triggered by an alarm. The user user owns the row that is created in the event table by this command. This example also generates a Simple Network Management Protocol (SNMP) trap when the event is triggered. Step 5 exit Exits configuration mode. Switch(config)# exit Displaying RMON Status To display the current RMON agent status on the device, use one or more of the privileged EXEC commands described in Table 1: Commands for Displaying RMON Status, on page 3. Table 1: Commands for Displaying RMON Status Command show rmon alarms show rmon events Purpose Displays the RMON alarm table. Displays the RMON event table. OL

4 Alarm Troubleshooting Remote Network Monitoring and Alarm Troubleshooting Alarm Troubleshooting This section gives a description, severity, and troubleshooting procedure for each commonly encountered Cisco ME 2600X alarm and condition. Trouble-Clearing Procedures This section list alarms alphabetically and includes some conditions commonly encountered when troubleshooting alarms. The severity, description, and troubleshooting procedure accompany each alarm and condition. Note When checking alarms, ensure that alarm suppression is not enabled on the port. FMEA FAN Alarm Default Severity: Critical (CR), Service-Affecting (SA) This alarm gets raised when a power failure has encountered in any of the fan modules. Precondition: Make sure FMEA is enabled on Cisco ME 2600X. If not issue 'fmea enable 1' on Cisco ME 2600X. Clearing the FMEA FAN Alarm 1. Check all connections are intact inside the module and replace the fan module. Check all connections are intact inside the module and replace the fan module. Sample output for FMEA: *Nov 28 14:04:20.366: %NGXP_FMEA-1-ALARM: FMEA Alarm Notification for index:23 Fault Desc:FAN.01:FAN alarm with Timestamp:14:04:23 UTC To view the last occurrence of FMEA alarm: Switch# fmea alarms Alarm raised:count:1 Index:23=>FAN.01:FAN alarm FirstTimeStamp:13:58:23 UTC CurTimeStamp:14:02:23 UTC If the condition does not clear, log into the Technical Support Website at index.html for more information or call Cisco TAC ( ). 4 OL

5 Remote Network Monitoring and Alarm Troubleshooting Trouble-Clearing Procedures MAC-BD-LIMT-REACHED Default Severity: Minor (MN), Non-Service-Affecting (NSA) The MAC Bridge Domain Limit Reached (MAC-BD-LIMT-REACHED) alarm is raised when the MAC address learnt on the bridge domain has reached a limit of 32,000. Clearing the MAC-BD-LIMT-REACHED Alarm 1. Reduce the MAC address size on the bridge domain. Reduce the MAC address size on the bridge domain. If the condition does not clear, log into the Technical Support Website at index.html for more information or call Cisco TAC ( ). MAC-SYS-LIMT-REACHED Default Severity: Minor (MN), Non-Service-Affecting (NSA) The MAC System Limit Reached (MAC-SYS-LIMT-REACHED) alarm is raised when the system MAC address limit of 32,000 is reached. Clearing the MAC-SYS-LIMT-REACHED Alarm 1. Reduce the system MAC address size to less than 32,000. Reduce the system MAC address size to less than 32,000. If the condition does not clear, log into the Technical Support Website at index.html for more information or call Cisco TAC ( ). OL

6 Trouble-Clearing Procedures Remote Network Monitoring and Alarm Troubleshooting 6 OL