NLI2ZCOM (N2Z) Driver Messages

Explanation: When x25init is run, the N2Z driver scans through all of the ZLUs defined in the TTGEN configuration and looks for X.25 line ZLUs (Level 2) and their associated virtual circuit ZLUs (Level 3) using the ZCOM routine zinfo(). However this call has unexpectedly returned an error preventing the N2Z driver from acquiring the information needed to start up an X.25 line.

Action: Check the error returned by the zinfo call against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: While attempting to establish a communication path to the ZCOM subsystem, an unexpected error occurred. The previous error message logged gives the particular ZCOM call that failed and the specific reason for the failure.

Action: Consult the previous error message containing the reason for the failure and take corrective action as necessary.

Explanation: For most requests issued by the N2Z driver to the ZCOM subsystem, a valid ZCOM checksum value is required for the ZLU affected by the request. This value is assigned to each ZLU when ZCOM is started. During initialization the N2Z driver attempts to retrieve the checksum value of all ZLUs associated with an X.25 line. This operation has unexpectedly failed preventing the N2Z driver from bringing the X.25 line up.

Action: Check the error returned by the zinfo call against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: x25init was run without first successfully starting the ZCOM subsystem. You should run zmasterd cold <configuration file>.

Action: Issue commands to start up the ZCOM subsystem before running x25init. ZMON must be executed first followed by zx25d_init. Examine the ZCOM message log file to verify that ZCOM has been successfully started. For example:

zmasterd cold /opt/acc/cfg/x25.tmem

Explanation: Before the N2Z driver is allowed to issue any request to the ZCOM subsystem it must first successfully issue a ZCOM zinit() call. This routine has unexpectedly returned an error. This may be due to an internal defect in the product.

Action: Check the error returned by the zinit call against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: During the N2Z driver initialization, it issues a zopen call to allocate a program ZLU on which it will receive inbound data and unsolicited event status. The call unexpectedly returned an error. Without this program ZLU the N2Z driver is unable to communicate with the ZCOM subsystem drivers and is therefore unable to bring up the X.25 line. This may be due to an internal defect in the product.

Action: Check the error returned by the zopen call against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: During the processing of an outbound SVC Clear Request, the driver was unable to allocate a ZCOM message buffer to send the Clear Request to the ACC card. The driver has reset the X.25 link.

Action: The usual cause for this condition is defining a ZCOM buffer-pool that is too small for the X.25 traffic loads used in the customer's application environment. Increase the size of the kernel tunable zcom_mem_size in /stand/system (adding it if necessary) and rebuild your kernel.

Explanation: The zsetkfunc call is used by the N2Z driver to tell ZCOM which subroutine to call to pass data and unsolicited status events to the N2Z driver. This call has unexpectedly failed. The N2Z driver is therefore unable to communicate with the ZCOM subsystem. This may be due to an internal defect in the product.

Action: Check the error returned by the zsetkfunc call against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: The zinfo call is used by the N2Z driver when x25init is run to find all virtual circuit ZLUs associated with the desired X.25 line. This call has unexpectedly failed which prevents the N2Z driver from determining which L3 ZLUs to use. The N2Z driver will be unable to bring the X.25 line up without this information. This may be due to an internal defect in the product.

Action: Check the error returned by the zsetkfunc call against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: The driver has been notified that the Streams X.25 subsystem has been shutdown, typically by executing "x25stop -K". The driver has issued Clear Requests on all active SVCs and has then shutdown and deallocated all X.25 links.

Action: No action is necessary. This message is for informational purposes.

Explanation: The N2Z driver while attempting to initialize an X.25 link detected two X.25 link ZLUs defined for the same MUX and Port (and Subchannel) number. Only one X.25 link ZLU may be defined for any given MUX and Port.

Action: Correct the TTGEN configuration file, recompile it using TTGEN, and restart the ZCOM subsystem with the new configuration.

Explanation: The N2Z driver received a status message indicating that a user has shutdown the ZCOM subsystem. This has the effect of shutting down all of the X.25 physical links. The N2Z driver automatically shuts down all X.25 lines that are currently active which in turn will notify any applications using those X.25 lines.

Action: No action is necessary. When ZCOM is restarted (by running zmasterd), x25init must be executed again to bring up each X.25 line.

Explanation: The N2Z driver attempted to retrieve the ZCOM header table using the zinfo routine in order to get critical information such as the number of MUX cards currently configured, but the call unexpectedly failed with the indicated error code. The N2Z driver is unable to proceed with the initialization of an X.25 line without this information. This may be due to an internal defect in the product.

Action: Check the error returned by the zinfo call against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP support representative (if the error code indicates an internal defect) as necessary.

Explanation: The n2z_max_zlu kernel tunable parameter is used to specify the maximum value for an X.25 ZLU (L2 or L3) that will ever be defined in a ZCOM TTGEN configuration file. At least one ZLU in the ZCOM TTGEN configuration file currently being used has exceeded this value. Note that the nli2zcom driver dynamically creates ZLUs as needed. Make sure there are sufficient unused terminal entries to allow the nli2zcom driver to dynamically create them (one per VC and link). The ZCOM utility zmntr can be used to examine the VC and Link ZLUs.

Action: Modify the value of the kernel tunable n2z_max_zlu by adding it to the /stand/system file (if not already there) and increasing its value. It is recommended that you set its value to the same size as the Terminal-ZLU parameter in your current ZCOM ttgen configuration file. After modifying this tunable, you must rebuild your kernel using the mk_kernel utility.

Explanation: The MUX number specified in the minor number of the device file referenced by your x25init configuration file must be less the value of n2z_max_cards. Either the minor number of the device file is incorrect or the value of n2z_max_cards is too small.

Action: If the minor is incorrect, recreate the device file with the proper minor number (see Appendix D “Tuning and Sizing”). Otherwise, edit the file /stand/system and increase the value of n2z_max_cards to be greater than the largest MUX number reference in any of your x25init device files. After increasing this value, run mk_kernel, move the new kernel into place and reboot.

Explanation: The MUX number referenced in the device file used in your x25init configuration file has not been declared in the TTGEN configuration file used to start up the ZCOM subsystem.

Action: Either use a different device file in your x25init configuration file or change your TTGEN configuration file to include the specified MUX interface number.

Explanation: The MUX card referenced by your x25init configuration file either is not physically installed in the system (use ioscan to find out), has been programmatically disabled, or has experienced a hardware failure. The card status will be displayed in the message (ifstat). The status is represented as a bit field and is documented in the Interface Table section of the ACC Programmer's Reference Guide.

Action: Install or replace the hardware as necessary.

Explanation: This error is logged when x25init is run for a MUX port and/or subchannel number that is disabled (hardware failure) or has not been defined in the TTGEN configuration file used to start up the ZCOM subsystem.

Action: Make sure the port being referenced has a Port-Definition statement in the TTGEN configuration file. If this is an E1/T1 card, make sure the subchannel is defined. Make sure all of the ports were successfully initialized. If the ports all passed their self-test, the LED on the ACC MUX card will be green. If any of the ports have failed, the LED will be amber/yellow. You may need to replace the MUX card if any of the ports have experienced a hardware failure. As an alternative, you may change your x25init configuration file to reference a different MUX port and subchannel number.

Explanation: During a link shutdown, the ACC driver disables all of the VCs and waits for a “disabled status” to arrive on each before deallocating the resources associated with the link. However, one or more of the expected status indications did not arrive within the time allotted by the driver. Generally, this indicates a defect in the X.25 firmware.

Action: No action will be necessary if no further problems are observed. If additional problems are experienced, you should contact your HP representative.

Explanation: The tunable parameter n2z_max_devs is used to determine how many concurrent active streams may be open to the nli2zcom driver. This message is logged when an attempt is made to open a new stream to the nli2zcom driver and the maximum number of configured streams is already open.

Action: Increase the value of the tunable parameter n2z_max_devs in /stand/system and rebuild your HP-UX system.

Explanation: A request was made to start-up another X.25 link but the maximum number of X.25 links supported by the ACC product have already been initialized and are in use. In order to add another link, you must first run x25stop on one or more X.25 links. The maximum number of allowed links is logged in the error message.

Action: None, this is an informational message.

Explanation: A request was made to start-up an X.25 link on a card, port, and subchannel that has already had an X.25 link initialized on it. This is an internal defect.

Action: Contact your HP support representative.

Explanation: The ZCOM implementation of the X.25 protocol only supports the level 3 packet sizes listed above. However, the configuration file supplied to x25init did not use one of the supported packet size values for the “def_inpacket[size]” and/or “def_outpacket[size]” parameters.

Action: Correct your x25init configuration file and rerun x25init.

Explanation: The ZCOM implementation of the X.25 protocol only supports the level 3 PVC packet sizes listed above. However, the configuration file supplied to x25init did not use one of the supported packet size values for the “pvc_inpacket[size]” and/or “pvc_outpacket[size]” parameters.

Action: Correct your x25init configuration file and rerun x25init.

Explanation: The N2Z driver issued a call to zinfo to retrieve information it needed to properly setup the indicated ZLU. This call has unexpectedly failed which prevents the N2Z driver from bringing the X.25 line up.

Action: Check the error returned by the zinfo call against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: The N2Z driver issued a ZCOM zcntl call to configure the ZLUs poll word, select word and option byte, but the call unexpectedly failed. This call is used to configure the PVC packet and window sizes, end-to-end acknowledgment, and other critical internal parameters. The N2Z driver cannot bring up the X.25 line without being able to successfully issue this call.

Action: Check the error returned by the zinfo call against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: The N2Z driver issued a ZCOM zinfo call to retrieve the contents of the Logical Terminal Table for an X.25 line ZLU. However, this call unexpectedly failed. The ZCOM Logical Terminal Table contains configuration information such as the number of PVCs, the default SVC window and packet sizes, etc. This area is also used to maintain runtime statistics on an X.25 line. This routine is called whenever x25stat or x25init is executed. Since this routine failed, the operation will be rejected with an “ENETDOWN” error.

Action: Check the error returned by the zinfo call against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: The N2Z driver issued a ZCOM zltstore call to retrieve the address of the Logical Terminal Table area containing configuration and statistics information for an X.25 line ZLU, however, this call unexpectedly failed. This routine is called whenever x25init or x25stat is run. This failure will cause the operation to be rejected with an “ENETDOWN” error.

Action: Check the error returned by the zinfo call against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: The ZCOM zcntl function call to enable a ZLU has unexpectedly failed. This means that the indicated ZLU can neither receive nor place outgoing calls.

Action: Check the error returned by the zcntl call against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: The N2Z driver called the ZCOM routine zltup() to configure various X.25 parameters related to the X.25 line and SVCs. This call has unexpectedly failed which prevents the N2Z driver from successfully configuring and initializing this X.25 line. This call may have failed for any number of reasons including a hardware failure in the Mux card, an operator shutting down ZCOM, or a software defect.

Action: Check the error returned by the zltup call against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: As part of initializing an X.25 line, the N2Z driver issues an ACC X.25 function call to instruct the X.25 subsystem to send level 2 state changes to the N2Z driver asynchronously. This X.25 function call has unexpectedly failed. The N2Z driver cannot operate correctly without this state change information and therefore the X.25 line will NOT be brought up.

Action: Check the error returned against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: The zcntl Activate request is part of the data flow control between the ACC Mux card and N2Z driver. Specifically this request is used to tell the Mux card firmware that it may begin to accept inbound data from a specific established virtual circuit. This request has unexpectedly failed and may have severe consequences for the affected virtual circuit, as the X.25 firmware will continue to reject any inbound data packets with an RNR packet. During normal operations there are no known reasons for this failure.

Action: Check the error returned against those listed in the ZCOM Error Codes chapter of the ACC Error 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.

Explanation: A shutdown request was issued and the N2Z driver has brought down the selected X.25 line ZLU and all virtual circuit ZLUs associated with the line and then waited for the X.25 line down status to arrive. However, this state change did not arrive within the tunable timeout period. This may indicate a serious problem in the ACC X.25 firmware or ZCOM subsystem, but might also be caused by the remote side taking an inordinately long time to bring the link down. Note that the default timeout value is 90 seconds. The X.25 specification indicates that the time to actually shutdown the link is well over 3 minutes.

Action: No action will be necessary if no further problems are observed. If additional problems are experienced, you should examine the problem in detail. There are many reasons why a timeout could occur. Examples include failure of the ACC Mux card, an unresponsive remote DTE, a timeout value which is too short, or an internal software defect. The N2Z driver is unable to determine the specific cause. All components of the data communication path should be checked for physical integrity and normal operation. Try increasing the L2 timeout value (n2z_link_timeout parameter in /stand/system). If the problem persists contact your HP representative.

Explanation: The zcntl Deactivate request is part of the data flow control between the ACC Mux card and N2Z driver. Specifically this request is used to tell the Mux card firmware that it must stop accepting inbound data from a specific established virtual circuit. Typically this request is issued whenever an application is not reading its inbound data faster than the data is arriving, and the driver is running low on buffers to store the inbound data. This request has unexpectedly failed and may have severe consequences for the affected virtual circuit, as the X.25 firmware will continue to accept inbound data packets which may consume all available data buffers in the N2Z driver, causing the inbound data to be lost. During normal operations there are no known reasons for this failure.

Action: Check the error returned against those listed in the ZCOM Error Codes chapter of the ACC Error 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.

Explanation: The N2Z driver was entered in a request to send expedited data on a virtual circuit. ZCOM uses the zcntl function call with a Control Write request code for sending expedited data to a virtual circuit. The function call, however, has unexpectedly failed.

Action: Check the error returned against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: The nli2zcom driver issued a call to zconfig to deallocate all of the resources associated with the indicated ZLU in preparation for deallocating it. However, this call unexpectedly failed with the indicated error code. In most cases, this error can be safely ignored.

Action: Check the error returned against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: The nli2zcom driver issued a call to zconfig to deallocate the TERM entry associated with the indicated ZLU. However, this call unexpectedly failed with the indicated error code. In most cases, this error can be safely ignored.

Action: Check the error returned against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: The ZCOM subsystem has detected (at run-time) an invalid configuration for an X.25 line ZLU. The X.25 line is unusable until the configuration problem is corrected.

Action: Double check both the TTGEN configuration file and the x25init configuration file for consistency. If no problems are found and the problem persists, contact your HP representative.

Explanation: Unsolicited status has been received indicating a previous write request has failed. Note that this is a reasonably common error if a virtual circuit is shutdown without waiting for all outbound data to be successfully transferred to the remote system.

Action: Check the error returned against those listed in the ZCOM Status Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary. You should also check the Buffer Completion Statuses section of the X.25 Status and Completion Messages chapter.

Explanation: The N2Z driver was instructed to place on outgoing call on the indicated ZLU. It has called the X.25 function zx25callout(). However, this call has unexpectedly failed.

Action: Check the error returned against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and those listed at the beginning of this appendix and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: The N2Z driver received an indication that an incoming call has arrived and issued a request to the X.25 subsystem to acknowledge the incoming call. However, this request has experienced an unexpected error which prevented the N2Z driver from acknowledging the call.

Action: Check the error returned against those listed at the beginning of this appendix and take corrective action as necessary. If the problem persist and you are unable to determine its cause or the error code indicates a probable internal defect, contact your HP support representative.

Explanation: The N2Z driver called the ZCOM zsend() routine to transmit data across a virtual circuit but the routine has unexpectedly failed. This is a severe error and in most cases results in the loss of the outbound data. There are no known causes for this error during normal operations.

Action: Check the error returned against those listed in the ZCOM Error Codes chapter of the ACC Error 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.

Explanation: The N2Z driver calls the X.25 routine zx25callrej() whenever it needs to reject an incoming call or disconnect an established virtual circuit. However, this routine has returned an unexpected failure. The virtual circuit may or may not have been disconnected. There are no known causes for this failure during normal operations.

Action: Check the error returned against those listed at the beginning of this appendix 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.

Explanation: The N2Z driver calls the ZCOM X.25 routine zx25reset_conf() whenever it needs to confirm an inbound reset indication on an established virtual circuit. However, this routine has returned an unexpected failure. A reset confirmation packet may or may not have been sent. This error could be logged under normal conditions, if say for example, the link went down just as the reset confirm was being issued.

Action: Check the error returned against those listed at the beginning of this appendix 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.

Explanation: The ZCOM zset_rcvr routine is called by the N2Z driver to tell the ZCOM subsystem to send all status information and inbound data for the level 2 and virtual circuit ZLUs to the N2Z driver's inbound event handling routine. This routine has unexpectedly failed. This is a serious problem which will prevent the N2Z driver from bringing the X.25 line up. There are no known causes for this failure.

Action: Check the error returned against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and take corrective action as necessary. If the problem persist and you are unable to determine its cause or the error code indicates a probable internal defect, contact your HP support representative.

Explanation: Before the X.25 line ZLU can be brought up or a virtual circuit ZLU can place or accept a call, the ZLU must be placed into an “enabled” state. During an x25init operation the N2Z driver issues a ZCOM zcntl request to the X.25 line ZLU and all virtual circuit ZLUs to place them into an “enabled” state. One of these calls has unexpectedly failed. There are no known causes for this failure.

Action: Check the error returned against those listed in the ZCOM Error Codes chapter of the ACC Error 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.

Explanation: When x25init or x25stop is run, it causes the N2Z driver to issue a ZCOM zcntl function call to disable all virtual circuit ZLUs and the X.25 line ZLU. This causes all virtual circuits to be unconditionally disconnected and the X.25 link to be brought down. In addition, it puts the ZLUs into the correct state for reconfiguration in the case where x25init was run. During this operation one of the requests to disable a ZLU has unexpectedly failed. There are no known causes for this failure.

Action: Check the error returned against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and take corrective action as necessary. If the problem persist and you are unable to determine its cause or the error code indicates a probable internal defect, contact your HP support representative.

Explanation: Before the X.25 line ZLU can be brought up or a virtual circuit ZLU can place or accept a call, the ZLU must be placed into an "enabled" state. During an x25init operation the N2Z driver issues a ZCOM zcntl request to the X.25 line ZLU and all virtual circuit ZLUs to place them into an “enabled” state. One of these calls has unexpectedly failed. There are no known causes for this failure.

Action: Check the terminal status code returned against those listed in the ZCOM Status Codes chapter of the ACC Error 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.

Explanation: When x25init or x25stop is run, it causes the N2Z driver to issue a ZCOM zcntl function call to disable all virtual circuit ZLUs and the X.25 line ZLU. This causes all virtual circuits to be unconditionally disconnected and the X.25 link to be brought down. In addition, it puts the ZLUs into the correct state for reconfiguration in the case where x25init was run. During this operation one of the request to disable a ZLU has unexpectedly failed. There are no known causes for this failure.

Action: Check the terminal status code returned against those listed in the ZCOM Status Codes chapter of the ACC Error 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.

Explanation: The zcntl Activate request is part of the data flow control between the ACC Mux card and N2Z driver. Specifically this request is used to tell the Mux card firmware that it may begin to accept inbound data from a specific established virtual circuit. This request has unexpectedly failed and may have severe consequences for the affected virtual circuit, as the X.25 firmware will continue to reject any inbound data packets with an RNR packet. During normal operations there are no known reasons for this failure.

Action: Check the terminal status code returned against those listed in the ZCOM Status Codes chapter of the ACC Error 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.

Explanation: The X.25 specification (all years) mandates that the starting logical channel number for PVCs must begin with one. However, the N2Z driver detected an x25init configuration that specified a starting LCI value for PVCs other than one.

Action: Edit the x25init configuration file and change the starting “lci” parameter for PVCs. This must be set to “1”.

Action: This is an internal defect. Contact your HP support representative.

Explanation: The N2Z driver received a request to reset a virtual circuit. This is accomplished through the X.25 zx25reset() function call. This routine has unexpectedly failed. It is unknown whether the reset has been issued. There are no known causes for this failure.

Action: Check the error returned against those listed at the beginning of this appendix 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.

Action: This is an internal defect. Contact your HP support representative.

Explanation: An application has issued a request to send expedited data across a virtual circuit but the length of the expedited data was either illegal or too long for the network type specified in the x25init configuration file. For a 1980 type X.25 network, only 1 byte of expedited data may be sent. For a 1984 type X.25 network, up to 32 bytes of expedited data may be sent.

Action: Correct the application program or x25init configuration file as appropriate.

Explanation: An attempt was made to send expedited data before a previously sent expedited data packet had been confirmed. Normally, an application which has sent an expedited data packet would block until the expedited data confirmation arrived. However, if the application has requested non-blocking mode, the I/O request to send expedited data returns immediately. The application must wait for the expedited data confirmation to arrive (indicated through a out-of-band signal) before it sends another expedited data packet.

Action: Correct the application program.

Explanation: This message indicates that the ACC Mux X.25 firmware transmitted an HDLC Frame Reject (FRMR) frame. The FRMR frame is used by the secondary to report an error condition. It is always transmitted as a response to a command that has asked the secondary to perform some action that the secondary cannot do. This condition usually indicates a violation in the HDLC protocol and is probably due to an internal defect in the HDLC implementation of the DTE and/or DCE.

Action: If the problem persists, you should connect an HDLC protocol analyzer to the X.25 line and diagnose the problem. If the problem appears to be in the X.25/ACC product, contact your HP support representative.

Explanation: This message indicates that the X.25 line has received an HDLC Frame Reject (FRMR) frame. The FRMR frame is used by the secondary to report an error condition. It is always transmitted as a response to a command that has asked the secondary to perform some action that the secondary cannot do. This condition usually indicates a violation in the HDLC protocol and is probably due to an internal defect in the HDLC implementation of the DTE and/or DCE.

Action: If the problem persists, you should connect an HDLC protocol analyzer to the X.25 line and diagnose the problem. If the problem appears to be in the X.25/ACC product, contact your HP support representative.

Explanation: This message indicates that the X.25 line has received a level 2 (HDLC) Disconnected Mode (DM) frame as a response to a transmitted frame. This is used to indicate that the remote side is logically disconnected. When the N2Z driver receives this status, the X.25 is placed into the “down” state. This message may indicate that the X.25 line at the HDLC layer is experiencing problems. In most cases you will need to hook up a protocol analyzer to the line to diagnose the problem.

Action: If the problem persists, check both the local and remote nodes, physical cabling, and if necessary, diagnose the problem using a protocol analyzer.

Explanation: This message indicates that the X.25 line has received a level 2 (HDLC) Set Asynchronous Balanced Mode (SABM) frame. This type of frame should never be received from a link that is up and operating normally and is indicative of a problem at the HDLC layer. This command is used to restart the link at level 2. When the N2Z driver receives this status, the X.25 is placed into the “down” state. This message may indicate that the X.25 line at the HDLC layer is experiencing problems. In most cases you will need to hook up a protocol analyzer to the line to diagnose the problem.

Action: If the problem persists, check both the local and remote nodes, physical cabling, and if necessary, diagnose the problem using a protocol analyzer.

Explanation: The N2Z driver issued a ZCOM zcntl call to configure the ZLUs poll word, select word and option byte, but the call unexpectedly failed. This call is used to configure the PVC packet and window sizes, end-to-end acknowledgment, and other critical internal parameters. The N2Z driver cannot bring up the X.25 line without being able to successfully issue this call.

Action: Check the terminal status code returned against those listed in the ZCOM Status Codes chapter of the ACC Error 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.

Explanation: The N2Z driver received a request to return various statistical information about an X.25 line. The N2Z driver issued a zcntl control write request to cause the X.25 line statistics to be uploaded into the ZCOM interface table. This request has unexpectedly failed. This means that the latest information will be unavailable. The N2Z driver will report stale statistical information which could be as old as 10 seconds. The error may be indicative of a more serious problem.

Action: Check the error returned against those listed in the ZCOM Error Codes chapter of the ACC Error 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.

Explanation: This message indicates that the X.25 line has received a level 2 (HDLC) Supervisory Response frame which had the F-bit set. That is, an unsolicited final response when none was expected. When the N2Z driver receives this status, the X.25 is placed into the “down” state. This message may indicate that the ACC and remote node's implementation of HDLC/LAP-B are incompatible.

Action: If the problem persists, check both the local and remote nodes, physical cabling, and if necessary, diagnose the problem using a protocol analyzer.

Action: This is an internal defect. Contact your HP support representative.

Explanation: The ZCOM zrcvr routine is called by the N2Z driver to tell the ZCOM subsystem to send all control status information for the level 2 and virtual circuit ZLUs to the N2Z driver's inbound event handling routine. This routine has unexpectedly failed. This is a serious problem which will prevent the N2Z driver from bringing the X.25 line up. There are no known causes for this failure.

Action: Check the error returned against those listed in the "ZCOM Error Codes" chapter of the ACC Error 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.

Explanation: The N2Z driver was asked to place a call with more than 16 bytes of call user data but the N2Z driver did not find the “fast-select” facility in the “facilities” packet. It is illegal to send more than 16 bytes of call user data without also selecting the fast select facility.

Action: Correct the application program and/or x25init configuration as appropriate.

Explanation: The N2Z driver received an inbound call that contained facilities that did not match the x25init configuration file. For example, the inbound call requested flow-control negotiation but the x25init specified that flow-control negotiation is disabled. In most instances, the proper action is to immediately clear the inbound call. The x25init configuration must agree with the network subscription values.

Action: Either correct the network subscription to agree with the values used in the x25init configuration file or modify the x25init configuration file to match the network subscription values.

Explanation: The N2Z driver issued a zinfo call to retrieve the configuration information on the MUX card associated with the X.25 line being initialized, but the zinfo call unexpectedly failed with the indicated error number. This error will prevent the N2Z driver from bringing the X.25 link up.

Action: Check the error returned by the zinfo call against those listed in the "ZCOM Error Codes" chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: The nli2zcom driver issued a zport call to configure the port parameters of a port on an ACC card. This request is issued when the n2z_pcfg utility is run. The zport() call unexpectedly failed with the indicated error number. Most likely, the user supplied an illegal port configuration.

Action: Check the error returned by the zport call against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: This message indicates that the X.25 line has received a level 2 (HDLC) Unnumbered Acknowledgment (UA) frame as a response to a transmitted frame when there was no unnumbered command frame outstanding. When the N2Z driver receives this status, the X.25 link is placed into the “down” state. An attempt will be made to automatically re-establish the level 2 connection. The application will need to re-establish all of the virtual circuits. This message may indicate that the X.25 line at the HDLC layer is experiencing problems. In most cases you will need to hook up a protocol analyzer to the line to diagnose the problem.

Action: If the problem persists, check both the local and remote nodes, physical cabling, and if necessary, diagnose the problem using a protocol analyzer.

Explanation: The nli2zcom driver issued a zport call to configure the port parameters of a port on an ACC card. This request is issued when the n2z_pcfg utility is run. The zport() call unexpectedly failed with the indicated status code (see /opt/acc/include/zcom/zcomstatus.h). Most likely, the user supplied an illegal port configuration.

Action: Check the error returned by the zport call against those listed in the "ZCOM Status Codes" chapter of the ACC Error Guide and correct the problem or contact your HP representative (if the error code indicates an internal defect) as necessary.

Explanation: The N2Z driver issued a call to zconfig to dynamically create a new TERM entry in the Physical and Logical terminal tables to the represent the new X.25 link. However, this call unexpectedly failed with the indicated error. Most likely, all of the spare terminal entries are in use. You may need to increase the Terminal-ZLU, Physical-Term, and Logical-Term parameters in your TTGEN configuration file.

Action: Check the error returned against those listed in the "ZCOM Error Codes" chapter of the ACC Error 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.

Explanation: The N2Z driver issued a call to zconfig to dynamically create a new TERM entry in the Physical and Logical terminal tables to represent a new virtual circuit. However, this call unexpectedly failed with the indicated error. Most likely, all of the spare terminal entries are in use. You may need to increase the Terminal-ZLU parameter in your TTGEN configuration file.

Action: Check the error returned against those listed in the ZCOM Error Codes chapter of the ACC Error 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.

Explanation: The N2Z driver has dynamically modified the configuration for the X.25 link. When it attempted to notify the x25cn daemon of the configuration change using zconfig() to generate a dynamic reconfiguration system event message, the call unexpectedly failed with the indicated error. Most likely the X.25 line is unusable. There are no known causes for this function to fail.

Action: Check the error returned against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and take corrective action as necessary. Try re-issuing the x25init command. 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.

Explanation: As a result of an application ioctl request to set the X.25 inbound fragment size, the N2Z driver has issued a request to the firmware on the ACC card to set the point at which the firmware should send inbound data on a VC to the driver. Normally the card waits until the last packet of the data message has been received before passing the message to the driver. The request to change this behavior has unexpectedly failed. There are no known causes for this function to fail.

Action: Check the error returned against those listed in the ZCOM Error Codes chapter of the ACC Error Guide and take corrective action as necessary. If the problem persists and/or abnormal behavior is observed, contact your HP support representative.

Explanation: Most likely an application program has opened the wrong device file and issued an ioctl request to the nli2zcom driver that was meant for another subsystem.

Action: If the problem persists and/or abnormal behavior is observed, contact your HP support representative.

Explanation: Most likely an application program has opened the wrong device file and issued an ioctl request to the nli2zcom driver that was meant for another subsystem.

Action: If the problem persists and/or abnormal behavior is observed, contact your HP support representative.

Explanation: The request by x25init to initialize an X.25 link has failed. One or more prior messages have been logged providing the specific reason for the failure.

Action: Examine any relevant previous error messages logged and take corrective action as needed.

Explanation: The request to shutdown and deallocate an X.25 link has failed. One or more prior messages have been logged providing the specific reason for the failure. This error can occur when either x25stop or x25init is run. Note that x25init also runs x25stop (internally) on the given card, port, and subchannel to insure that there is not an active X.25 link on the line.

Action: Examine any relevant previous error messages logged and take corrective action as needed.

Explanation: The N2Z driver event handler received an unsolicited event which it did not expect and was unable to interpret. The N2Z driver is ignoring this event. This is indicative of an internal defect in the ZCOM subsystem or X.25 firmware. In most cases this problem will not affect normal operation of the X.25 link. However you should report this condition to your HP support representative. This message may be a symptom of a more serious internal problem.

Action: If this problem occurs frequently or if any abnormal behavior is observed, you should contact your HP support representative.

Explanation: While the N2Z driver was initializing and preparing to bring an X.25 line up it detected an illegal value for the level 2 retransmission counter (N2). The N2Z driver is continuing to bring the line up but has set the N2 value equal to one.

Action: No action is necessary but you should modify your x25init configuration file and select a value for N2 which is legal.

Explanation: While the N2Z driver was initializing and preparing to bring an X.25 line up it detected a value for the level 2 retransmission counter (N2) which is larger than the maximum value supported by the ZCOM X.25 firmware. The N2Z driver is continuing to bring the line up but has set the N2 value to the maximum value supported by the X.25 firmware (31).

Action: No action is necessary but you should modify your x25init configuration file and select a value for N2 which is legal (e.g., 1-31).

Explanation: While the N2Z driver was initializing and preparing to bring an X.25 line up it detected a value for the level 2 frame acknowledgment timer (T1) which is larger than the maximum value supported by the ZCOM X.25 firmware. The N2Z driver is continuing to bring the line up but has set the T1 value to the maximum value supported by the X.25 firmware (6300000).

Action: No action is necessary but you should modify your x25init configuration file and select a value for T1 which is legal.

Explanation: While the N2Z driver was initializing and preparing to bring an X.25 line up it detected an illegal value for the level 2 window size parameter (K). The N2Z driver is continuing to bring the line up but has set the value of K equal to one.

Action: No action is necessary but you should modify your x25init configuration file and select a value for K which is legal.

Explanation: While the N2Z driver was initializing and preparing to bring an X.25 line up it detected a value for the level 2 window size parameter (K) which is larger than the maximum value supported by the ZCOM X.25 firmware. The N2Z driver is continuing to bring the line up but has set the value of K to the maximum value supported by the X.25 firmware (7).

Action: No action is necessary but you should modify your x25init configuration file and select a value for K which is legal (e.g., 1-7).

Explanation: This message is logged whenever a Reset is received for a virtual circuit.

Action: No action is necessary. This message is logged for informational purposes.

Explanation: An expedited data packet was sent on a virtual circuit, but it was not acknowledged by the remote DXE within the required amount of time.

Action: No action is necessary. This message is logged for information purposes.

Explanation: This message is logged whenever the local X.25 software has spontaneously generated a reset request on a virtual circuit due to some kind of protocol error (e.g. packet too long, reset timeout, etc). Another message will also be logged containing the cause and diagnostic codes of the generated reset packet. This may indicate a problem with the remote DXE, or link problems.

Action: No action is necessary. This message is logged for informational purposes.

Explanation: The nli2zcom driver received a request to configured and start up an X.25 link. However, when configuring the packet layer window size for PVCs, the value supplied was outside the legal range of 1 to 7. A default value has been chosen, but this value may not match your X.25 subscription value.

Action: No action is required. However, you should correct your x25init configuration file. This message is logged for informational purposes.

Explanation: The nli2zcom driver received a request to configured and start up an X.25 link. However, when configuring the packet layer window size for SVCs, the value supplied was outside the legal range of 1 to 7. A default value has been chosen, but this value may not match your X.25 subscription value.

Action: No action is required. However, you should correct your x25init configuration file. This message is logged for informational purposes.

Explanation: The nli2zcom driver received a streams M_IOCTL message type which it did not expect and is unable to interpret. The nli2zcom driver is ignoring this message. This is indicative of an internal defect ACC or X.25/9000 subsystems or a user application is issuing request to the wrong device file. In most cases this problem will not affect normal operation of the X.25 link. However you should report this condition to your HP support representative if abnormal behavior is observed.

Action: No action is required. This message is logged for informational purposes.

Explanation: The nli2zcom driver queue put function received a streams M_PCPROTO message with an NLI command primitive which it did not expect and was unable to interpret. The nli2zcom driver is ignoring this message. This is indicative of an internal defect ACC or X.25/9000 subsystems or a user application is issuing request to the wrong device file. In most cases this problem will not affect normal operation of the X.25 link. However you should report this condition to your HP support representative. This message may be a symptom of a more serious internal problem.

Action: If this problem occurs frequently or if any abnormal behavior is observed, you should contact your HP support representative.

Explanation: The nli2zcom driver received a streams M_PROTO message with an NLI command primitive which it did not expect and was unable to interpret. The nli2zcom driver is ignoring this message. This is indicative of an internal defect ACC or X.25/9000 subsystems or a user application is issuing request to the wrong device file. In most cases this problem will not affect normal operation of the X.25 link. However you should report this condition to your HP support representative. This message may be a symptom of a more serious internal problem.

Action: No action is required. If this problem occurs frequently or if any abnormal behavior is observed, you should contact your HP support representative. This message is logged for informational purposes.

Explanation: The nli2zcom driver received a streams message which it did not expect and was unable to interpret. The nli2zcom driver is ignoring this message. This is indicative of an internal defect ACC or X.25/9000 subsystems or a user application is issuing request to the wrong device file. In most cases this problem will not affect normal operation of the X.25 link. However you should report this condition to your HP support representative. This message may be a symptom of a more serious internal problem.

Action: No action is required. If this problem occurs frequently or if any abnormal behavior is observed, you should contact your HP support representative. This message is logged for informational purposes.

Explanation: The nli2zcom driver received an NLI N_Listen message which was invalid. This is indicative of an internal defect in the ACC or X.25/9000 subsystems or a user application is issuing request to the wrong device file. You should report this condition to your HP support representative. This message may be a symptom of a more serious internal problem.

Action: No action is required. If this problem occurs frequently or if any abnormal behavior is observed, you should contact your HP support representative. This message is logged for informational purposes.

Explanation: When incoming data arrives from a virtual circuit, the N2Z driver allocates a system buffer to hold the inbound data until it can be delivered to the user process. In this case, the driver's request for additional memory has been denied due to lack of available system memory. The inbound data has been thrown away.

Action: You should increase the amount of memory reserved for network use.

Explanation: A request was made to the N2Z driver to place an outgoing call but all available outgoing virtual circuits are currently in use. The driver has rejected the request.

Action: Try again later or disconnect some of the existing outgoing virtual circuits. If necessary, regenerate both systems to add additional virtual circuits capable of placing outgoing calls.

Explanation: When incoming data arrives from a virtual circuit, the N2Z driver allocates a system buffer to hold the inbound data until it can be delivered to the user process. In this case, the driver's request for additional memory has been denied due to lack of available system memory. The inbound data has been thrown away.

Action: You should increase the amount of memory reserved for network use.

Explanation: Whenever a new stream is opened to the nli2zcom driver, a data structure is allocated to manage that stream. However the nli2zcom driver was unable to allocate a data structure due to insufficient system resources. This could be due to not having enough physical memory install to support the application environment and work load or to applications which use memory without releasing it or that fail to read inbound data in a timely fashion. Note that each VC uses one stream as well as system administration commands issued to the driver (such as requests for statistics, x25stop on a link, etc).

Action: Install additional system memory or analyze memory usage and take corrective measures.

Explanation: This message is logged when the nli2zcom driver receives an inbound call or clear indication and is unable to allocate a ZCOM data buffer to save the addresses, facilities, and user data (CUD). This information has been lost but the call or clear processing is proceeding. This may or may not be serious depending on how the application is using X.25.

Action: You may need to increase the amount of ZCOM buffer space available using the ACC kernel tunable zcom_mem_size and the TTGEN parameter Buffer-Pool.

Explanation: This message is logged when the nli2zcom driver needs to send an Disconnect Indication upwards, but was unable to allocate a streams message buffer to send the request with. The disconnect has been lost and the driver was unable to notify the upper layers that the VC is no longer in use.

Action: You may need to increase the amount of system memory installed. You should make sure the all applications are coded properly to read inbound data promptly and to release memory when no longer needed.

Explanation: This message is logged when the nli2zcom driver needs to send a Streams M_FLUSH message upwards, but was unable to allocate a streams message buffer. The driver has been unable to flush any pending data in the streams read queues for this VC.

Action: You may need to increase the amount of system memory installed. You should make sure the all applications are coded properly to read inbound data promptly and to release memory when no longer needed.

Explanation: This message is logged when the nli2zcom driver needs to send a Streams M_ABORT message upwards, but was unable to allocate a streams message buffer. A M_ABORT message is used to detach PVCs and clear SVCs when there is insufficient resources for the normal mechanism. The driver has been unable to notify the upper layers that the VC is no longer in use.

Action: You may need to increase the amount of system memory installed. You should make sure the all applications are coded properly to read inbound data promptly and to release memory when no longer needed.

Explanation: This message is logged when the nli2zcom driver needs to send a data acknowledgment message (for a previous message with the D-bit set) upwards, but was unable to allocate a streams message buffer. The Data Ack indication has been lost.

Action: You may need to increase the amount of system memory installed. You should make sure the all applications are coded properly to read inbound data promptly and to release memory when no longer needed.

Explanation: This message is logged when the nli2zcom driver needs to send a reset indication message upwards, but was unable to allocate a streams message buffer. The reset indication has been lost.

Action: You may need to increase the am