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.
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
To enable DSP operational state notifications when a DSP fails and when it recovers, you should understand the following concepts:
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-statecommand, 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:
Perform this task to enable DSP operational state notifications from the CLI.
Perform this task to enable DSP operational state notifications using your SNMP application.
This SNMP command sets the enable operation state notification object identifier (OID) to true. After entering this command, the system returns the followinbg response: cdspEnableOperStateNotification.0 = true(1). |
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.
Related Topic |
Document Title |
---|---|
Network management commands |
Cisco IOS Network Management Command Reference |
MIB |
MIBs Link |
---|---|
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: |
Description |
Link |
---|---|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
Table 1 | Feature Information for DSP Operational State Notifications |
Feature Name |
Releases |
Feature Information |
---|---|---|
DSP Operational State Notifications |
12.4(4)T |
The following command was modified: snmp-server enable traps |
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.