Troubleshooting guide

3-28
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
Automatic System Log Rotation
As the system operates, the Cisco PGW 2200 Softswitch software creates the system logs that are stored
in a file in the /opt/CiscoMGC/var/log directory. The XECfgParm.dat file parameter sets the name of the
system log file, logFileNamePrefix (the default value is platform). The Cisco PGW 2200 Softswitch
software stops writing to the current system log file, archives the contents of that file, and commences
writing to a new system log file. This process is referred to as log rotation.
Log rotation occurs because of one of the following conditions:
• Cisco PGW 2200 Softswitch software startup (the log rotation script is run)
• Log rotation script (log_rotate.sh) is run manually.
• Size of the active system log file exceeded the value that is set in the XECfgParm.dat parameter,
fileRotateSize.
• Time elapsed since the last log rotation exceeded the value that is set in the XECfgParm.dat
parameter, fileRotateInterval.
When the system rotates the system log file, it archives the current system log file and opens a new
system log file. The system stores the archived log file in the /opt/CiscoMGC/var/spool directory. Once
the Cisco PGW 2200 Softswitch software is operating, the log server takes over the actual file rotation
function of renaming the active file to a historical file with a new filename. The filename is constructed
according to the following format:
logFileNamePrefix_yyyymmddhhmmss.log, where the time stamp indicates the system date and time
when the log is rotated.
Rotating System Logs Manually
You can also run the log rotation script manually to force the system to archive the current system log
file. To run the script manually, log into the active Cisco PGW 2200 Softswitch as root, and enter the
following UNIX command:
/opt/CiscoMGC/bin/log_rotate.sh
The system creates a new current system log file and archived log file, as described in the “Automatic
System Log Rotation” section on page 3-28.
Creating a Disaster Recovery Plan
You should formulate a disaster recovery plan to ensure that you can restore the Cisco PGW 2200
Softswitch after it is forced out of service by a natural or man-made disaster. The plan should include
regular backups of the system software.
See the “Backing Up System Software” section on page 3-29 for more information about backup
operations. Store the backup data for your system in a secure location, in a site separate from the
equipment, to ensure that the same disaster does not affect the backed up data.
For information on performing a disaster recovery, see the “Recovering from Cisco PGW 2200
Softswitch Failure” section on page 6-172.