The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Cisco CMTS Universal Broadband Series Router notifications supported by the MIB enhancements feature introduced in Cisco IOS Release 12.2SC. SNMP uses notifications to report events on a managed device. The notifications are traps or informs for different events. The router also supports other notifications that are not listed.
An SNMP agent can notify the SNMP manager when important system events occur, such as the following:
When an agent detects an alarm condition, the agent:
SNMP notifications are sent as one of the following:
To use SNMP notifications on your system, you must specify trap recipients. These recipients indicate where network registrar notifications are directed. Traps are enabled using the snmp-server enable traps command.
Many commands use the key word traps in the command syntax. Unless there is an option in the command to select either traps or informs, the keyword traps refers to traps, informs, or both. Use the snmp-server host command to specify whether to send SNMP notifications as traps or informs. The types of traps can be specified in command.
Note Most notification types are disabled by default. However, some notification types cannot be controlled with the snmp command. For example, some notification types are always enabled and other types are enabled by a different command. The linkUpDown notifications are controlled by the snmp trap link-status command. If you enter this command with no notification-type keywords, the default is set to enable all notification types controlled by the command.
Specify the trap types if you do not want all traps to be sent. Then use multiple snmp-server enable traps commands, one for each of the trap types that you used in the snmp host command. The event table must have an entry that specifies the action that is to be performed.
For detailed information about notifications and a list of notification types, refer the following Cisco documents at:
You can enable MIB notifications using either of the following procedures:
The Traps Sent with SNMP-Server Enabled Traps Configured guide at: http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a008021de3e.shtml
– To enable the notifications set the object to true(1).
– To disable the notifications, set the object to false(2).
Note If you issue the snmp-server enable 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.
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:
Note In the following tables, where no action required appears in the Recommended Action column, there might be instances where an application, such as trouble ticketing, occurs.
Table 4-1 lists notifications generated for events that might indicate the failure of the Cisco CMTS uBR router or conditions that might affect the router functionality.
These notifications indicate the failure of a line card or error conditions on the card that might affect the functionality of all interfaces and connected customers.
Table 4-2 lists ENTITY-MIB notifications that the Cisco CMTS uBR router cards and SPAs generate.
Table 4-3 lists CISCO-FLASH-MIB notifications that the Cisco CMTS uBR router flash cards generate.. These notifications indicate the failure of a flash card or error conditions on the card that might affect the functionality of all interfaces and connected custom.
Table 4-4 lists notifications that the router generates for link-related (interface) events.
Table 4-5 lists notifications that the router generates for Packet Forwarding Engine (PFE) events on the Cisco uBR10012 router. For Cisco uBR10012 router, the PFE is the parallel express forwarding network processor (PXF), which is part of the performance routing engine (PRE).
Table 4-6 lists notifications generated by the CMTS router for events related to system configuration.
Table 4-7 lists service notifications generated by the CMTS router to indicate conditions for services.
Table 4-8 lists notifications that the Cisco CMTS uBR router generates to indicate error conditions for routing protocols.
Table 4-9 lists notifications generated by the Cisco CMTS uBR router to indicate error conditions for routing services.
Table 4-10 lists alarm notifications generated by the router for SONET events.
Table 4-11 lists CISCO-STACK-MIB notifications generated by the router to indicate that a chassis module has become active or stopped responding. These notifications are supported by the Cisco CMTS router.
Table 4-12 lists CISCO-RTTMON-MIB notifications that can occur during round-trip time (RTT) monitoring.
Table 4-13 lists CISCO-ENVMON-MIB notifications generated for events that might indicate the failure of the Cisco CMTS uBR router or conditions that might affect the router functionality.
Table 4-14 lists CISCO-RF-MIB notifications that can occur in a redundant system. There are two types of notifications:
Table 4-16 lists the notifications that occur in the following supported MIBs:
Table 4-16 lists the notifications that occur in the DOCS-DIAG-MIB.
Table 4-17 lists the notifications that occur in the following supported MIBs: