Troubleshooting guide

3-26
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations
Periodic Maintenance Procedures
If any disk partition exceeds the configured usage threshold, the Cisco PGW 2200 Softswitch generates
a DISK alarm (a major alarm). The DISK alarm warns of a disk partition overrun and of insufficient disk
space. See the “DISK” section on page 6-38 for information about the corrective actions that are required
to resolve a DISK alarm.
Disk monitor does not trim some other files, such as call trace files, which use large amounts of disk
space. You might need to delete call trace files periodically. The system creates call trace files when you
perform call traces while troubleshooting a problem. These files can be rather large. Leaving them on
your disk could cause problems. For more information about deleting call trace files, see the “Deleting
Unnecessary Files to Increase Available Disk Space” section on page 6-169.
Configuring Disk Monitor
You can configure the disk monitor only while the Cisco PGW 2200 Softswitch software is turned off.
Therefore, you should configure disk monitor only during initial installation. For more information on
configuring the disk monitor during initial installation, see the XECfgParms.dat section of Cisco PGW
2200 Softswitch Release 9.8 Software Installation and Configuration Guide.
To configure disk monitor after initial installation, perform the following steps:
Caution To perform the following procedure, turn off the Cisco PGW 2200 Softswitch software. Do not attempt
the following procedure without the guidance of the Cisco TAC. See the “Obtaining Documentation and
Submitting a Service Request” section on page xviii for more information on contacting the Cisco TAC.
If your system is a single Cisco PGW 2200 Softswitch in a simplex configuration, performing this
procedure causes the system to drop all calls.
Step 1 Determine whether any alarms are pending on the active Cisco PGW 2200 Softswitch, as described in
the “Retrieving All Active Alarms” section on page 6-3.
If any alarms are pending, you can determine the appropriate courses of action by searching for the
corrective actions for those alarms in the “Alarm Troubleshooting Procedures” section on page 6-4. If
the alarms are not in that section, corrective action is not required. For more information on those alarms,
see the Cisco PGW 2200 Softswitch Release 9 Messages Reference.
Step 2 Repeat Step 1 for the standby Cisco PGW 2200 Softswitch.
Step 3 On each host, modify the disk monitor parameters in the XECfgParm.dat files. Use the procedure that is
described in the “Rebooting Software to Modify Configuration Parameters” section on page 6-183.
• diskmonitor.Limit parameter—Sets the number of days to preserve logged data before trimming.
The default value is 7.
• diskmonitor.OptFileSys—Enables monitoring user-configurable file systems. This utility monitors the
/opt file system for threshold crossing. Using this parameter, you can monitor additional file systems
(disk slices) by setting the parameter to the preferred directory, such as /tmp, /usr, or /var. The system
sends the messages that are associated with this parameter to the platform.log file. To retrieve these
messages, you must scan the platform.log file for messages. The system presents the messages in the
following format:
Filesystem <file_system_name> has exceeded <num> percent full.
The following sample output shows how a message appears:
Filesystem /var has exceeded 80 percent full