Maintenance-Object Repair Procedures
555-233-143
8-926
Issue 1 May 2002
INADS Link Test (No Test Number)
The INADS Link test attempts to call an alarm receiver (in the background) to
verify the communications link with the alarm receiver. When a user issues the
test inads-link command, the system immediately returns either a
Command
successfully completed
or
Command failed
message.
The “Command successfully completed” message means the switch will attempt
attempt to call the alarm receiver in 2 minutes. (This test runs even if Alarm
Origination is disabled.) The 2-minute delay provides enough time for a remote
technician to hang up the call and thus free up the alarm receiver’s line so that the
customer’s switch can call the alarm receiver back. The “Command failed”
message appears when either:
■
A previously issued test inads-link command is in progress
■
The system is attempting to report active alarms to the alarm receiver
As any error conditions are encountered during the test, they are logged against
the INADS Link MO.
■
If the initial test result was “Command successfully completed,” any logged
error codes would range from 1–9.
■
If the initial test result was “Command failed,” any logged error codes would
be 10 or 11.
An error is logged at the alarm receiver even if the call to the alarm receiver finally
succeeds. The the alarm receiver’s software (Release 3.2 or later):
1. Recognizes this special “test inads” alarm type
2. Automatically opens and closes a trouble ticket
Within the trouble ticket, a field containing the description “TESTING
INADS LINK” indicates that the ticket was initiated by a test inads-link
command.
After entering the command, up to 9 minutes can elapse before the switch places
the call and the alarm receiver responds. Therefore, to determine whether the call
was successful, the Error Log should be examined (using the inads category)
10 minutes after successfully issuing the command.
explains the
error codes.
Summary of Contents for S8700 Series
Page 50: ...Maintenance Architecture 555 233 143 1 26 Issue 1 May 2002 ...
Page 74: ...Initialization and Recovery 555 233 143 3 12 Issue 1 May 2002 ...
Page 186: ...Alarms Errors and Troubleshooting 555 233 143 4 112 Issue 1 May 2002 ...
Page 232: ...Additional Maintenance Procedures 555 233 143 5 46 Issue 1 May 2002 ...
Page 635: ...status psa Issue 1 May 2002 7 379 555 233 143 status psa See status tti on page 7 406 ...
Page 722: ...Maintenance Commands 555 233 143 7 466 Issue 1 May 2002 ...