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.
The DSP Operational State Notifications feature enables notifications to be generated when digital signaling processor (DSP) failure and recovery events occur. These notifications help facilitate troubleshooting and lessen downtime.
This feature module describes updates to the Cisco DSP Management MIB (CISCO-DSP-MGMT-MIB) for enabling and generating DSP operational state notifications. Also described is how to enable the feature either using the command-line interface (CLI) or by modifying settings at the network management device.
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
•Prerequisites for DSP Operational State Notifications
•Information About DSP Operational State Notifications
•How to Enable DSP Operational State Notifications
•Configuration Examples for DSP Operational State Notifications
•Feature Information for DSP Operational State Notifications
•Familiarity with the CISCO-DSP-MGMT-MIB and Simple Network Management Protocol (SNMP).
To enable DSP operational state notifications when a DSP fails and when it recovers, you should understand the following concepts:
•DSP Operational State Notification
•Benefits of DSP Operational State Notifications
The CISCO-DSP-MGMT-MIB monitors DSP resources and status.
A DSP notification consists of a DSP ID that indicates which DSP is affected and an operational state that indicates whether the DSP has failed or recovered.
When this feature is configured using the snmp-server enable traps dsp oper-state command, a notification is generated when a single DSP fails instead of after all DSPs have failed. For example, a DSP fails, and you lose your voice calls. In a DSP failure notification, the problem is identified. If no DSP failure notification is generated, a network management station (NMS) has to poll the router for configuration and status information to diagnose the problem.
The DSP Operational State Notifications feature enables the generation of notifications when DSP failure and recovery events occur. These notifications help facilitate troubleshooting and lessen downtime because an NMS does not have to poll the router for configuration and status information to diagnose the problem..
DSP operational state notifications can be configured in two ways. To configure these notifications, perform one of the following tasks:
•Enabling DSP Operational State Notifications from the CLI
•Enabling DSP Operational State Notifications Using an SNMP Application
Perform this task to enable DSP operational state notifications from the CLI.
1. enable
2. configure terminal
3. snmp-server enable traps [notification type][vrrp]
4. end
5. exit
Perform this task to enable DSP operational state notifications using your SNMP application.
1. setany -v2c 1.4.198.75 test cdspEnableOperStateNotification.0 -i 1
Step 1 setany -v2c 1.4.198.75 test cdspEnableOperStateNotification.0 -i 1
This SNMP command sets the enable operation state notification object identifier (OID) to true.
After entering this command, the system returns the following response: cdspEnableOperStateNotification.0 = true(1).
•Enabling DSP Operational State Notifications Using the CLI: Example
•Enabling DSP Operational State Notifications Using an SNMP Application: Example
The following sample configuration code shows how to enable DSP operational state notifications using the CLI:
Router> enable
Router# configure terminal
Router(config)# snmp-server enable traps dsp oper-state
The following example shows a typical DSP failure notification:
*Jun 1 02:37:05.720:SNMP:V1 Trap, ent cdspMIBNotificationPrefix, addr 1.4.198.75, gentrap 6, spectrap 2
cdspOperState.37 = 2
entPhysicalEntry.7.37 = DSP (C549) 1/2/0
The following example shows a typical DSP recover notification:
*Jun 1 02:37:10.820:SNMP:V1 Trap, ent cdspMIBNotificationPrefix, addr 1.4.198.75, gentrap 6, spectrap 2
cdspOperState.37 = 1
entPhysicalEntry.7.37 = DSP (C549) 1/2/0
The following sample configuration code shows how to enable DSP operational state notifications from your SNMP application:
In your SNMP application, you type the following command:
setany -v2c 1.4.198.75 test cdspEnableOperStateNotification.0 -i 1
The application shows the following response:
cdspEnableOperStateNotification.0 = true(1)
The following sections provide references related to the DSP Operational State Notifications feature.
|
|
---|---|
Network management commands |