Troubleshooting guide

6-26
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
Step 3 Verify that the dial plan file was loaded correctly, by using the procedure that is described in the
“Verifying Proper Loading of a Dial Plan” section on page 6-121.
ANAL: Prof_InvldNPAValue
This alarm occurs during profile analysis when the system encounters a 7-digit B-number and the NPA
property is set against the originating trunk group. An NPA string of more or less than three characters
is invalid. Data corruption is the most likely cause of this problem.
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 Verify that the NPA values have been properly provisioned for the trunk group by using the numan-rtrv
MML command. See Cisco PGW 2200 Softswitch Release 9.8 Dial Plan Guide for more information.
If the NPA values are incorrect, modify them using the numan-ed MML command. See Cisco PGW
2200 Softswitch Release 9.8 Dial Plan Guide for more information. Save and activate your dial plan
changes as described in the “Saving and Activating your Provisioning Changes” section on page 3-65.
Otherwise, proceed to Step 3.
Step 3 Verify that the dial plan file was loaded correctly, using the procedure that is described in the “Verifying
Proper Loading of a Dial Plan” section on page 6-121.
ANAL: Prof_InvRslts_NOATbl
This alarm occurs when profile analysis successfully reads the NOA table but the value that is returned
is logically invalid. Profile analysis gets two values from the NOA table: an immediate result index and
an NPI index. An immediate result index indicates that analysis should start reading results now, but an
NPI index indicates that another table read is required to find the correct result table index. These results
are logically incompatible. Most likely this results from a failure of the underlying software or a
corruption of the NOA table.
Corrective Action
To correct the problem, verify that the dial plan file was loaded correctly, using the procedure that is
described in the “Verifying Proper Loading of a Dial Plan” section on page 6-121.
ANAL: Prof_InvRslts_NOATbl_A
This alarm occurs when profile analysis successfully reads the NOA table but the value that is returned
is logically invalid. Profile analysis gets two values from the NOA table, an immediate result index and
an NPI index. The immediate result index indicates that analysis should start reading results now but the
NPI index indicates that another table read is required to find the correct result table index. These results
are logically incompatible. Most likely, the system raises this alarm when it detects a failure of the
underlying software or a corruption of the NOA table.