User guide

C-111
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Service Agent Problems
Step 3 Verify that the community string for the snmpset is set to private
Step 4 Verify that the mib objects that are being set are correct.
The mib objects that should be set for the manager's registration are
stratacom.rtm.trapsConfig.trapConfigTable.trapConfigEntry.managerRowStatus
mstratacom.rtm.trapsConfig.trapConfigTable.trapConfigEntry.trapFilterRegisterCategory
stratacom.rtm.trapsConfig.trapConfigTable.trapConfigEntry.managerPortNumber
Step 5 Verify that the ip address to which you are sending the snmpset request is correct
Defect Information—Collect the following information for further analysis:
• Collect RtmProxy.log* and snmpd.log*
Possible alternative workaround—None
C.13.1.2 Not Receiving Any Traps
Traps are not being received on the port with which the manager registered.
Step 1 Verify that the registration with RtmProxy went through successfully. If the registration did not go
through, seeC.13.1.1 Registration with RtmProxy Failed.
Step 2 Verify the port number that RtmProxy is sending traps to is the same as the port number on which the
trap receive utility or manager is listening. This can be done by
tballraker29% /opt/OV/bin/snmpget -d -v1 -p8161 -t 3000 -r 0 -cpublic 172.28.131.137
stratacom.rtm.trapsConfig.trapConfigTable.trapConfigEntry.managerPortNumber.172.28.131.158
where 172.28.131.137 is the Cisco MGM IP Address and
172.28.131.158 is the Manager IP Address ( or IP Address of the station where the trap receive utility is
running)
Step 3 Verify that the manager is still registered with RtmProxy. This can be done by doing
tballraker29% /opt/OV/bin/snmpget -d -v1 -p8161 -t 3000 -r 0 -cpublic 172.28.131.137
stratacom.rtm.trapsConfig.trapConfigTable.trapConfigEntry.managerRowStatus.172.28.131.158
where 172.28.131.137 is the Cisco MGM IP Address and
172.28.131.158 is the Manager IP Address (or IP Address of the station where the trap receive utility is
running)
The snmp should return 1.
Defect Information—Collect the following information for further analysis:
• Collect the RtmProxy.log* and snmpd.log*
Possible alternative workaround—Re-register with RtmProxy.