CLASS: Protocol 600-699

zx25d 600 ZCOM has been shutdown. The ACC X.25 subsystem is now down!

Explanation:: The ZCOM subsystem was shutdown by a user issuing a zmasterd stop command. The ACC X.25 subsystem will automatically shut itself down when this occurs. The ACC X.25 subsystem requires the ZCOM subsystem in order to operate.
Action:: No action is necessary. This is an informational message.

zx25d 601 Link ZLU <#> not established on enable. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: This message is logged if an X.25 link has been enabled but the X.25 subsystem was unable to establish X.25 at level 2. Usually this is because the remote system/device is not responding. The X.25 link will automatically come up when the remote system responds.
Action:: No action is necessary. This is an informational message.

zx25d 602 Link ZLU <#> disconnected due to DISABLE request. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has been disconnected due to a user or application issuing a request to disable the X.25 link ZLU. After this message, the X.25 link will not respond to level 2 protocol packets.
Action:: No action is necessary. This is an informational message.

zx25d 603 Link ZLU <#> disconnected due to loss of Carrier Detect. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has gone down because the modem line Carrier Detect (CD) has dropped. That is, X.25 at level 1 is down and has not come back up. Note that the X.25 link Poll word bit CTS can control how the firmware behaves with respect to the CD and CTS modem lines.
Action:: No action is necessary. This is an informational message.

zx25d 604 Link ZLU <#> disconnected due to loss of CTS. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has gone down because the modem line Clear-To-Send has dropped. That is, X.25 at level 1 is down and has not come back up. Note that the X.25 link Poll word bit CTS can control how the firmware behaves with respect to the CD and CTS modem lines.
Action:: No action is necessary. This is an informational message.

zx25d 605 Link ZLU <#> down; exceeded N2 retransmit limit. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has experienced transmission errors and the HDLC/LAP-B link has gone down because the N2 retransmission counter has been exceeded. The X.25 subsystem has been unable to re-establish the link at level 2.
Action:: No action is necessary. This is an informational message.

zx25d 606 Link ZLU <#> down due to transmitted FRMR. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:

The X.25 link has gone done due to the transmission of a Frame Reject (FRMR). The X.25 subsystem has been unable to re-establish the HDLC/LAP-B link. Possible reasons for an FRMR are:

Receipt of a command or response that is invalid or not implemented.
Receipt of an I frame with an information field exceeding the maximum established length.
Receipt of a frame with an information field that is not permitted, or receipt of an S frame or U frame of incorrect length.
Receipt of an invalid N(R) within an incoming frame.

Action:

No action is necessary. This is an informational message.

zx25d 607 Link ZLU <#> down due to received FRMR Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has gone down due to the receipt of a Frame Reject (FRMR). The X.25 subsystem has been unable to re-establish the HDLC/LAP-B link. Possible reasons for an FRMR are described in message 606.
Action:: No action is necessary. This is an informational message.

zx25d 608 Link ZLU <#> down due to received DM frame. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has gone down due to the receipt of a Disconnected Mode (DM) frame. The X.25 subsystem has been unable to re-establish the HDLC/LAP-B link. This DM frame is used to inform the primary that the secondary is in a logically disconnected state.
Action:: No action is necessary. This is an informational message.

zx25d 609 Link ZLU <#> down due to received SABM. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has gone down due to the receipt of a Set Asynchronous Balanced Mode (SABM) command. This message indicates the remote DXE has gone down without the knowledge of the local system and is now trying to resynchronize the link at level 2. The X.25 subsystem was unable to re-establish the HDLC/LAP-B link.
Action:: No action is necessary. This is an informational message.

zx25d 610 Link ZLU <#> disconnected due to received DISC. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has gone down due to the receipt of a Disconnect (DISC) frame. A DISC frame indicates that the remote DXE is terminating operations (e.g. shutting down).
Action:: No action is necessary. This is an informational message.

zx25d 611 Link ZLU <#> down due to received UA frame. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has gone down due to the receipt of an unexpected UA frame. The X.25 subsystem was unable to re-establish the HDLC/LAP-B link.
Action:: No action is necessary. This is an informational message.

zx25d 612 Link ZLU <#> down due to received unsolicited final response. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has gone down due to the receipt of an supervisory response frame that had the final response bit set (F-bit=1) when no final response was requested. The X.25 subsystem was unable to re-establish the HDLC/LAP-B link.
Action:: No action is necessary. This is an informational message.

zx25d 621 Link ZLU <#> HDLC/LAP-B established on enable. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: After a user or application has enabled the X.25 link ZLU, this message is logged when the X.25 subsystem has successfully established the X.25 link at level 2. Note that the X.25 link will not be usable until the packet layer has been restarted.
Action:: No action is necessary. This is an informational message.

zx25d 622 Link ZLU <#> reset due to DISABLE request. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: This message should never be observed during normal operations.
Action:: No action is necessary. This is an informational message.

zx25d 623 Link ZLU <#> reset due to loss of Carrier Detect. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has gone down because the modem line Carrier Detect (CD) has dropped. That is, X.25 at level 1 went down. This message indicates that level 1 is up and the X.25 subsystem is attempting to re-establish X.25 at level 2.
Action:: No action is necessary. This is an informational message.

zx25d 624 Link ZLU <#> reset due to loss of CTS. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has gone down because the modem line Clear-To-Send (CTS) has dropped. That is, X.25 at level 1 went down. This message indicates that level 1 is up and the X.25 subsystem is attempting to re-establish X.25 at level 2.
Action:: No action is necessary. This is an informational message.

zx25d 625 Link ZLU <#> reset; exceeded N2 retransmit limit. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has experienced transmission errors and the HDLC/LAP-B link has gone down because the N2 retransmission counter has been exceeded. The X.25 subsystem is in the process of re-establishing the X.25 link at level 2.
Action:: No action is necessary. This is an informational message.

zx25d 626 Link ZLU <#> reset due to transmitted FRMR Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has gone down due to the transmission of a Frame Reject (FRMR). The reasons for generating a FRMR are listed in message 606. The X.25 subsystem is in the process of re-establishing the X.25 link at level 2.
Action:: No action is necessary. This is an informational message.

zx25d 627 Link ZLU <#> reset due to received FRMR. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has gone down due to the receipt of a Frame Reject (FRMR). The reasons for generating a FRMR are listed in message 606. The X.25 subsystem is in the process of re-establishing the X.25 link at level 2.
Action:: No action is necessary. This is an informational message.

zx25d 628 Link ZLU <#> reset due to received DM frame. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has gone down due to the receipt of a Disconnected Mode (DM) frame. This DM frame is used to inform the primary that the secondary is in a logically disconnected state. However, it appears that the remote DXE is still responding and the X.25 subsystem is in the process of re-establishing the X.25 link at level 2.
Action:: No action is necessary. This is an informational message.

zx25d 629 Link ZLU <#> reset due to received SABM. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has gone down due to the receipt of a Set Asynchronous Balanced Mode (SABM) command. This message indicates the remote DXE has gone down without the knowledge of the local system and is now trying to resynchronize the link at level 2. The X.25 subsystem is in the process of re-establishing the X.25 link at level 2.
Action:: No action is necessary. This is an informational message.

zx25d 630 Link ZLU <#> reset due to received DISC. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: This message should never be observed during normal operations.
Action:: No action is necessary. This is an informational message.

zx25d 631 Link ZLU <#> reset due to received UA frame. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has gone down due to the receipt of an unexpected UA frame. The X.25 subsystem is in the process of re-establishing the X.25 link at level 2.
Action:: No action is necessary. This is an informational message.

zx25d 632 Link ZLU <#> reset due to received unsolicited final response. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: The X.25 link has gone down due to the receipt of an supervisory response frame that had the final response bit set (F-bit=1) when no final response was requested. The X.25 subsystem is in the process of re-establishing the HDLC/LAP-B link.
Action:: No action is necessary. This is an informational message.

zx25d 638 Link ZLU <#> FRMR reason code = 0x<#>.

Explanation:: This message is logged whenever a Frame Reject (FRMR) is transmitted or received and indicates the reason for the Frame Reject. See the HDLC/LAP-B specification for information on how to interpret the contents of the reason field.
Action:: No action is necessary. This is an informational message.

zx25d 639 Link ZLU <#> Unexpected packet received (length = <#>). Packet contents = 0x<#>.

Explanation:: This message is logged whenever an X.25 level 3 packet arrives that the X.25 protocol driver is unable to interpret its type or the packet type is unsupported. For example, receipt of a Registration Request will result in this message being logged because Registration Request packets are not supported. Note that the first four bytes of the input buffer are dumped in hex format.
Action:: No action is necessary. This is an informational message.

zx25d 640 Link ZLU <#> restarted due to invalid packet (type = <#>) received.

Explanation:: This message indicates that the X.25 packet layer is being restarted as required by the ITU-T specification due to the receipt of the indicated packet type. Possible packet types are as follows:
type 34 = Restart Confirm
type 35 = Call Request
type 36 = Call Connected
type 37 = Clear Indication
type 38 = Clear Confirm
type 39 = Reset Indication
type 40 = Reset Confirm
type 41 = Invalid Reset Ind
type 42 = Invalid Reset Conf
type 44 = Data packet
type 45 = Reject packet
type 46 = RNR packet
type 47 = RR packet
type 50 = Pkt Format Error
type 51 = Bad Restart pkt LCN
type 52 = Restart Format Error
type 54 = Unknown pkt type
type 57 = Pkt type not supplied
type 60 = Invalid Clear pkt
type 61 = Invalid Call pkt
Action:: No action is necessary. This is an informational message.

zx25d 641 Link ZLU <#>: Diagnostic Packet received. Diag code = <#>, Explanation=0x<#>.

Explanation:: This message is logged whenever a diagnostic packet is received. The message contains the Diagnostic code and Explanation fields from the diagnostic packet.
Action:: No action is necessary. This is an informational message.

zx25d 642 Link ZLU <#> X.25 Packet layer (lvl 3) restart complete. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: This message is logged whenever the X.25 subsystem completes the restart processing for X.25 at level 3. This indicates that the X.25 link is now fully established and can be used to establish calls and transfer data.
Action:: No action is necessary. This is an informational message.

zx25d 643 X.25 Protocol server started - Rev: 3.10 - 991201 Logical terminal area X25CNT: <#> Bytes

Explanation:: This message is logged to indicate that the ACC X.25 subsystem has been initialized. The message includes the revision code for the X.25 protocol driver and the expected size of the Logical Data Area used to hold X.25 link configuration and state information.
Action:: No action is necessary. This is an informational message.

zx25d 644 Link ZLU <#> X.25 shutdown initiated. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: This message is logged whenever the X.25 subsystem shuts down an X.25 link due to a user request. Typically this is through a call to zcntl to disable the X.25 link ZLU or using zmntr to shutdown the link.
Action:: No action is necessary. This is an informational message.

zx25d 645 Link ZLU <#> X.25 shutdown complete. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: This message is logged when the X.25 protocol driver completes the X.25 link shutdown processing as requested by a user. The X.25 link is no longer usable and will not respond to any protocol packets sent by the remote DXE.
Action:: No action is necessary. This is an informational message.

zx25d 646 Link ZLU <#>: Enable failed due to bad configuration! Either N2 = 0 and/or K = 0.

Explanation:: A user or application has attempted to bring an X.25 link up, but the link initialization has failed due to an illegal configuration. Specifically, either the level 2 window size (K) and/or the retransmission counter (N2) in the X.25 link ZLU's select word has been set to zero.
Action:: Correct the application or TTGEN configuration as necessary.

zx25d 647 Link ZLU <#>: Bad P(S) received on VC ZLU <#>. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: A data packet was received with an invalid sequence number in the P(S) field. In most cases this will cause the virtual circuit to be reset.
Action:: No action is necessary. This is an informational message.

zx25d 648 Link ZLU %<#>: Bad P(R) received on VC ZLU <#>. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: A data or flow control packet was received with an invalid sequence number in the P(R) field. In most cases this will cause the virtual circuit to be reset.
Action:: No action is necessary. This is an informational message.

zx25d 649 Link ZLU <#>: Reject pkt received on VC ZLU <#>. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: A Reject packet has been received on the indicated VC ZLU. This packet usually indicates that the remote DXE received an incorrect sequence number in a transmitted data packet. The Reject packet requests that a data packet be retransmitted. However, this implementation does not support retransmission of level 3 data packets and therefore a Reset Request will be issued on this VC.
Action:: No action is necessary. This is an informational message.

zx25d 650 Link ZLU <#>: VC control timeout on VC ZLU <#>.

Explanation:: This message indicates that the remote DXE has not responded to a protocol packet. During normal operating conditions, this message should never occur.
Action:: No action is necessary. This is an informational message.

zx25d 651 Link ZLU <#>: VC data acknowledgment timeout on ZLU <#>. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: This message indicates that the remote DXE has not acknowledged a transmitted data packet within the allowed amount of time (timer T25). This will cause the virtual circuit to be reset. Note that if the X.25 link has been configured not to use the T25 timer, this message will not occur.
Action:: No action is necessary. This is an informational message.

zx25d 652 Link ZLU <#>: VC RNR timeout on ZLU <#>. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: A remote DXE has returned an RNR flow control protocol packet in response to a transmitted data packet for a virtual circuit. An RNR packet mandates that no further data packets on this VC be transmitted to the DXE until an RR is received. The X.25 subsystem will allow this condition to exist for 120 seconds. If the remote DXE does not send an RR within this time frame, this message is logged and the VC will be reset.
Action:: No action is necessary. This is an informational message.

zx25d 653 Link ZLU <#>: MUX buffer shortage for VC ZLU <#>.

Explanation:: This message should never occur during normal operations. However, it generally indicates that the X.25 link has not been configured correctly and/or the application is not properly using X.25 subsystem with regard to the MUX card buffers.
Action:: No action is necessary. This is an informational message.

zx25d 654 Link ZLU <#>: Unauthorized interrupt confirm on VC ZLU <#>. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: This message is logged when an Interrupt Confirmation packet arrives for which no Interrupt packet had been sent. This generally indicates a protocol error in the remote DXE.
Action:: No action is necessary. This is an informational message.

zx25d 655 Link ZLU <#>: Interrupt pkt timeout on VC ZLU <#>. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: This message is logged if the T26 timer expires without having received an Interrupt Confirmation packet in response to a transmitted Interrupt packet. This generally indicates a protocol error in the remote DXE. This will cause the virtual circuit to be reset.
Action:: No action is necessary. This is an informational message.

zx25d 656 Link ZLU <#>: I, S, or Int packet too long on VC ZLU <#>. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: This message indicates a data packet was received that exceeded the configured X.25 level 3 packet size or an interrupt packet was received that was longer than 1-byte for 1980 links or 32-byte for 1984/88 links. This will cause the virtual circuit to be reset.
Action:: No action is necessary. This is an informational message.

zx25d 657 Link ZLU <#>: Inconsistent Q-bit usage on VC ZLU <#>. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: This message indicates that the inbound data packets in a complete packet sequence (message) did not ALL contain the same Q-bit value. This will cause the virtual circuit to be reset.
Action:: No action is necessary. This is an informational message.

zx25d 658 Link ZLU <#>: Invalid GFI received on VC ZLU <#>.

Explanation:: This message is logged when a protocol packet is received for a VC whose GFI field bits were illegal. Most likely the modulo 128 bit was set (bit 6). The ACC X.25 subsystem does not support modulo 128 sequence numbering. This will cause the virtual circuit to be reset or cleared as appropriate for the current state of the VC.
Action:: No action is necessary. This is an informational message.

zx25d 659 Link ZLU <#>: Illegal use of D-bit on VC ZLU <#>. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: For 1984 or later X.25 links, the D-bit in transmitted and/or received data packets may only be set if it has been negotiated at call setup time. For this VC, D-bit usage had not been successfully negotiated and a data packet was received that had the D-bit set. This will cause the virtual circuit to be reset.
Action:: No action is necessary. This is an informational message.

zx25d 660 Link ZLU <#>: Invalid short data packet on VC ZLU <#>. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: This message is logged when a data packet is received that has the M-bit set but whose length is less than the configured X.25 level 3 packet size. The virtual circuit will be reset as required by the ITU-T specification.
Action:: No action is necessary. This is an informational message.

zx25d 661 Link ZLU <#>: VC ZLU <#> being flushed.

Explanation:: This message indicates that a port break request has been issued. This message should never be seen during normal operations.
Action:: No action is necessary. This is an informational message.

zx25d 662 Link ZLU <#>: Packet too short on VC ZLU <#>. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: This message is logged when an X.25 data packet arrives that is less than four bytes and modulo 128 is being for this VC. The virtual circuit will be reset as required by the ITU-T specification.
Action:: No action is necessary. This is an informational message.

zx25d 663 Link ZLU <#>: Illegal interrupt packet on VC ZLU <#>. Mux= <#>, Port= <#>, Subchannel= <#>.

Explanation:: This message is logged when an interrupt packet is received and there is already an inbound unconfirmed interrupt packet pending. The virtual circuit will be reset as required by the ITU-T specification.
Action:: No action is necessary. This is an informational message.

zx25d 681 Link ZLU <#> reset due to a received Restart Indication. Cause = <#> Diagnostic = <#>

Explanation:: This message is logged whenever a Restart packet is received from the remote system on an X.25 link. The message contains the ZLU of the X.25 link that received the Restart as well as the Restart packet's cause and diagnostic codes. Note that this packet causes all SVCs to be disconnected.
Action:: No action is necessary. This is an informational message.

CLASS: Protocol 600-699

Technical documentation

» Table of Contents