Server initialization, recovery, and resets
S8700 Initialization
120
Maintenance Procedures
December 2003
e
DupMgr
f
Avaya™ Communication Manager
These applications come up and start heartbeats to the Watchdog.
NOTE:
Use the Linux command statapp to view the status of the applications.
The Watchdog also starts up a script to monitor Linux services. It starts up threads to
communicate with a Hardware-Sanity device.
6
Hardware-Sanity — The Watchdog periodically tells the hardware-sanity device how long to wait
before rebooting the system. If the Hardware-Sanity driver doesn’t receive an update within that
interval, the HW Watchdog’s timer resets the processor.
7
Arbiter — The Arbiter decides whether the server goes active or standby.
Active server’s initialization
These steps are executed on the server or active server (duplicated):
1
Avaya™ Communication Manager — The Watchdog process creates the Communication
Manager application by starting up the Process Manager (prc_mgr). The Process Manager starts
up the Communication Manager processes by:
•
Reading the Process Table file (
/opt/defty/bin/Proc_tab.z
)
•
Creating every process with the PM_INIT attribute
Other Communication Manager processes (i.e., “initmap” and “hmm”) create other “permanent”
Communication Manager processes.
The Process Manager also:
•
Verifies that Communication Manager is authorized to run on this server.
•
Maintains a heartbeat to the Watchdog.
Standby server’s initialization
These steps are executed on the standby server:
1
Avaya™ Communication Manager — On the standby server, many processes are frozen so that
the Standby DupMgr can shadow into them without interfering with those writes. However, some
shadowed and unshadowed processes need to run on the standby. These processes are known as
the “run-on-standby” processes, and they have the RUN_STBY attribute.
The PCD process runs on the standby to communicate with port networks. The rest of these
processes support the PCD or create processes that need to be shadowed into.
Some of the processes are:
•
prc_mgr (Process Manager) — unshadowed
•
phantom — unshadowed
•
net_mgr — unshadowed
•
tim — unshadowed
Summary of Contents for CMC1
Page 1: ...Maintenance Procedures 555 245 103 Issue 1 1 December 2003 ...
Page 14: ...Contents 14 Maintenance Procedures December 2003 ...
Page 416: ...Additional maintenance procedures IP Telephones 416 Maintenance Procedures December 2003 ...
Page 426: ...Index X 426 Maintenance Procedures December 2003 ...
