Table Of Contents

Monitoring Notifications

Notification Overview

Enabling Notifications

Enabling Notifications Using the CLI

Enabling Sensor Traps Using an SNMP Command

Enabling Informs Using the CLI and SNMP Manager

Environmental or Functional Notifications

Cisco 7304 Line Card Notifications

Interface Notifications

PFE-MIB Notifications

Threshold Notifications

Service Notifications

Routing Protocol Notifications

RTT Monitor Notifications

Monitoring Notifications

---

This chapter describes the Cisco 7304 router notifications supported by the MIB enhancements feature introduced in Cisco IOS Release 12.2SB. 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 not listed.

---

Note Many commands use the keyword traps in the command syntax. The keyword traps refers to notifications that are either traps, informs, or both. The tables in this chapter use the term traps even though the event might be an inform.

---

This chapter contains the following sections:

•Notification Overview

•Enabling Notifications

•Environmental or Functional Notifications

•Cisco 7304 Line Card Notifications

•Interface Notifications

•PFE-MIB Notifications

•Threshold Notifications

•Service Notifications

•Routing Protocol Notifications

•RTT Monitor Notifications

Notification Overview

An SNMP agent can notify the manager when important system events occur, such as the following:

•An 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 either:

•Traps—Unreliable messages, which do not require receipt acknowledgement from the SNMP manager.

•Informs—Reliable messages, which are stored in memory until the SNMP manager issues a response. Informs use more system resources than traps.

The following URLs provide access to additional SNMP information:

•http://www.cisco.com/warp/public/477/SNMP/index.html—Provides links to general SNMP information and tips for using SNMP to gather data.

•http://www.cisco.com/warp/public/477/SNMP/mibs_9226.shtml—lists frequently asked questions (FAQs) about Cisco MIBs.

Enabling Notifications

You can enable notifications using the command line interface (CLI) and the SNMP setany command. This section describes how to enable:

•SNMP notifications using the CLI

•Sensor MIB traps using the SNMP setany command

•Informs

---

Note You must use the setany command to enable sensor traps.

---

---

Note Many of the notifications can also be enabled through SNMP. SNMP notifications can be sent as traps or inform requests. The snmp-server enable traps <notification-type> command enables both traps and inform requests for the specified notification types.

---

Enabling Notifications Using the CLI

To use the command line interface (CLI) to enable the Cisco 7304 router to send SNMP notifications (traps or informs) perform the following steps.

---

Step 1 Make sure SNMP is configured on the Cisco 7304 router (see the "Enabling SNMP Support" section on page 2-4).

Step 2 Enable traps on the Cisco 7304 router. To enable specific traps, include a notification-type keyword in the command. (Table 4-1 lists keywords.) Enter a separate command for each trap type. For example, the command snmp-server enable traps entity configures the Cisco 7304 router to generate a trap for configuration changes.

Router(config)# snmp-server enable traps [ notification-type ]

---

Note If you issue the snmp-server enable traps command without a notification-type keyword, the Cisco 7304 router generates traps for all types of events, which might not be desirable.

---

Step 3 Identify (by IP address) the host to receive SNMP traps from the Cisco 7304 router:

Router(config)#snmp-server host <host-address> version <SNMP version> <community/user(V3)> 
udp-port<UD Port No>

Step 4 To disable traps on the Cisco 7304 router, enter the following command. If you omit notification-type, all traps are disabled. If you include a keyword, only those types of traps are disabled.

Router(config)# no snmp-server enable traps [ notification-type ]

---

Table 4-1 Cisco 7304 Router Notification-Type Keywords 

Keyword	Description
alarms	Send a notification when an alarm occurs.
atm subif	Send a notification for alarms and events on ATM subinterfaces.
bgp	Send a notification for BGP state changes.
config	Send a notification when the router configuration changes.
ds1	Send a notification for DS1-related alarms and events.
ds3	Send a notification for DS3-related alarms and events.
entity	Send a notification when the router configuration (ENTITY-MIB) changes.
envmon	Send a notification when an environmental threshold is exceeded (for example, when the critical temperature threshold is exceeded).
fru-ctrl	Send a notification when the status of a field replaceable unit (FRU) changes.
hsrp	Send a notification for Hot Standby Routing Protocol (HSRP) events.
mpls traffic-eng	Send a notification for events related to MPLS traffic engineering.
pppoe	Send a notification for Point-to-Point Protocol over Ethernet (PPPoE) events.
pim	Send a notification for Protocol Independent Multicast (PIM) events.
rtr	Send a notification for SA Agent (RTR) events.
snmp [authentication] [linkdown] [linkup] [coldstart] [warmstart]	Generate an RFC 1157 generic trap for the following events: authentication—An authentication failure occurs. linkdown—An interface fails. linkup—An interface becomes active. coldstart—The router is powered on. warmstart—The router is restarted.
syslog	Send error message notifications (Cisco Syslog MIB). Specify the level of messages to be sent with the logging history level command.

Enabling Sensor Traps Using an SNMP Command

To use the SNMP setany command to enable or disable SensorThresholdNotification traps, follow these steps:

---

Step 1 Set entSensorThresholdNotificationEnable to true(1) value for each threshold. This variable controls the generation of entSensorThresholdNotification traps for this threshold. For example, type:

setany -v2c IP 34.3.2.5 private entSensorThresholdNotificationEnable.X.y -i 1

Step 2 To disable the entSensorThresholdNotification trap, use the variable false(2).

---

Enabling Informs Using the CLI and SNMP Manager

To use the SNMP setany command to enable or disable informs, follow these steps:

---

Step 1 Using the command line interface, set entSensorThresholdNotificationEnable to true(1) value for each threshold. This variable controls the generation of entSensorThresholdNotification informs for this threshold. For example, type:

setany router(config)#snmp-server enable informs

router(config)#snmp-server host <host-address> version <SNMP version> <community/userName> 
udp-port<UD Port No>

Step 2 Using the SNMP manager, type:

winstar:/opt/ats3.6.0>inform <SNMP version> <dst_addr>  <community/userName> 
<snmpTrapOID_value(OID)> [variable_name type value . . .]

Step 3 To disable the entSensorThresholdNotification trap, use the variable false(2).

---

Environmental or Functional Notifications

Table 4-2 lists the notifications which are traps and informs generated for events that might indicate the failure of the Cisco 7304 router or conditions that might affect the router's functionality.

Table 4-2 Environmental or Functional Traps 

Event	Trap and Trap Objects	Notes
	CISCO-ENTITY-FRU-CONTROL-MIB
Operational status	cefcModuleStatusChange cefcModuleOperStatus cefcModuleStatusLastChangeTime. entPhysicalDescr entPhysicalName	The cefcModuleStatusChange trap is supported only for standby RP. This trap is enabled through the CLI command: [no] snmp-server enable trap fru-ctrl
Operational status	cefcMIBNotificationEnablesGroup	The cefcMIBEnableStatusNotification indicates whether the system produces the cefcMIBNotifications. A false value will prevent FRU notifications from being generated by this system.
	CISCO-ENVMON-MIB
Critical condition shutdown imminent	ciscoEnvMonShutdownNotification No objects are included in the trap so that it can be encoded and sent as soon as possible.	Sent when a testpoint nears a critical state and the router is about to shut down (for example, if auto-shutdown is enabled and the chassis core or inlet temperature reaches critical state and remains there for more than 2 minutes). Enable this trap through the CLI or by setting ciscoEnvMonEnableShutdownNotification to true(1). Note A shutdown may occur before the notification is sent. Therefore, a management application should not rely on this notification.
Power supply status	ciscoEnvMonRedundantSupplyNotification ciscoEnvMonSupplyStatusDescr ciscoEnvMonSupplyState	Sent when a Power Entry Module fails. Enable this trap through the CLI or by setting ciscoEnvMonEnableRedundantSupplyNotification to true(1).
Temperature Status	ciscoEnvMonTemperatureNotification ciscoEnvMonTemperatureStatusDescr ciscoEnvMonTemperatureStatusValue ciscoEnvMonTemperatureState	Sent when the core or inlet temperature is outside its normal range, when ciscoEnvMonState is at the Warning or Critical state. Enable this trap through the CLI or by setting ciscoEnvMonEnableTemperatureNotification to true(1).
1 The cefcFRUPowerAdminStatus is on(1) when a power supply is disabled. When there is a power supply, the cefcFRUPowerAdminStatus is always on(1) for both power supplies, regardless if the power supply is disabled. 2 Be aware that ENVON-MIB traps occur; but they are not supported. 3 To enable and disable CISCO-ENTITY-FRU-CONTROL MIB traps, use the <no> snmp-server enable trap fru-ctrl CLI command. 4 The cefcFRUInserted and cefcFRIRemoved traps are generated for line cards.

Cisco 7304 Line Card Notifications

Table 4-3 lists the traps and notifications generated by Cisco 7304 router line cards. These traps indicate the failure of a line card or error conditions on the card that might affect the functionality of all interfaces and connected customers. The following is a list of Cisco 7304 line card temperature and voltage sensors:

•Temperature sensors:

–temperature sensor 1—warning high

–temperature sensor 2—critical high

–temperature sensor 3—shut high

•Voltage sensors:

–voltage sensor 1—warning low

–voltage sensor 2—warning high

–voltage sensor 3—critical low

–voltage sensor 4—critical high

–voltage sensor 5—shut low

–voltage sensor 6—shut high

---

Note All of the sensors generate traps if the voltage passes the threshold level.

---

Table 4-3 Line Card Traps 

Event	Trap and Trap Objects	Notes
	ENTITY-MIB
Line card inserted	entConfigChange	Trap generated when an entry for the Cisco 7304 line card is added to the entPhysicalTable (which causes the value of entLastchangeTime to change).
	CISCO-ENTITY-SENSOR-MIB
	entSensotThresholdNotification entSensorThresholdValue entSensorValue	Notification indicates sensor devices in the system and provides the ability to monitor system status.
Line card errors	CISCO-ENTITY-ALARM-MIB
	ceAlarmAsserted ceAlarmHisEntPhysicalIndex ceAlarmHistAlarmType ceAlarmHistSeverity ceAlarmHistTimeStamp	If you manually shut down the line card, then you get the line card error. Sent when the alarm Card Stopped Responding OIR is asserted.
	CISCO-ENTITY-FRU-CONTROL-MIB
Line card inserted.	cefcFRUInserted entPhysicalContainedIn entPhysicalDescr entPhysicalNam	•The trap indicates the entPhysicalIndex of the slot that the line card was inserted in. •Enable/disable this trap through the CLI command: [no] snmp-server enable trap fru-ctrl •Traps are generated for line cards only.
Line card removed.	cefcFRURemoved entPhysicalContainedIn entPhysicalDescr entPhysicalName	Traps are generated for line cards only.

Interface Notifications

Table 4-4 lists the notifications which are traps and informs generated by the router for link-related (interface) events and alarms supported by the Cisco 7304 interfaces.

Table 4-4 Link Traps and Alarm Notifications 

Event	Trap and Trap Objects	Notes
	IF-MIB
Link Down	linkDown ifIndex ifAdminStatus ifOperStatus ifDesc ifType local	Sent when a link is about to enter the Down state, which means it can not transmit or receive traffic. The ifOperStatus object shows the link's previous state. Value is down(2). To see if link traps are enabled or disabled on an interface, check ifLinkUpDownTrapEnable (IF-MIB) for the interface. To enable link traps, set ifLinkUpDownTrapEnable to enabled(1). Enable the IETF (RFC 2233) format of link traps by issuing the CLI command snmp-server trap link ietf.
Link Up	linkUp ifIndex ifAdminStatus ifOperStatus ifDesc ifType local	Sent when a link's state is no longer Down. The value of ifOperStatus indicates the link's new state. Value is up(1). To see if link traps are enabled or disabled on an interface, check ifLinkUpDownTrapEnable (IF-MIB) for the interface. To enable link traps, set ifLinkUpDownTrapEnable to enabled(1). Enable the IETF (RFC 2233) format of link traps by issuing the CLI command snmp-server trap link ietf.
	ceAlarmAsserted ceAlarmHistEntPhysicalIndex ceAlarmHistAlarmType ceAlarmHistSeverity ceAlarmHistTimeStamp	Asserted—Indicates that the condition described by the alarm exists. The agent generates this trap when a physical entity asserts an alarm.
	ceAlarmAsserted	Asserted—Indicates that the condition described by the alarm does not exist. This object specifies a severity threshold governing the generation of ceAlarmAsserted notifications.

PFE-MIB Notifications

Table 4-5 lists the notifications which are traps and informs generated by the router for packet forwarding engine (PFE) events. On the Cisco 7304 router, the PFE is the parallel express forwarding network processor (PXF), which is part of the performance routing engine (PRE).

Table 4-5 PFE Traps 

Event	Trap and Trap Objects	Notes
Threshold exceeded	CISCO-ENTITY-PFE-MIB
	cePfeHistThldEvent cePfeHistEntPhysIndex cePfeHistType cePfeHistThld cePfeHistValue	Sent when PFE utilization or efficiency reaches or exceeds a threshold. For example, if the current PFE utilization (cePfePerfCurrentUtilization) reaches or exceeds the threshold cePfePerfConfigThldUtilization, SNMP generates a thldUtilizationEvent. cePfeHistType indicates the type of event that occurred. See the MIB object HistEventType for details about event types. Enable this trap through the CLI or by setting cePfeHistNotifiesEnable to notify(3) or logAndNotify(4).

Threshold Notifications

Table 4-6 lists the notifications which are traps and informs that can occur when an environmental threshold is exceeded. The threshold notifications indicate that a threshold violation occurred.

Table 4-6 MPLS-VPN Traps 

Event	Trap and Trap Objects	Notes
	CISCO-VPN-MIB
Threshold crossed	mplsNumVrfRouteMidThreshExceeded	Enables a notification of a warning that the number of routes created has crossed the warning threshold. This warning is sent only at the time the warning threshold is exceeded. Note This notification is sent to the NMS only at the time the threshold is exceeded. Whenever the number of routes falls below this threshold and exceeds the threshold again, a notification is sent to the NMS.
Threshold crossed	mplsNumVrfRouteMaxThreshExceeded	Enables a notification that a route creation attempt was unsuccessful because the maximum route limit was reached. Another notification is not sent until the number of routes falls below the maximum threshold and reaches the maximum threshold again. The max-threshold value is determined by the maximum routes command in VRF configuration mode. Note A trap notification is sent to the NMS when you attempt to exceed the maximum threshold. Another notification is not sent until the number of routes falls below the maximum threshold and reaches the maximum threshold again.
Threshold crossed	mplsLdpFailedInitSessionThresholdExceeded	Trap generated when a local LSR and an adjacent LDP peer attempt to set up an LDP session between them, but fail to do so after a specified number of attempts. The default number of attempts is 8. This default value is implemented in Cisco IOS and cannot be changed using either the CLI or an SNMP agent. Note Eight failed attempts to establish an LDP session between a local LSR and an LDP peer, due to any type of incompatibility between the devices, causes this notification message to be generated.

Service Notifications

Table 4-7 lists the notifications which are traps and informs generated by the router to indicate conditions for services.

Table 4-7 MPLS-Service Traps 

Event	Trap and Trap Objects	Notes
	CISCO-VPN-MIB
Status	MplsVrfIfUp	Enables a notification for the assignment of a VPN routing or forwarding instance (VRF) to an interface that is operational or for the transition of a VRF interface to the operationally up state.
Status	mplsVrfIfDown,	Enables a notification for the removal of a VRF from an interface or the transition of an interface to the down state.
	MPLS-LDP-MIB
MPLS LDP Session Up	mplsLdpSessionUp	Trap generated when an LDP entity (a local LSR) establishes an LDP session with another LDP entity (an adjacent LDP peer in the network).
MPLS LDP Session /Down	mplsLdpSessionDown	Trap generated when an LDP session between a local LSR and its adjacent LDP peer is terminated.
	Note This implementation of the MPLS LDP MIB traps for Cisco IOS Release 12.0(21)ST is limited to read-only (RO) permission for MIB objects, except for MIB object mplsLdpSessionUpDownTrapEnable has been extended to be writeable (WO) by the SNMP agent.
	mplsLdpPathVectorLimitMismatch	Trap generated when a local LSR establishes an LDP session with its adjacent peer LSR, but the two LSRs have dissimilar path vector limits. The value of the path vector limit can range from 0 through 255; a value of 0 indicates that loop detection is off; any value other than zero up to 255 indicates that loop detection is on and, in addition, specifies the maximum number of hops through which an LDP message can pass before a loop condition in the network is sensed. We recommend that all LDP-enabled routers in the network be configured with the same path vector limit. Accordingly, the mplsLdpPathVectorLimitMismatch object exists in the MPLS LDP MIB to provide a warning message to the NMS when two routers engaged in LDP operations have a dissimilar path vector limit.
	MPLS-TE-MIB
MPLS Tunnel Up	mplsTunnelUp MplsTunnelIndex mplsTunnelInstance mplsTunnelIngressLSRId mplsTunnelEgressLSRId mplsTunnelAdminStatus mplsTunnelOperStatus	Notification generated when the mplsTunnelOperStatus object for a configured tunnel is about to transition from the Down state to any state except NotPresent. Note The value of mplsTunnelOperStatus indicates the transitioning state of the tunnel object.
MPLS Tunnel Down	mplsTunnelDown mplsTunnelIndex mplsTunnelInstance mplsTunnelIngressLSRId mplsTunnelEgressLSRId mplsTunnelAdminStatus mplsTunnelOperStatus	Notification generated when the mplsTunnelOperStatus object for a configured tunnel is about to transition to the up(1) or the down(2) state respectively. Note The value of mplsTunnelOperStatus indicates the previous state of the tunnel.
MPLS Tunnel Rerouted	mplsTunnelRerouted mplsTunnelIndex mplsTunnelInstance mplsTunnelIngressLSRId mplsTunnelEgressLSRId mplsTunnelAdminStatus mplsTunnelOperStatus	Notification generated when a tunnel is rerouted or reoptimized. Note If the actual path is used, the new path might be written to mplsTunnelRerouted after the notification is issued.

Routing Protocol Notifications

Table 4-8 lists the notifications which are traps and informs generated by the Cisco 7304 router to indicate error conditions for routing protocols and services.

Table 4-8 Routing Protocol Traps 

Event	Trap and Trap Objects	Notes
BGP State Transitions	BGP4-MIB
	bgpEstablished bgpPeerLastError bgpPeerState	Trap generated when the BGP protocol becomes active on the router (it enters the Established state).
	bgpBackwardTransition bgpPeerLastError bgpPeerState	Trap generated when BGP transitions from a higher-level state to a lower-level state.

RTT Monitor Notifications

Table 4-9 lists the notifications which are traps and informs that can occur during round-trip time (RTT) monitoring.

Table 4-9 RTT Monitor Traps 

Event	Trap and Trap Objects	Notes
Connection Change	CISCO-RTTMON-MIB
	rttMonConnectionChangeNotification rttMonCtrlAdminTag rttMonHistoryCollectionAddress rttMonCtrlOperConnectionLostOccurred	Notification indicates that the value of rttMonCtrlOperConnectionLostOccurred changed, which occurs when the connection to a target has either failed to be established or was lost and then re-established. Note that this is a connection to a target only, not to a hop in the path to the target.
Timeout	CISCO-RTTMON-MIB
	rttMonTimeoutNotification rttMonCtrlAdminTag rttMonHistoryCollectionAddress rttMonCtrlOperTimeoutOccurred	Notification indicates that a timeout occurred or was cleared, during an RTT probe. (The system sends the notice when the value of rttMonCtrlOperTimeoutOccurred changes).
Threshold crossed	CISCO-RTTMON-MIB
	rttMonThresholdNotification rttMonCtrlAdminTag rttMonHistoryCollectionAddress rttMonCtrlOperOverThresholdOccurred	Notification indicates that a threshold violation occurred during an RTT probe, or that a previous violation has subsided in a subsequent RTT operation.