Cisco CMTS Universal Broadband Series Router MIB Specifications Guide 12.2 BC

Indicates that the status of a module has changed. A management application can use this trap to update the status of a module it manages.

Module has unknown state

Enter the show module command to view error message details. For Syslog messages associated with this event, consult Messages and Recovery Procedures.

A line card is provisioned for a slot but it is not present in the slot.

Insert a configured line card in the specific slot.

Module is operational

No action is required.

Module has failed due to some condition

Enter the show module command to view error message details. For Syslog messages associated with this event, consult Messages and Recovery Procedures.

Indicates that the power status of a field replaceable unit has changed.

FRU is powered off because of an unknown problem.

Enter the show power command to check the actual power usage.For Syslog messages associated with this event, consult Messages and Recovery Procedures

FRU is powered on

No action is required.

FRU is administratively off

No action is required.

FRU is powered off because available system power is insufficient

Enter the show power command to check the actual power usage.

Indicates that a FRU was inserted. The trap indicates the entPhysicalIndex of the slot that the line card was inserted in.

A new field replaceable unit like a line card, SIP and SPA modules, fan, port, power supply, or redundant power supply was added.

No action is required; but you can enable this trap through the CLI or by setting cefcMIBEnableStatusNotification to true(1).

Indicates that a FRU was removed and indicates the entPhysicalIndex of the slot from which the line card was removed.

A field replaceable unit like line cards, SIP and SPA modules, fan, ports, power supply, or redundant power supply was removed.

Replace the field replaceable unit.

Indicates that a FRU status has changed.

The chassis temperature is too high, a minor or major alarm has been detected.

Inspect the indicated component closely to determine why it is operating out of the normal operating temperature range and whether it will eventually exceed the allowed operating temperature range.

A redundant power supply has been powered off.

Replace the field replaceable unit.

Router's cooling fan could be close to failure.

One or more fans in the system fan tray have failed. Although this is a minor alarm, system components could overheat and be shut down.

Replace the fan as soon as possible or the system might shut itself down or fail to operate properly.

Indicates that a FRU status has changed.

A redundant power supply has been powered on.

No action required.

RAM to CPU Usage

TBD

An entry for the line card or a shared port adapter is removed from the entPhysicalTable (which causes the value of entLastchangeTime to change).

A line card was removed.

Replace the field replaceable unit.

Indicates that the line card operational state changed. A management application uses this trap to update the status of a module that it is managing.

A line card is provisioned for a slot but it is not present in the slot.

Add a module.

Indicates that the sensor value crossed the threshold. This notification reports the most recent measurement seen by the sensor and this notification indicates the value of the threshold.

The sensor value in a module crossed the threshold listed in entSensorThresholdTable, This notification is generated once each time the sensor value crosses the threshold.

Remove the configuration that bypasses the module shutdown due to sensor thresholds being exceeded. Shut down the module after removing the configuration. It exceeded major sensor thresholds.

The local CPU was unable to access the temperature sensor on the module. The module will attempt to recover by resetting itself.

Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.

The agent generates this trap when a physical entity asserts an alarm, such as the power entry module 0 failure.

You manually shut down the line card, then you get the line card error or the alarm Card Stopped Responding OIR occurs.

Check the entPhysicalDescr type and take the corresponding action; because there are many types of asserted alarms.

The agent generates this trap when a physical entity clears a previously asserted alarm or when the core or inlet temperature crosses a threshold, such as inlet critical temperature limit.

The agent generates this trap when:

•a physical entity clears a previously asserted alarm

•a line card is installed in a slot and the alarm Active Card Removed OIR is cleared.

Notes:

* Sensor entities are the physical entities whose entity class must be defined to type entity sensor(8) in the entPhysicalTable.

* Notifications happen only if the particular entity has an entry in entity table.

* If ceAlarmNotifiesEnable is set to 0, it disables ceAlarmAsserted and ceAlarmCleared notifications. Similarly, when ceAlarmSyslogEnable is set to 0, it disables syslog messages corresponding to alarms.

* If ceAlarmHistTableSize is set to 0, it prevents any history from being retained in the ceAlarmHistTable. In addition whenever the ceAlarmHistTableSize is reset (either increased or decreased) the existing log is deleted.

* When a new alarm condition is detected, the carrier alarm LEDs in the individual line cards are currently set by the line card software. The IOS alarm subsystem does not control the LEDs.

RAM to CPU Usage

TBD

Indicates a removable flash device was inserted into the router.

Status change occurred when a removable flash card is inserted in the router.

To determine which flash card was inserted, use the ciscoFlashDeviceIndex to check the ciscoFlashDeviceTable.

This is generated every time a conceptual row is created, modified, or deleted in any of the following tables:

•entPhysicalTable

•entLogicalTable

•entLPMappingTable

•entAliasMappingTable

•entPhysicalContainsTabl

That means a new device (flash or any card) is added or removed from the router.

And the entLastChangeTime is the sysUpTime at the time a flash card is added or deleted.

Status change occurred when a flash card was added or removed.

To determine which flash card was removed from the router, use the ciscoFlashDeviceIndex to check the ciscoFlashDeviceTable.

ciscoFlashMiscOpCompletionTrap

Indicates that a flash operation has occurred.

Sent when the following flash operations occur:

•copy operation finishes

•partitioning operation finishes

•miscellaneous flash card operation finishes

Enable this trap through the CLI or setting the corresponding flash object to true(1).

•Indicates that 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 current state. Value is down(2).

•Indicates that the wideband downstream ports on the SPA are in a down state.

An internal software error might have occurred.

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.

•Indicates that a link is about to enter the Up state and the ifOperStatus object shows the link's current status.

•Indicates that the wideband downstream ports on the SPA are in a up state.

The port manager reactivated a port in the link-down state during a switchover.

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.

Objects:

•cePfeHistEntPhysIndex,

•cePfeHistType,

•cePfeHistThld,

•cePfeHistValue

Indicates that the configured threshold is crossed. The threshold value and the type are found from the cePfeHistType and cePfeHistThld. And the event type can be any of the enumerations of the HistEventType.

A threshold event has occurred and the cePfeHistNotifiesEnable is set to notify(3) or logAndNotify(4).

After generation this notification, another notification is not sent out until the sample value falls below the threshold value.

• thldUtilizationEvent

Generated if the cePfePerfCurrentUtilization, at the time of sampling, becomes greater than or equal to the cePfePerfThldUtilization

•thldEfficiencyEvent

Generated if the cePfePerfCurrentEfficiency, at the time of sampling, becomes less than or equal to the cePfePerfThldEfficiency.

•thld1MinUtilizationEvent

Generated if the cePfePerfCurrent1MinUtilization, at the time of sampling, becomes greater than or equal to the cePfePerfThld1MinUtilization.

•thld1MinEfficiencyEvent

Generated if the cePfePerfCurrent1MinEfficiency, at the time of sampling, becomes less than or equal to the cePfePerfThld1MinEfficiency.

• thld5MinUtilizationEvent

Generated if the cePfePerfCurrent5MinUtilization, at the time of sampling, becomes greater than or equal to the cePfePerfThld5MinUtilization.

• thld5MinEfficiencyEvent

Generated if the cePfePerfCurrent5MinEfficiency, at the time of sampling, becomes less than or equal to the cePfePerfThld5MinEfficiency.

Indicates a PFE restart occurred.

The PFE processor restarted

Enable this trap using the CLI snmp-server command or by setting cePfeHistNotifiesEnable to notify(3) or logAndNotify(4)

•ccCopyServerAddress

•ccCopyFileName

•ccCopyState

•ccCopyTimeStarted

•ccCopyTimeCompleted

•ccCopyFailCause

A ccCopyCompletion trap is sent when a config-copy request is completed. The ccCopyFailCause is not instantiated, and hence not included in a trap, when the ccCopyState is successful.

Sent when the CMTS router finishes copying a configuration file to or from another location.

Enable this trap by setting ccCopyNotificationOnCompletion to true(1).

The current configuration changed.

Sent when the running configuration changes.

No action required.

Indicates that a mplsTunnelOperStatus object for a configured tunnel is about to transition from the Down state to any state except NotPresent.

A configured tunnel transitioned from the Down state to any state except NotPresent.

May be caused by an administrative or operational status check of the tunnel.

No action is required.

Enable this trap through the CLI or by setting mplsTunnelTrapEnable to true(1)>

Indicates that the mplsTunnelOperStatus object for a configured MPLS traffic engineering tunnel is about to transition to the up(1) or the down(2) respectively.

A configured tunnel is transitioning to the down state.

May be caused by an administrative or operational status check of the tunnel.

Indicates that the signalling path for an MPLS traffic engineering tunnel changed.

A tunnel was rerouted or reoptimized.

If you use the actual path, then write the new path to mplsTunnelRerouted after the notification is issued.

Admin Status of Interface Up/Down

-MIB

•

•

•

Admin Status of Subinterface Up/Down

-MIB

•

•

The BGP FSM enters the ESTABLISHED state. It becomes active on the router.

The BGP routing protocol changed status.

No action is required.

Indicates that the BGP protocol transitions 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]

Indicates a loopback test.

Sent when an OAM loopback test completes.

Enable this trap through the CLI or by setting oamLoopbackPingTrapOnCompletion to true(1).

Indicates that the PPPoE system session exceeded a threshold.

Sent when the number of active PPPoE sessions exceeds the value of cPppoeSystemThresholdSessions.

Enable this trap through the CLI.

Indicates that the PPPoE VC session exceeded a threshold.

Sent when the number of active PPPoE sessions on the VC exceeds the value of cPppoeVcThresholdSessions.

Enable this trap through the CLI.

Admin Status of Interface Up/Down

-MIB

•

•

•

Admin Status of Subinterface Up/Down

-MIB

•

•

The casState object changes status.

The object casState does not necessarily indicate the current state of the server. This is because casState is always up(1) unless an AAA request fails. In that case, casState is set to dead(2) and then reset to up(1) to allow the router to send requests to the server after a failure.

The number of minutes casState remains dead(2) is specified by the radius-server deadtime minutes command. For example, if server deadtime is 5 minutes and an AAA request fails, a trap is generated with casState set to dead(2). Five minutes later, another trap is generated with casState set to up(1) even though the server may still be down.

Sent when the casState object changes state. The value of casState indicates if the router should send requests to the authentication, authorization, and accounting (AAA) server:

· up(1)—Send requests to the server.

· dead(2)—Do not send requests to the server. Send requests to the next available server instead.

Enable this trap by setting casServerStateChangeEnable to true(1).

Sent when the Service Selection Gateway (SSG) detects that a RADIUS client has rebooted. (SSG uses RADIUS servers to authenticate subscribers.)

A RADIUS client has rebooted.

Enable this trap by setting ssgCfgRadiusClientRebootNotification to true(1).

ceClearAlarm

These notifications indicate error conditions on a SONET circuit and the status of SONET layers.

Note that not all SONET and Packet over SONET (POS) line cards generate all of the traps.

Sent when one of the following alarm status has changed. See footnote below.

Check out the AlarmType and ceAlarmHistSeverity values.

Paths, for example a Path Alarm Indication Signal

Line, for example a Line Remove Failure Indication

Section, for example a Section Loss of Frame Failure

Clock problems, for example a Far End Clock Out of Range

Signal, for example a Out of Frame Failure

Near End/Far End, for example a Far End Alarm Indication Signal

Thresholds, for example a Threshold Cross Alarm-B1

The status of a module changes from the OK state to another state.

The agent entity has detected that the moduleStatus object in this MIB has transitioned out of the ok (2) state for one of its modules. The generation of this trap can be controlled by the sysEnableModuleTraps object in this MIB.

Replace module.

The status of a module changes to the OK state.

The agent entity has detected that the moduleStatus object in this MIB has transitioned to the ok (2) state for one of its modules. The generation of this trap can be controlled by the sysEnableModuleTraps object in this MIB.

No action required.

Sent when the value of rttMonCtrlOperConnectionLostOccurred changes.

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 not to a hop in the path to the target.

Check for the connectivity to the target. There could be link problems to the target through different hops.

A timeout occurred or was cleared during an RTT probe.

An RTT probe occurred and the system sends the notice when the value of rttMonCtrlOperTimeoutOccurred changes.

Check for the end-to-end connectivity if rttMonCtrlOperTimeoutOccurred if the notification returns true.

No action is required if rttMonCtrlOperTimeoutOccurred is false.

Threshold violation occurred during an RTT probe.

Indicates that the previous violation has subsided for a subsequent RTT operation. which results in rttMonCtrlOperOverThresholdOccurred changing value.

Check for the end-to-end connectivity if rttMonCtrlOperOverThresholdOccurred in the notification is true otherwise no action required.

A ciscoEnvMonShutdown
Notification is sent if the environmental monitor detects a testpoint reaching a critical state and is about to initiate a shutdown.

This notification contains no objects so that it may be encoded and sent in the shortest amount of time possible. Management applications should not rely on receiving such a notification as it may not be sent before the shutdown completes.

A test point 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).

The system has a configuration to shut down a module if its operating temperature exceeds a temperature threshold. This configuration has been bypassed, and a module will still operate in an over-temperature condition. Operating at an over-temperature condition can damage the hardware.

Do not override the system critical alarms like facility-alarm-intake-temperature.

Enable this trap through the following CLI command snmp-server-enable traps envmon shutdown or by setting the ciscoEnvMonEnableShutdownNotification to true(1).

Fan status. A ciscoEnvMonFanNotification is sent if the system detects a fan failure or an empty tray.

One or more fans in the system fan tray have failed, or the fan tray is missing. Although this is a minor alarm, system components could overheat and be shut down.

Replace the system fan tray.

Enable this trap using the CLI snmp-server-enable traps envmon fan command or by setting ciscoEnvMonEnableFanNotification to true (1).

Power supply status. Sent if the redundant power supply (if available) fails.

An environmental condition, an over-temperature condition, or inconsistent voltage to the module occurred. Since such a notification is usually generated before the shutdown state is reached, it can convey more data and has a better chance of being sent than does the ciscoEnvMonShutdownNotification.

Ensure that the system power supplies are optimally redundant.

Use power supplies with identical output ratings or reduce system power consumption.

Enable this trap using the CLI snmp-server enable traps envmon supply command or by setting ciscoEnvMonEnableRedundantSupplyNotification to true (1).

ciscoEnvMonTempStatusChangeNotif

Temperature status. The core or inlet temperature is outside its normal range, when ciscoEnvMonState is at the Warning or Critical state.

Since such a Notification is usually generated before the shutdown state is reached, it can convey more data and has a better chance of being sent than does the ciscoEnvMonShutdownNotification.

During previous reloads, this module experienced a timeout while accessing the temperature sensor. All further access to the temperature sensor will be disabled. This condition indicates a possible problem with the temperature sensor.

Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.

Enable this trap using the CLI snmp-server enable traps envmon temperature command or by setting ciscoEnvMonEnableTemperatureNotification to true (1).

* The cefcFRUPowerAdminStatus is on(1) when a redundant power supply is disabled. When there is a redundant power supply, the cefcFRUPowerAdminStatus is always on(1) for both power supplies, regardless if the redundant power supply is disabled.

Indicates that the RF state changed.

A switch of activity notification is sent by the newly active redundant unit.

A switch of activity occurs. If a SWACT event is indistinguishable from a reset event, then a network management station should use this notification to differentiate the activity.

If the switchover occurred due to active unit failed indicated by cRFStatusLastSwactReasonCode, see if there is any hardware failures, otherwise no action is required.

Indicates that the RF state changed.

The active redundant unit RF state changed or the RF state of the peer unit changed.

To avoid an increase of notifications for all state transitions, send notifications for transitions to the following RF states:

•standbyCold(5)

•standbyHot(9)

•active(14)

•activeExtraload(15)

•docsDevCmtsInitRegReqFailTrap

Indicates that a registration request failed. The failure was detected on the CMTS side.

A registration request failed during the CM initialization process.

Correct the registration request failure.

•docsDevCmtsInitRegRspFailTrap

Indicates a registration response failed. The failure was detected on the CMTS side.

A registration response failed during the CM initialization process.

Correct the registration response failures.

•docsDevCmtsInitRegAckFailTrap

Indicates a registration acknowledgement failed. The failure was detected on the CMTS side.

A registration acknowledgement failed during the CM initialization process.

Correct the registration acknowledgement failures.

•docsDevCmtsDynServReqFailTrap

Indicates a dynamic service request failed. The failure was detected on the CMTS side.

A dynamic service request failed during the dynamic services process.

Correct the dynamic service request failures.

•docsDevCmtsDynServRspFailTrap

Indicates a dynamic service response failed. The failure was detected on the CMTS side.

A dynamic service response failed during the dynamic services process.

Correct the dynamic service response failures.

•docsDevCmtsDynServAckFailTrap

Indicates a dynamic service acknowledgement failed. The failure was detected on the CMTS side.

A dynamic service acknowledgement failed during the dynamic services process.

Correct the dynamic service acknowledgement failures.

•docsDevCmtsBpiInitTrap

Indicates a BPI initialization attempt failed. The failure was detected on the CMTS side.

A BPI initialization attempt failed during the CM registration process.

Correct the BPI initialization attempt failures.

•docsDevCmtsBPKMTrap

Indicates a BPKM operation failed. The failure was detected on the CMTS side.

A BPKM operation failed.

Correct the BPKM operation failures.

•docsDevCmtsDynamicSATrapTrap

Indicates a dynamic security association operation failed. The failure was detected on the CMTS side.

A dynamic security association operation failed.

Correct the dynamic security association operation failures.

•docsDevCmtsDCCReqFailTrap

A dynamic channel change request failed. The failure was detected on the CMTS side.

A dynamic channel change request failed during the dynamic channel change process

Correct the dynamic channel change request failures.

•docsDevCmtsDCCRspFailTrap

Indicates a dynamic channel change response failed. The failure was detected on the CMTS side.

A dynamic channel change response failed during the dynamic channel change process.

Correct the dynamic channel change response failures.

•docsDevCmtsDCCAckFailTrap

A dynamic channel change acknowledgement failed. The failure was detected on the CMTS side.

A dynamic channel change acknowledgement failed during the dynamic channel change process.

Correct the dynamic channel change acknowledgement failures.

1 The following traps can be enabled using the CLI snmp-server enable trap docsis-cmts command.

bpi—Enable BPI init fail trap

bpkm—Enable BPKM fail trap

dccack—Enable dynamic channel change acknowledgement fail trap

dccreq—Enable dynamic channel change request fail trap

dccrsp—Enable dynamic channel change response fail trap

dsack—Enable dynamic service acknowledgement fail trap

dsreq—Enable dynamic service request fail trap

dsrsp—Enable dynamic service response fail trap

dynsa—Enable Dynamic SA fail trap

regack—Enable registration acknowledgement fail trap

regreq—Enable registration request fail trap

regrsp—Enable registration response fail trap

2 The following traps can be enabled by setting the bit value in docsDevCmtsTrapControl:

  cmtsInitRegReqFailTrap( 0)

cmtsInitRegRspFailTrap( 1)

cmtsInitRegAckFailTrap( 2)

cmtsDynServReqFailTrap( 3)

cmtsDynServRspFailTrap( 4)

cmtsDynServAckFailTrap( 5)

cmtsBpiInitTrap( 6)

cmtsBPKMTrap( 7)

cmtsDynamicSATrap( 8)

cmtsDCCReqFailTrap( 9)

cmtsDCCRspFailTrap( 10)

cmtsDCCAckFailTrap( 11)

•cdrqCmtsCmRQDoneNotification

Indicates the CMTS CM poller finished polling for the current cycle.

•cdrqCmtsCmPollerStartTime

Indicates the time when the polling cycle started.

CMTS CM poller started polling.

No action required

•cdrqCmtsCmPollerStopTime

Indicates the time when the polling cycle finished.

CMTS CM poller finished polling.

No action required

Indicates if the metering record file was created successfully or not and if streaming the file to the collection server was successful or not.

The receipt of this notification is an indication to the collection server that the file can be accessed through ftp or any file transfer protocol in the case of local storage.

Enable this trap by setting ccmtrMeteringNotifEnable to true(1)

•ccmtrCollectionStatus,

Indicates the success or failure of the export.

•ccmtrCollectionDestination,

Indicates the destination of the export in both the success and failure scenarios.

•ccmtrCollectionTimestamp

Indicates the timestamp of the export in both the success and failure scenarios.

Indicates a failure relating to DMIC.

Sent whenever a modem is locked because it failed the Dynamic Message Integrity Check (DMIC).

Describes a change in status for cable hopping, modulation profile, or channel width.

Cable upstream runtime frequency (hopping), profile, or channel width status changed. See footnote below.

Use the cable upstream threshold command to change these values The CNR threshold for the secondary modulation profile defaults to 15 dB. The correctable FEC error threshold defaults to 1 percent of total packets received, and the invalid FEC error threshold defaults to 1 percent of total packets received.

1. In the case of frequency hopping, ccsUpSpecMgmtHopCondition would indicate whether SNR or modemOffline that caused the hopping.

2. Frequency hopping is based on the carrier-to-noise ratio (CNR) and the correctable FEC error and uncorrectable FEC error values. A channel will frequency hop if the CNR falls below the configurable threshold AND either the correctable or uncorrectable FEC error values exceed the configurable threshold values.

3. Channel width may be too small.