Table Of Contents
Environmental or Functional Notifications
Routing Protocol Notifications
Redundancy Framework Notifications
Monitoring Notifications
This chapter describes the Cisco ASR 9000 Series routernotifications supported by the MIB enhancements feature introduced in Cisco IOS XR Software Release 3.7. SNMP (Simple Network Management Protocol) uses notifications to report events on a managed device. The notifications are traps for different events. The router also supports other notifications not listed.
This chapter contains the following sections:
SNMP Notification Overview
An SNMP agent can notify the SNMP manager when important system events occur, such as the following:
•
Interface or card starts or stops running
•
Temperature thresholds are crossed
•
Authentication failures occur
When an agent detects an alarm condition, the agent:
•
Logs information about the time, type, and severity of the condition
•
Generates a notification message, which it then sends to a designated IP host
SNMP notifications are sent as one of the following:
•
Traps—Unreliable messages, which do not require receipt acknowledgement from the SNMP manager.
To use SNMP notifications on your system, you must specify their recipients. These recipients indicate where Network Registrar notifications are directed. By default, all notifications are enabled, but no recipients are defined. Until you define the recipients, no notifications are sent.
Many commands use the traps keyword in the command syntax.
![]()
Note
Most notification types are disabled by default. However, some notification types cannot be controlled with the snmp command. For example, some notification types can be enabled by snmp or CLI (command-line interface) and other types are enabled by a combination of CLI and snmp. The linkUpDown notifications are controlled by the snmp trap link-status and snmp-server trap link ietf commands.
Specify the trap types to avoid having all traps sent, then use multiple snmp-server traps commands, one for each of the trap types used in the snmp host command.
Enabling Notifications
You can enable MIB notifications using either of the following procedures:
•
CLI—Specify the recipient of the trap message and specify the types of traps sent. The enabling command also specifies which types of traps are enabled. For detailed procedures, go to the following URL:
http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.7/vfw/command/reference/vfr37snp.html
•
Performing an SNMP SET operation with the setany command—To enable or disable MIB notifications, perform an SNMP SET operation on a specific object.
–
To enable the notifications, set the object to true (1).
–
To disable the notifications, set the object to false (2).
For detailed procedures, go to the following URL:
http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.7/system_management/command/reference/yr37snmp.html![]()
Note
If you issue the snmp-server traps command without a notification-type argument, the router generates traps for all types of events, which might not be desirable. Some MIBs require the user to set additional objects to enable some notifications.
Cisco SNMP Notifications
This section contains tables that describe a MIB event, why the event occurred, and a recommendation as to how to handle the event. Each table lists the following information:
•
Event—Event display
•
Description—What the event indicates
•
Probable cause—What might have caused the notification
•
Recommended action—Recommendation as to what should be done when the particular notification occurs
![]()
Note
In the following tables, where "no action is required" is documented, there might be instances where an application, such as trouble ticketing, occurs. For detailed information, go to:
http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.7/system_management/command/reference/yr37snmp.html
Environmental or Functional Notifications
Table 6-1 lists notifications generated for events that might indicate the failure of the Cisco Carrier Routing System or conditions that might affect router functionality.
Flash Card Notifications
Table 6-2 lists CISCO-FLASH-MIB notifications generated by Cisco Carrier Routing System flash cards. These notifications indicate the failure of a flash card or error conditions on the card that might affect the functionality of all interfaces.
Interface Notifications
Table 6-3 lists notifications generated by the router for link-related (interface) events.
Routing Protocol Notifications
Table 6-4 lists BGP4-MIB notifications that are Border Gateway Protocol (BGP) state changes generated by the Cisco Carrier Routing System to indicate error conditions for routing protocols and services.
Table 6-4 Routing Protocol Notifications
Event Description Probable Cause Recommended Action bgpEstablishedThe BGP FSM1 enters the ESTABLISHED state. It becomes active on the router.
The BGP routing protocol changed status.
No action is required.
bgpBackwardTransitionIndicates BGP protocol transition from a higher-level state to a lower-level state. The prefix count for an address family on a BGP session exceeded the configured threshold value.
The BGP routing protocol changed status.
This threshold value is configured using the CLI command neighbor nbr_addr max_prefixes
[threshold] [warning-only]
1 FSM = finite state machine
Redundancy Framework Notifications
Table 6-5 lists CISCO-RF-MIB notifications that can occur in a redundant system. There are two types of notifications:
•
Switch of Activity (SWACT)—Either a forced or automatic switch of active status from the active unit to the standby unit. The former standby unit is now referred to as the active unit.
•
Progression—Process of making the redundancy state of the standby unit equivalent to that of the active unit. This includes transitioning the RF state machine through several states, which drives the clients on the active unit to synchronize any relevant data with their peer on the standby unit.