fails, the user performs a manual RTS. The user also performs a manual REX,
or an automated REX, to return the XPM to service from ISTb.
A REX maintenance record is stored for each XPM that contains the following
information:
•
REX scheduler, if the XPM is in the system
•
date and time and result (passed/failed) of the last REX
•
failure reason, diagnostics failures, and a list of defective cards, if the last
REX failed
•
date and time of previous failed REX
•
date and time of first passed REX that follows previous failure
The following limits apply to REX tests:
•
SuperNode supports concurrent REX tests for a maximum of ten XPMs
with the same REX test class.
•
For REX to run, the node must be either:
— INSV, ISTb because of a REX failure
— ISTb because P-side PCM30 links are OOS
•
If a Warm SWACT is not possible, REX terminates.
•
After successful completion of REX, the XPM has a new active unit
because of the SWACT.
•
If a restart occurs while REX is in progress, the system does not generate
the PM600 log. The system does not generate the log because the restart
deallocates the temporary data store used to build the PM600 log.
•
The system provides No SWACT controller override for manual REX.
REX test state machine interface to the pre-SWACT and
post-SWACT audits
The REX test state machine or controller:
•
calls the pre-SWACT audit, messages the other unit, and the warm SWACT
occurs if the audit passes
•
accounts for SWACT denial and failure reasons
•
terminates a REX test if a SWACT denial occurs
•
terminates a REX test if a SWACT back occurs. The active unit of the
XPM does not change from the time the REX test began. A REX test
DMS-100 Family Remote Switching Center Multi-Access Maintenance Manual XPM11 and up
Maintenance overview 2-63