Troubleshooting guide

3-5

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

OL-0800-14

Chapter 3 Cisco PGW 2200 Softswitch Platform Operations

Daily Tasks

If any of the processes stop, contact the Cisco TAC for assistance. See the “Obtaining Documentation

and Submitting a Service Request” section on page xviii for more information on contacting the Cisco

TAC.

Understanding Processes

The Cisco PGW 2200 Softswitch software contains processes and process groups that perform various

functions. These functions include managing the I/O channels; generating alarms, call detail records

(CDRs), and logs; and performing signal conversion. The Cisco PGW 2200 Softswitch software process

manager processes all these processes.

There are three different process monitoring levels:

• Active process—Controlled and monitored directly by the process manager.

• Passive process—Does not communicate with the process manager.

• Monitoring process—Periodically runs an executable file or script and sets or clears an alarm that

is based on the return code. This type of process can monitor other processes or tasks that can be

checked programmatically. Some examples are the amount of available disk space, system daemon

existence, and established process dependency.

Table 3-1 shows the system processes and process groups that are controlled by the process manager. All

the processes are in the directory /opt/CiscoMGC/bin.

Table 3-1 Processes Controlled by the Process Manager

Group Process Description

ENGG-01 Engine Group

Replic-01 Replicator controller. It is an active process. If it fails, it causes a

critical out-of-service alarm.

ENG-01 Call engine. It is an active process. If it goes down, the system

cannot process calls. Its failure causes a critical out-of-service

alarm.

IOSG-01 I/O Subsystem Group

IOCM-01 I/O channel manager. It is a passive process. If it goes down, it