DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Architecture
1-20SPE Duplication
1
As shown in Figure 1-7, all maintenance capabilities for the standby SPE are built
upon these three strategies.
Figure 1-7. Components of Standby Maintenance
Standby SPE maintenance software is designed to attempt to self-correct
problems. If a problem occurs, this software automatically tries to address the
problem, bring the standby SPE back to a state of availability and clear all alarms
which might have been raised. Typically, if a standby SPE problem has not
cleared, it is of a hardware nature and some type of hardware component
maintenance or replacement action is indicated. Once such corrections have
been made, the system software will automatically bring the standby SPE back to
full availability. There is no management terminal command to stimulate refresh of
standby SPE memory; system software automatically accomplishes this itself
when conditions are appropriate. The same is true of efforts to turn on shadowing
where no explicit user interface command to turn on/off shadowing is available
(note that busyout/release, below, can be used to indirectly accomplish this).
Standby Maintenance Monitor Software
The Standby Maintenance Monitor (SMM) is a software package that is
always
running on key components of the standby SPE to verify its competence. SMM
tests individual standby SPE components and reports back to the active SPE, by
the handshake message, any failures of individual tests. Failure reports trigger
enhanced maintenance attention to standby SPE component problems by active
Standby SPE
Hardware Status
Reading
Maintain
Handshake
Communication
Maintain
Standby SOH,
Shadowing,
Lock
Status
Memory
Shadowing
Memory
Refresh
G3-MT
Access to
Standby SPE
Components
Error/Alarm
Logging
for Standby
Components
Handshake
Comm. Up
Time of day
clocks
in synch
Handshake
Comm.Down
Stby SPE
down/lock
G3-MT
Access to
SPE-Down
Interface
