Troubleshooting guide

B-5
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Appendix B Troubleshooting Cisco ITP-L Signaling
Troubleshooting SS7 Link Problems
Link Status
Congestion status is maintained for backhaul.
Example of a congestion status message:
Nomad-C#sho ss7 mtp2 state
SS7 MTP2 states for channel 0
Protocol version for channel 0 is Bellcore GR-246-Core Issue 2, Dec 1997
MTP2LSC_INSERVICE MTP2IAC_IDLE
MTP2TXC_INSERVICE MTP2RC_INSERVICE
MTP2SUERM_MONITORING MTP2AERM_IDLE
MTP2CONGESTION_IDLE
Congestion Backhaul = Abate
Remote Processor Outage = FALSE
Troubleshooting SS7 Link Problems
The following sections describe methods of troubleshooting SS7 link problems:
• Checking Link Configuration Files, page B-5
• Checking UDP Traffic Flows, page B-6
• Checking Connection between Cisco PGW 2200 Softswitch and Cisco ITP-L, page B-6
• Checking the T1/E1 Link State, page B-6
• Verifying the Link Alignment Status, page B-6
• Verifying Exchanged Point Codes, page B-7
• Cross-Checking Configuration Files, page B-9
Checking Link Configuration Files
Check the configuration files on the Cisco PGW 2200 Softswitch and the Cisco ITP-L. The IP addresses
and UPD ports must match.
• MTP2 Configuration:
– Is the channel configured to the proper MTP2 variant?
– Do the MTP2 variant protocol parameters match the remote configuration?
• Session Manager Configuration:
– Are the proper number of sessions defined, session-0 and session-1?
– Do the session configurations match the Cisco PGW 2200 Softswitch session configurations?
– Do the RUDP parameters match the Cisco PGW 2200 Softswitch RUDP configuration?