Troubleshooting guide

6-169

Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide

OL-0800-14

Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform

Platform Troubleshooting

The following sections contain procedures that pertain to resolving problems with the Cisco PGW 2200

Softswitch platform:

• Verifying Cisco PGW 2200 Softswitch Ethernet Operation, page 6-169

• Deleting Unnecessary Files to Increase Available Disk Space, page 6-169

• Recovering from a Switchover Failure, page 6-170

• Recovering from Cisco PGW 2200 Softswitch Failure, page 6-172

• Restoring Stored Configuration Data, page 6-177

• Restoring a Backup File from a Device, page 6-178

• Configuration Export Failed Because of MMDB, page 6-180

• Measurements Are Not Being Generated, page 6-180

• Call Detail Records Are Not Being Generated, page 6-181

• Resolving a Failed Connection to a Peer, page 6-181

• Rebooting Software to Modify Configuration Parameters, page 6-183

• Diagnosing SNMP Failure, page 6-184

• Correcting the System Time, page 6-185

• Securing Your Network, page 6-187

• TIBCO Interface Not Working, page 6-195

• Installing the License File, page 6-197

• Replacing a Failed Disk, page 6-197

Verifying Cisco PGW 2200 Softswitch Ethernet Operation

See the documentation that Sun Microsystems provides for more information on verifying the proper

functioning of the Ethernet connections on the Cisco PGW 2200 Softswitch.

Deleting Unnecessary Files to Increase Available Disk Space

You might need to delete call trace files, archived log files, or configurations from your system to

increase available disk space on the Cisco PGW 2200 Softswitch. The following procedure presents the

process for deleting all three file types.

Step 1 Log in to the active Cisco PGW 2200 Softswitch and enter the cd /opt/CiscoMGC/var/trace and ls

UNIX commands to determine whether the affected disk drive contains any call trace files in the

/opt/CiscoMGC/var/trace directory.

The system responds with a list of files in the directory. If the command response indicates that there are

*.btr and *.trc files in this directory, proceed to Step 2. Otherwise, proceed to Step 4.

Note Do not delete any call trace files that are related to troubleshooting any current system problems.