CLASS: Normal 400-499

zx25d 400 X.25 link ZLU (<#>) is larger than zx25_max_zlu (<#>)! Increase the size of the kernel tunable zx25_max_zlu in /stand/system.

Explanation:: The system tunable zx25_max_zlu specifies the maximum value allowed for an X.25 ZLU. The default value for this parameter is 16,384. While initializing the specified link, it was determined that the X.25 link's ZLU number was larger than this value. The X.25 protocol driver is unable to initialize this X.25 link due to this error. The X.25 link will not be usable.
Action:: Increase the value of zx25_max_zlu in /stand/system and rebuild your system using mk_kernel.

zx25d 401 zset_rcvr() for ZLU <#> unexpectedly failed with error <#>.

Explanation:: The zset_rcvr routine is used to instruct the ZCOM subsystem to deliver all X.25 protocol status and data messages to the X.25 Protocol driver event handler routine. This routine has unexpectedly failed. This is a serious error which will prevent the X.25 driver from initializing the indicated X.25 link ZLU. The X.25 link ZLU has been marked as unusable. There are no known causes for this failure.
Action:: Check the error returned against those listed in this guide and take corrective action as necessary. If the problem persists and you are unable to determine its cause or the error code indicates a probable internal defect, contact your HP support representative.

zx25d 402 zltstore() for ZLU <#> unexpectedly failed with error <#>.

Explanation:

The zltstore routine is used to find the offset of the X.25 configuration information within the Logical Terminal Table. This routine has unexpectedly failed. This is a serious error which will prevent the X.25 driver from initializing the indicated X.25 link ZLU since the driver is unable to find the configuration information. The X.25 link ZLU has been marked as unusable. This routine could fail if the TTGEN configuration file did not contain the following statement, exactly as shown, in the global parameters area:

Logical-Data 10 X25CNT,0, X25CNT_LDSIZE

Action:

Check the error returned against those listed in this guide and take corrective action as necessary. If the problem persists and you are unable to determine its cause or the error code indicates a probable internal defect, contact your HP support representative.

zx25d 403 Unable to allocate system memory for X.25 link ZLU <#>.

Explanation:: When the ACC X.25 subsystem tries to initialize an X.25 link for the first time, it dynamically allocates a data structure to hold link related information by calling the HP-UX kernel routine MALLOC(). This routine was unable to allocate the required amount of memory. This is a serious error which will prevent the X.25 driver from initializing the indicated X.25 link ZLU.
Action:: Check your system configuration to insure that you have sufficient memory available and that your swap space is large enough. If the problem persists and you are unable to determine its cause, contact your HP support representative.

zx25d 404 The zcntl() to enable the X.25 link ZLU <#> unexpectedly failed with error <#>.

Explanation:: If the X.25 link configuration does not specify no_autostart, the X.25 driver will automatically try to bring the X.25 link up by issuing an zcntl call to enable the X.25 link ZLU. This routine has unexpectedly failed. This X.25 link is usable, but you will need to manually enable it using the zmntr utility.
Action:: Check the error returned against those listed in this guide and take corrective action as necessary. If the problem persists and you are unable to determine its cause or the error code indicates a probable internal defect, contact your HP support representative.

zx25d 405 The zcntl() to activate the X.25 link ZLU <#> unexpectedly failed with error <#>.

Explanation:: If the X.25 link configuration does not specify no_autostart, the X.25 driver will automatically try to bring the X.25 link up by issuing an zcntl call to enable the X.25 link ZLU and immediately follow this with a zcntl call to activate the X.25 link. The activate request has unexpectedly failed. This X.25 link is usable, but you may need to manually activate it using one of the ZCOM utility programs.
Action:: Check the error returned against those listed in this guide and take corrective action as necessary. If the problem persists and you are unable to determine its cause or the error code indicates a probable internal defect, contact your HP support representative.

zx25d 406 The zcntl() to retrieve firmware revision codes for the X.25 link ZLU <#> unexpectedly failed with error <#>.

Explanation:: When an X.25 link is initialized for the first time, the X.25 protocol driver issues a zcntl() control write request to retrieve the version codes of the X.25 and HDLC/LAP-B firmware to determine if the driver is compatible with the version of firmware being used by the MUX card. This request has unexpectedly failed. The MUX will be assumed to be running with compatible firmware. This error should have no impact on the operation of this X.25 link.
Action:: Check the error returned against those listed in this guide and take corrective action as necessary. If the problem persists and you are unable to determine its cause or the error code indicates a probable internal defect, contact your HP support representative.

zx25d 407 The zcntl() to configure the X.25 link ZLU <#>'s timers (T1, T2, T3/T4) has unexpectedly failed with error <#>.

Explanation:: When the X.25 driver receives notification that X.25 at level 2 (HDLC/LAP-B) has been established, it issues a request to set the X.25 level 2 protocol timer values. It issues a zcntl() control write request to set the T1, T2, and T3/T4 timer values with the indicated error. The X.25 driver will ignore this error and continue to attempt to bring the link up. Note: If abnormal behavior is observed on the link, the X.25 link should be shutdown and re-initialized.
Action:: Check the error returned against those listed in this guide and take corrective action as necessary. If the problem persists and you are unable to determine its cause or the error code indicates a probable internal defect, contact your HP support representative.

zx25d 408 The zcntl() control write (type <#>) to the X.25 link ZLU <#> has unexpectedly failed with error <#>.

Explanation:: The primary mechanism used by the X.25 Protocol driver to establish the X.25 packet layer and for managing VC Call Request, Clears, and Resets is through special Control Write requests issued to the X.25 firmware. A control write request is performed using the zcntl() routine. One of these request has unexpectedly failed. This may be a normal condition, for example, in the case where the link is disconnected right as a call is being placed. The type value indicates the type of control write request issued and is displayed for internal support purposes.
Action:: Check the error returned against those listed in this guide and take corrective action as necessary. If the problem persists and you are unable to determine its cause or the error code indicates a probable internal defect, contact your HP support representative.

zx25d 409 The zread on ZLU <#> has unexpectedly failed with error <#>.

Explanation:: The X.25 protocol's event handler routine was entered to indicate that status message or protocol packet has arrived. However, when the driver issued a zread call to retrieve the event, the routine unexpectedly failed. The zread request will be retried. If three consecutive zread calls fail, the X.25 subsystem is disabled by the driver.
Action:: Check the error returned against those listed in this guide and take corrective action as necessary. If the problem persists and you are unable to determine its cause or the error code indicates a probable internal defect, contact your HP support representative.

zx25d 410 The zcntl() on ZLU <#> to disable the X.25 link has unexpectedly failed with error <#>.

Explanation:: During the normal processing of an X.25 link disable request (the user disabled the X.25 link ZLU), the driver is required to reissue the disable after the link has been fully brought down. This causes the ZLU disabled unsolicited status message to be delivered to the application program. This request has unexpectedly failed. This may result in the application not receiving the X.25 Link ZLU disabled status.
Action:: Check the error returned against those listed in this guide and take corrective action as necessary. If the problem persists and you are unable to determine its cause or the error code indicates a probable internal defect, contact your HP support representative.

zx25d 411 The zsend (type <#>) to the X.25 link ZLU <#> has unexpectedly failed with error <#>.

Explanation:

The ZCOM API routine zsend to the specified ZLU has unexpectedly failed due to the indicated ZCOM error. This routine is used to send X.25 protocol packets on the link. For example, sending a clear packet in response to any packet received on an unassigned logical channel. It is possible for this failure to occur under normal conditions such as a link disconnect right as the zsend is being issued. The type parameter in the message indicates the type of protocol packet being sent as follows:

type 14 = Restart Confirmed packet
type 19 = Clear/Reset for abnormal packet
type 20 = Enable PVC
type 21 = Call Accepted packet
type 22 = Reply to application request
          (e.g. zx25... call)
type 24 = Diagnostic Packet

Action:

zx25d 412 The zsend() of unsolicited status failed with error <#>. Src ZLU = <#>, Dest ZLU = <#>, Status = <#>.

Explanation:: Unsolicited status message numbers 64 through 85 and 110 through 128 are generated by the X.25 protocol driver. These status messages are sent to all applications that have set themselves up as receivers on the VC ZLUs or have called the zx25l2stat_rcvr() routine. The X.25 Protocol driver uses the zsend routine to pass these status messages to the appropriate applications. This routine has unexpectedly failed. This may have a severe consequence for the application depending on the particular status and use made of it by the application. The Src ZLU parameter is the VC or X.25 Link ZLU associated with the status message. The Dest ZLU is the application's program ZLU that the message was being queued on. The Status parameter is the specific unsolicited status code that was being send. See Appendix A for more information on unsolicited status messages and a list of the different status codes.
Action:: Check the error returned against those listed in this guide and take corrective action as necessary. If the problem persists and you are unable to determine its cause or the error code indicates a probable internal defect, contact your HP support representative.

zx25d 413 Zc_zlumapt() of X.25 Link ZLU <#> failed with error <#>.

Explanation:: The Zc_zlumapt is used to determine if the X.25 link ZLU has been mapped to another ZCOM ZLU and to make sure that the target mapped ZLU is a terminal ZLU. This routine has unexpectedly failed. Most likely this is due to an application programming error. That is, the X.25 link ZLU was incorrectly mapped to another ZCOM ZLU.
Action:: Check the error returned against those listed in this guide and correct the application program.

zx25d 414 Zc_zlumapt() of X.25 VC ZLU <#> failed with error <#>.

Explanation:: The Zc_zlumapt is used to determine if the X.25 Virtual Circuit ZLU has been mapped to another ZCOM ZLU and to make sure that the target mapped ZLU is a terminal ZLU. This routine has unexpectedly failed. Most likely this is due to an application programming error. That is, the X.25 VC ZLU was incorrectly mapped to another ZCOM ZLU.
Action:: Check the error returned against those listed in this guide and correct the application program.

zx25d 415 There are more PVCs subscribed to (<#>) than configured (<#>) for the X.25 Link ZLU <#>.

Explanation:: The X.25 link ZLU indicated did not have enough PVC ZLUs defined to fulfil the X.25 subscription (last_pvc). This may cause operational errors as some of the subscribed PVC Logical Channels will not be usable. If a packet arrives on an unusable PVC, the X.25 driver will automatically generate a Reset Request.
Action:: Correct the X.25 configuration. You may either change the last_pvc parameter for the X.25 link ZLU or add more PVC Term entries to the TTGEN configuration file.

zx25d 416 There are more two-way SVCs subscribed to (<#>) than configured (<#>) for the X.25 Link ZLU <#>.

Explanation:: The X.25 link ZLU indicated did not have enough two-way outgoing SVC ZLUs defined to fulfil the X.25 subscription (first_outsvc and last_outsvc). This may cause operational errors as the network may attempt to establish more calls than you have available Virtual Circuits to accept them on. If this should occur, the inbound call will automatically be cleared with an appropriate error. In addition, your application will not have as many outgoing SVCs as expected.
Action:: Correct the X.25 configuration. You may either change the first_svc and last_svc parameters for the X.25 link ZLU or add more two-way SVC Term entries to the TTGEN configuration file.

zx25d 417 There are more one-way incoming SVCs subscribed to (<#>) than configured (<#>) for the X.25 Link ZLU <#>.

Explanation:: The X.25 link ZLU indicated did not have enough two-way outgoing SVC ZLUs defined to fulfil the X.25 subscription (first_outsvc and last_outsvc). This may cause operational errors as the network may attempt to establish more calls than you have available Virtual Circuits to accept them on. If this should occur, the inbound call will automatically be cleared with an appropriate error.
Action:: Correct the X.25 configuration. You may either change the first_insvc and last_insvc parameters for the X.25 link ZLU or add more one-way incoming SVC Term entries to the TTGEN configuration file.

zx25d 418 There are more one-way outgoing SVCs subscribed to (<#>) than configured (<#>) for the X.25 Link ZLU <#>.

Explanation:: The X.25 link ZLU indicated did not have enough one-way outgoing SVC ZLUs defined to fulfil the X.25 subscription (first_outsvc and last_outsvc). This may cause operational errors as your application will not have as many outgoing SVCs as expected.
Action:: Correct the X.25 configuration. You may either change the first_outsvc and last_outsvc parameters for the X.25 link ZLU or add more one-way outgoing SVC Term entries to the TTGEN configuration file.

zx25d 419 Inbound call arrived on PVC LCN <#> for Link ZLU <#>. The inbound call has been cleared.

Explanation:: An Incoming CALL packet has arrived on a Logical Channel Number that the subscription parameters have specified as a PVC. This is due to a mis-match in the subscription parameters configured for the DTE and DCE. These parameters must agree exactly.
Action:: Correct either the DTE or DCE's X.25 subscription parameters.

zx25d 420 Inbound call arrived on one-way outgoing SVC (LCN <#>) for Link ZLU <#>. The inbound call has been cleared.

Explanation:: An Incoming CALL packet has arrived on a Logical Channel Number that the subscription parameters have specified as a one-way outgoing SVC. That is, the Logical Channel used in the CALL packet is only allowed to place an outbound CALL request. The inbound call has automatically been cleared. This is due to a mis-match in the subscription parameters configured for the DTE and DCE. These parameters must agree exactly.
Action:: Correct either the DTE or DCE's X.25 subscription parameters.

zx25d 421 No available (idle) ZLUs for inbound call. The inbound call has been cleared.

Explanation:: An Incoming CALL packet has arrived but there are no SVC ZLUs available to handle it. For an SVC to be available, it must be defined, enabled, configured to accept inbound calls and must be in the "idle" state. In addition, the SVC may not be available if it has been configured to only accept calls from a specific X.121 address. The inbound call has automatically been cleared with an appropriate diagnostic code.
Action:: No action is necessary. This is an informational message, however, you may want to increase the number of SVCs for inbound call in your X.25 subscription.

zx25d 422 Inbound call on LCN <#> specified Restricted Fast-Select. Unable to accept call on link ZLU <#>; call cleared.

Explanation:: An Incoming CALL packet has arrived that specified the facility Restricted Fast-Select on a ZLU that is configured to automatically accept all inbound calls. This facility does not allow the call to be accepted. The inbound call has automatically been cleared as required by this facility.
Action:: No action is necessary. This is an informational message.

zx25d 423 There are no VCs defined on the X.25 Link ZLU <#>!

Explanation:: An attempt was made to startup (enable) an X.25 link ZLU that does not have any virtual circuits configured on it.
Action:: Correct your TTGEN configuration file or if you are dynamically creating the VC ZLUs, correct your application. The X.25 link can not be used until the configuration is corrected.

zx25d 424 Link <#>: Unknown L2 state (<#>) for event <#>! Notify your HP support representative.

Explanation:: An X.25 protocol event occurred on the indicated X.25 link ZLU. However, when the X.25 protocol driver attempted to process the event, the link state variable contained an unknown state value. This probably indicates that the data structure for the X.25 link has been corrupted.
Action:: This is an internal defect. Contact your HP support personal.

zx25d 425 Link <#>: Call request timed out on SVC ZLU <#>!

Explanation:: An outbound Call Request packet was transmitted, however the remote DXE did not respond with a CALL Connected or CLEAR Indication packet within the time allowed (Timer T11 or T21). A CLEAR Request packet has automatically been transmitted.
Action:: Check the remote DXE and correct any problems found.

zx25d 426 Link <#>: Application timeout for inb. call on ZLU <#>!

Explanation:: An Incoming CALL packet arrived on a ZLU that was configured for Application inbound call acknowledgment required. However, the application did not accept or clear the call within the allowed amount of time (40-50 seconds). A CLEAR Request packet has automatically been transmitted. Note that this message may appear in rare cases where the CPU is put under extreme loads. If this is a frequent problem and the application has been correctly coded, you may need to upgrade to a higher performance processor.
Action:: Correct the application program or modify the configuration to allow the X.25 protocol driver to automatically accept inbound calls.

zx25d 427 Link <#>: Reset request timed out on VC ZLU <#>!

Explanation:: An outbound Reset Request packet was transmitted, however the remote DXE did not respond with a Reset Confirmation packet within the time allowed (Timer T12 or T22). The Reset Request will be retransmitted unless R22 has been exceeded.
Action:: Check the remote DXE and correct any problems found.

zx25d 428 Link <#>: Application timeout for inb. reset on ZLU <#>!

Explanation:: An Incoming RESET packet arrived on a ZLU that was configured for Application Reset Confirmation required. However, the application did not confirm the reset (using zx25reset_conf) within the allowed amount of time (40-50 seconds). A Reset Confirmation packet has automatically been transmitted. Note that this message may appear in rare cases where the CPU is put under extreme loads. If this is a frequent problem and the application has been correctly coded, you may need to upgrade to a higher performance processor or your application may need to run at a real-time priority.
Action:: Correct the application program or modify the configuration to allow the X.25 protocol driver to automatically confirm inbound resets.

zx25d 429 Link <#>: Clear request timed out for SVC ZLU <#>!

Explanation:: An outbound Clear Request packet was transmitted, however the remote DXE did not respond with a Clear Confirmation packet within the time allowed (Timer T13 or T23). The Clear Request will be retransmitted unless R23 has been exceeded.
Action:: Check the remote DXE and correct any problems found.

zx25d 430 Link <#>: Timeout for ZLU <#> in inconsistent state <#>.

Explanation:: A VC protocol timeout event occurred on a VC ZLU that is in a state that should never receive a timeout.
Action:: In most cases, this message can be ignored. However, if this message is frequently logged or abnormal behavior is observed, you should contact your HP support personnel.

zx25d 431 Link <#>: Reset retry counter (R22) exceeded for ZLU <#>! For SVCs, the call has been cleared.

Explanation:: An outbound Reset Request packet was retransmitted, however the remote DXE is not responding with a Reset Confirmation packet within the time allowed (Timer T13 or T23) and the Reset Request retransmit counter R22 was exceeded. The X.25 driver will automatically issue a Clear Request if this VC is an SVC. Otherwise, the PVC will be put into the Data Transfer Ready state.
Action:: Check the remote DXE and correct any problems found.

zx25d 432 Link <#>: Clear request retry counter (R23) exceeded for ZLU <#>! SVC being forced into the "idle" state.

Explanation:: An outbound Clear Request packet was retransmitted, however the remote DXE is not responding with a Clear Confirmation packet within the time allowed (Timer T13 or T23) and the Clear Request retransmit counter R23 was exceeded. The X.25 driver is assuming that the call is cleared and has put the ZLU into the "idle" state. A ZLU in the idle state is allowed to place outbound calls or accept inbound calls, if configured to do so.
Action:: Check the remote DXE and correct any problems found.

zx25d 433 Link <#>: Too many X.25 links defined. Link ignored!

Explanation:: More X.25 link ZLUs have been defined than the X.25 Protocol driver has table space for. This is currently 512 X.25 links. Note that although you may configure up to 512 X.25 links, only 128 links are supported.
Action:: Correct your X.25 configuration.

zx25d 434 Link <#>: Unexpected pkt (type=<#>) for ZLU <#> state <#>. Call cleared or VC Reset has been issued.

Explanation:

This message indicates that the DXE has transmitted an X.25 level 3 protocol packet that is invalid for the current state of the VC. For example, if the local DTE sent a legal Call Request packet and the DCE responded with a Data packet, the Data packet is invalid for the DTE's state. The only valid packets are a Call Connected or Clear Indication packet. This message indicates that the remote DXE is violating the ITU-T X.25 protocol. A Clear or Reset Request will automatically be sent as appropriate for the VC type and current state. The packet type and state values are as follows:

type 44 = Data packet	type 46 = RNR packet
type 45 = Reject packet	type 47 = RR packet
state 2 = Enabled	state 3 = Idle
state 4 = Clear Recovery	state 5 = Clear Request
state 6 = DXE Clear Ind	state 7 = Call Request
state 8 = DXE Call Ind	state 9 = Call Collision
state 10 = Data Xfer Ready	state 11 = Reset Request
state 12 = DXE Reset Ind	state 13 = Abnormal Clear

Action:

No action is necessary. This is an informational message. However, it may indicate a problem with the remote DXE.

zx25d 435 Link <#>: VC enabled status received for term <#>, but no ZLU is associated with it. Probable F/W failure.

Explanation:: The X.25 Protocol driver received a VC enabled unsolicited status message, however, there was no associated VC ZLU for the indicated MUX terminal number. This most likely means there is a defect in the MUX firmware.
Action:: In most cases, this message can be ignored. However, if this message is frequently logged or abnormal behavior is observed, you should contact your HP support personnel.

zx25d 436 Link <#>: VC disabled status received for term <#>, but no ZLU is associated with it. Probable F/W failure.

Explanation:: The X.25 Protocol driver received a VC disabled unsolicited status message, however, there was no associated VC ZLU for the indicated MUX terminal number. This most likely means there is a defect in the MUX firmware.
Action:: In most cases, this message can be ignored. However, if this message is frequently logged or abnormal behavior is observed, you should contact your HP support personnel.

zx25d 437 Link <#>: No ZLU associated with Term #<#> on write completion! Probable driver defect.

Explanation:: The X.25 Protocol driver received a Control Write completion status message, however, there was no associated VC ZLU for the indicated MUX terminal number. This most likely means there is a defect in the ZCOM or X.25 driver software.
Action:: If this message is frequently logged or abnormal behavior is observed, you should contact your HP support personnel.

zx25d 438 Link <#>: Control write (type = <#>) failed with error <#>!

Explanation:: The primary mechanism used by the X.25 Protocol driver to manage VC Call Request, Clears, and Resets is through special Control Write requests issued to the X.25 firmware. A control write request is performed using the zcntl() routine. The completion status returned by the X.25 firmware for one of these requests has indicated an unexpected failure. This may be a normal condition, for example, in the case where the link is disconnected right as a call is being placed. The type value indicates the type of control write request issued and is displayed for internal support purposes. PVCs are automatically reset while SVCs are cleared.
Action:: Check the error returned against those listed in this guide and take corrective action as necessary. If the problem persists and you are unable to determine its cause or the error code indicates a probable internal defect, contact your HP support representative.

zx25d 439 Link <#>: Write request (type = <#>) failed with error <#>! Virtual Circuit will be reset or cleared.

Explanation:

The buffer completion status for a zsend request to the specified ZLU has unexpectedly failed due to the indicated error. This routine is used to send X.25 protocol packets on the link. For example, sending a clear packet in response to any packet received on an unassigned logical channel. It is possible for this failure to occur under normal conditions such as a link disconnect right as the zsend is being issued. The type parameter in the message indicates the type of protocol packet being sent as follows:

type 14 = Restart Confirmed packet
type 19 = Clear/Reset for abnormal packet
type 20 = Enable PVC
type 21 = Call Accepted packet
type 22 = Reply to application request (e.g. zx25... call)
type 24 = Diagnostic Packet

Action:

zx25d 440 Link <#>: Too many PVCs (<#>) subscribed to! Unable to initialize X.25 link.

Explanation:: The TTGEN configuration file specified a PVC subscription value that was too large. The maximum number of PVCs allowed is 254.
Action:: Correct the X.25 configuration.

zx25d 441 Link <#>: Illegal LCI value in channel assignment table (> 4095)! Unable to initialize X.25 link.

Explanation:: The X.25 subscription parameters for the indicated X.25 link ZLU specified a Logical Channel Number greater than 4095. ITU-T does not allow Logical Channel numbers greater than 4095 to be used.
Action:: Correct the X.25 configuration.

zx25d 442 Link <#>: Illegal one-way incoming SVC channel assignment! The LIC value (<#>) is greater than the HIC value (<#>).

Explanation:: The X.25 subscription for one-way incoming SVCs did not specify a legal Logical Channel Number assignment.
Action:: Correct the X.25 configuration.

zx25d 443 Link <#>: Illegal two-way SVC channel assignment! The LIC value (<#>) is greater than the HIC value (<#>).

Explanation:: The X.25 subscription for two-way SVCs did not specify a legal Logical Channel Number assignment.
Action:: Correct the X.25 configuration.

zx25d 444 Link <#>: Illegal one-way outgoing SVC channel assignment! The LIC value (<#>) is greater than the HIC value (<#>).

Explanation:: The X.25 subscription for one-way outgoing SVCs did not specify a legal Logical Channel Number assignment.
Action:: Correct the X.25 configuration.

zx25d 445 Link <#>: Overlap in LCI assignment OR LCI values not ordered correctly (e.g. PVC < SVC IN < SVC IO < SVC OUT)!

Explanation:: During validation of the logical channel assignment table, the X.25 driver detected either an overlap in the logical channel numbers or LCNs not specific in the correct order (numerically). Note the all PVC LCNs must be less then the one-way incoming SVC LCNs, which must be less than the two-way SVC LCNs, which must be less than the one-way outgoing SVC LCNs, which must be less than 4096.
Action:: Correct the X.25 configuration.

zx25d 446 Link <#>: Too many Virtual Circuits (<#>) subscribed to! Unable to initialize X.25 link.

Explanation:: The X.25 subscription has specified more than 254 Virtual Circuits for an X.25 link on an 2/8-channel card or 1023 VCs on a 4-channel E1/T1 card.
Action:: Correct the X.25 configuration.

zx25d 447 VC ZLU (<#>) is larger than zx25_max_zlu (<#>)! Increase the size of the kernel tunable zx25_max_zlu in /stand/system. The VC ZLU has been ignored.

Explanation:: The system tunable zx25_max_zlu specifies the maximum value allowed for an X.25 ZLU. The default value for this parameter is 16,384. While initializing the specified link, it was determined that the X.25 VC's ZLU number was larger than this value. The X.25 protocol driver ignores this VC ZLU. The X.25 link can be used with those VCs that have been successfully initialized.
Action:: Increase the value of zx25_max_zlu in /stand/system and rebuild your system using mk_kernel.

zx25d 448 X.25 link ZLU (<#>) is larger than zx25_max_zlu (<#>)! Increase the size of the kernel tunable zx25_max_zlu in /stand/system. Unable to dynamically configure link!

Explanation:: The system tunable zx25_max_zlu specifies the maximum value allowed for an X.25 ZLU. The default value for this parameter is 16,384. While initializing the specified link, it was determined that the X.25 link's ZLU number was larger than this value. The X.25 protocol driver is unable to initialize this X.25 link due to this error. The X.25 link will not be usable.
Action:: Increase the value of zx25_max_zlu in /stand/system and rebuild your system using mk_kernel.

CLASS: Normal 400-499

Technical documentation

» Table of Contents