|
|
These system operation procedures refer to a Sun Host Computer configuration. The procedure flow diagram can be found in "Alarm Support Diagrams."
Under normal conditions, powering up the system will automatically launch the TransPath system and the SNMP (simple network management protocol) daemon. The SNMP is used to manage TCP/IP network devices, configurations, data collection, performance, and security. Activating the SNMP daemon initiates these processes. Using the platform startup command sequence located in the inittab file and the /etc/init.d directory, the platform auto-start boots up the system with the default settings for your configuration.
The /etc/rc3 file contains commands and operations executed when the system enters full multi-user mode. This file invokes /etc/rc3.d/S50transpath to automatically start the TransPath system. The UNIX file named S50transpath is linked to another file named /etc/init.d/transpath.
Another way to start the system is to use the semi-automatic function. This can be accomplished by manually executing the following single command line:
#sh /etc/init.d/transpath start
#sh is the super user prompt. The operator must have Superuser access in order to run this startup command.
The Process Manager (procM) software program is used to start all platform processes and configurations required for processing traffic through the system. The startup sequence checks the "process status" for any running platform processes and will not attempt to start up any process that is already running.
The TransPath system can be configured to enable manual startup. Using this technique, the TransPath system has the same operational characteristics as automatic and semi-automatic startup, but file and process permissions are altered. Manual startup should only be performed when semi-automatic startup does not provide the necessary degree of process control.
 | Caution Manual startup alters file and process premissions. Only perform manual startup when semi-automatic startup does not provide the necessary degree of process control. |
Step 1 Prior to initiating this command sequence, the user must be assigned to the /etc/group transpath.
Step 2 Do not start the application outside of TransPath ownership. This creates a process and file ownership contention within the platform being initialized.
Step 3 The user must inherit the TransPath system user login shell environment variables. (See Chapter 10, "System Administration.")
Step 4 The Operator must log on as a user assigned to the group: transpath
However, when the user normally defaults to a different group on login, the user must execute the newgrp transpath procedure prior to the Process Manager (procM) startup command. This UNIX command line is:
>newgrp transpath
Step 5 Enter this executable command line to change directories to the directory named "bin":
>cd /opt/TransPath/bin
Step 6 Enter this executable command line to start the Process Manager:
>/opt/TransPath/bin/procM
The Process Manager starts up.
The system operation procedure flowchart for stopping the application can be found in "Alarm Support Diagrams."
An operator with Superuser privilege can stop the TransPath system application by invoking a command file. This would occur, for example, during maintenance and engineering windows in order to service the network element. This can be accomplished by manually executing the following single command line:
#sh /etc/init.d/transpath stop
The status of the processes will be displayed until the platform shutdown is completed.
This procedure allows any user assigned by the System Administrator to the transpath group to stop the application with the Man Machine Language (MML) user interface provided as part of the package.
Step 1 Prior to initiating this command sequence, the user must be assigned to the /etc/group transpath and must have inherited the application specific environment variables.
Step 2 The Operator must log on as a user assigned to the transpath group.
Step 3 Start the MML session in the application, using this UNIX executable command line:
However, if the default MML session is occupied by another person, then the user must initialize an idle MML session by using a session ID variable. The following UNIX executable command line must be entered:
>mml -s [x] ( x = session number. See "MML Commands.")
Step 4 Next, enter the following MML Command:
mml> STP-SOFTW:ALL
Step 5 The Process Manager (PM-01) process stops all processes except itself. Retrieve the Process Status by executing the following MML command:
mml> RTRV-SOFTW:ALL
See "MML Commands" for the MML command responses.
Step 6 After the Process Manager has removed all TransPath system support software from service and placed them in a "not running" state, execute the Stop Process Manager MML command.
mml> STP-SOFTW:PM-01
Step 7 The only processes currently running are the MML session(s), from which a "quit" command must be used to remove all TransPath system associated software from system operations.
Execute this command:
mml> QUIT
When necessary, the operator can execute UNIX level commands to identify and terminate any outstanding MML sessions that exist on the system.
The Process Manager manages the TransPath system and is responsible for controling the various process and process groups that make up the system. With the Process Manager, users can start, monitor, and shut down the various processes running on the TransPath system.
The following are the three major functions of the Process Manager:
1. Starting up applications and their processes in an orderly manner.
2. Monitoring the health of managed processes and restarting processes as defined in the processes.dat file.
3. Shutting down applications and their processes in an orderly manner.
The following is a list of the process groups that the Process Manager control:
| Execution environment |
|---|---|
| Engine |
| IO subsystem |
| Performance monitoring |
The individual processes are described in the following table.
| Process | Group | Executable | Description |
CFM-01 | XEG-01 | ../bin/cfgM | Configuration manager |
ALM-01 | XEG-01 | ../bin/almM | Alarm manager |
MM-01 | XEG-01 | ../bin/measMgr | Measurement manager |
DMPR-01 | XEG-01 | ../bin/dmpr | Dumper |
ENG-01 | ENGG-01 | ../bin/engine | Engine |
IOCM-01 | IOSG-01 | ../bin/ioChanMgr | IO Channel manager |
IOCC-01 | IOSG-01 | ../bin/ISDNPRI | IO Channel controller ( |
IOCC-02 | IOSG-01 | ../bin/DPNSS | IO Channel controller ( |
IOCC-ASP | IOSG-01 | ../bin/ASP | IO Channel controller (Aux Sig Network) |
DSKM-01 | PFMG-01 | ../local/diskmonitor.sh | Disk monitor |
Once the Process Manager and the rest of the processes are running, the operator can then stop and start processes individually, or by process group, using the MML interface commands. Applications consist of one or more operating system processes that are managed as a group. Each application may be managed independently of the others.
The operator cannot start the Process Manager using MML interface commands. When the MML command STP-SOFTW is used to stop the processes, restart the Process Manager by executing the platform semi-automatic startup procedure (see the "Semi-Automatic Startup" section
). The Process Manager goes through its initialization sequence and starts any other processes that were stopped at the time of initialization. The Process Manager does not restart any process or process group that is already running. When the Process Manager is already running, the sequence for a graceful system startup by the MML is as follows:
1. XEG-01
2. ENGG-01
3. OSG-01
4. PFMG-01
The TransPath system database contains the dependencies.dat table, which controls the order in which the Process Manager (PM-01) starts and stops processes and process groups. Dependencies have been established as part of the default installation of the software onto the system. The default settings have been established to prevent certain processes or process groups from starting or stopping, either before or after another process or process group. A command to start or stop a process or process group that has dependencies results in a delay of execution until all dependents have been stopped or started. In other words, the command to start or stop a process or process group is in a pending execution state until the dependency on another process or process group is cleared.
The following tables show how the processes are organized into groups and how inter-dependencies are formed. These are simple examples: customer configurations will vary significantly. For process group information, refer to "Data Dictionary and Glossary."
| Criteria | Process Group | Process | |
1 | Call processing critical | IOSG-01 | IOCM-01 IOCC-01 IOCC-02 IOCC-ASP |
2 | Call processing critical | ENGG-01 | ENG-01 |
3 | Support system critical | XEG-01 | CFM-01 ALM-01 DMPR-01 MM-01 |
4 | Support system non critical | PFMG-01 | DSKM-01 |
| Dependent Type (g = group, p = process) | Dependent | Dependency Type (g = group, p = process) | Parent |
g | ENGG-01 | g | XEG-01 |
g | IOSG-01 | g | ENGG-01 |
p | IOCM-01 | g | XEG-01 |
p | IOCC-01 | p | IOCM-01 |
p | IOCC-02 | p | IOCM-01 |
p | IOCC-ASP | p | IOCM-01 |
DSKM-01 and PFMG-01 are not listed because they are not dependents of any call processing or support processes. They can be started or stopped without any interference from the mission critical processes. For additional information on the dependencies table, refer to "Data Dictionary and Glossary."
The retrieve software MML command RTRV-SOFTW:<proc> examines the system processes, and returns the status of the managed processes. This MML command displays the status of a process, process groups, or all processes. The status of a process can be either RUNNING or NOT RUNNING. There are three variations of this command:
A process in the NOT RUNNING state can be started by using the MML start software process command: STA-SOFTW:<procName>.
To retrieve the process status for a specific process, use the MML command RTRV-SOFTW with the name of the process as in the following examples:
mml> RTRV-SOFTW:<proc>
For emaple:
mml> RTRV-SOFTW:ENG-01
Sample response:
CONFIG01/BUILD 13.6 97-05-15 14:37:08
M RTRV
"ENG-01:RUNNING"
;
To retrieve the process status for a specific process group, use the MML command RTRV-SOFTW with the name of the process group as in the following examples:
mml> RTRV-SOFTW:<groupName>
For example:
mml> RTRV-SOFTW:XEG-01
Sample Response:
CONFIG01/BUILD 13.6 97-05-15 14:39:15 M RTRV "CFM-01:RUNNING" "ALM-01:RUNNING" "MM-01:RUNNING" "DMPR-01:RUNNING" ;
To retrieve the process status for all processes and all process groups, use the MML command RTRV-SOFTW: with the word ALL at the end as in the following example:
mml> RTRV-SOFTW:ALL
Sample Response:
CONFIG01/BUILD 13.6 97-05-15 14:41:27 M RTRV "CFM-01:RUNNING" "ALM-01:RUNNING" "MM-01:RUNNING" "DMPR-01:RUNNING" "DSKM-01:RUNNING" "ENG-01:RUNNING" "IOCM-01:RUNNING" "IOCC-01:RUNNING" "IOCC-02:RUNNING" ;
The operator can start an individual process or a process group. The start software command is issued to the Process Manager, which in turn executes and manages the startup sequence of the targeted process or subsystem. The MML commands start a process or process group with the name of the process or group following the colon. STA-SOFTW:<procName> starts a process, while STA-SOFTW:<groupName> starts a process group. These commands are shown in the following examples:
mml> STA-SOFTW:<procName>
For example:
mml> STA-SOFTW:<groupName>
The operator can start an individual process. The start software command is issued to the Process Manager to start the individual process. The Process Manager executes and manages the startup sequence for the targeted process. These commands are shown in the following examples:
mml> STA-SOFTW:<procName>
For example:
mml> STA-SOFTW:DSKM-01
Sample Response:
CONFIG01/BUILD 13.6 97-05-15 14:47:01
M COMPLD
;
mml>
The operator can start a process group. The start software command is issued to the Process Manager to start the specified process group. The Process Manager executes and manages the startup sequence for the targeted process group. These commands are shown in the following example:
mml> STA-SOFTW:<groupName>
For example:
mml> STA-SOFTW:IOSG-01
Sample Response:
CONFIG01/BUILD 13.6 97-05-15 14:51:48
M COMPLD
;
mml>
The procedures for starting individual or group processes are covered in "Alarm Support Diagrams."
The operator can stop an individual process, a process group, or all processes. The stop command is issued to the Process Manager, which in turn executes and manages the shutdown sequence of the targeted process or subsystem.
The operator can stop an individual process. The stop software command is issued to the Process Manager to stop the specific process. The Process Manager executes and manages the stop sequence for the targeted process. For example:
mml> STP-SOFTW:<procName>:<KILL>
> parameter shown in the example above is used only in cases when the operator intends to bypass the normal termination signal to the process, thus expediting the shutdown. As a result, the shutdown may cause the recovery data to be out of sync upon restart of the process. See "MML Commands" for a more detailed explanation of these commands.
Sample Response:
CONFIG01/BUILD 13.6 97-05-15 14:57:47 M COMPLD ;
The operator can stop a process group. The stop software command is issued to the Process Manager to stop the specified process group. The Process Manager executes and manages the stop sequence for the targeted process group. For example:
mml> STP-SOFTW:<groupName>
For example:
mml> STP-SOFTW:IOSG-01
Sample Response:
CONFIG01/BUILD 13.6 97-05-15 14:57:47 M COMPLD ;
Use this MML command to stop all other processes and process groups except for the MML and the Process Manager (procM). Both of these continue to run after the following command is issued:
mml> STP-SOFTW:All
Sample Response:
CONFIG01/BUILD 13.6 97-05-15 15:02:15 M COMPLD SWDT "ALL:" ; mml>
The procedures for stopping individual or group processes are covered in "Alarm Support Diagrams."
|
|