NS3000/iX Error Messages Reference Manual (36923-90043)

382 Chapter18
PCI LAPBMUX Link Error Messages
SDI Generic Status Values
ACTION: Make the appropriate changes and reissue the request.
129 ($81) MESSAGE: An invalid connection ID was specified.
CAUSE: The requested Connection ID does not exist.
ACTION: Make the appropriate changes and reissue the request.
130 ($82) MESSAGE: Link did not understand the specified address family.
CAUSE: The Driver detected an error in the address family in the
request message.
ACTION: Fix the configuration file and then try again.
131 ($83) MESSAGE: Link found an error within the specified address family.
CAUSE: The Driver detected an error in the address family in the
request message.
ACTION: Fix the configuration file and they try again.
132 ($84) MESSAGE: An invalid or redundant protocol SAP address was
specified.
CAUSE: For the Rendezvous Request, the LSAP value is the NULL or
Global SAP. For the connect request, this error indicates that this SAP
already has a link to the specified RSAP and destination address
combination, or the remote SAP specified was the null SAP, global SAP,
or a group SAP.
ACTION: Use an acceptable SAP and Destination Address.
133 ($85) MESSAGE: The specified local Protocol SAP was already opened.
CAUSE: For the Rendezvous Request, this error indicates that the LSAP
has already opened.
ACTION: Use an acceptable SAP value.
161 ($A1) MESSAGE: A request was not accepted due to current state of the
link.
CAUSE: The requested message cannot be accepted because of the
existing state of the link station. (example, A write event message will
not be accepted if the link is in the disconnected, opening or closed
state).
ACTION: According to the subsystem.
201 ($C9) MESSAGE: A formatter error was detected.
CAUSE: A Module Configurator/Deconfigurator failed to start/stop the
TRACE MANAGER, however, the configuration/deconfiguration
operation has completed (example, The Driver has deallocated the
Driver’s resources).
ACTION: According to the subsystem.