This article describes how to successfully configure Simple Network Management Protocol (SNMP) in order to retrieve SNMP traps from Cisco Customer Voice Portal (CVP) server.
Cisco recommends that you have knowledge of:
Cisco voice portal
Operations Console (OAMP)
Management Information Base (MIB) browser
The information in this document is based on:
CVP Operations Console (OAMP) 10.0
CVP call server 10.0
MIB browser (no specific version)
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Step 1. Delete the current SNMP string from OAMP and delete the notification destinations (If already added anything previously)
Step 2. Freshly add the SNMP v2 String.
Step 3. Add the call servers.
Step 4. Add the call server IP in Accept SNMP packet from these Hosts and add it to Devices tab as well. As shown in the images.
Step 5. Add the notification destination
Notification Destination Name and Host IP Address must be from the host where MIB browser is installed. Add it to the Devices tab as well. Keep Port Number to 162 default. As shown in the iamge.
Step 6. Navigate to the Call Server that you have added and restart the Call Server, SNMP and Voice Extensible Markup Language (VXML) services from services.msc.
Caution: This step has to be done in maintenance window only.
More details on how to add notification destination can be found in this image:
Step 7. Once you finish this, navigate to MIB browser > Advanced.
Add the Call Server IP in the Address bar, and select Advanced, after that a pop windows like the one shown in the image appears. Keep Port number to 161 only because Call Server uses this port to send the SNMP traps.
Edit Read Community with your name given on OAMP and SNMP Version as 2, as shown in the image.
Step 8. Navigate to the CVP box from which you try to receive SNMP traps. Navigate to the path C:\Cisco\CVP\conf and copy the file CISCO-CVP-MIB.my to the host where you run the MIB browser. Click Load MIBs to load the MIB file copied as shown in the image.
Step 9. Once you load the copied MIB file you are all set to receive the SNMP traps. Click Get or Get Next on any object and see the output on the right side as shown in the image.
Step 1. Click Get or Get Next on ccvpVersion to get an output, as shown in the image.
Step 2. For test purposes, restart the Call Server and see the traps in the Trap Receiver tab.
Caution: This step has to be done in lab for only for test purposes.
Traps shows up with description ccvpCvpEvent
Step 1. Ensure the port 161 on call server is open. To do so you can use netstat command, as shown in the image.
Step 2. From OAMP navigate to C:\Cisco\CVP\conf\SNMPD.CNF and check that all changes that you did from OAMP were pushed to SNMPD.CNF file through Java Management Extensions (JMX) (You can manually edit this file with required configuration if the values were not pushed from OAMP).
Step 3. Once you verify all the configuration changes are reflected in SNMPD.CNF file, restart CVP SNMP service to recover if any issues happened with memory, etc.
Logs rekated to SNMP on CVP server can be found in C:\Cisco\CVP\logs\SNMP.
If any memory issues arises, SNMPDM shows errors with Process ID (PID) in the snmpdm logs.
Step 4. If for some reason cvpsnmpmgmt crashes or runs out of memory try to remove and install it back. as shown in the image
Caution: In production environments, perform this step on a maintainance window.