Appendix J Troubleshooting
J.10.12 Service Agent Problems
J.10.12.1.1 Registration with RtmProxy Failed
Manager's SNMP request to register with RtmProxy returned an error.
Step 1 Verify that the CTM core is up and running by executing ps
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
•RtmProxy.log* and snmpd.log* Possible alternative
J.10.12.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, see J.10.12.1.1 Registration with RtmProxy Failed, page
Step 2 Use the following to verify that 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.
tballraker29% /opt/OV/bin/snmpget
where 172.28.131.137 is the CTM 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 Use the following to verify that the Manager is still registered with RtmProxy.
tballraker29% /opt/OV/bin/snmpget
where 172.28.131.137 is the CTM 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
•RtmProxy.log* and snmpd.log*
Possible alternative
| Cisco Transport Manager Release 6.0 User Guide |
|