Troubleshooting guide

6-137
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform
Resolving Bearer Channel Connection Problems
For example, to change the settings for the COT to per call and seizing (glare) to no circuit control for
the trnkgrpdms trunk group, enter the
prov-ed:ztrnkgrp:name="trnkgrpdms",ExtCOT="Loop", CotPercentage=”100”,GLARE="0" command:
Step 12 Activate your new configuration as described in the “Saving and Activating your Provisioning Changes”
section on page 3-65.
Step 13 Return to Step 1 and enter the vld-cic command again.
If the response indicates that the test passed, proceed to Step 14.
If the response indicates that the test failed, resume performing this procedure from Step 2 and modify
the mismatched settings that were identified in the latest command response.
Step 14 Repeat Step 1 through Step 13 for each additional CIC that you want to test.
Resolving ISDN D-Channel Discrepancies
When there is a mismatch between the D-channels that are configured on the Cisco PGW 2200
Softswitch and the D-channels that are configured on the associated media gateway, the system
generates an ISDN log message. To resolve the log message, complete the following steps:
Step 1 Enter the cd $BASEDIR/etc command at the active Cisco PGW 2200 Softswitch to change directories.
Step 2 Determine the component IDs associated with the D-channel number identified in the log text by
searching for the D-channel number in the data files.
For example, if the log message contains the following text:
PROT_ERR_ISDN:Error message from ISDN:Receive MGMT_ERROR_IND for set 1, channel 2854
The D-channel number in the example is 2854. Therefore, search for occurrences of D-channel 2854 in
the data files.
Enter the
grep d_num *.dat command to search the data files for the identified D-channel number:
Where d_num is the D-channel number that is identified in the alarm message.
The system returns a message like the following:
sigChanDev.dat:001002bd 00160002 1 0034015e 00030011 00060001 2854
sigChanDev.dat:001002be 00160002 1 0034015e 00030011 00060002 2854
The response lists the data files in which the D-channel number was found, along with the associated
properties. In the preceding example, the D-channel number, 2854, was found twice in the
sigChanDev.dat file. The component IDs are in the column immediately following the data filename.
So, in this example, the component IDs are 001002bd and 001002be.
Step 3 Determine the MML name of an IP link that is associated with one of the component IDs you identified
in Step 2 by using the
grep comp_ID components.dat command.
Where:
comp_ID—Component ID identified in Step 2.
The system returns a message like the following:
001002bd 0034015e "bh531-31" "IP link-backhaul svc mgx8260 EAST"