Troubleshooting guide

6-56
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
MMDB: Database unavailable
This alarm occurs when the main memory database is unavailable to provide any services. The
Cisco PGW 2200 Softswitch attempts to recover. The alarm clears when the database becomes available.
Corrective Action
To correct the problem, delete any unnecessary files from the
Cisco PGW 2200 Softswitch, as described in the “Deleting Unnecessary Files to Increase Available Disk
Space” section on page 6-169.
MMDB: Database cause switchover
This alarm occurs when the main memory database is unavailable on a redundant system and is
indicating that the system should switchover. The Cisco PGW 2200 Softswitch attempts to recover. The
alarm clears when the database becomes available.
Corrective Action
To correct the problem, delete any unnecessary files from the standby
Cisco PGW 2200 Softswitch, as described in the “Deleting Unnecessary Files to Increase Available Disk
Space” section on page 6-169.
MMDB: Database nearly full
This alarm occurs when the main memory database detects that allocated resources for data storage are
nearly all utilized.
Corrective Action
To correct the problem, delete any unnecessary files from the
Cisco PGW 2200 Softswitch, as described in the “Deleting Unnecessary Files to Increase Available Disk
Space” section on page 6-169.
NAS: AuditResponse Failure
This alarm occurs when the identified media gateway fails to send a RESYNC RESP message back to
the Cisco PGW 2200 Softswitch within the audit time interval.
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 affected media gateway is in the in-service state, as described in the “Verifying the Status
of all Signaling Services” section on page 3-9.
If the affected media gateway is in-service, proceed to Step 3. Otherwise, proceed to Step 4.
Step 3 Verify that the configuration of the affected media gateway is correct. See the documentation for the
media gateway for more information.