User guide

C-110
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Service Agent Problems
C.13 Service Agent Problems
RtmProxy is the only component in Service agent that is used in Cisco MGM. Service Agent processes
user request through SNMP and convey to switch agent and finally return the result to user.
This section includes the following information:
• C.13.1 RtmProxy
C.13.1 RtmProxy
RtmProxy is Cisco MGM's northbound SNMP interface to provide traps from all switches to the
customer applications. It is an interface with which the customer application registers for traps.The
customer application use snmp to register with RtmProxy. Figure C-7 gives the flow of information.
Figure C-7 RTMProxy
The OSS/Manager send snmp request to port 8161 of the Cisco MGM machine. In this request they
specify the port on which they are listening for traps. In the above example, the manager will be sent
traps on port 162. The registration, de-registration and other such scripts can be found at
/opt/svplus/scripts/proxyscripts/rtmproxy on a Cisco MGM machine. These scripts can be used as
reference for registration and de-registration with RtmProxy. These scripts are meant only for internal
use.
This section includes the following information:
• C.13.1.1 Registration with RtmProxy Failed
• C.13.1.2 Not Receiving Any Traps
• C.13.1.3 Manager Gets Deregistered
• C.13.1.4 Nodal Community Strings Do Not Work
C.13.1.1 Registration with RtmProxy Failed
Manager's snmp request to register with RtmProxy returned an error.
Step 1 Verify that the Cisco MGM core is up and running. This can be verified by doing ps -ef | grep RtmProxy
on the Cisco MGM machine.
Step 2 Verify that the snmpset request was sent to port 8161.
Eventd
RtmProxy
OSS/
Manager
Master
Agent
NTS
Databroker
Port 8161
Port 162
Port 9863
120753