ACC Error Guide Edition 1 HP 9000 Networking Manufacturing Part Number : Z7345-90003 E0204 © Copyright 2004 Hewlett-Packard Company.
Legal Notices The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty.
This software is based in part on the Fourth Berkeley Software Distribution under license from the Regents of the University of California. ©copyright 1980, 1984, 1986 Novell, Inc. ©copyright 1986-1992 Sun Microsystems, Inc. ©copyright 1985-86, 1988 Massachusetts Institute of Technology. ©copyright 1989-93 The Open Software Foundation, Inc. ©copyright 1986 Digital Equipment Corporation. ©copyright 1990 Motorola, Inc.
Publishing History The manual publishing date and part number indicate its current edition. The publishing date will change when a new edition is published. Minor changes may be made without changing the publishing date. The manual part number will change when extensive changes are made. Manual updates may be issued between editions to correct errors or document product changes. To ensure that you receive the updated or new editions, you should subscribe to the appropriate product support service.
Preface This guide contains an explanation of the error and status codes, and the messages that may be logged via the zmlog utility. Chapters 2 to 4 describe how the error and status codes are returned, how they should be interpreted and what each of them mean. In the remaining chapters, messages logged by the various subsystems are presented in chapters of their own. NOTE The information contained in this manual applies only to HP 9000 computer systems running HP-UX 11.0.
Chapter 7 ZNODE Error Messages describes the error messages produced by this remote node daemon. Chapter 8 ZMASTERD Log Messages contains an explanation of the TTGEN error and status messages. Chapter 9 ZMASTERD Log Messages - describes the log messages produced by this daemon monitoring feature. Chapter 10 PCAPTURE Log Messages - describes the error messages produced by the pcapture daemon. Chapter 11 WATCH Log Messages - describes the error messages produced by the watch daemon.
Related Documentation The documentation available for the Multiprotocol ACC family of products includes the following hardware and software manuals: Hardware Manuals • 8-Channel PCI ACC Multiplexer Hardware Installation and Reference Manual Software Manuals • • • • • • • • • • • • ACC Installation and Configuration Guide ACC Utilities Reference Guide ACC Programmer’s Reference Guide ACC Error Guide HDLC Frame Protocol User’s Guide ACC X.25 Protocol User’s Guide ACC X.
Contents 1. ZCOM Message Logging and Error/Status Codes Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Log Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Subsystem Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2. ZCOM Error Codes ZCOM Error Code and zcomerror( ) Routine . . .
Contents 7. ZNODE Error Messages ZNODE Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 8. TTGEN Error Messages Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TTGEN Summary Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disaster Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ZISDN Kernel Driver: Disasters 1000 - 1999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ZISDN Kernel Driver: Errors 2000 - 2999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ZISDN Kernel Driver: Warning 3000 - 3999 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ZISDN Kernel Driver: Informative 4000 - 4999 . . . .
Contents 14
1 Chapter 1 ZCOM Message Logging and Error/Status Codes 15
ZCOM Message Logging and Error/Status Codes Introduction Introduction The ZCOM subsystem provides a centralized message logging mechanism to allow the ACC software components to log runtime messages to text files. The different subsystems log messages to indicate their normal operations and the errors they encountered. Sometimes the messages may contain vital information for trouble-shooting runtime problems.
ZCOM Message Logging and Error/Status Codes Log Message Format Log Message Format An example of a message that might be displayed via zmlog is the following: 09:51:22 zmast 00125 Daemon znode has been stopped. The message has a time stamp, followed by an 5-character identifier of what daemon or driver is reporting the message. In this case, the message is being reported by the zmasterd daemon. The 5-digit message number and explanation follow.
ZCOM Message Logging and Error/Status Codes Subsystem Identifier Subsystem Identifier Each message has a 5-character subsystem identifier to indicate the source of the message, e.g. the ZCOM Subsystem log messages that are identified by the label “zcom”, the daemons provided by the base ACC product are logged with their program name: “watch”, “zmast” (for zmasterd), “zmon” and “znode”. Other daemons and drivers that are provided with the ACC accessory products may also report messages via zmlog.
2 Chapter 2 ZCOM Error Codes 19
ZCOM Error Codes ZCOM Error Code and zcomerror( ) Routine ZCOM Error Code and zcomerror( ) Routine The ZCOM error code is a 32-bit integer. It is returned with most of the ZCOM APIs to indicate the result of the request. The error code is zero if the request is successful, and non-zero if a failure occurred. zcomerror routine returns a character string which corresponds to the supplied ZCOM error code.
ZCOM Error Codes Meanings of the Error Codes Meanings of the Error Codes The error code returned by the ZCOM API library routine calls is zero if the routine was successful, and non-zero if a failure occurred. The ZCOM error codes, their symbolic names, their explanation, and (if applicable) the corrective action are given below. Applications should always use the symbolic name for an error as the error code value is subject to change.
ZCOM Error Codes Meanings of the Error Codes ZENOZLU (-3): ZLU table is full Explanation: All of the defined program ZLUs have been assigned to ZCOM user programs. This could be caused by user programs that allocate an excessive number of ZLUs without closing them after use. This could also be caused by specifying a TTGEN Program-ZLU parameter value that is too small. Action: If the problem was caused by mismanagement of the ZLUs by the application program, then correct the application source code.
ZCOM Error Codes Meanings of the Error Codes ZEZLU (-7): ZLU is out of range Explanation: An invalid ZLU was specified. The ZLU number must be in the range from 1 to the total number of ZLUs (Terminal-ZLU and Program-ZLU parameters) defined in the TTGEN configuration file. Action: Correct the application source code or increase the Terminal-ZLU and/or Program-ZLU parameters in your TTGEN configuration as needed.
ZCOM Error Codes Meanings of the Error Codes ZENAME (-11): Name of ZLU not unique Explanation: The 7-character ZLU name specified is already used by another program ZLU. The ZCOM subsystem requires a unique symbolic name for each program ZLU. The zname() routine can be used to determine if a symbolic name has been assigned to another program ZLU. Action: Correct the application source code. ZEFLUSH (-12): Message has been flushed Explanation: This error is used as a response to a message sender.
ZCOM Error Codes Meanings of the Error Codes ZENOLTT (-15): No spare logical terminal tables Explanation: All of the logical terminal tables are assigned and in use, leaving no spare ones to create a new terminal with. This could be caused by applications dynamically creating new terminals and then not deleting them when done. Alternately, you may have configured the ZCOM subsystem with too few logical terminal table entries for your needs.
ZCOM Error Codes Meanings of the Error Codes ZERCVRFULL (-18): Too many shared receivers Explanation: When an application requests adding a program ZLU as a shared receiver, and the internal limit of the number of programs that can be in the shared receiver list is reached, this error is returned. Action: This is an application problem. The ZCOM subsystem allows up to 64 program ZLUs in the shared receiver list for each terminal ZLU.
ZCOM Error Codes Meanings of the Error Codes ZEROUTE (-20): Remote call sent to wrong node Chapter 2 Explanation: This error is returned when the internal ZCOM consistency checks detect a remote request that appears to have been routed to the incorrect destination node. This could occur if the Node-Definition sections on the different systems running the ZCOM subsystem are inconsistent.
ZCOM Error Codes Meanings of the Error Codes ZENOBUF (-21): Not enough system free buffers Explanation: This error is returned when the ZCOM subsystem is unable to allocate a buffer from the ZCOM kernel buffer pool in order to process the request. There are many reasons why this error can occur.
ZCOM Error Codes Meanings of the Error Codes ZENTOUT (-23): Remote node timed out Explanation: This error is returned when a request issued to a remote node has taken longer than the configured timeout value. There are many reasons for this error. The remote node or link to the node could have failed after the request was sent, the timeout value may be too short for the amount of system activity at the remote node, or the znode daemon may have been deactivated.
ZCOM Error Codes Meanings of the Error Codes ZENOTERM (-27): No more terminals for this port Explanation: There is a maximum limit of 255 terminals that can be assigned to any given port on a MUX card. In addition, there may be a lower limit enforced based on the type of protocol used on the port. That is, the limit is protocol dependent. If an application attempts to programmatically add a terminal to a port and this limit is exceeded, then this error is returned.
ZCOM Error Codes Meanings of the Error Codes ZEVALUE (-30): Value out of range. Explanation: The value specified is not in the correct range for the request being issued. Action: Correct the application source code. ZEWAIT (-31): Error while awaiting response Explanation: This error indicates an internal defect in the ZCOM drivers. Action: Contact your HP support representative. ZEIRRFULL (-32): Too many interface requests Explanation: Some types of interface requests (.e.
ZCOM Error Codes Meanings of the Error Codes ZEPTLINK (-35): Corrupted PTT group linkage Explanation: This error is returned whenever the ZCOM subsystem discovers an inconsistency in the group linkage of physical terminals. This error could occur if the ZCOM kernel memory tables are corrupt. Action: Contact your HP support representative. ZERCODE (-36): Illegal request code in header Explanation: This error is returned when an internal defect in the product is detected.
ZCOM Error Codes Meanings of the Error Codes ZEBADBH (-40): Corrupted buffer header Explanation: Data corruption within the ZCOM subsystem. Action: Contact your HP support representative. ZEDSCLOCK (-41): DSC function is disabled Explanation: This error is returned when a Dynamic System Configuration function has been requested and the DSC functionality has been disabled (see zconfig). Usually an application program is suspended until DSC is enabled again. However, in certain situation (e.g.
ZCOM Error Codes Meanings of the Error Codes Action: Correct the application program. Make sure there are no other applications accessing the terminal or interface being deleted. ZEREOPEN (-44): Re-open ZLU as different type Explanation: The routine zopen attempted to re-open an existing ZLU that was not a program ZLU. Only program ZLUs are allowed to be re-opened. Action: Correct the application source code.
ZCOM Error Codes Meanings of the Error Codes Action: Correct the application source code. The receivers for a terminal can be removed using the ZCOM zconfig() routine (clear terminal function) or using the zset_rcvr() and if needed, the zevent_rcvr() routine. ZENOTDSB (-48): Must be disabled first Explanation: The requested function requires the terminal to be disabled. However, the terminal was found not to be in the disabled state. Action: Correct the application program.
ZCOM Error Codes Meanings of the Error Codes ZERNODE (-52): Receiver ZLU must be local Explanation: In the current implementation, the zset_rcvr routine only accepts a receiver ZLU on the local node. Any non-zero node number which is not a local node number will be rejected with this error. Action: Use zero or a local node number with the receiver ZLU.
ZCOM Error Codes Meanings of the Error Codes ZEIFTINUSE (-57): Interface table already in use Explanation: The specified interface table (interface card number) is already defined and in use. An unused spare interface table entry must be specified for this request. Action: Correct the application program or if needed increase the number of spare interface tables by increasing the value of the Interface-Table parameter in your TTGEN configuration file.
ZCOM Error Codes Meanings of the Error Codes ZENDOWN (-61): Remote node is DOWN Explanation: This error is returned whenever a request is issued for a remote node that is not currently accessible by the local ZCOM subsystem. That is, the local node has been unable to establish communications with the specified remote node. There are many reasons why this condition can occur.
ZCOM Error Codes Meanings of the Error Codes ZENOSLAB (-64): No spare data storage label Explanation: This error is returned when all data storage labels are used. Hence no new zltstore call will be accepted. The maximum number of data storage labels is fixed in the ZCOM subsystem and is not adjustable. Action: Re-design or reorganize the application to use less storage labels.
ZCOM Error Codes Meanings of the Error Codes ZEPQNO (-68): Bad physical queue number Explanation: The zsetql routine is used to set the queue limit for a physical terminal queue, but an illegal queue number was specified. Refer to zsetql(3x) for more information. Action: Correct the application source code. ZEZCOMREV (-69): ZCOM software not compatible Explanation: The ZCOM software revision code is made up of four numbers.
ZCOM Error Codes Meanings of the Error Codes Action: Replace the bad Mux interface card. ZENOLS (-72): Logical storage not allocated Explanation: This error is returned when zltstore is called with the no-allocate bit (ZCOM_ZLTSTORE_NA) set, but the specified storage label has not been previously defined. This error indicates that the caller is trying to access a logical data storage that does not exist. Action: Correct the application source code.
ZCOM Error Codes Meanings of the Error Codes ZEFILESYS (-76): File system error, check errno Explanation: ZCOM requests are passed to the ZCOM driver via a set of standard HP-UX device files. This error code is returned when the system detects a generic file system error not directly related to the ZCOM subsystem. The global variable errno carries the HP-UX file system error code. Action: Examine the value of errno and correct the problem as needed.
ZCOM Error Codes Meanings of the Error Codes ZEBRESET (-78): System being reset Explanation: This error code is reported by ZMON at ZCOM subsystem startup. Each indicates that the ZCOM subsystem is in an unexpected state. If ZMON is aborted (or killed) abnormally, the ZCOM subsystem may be left in an unknown state and this may cause these errors to occur upon a system restart. Action: ZMON is usually able to cope with these errors automatically.
ZCOM Error Codes Meanings of the Error Codes ZEHLABLEL (-84): Bad system header label Explanation: During ZCOM subsystem startup, ZMON reports this error if it finds that the header label in ZCOM kernel memory is corrupt. The occurrence of this error could be due to memory corruption or a defect in the ZMON process. Action: Contact your HP support representative.
ZCOM Error Codes Meanings of the Error Codes ZEQFLUSH (-88): Queue is being flushed Explanation: This error indicates the destination program or terminal ZLU is being shut down and is not accessible. This could occur as a result of shutting down the ZCOM subsystem while a program is trying to access the ZLU. Action: Application dependent. ZEDAMIO (-89): Problem in I/O with DAM Explanation: This error indicates an inter-driver interface problem between the LDM and DAM.
ZCOM Error Codes Meanings of the Error Codes ZEORMLOOP (-93): OMX receiver maps into a loop Explanation: When the ZCOM subsystem tries to deliver a data message to the receiver for an outbound multiplexing terminal and finds that the receiver ZLU is mapped into an infinite loop, this error is returned. Normally, this should not occur. Action: Contact your HP support representative.
ZCOM Error Codes Meanings of the Error Codes ZEPCOUNT (-97): Invalid number of parameters Explanation: This error is returned only for Fortran ZCOM routines. Some of the FORTRAN versions of the ZCOM routines allow a variable number of parameters. The error parameter is used to specify how many parameters are being passed into the routine for this instance of the call. However, the value passed in did not meet the minimum number of parameters required for this specific request.
ZCOM Error Codes Meanings of the Error Codes ZEPFAIL (-101): Mux card powerfail Explanation: See message “zcom 00201: Card <#> - System powerfail detected” for a description. ZEFATAL (-102): Mux card fatal error Explanation: See message “zcom 00204: Card <#> - failure detected (card reset)!” for a description. ZEINT (-103): Mux card unexpected interrupt Explanation: See message “zcom 00200: Warning - DMA complete received on port <#> with no DMA active.” for a description.
ZCOM Error Codes Meanings of the Error Codes ZEUNIMP (-106): Function not implemented Explanation: This error is returned when a call is made to an unsupported ZCOM routine or a request is not supported by the current version of ZCOM subsystem. Currently, only the zxcpt routine is not supported and will have this error returned. Action: Correct the application source code.
ZCOM Error Codes Meanings of the Error Codes ZEBAD_ECLASS (-110): Invalid event class Explanation: This error is returned by the zevent_rcvr routine when an invalid eclass parameter value has been specified. Action: Correct the application source code. ZEOBSOLETE (-111): Function obsoleted Explanation: This error indicates that the function called has been obsoleted and is no longer supported. In most cases, a replacement function has been available for several releases.
ZCOM Error Codes Meanings of the Error Codes ZeBAD_HPA (-120): Bad HPA in interface table Explanation: This error is returned when the DAM driver detects inconsistencies between the hardware card it binds with and the HPA sets up in the ZCOM interface table. This error indicates internal software incompatibility. Action: Check to make sure there is no problem in software installation, re-install if necessary. If problem persists, contact your HP support personnel.
ZCOM Error Codes Meanings of the Error Codes ZeCARD_NOT_READY (-124): Mux not fully started up Explanation: This error is returned when the LDM issues a LLIO “READY” request to the DAM without having successfully issued the correct sequence of LLIO requests. Action: Contact your HP support personnel.
ZCOM Error Codes Meanings of the Error Codes ZeNOT_IN_LLIO (-128): DAM is not in the LLIO mode Explanation: This error is returned when a LLIO “RESET” request is issued while the card is in a normal runtime operating mode. This command is not allowed without first running zmasterd stop or zmon stop. Action: Run zmasterd stop or zmon stop before attempting to issue a reset command.
ZCOM Error Codes Meanings of the Error Codes ZeNO_PORTS (-131): No defined ports on Mux Explanation: This error is returned by the DAM when it is asked to initialize an ACC Mux card that did not have any ports defined for it. This could be a defect in TTGEN but most likely was caused by an incorrect TTGEN configuration file. Action: Correct your TTGEN configuration file.
3 Chapter 3 ZCOM Status Codes 55
ZCOM Status Codes ZCOM Error and Status Codes ZCOM Error and Status Codes There might be some confusion about ZCOM error codes versus ZCOM status codes because both are returned (via different call mechanisms) by ZCOM API calls, and ZCOM status codes look like they are reporting error conditions. A ZCOM error code is intended to report status, typically problems, about an application’s ability to interact with the ZCOM subsystem.
ZCOM Status Codes Notification of Status Codes Notification of Status Codes Each attempt at communication between an application program and a ZCOM terminal has a status code associated with it. The status code may be associated with a request to send a message to a terminal ZLU, to read a message from a terminal ZLU, to change the state of a terminal ZLU, or it may be an unsolicited report of a terminal ZLU status change.
ZCOM Status Codes ZCOM Terminal Request Codes ZCOM Terminal Request Codes Each request to or from a terminal has a request code indicating the type of operation. This code is in addition to the ZCOM message type. The request code is defined for all messages with message types ZCOM_MSTYPE_MSLT(1) and ZCOM_MSTYPE_RSLT(6) (or ZCOM_MSTYPE_MSRT(9) and ZCOM_MSTYPE_RSRT(14) for remote terminals). These are messages from terminals or responses from terminals.
ZCOM Status Codes Interpretation of Status Codes Interpretation of Status Codes A message of type ZCOM_MSTYPE_MSLT(1), or ZCOM_MSTYPE_MSRT(9) obtained from a read via zread or zpeek is typically delivering data which has been received by an ACC card from the network.
ZCOM Status Codes ZCOM Status Message Routine ZCOM Status Message Routine The zcomstatus routine returns a character string which gives an explanation of the status codes. This routine may be called to format status messages describing the reason for the status returned in a terminal request. The format and a typical use of the zcomstatus routine is as follows: #include #include
ZCOM Status Codes Meanings of the Status Codes Meanings of the Status Codes The ZCOM status codes are divided into three groups, depending on the associated request code. Within each group, not all status codes apply to all request codes. The groups are: Terminal input, output control, and unsolicited errors Request codes: 1, 2, 3 and 5 Terminal configuration and state control Request codes: 6, 7, 8, 9, 10 Port configuration Request code: 11 It it only possible to report one status per status code.
ZCOM Status Codes Terminal I/O Status Codes Terminal I/O Status Codes Status Code Status Message/Description IO_OK(00) No error detected This is the normal status code returned when a request has been carried out successfully. IO_DSBL(01) Terminal disabled The terminal needs to be enabled to carry out the request. IO_TX_TMOUT(02) Cable or local modem fault The external transmit clock has stopped.
ZCOM Status Codes Terminal I/O Status Codes IO_TX_URUN(08) Transmit underrun The multiplexer could not supply data fast enough to keep the transmitter running. With a character oriented synchronous protocol this will usually result in SYNC characters being inserted. With a bit oriented synchronous protocol the frame being transmitted will be aborted. IO_INV_RESP(09) Invalid terminal response The remote device has responded with a message which is invalid in the current state.
ZCOM Status Codes Terminal I/O Status Codes IO_ADDR(16) Address error A message has been received containing an incorrect address. Possibly a response from a device which was not polled. IO_SUBADDR(17) Subaddress error The subaddress within a received message does not match the one within the corresponding poll or select. IO_RX_ORUN(18) Receiver overrun Data was received from a port faster than the multiplexer could load it into a buffer.
ZCOM Status Codes Terminal I/O Status Codes IO_UNA_CTL(26) Unable to process control write A control write was requested but the multiplexer is unable to process the request at this time (possibly due to a shortage of resources such as buffers). IO_LTERM_DSBL(27) Logical terminal disabled This logical terminal must be enabled before a data may be transmitted on it. IO_LTERM_DOWN(28) Logical terminal down The logical terminal is currently down and cannot have data transmitted over it.
ZCOM Status Codes Terminal I/O Status Codes IO_RETRY(35) Retryable error occurred An internal status code used between the driver and firmware to indicate that a request should be retried at a later time. IO_BUF_SIZE(36) Buffer size illegal The message is too large and is rejected by the firmware. For the Z7330A interface the limit is 16,384 bytes. IO_INV_REQ(37) Invalid request code The destination of the request did not recognize the specified request code.
ZCOM Status Codes Terminal I/O Status Codes IO_DEFER(128) Deferred request (internal usage) An internal status code used between the driver and the firmware to indicate that the request will have a deferred response.
ZCOM Status Codes Terminal State Control Status Codes Terminal State Control Status Codes Status Code Status Message/Description TM_OK(00) No error detected The request was performed with no detected problem. TM_MUST_DSBL(01) Terminal must be disabled For a terminal control request the terminal must be disabled. TM_ROLL_FULL(02) Too many terminals on port No more terminals can be added to the requested port unless an existing one is moved to another port or deleted.
ZCOM Status Codes Terminal State Control Status Codes TM_GRP_DSBL(08) Group not disabled All other terminals on the same port and with the same group poll address must be disabled before a terminal’s configuration can be changed. TM_NEW_GRP_DSBL(09) New group must be disabled All other terminals on the same port and with the same group poll address must be disabled before a terminal can be added to that group. TM_NOT_ALLOWED(10) Not allowed for this terminal Not used.
ZCOM Status Codes Terminal State Control Status Codes TM_RETRY(35) Retryable error occurred An internal status code used between the driver and firmware to indicate that a request should be retried at a later time. TM_BUF_SIZE(36) Buffer size is illegal The length of the request data for a set terminal parameters request is not valid. TM_INV_REQ(37) Invalid request code (internal error) The destination of the request did not recognize the specified request code. This should never happen.
ZCOM Status Codes Port Configuration Status Codes Port Configuration Status Codes Status Code Status Message/Description PT_OK(00) No error detected The request was performed with no detected problem. PT_INV_PORT(01) Port number out of range Port numbers must be in the range zero (0) to seven (7). PT_BAD_PARM(02) Bad parameter specified The port request code was not recognized.
ZCOM Status Codes Port Configuration Status Codes PT_NO_DPLL(10) No DPLL available at this baud rate The specified baud rate is not compatible with using DPLL as the clock source. PT_TOO_FAST(11) Async. mode not available for baud rate > 38400 An attempt was made to configure an asynchronous port with a baud rate that was too high.
4 Chapter 4 X.
X.25 Status and Completion Messages Introduction Introduction X.25 may produce a wide range of buffer status codes and unsolicited status messages, apart from the standard communications statuses. Most of the messages are received by the zx25d driver. The ACC X.25 driver (zx25d) may also produce error messages which will be logged to the system error logging device by zmlog. Refer to the ACC Utilities Reference Guide for more information on zmlog.
X.25 Status and Completion Messages Introduction mhdp->mrq.mrqstat contains one of the status codes listed below in the lower seven bits of the field (e.g. bits 0-6). Buffer Completion Statuses At the link level (X.25 link ZLU), the following two buffer (write) completion error statuses may be returned, as well as the more usual standard statuses. Although these are a part of the standard status set, they are not used by most protocols, and have a particular significance within X.25.
X.25 Status and Completion Messages Introduction Unsolicited Status Messages The X.25 subsystem generates many different types of X.25 unsolicited status messages. Some of the status messages provide X.25 link specific information, that is, some of the status codes are only generated by the X.25 link and will never be generated by a Virtual Circuit ZLU. Other codes pertain to various VC related protocol errors. Typically these are only delivered to the zx25d X.25 protocol driver.
X.25 Status and Completion Messages Introduction end of the link is not responding to the HDLC/LAP-B protocol packets sent by the ACC. If bit 7 = 0, then the link is up (at level 2). ST25DSBL (65) The X.25 link has been disconnected due to a disable request on the X.25 link ZLU. ST25XDCD (66) X.25 Link disconnected or restarted due to loss of DCD. Bit 7 of the mrqstat field will indicate the current up/down state of the link. ST25XCTS (67) X.25 Link disconnected or restarted due to loss of CTS.
X.25 Status and Completion Messages Introduction ST25RUFR (75) X.25 Link disconnected or restarted due to a received unsolicited final response frame. Bit 7 of the mrqstat field will indicate the current up/down state of the link. ST25ENF (77) X.25 Link ZLU enable failed due to an invalid configuration. Check the various configuration parameters, particularly the poll and select words for this X.25 link ZLU. ST25ENB (78) X.25 Link ZLU has been enabled. ST25TPA (79) X.25 Link ZLU has been activated.
X.25 Status and Completion Messages Introduction messages. If an application is sending a large contiguous message, it is recommended that the message be broken up and sent in 4,096 byte blocks using the M-bit where appropriate. ST25RSTRT (85) X.25 link Restart processing complete. The X.25 packet layer (level 3) is now up. Note that SVC and PVC ZLUs can not be used until the packet layer is up.
X.25 Status and Completion Messages Introduction ST25BADPR (94) Bad P(R) in received packet. This indicates that a data packet received on a VC contained an invalid sequence number in the P(R) field. This will cause the VC to be reset. ST25RXREJ (95) The VC received a REJECT packet. This will cause the VC to be reset. ST25LCCTO (96) A Virtual Circuit control timeout has occurred. This indicates that the remote end of the link has not responded to a protocol packet within the appropriate amount of time.
X.25 Status and Completion Messages Introduction ST25PKLNG (102) VC interrupt or data packet too long. The remote end of the link sent a data packet which exceeded the X.25 level 3 packet size or an interrupt packet larger than 32 bytes for 1984 X.25 or larger than 1 byte for 1980 X.25. This will cause the VC to be reset. ST25BADQB (103) Inconsistent Q-bit usage detected in VC data packets. This indicates the inbound data packets of a complete packet sequence did not ALL contain the same Q-bit value.
X.25 Status and Completion Messages Introduction ST26INTPT (110) The VC has received an Interrupt Packet. The data buffer contains up to 32 bytes worth of interrupt data. ST26ICONF (111) Interrupt Confirmation packet received for this Virtual Circuit. The remote DTE has confirmed the Interrupt packet which was sent. ST26LCENB (112) VC ZLU has been enabled. This indicates that the VC ZLU is now in the enabled state. At this point, the ZLU is available to place a call (SVC) or for transferring data (PVC).
X.25 Status and Completion Messages Introduction ST26LCRST (118) VC Reset Request confirmation received. This indicates that the Reset request processing is complete. Either a reset collision has occurred or the remote end of the link has confirmed the reset request. ** ST26CLRCV (119) Inbound Call Request received on the SVC ZLU. This status is only received when the ACK bit is set to 0 in the VC ZLU’s option word. The ACC X.25 subsystem will automatically attempt to send a Call Accept packet.
X.25 Status and Completion Messages Introduction VC UP status message. Status 123 also has an associated data buffer which contains the Call Accept packet information. ** ST26LCRSS (124) Local VC Reset initiated due to protocol exception condition. This indicates that the ACC X.25 subsystem has sent a Reset Request as the result of an exception condition. For example, if an Interrupt packet that was sent is not confirmed within T26 seconds. ZxRESET_TO(125) VC Reset Request has timed out.
X.25 Status and Completion Messages Introduction } char x25pkdata[X25PKDATALEN]; x25pkform_type Figure 4-1 /* Facility and user data */ Packet Data Layout 16 Bits X X Delivery Confirmation Bit State x25pkdbit Cause x25pkcaus Diagnostic x25pkdiag Use This Address Instead of Default x25pkdflg Called X.121 Address (BCD) x25pkcald (8 Bytes) 4-Bit Length X Use This Address Instead of Default x25pkgflg Called X.
X.
5 Chapter 5 ZCOM Driver Log Messages 87
ZCOM Driver Log Messages ZCOM Driver Messages ZCOM Driver Messages This chapter contains an explanation of the ZCOM Subsystem messages that may be logged by the base drivers, LDM and DAM. These messages are identified by the label “zcom”. Meaning of Messages zcom 00000: System bootup Explanation: This message is automatically logged by the LDM when the HP-UX system is booted up. Action: None required, this is an informational message.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00102: Flushed <#> message(s) on closing ZLU <#> Explanation: When a ZLU is to be closed or mapped (to another ZLU), if the LDM finds some pending messages queued on that ZLU, it flushes the queue and releases all buffers to the buffer pool. These messages are reported when this happens. Action: None needed, this is an informational message.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00121: Initiate reset with <#> active ZCOM requests Explanation: When a user initiates a ZCOM subsystem shutdown while there are application requests currently in progress, the LDM will wait for 5 seconds before it forces the ZCOM subsystem to shutdown. These two messages report the number of active application requests in progress when the LDM forced the ZCOM subsystem to shutdown. Action: None needed, this is an informational message.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00150: Error in copying data from ZNODE: Explanation: This error is reported when there is a problem in copying data from ZNODE’s program data space to the LDM’s kernel data space. This could indicate inconsistencies in the versions of the ZCOM kernel drivers and the ZNODE daemon. This error will cause ZNODE to terminate, thereby resulting in all remote nodes being inaccessible.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00152: Late API response returned from node <#> Explanation: The LDM received a remote API request response after it had timed out the original request. When a ZCOM request is issued to a remote node, the LDM sends the request and allows a fixed (configurable) amount of time for the request to be completed (response to arrive).
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00154: Dropped data not for this node (from node <#> to <#>) Explanation: The LDM received data from a remote node that does not appear to be intended for the local ZCOM subsystem. The source and destination node numbers from the original request are displayed in the message. The request message (data) has been discarded.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00157: Can’t read ZNODE queue: Explanation: The LDM attempted to retrieve a request from its internal ZNODE queue but encountered an unexpected error. The specific reason for the error is given in the error text displayed in the message. Depending on the error, ZNODE may terminate. Action: Examine the error text and correct the problem if possible. Check for possible incompatible versions of ZCOM software installed.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00159: Can’t build response for node <#>: Explanation: The LDM attempted to link a deferred response to a response record for a remote request (e.g. zsend mode 8), but detected an unexpected error. The specific reason for the error is given in the error text displayed in the message. The completion response message is lost and the remote application will eventually receive a ZENTOUT (-23, Remote node timed out) error for the request.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00161: Can’t send response to node <#>: Explanation: The LDM attempted to place a response message on the ZNODE queue to be passed back to the remote application but encountered an unexpected error. The specific reason for the error is given in the error text displayed in the message. The completion response message is lost and the remote application will eventually receive a ZENTOUT (-23, Remote node timed out) error for the request.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00163: ZNODE has terminated, all nodes set DOWN Explanation: This message is logged when the LDM detects that ZNODE has terminated. ZNODE could have terminated abnormally (core dump), been killed (kill -9), or the user could have shutdown znode (zmasterd deact znode). The LDM will mark all remote nodes as down. In addition, the local node is also marked down to indicate that ZNODE is no longer running.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00166: Node <#> link <#> DOWN: Explanation: This message is logged when one of the links to a remote node has gone down. The Remote-Node definition in the TTGEN configuration file allows up to four links to be specified. The links are numbered from 0 to 3. This message will be followed by a node down message (zcom 164) if this link is the only one defined or is the last usable link for the associated remote node.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00169: Not enough memory for Buffer-Pool size of <#> bytes Buffer-Pool size reduced to <#> bytes. Explanation: This message is logged during ZCOM subsystem startup if the LDM finds the specified Buffer-Pool size in the ttgen configuration file is larger than what the kernel can accommodate. When kernel memory is not sufficient to meet the ttgen configuration, the memory reserved for Buffer-Pool is reduced to allow system startup.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00200: Warning - DMA complete received on port <#> with no DMA active. Explanation: This message is logged whenever the ACC Device Adapter Manager (DAM) receives a DMA completion interrupt but the DAM has determined that no DMA operation is in progress. The DMA completion interrupt will be ignored by the DAM. Action: In most cases, you may safely ignore this message.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00203: Card <#> - Firmware failure detected (card reset)! Explanation: The DAM received an unsolicited interrupt from an ACC Mux card indicating that the ZCOM Mux card firmware has experienced some kind of fatal error (internal defect). The card will be reinitialized and all operations in process at the time of the firmware failure will be restarted. Action: Contact your HP Support Representative.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00206: Card <#> Port <#> configuration failed with error <#>. Explanation: A $PORT backplane transaction was issued to the ACC Mux card which completed with an error. This could be due to an illegal configuration or a self-test failure for that port. Action: If due to a bad configuration, correct your TTGEN configuration file. If the port failed its self-test, the port will remain unusable.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00209: Improperly configured ZLU <#> found during card restart. Most likely this is due to an application defect. The application did not issue a zcntl (ZCOM_MRCODE_TERM) request. Explanation: While attempting to initialize all of the terminal ZLUs configured into an ACC Mux card, the DAM found a Physical Terminal Table entry which was marked as not in use.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00211: Card <#> - NULL PTT entry in IFT->ifplook[] table! Port number = <#> Terminal number = <#>. Explanation: The ifplook data structure is used by the DAM to vector inbound data and status to the correct Physical Terminal Table entry which the event is to be queued on. However, the DAM did not find a valid pointer in the ifplook table entry indicated by the Mux firmware. The DAM has discarded the data and/or status information.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00213: Card <#> ZLU <#> Error on read (length mismatch)! Explanation: Processing of inbound data and status is a two step process. First the DAM receives an unsolicited interrupt packet indicating the type of inbound data and its length. The DAM then issues a transaction to the Mux card to read the inbound data or status packet. Within this packet is the length of the data.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00216: Card <#> ZLU <#> Queue limited for inbound data. Explanation: When a program ZLU is created the application can select the maximum amount of inbound data and/or status that can be queued onto the ZLU. This message is logged when that limit has been exceeded. The data and/or status information is thrown away when this limit is exceeded.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00219: Card <#> Port <#> Port is out of transmit buffers. Explanation: This message indicates that the ACC Mux card has temporarily consumed all of its internal transmit data buffers and is currently unable to accept another request. The DAM will send the request again when this condition is alleviated. If this condition occurs frequently, it will have a negative impact on performance. Action: No action is necessary.
ZCOM Driver Log Messages ZCOM Driver Messages Action: Contact your HP Support Representative. zcom 00223: Card <#> Port <#> Term <#>: Zc_qbadd failed with error <#>! Unable to allocate a buffer for inbound data. Explanation: While attempting to allocate a ZCOM subsystem buffer for inbound data an unexpected failure occurred. Action: Examine the error returned and check the ZCOM manuals.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00225: Card <#> Port <#> RXDT15 bad reply (status = <#>), data dropped! Explanation: This message can occur when the DAM issues a request to read inbound data and the Mux firmware cannot find any inbound data to send or if the length of the inbound data requested by the DAM is different then the length maintained by the Mux firmware. Action: Contact your HP Support Representative. zcom 00226: Card <#> Port <#> Error on $RXDT15 read (length mismatch).
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00229: Card <#> Port <#> No buffers and no requests pending Explanation: This message is logged when the DAM is notified by the ACC MUX firmware that their are no available buffers on the card, but the DAM has no outstanding write request to the card. This is a rare but potential condition that can arise with a complex protocol such as X.25 and can normally be ignored.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00231: ZLU <#> receiver data dropped: Unable to create a copy of data for a shared receiver. Explanation: When more than one receiver for a terminal ZLU is defined, the drivers must queue the inbound data message on each program’s input queue. However, when the driver attempted to create the data structures to link the data to each input queue, the operation unexpectedly failed. The error text contains the specific reason for the failure.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00235: Card <#> - I/O suspended due to lack of ZCOM buffers. Explanation: When the ACC card indicates an inbound data buffer needs to be transferred to the host, the driver attempts to allocate a buffer to DMA the data into. This message is logged when there are no free buffers remaining in the ZCOM buffer pool.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00252: Card <#> - Too few or too many quads in backplane request. Explanation: This is an internal defect. Action: Contact your HP Support Representative. zcom 00300: Card <#> - NULL PTT entry in IFT->ifplook[] table! Terminal number = <#>. Explanation: See “zcom 00211: Card <#> - NULL PTT entry in IFT->ifplook[] table! Port number = <#> Terminal number = <#>.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00305: Card <#> Internal error: Transmit requeue stack not empty on exit! Explanation: This is an internal defect. Action: Contact your HP Support Representative. zcom 00306: Card <#> Port <#> Invalid request code on port list! Explanation: This is an internal defect. Action: Contact your HP Support Representative. zcom 00307: Card <#> Port <#> Ran out of DMA quads for port config data! Explanation: This is an internal defect.
ZCOM Driver Log Messages ZCOM Driver Messages zcom 00312: Card <#>: Requested <#> IRQs but available IRQs is <#>. Explanation: This is an internal defect. Action: Contact your HP Support Representative. zcom 00313: Card <#>: $STAT returned illegal terminal #<#>. Terminal ignored. Explanation: These are internal defects. Action: Contact your HP Support Representative. zcom 00321: Card <#>: Invalid pending IRQ count 0x<#> Explanation: These are internal defects.
ZCOM Driver Log Messages ZCOM Driver Messages 116 Chapter 5
6 Chapter 6 ZMON Error Messages 117
ZMON Error Messages ZMON Error Messages ZMON Error Messages Message 001 - Program aborted (location = ) Explanation: This message is issued by ZMON when it cannot complete the task requested. The line code indicates the internal line of the ZMON program when the problem occurred. This line number may be useful in tracking the cause of the problem. Action: Investigate the cause of the program abort, correct the problem, and if necessary retry the failed ZMON operation.
ZMON Error Messages ZMON Error Messages Message 006 - Getting ZCOM system status … Explanation: Message printed as a result of ZMON STATUS being issued. Action: None Message 007 - Enable driver debug (level = ) … Explanation: Message printed as a result of ZMON DEBUG being issued. Action: None Message 008 - Disable driver debug … Explanation: Message printed as a result of ZMON NODEBUG being issued.
ZMON Error Messages ZMON Error Messages Message 012 - ZMON file: Explanation: Message displays the name of the ZMON device file used to access the ZCOM kernel memory. This file is usually /dev/zmon. Action: This message is usually preceded by message 011 describing the reason the file could not be opened. Correct the problem and retry the ZMON startup.
ZMON Error Messages ZMON Error Messages Message 022 - Can’t allocate scratch memory of bytes Explanation: Message printed when ZMON cannot allocate local memory for processing the TTGEN output file. Action: Correct the memory shortage problem and retry the ZMON startup. Message 023 - Memory file read error: Explanation: Message printed when ZMON cannot read data from the TTGEN memory image file. This may indicate a corrupt file. Action: Retry the ZMON startup.
ZMON Error Messages ZMON Error Messages Message 026 - Incomplete write to ZMON file Explanation: Message printed when ZMON cannot write data to the ZMON LDM device file (usually /dev/zmon). This may indicate a corrupt TTGEN memory image file, or some internal inconsistency in the ZCOM LDM. Action: Retry the ZMON startup. If this problem persists rerun TTGEN from the source TTGEN configuration file (.answ file) to rebuild the memory image file. When the file has been rebuilt, retry the ZMON startup.
ZMON Error Messages ZMON Error Messages Message 029 - ioctl(memory) error: Explanation: Message is displayed when ZMON encounters a memory error when configuring the ZCOM kernel memory. The usual cause is insufficient memory (Not enough memory for this configuration) in the zcom_mem_size parameter in the system file used to build your kernel (usually /stand/system).
ZMON Error Messages ZMON Error Messages Message 040 - ioctl(getirr) error: Explanation: This message is displayed when ZMON receives an error while reading an event from the LDM interface request queue. After displaying this error, ZMON will terminate. Action: Restart ZMON with ZMON QUEUE. If this still does not clear the problem try rebooting the HP-UX system; and then report the problem to HP.
ZMON Error Messages ZMON Error Messages Message 044 - Request at - startup card Explanation: This message is displayed whenever the Dynamic System Configuration function enable interface is performed. This indicates that the specified interface card is to be restarted. Action: None Message 045 - Request at - disable card Explanation: This message is displayed whenever the Dynamic System Configuration function disable interface is performed.
ZMON Error Messages ZMON Error Messages Message 050 - Card number out of range, restart ignored Explanation: Message printed as a result of the ZMON RESTART request being issued with an invalid card (MUX interface) number. Action: Reissue the RESTART request with the correct card number.
ZMON Error Messages ZMON Error Messages Message 062 - Status since - Ready (running) Explanation: Message printed as a result of the ZMON STATUS request being issued. This status indicates that the ZCOM system has been successfully started up and is available for normal operations. Action: None Message 063 - Status since - Being reset Explanation: Message printed as a result of the ZMON STATUS request being issued.
ZMON Error Messages ZMON Error Messages Message 067 - Status since - Initialized (idling) Explanation: Message printed as a result of the ZMON STATUS request being issued. This is also a transient status that indicates the ZCOM system is being started up. Action: None Message 068 - Status since - Unknown (0x) Explanation: Message printed as a result of the ZMON STATUS request being issued. This message indicates the ZCOM system is in an unknown state.
ZMON Error Messages ZMON Error Messages Message 074 - ioctl(reset) error: Explanation: Message printed as a result of a ZCOM reset request being issued. The message indicates the IOCTL request to reset the ZCOM system has failed. Action: Report the problem to the nearest HP representative. Message 075 - ZCOM system stopped Explanation: Message printed as a result of the ZMON STOP request being issued.
ZMON Error Messages ZMON Error Messages Message 103 - Card inconsistent or corrupted IFT Explanation: During the restart/shutdown of a Mux card ZMON reports the last backplane activity that the DAM attempted to the card. This information is contained in the ZCOM IFT (interface table) and must be read via the /dev/zmon device file. This error indicates the read has failed for some reason. The restart/shutdown of the card is abandoned if this error is encountered.
ZMON Error Messages ZMON Error Messages Message 106 - Card request ignored because IFT is not initialized Explanation: ZMON tries to process a startup or shutdown request for an interface card, but the card information is not defined (e.g. it is skipped in the TTGEN configuration file). The card information is contained in the ZCOM IFT (interface table), and can be read via the /dev/zmon device file. This error indicates the IFT is not set up.
ZMON Error Messages ZMON Error Messages Message 109 - Card request ignored because it’s an old request Explanation: ZMON displays this message when it receives an Interface Restart Request (IRR) and finds that the current system is already restarted AFTER the time when this IRR is generated. This usually happens when there are multiple IRRs generated during a card startup (e.g. an unstable card may fail a few times during its startup).
ZMON Error Messages ZMON Error Messages Message 112 - Card Current ports: Hi-Pri Lo-Pri Explanation: The Mux card hardware or software has failed for some reason. These port numbers represent the last ports accessed by the driver. This information may be useful in determining the cause of the failure. Action: Report these values to HP to assist in diagnosing the reason for the failure.
ZMON Error Messages ZMON Error Messages Message 118 - Card control request overridden by other request Explanation: When there are multiple card control requests issued to ZMON at the same time, a later one may override the one already in-progress, if appropriate. For example, when ZMON is restarting a card and a “zmon shutdown …” is issued on the same card, the first RESTART request will be aborted by the second SHUTDOWN required.
ZMON Error Messages ZMON Error Messages Message 141 - ZCOM system is not running Explanation: Message is displayed when a ZMON request is issued (for example, ZMON RESTART) when ZCOM is not running. Action: Restart the ZCOM system. Message 142 - Can’t read ZCOM system header: Explanation: Message is displayed when ZMON fetches the ZCOM header record before attempting to execute some of the ZMON commands. In this case the request failed with the reason given.
ZMON Error Messages ZMON Error Messages Message 202 - Card enable error: Explanation: Message is displayed when ZMON is attempting an operation on a Mux card and it fails. The error may be either a file system error or a ZCOM error. The cause of the error is displayed in the reason field. Action: Take appropriate action to rectify the problem and restart the Mux card, or restart the ZCOM system.
ZMON Error Messages ZMON Error Messages Message 206 - Card set-ready error: Explanation: Message is displayed when ZMON is attempting an operation on a Mux card and it fails. The error may be either a file system error or a ZCOM error. The cause of the error is displayed in the reason field. Action: Take appropriate action to rectify the problem and restart the Mux card, or restart the ZCOM system.
ZMON Error Messages ZMON Error Messages Message 222 - Card Port controller test failed Explanation: Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals. Action: At a convenient time, shutdown the system and replace the Mux card.
ZMON Error Messages ZMON Error Messages Message 225 - Loopback test failed Explanation: Message printed as a result of a serious selftest failure. The LED on the back of the card will be RED or OFF. The card will be unusable and all terminals configured on the card will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the card—the tt command alone will not show the unavailable terminals. Action: At a convenient time, shutdown the system and replace the Mux card.
ZMON Error Messages ZMON Error Messages Message 231 - Card Port DSR signal missing Explanation: Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.
ZMON Error Messages ZMON Error Messages Message 234 - Card Port RTS signal missing Explanation: Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.
ZMON Error Messages ZMON Error Messages Message 237 - Card Port RS232 external loopback test failed Explanation: Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.
ZMON Error Messages ZMON Error Messages Message 241 - Card $DWNL (upload) gives non-zero reply Explanation: Before downloading the Mux card ZMON attempts to read the ROM label of the firmware on the Mux card. In this case the read has failed. Action: Take the appropriate action to rectify the problem and restart the Mux card or ZCOM system.
ZMON Error Messages ZMON Error Messages Message 245 - Card firmware file read error: corrupted record Explanation: Message issued when ZMON encounters a corrupt record in the firmware download file for the Mux card. The Mux will be unusable until the problem is rectified. Action: Replace the corrupt firmware file with a clean file and restart the Mux card with ZMON RESTART or restart ZCOM with ZMON COLD.
ZMON Error Messages ZMON Error Messages Message 249 - Card firmware object file not executable Explanation: Message issued when ZMON encounters a corrupt record in the firmware download file for the Mux card. The Mux will be unusable until the problem is rectified. Action: Replace the corrupt firmware file with a clean file and restart the Mux card with ZMON RESTART or restart ZCOM with ZMON COLD.
ZMON Error Messages ZMON Error Messages Message 260 - Card dumped to Explanation: When ZMON receives a message that causes the Mux to be reloaded and restarted, ZMON will attempt to dump the contents of the Mux memory to a file in the /var/opt/acc/dmp directory, if this directory exists. This message is displayed after ZMON has successfully dumped the contents of the interface memory to a file in this directory, and gives the dump file name.
ZMON Error Messages ZMON Error Messages Message 264 - Card error in upload: Explanation: Message is generated if ZMON is unable to read from the Mux card during the Mux memory dump. The dump sequence will be retried once, after resetting the interface. The problem is most likely to be a hardware or firmware related issue. It may be that the Mux software or firmware has failed in such a way that the upload for the dump is not possible.
ZMON Error Messages ZMON Error Messages Message 267 - Card bad dump file Explanation: When ZMON receives a message that causes the Mux to be reloaded and restarted, ZMON will attempt to dump the contents of the Mux memory to a file in the /var/opt/acc/dmp directory, if this directory exists. This message is displayed because ZMON has detected an error in the dump process, and the dump file is not complete. Action: None.
ZMON Error Messages ZMON Error Messages Message 270 Card dump can't fork to gzip: Explanation: When ZMON receives a message that causes the Mux to be reloaded and restarted, ZMON will attempt to dump the contents of the Mux memory to a file in the /var/opt/acc/dmp directory, if this directory exists. After ZMON has successfully created the dump file, it forks a child process to run gzip to compresses the dump file. This message is displayed when ZMON cannot create the child process.
ZMON Error Messages ZMON Error Messages Message 273 - Card Port Unknown port test failed Explanation: Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.
ZMON Error Messages ZMON Error Messages Message 276 - Card Port Line loop test failed Explanation: Message printed as a result of a selftest failure. The LED on the back of the card will be AMBER. The port will be unusable and all terminals configured on the port will be unavailable. Use the ZMNTR with the tta command to view terminals configured on the port—the tt command alone will not show the unavailable terminals.
ZMON Error Messages ZMON Error Messages Message 280 - ioctl (response) error: Explanation: This message is logged when ZCOM was unable to send a response to the LDM for ZMON request that requires a completion response. The message contains the reason why the IOCTL request failed. Action: Examine the reason for the failure and correct if possible. If this appears to be an internal defect of the product, report the problem to your nearest HP support representative.
ZMON Error Messages ZMON Error Messages Message 294 - Failed to get sema ID for download, error: Explanation: This message is displayed when ZMON failed to allocate a semaphore id used to synchronize the interface download. Action: Report this problem to Hewlett Packard. Message 295 - Download get semaphore failed error: Explanation: This message is displayed when ZMON is unable to allocate a semaphore id used to synchronize the interface download.
ZMON Error Messages ZMON Error Messages Message 302 - Card No ACC card at BC address address Explanation: There is no ACC card at the address in the Bus Converter . Action: Either correct the configuration in the ttgen .answ file, or correct the hardware configuration.
ZMON Error Messages ZMON Error Messages Action Reduce the memory you attempted to allocate to other resources (e.g. terminal tabels, message headers, trace buffer), or decrease the buffer size (zbufsize), in order to be able to increase the number of ACC buffers. Depending on the card type, you may need to specify this number using the zbufnbr interface tunable parameter. After re-running ttgen, you must restart the ZCOM subsystem.
ZMON Error Messages ZMON Error Messages Message 321 - Cannot open key file : Explanation: Message display when ZMON detects a problem in opening firmware keys file with the given name. Action: Replace the firmware keys file from a backup copy. If a backup copy of the file is not available, then the software may need to be re-installed. You will not be able to download this class of interface without access to this file.
ZMON Error Messages ZMON Error Messages Message 331 - Warning: Reached limit, , on the number of installed ACC cards that can be included in the bus-address checking. Explanation: The configuration you are attempting to initialize has more ACC cards defined than can be processed in an internal table which zmon uses to verify bus addresses. Action: Zmon will continue processing, but you may have other errors which cannot be detected.
ZMON Error Messages ZMON Error Messages Message 335 - Error: Missing bc1/bc bus address field. Input line: From helper script: Explanation: Output read form the script was , rather than bus converter address. Action: Verify that the script file has not been corrupted. If the problem recurs, contact HP support. Message 336 - Could not convert bc/bc1 value, to an integer.
ZMON Error Messages ZMON Error Messages Message 339 - Could not convert string card value, to an integer. Errno : Input line: from helper script: Explanation: The string was parsed as a card address from the input line from script . A file system error with explanation was diagnosed in attempting to convert it to an integer. Action: Verify that the script file has not been corrupted.
ZMON Error Messages ZMON Error Messages 160 Chapter 6
7 Chapter 7 ZNODE Error Messages 161
ZNODE Error Messages ZNODE Error Messages ZNODE Error Messages Message 100 - Out of memory Explanation: This message is issued when there is not enough memory in the system to complete the task requested of znode. Action: Free up some memory resources and try again. Message 102 - Couldn’t get / service from /etc/services Explanation: This message is issued when znode fails to obtain the znode name service from /etc/services.
ZNODE Error Messages ZNODE Error Messages Message 105 - Link unusable, couldn’t resolve linkname to an IP address Explanation: This message is issued when znode fails to resolve an internet address for the given hostname or IP address string. Action: Report this problem to your HP support representative. Message 107 - Couldn’t fork daemon process, error: Explanation: This message is issued when znode fails to fork a child.
ZNODE Error Messages ZNODE Error Messages Message 111 - Bad magic number from read Explanation: This message is issued when znode detects a read error signified by an erroneous magic number in the message buffer. Action: This problem may occur if the znode program is incompatible with the ZCOM driver (i.e., different versions). Make sure that the system has been regenerated and rebooted after it has been updated with the new ACC software.
ZNODE Error Messages ZNODE Error Messages Message 117 - Message len () doesn’t match result from write() Explanation: This message is issued when znode detects that there is a mismatch in message length between the length of the message buffer and the length resulted from the write operation performed on the LDM. Action: Report this problem to your HP support representative.
ZNODE Error Messages ZNODE Error Messages Action: Correct the problem with the given reason if possible. This device file can be created manually using mknod (refer to the ACC Installation and Configuration Guide, Appendix A on “Device Files”) with read and write access. If this also fails, contact your HP support representative. Message 124 - Can’t get the znode semaphore: Explanation: This message is issued when znode fails to obtain the znode semaphore.
ZNODE Error Messages ZNODE Error Messages Message 128 - Possible socket read truncation. Received %d bytes. Expected %d bytes. Explanation: A message received from a remote node was shorter than expected. Data may have been lost. This is an internal error. Action: Contact your local HP representative. Message 129 - Unknown source node %d. Explanation: The local node received a message from a node that is not configured in the local .answ file.
ZNODE Error Messages ZNODE Error Messages Message 132 - Bad packet revision %d received from node %d. Packet dropped. Explanation: The znode program on the remote node is not of a compatible revision with the znode program on the local node. All ZCOM nodes which communicate using the ZNODE functionality must have identical revision of the ACC software installed. Action: Update the remote node with the same version of the ACC products as the local node.
ZNODE Error Messages ZNODE Error Messages Message 135 - Possibly remote node %d is running old, incompatible znode software! Chapter 7 Explanation: The znode program on the remote node is not of a compatible revision with the znode program on the local node. Action: Update the remote node with the same version of the ACC products as the local node. (Note that the znode program is supplied with the ACC Base Software product as well as the X.25/ACC Bundled ACC product.
ZNODE Error Messages ZNODE Error Messages 170 Chapter 7
8 Chapter 8 TTGEN Error Messages 171
TTGEN Error Messages Introduction Introduction This chapter contains an explanation of the TTGEN error and status messages. TTGEN groups the problems it detects from a configuration file into four categories: The sections following this introduction provide lists of errors and other messages which may be produced by TTGEN. The severity code indicates whether that problem is a Disaster (value 3 or above), an Error (value 2), or a Warning (value 1).
TTGEN Error Messages Introduction Warning Messages Warning messages indicate minor configuration problems. TTGEN detects some non-critical configuration problems with the configuration file. This may cause unexpected results or unavailable functions during normal runtime operations. However, the system should otherwise operate normally without encountering a fatal error. If only warnings are detected, a ZCOM memory file and listing (if requested) will be produced.
TTGEN Error Messages TTGEN Summary Message TTGEN Summary Message TTGEN: END$ %d Disasters, %d Errors, %d Warnings (Severity 0) Explanation 174 Indicates how many disasters, errors, and warnings were found while running TTGEN. No memory image output file or listing will be created if there are any disasters or errors.
TTGEN Error Messages Disasters Disasters Disaster 02: Problem in running C Pre-processor. (Severity 3) Explanation TTGEN uses the C-Pre-processor (/opt/langtools/lbin/cpp) to pre-process the TTGEN configuration file. This error means that TTGEN cannot find cpp, or cpp returns an error (e.g., bad “#” statements, or can’t create temp files, etc.) Action: Try correcting the problem with cpp (e.g., run cpp on the configuration file without using TTGEN), or using the TTGEN “-n” option to by-pass cpp.
TTGEN Error Messages Disasters Disaster 06: “%s”(%d): Read error: %s (Severity 3) Explanation File read error (e.g., data corruption) of configuration file. Action: Make sure file and directory are properly set up and access permission is correct. Disaster 07: “%s”(%d): Comment closing pattern not found (Severity 3) Explanation File has incomplete comments (i.e., /* without closing */). Action: Check and rectify file for incomplete comments.
TTGEN Error Messages Disasters Disaster 12: “%s”(%d): ”%s” section in wrong sequence (Severity 3) Explanation Error in configuration file section sequence. The mentioned section should not be in here. END$ expected. Action: Remove or re-arrange the misplaced section. Disaster 13: “%s”(%d): Can’t allocate memory of %d bytes (Severity 3) Explanation TTGEN allocates virtual dynamic memory (through malloc) during compilation.
TTGEN Error Messages Errors Errors Error 114: “%s”(%d): Bad tracesize %s (range %d..%d). (Severity 2) Explanation The specified value of TRACESIZE is invalid. The value range of values is 0...16777216 (16M). Action: Change to an appropriate value. Error 115: "%s"(%d): Bad traceopt %s (range %d..%d). (Severity 2) Explanation The specified value of TRACEOPT is invalid. The value range of values is 0...FFFFFFFEh (or -2147483648…2147483647, except -1). Note that FFFFFFFFh (or -1) is not allowed.
TTGEN Error Messages Errors Error 119: “%s”(%d): Bad data value “%s” (range %d..%d) (Severity 2) Explanation The numeric value specified after the “BYTES” or “INT16” keyword (of LDATA statement) is invalid. Value should be in the specified range. Action: Use an appropriate value. Error 120: “%s”(%d): Unexpected word “%s”, line skipped (Severity 2) Explanation An specified word is found in the configuration file and is unknown to TTGEN. Action: Check for misspelling.
TTGEN Error Messages Errors Error 124: “%s”(%d): Total number of ZLUs > %d (Severity 2) Explanation Total number of ZLUs (i.e., TERMINAL-ZLU and PROGRAM-ZLU) exceeded the allowable limit. Action: Reduce number of TERMINAL-ZLU or PROGRAM-ZLU to an appropriate value. Error 125: “%s”(%d): Bad Logical-Term “%s” (range %d..%d) (Severity 2) Explanation Bad Logical-Term specified. The valid range of values is 1…65535 (ZCOM_MAXLTERM in /opt/acc/include/zcom/zcomsys.h).
TTGEN Error Messages Errors Error 129: “%s”(%d): Bad Transmit-Limit ”%s” (range %u..%u) (Severity 2) Explanation Specified value for Transmit-Limit is out of range. Action: Change to an appropriate value. Error 130:“%s”(%d): (Severity 2) Bad Unack-Limit “%s” (range %u..%u) Explanation Specified value for Unack-Limit is out of range. Action: Change to an appropriate value. Error 131: “%s”(%d): Bad Logical-Size “%s” (range %d..
TTGEN Error Messages Errors Error 134: “%s”(%d): Bad application number “%s” (range %d..%d) (Severity 2) Explanation Bad Logical Data application number. The specified “Application Number” field is out of range. Action: Change to an appropriate value. Error 135: “%s”(%d): Label name missing (Severity 2) Explanation Logical-Data label name missing. Each LOGICAL-DATA statement must have a unique label name specified. Action: Insert label name. Error 136: “%s”(%d): Bad data offset “%s” (range %d..
TTGEN Error Messages Errors Error 139: “%s”(%d): Size must be a multiple of %d (Severity 2) Explanation Logical-Data size must be a multiple of 8 bytes. In HP-UX 11.0 64-bit environment, data alignment to a 8-byte boundary is necessary for data structures with “long” or “pointer” types. To be consistent in both 32/64-bit environments, TTGEN requires the LOGICAL-DATA to have a size which is a multiple of 8 bytes. Action: Increase the byte size to multiples of 4 bytes.
TTGEN Error Messages Errors Error 144: “%s”(%d): Size must be a multiple of %d (Severity 2) Explanation Buffer-Pool size must be a multiple of 8 bytes. In the HP-UX 11.0 64-bit environment, data alignment to a 8-byte boundary is necessary for data structures with “long” or “pointer” types. To be consistent in both 32/64-bit environments, TTGEN requires BUFFER-POOL to have a size which is a multiple of 8 bytes. Action: Increase the byte size to a multiple of 8 bytes.
TTGEN Error Messages Errors Error 149: “%s”(%d): Bad slot number “%s” (range %d..%d) (Severity 2) Explanation Bad ACC interface slot number specified. The specified slot number is out of range. Action: Use an appropriate value. Error 150: “%s”(%d): File name missing (Severity 2) Explanation ACC interface protocol file name missing. The Interface-Definition statement must have a firmware download file specified. Action: Add appropriate firmware download file name (must use full path name).
TTGEN Error Messages Errors Error 154: “%s”(%d): Bad port mode “%s”, line ignored (Severity 2) Explanation Bad Port mode specified. The specified field in PORT statement has an unexpected value. The line is ignored in order to continue compilation. Action: Check for misspelling or syntax problem. Use an appropriate value. Error 155: “%s”(%d): Bad operating mode “%s”, line ignored (Severity 2) Explanation Bad Port operating mode specified. The specified field in PORT statement has an unexpected value.
TTGEN Error Messages Errors Error 158: “%s”(%d): Bad parity ”%s”, line ignored (Severity 2) Explanation Bad Port parity specified. The specified field in PORT statement has an unexpected value. The line is ignored in order to continue compilation. Action: Check for misspelling or syntax problem. Use an appropriate value. Error 159: “%s”(%d): Bad stop bits “%s”, line ignored (Severity 2) Explanation Bad Port stop bits specified. The specified field in PORT statement has an unexpected value.
TTGEN Error Messages Errors Error 165: “%s”(%d): SDLC mode cannot specify parity (Severity 2) Explanation Port SDLC mode cannot specify parity. The specified port configuration combination is invalid. Action: Use an appropriate configuration. Error 166: “%s”(%d): SYNC mode must specify parity (Severity 2) Explanation Port SYNC mode must specify parity. The specified port configuration combination is invalid. Action: Use an appropriate configuration.
TTGEN Error Messages Errors Error 171: “%s”(%d): Bad port ”%s” (range %d..%d), line ignored (Severity 2) Explanation The specified port number is out of range. The line is ignored in order to continue compilation. Action: Use an appropriate value. Error 172: “%s”(%d): Bad device name ”%s”, line ignored (Severity 2) Explanation The specified device name is defined in the ZCOMDEVICE file used by TTGEN (i.e., /opt/acc/cfg/zcomdevice).
TTGEN Error Messages Errors Error 177: “%s”(%d): Bad branch number “%s” (range %d..%d) (Severity 2) Explanation The specified value is out of range. Action: Use an appropriate value. Error 178: “%s”(%d): Bad workstation number “%s” (range %d..%d) (Severity 2) Explanation The specified value is out of range. Action: Use an appropriate value. Error 179: “%s”(%d): Bad area number “%s” (range %d..%d) (Severity 2) Explanation The specified value is out of range. Action: Use an appropriate value.
TTGEN Error Messages Errors Error 183: “%s”(%d): Previous PTERM has no following LTERM (Severity 2) Explanation A PTERM statement is used but without LTERM following it. This causes the defined physical terminal to become inaccessible. Action: Insert missing LTERM statement, or remove this unnecessary PTERM. Error 184: “%s”(%d): Must have a TERM or PTERM defined before (Severity 2) Explanation An LTERM statement is used but without a preceding PTERM or TERM.
TTGEN Error Messages Errors Error 188: “%s”(%d): More than %d terminals on this port (Severity 2) Explanation The number of physical terminals defined on this port exceeds the absolute limit for a port on this interface. Action: Remove the invalid terminal definition. Error 189: “%s”(%d): Bad node number “%s” (range %d..%d) (Severity 2) Explanation Specified node number is out of range. Action: Use an appropriate value.
TTGEN Error Messages Errors Error 194: “%s”(%d): Local node not specified (Severity 2) Explanation Local node number must be defined in NODE-DEFINITION section. Action: Insert “Local-Node” entry in “NODE-DEFINITION” section. Error 196: “%s”(%d): Missing storage label (Severity 2) Explanation A storage label name is missing after the “NAME” keyword in a “LDATA” statement. Action: Insert the appropriate label name. Error 197: “%s”(%d): Bad data offset “%s” (range %d..
TTGEN Error Messages Errors Error 200: “%s”(%d): Bad low-water mark “%s” (range %d..%d) (Severity 2) Explanation The specified flow control low-water mark is invalid. The valid range of values is 1…2147483645 (ZCOM_MAXQLIM in /opt/acc/include/zcom/zcomsys.h). Action: Change to an appropriate value. Error 201: “%s”(%d): Bad high-water mark “%s” (range %d..%d) (Severity 2) Explanation The specified flow control high-water mark is invalid.
TTGEN Error Messages Errors Error 207: “%s %d”: Illegal L2 window size “%d” in Select Word Explanation Action: Change to an appropriate value. Error 208: “%s %d”: Illegal L2 retry counter “%d” in Select Word Explanation Action: Change to an appropriate value. Error 209: “%s %d”: Bad PVC Logical Channel Nbr range (0..255) Explanation Action: Change to an appropriate value. Error 210: “%s %d”: Bad %s SVC Logical Channel Number range Explanation Action: Change to an appropriate value.
TTGEN Error Messages Errors Error 215: “%s %d”: Virtual Circuit trm defined before Link trm %d. Explanation Action: Re-order the terminal definitions. Error 216: “%s %d”: Online_fac_reg facility not supported in the %d ITU-T recommendation X.25 Explanation Action: Change to an appropriate value. Error 217: “%s %d”: TOA_NPI_addr facility not supported in the %d ITU-T recommendation X.25 Explanation Action: Change to an appropriate value.
TTGEN Error Messages Errors Error 222: “%s %d”: Number of two-way SVC's defined is less than the LCN subscription specified in the X.25 link term entry. Explanation Action: Change to an appropriate value. Error 223: “%s %d”: Number of outgoing SVC's defined is less than the LCN subscription specified in the X.25 link term entry. Explanation Action: Change to an appropriate value. Error 224: “%s”(%d): X.25 keyword “%s” not allowed in non-X.
TTGEN Error Messages Errors Error 229: “%s %d”: Calls_in_barred and Calls_out_barred are mutually exclusive, only one may be enabled! Explanation Action: Change to an appropriate value. Error 230: “%s %d”: Timer T1 must be greater than Timer T2! Explanation Action: Change to an appropriate value. Error 231: “%s %d”: Timer T3/T4 must be greater than Timer T1! Explanation Action: Change to an appropriate value. Error 232: “%s”(%d): Invalid X.
TTGEN Error Messages Errors Error 250: “%s”(%d): Illegal keyword %s for interface card %d. (Severity 2) Explanation See the section “Z7340A Tunable Parameters” in chapter 2 of the ACC Utilities Reference Guide for legal keywords. Action: Correct to an appropriate keyword. Error 251: “%s”(%d): Bad zbufsize %d (must be multiple of 16) (Severity 2) Explanation Zbufsize value must be a multiple of 16. Action: Change to an appropriate value. Error 252: “%s”(%d): Bad ttablenbr %s (range %d..
TTGEN Error Messages Errors Error 257: “%s”(%d): Bad bquota %s (range %d..%d) (Severity 2) Explanation Valid bquota range is 1-1M. Action: Change to an appropriate value. Error 258: “%s”(%d): Bad tsize %s (range %d..%d) (Severity 2) Explanation Valid tsize range is 1-32k. Action: Change to an appropriate value. Error 259: “%s”(%d): Bad frame mode "%s", line ignored (Severity 2) Explanation Valid frame modes are F4, F12, D3/4, ESF and F72. Action: Change to an appropriate value.
TTGEN Error Messages Errors Error 264: “%s”(%d): Bad Subchannel ITBS %s (range %d..%d) (Severity 2) Explanation Valid subchannel ITBS values are 0-63. Action: Change to an appropriate value. Error 265: “%s”(%d): Bad Subchannel timeslot number %s (range %d..%d) (Severity 2) Explanation Valid timeslot numbers are 0-31. Action: Change to an appropriate value. Error 266: “%s”(%d): Bad Subchannel timeslot fill mask %s (range %d..
TTGEN Error Messages Errors Error 271: “%s”(%d): Bad E1/T1 Port-Limit “%s” (range %u..%u) Explanation The E1T1-Port-Limit parameter is out of range. Action: Change to an appropriate value. Error 272: “%s”(%d): No E1/T1 cards defined, so Port-Limit (%u) must remain within the range %u..%u Explanation The Port-Limit parameter may exceed it’s normal limit. Action: Change to an appropriate value. Error 273: “%s”(%d): Port-Limit (%u) must remain within %u..
TTGEN Error Messages Errors Error 277: “%s”(%d): Minimum ‘%s’ Logical-data size required: %d. Explanation The “X25UDT” area has been defined too small. Action: Increase the size of the “X25UDT” area in the Configuration section. Error 278: “%s”(%d): Too many digits, %d, in non-ASCII octal value in Udata string: %s. Only %d max allowed. Last digit at char position %d in string (starting from 0) Explanation Action: Correct the Udata parameter.
TTGEN Error Messages Errors Error 283: “%s”(%d): Two Udata statements were detected for Term entry %d. Only one Udata is allowed per Term entry Explanation Action: Remove one of the Udata statements. Error 284: “%s”(%d): An Ldata statement can only be used after a Term or Lterm entry, or after an Ldata statement following a Term or Lterm entry. Explanation Action: Move the Ldata statement to the correct place in the configuration file.
TTGEN Error Messages Errors Error 289: "%s"(%d): Unrecognized subchannel keyword id: %d (Severity 2) Explanation The Subchannel definition has an unrecognized keyword. The keyword id number displayed is an internally used value. Action: Check for misspelling. Correct the spelling or remove the unsupported word. If the problem persists, this may indicate an internal software problem, please inform HP support center.
TTGEN Error Messages Warnings Warnings Warning 300: “%s”(%d): Ignored extra word “%s” (Severity 1) Explanation An extra, unexpected word is found and ignored. Action: Check for syntax problems, and remove extra word. Warning 301: “%s”(%d): Re-defining “%s” (Severity 1) Explanation The specified configuration is previously defined. Re-definition is not allowed. Remove any extraneous definitions. Action: Check for syntax problems, and remove duplicate definitions.
TTGEN Error Messages Warnings Warning 305: “%s”(%d): Too many “%s” (maximum %d), line ignored (Severity 1) Explanation More than 20 Logical-Data definitions in Configuration section. Action: Remove the invalid entry (or entries). Warning 306: “%s”(%d): System name not defined, using default (Severity 1) Explanation System name is not specified (in CONFIGURATION section), hence a default name is used. Action: Specify an appropriate system name or just use the default name.
TTGEN Error Messages Warnings Warning 310: “%s”(%d): No program ZLU defined (Severity 1) Explanation For normal uses, the system should have some program ZLUs defined. Action: Define “PROGRAM-ZLU” in “CONFIGURATION” section. Warning 311: “%s”(%d): Re-defining interface %d (Severity 1) Explanation The specified ACC interface card is previously defined. This line is ignored in order to continue compilation. Action: Check for correct interface number or remove duplicated ACC card definition.
TTGEN Error Messages Warnings Warning 315: "%s"(%d): Must have a PORT defined before (Severity 1) Explanation The "Port-Limit" keyword must follow a "Port" entry. The port limit defined is applicable to the preceding port definition. Action: Insert an appropriate "Port" definition before this line, or remove this unnecessary "Port-Limit" definition. Warning 316: “%s”(%d): Not used.
TTGEN Error Messages Warnings Warning 321: “%s”(%d): Re-defining interface %d port %d (Severity 1) Explanation The specified PORT configuration is previously defined. Action: Check previous PORT configuration and remove duplicates. Warning 322: “%s”(%d): Interface %d has undefined port(s) (Severity 1) Explanation The specified ACC interface card does not have all of its ports configured in Port-Definition section. This means those ports are unusable unless configured via the zport application routine.
TTGEN Error Messages Warnings Warning 326: “%s”(%d): Terminal name truncated to %d characters (Severity 1) Explanation The specified terminal name is too long and is truncated. Action: Simplify and shorten the terminal name to avoid truncation. Warning 327: “%s”(%d): No data specified “%s”, parameter ignored. Action: Correct this parameter. Warning 328: “%s %d”: The 1980 ITU-T recommendation X.25 does not support D-Bit negotiation. Action: Select 1988 X.25 support or do not use the D-bit.
TTGEN Error Messages Warnings Warning 334: “%s %d”: %s is larger than %s, using lower value Action: Change to an appropriate value if the default is not acceptable. Warning 335: “%s %d”: LCN value in Poll Word of SVC not 0, resetting Action: Set the LCN parameter of SVCs to zero. Warning 336: “%s %d”: Illegal “%s” size in PVC Select Word, using default value of %d. Action: Change to an appropriate value if the default is not acceptable. Warning 337: “%s %d”: SVC Select Word not zero.
TTGEN Error Messages Warnings Warning 343: “%s %d”: Invalid %s value (range %d..%d or %d..%d in bps), using default of %d. Action: Change to an appropriate value if the default is not acceptable. Warning 344: “%s %d”: CLR bit set but CNT bit is not set in the VC option word, setting CNT bit to 1. Action: Set the CNT bit in the VC option word. Warning 345: “%s”(%d): Application number should be 10 for a X.25 link terminal. Action: Change to the appropriate value.
TTGEN Error Messages Warnings 214 Chapter 8
9 Chapter 9 ZMASTERD Log Messages 215
ZMASTERD Log Messages ZMASTERD Log Messages ZMASTERD Log Messages zmast 100 - Out of memory Explanation: This message is displayed when there is not enough memory in the system to complete the task requested of zmasterd. Action: Free up some memory and rerun the last zmasterd command. zmast 101 - Launched daemon , Explanation: This message displays the name and the process ID of the daemon just launched by zmasterd.
ZMASTERD Log Messages ZMASTERD Log Messages zmast 105 - Couldn’t kill , , error: Explanation: This message is displayed when the command zmasterd deact or zmasterd stop is entered, and zmasterd’s attempt to terminate the specified daemon failed. Action: Report this problem to your HP support representative. zmast 106 - has been deactivated.
ZMASTERD Log Messages ZMASTERD Log Messages Action: None, if you don’t want to restart the ZCOM subsystem. However, if you want to stop and restart the ZCOM subsystem, do zmasterd stop first before issuing zmasterd again to restart the ZCOM subsystem. zmast 110 - Invalid daemon name entered. Explanation: This message is displayed when an invalid daemon name is entered for the zmasterd act or deact command. zmasterd currently supports the following daemons: pcapture, watch, zmlog, zmon and znode.
ZMASTERD Log Messages ZMASTERD Log Messages zmast 115 - Obtain zmasterd semaphore failure Explanation: This message is displayed when the semaphore service failed to respond to zmasterd’s request. Action: This is a zmasterd internal error. Report this problem to your HP support representative. zmast 116 - Command disallowed, zmasterd daemon is already active.
ZMASTERD Log Messages ZMASTERD Log Messages zmast 120 - Daemon , terminated with . Explanation: This message is displayed when zmasterd catches a terminate signal from one of the daemons that zmasterd monitors. refers to the terminating status of the terminated daemon. Action: None, zmasterd will relaunch the terminated daemon. However, if abnormal behavior is observed report this condition to your HP support representative.
ZMASTERD Log Messages ZMASTERD Log Messages zmast 125 - Daemon has been stopped. Explanation: This message is displayed when zmasterd stops a running daemon in response to the zmasterd stop command. Action: None. zmast 126 - does not exist in the system. Explanation: This message is displayed if the user specified daemon for the zmasterd command does not exist in the system. Action: Find out the reason why the specified daemon does not exist in the system, correct it and retry.
ZMASTERD Log Messages ZMASTERD Log Messages 222 Chapter 9
10 Chapter 10 PCAPTURE Log Messages 223
PCAPTURE Log Messages PCAPTURE Log Messages PCAPTURE Log Messages Some of the PCAPTURE messages are accompanied by an ASCII ZCOM reason string. Additional information regarding ZCOM error message routines can be found in ‘Chapter 2, “ZCOM Error Codes.” Message 1 - Protocol analyzer capture program Explanation: This message displays the revision code of the pcapture software. Action: None.
PCAPTURE Log Messages PCAPTURE Log Messages Message 5 - Bad ZREAD call, error: Explanation: This message is issued when an attempt to read from the pcapture ZLU has failed. This will be accompanied by a text reason message from the ZCOM subsystem. Action: Address the reason and run pcapture again. Note that pcapture will try zread again until the maximum number of reads has been exceeded. Restart pcapture.
PCAPTURE Log Messages PCAPTURE Log Messages Message 9 - Bad ZLTSTORE for label size , Error: Explanation: This message is issued when an attempt to get the logical terminal table storage has failed. This will be accompanied by a text reason message from the ZCOM subsystem. Action: Correct the problem with the indicated reason. Review the .answ file to make sure that the analyzer related configuration is correct.
PCAPTURE Log Messages PCAPTURE Log Messages Message 200 - ZLUs are already active Explanation: This message is displayed when the analyzer is already running on specified ZLU. Action: Correct the problem and retry if it is necessary. Message 201 - Too many analyzer sessions are already active Explanation: This message is displayed when there are already too many active analyzer sessions in the system and there is not enough room to allow an additional one.
PCAPTURE Log Messages PCAPTURE Log Messages Message 205 - ZLUs are already stopped Explanation: This message is displayed if the ZLUs are already stopped. Action: Must enable and activate the ZLUs first before they can be used. Message 206 - Cannot malloc() buffer for file capture data 228 Explanation: This message is displayed if there is not enough free memory in the system to allocate for the file buffer. Action: Correct the memory shortage problem and retry.
11 Chapter 11 WATCH Log Messages 229
WATCH Log Messages WATCH Log Messages WATCH Log Messages The following messages may be logged by the watch program via the zmlog logging mechanism: watch 2 - Cannot open /opt/acc/cfg/zcomdevice file Explanation: The /opt/acc/cfg/zcomdevice is not on the system or the file has incorrect permissions. Action: If the file exists, make sure it has read permissions set for root, and that watch is being started by a superuser. If the file does not exist, it must be either reinstalled, or recreated.
WATCH Log Messages WATCH Log Messages watch 6 - No MONITOR devices found in terminal table Explanation: There are no Term entries in the .answ file that correspond to the .tmem file that was used to bring up the ZCOM Mux subsystem. This means that the watch daemon may not be used. Action: Configure one MONITOR Term entry into the .answ file per Mux card.
WATCH Log Messages WATCH Log Messages 232 Chapter 11
12 Chapter 12 ZX25D System Messages 233
ZX25D System Messages Overview Overview The ACC X.25 subsystem is implemented through an X.25 protocol driver (zx25d). This driver uses the standard ZCOM error logging mechanism (zmlog) for logging informational and error messages. Refer to the ACC Utilities Reference Guide for more information on zmlog. The messages logged are split into four different classes based on the message number: Serious, Normal, Warning, and Protocol messages.
ZX25D System Messages CLASS: Serious 300-399 CLASS: Serious 300-399 zx25d 300 X.25 initialization failure; zinit failed with error <#>! Explanation: The ZCOM API routine zinit has unexpectedly failed due to the indicated ZCOM error during the initialization of the ACC X.25 subsystem. The X.25 subsystem will not be usable until this error is corrected. Action: Examine the specific reason for the failure and take corrective action as necessary.
ZX25D System Messages CLASS: Serious 300-399 zx25d 303 X.25 initialization failure; zevent_rcvr failed with error <#>! Explanation: The ZCOM API routine zevent_rcvr has unexpectedly failed due to the indicated ZCOM error during the initialization of the ACC X.25 subsystem. The X.25 subsystem will not be usable until this error is corrected. Action: Examine the specific reason for failure and take corrective action as necessary.
ZX25D System Messages CLASS: Serious 300-399 zx25d 305 Infinite loop detected in the PTT group linkage! The X.25 link ZLU <#> will not be usable. Explanation: While scanning the Physical Terminal Table for all Virtual Circuit ZLUs associated with the indicated X.25 link ZLU, the X.25 Protocol driver detected that it had gone into an infinite loop due to a corrupt PTT group linkage word. This could only occur as a result of an internal defect. Since the X.
ZX25D System Messages CLASS: Normal 400-499 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.
ZX25D System Messages CLASS: Normal 400-499 zx25d 402 zltstore() for ZLU <#> unexpectedly failed with error <#>. Explanation: Logical-Data 10 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.
ZX25D System Messages CLASS: Normal 400-499 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.
ZX25D System Messages CLASS: Normal 400-499 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.
ZX25D System Messages CLASS: Normal 400-499 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.
ZX25D System Messages CLASS: Normal 400-499 zx25d 410 The zcntl() on ZLU <#> to disable the X.25 link has unexpectedly failed with error <#>. Chapter 12 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.
ZX25D System Messages CLASS: Normal 400-499 zx25d 411 The zsend (type <#>) to the X.25 link ZLU <#> has unexpectedly failed with error <#>. Explanation: type type type type type 14 19 20 21 22 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.
ZX25D System Messages CLASS: Normal 400-499 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.
ZX25D System Messages CLASS: Normal 400-499 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.
ZX25D System Messages CLASS: Normal 400-499 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.
ZX25D System Messages CLASS: Normal 400-499 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.
ZX25D System Messages CLASS: Normal 400-499 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 System Messages CLASS: Normal 400-499 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.
ZX25D System Messages CLASS: Normal 400-499 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.
ZX25D System Messages CLASS: Normal 400-499 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.
ZX25D System Messages CLASS: Normal 400-499 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.
ZX25D System Messages CLASS: Normal 400-499 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.
ZX25D System Messages CLASS: Normal 400-499 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 System Messages CLASS: Normal 400-499 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 System Messages CLASS: Normal 400-499 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).
ZX25D System Messages CLASS: Normal 400-499 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! 258 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.
ZX25D System Messages CLASS: Warning 500-599 CLASS: Warning 500-599 zx25d 500 The X.25 subsystem is not up! Unable to process msg. Explanation: An X.25 related event message or a request from an application program (as a result of a call to one of the zx25...() routines) has arrived on the X.25 Protocol driver’s event handler, however, the X.25 subsystem is currently shutdown or has not been initialized. Therefore, the event message has been discarded. Action: No action is necessary.
ZX25D System Messages CLASS: Warning 500-599 zx25d 503 No Logical Channel Number configured for PVC ZLU <#>. An LCN will be dynamically selected for this PVC. Explanation: During the initialization of an X.25 link, the X.25 protocol driver detected a PVC ZLU entry that was incorrectly configured and did not contain a Logical Channel Number in the Poll word. The X.25 driver will automatically assign an unused LCN to this PVC ZLU (if available).
ZX25D System Messages CLASS: Warning 500-599 zx25d 505 There are more PVCs configured (<#>) than subscribed to (<#>) for the X.25 Link ZLU <#>. Explanation: During the initialization of an X.25 link, the X.25 protocol driver detected that there were more PVC ZLU terminal entries defined than were specified in the X.25 subscription parameters. That is, the value of the last_pvc parameter is less than the total number of PVC ZLUs defined.
ZX25D System Messages CLASS: Warning 500-599 zx25d 507 There are more one-way incoming SVCs configured (<#>) than subscribed to (<#>) for the X.25 Link ZLU <#>. Explanation: During the initialization of an X.25 link, the X.25 protocol driver detected that there were more one-way incoming (x25.svc.in) SVC ZLU terminal entries defined than were specified in the X.25 subscription parameters. That is, the value of the (last_insvc first_insvc) is less than the total number of one-way incoming SVC ZLUs defined.
ZX25D System Messages CLASS: Warning 500-599 zx25d 509 Link <#>: Call collision on VC ZLU <#> (LCN <#>) occurred. The inbound call has been ignored. Mux= <#>, Port= <#>, Subchannel= <#>. Explanation: An Incoming CALL packet arrived with the same LCN as an outbound CALL Request just sent. This condition is known as a call collision and as required by the ITU-T specification, the inbound call has been discarded (ignored). This message is only logged if the X.25 link is a DTE.
ZX25D System Messages CLASS: Warning 500-599 zx25d 512 Link <#>: Call received on SVC ZLU <#> (LCN <#>) in improper state (). The inbound call has been ignored. Explanation: Action: 264 An Incoming CALL packet arrived on an LCN whose current state indicates that this packet is not valid. For example, if an Incoming CALL arrived and was followed by a second Incoming CALL with the same LCN value, the second Incoming CALL packet would be invalid.
ZX25D System Messages CLASS: Warning 500-599 zx25d 513 Link <#>: Call confirm received on Idle LCN <#>. A clear has been issued on the SVC. Explanation: An inbound Call Connected packet arrived on an LCN that had not sent a Call Request packet. That is, this was a spurious packet on a Logical Channel that was not currently in use. A Clear Request has been automatically sent in response as required by ITU-T. Action: No action is necessary. This is an informational message.
ZX25D System Messages CLASS: Warning 500-599 zx25d 515 Link <#>: X.25 Timeout occurred during restart exchange. Mux= <#>, Port= <#>, Subchannel= <#>. Explanation: A Restart Request was transmitted, however, the remote DXE did not respond with a Restart Confirmation or Restart Indication packet within the time allowed (timer T10/T20). Most likely, the remote DXE is currently powered down or has not been enabled/initialized. The X.
ZX25D System Messages CLASS: Warning 500-599 zx25d 518 Link <#>: Buffer shortage on port. Mux= <#>, Port= <#>, Subchannel= <#>. Explanation: The MUX firmware was unable to find a free buffer to hold an inbound X.25 protocol packet or could not find a free buffer to transmit a protocol packet (e.g. RR). The packet has been lost. This may cause severe operational problems on the X.25 link.
ZX25D System Messages CLASS: Warning 500-599 zx25d 520 Link <#>: Call accept received on SVC ZLU <#> (LCN <#>) in improper state (). Explanation: An inbound Call Connected packet arrived on an LCN whose current state indicates that this packet is not valid. For example, if an Incoming CALL arrived and was followed by a Call Connected packet with the same LCN value, the Call Connected packet would be invalid. The parameter indicates the current state that the LCN is in.
ZX25D System Messages CLASS: Warning 500-599 zx25d 523 Link <#>: Reset confirm received on SVC ZLU <#> (LCN <#>) in improper state (). Explanation: An inbound Reset Confirmation packet arrived on an LCN whose current state indicates that this packet type is invalid. This would be true any time a Reset Confirmation packet arrived when a Reset Request has not been sent. The parameter indicates the current state that the LCN is in.
ZX25D System Messages CLASS: Warning 500-599 zx25d 526 Link <#>: Call user data too long (<#> bytes) on inbound call for SVC zlu <#> (LCN=<#>). Call cleared! Explanation: An Incoming CALL packet arrived with Call User data that exceeded the maximum permissible size of 128 bytes. The call has been automatically cleared as required by ITU-T. Action: No action is necessary. This is an informational message. zx25d 527 Link <#>: Call user data too long (<#> bytes) on inbound call for SVC zlu <#> (LCN=<#>).
ZX25D System Messages CLASS: Warning 500-599 zx25d 529 Link <#>: Facilities data too long (<#> bytes) in call accept for SVC zlu <#> (LCN=<#>). Call cleared! Explanation: An inbound Call Connected packet arrived with facilities data that exceeded the maximum permissible size of 109 bytes. The call has been automatically cleared as required by ITU-T. Action: No action is necessary. This is an informational message.
ZX25D System Messages CLASS: Warning 500-599 zx25d 533 Link <#>: Call user data too long (<#> bytes) in clear packet for SVC zlu <#> (LCN=<#>). Explanation: An inbound Clear Indication packet arrived with Call User data that exceeded the maximum permissible size of 128 bytes. A Clear Request has automatically been issued as required by ITU-T. Action: No action is necessary. This is an informational message. zx25d 534 Link <#>: Call user data not allowed in clear packet for SVC zlu <#> (LCN=<#>).
ZX25D System Messages CLASS: Warning 500-599 zx25d 536 Link <#>: Interrupt confirm pkt on SVC ZLU <#> (LCN <#>) in improper state (). Reset or Clear has been issued. Explanation: An inbound Interrupt Confirmation packet arrived on an LCN whose current state indicates that this packet type is invalid. This would be true any time an Interrupt Confirmation packet arrived when an Interrupt packet had not been sent. The parameter indicates the current state that the LCN is in.
ZX25D System Messages CLASS: Protocol 600-699 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.
ZX25D System Messages CLASS: Protocol 600-699 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 System Messages CLASS: Protocol 600-699 zx25d 606 Link ZLU <#> down due to transmitted FRMR. Mux= <#>, Port= <#>, Subchannel= <#>. Explanation: Action: 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.
ZX25D System Messages CLASS: Protocol 600-699 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.
ZX25D System Messages CLASS: Protocol 600-699 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 System Messages CLASS: Protocol 600-699 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 System Messages CLASS: Protocol 600-699 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.
ZX25D System Messages CLASS: Protocol 600-699 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.
ZX25D System Messages CLASS: Protocol 600-699 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.
ZX25D System Messages CLASS: Protocol 600-699 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= <#>.
ZX25D System Messages CLASS: Protocol 600-699 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 System Messages CLASS: Protocol 600-699 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.
ZX25D System Messages CLASS: Protocol 600-699 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.
ZX25D System Messages CLASS: Protocol 600-699 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 System Messages CLASS: Protocol 600-699 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.
ZX25D System Messages CLASS: Protocol 600-699 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 <#>.
ZX25D System Messages CLASS: Protocol 600-699 290 Chapter 12
13 Chapter 13 SNA/ACC Error Log Messages 291
SNA/ACC Error Log Messages SNACC Error Messages SNACC Error Messages snacc 00176: ERROR (0xB0): Attempted to do an operation to an ACC system that is shutdown. Explanation: The ZCOM system has been shutdown with the zmasterd utility. Action: Restart the ZCOM system with the zmasterd utility if needed. snacc 00177: ERROR (0xB1): An ACC ZLU is associated with a mux card in the ACC physical terminal table but SNA/ACC internal tables do not recognize this card.
SNA/ACC Error Log Messages SNACC Error Messages snacc 00179: ERROR (0xB3): Unable to open a primary ZLU. Function called: ; Return code: <#> Explanation: SNAplus failed to establish a ZCOM port because the zopen() function returned with an error. Action: Make sure the ZCOM system has started properly. Refer to Chapter 2, “ZCOM Error Codes,” for the ZCOM return code value. snacc 00180: ERROR (0xB4): Unable to the fetch the ZCOM header table.
SNA/ACC Error Log Messages SNACC Error Messages snacc 00183: ERROR (0xB7): Unable to fetch the ZCOM logical terminal table from the ACC subsystem. Function called: ; Return code: <#> Explanation: Failed to establish a ZCOM link. zinfo() returned a ZCOM error while retrieving information on a specific logical terminal table entry. Action: Refer to Chapter 2, “ZCOM Error Codes,” to determine the error condition. snacc 00184: ERROR (0xB8): Unable to setup callback function.
SNA/ACC Error Log Messages SNACC Error Messages Action: Start up the ZCOM subsystem if needed. Increase the ZCOM buffer-pool size (requires regeneration of the system). If the problem persists, contact your local HP support personal. snacc 00187: ERROR (0xBB): ACC Mux id number is not configured. Card id number requested: <#>. Max card id number configured: <#>. Explanation: Possible ttgen configuration problem. Action: Modify the ttgen configuration file if needed.
SNA/ACC Error Log Messages SNACC Error Messages Action: This is a transient problem and should clear up shortly. If the problem persists, contact your local HP support personal for assistance. snacc 00191: ERROR (0xBF): ACC port id number is out of expected range. Minimum possible id number: <#>. Maximum possible id number: <#>. Explanation: The port number range of the ACC 8 channel card is from zero to 7. The application must specify a value that is between zero and 7, inclusively.
SNA/ACC Error Log Messages SNACC Error Messages snacc 00195: ERROR (0xC3): ACC port is already in use. Explanation: Configuration problem. The application number and the Terminal type is defined incorrectly in the ACC ttgen configuration file. Action: Refer to SNA/ACC installation chapter for more information on how to create ACC ttgen configuration files to support the SNAplus2 subsystem. snacc 00196: ERROR (0xC4): ACC port configuration failed.
SNA/ACC Error Log Messages SNACC Error Messages snacc 00201: ERROR (0xC9): malloc() system call failed. errno value: <#>. Explanation: The SNA/ACC software calls the system malloc() routine to allocate system memory for internal tables. It is likely the system has exhausted it memory. Action: Add more system memory. If adding more system memory does not relieve the problem, there may be a software memory leakage problem. Contact your local HP support representative.
SNA/ACC Error Log Messages SNACC Error Messages Action: Check the SNAplus configuration for the length of the port’s dial string. snacc 00206: ERROR (0xCE): I/O error occurred. Function called: ; Return code: <#> Chapter 13 Explanation: Failed to close ZCOM port. The zcntl() function called to send a terminal disable request returned a ZCOM error.
SNA/ACC Error Log Messages SNACC Error Messages 300 Chapter 13
14 Chapter 14 ACC Kernel Log Messages 301
ACC Kernel Log Messages Overview Overview The ISDN/ACC kernel log messages are reported by the NS_LS_N2Z subsystem to the /usr/adm/nttl.LOG00 file. The messages can be displayed by running /usr/sbin/netfmt with /usr/adm/nettl.LOG00, for example: /usr/sbin/netfmt -f /usr/adm/nettl.LOG00 -t50 The messages logged are split into four different classes based on the message number: Disasters, Errors, Warning, and Informative messages.
ACC Kernel Log Messages ZISDN Kernel Driver: Disasters 1000 - 1999 ZISDN Kernel Driver: Disasters 1000 - 1999 zisdn 1022 ISDN: ACC initialization failure: zinit failed with error <#>! The ACC ISDN subsystem can not be used. Explanation: The ZCOM API routine zinit has unexpectedly failed due to the indicated ZCOM error during the initialization of the ISDN/ACC subsystem. The ISDN/ACC subsystem will not be usable until this error is corrected.
ACC Kernel Log Messages ZISDN Kernel Driver: Disasters 1000 - 1999 Action: Look for the error number in Chapter 2, “ZCOM Error Codes,” and take corrective action as necessary. If the problem persists and you are unable to correct the problem or the error indicates an internal failure, contact your HP support representative.
ACC Kernel Log Messages ZISDN Kernel Driver: Errors 2000 - 2999 ZISDN Kernel Driver: Errors 2000 - 2999 zisdn 2076 error <#>. ISDN: zread on ZLU <#> has unexpectedly failed with Explanation: The zread call failed with error. Action: Check the system error returned by the N2z_connect_req call and correct the problem. If you are unable to resolve the problem, contact your HP representative.
ACC Kernel Log Messages ZISDN Kernel Driver: Errors 2000 - 2999 zisdn 2080 ISDN: Unable to configure ISDN group <#>. The ISDN subsystem is not running! 306 Explanation: The ISDN/ACC subsystem is not running. Action: Start the ISDN/ACC subsystem first, then configure the group link. If you are unable to resolve the problem, contact your HP representative.
ACC Kernel Log Messages ZISDN Kernel Driver: Warning 3000 - 3999 ZISDN Kernel Driver: Warning 3000 - 3999 zisdn 3024 ISDN: Message arrived from an unrecognized module. Source ZLU = <#>, Sender ID = <#>, Receiver ID = <#>. Explanation: Warning! message from an unrecognized module, message is ignored. Action: No action. zisdn 3025 ISDN: The ACC ISDN subsystem is not up! Unable to process inbound message. Message ignored. Explanation: Warning! ISDN/ACC subsystem is not up, message is ignored.
ACC Kernel Log Messages ZISDN Kernel Driver: Informative 4000 - 4999 ZISDN Kernel Driver: Informative 4000 - 4999 zisdn 4016 ISDN: ACC X.25/ISDN subsystem started. Rev: B.03.02 Maximum number of ISDN group links is <#>. Explanation: Indicate the ISDN/ACC subsystem is started. Action: No action is necessary. This is an informational message. zisdn 4017 ISDN: The ACC ZCOM subsystem has been shutdown. The ACC ISDN subsystem is shutting down.
15 Chapter 15 ACC User Log Messages 309
ACC User Log Messages Overview Overview The ISDN/ACC user log messages are reported by the ISDN_ACC_USR subsystem to the /usr/adm/nttl.LOG00 file. The messages can be displayed by running /usr/sbin/netfmt with /usr/adm/nettl.LOG00, for example: /usr/sbin/netfmt -f /usr/adm/nettl.LOG00 -t50 The messages logged are divided into three groups: Call Daemon, X25 Daemon and Config Daemon. Within each group the messages are grouped again based on the message number.
ACC User Log Messages Call Daemon: Errors 2000 - 2399 Call Daemon: Errors 2000 - 2399 isdncalld 2002 Cannot init ZCOM. Exiting. Explanation: Failed on initializes ZCOM and creates a named ZLU for communicating the call daemon’s clients. Action: Verify that the ISDN/ACC subsystem is running by entering: ps -ef | grep isdncalld. Contact your HP representative. isdncalld 2003 Cannot init shared memory. Exiting. Explanation: Failed on initializes shared memory. Action: Contact your HP representative.
ACC User Log Messages Call Daemon: Errors 2000 - 2399 isdncalld 2045 Cannot map ZLU <#> to nai. Explanation: Unable to map the link’s zlu to its nai. Action: Contact your HP representative. isdncalld 2049 Cannot deactivate/disable ZLU <#>. Explanation: Failed on zcntl call. Action: Check the ZCOM error and correct the problem, or contact your HP representative if the problem is not resolved. isdncalld 2051 ---Conn Error: <#>-<#> Explanation: Connection error status.
ACC User Log Messages Call Daemon: Errors 2000 - 2399 isdncalld 2071 Bad zconfig status: <#>. Explanation: Failed on zconfig() call. Action: Contact your HP representative. isdncalld 2072 Zconfig error on term configuration: . Explanation: Failed on zconfig() call. Action: Contact your HP representative. isdncalld 2073 Zcntl error on term configuration: . Explanation: Failed on zcntl() call. Action: Contact your HP representative. isdncalld 2074 Zinfo error: .
ACC User Log Messages Call Daemon: Errors 2000 - 2399 isdncalld 2100 Fatal ZCOM read error: . Explanation: Failed on zread call. Action: Look for the error number in /opt/acc/include/zcom/ zcomsys.h, and take corrective action as necessary. If the problem persists and you are unable to correct the problem or the error indicates an internal failure, contact your HP support representative. isdncalld 2105 Zsend error on ZLU <#>: . Explanation: Failed on zsend call.
ACC User Log Messages Call Daemon: Errors 2000 - 2399 isdncalld 2126 Application not registered: Explanation: Application is not registered. Action: Register the application or contact your HP representative. isdncalld 2128 Find_port: outbound call disallowed. Explanation: Outbound call is disallowed for this cmap record. Action: Check the cmap configuration file and correct the problem, or contact your HP representative if the problem is not resolved.
ACC User Log Messages Call Daemon: Errors 2000 - 2399 isdncalld 2204 316 Link_add error. Explanation: Unable to find a free link slot. Action: Contact your HP representative.
ACC User Log Messages X25 Daemon: Errors 2400 - 2499 X25 Daemon: Errors 2400 - 2499 isdnx25d 2401 Explanation: Unable to initialize the shared memory. Action: Contact your HP representative. isdnx25d 2402 Can't init ZCOM. Exiting. Explanation: Unable to get the primary ZLU. Action: Contact your HP representative. isdnx25d 2403 Can't init ACU interface. Exiting. Explanation: Unable to initialize the communication with the call daemon. Action: Contact your HP representative.
ACC User Log Messages X25 Daemon: Errors 2400 - 2499 Action: isdnx25d 2413 mknod() error, errno=<#>. Explanation: Unable to create the group link’s device file. Action: Check the system error and correct the problem or contact your HP representative if the problem is not resolved. isdnx25d 2414 Cannot create file . Explanation: Unable to create file. Action: Contact your HP representative. isdnx25d 2415 Cannot open file .
ACC User Log Messages Calld Daemon: Informative 4001 - 4009 Calld Daemon: Informative 4001 - 4009 isdncalld 4001 Explanation: Indicate the ISDN call daemon is started. Action: No action is necessary. isdncalld 4008 Quit signal received. Explanation: Indicate the quit signal is received Action: No action is necessary. isdncalld 4009 Chapter 15 ISDN CALL DAEMON STARTED. ISDN CALL DAEMON EXITING. Explanation: Indicate the ISDN call daemon is exited. Action: No action is necessary.
ACC User Log Messages X25 Daemon: Informative 4490 - 4499 X25 Daemon: Informative 4490 - 4499 isdnx25d 4491 Explanation: Indicate the ISDN x25 daemon is started. Action: No action is necessary. This is an informational message. isdnx25d 4492 320 ISDN X25 DAEMON STARTED. ISDN X25 DAEMON EXITING ---------- Explanation: Indicate the ISDN x25 daemon is exiting. Action: No action is necessary. This is an informational message.
ACC User Log Messages Config Daemon: Informative 4501 - 4510 Config Daemon: Informative 4501 - 4510 isdnconfd 4501 shutdown. isdnconfd: The ISDN/ACC product has finished Explanation: Indicate the ISDN/ACC product has finished shutdown. Action: No action is necessary. This is an informational message. isdnconfd 4502 successfully. isdnconfd: The ISDN/ACC product has started up Explanation: Indicate the ISDN/ACC product has started. Action: No action is necessary. This is an informational message.
ACC User Log Messages Config Daemon: Errors 6000 - 6999 Config Daemon: Errors 6000 - 6999 If you use ISDN/SAM to create your configuration files, you should not receive any of the ISDN config daemon error messages. However, if you do receive an ISDN config daemon error or information message, it should be self explanatory. Try to correct the problem by examining the error message first. If you are still unable to solve the problem, contact your HP representative.
ACC User Log Messages Config Daemon: Errors 6000 - 6999 isdnconfd 6606 : Error occurred on ZCOM zread() call for startup response message. Zero-length message received. Runstring: Pid from fork: <#>. Chapter 15 Explanation: Failed on ZCOM zread() call. Action: Check the ZCOM error and correct the problem, or contact your HP representative.
ACC User Log Messages Config Daemon: Errors 6000 - 6999 324 Chapter 15
