Xsm100; Xsm101; Xsm102 - Nortel Meridian SuperNode SL-100 Reference Manual

7-10 Log and fault reports

XSM100

Log XSM100 is generated when the XSM maintenance task on the CC is
unable to send a status inquiry message to the XSM due to the datalink being
down. This log belongs to the optional subsystem XSMSUB.
The following is an example report format:
XSM100 mmmdd hh:mm:ss nnnn INFO XSM_DATA_REPORT
DATALINK indicates the datalink datafilled in Table SLLNKDEV associated
with the destination master XSM.
The following is an example log report:
XSM100 JAN23 17:36:35 1234 INFO XSM_DATA_REPORT
Operating company personnel should take action to bring the datalink into
service.

XSM101

Log XSM101 is generated for each SLLNK datalink the first time an XSM
status inquiry message is successfully queued after the XSM100 condition is
cleared. This log belongs to the optional subsystem XSMSUB.
The following is an example report format:
XSM101 mmmdd hh:mm:ss nnnn INFO XSM_DATA_REPORT
The following is an example log report:
XSM101 JAN23 17:52:05 1235 INFO XSM_DATA_REPORT

XSM102

Log XSM102 is generated when the XSM input handler cannot process an
incoming message due to free queue being exhausted. This log belongs to the
optional subsystem XSMSUB.
555-4001-129 Standard 08.01 November 2000
<Report text here>
DATALINK = <sllnk device name>
DATALINK IS DOWN.
DATALINK = XSMLOOP1
<Report text here>
DATALINK = <sllnk device name>
DATALINK IS UP.
DATALINK = XSMLOOP1
FAILED TO SEND XSM MESSAGE.
STATUS INQUIRY SENT.