Table Of Contents
DSP Operational State Notifications
Contents
Prerequisites for DSP Operational State Notifications
Information About DSP Operational State Notifications
CISCO-DSP-MGMT-MIB
DSP Operational State Notification
Benefits of DSP Operational State Notifications
How to Enable DSP Operational State Notifications
Enabling DSP Operational State Notifications from the CLI
Enabling DSP Operational State Notifications Using an SNMP Application
Configuration Examples for DSP Operational State Notifications
Enabling DSP Operational State Notifications Using the CLI: Example
Enabling DSP Operational State Notifications Using an SNMP Application: Example
Additional References
Related Documents
MIBs
Technical Assistance
Command Reference
DSP Operational State Notifications
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.
History for the DSP Operational State Notifications Feature
Release
|
Modification
|
12.4(4)T
|
This feature was introduced.
|
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.
Contents
•
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
•
Additional References
•
Command Reference
Prerequisites for DSP Operational State Notifications
•
Familiarity with the CISCO-DSP-MGMT-MIB and Simple Network Management Protocol (SNMP).
Information About DSP Operational State Notifications
To enable DSP operational state notifications when a DSP fails and when it recovers, you should understand the following concepts:
•
CISCO-DSP-MGMT-MIB
•
DSP Operational State Notification
•
Benefits of DSP Operational State Notifications
CISCO-DSP-MGMT-MIB
The CISCO-DSP-MGMT-MIB monitors DSP resources and status.
DSP Operational State Notification
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.
Benefits of DSP Operational State Notifications
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..
How to Enable DSP Operational State Notifications
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
Enabling DSP Operational State Notifications from the CLI
Perform this task to enable DSP operational state notifications from the CLI.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
snmp-server enable traps [notification type][vrrp]
4.
end
5.
exit
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
snmp-server enable traps
[notification-type][vrrp]
Example:
Router(config)# snmp-server enable traps dsp
oper-state
|
Enables the generation of DSP notifications made up of the DSP ID that indicates which DSP is affected and the operational state that indicates whether the DSP has failed or recovered.
|
Step 4
|
end
Example:
Router(config)# end
|
Returns the device to privileged EXEC mode.
|
Step 5
|
exit
Example:
Router# exit
|
Returns the device to user EXEC mode.
|
Enabling DSP Operational State Notifications Using an SNMP Application
Perform this task to enable DSP operational state notifications using your SNMP application.
SUMMARY STEPS
1.
setany -v2c 1.4.198.75 test cdspEnableOperStateNotification.0 -i 1
DETAILED STEPS
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).
Configuration Examples for DSP Operational State Notifications
•
Enabling DSP Operational State Notifications Using the CLI: Example
•
Enabling DSP Operational State Notifications Using an SNMP Application: Example
Enabling DSP Operational State Notifications Using the CLI: Example
The following sample configuration code shows how to enable DSP operational state notifications using the CLI:
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
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
entPhysicalEntry.7.37 = DSP (C549) 1/2/0
Enabling DSP Operational State Notifications Using an SNMP Application: Example
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)
Additional References
The following sections provide references related to the DSP Operational State Notifications feature.
Related Documents
MIBs
MIB
|
MIBs Link
|
• CISCO-DSP-MGMT-MIB
• CISCO-DSP-MGMT-CAPABILITY-MIB
|
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://www.cisco.com/go/mibs
|
Technical Assistance
Description
|
Link
|
The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.
|
http://www.cisco.com/techsupport
|
Command Reference
The following commands are introduced or modified in the feature or features documented in this module. For information about these commands, see the Cisco IOS Network Management Command Reference at http://www.cisco.com/en/US/docs/ios/netmgmt/command/reference/nm_book.html. For information about all Cisco IOS commands, go to the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or to the Cisco IOS Master Commands List.
•
snmp-server enable traps
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website 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. (0809R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.