Nortel DMS 100 Series Maintenance Manual page 81

The REX test order is as follows:
• critical nodes like CM and MS
• the number of days since the last system or manual REX test
• the order of internal PM number
Table REXSCHED must be entered to establish the REX schedule for the
RSC-M. This table contains the information that the the REX coordinator
requires to schedule the tests according to operating company specifications.
In addition, the entry of table REXSCHED can disable the test. For additional
information on table REXSCHED, refer to the data schema section of the
Translations Guide.
The system generates the node evaluation graph log (NAG400) each hour, or
in response to the NAG command. The system generates this log to list all
nodes not INSV. The REX_INFO field of log NAG400 displays the results of
the latest REX test.
Audits of the IM links
sure the data passed on the links is not lost or damaged. The audit runs on the
inactive and active units. If the system detects a fault, the active INSV unit
reports the fault to the CC.
When the system detects a fault on the IML link or links, the following occurs:
• the link is closed.
• the RSC-M status changes to ISTb.
• the RSC-M units do not communicate over the links. A Warm SWACT
cannot occur.
• the system generates a PM128 log.
at the RSC-M level, the QUERYPM FLT command contains the following
message:
NOT-CRITICAL HARDWARE FAULT
RSC-M testing
Operating company personnel normally issue the TST command to test the
RSC-M. The types of test depend on two conditions, the state of the RSC-M
and the parameters in the TST command.
The following determines fault conditions for the RSC-M:
• overload indicators (PM128, QUERYPM)
• REX
DMS-100 Family Remote Switching Center Multi-Access Maintenance Manual XPM11 and up
An audit runs sanity tests on IM links to make
Maintenance overview 2-65