Troubleshooting guide

6-88
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform
Troubleshooting Using Cisco PGW 2200 Softswitch Alarms
Wrong IP Path
This alarm occurs when an IP route or local interface that is associated with the identified component
cannot be used. The system can raise this alarm when one of the following occurs:
• Another route in the operating system routing table overrides the affected route.
• Someone deletes a route that is configured on your system by issuing the route delete UNIX
command.
• An IP link or route has been provisioned incorrectly.
• This alarm can also occur if an IP signaling channel is misconfigured. Enter the netstat -rnv UNIX
command to retrieve the current operating system routing table.
Corrective Action
To correct the problem, perform the following steps:
Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC”
section on page 6-93.
Step 2 Log in to the active Cisco PGW 2200 Softswitch and retrieve the current operating system routing table
by issuing the netstat -rnv UNIX command:
The system returns a response like the following:
IRE Table: IPv4
Destination Mask Gateway Device Flags
----------------- ---------------- -------------- ------ -----
10.82.80.0 255.255.255.0 10.82.82.1 UGH
10.82.81.0 255.255.255.0 10.82.83.1 UGH
10.82.82.0 255.255.255.0 10.82.82.112 hme0 U
10.82.83.0 255.255.255.0 10.82.83.112 hme1 U
default 0.0.0.0 10.82.82.1 UG
224.0.0.0 240.0.0.0 10.82.82.112 hme0 U
127.0.0.1 255.255.255.255 127.0.0.1 lo0 UH
Step 3 If the response does not contain the route that is identified in the alarm, open the operating system
routing table file by using a text editor such as vi. Otherwise, proceed to Step 6.
Step 4 Add the route to the routing table by using the appropriate text editor command.
Step 5 Save the file and exit the editing session. If adding the route to the routing table resolves the problem,
the procedure is complete. Otherwise, proceed to Step 6.
Step 6 Verify that the provisioned settings for the identified IP link are correct. Enter the prov-rtrv MML
command, as described in the “Retrieving Provisioning Data” section on page 3-69.
If the provisioned settings for the IP link are correct, proceed to Step 8.
If the provisioned settings for the IP link are incorrect, proceed to Step 7.
Step 7 Start a dynamic reconfiguration session to change the settings, as described in the “Invoking Dynamic
Reconfiguration” section on page 3-66. If changing the IP link settings resolves the problem, the
procedure is complete. Otherwise, proceed to Step 8.
Step 8 Contact the Cisco TAC to analyze the problem further and to determine a solution. For more information
about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request”
section on page xviii.