57
TOPS VSN Log and alarm messages
12. Control link log messages - 9441
0000/0000
Message:
Data Link [link_identifier] to DMS [common_language_location
_identifier] is in service.
Description:
This log is generated when the X.25 Control Link has been
reset. At initialization time this log is considered a normal occurrence. At any
other time it is not. Data may have been lost depending on the activity in
progress at the time of the reset.
Action:
No action is required. The condition indicates that a link is now
available. If data was lost, if cannot be recovered.
0000/0001
Message:
Data Link [link_identifier] to DMS [common _language_location
_identifier] is out of service. Reason = [reason].
Description:
This log is generated when the X.25 Control Link is no longer
available for use. Data may have been lost depending on the activity in
progress at the time of the reset. The reason may be one of the following: 1)
X.25 PRU managing link is down ( The X.25 PRU is out of service), or 2) Link is
down (X.25 service associated with the physical link has been reset and is no
longer available).
Action:
No action is required if within 30 seconds a log is generated
indicating that the specified data link is now available. If this log does not follow,
check all physical connections. If all are in good order, the problem is likely
associated with a DMS failure (i.e.. MPC card). If the reason given is X.25 PRU
Failure, the PRU must be returned to service. If a return to service does not
happen automatically, it means the maximum fault count limit has been
exceeded. This indicates that the processor is in trouble.
0000/0002
Message:
Data Link PRU has bad initialization data.
Reason = [reason].
4
Description:
This log is generated when invalid data has been found in
"Datalink_Config" or "VSN_System" tables for a particular Data Link (DL) PRU.
The reason given may be one of the following: 1) too many links (more than 4
links have been configured for each DL PRU), 2) Data Link tables are missing 3)
no links defined in tables (no links are defined in Datalink_Config table), 4) X.25
PRU referenced in table does not exist (the X.25 PRU number in Datalink
Config table does not exist), 5) no call sanity timeout parameter defined in
VSN_System table, 6) No maximum calls allowed parameter defined in
VSN_System table, 7) no VSN identifier defined in VSN_System table, 8) two
different DMS CLLIs defined for one Data Link PRU.
Action:
Modify data entry in Datalink_Config or VSN_System tables, then
reinitialize the failed DL PRU.