Troubleshooting guide

6-39
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
EISUP: Unexpected Msg/Par
This alarm occurs when the EISUP module receives an unsupported message or parameter. This alarm
is most likely to occur when the local EISUP version is older than the EISUP version used by the Cisco
PGW 2200 Softswitch or the Cisco H.323 Signaling Interface (HSI) on the other end.
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 To upgrade the version of EISUP locally, you must either upgrade the Cisco PGW 2200 Softswitch
software to the same release as the other Cisco PGW 2200 Softswitch, or to the release supported by
your current version of the Cisco HSI software.
The steps that are required to upgrade the Cisco PGW 2200 Softswitch software are in
Cisco PGW 2200 Softswitch Release 9 Software Installation and Configuration Guide.
If upgrading the Cisco PGW 2200 Softswitch software clears the alarm, the procedure is complete.
Otherwise, proceed to Step 3.
Step 3 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.
ENGINE CONFIG FAIL
This alarm occurs when a component in the engine configuration fails.
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 Search the active system log file for log messages indicating which component is raising this alarm. Use
the procedure that is described in the “Viewing System Logs” section on page 6-90.
If there are logs that indicate a failed component, proceed to Step 3.
If there are no logs that indicate a failed component, proceed to Step 4.
Step 3 Begin a dynamic reconfiguration session to reprovision the failed component. Use the procedure that is
described in the “Invoking Dynamic Reconfiguration” section on page 3-66.
If that resolves the problem, the procedure is complete. Otherwise, proceed to Step 4.
Step 4 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.