NS 3000/iX Error Messages Reference Manual HP 3000 MPE/iX Computer Systems Edition 9 36923-90041 E1098 Printed in: U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents 1. CIERR Error Messages Network Services Environment Error Messages . . . . . . . . . . . . . . . . . 26 2. DSERR Error Messages 3. NS/NFTERR and NS/NFTWARN Messages 4. NFT/3000 Error Messages 5. NetIPC (SOCKERRS) Error Messages 6. Virtual Terminal (VT ERROR) Error Messages 7. Network Services Information Messages 8. Remote File Access Error Messages 9. Remote Process Management Error Messages 10. Network Transport Protocol (PMERR) Error Messages 11. FPARSE Error Messages 12.
Contents 19. Logging Location Codes Logging Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Transport Subsystem Logging . . . . . . . . . . . . . . . . . . . . . PARM Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Services Subsystem Logging . . . . . . . . . . . . . . . . . . . . . . Network IPC Subsystem Logging .
Figures Figure 19-1 . A Formatted Log Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310 Figure 19-2 . Class 3, A Non-Critical Transport Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320 Figure 19-3 . Logging Statistics Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 6
Tables Table 19-1. Logging Subsystems and Class Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311 Table 19-2. Network Transport Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313 Table 19-3. Network Service Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317 Table B-1. Subsystem Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface This manual contains most messages and errors generated by NS 3000/iX subsystems for the MPE/iX 6.0 release. What if the Error Is Not in this Manual If you have encountered an error that is not in this manual, here are some ideas on how you might find the error: • If it is an NMMGR error, or error from any of the Node Management Services Utilities, refer to Appendix A in Using The Node Management Services (NMS) Utilities.
CIERR Error Messages 1 CIERR Error Messages CIERR errors are reported by the Command Interpreter when an error is detected in the DSLINE, REMOTE, or NSCONTROL commands. (NETCONTROL is not included here; NETCONTROL has its own set of errors.) NOTE A CI error is displayed on $STDLIST during the execution of the command. Some CI errors display a pointer (^) to the error in the command.
CIERR Error Messages ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: INVALID ASCAT.NET.SYS MESSAGE CATALOG. 5002 CAUSE: The ASCAT.NET.SYS message catalog exists, but is not in the proper format. It may have been overwritten by a file that is not a properly prepared message catalog. ACTION: Check that the message sets of the ASCAT.NET.SYS catalog are correct. Run the MAKECAT utility to prepare the message catalog properly. MESSAGE: INTERNAL DS ERROR — COULD NOT ALLOCATE KEYWORD BUFFER.
CIERR Error Messages MESSAGE: NON-ALPHANUMERIC CHARACTER IN FILE NAME. 5009 CAUSE: There is a character in a file name that is not an alphabetic or a numeric character (or special character . or /). ACTION: Correct the file name and reissue the command. MESSAGE: EXPECTED , ; OR RETURN. 5010 CAUSE: An invalid delimiter was found after a parameter for a command option. ACTION: Correct the syntax error and reissue the command. MESSAGE: EXPECTED , ; OR RETURN.
CIERR Error Messages MESSAGE: TOO MANY PARAMTERS IN TRACE OPTION. 5017 CAUSE: More than the five defined parameters were specified in a DSLINE TRACE option. ACTION: Correct the syntax and reissue the command. MESSAGE: EXPECTED OR ‘. 5018 CAUSE: A string that begins with a quotation mark as a delimiter () or (‘) does not end with a closing quotation mark () or (‘). You must use the same delimiter for starting and ending the string. ACTION: Correct the syntax and reissue the command.
CIERR Error Messages MESSAGE: TOO MANY TRACE OPTIONS (MAXIMUM OF 10). 5025 CAUSE: There were more than 10 TRACE options specified in a DSLINE command. ACTION: Consolidate the TRACE options into less than 10, or break the DSLINE command into two or more DSLINE commands, each with less than 10 TRACE options. MESSAGE: DS/3000 DSLINE OPTION IS IGNORED FOR NS NODE. 5026 CAUSE: A DSLINE command for an NS node environment specified a DS/3000 option that is not supported for the NS node.
CIERR Error Messages MESSAGE: INTERNAL DS ERROR — COULD NOT GET PORT DST. 5032 CAUSE: A port data segment entry could not be allocated for the port between the CI and the Virtual Terminal server. ACTION: See “Submitting an SR” in appendix A of this manual. MESSAGE: INTERNAL DS ERROR — COULD NOT START VT. 5033 CAUSE: The Virtual Terminal service could not be initiated. ACTION: See “Submitting an SR” in appendix A of this manual. MESSAGE: INTERNAL DS ERROR — RECEIVED BAD PORT MESSAGE.
CIERR Error Messages MESSAGE: LOCAL VT SERVICE HAS BEEN ABORTED. 5037 CAUSE: An NSCONTROL ABORT has been issued. This immediately terminates all network services, including the local Virtual Terminal service. ACTION: Issue either an NSCONTROL START or an NSCONTROL START=VTL to start the local VT service, or wait until the service is started. (Only users with NM capability can use the NSCONTROL command.) MESSAGE: VIRTUAL TERMINAL SERVICE DETECTED AN ERROR.
CIERR Error Messages ACTION: None (the selected environment is closed). MESSAGE: ALL DSLINE OPTIONS BUT RESET ARE IGNORED. 5044 CAUSE: Other options besides RESET were specified in a DSLINE command. ACTION: None (the selected environment is closed). MESSAGE: DSLINE OPTION OVERRIDES PREVIOUS DSLINE OPTION. 5045 CAUSE: More than one DSLINE option was included in a REMOTE HELLO command. The last DSLINE option is used. ACTION: None (the REMOTE HELLO will be executed). MESSAGE: DSLINE OPTION IGNORED.
CIERR Error Messages ACTION: Consolidate options in the command, or break the command into two or more NSCONTROL commands. MESSAGE: EXPECTED SERVER PROGRM FILE NAME. 5051 CAUSE: The first parameter of a SERVER option in an NSCONTROL command was not a program name. ACTION: Correct the SERVER option and reissue the command. MESSAGE: EXPECTED MINIMUM NUMBER OF SERVERS (>=0 AND =32767).
CIERR Error Messages ACTION: Correct the LOG option and reissue the command. MESSAGE: INTERNAL DS ERROR — COULD NOT SEND CONTROL MESSAGE. 5060 CAUSE: The port message with the NSCONTROL information could not be sent from the CI to the DSDAD process. ACTION: See “Submitting an SR” in appendix A of this manual. MESSAGE: DSDAD.NET.SYS DOES NOT EXIST. 5061 CAUSE: The DSDAD.NET.SYS program file is missing. ACTION: Restore the DSDAD.NET.SYS file from the NS product tape. MESSAGE: INVALID CONTROL OPTION.
CIERR Error Messages MESSAGE: ABORT DOES NOT ACCEPT ANY PARAMETERS. 5073 CAUSE: Parameters were specified for an :NSCONTROL ABORT option. ACTION: Delete the parameters and reissue the command. MESSAGE: EXPECTED ONE OF USERS, SERVICES, SERVERS, OR ALL. 5074 CAUSE: The parameter for a SHOW option in an NSCONTROL command was not one of the defined choices. ACTION: Correct the SHOW command and reissue the parameters. MESSAGE: EXPECTED MAXIMUM NUMBER OF SERVERS (=> 0 and >32767).
CIERR Error Messages MESSAGE: EXPECTED GENERIC ENVIRONMENT ID. 5080 CAUSE: In a DSLINE RESET, the environment ID was not generic. ACTION: Correct the syntax and reissue the command. MESSAGE: INVALID VERSION OPTION: EXPECTED MOD. 5081 CAUSE: In a NSCONTROL VERSION command, an invalid option for VERSION was specified. VERSION=MOD is the only allowed option. ACTION: Correct the syntax and reissue the command. MESSAGE: REMOTE HELLO FAILED.
CIERR Error Messages MESSAGE: EXPECTED ENVIRONMENT ID OR NODE NAME 5087 CAUSE: The command REMOTE HELLO;DSLINE= was issued without an envid=nodename or node name. ACTION: Reissue the command, and include the envid=nodename or nodename following the equal sign (=). MESSAGE: REMOTE SESSION CANNOT LOGOFF WHILE FRA/RDBA IS ACTIVE. 5088 CAUSE: You cannot logoff until RFA/RDBA terminates. ACTION: Logoff when RFA/RDBA terminates. MESSAGE: ANOTHER PROCESS IS EXECUTING A REMOTE COMMAND IN THIS ENVIRONMENT.
CIERR Error Messages MESSAGE: ATTEMPT TO PLACE NFT SERVER INTO REQUESTORS ENVIRONMENT FAILED. 5104 CAUSE: Probable internal error. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: UNABLE TO CONTRACT NFT SERVER. 5105 CAUSE: Probable internal error. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: NO NFT SERVERS ARE CURRENTLY AVAILABLE. 5106 CAUSE: Maximum allowable limit of NFT Servers reached on system.
CIERR Error Messages ACTION: Try the command again. If it fails again submit an SR See Appendix A, “Submitting an SR,” of this manual. MESSAGE: INTERNAL ERROR — COULD NOT STORE VTTM ID IN DSTABLE. 5504 CAUSE: Internal resource error. ACTION: If this happens while running a program, prep or link the program with more stack space. If this happens after typing a command, see Appendix A, “Submitting an SR,” of this manual. MESSAGE: INTERNAL ERROR — COULD NOT STORE REQ. ID IN DSTABLE.
CIERR Error Messages Network Services Environment Error Messages Network Services Environment Error Messages Environment error messages are produced when an error is detected in the definition of an environment by a DSLINE or a REMOTE command. They are displayed on $STDLIST during the execution of the command, usually preceding a CI error or ENVIRONMENT message. These error messages are found in CATALOG.PUB.SYS, message set 16 (DS errors).
CIERR Error Messages Network Services Environment Error Messages ACTION: Terminate the service or services, and reissue the command. The DSLINE SHOW command will display which services are active for an environment. MESSAGE: CANNOT OPEN TRACE FILE filename. 627 CAUSE: A DSLINE TRACE=ON was issued, but the indicated trace file cannot be opened. ACTION: Check the parameters for the TRACE option, correct if in error, and reissue the command. MESSAGE: CANNOT CLOSE TRACE FILE filename.
CIERR Error Messages Network Services Environment Error Messages MESSAGE: ID OR NODE IN name IS GREATER THAN 16 CHARACTERS. 633 CAUSE: The first part of a (fully qualified) environment ID or node name is longer than the allowed 16 characters. ACTION: Shorten the name and reissue the command. MESSAGE: ID OR NODE IN name CONTAINS A NON-ALPHANUMERIC CHARACTER.
CIERR Error Messages Network Services Environment Error Messages MESSAGE: ORGANIZATION IN name IS GREATER THAN 16 CHARACTERS. 641 CAUSE: The third (organization) part of a (fully qualified) environment ID or node name is longer than the allowed 16 characters. ACTION: Correct the name and reissue the command. MESSAGE: ORGANIZATION IN name CONTAINS A NON-ALPHANUMERIC CHARACTER.
CIERR Error Messages Network Services Environment Error Messages ACTION: Wait for the remote session to be logged off, or log off the remote session (for example, by terminating any services using the environment). MESSAGE: CANNOT CHANGE NS NODE NAME FROM nodename TO GIVEN DOMAIN NAME. 687 CAUSE: The environment already exists with an NS node name. ACTION: First delete the old environment and then create a new environment with the domain node name.
DSERR Error Messages 2 DSERR Error Messages Environment error messages are produced when an error is detected in the definition of an environment by a DSLINE or a REMOTE command. They are displayed on $STDLIST during the execution of the command, usually preceding a CI error or ENVIRONMENT message. These error messages are found in CATALOG.PUB.SYS, message set 16 (DS errors). When an environment error is detected, the DSERR job control word is set to the error number.
DSERR Error Messages ACTION: Terminate the service or services, and reissue the command. The DSLINE SHOW command will display which services are active for an environment. MESSAGE: CANNOT OPEN TRACE FILE filename. 627 CAUSE: A DSLINE TRACE=ON was issued, but the indicated trace file cannot be opened. ACTION: Check the parameters for the TRACE option, correct if in error, and reissue the command. MESSAGE: CANNOT CLOSE TRACE FILE filename.
DSERR Error Messages MESSAGE: ID OR NODE IN name IS GREATER THAN 16 CHARACTERS. 633 CAUSE: The first part of a (fully qualified) environment ID or node name is longer than the allowed 16 characters. ACTION: Shorten the name and reissue the command. MESSAGE: ID OR NODE IN name CONTAINS A NON-ALPHANUMERIC CHARACTER. 634 CAUSE: The first part of a (fully qualified) environment ID or node name contains a character that is not alphabetic or numeric special characters @ # - . _ or ?.
DSERR Error Messages MESSAGE: ORGANIZATION IN name IS GREATER THAN 16 CHARACTERS. 641 CAUSE: The third (organization) part of a (fully qualified) environment ID or node name is longer than the allowed 16 characters. ACTION: Correct the name and reissue the command. MESSAGE: ORGANIZATION IN name CONTAINS A NON-ALPHANUMERIC CHARACTER.
DSERR Error Messages ACTION: Wait for the remote session to be logged off, or log off the remote session (for example, by terminating any services using the environment).
DSERR Error Messages 36 Chapter 2
NS/NFTERR and NS/NFTWARN Messages 3 NS/NFTERR and NS/NFTWARN Messages NFT messages may be distinguished from NFT/3000 messages in the following way: bit 2 of the DSCOPY result parameter or of the NFTERR JCW indicates the appropriate error set (on=NFT/3000; off=generic). The DSCOPYMSG intrinsic is able to determine the correct error set. In the descriptions of the following error messages and warnings, many references are made to qualifying error-message strings.
NS/NFTERR and NS/NFTWARN Messages ACTION: Verify that the source-computer name is correct, that the source computer is connected to the network, and that there are sufficient resources to establish a connection. Also, refer to the qualifying error string. Check the log file for PM errors. MESSAGE: UNABLE TO CONNECT TO TARGET NODE. 6 CAUSE: A connection could not be established to the computer where the target file resides.
NS/NFTERR and NS/NFTWARN Messages MESSAGE: COUNTER OFFER. 13 CAUSE: An internal error has occurred during negotiations between the source and target computers. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: REQUESTED DATA TYPE WAS REFUSED. 14 CAUSE: Consumer mainframe refused the data type offered by the producer mainframe. ACTION: Consult Using NS 3000/iX Network Services for the use of the ASC (ASCII) and BIN (binary) option. MESSAGE: REQUESTED RECORD WAS REFUSED.
NS/NFTERR and NS/NFTWARN Messages MESSAGE: TARGET RECORD SIZE IS INVALID. 20 CAUSE: Requested RSIZE is too large. ACTION: Specify a smaller record size. MESSAGE: TARGET FILE SIZE IS INVALID. 21 CAUSE: Requested FSIZE is too large. ACTION: Specify a smaller record size. MESSAGE: DUPLICATE TARGET FILE. 22 CAUSE: The target file exists and neither REPLACE nor OVERWRITE was specified. ACTION: Verify that the target file name is correct, and specify REPLACE or OVERWRITE.
NS/NFTERR and NS/NFTWARN Messages ACTION: Specify a command to copy the remainder of the files, and try again. MESSAGE: UNABLE TO PURGE TARGET FILE. 28 CAUSE: The existing target file could not be purged. ACTION: Refer to the qualifying file system error string to determine what to do. MESSAGE: INVALID TARGET FILE. 29 CAUSE: Check the target file name syntax and try again. ACTION: Refer to the qualifying file system error string to determine what to do. MESSAGE: UNABLE TO PURGE SOURCE FILE.
NS/NFTERR and NS/NFTWARN Messages MESSAGE: INVALID OR UNSUPPORTED TARGET DEVICE. 35 CAUSE: A request was made to send a file to a non-disk device. Such transfers are not supported. ACTION: Copy the file to disk on the target computer using DSCOPY and then to the non-disk device using a system utility program. MESSAGE: UNABLE TO CLOSE TARGET FILE. 36 CAUSE: An unexpected file system error occurred in closing the target file.
NS/NFTERR and NS/NFTWARN Messages MESSAGE: COMPRESSION WILL NOT BE DONE FOR THE CURRENT TRANSFER. 45 CAUSE: The source and/or the target computer does not support data compression (the COMPRESS option); or the transfer is local. File transfer will continue without data compression. ACTION: None. MESSAGE: UNABLE TO TURN ON TRACING. 46 CAUSE: Indicates that an internal error has occurred. File transfer will continue without tracing. ACTION: See Appendix A, “Submitting an SR,” of this manual.
NS/NFTERR and NS/NFTWARN Messages ACTION: Verify that the generic source file specification does match up with existing files. MESSAGE: INCOMING CONNECTION HAS GONE DOWN. 57 CAUSE: An incoming connection to an NFT server program has gone down for an unknown reason. ACTION: This error will appear only in a log file. See “Submitting an SR” in appendix A of this manual. MESSAGE: MOVE NOT SUPPORTED 58 CAUSE: Source mainframe does not support the MOVE option.
NS/NFTERR and NS/NFTWARN Messages MESSAGE: UNABLE TO RESTART TRANSFER 62 CAUSE: NFT attempted to restart a generic transfer and was unable to open the generic listf file, i.e., the file which contains the list of files to be transferred. This would occur if the file is opened exclusively or has been purged. ACTION: Make sure that the generic listf file (GENSETn) exists in the producer’s group and account and is not accessed exclusively. MESSAGE: SOURCE AND TARGET CHECKPOINTS DO NOT MATCH.
NS/NFTERR and NS/NFTWARN Messages MESSAGE: TARGET FILE BLOCK SIZE BEING CHANGED DUE TO FILE SYSTEM DIFFERENCES. 67 CAUSE: The block size for the Native Mode KSAM file has changed because of the file system differences. ACTION: None.
NFT/3000 Error Messages 4 NFT/3000 Error Messages NFT/3000 messages may be distinguished from other NFT messages in the following way: bit 2 of the DSCOPY result parameter or of the NFTERR JCW indicates the appropriate error set (on=NFT/3000, off=NFT). The DSCOPYMSG intrinsic is able to determine the correct error set. MESSAGE: NO ERRORS WERE DETECTED. 0 CAUSE: No errors occurred during the file transfer. ACTION: None. This is an informative message. MESSAGE: UNABLE TO OPEN NFT MESSAGE CATALOG.
NFT/3000 Error Messages MESSAGE: COMMAND LINE IS TOO LONG. 5 CAUSE: Input command length exceeded the allowed maximum (200 bytes). ACTION: Ensure that the command input file is correct. If the command is truly too long, global specifications may be used to shorten it. MESSAGE: CALL TO GENMESSAGE FAILED. 6 CAUSE: DSCOPYMSG intrinsic could not retrieve the specified error string from the NFT message catalog. ACTION: Make sure that NFTCAT2.NET.
NFT/3000 Error Messages MESSAGE: ! IS INVALID DELIMITER BETWEEN TARGET AND KEYWORDS. 13 CAUSE: Usually a typographical error. ACTION: Retype and reissue the command. MESSAGE: UNKNOWN KEYWORD: ! 14 CAUSE: Usually a typographical error. ACTION: Retype and reissue the command. MESSAGE: REMOTE ENVIRONMENT SPECIFIED BY USER DOES NOT EXIST. 15 CAUSE: The session associated with the specified node or environment cannot be found. Either the session was aborted externally or an internal error occurred.
NFT/3000 Error Messages MESSAGE: INVALID RECORD NUMBER FOR RESTART ID FILE. 24 CAUSE: Record number specified for restart ID file contains non-numeric characters or is too large. ACTION: Retype and reissue the command with the correct record number for the restart ID. MESSAGE: SCHAR AND ICHAR NOT ALLOWED AS GLOBAL SPECS 25 CAUSE: SCHAR and ICHAR may not follow “+” on the command line. ACTION: Specify these options for every transfer. MESSAGE: INVALID RESTART SPEC.
NFT/3000 Error Messages MESSAGE: ! OVERRIDES PREVIOUS RECORD TYPE. 36 CAUSE: Either FIX or VAR was specified when the other was already specified in the command line or globally. ACTION: None. MESSAGE: ! OVERRIDES PREVIOUS FILE TYPE. 37 CAUSE: Either SEQ or DIR was specified when the other was already specified in the command line or globally. ACTION: None. MESSAGE: ! OVERRIDES PREVIOUS DATA TYPE.
NFT/3000 Error Messages MESSAGE: VARIABLE LENGTH RECORDS CANNOT BE DIRECTLY ACCESSED. 46 CAUSE: The DIR option cannot be used on variable record files or with the VAR option. ACTION: Retry. MESSAGE: BUFFER MANAGER ERROR. 47 CAUSE: Probable internal error. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: ATTEMPT TO PLACE NFT SERVER BACK IN SYSTEM ENVIRONMENT FAILED. 48 CAUSE: Probable internal error. ACTION: See Appendix A, “Submitting an SR,” of this manual.
NFT/3000 Error Messages MESSAGE: UNABLE TO OBTAIN DATA SEGMENT FOR INTERNAL IPC. 54 CAUSE: Probable system resource problem. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: UNABLE TO FIND AFT ENTRY FOR INTERNAL IPC. 55 CAUSE: Probable internal error. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: CREATION OF INTERNAL IPC PORT FAILED. 56 CAUSE: Probable internal error. ACTION: See Appendix A, “Submitting an SR,” of this manual.
NFT/3000 Error Messages ACTION: Check file names and try the transfer again. MESSAGE: UNABLE TO CREATE GENERIC TEMP FILE. 65 CAUSE: NFT needs a temporary file to hold file names in a generic set. This error results when NFT is unable to create this file. The cause may be a lack of disk space, duplicate file name. ACTION: Check file space available, increase it if necessary (and possible). Check for temporary files named GENSET@. Purge these and try the transfer again.
NFT/3000 Error Messages MESSAGE: UNABLE TO CONTACT NFT SERVER 72 CAUSE: Probable internal error. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: UNABLE TO STORE NFT PORT ID IN PORT DICTIONARY. 73 CAUSE: Probable internal error. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: ERROR OCCURRED WHEN SETTING UP NFT SERVER. 74 CAUSE: Probable internal error. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: NO NFT SERVERS ARE CURRENTLY AVAILABLE.
NFT/3000 Error Messages MESSAGE: FILE PASSWORD IS TOO LONG. 81 CAUSE: Usually a typographical error. ACTION: Retype and reissue the command. MESSAGE: DEVICE NAME IS TOO LONG. 82 CAUSE: Usually a typographical error. ACTION: Retype and reissue the command. MESSAGE: INSUFFICIENT BUFFER SPACE FOR USER REQUEST. 84 CAUSE: Probable system resource problem. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: PM CAPABILITY IS REQUIRED FOR DEBUG.
NFT/3000 Error Messages MESSAGE: UNABLE TO OBTAIN INFO ON NEWLY CREATED SESSION. 91 CAUSE: Probable internal error. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: INVALID STRING FOLLOWING RIGHT BRACKET. 92 CAUSE: One or more invalid characters follow the right bracket in the logon part of the DSCOPY command. ACTION: Re-enter the command using the correct delimiters. MESSAGE: INVALID STRING FOLLOWING CLOSING QUOTE. 93 CAUSE: One or more invalid characters follow a closing quote.
NFT/3000 Error Messages MESSAGE: RESTART KEYWORD NOT ALLOWED IN DSCOPYI FILE. 104 CAUSE: User is attempting a restart from the DSCOPYI command file. ACTION: Only use the RESTART keyword when DSCOPYI has not been redirected to a file. MESSAGE: ERROR IN RETRIEVING RESTART ID NUMBER FROM RESTART ID FILE. 105 CAUSE: An error occurred while attempting to obtain the restart ID from the specified file. ACTION: Verify that the restart ID file name and record number are correct.
NFT/3000 Error Messages MESSAGE: TARGET FILE CANNOT RESIDE IN A HIERARCHICAL DIRECTORY. 114 CAUSE: Target file resides in HFS (hierarchical file system) namespace. ACTION: NFT is POSIX aware, not POSIX compliant, and does not support HFS files. MESSAGE: SOURCE FILE CANNOT BE BYTE STREAM RECORD TYPE. 115 CAUSE: Source file is a byte stream file. ACTION: NFT is POSIX aware, not POSIX compliant, and does not support byte stream files. MESSAGE: TARGET FILE CANNOT BE BYTE STREAM RECORD TYPE.
NFT/3000 Error Messages 60 Chapter 4
NetIPC (SOCKERRS) Error Messages 5 NetIPC (SOCKERRS) Error Messages NetIPC are (32-bit) integers that are returned in the result parameter of NetIPC intrinsics when the intrinsic execution fails. (A result of 0 indicates that the intrinsic succeeded.) In addition, both NetIPC errors and Transport Protocol errors are returned in the IPCCHECK intrinsic: NetIPC errors in the ipcerr parameter and Transport Protocol errors in the pmerr parameter. MESSAGE: SUCCESSFUL COMPLETION.
NetIPC (SOCKERRS) Error Messages ACTION: Verify that the proper bits are specified in the flags parameter. Bit numbering is from left to right (0–31). MESSAGE: INVALID OPTION IN THE opt RECORD. 8 CAUSE: An unsupported option was specified in the opt record, or a nonprivileged user attempted to specify a privileged option. ACTION: Check the options added to the opt record and remove or modify the option. Verify that the opt record was initialized correctly using INITOPT. MESSAGE: PROTOCOL IS NOT ACTIVE.
NetIPC (SOCKERRS) Error Messages ACTION: Contact your operator to see if the table can be expanded. MESSAGE: FORMAT OF THE opt RECORD IS INCORRECT. 18 CAUSE: NetIPC was unable to parse the specified opt record. ACTION: Check your INITOPT and ADDOPT calls. MESSAGE: ERROR DETECTED WITH MAXIMUM MESSAGE SIZE OPTION. 19 CAUSE: Maximum message size option in the opt record had an error associated with it (for example, too many bytes specified, invalid message size value).
NetIPC (SOCKERRS) Error Messages MESSAGE: INVALID NAME LENGTH. 28 CAUSE: Specified name length was too large or negative. ACTION: Check your name length parameter. Shorten the name if necessary. MESSAGE: INVALID DESCRIPTOR. 29 CAUSE: Specified descriptor is not a valid socket, connection, or destination descriptor. ACTION: Check the value being specified. MESSAGE: UNABLE TO NAME CONNECTION SOCKETS.
NetIPC (SOCKERRS) Error Messages ACTION: Shut down unused sockets, call IPCNAMERASE on any sockets that no longer need to be looked up, or get given sockets. See Appendix A, “Submitting an SR,” of this manual. MESSAGE: NAME NOT FOUND. 37 CAUSE: Name was not previously specified in an IPCNAME or IPCGIVE call; IPCNAMERASE or IPCGET was previously issued with the name; or socket no longer exists. ACTION: Check names specified, make sure names were properly agreed on, determine if a timing problem exists.
NetIPC (SOCKERRS) Error Messages MESSAGE: UNABLE TO INTERPRET RECEIVED PATH REPORT. 46 CAUSE: Unable to interpret the information returned by the remote socket registry process regarding the looked-up socket. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: INVALID MESSAGE RECEIVED FROM REMOTE SERVER. 47 CAUSE: The message received from the remote registry process does not appear to be a valid socket registry message. ACTION: See Appendix A, “Submitting an SR,” of this manual.
NetIPC (SOCKERRS) Error Messages MESSAGE: CALL WOULD BLOCK WHILE USING SELECT ASYNCHRONOUS NODE. 56 CAUSE: The no wait call would block because the socket is not ready for desired operation. ACTION: Re-initiate the call or call the select to assure socket is ready for desired operation. MESSAGE: ATTEMPT TO EXCEED LIMIT OF NOWAIT SENDS OUTSTANDING. 57 CAUSE: User tried to send data too many times in nowait mode without calling IOWAIT. ACTION: Call IOWAIT to complete a send. The limit is 7.
NetIPC (SOCKERRS) Error Messages MESSAGE: CONNECTION ABORTED BY LOCAL PROTOCOL MODULE. 65 CAUSE: Local protocol module encountered some error which caused it to abort the connection. ACTION: Call IPCSHUTDOWN to clean up your end of the connection. See Appendix A, “Submitting an SR,” of this manual. MESSAGE: INVALID CONNECTION DESCRIPTOR. 66 CAUSE: Supplied value is not that of a valid VC socket (connection) descriptor. ACTION: Check the value being given. MESSAGE: CONNECTION FAILURE DETECTED.
NetIPC (SOCKERRS) Error Messages MESSAGE: INVALID TIMEOUT VALUE. 76 CAUSE: Value specified for the timeout is negative. ACTION: Modify the value. MESSAGE: INVALID WAIT/NOWAIT MODE. 77 CAUSE: Mode of socket cannot be used. ACTION: Use IPCCONTROL to specify correct mode. MESSAGE: TRACING NOT ENABLED. 78 CAUSE: Attempted to turn off trace when tracing was not on. ACTION: Remove the call. MESSAGE: INVALID TRACE FILE NAME. 79 CAUSE: Requested trace file name is not valid.
NetIPC (SOCKERRS) Error Messages MESSAGE: PROCESS HAS NO LOCAL SOCKET DATA STRUCTURES. 84 CAUSE: IPCCHECK was called, but the user had no sockets or destination descriptors, and therefore no data structure for retaining error codes. ACTION: None, but no NetIPC or protocol module errors are available. MESSAGE: INVALID SOCKET ERROR NUMBER. 85 CAUSE: IPCERRMSG was called with an invalid NetIPC error code. ACTION: Check the value being passed. MESSAGE: UNABLE TO OPEN ERROR CATALOG SOCKCAT.NET.SYS.
NetIPC (SOCKERRS) Error Messages ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: RECEIVED AN UNSOLICITED REPLY. 95 CAUSE: Internal error. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: INTERNAL BUFFER MANAGER ERROR. 96 CAUSE: Attempted use of the buffer manager by NetIPC or the protocol module resulted in an error. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: INVALID DATA SEGMENT INDEX IN VECTORED DATA.
NetIPC (SOCKERRS) Error Messages ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: NO REPLY RECEIVED. 105 CAUSE: Internal error. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: ADDRESS CURRENTLY IN USE BY ANOTHER SOCKET. 106 CAUSE: Address being specified for use is already being used. ACTION: Stop application or choose a different socket address. MESSAGE: TRANSPORT IS GOING DOWN. 107 CAUSE: The transport is being shut down.
NetIPC (SOCKERRS) Error Messages MESSAGE: INVALID SOFTWARE INTERRUPT PROCEDURE LABEL. 113 CAUSE: Procedure label passed when enabling software interrupts is invalid. ACTION: Check the PLABEL you are passing. MESSAGE: CREATION OF SOCKET REGISTRY PROCESS FAILED. 114 CAUSE: Socket registry program missing. ACTION: Contact your Hewlett-Packard representative for assistance. MESSAGE: DESTINATION UNREACHABLE. 116 CAUSE: The transport was unable to route the packet to the destination.
NetIPC (SOCKERRS) Error Messages MESSAGE: INVALID NUMBER OF EVENTUAL OPT RECORD ENTRIES. 126 CAUSE: Number of option entries is either too high or negative. Either an internal restriction or a user mistake. ACTION: Remove the cause by making the number positive or smaller in value. MESSAGE: UNABLE TO READ ENTRY FROM OPT RECORD. 127 CAUSE: The option record indicates that the entry is not valid or the buffer supplied by the user was too small to hold all of the data.
NetIPC (SOCKERRS) Error Messages ACTION: Check the values being placed in the opt record. MESSAGE: RESET EVENT OCCURRED ON X.25 CONNECTION. 146 CAUSE: An unsolicited reset packet was received. ACTION: Use IPCCONTROL (request 12) to examine the cause/diagnostic field. The connection is still up and operational but some data may have been lost. MESSAGE: COULD NOT OBTAIN A SEMAPHORE. 151 CAUSE: The attempt to obtain a semaphore before sending a message to the protocol module failed.
NetIPC (SOCKERRS) Error Messages MESSAGE: INCOMPATIBLE WITH PROTOCOL STATE. 160 CAUSE: The user requested an operation which is not supported by the protocol module. ACTION: Verify the sequence of intrinsic calls. MESSAGE: X.25 PERMANENT VIRTUAL CIRCUIT DOES NOT EXIST. 162 CAUSE: No PVC configured. ACTION: Check the configuration file for X.25. MESSAGE: PERMANENT VIRTUAL CIRCUITALREADY ESTABLISHED. 163 CAUSE: A connection request was issued on a PVC which is in use by another process.
NetIPC (SOCKERRS) Error Messages MESSAGE: INVALID FACILITY FIELD. 171 CAUSE: For IPCCONNECT, IPCRECVCN, or IPCRECV, the opt parameter facility field length is wrong. ACTION: Check the facility field length. The length must be 1 to 109 bytes inclusive. MESSAGE: CONNECTION MUST BE REJECTED. 172 CAUSE: An IPCCONTROL request 9, accept the connection, cannot be performed. ACTION: Use IPCCONTROL request 15 to reject the connection. MESSAGE: MORE DATA IS ABAILABLE. 173 CAUSE: Warning message.
NetIPC (SOCKERRS) Error Messages 78 Chapter 5
Virtual Terminal (VT ERROR) Error Messages 6 Virtual Terminal (VT ERROR) Error Messages MESSAGE: RESOURCE NOT RELEASED ON TERMINATION. 1 CAUSE: During the termination process a resource was not released with a good disposition. ACTION: None; this is not a severe problem since MPE forces cleanup upon process termination. MESSAGE: INVALID STATUS FOUND. 2 CAUSE: Conflicting states existed in the VT status mask. The transition to a new state could not be made.
Virtual Terminal (VT ERROR) Error Messages MESSAGE: UNEXPECTED/BAD RESPONSE FROM VT. 7 CAUSE: The VT “partner” on the remote machine could not handle a request and has generated an unexpected protocol error. This is the result of Virtual Terminal error 4, 5 or 6 above. ACTION: One of your commands was probably not executed correctly. Terminate the session and re-issue the commands. If the problem persists, verify VT versions and/or submit SR. MESSAGE: VT SERVER NOT ADOPTED.
Virtual Terminal (VT ERROR) Error Messages MESSAGE: CR/LF SWITCH FAILED. 16 CAUSE: The File System did not honor the request to alter the issuing of Line Feed on receipt of a Carriage Return. ACTION: This may affect the actions of the remote application program: if problems occur, reestablish the remote session. MESSAGE: SET READ TIMEOUT FAILED. 17 CAUSE: Setting of a timed read failed.
Virtual Terminal (VT ERROR) Error Messages MESSAGE: SET DRIVER MODE FAILED. 25 CAUSE: The File System did not alter the setting of the driver/terminal handshake mode. ACTION: Terminate the remote program. MESSAGE: TERMINAL NOT ALLOCATED. 26 CAUSE: The terminal could not be allocated for access. ACTION: Check the MPE configuration and retry the remote session. MESSAGE: SET TERMINAL TYPE FAILED. 27 CAUSE: The terminal type was not reset as requested. ACTION: Terminate the remote program and rerun it.
Virtual Terminal (VT ERROR) Error Messages ACTION: Reestablish remote session. MESSAGE: CANNOT ACCESS SESSION DEVICE. 34 CAUSE: The session device is either incorrectly configured, is not a terminal, or is not accessible through the file system. ACTION: Check the above and reattempt logon. MESSAGE: VT INITIALIZATION FAILED. 35 CAUSE: VT could not initialize itself because of an internal error or a resource shortage.
Virtual Terminal (VT ERROR) Error Messages ACTION: Attempt to re-logon to the remote machine. MESSAGE: REMOTE NOT RESPONDING, CONNECTION CLOSED. 42 CAUSE: The remote VT closed the connection. The session has been terminated. ACTION: Attempt to re-logon to the remote machine. MESSAGE: VT COULD NOT SECURE BUFER SPACE. 43 CAUSE: There is insufficient buffer space because of a shortage of table space or system tables. The VT could not be started. ACTION: Reattempt the command.
Virtual Terminal (VT ERROR) Error Messages ACTION: Try the remote request later. MESSAGE: VT TERMINATED, COULD NOT FOPEN TERMINAL. 51 CAUSE: A File System error has occurred; the terminal was not accessible by the VT program. ACTION: Save the Node Management logfile, and if the problem recurs, see Appendix A, “Submitting an SR,” of this manual. MESSAGE: VT TERMINATED, INVALID DEVICE FOR SESSION. 52 CAUSE: Your session device is not an acceptable MPE session device.
Virtual Terminal (VT ERROR) Error Messages 86 Chapter 6
Network Services Information Messages 7 Network Services Information Messages These messages, displayed on $STDLIST during the execution of a command, give the user information about the environment(s) affected by the command. They are held in CATALOG.PUB.SYS, message set 16 (DS set). No action is required for these messages. MESSAGE: ENVIRONMENT envum: envid. 500 CAUSE: The defined or affected environment has been assigned an environment number envum and environment ID envid.
Network Services Information Messages MESSAGE: PLEASE ANSWER YES OR NO: 504 CAUSE: A question (such as ABORT REMOTE SESSION) has been asked, and the user entered a response other than YES or NO. This prompt is displayed until the user replies YES, Y, No, or N. ACTION: Enter either YES or NO in response to this message. MESSAGE: KILL RPM PROCESS ON envid? 505 CAUSE: A DSLINE CLOSE has been issued for an environment that includes an RPM-created process. Envid is the environment ID for the environment.
Network Services Information Messages MESSAGE: TRACE FILE FOR ALL SERVICES TO envid IS filename. 510 CAUSE: A DSLINE with a TRACE=ON or TRACE=OFF option was executed. These messages indicate which service to what environment is being (or has been) traced, and the fully qualified name of the trace file. One TRACE message is displayed for each TRACE option in the command.
Network Services Information Messages command. If a DSLINE with a generic environment ID turns tracing on or off for a set of environments, the TRACE FILE FOR ALL SERVICES TO envid IS filename message is displayed for each environment. ACTION: This is an informative message. MESSAGE: TRACE FILE FOR RPM TO envid IS filename. 515 CAUSE: A DSLINE with a TRACE=ON or TRACE=OFF option has been executed.
Remote File Access Error Messages 8 Remote File Access Error Messages Remote File Access errors are returned only through the FCHECK intrinsic. The FCHECK intrinsic is called when: • a file system intrinsic (such as FOPEN) encounters an error • during remote file access The following error codes refer to Network Service Remote File Access over Local Area Network (NS-Compatible) links. MESSAGE: HIERARCHICAL OR BYTE STREAM FILES NOT ALLOWED THROUGH RFA. UNIMPLEMENTED FUNCTION.
Remote File Access Error Messages MESSAGE: ILLEGAL USE OF NODE NAME. DS LINE WAS NOT OPENED WITH A USER :DSLINE COMMAND. (Actual Message Displayed) 214 CAUSE: The node does not exist or the specified node name is invalid. ACTION: Correct the node name. MESSAGE: NOT ENOUGH STACK SPACE FOR RFA. INSUFFICIENT AMOUNT OF USER STACK AVAILABLE. (Actual Message Displayed) 217 CAUSE: The MPE PREP command allocated the default ;MAXDATA or STACK values to the program, which are too small.
Remote File Access Error Messages MESSAGE: LOCAL COMMUNICATION LINE NOT OPENED BY OPERATOR. LOCAL COMMUNICATION LINE WAS NOT OPENED BY OPERATOR. (Actual Message Displayed) 240 CAUSE: The RFA/RDBA service has not been started. ACTION: Use the NETCONTROL START command to open the line. MESSAGE: INTERNAL ERROR. INTERNAL DS SOFTWARE ERROR ENCOUNTERED. (Actual Message Displayed) 242 CAUSE: This is an internal error. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Remote File Access Error Messages 94 Chapter 8
Remote Process Management Error Messages 9 Remote Process Management Error Messages RPM errors are (32-bit) integers that are returned in the result parameter of the intrinsics RPMCREATE, RPMKILL, RPMCONTROL, and RPMGETSTRING when the intrinsic execution fails. (A result of 0 indicates that the intrinsic succeeded.) There are two ranges of RPM errors returned by the HP 3000 implementation of RPM. The first range (0–99) includes generic RPM errors.
Remote Process Management Error Messages MESSAGE: ILLEGAL OPTION FORMAT. 5 CAUSE: The opt parameter in an RPMCREATE call is not formatted correctly. ACTION: Correct the opt format; use the INITOPT and ADDOPT intrinsics to format the opt array. MESSAGE: INVALID LOGIN. 6 CAUSE: This may be caused by several conditions relating to the login (Env) and password parameters of RPMCREATE: • The login parameter is syntactically incorrect for the remote machine.
Remote Process Management Error Messages 1. The (pd) value was not generated by PRM on the remote node. This would happen if the program descriptor were incorrect or corrupted, or if the RPMCREATE that was supposed to return the descriptor failed. 2. The (pd) value was generated for a program on the remote node, but the program terminated itself, or was terminated by an abort or an RPMKILL.
Remote Process Management Error Messages MESSAGE: PROGRAM ACCESS ERROR. 11 CAUSE: The program to be created by an RPMCREATE could not be accessed. This may be due to one of the following reasons: 1. The program file is secured against access from the login user and account. 2. The program file has a lockword that was not specified in progname. 3. The program name in progname is not syntactically correct ACTION: Depending on the cause: 1.
Remote Process Management Error Messages MESSAGE: UNSUPPORTED OPTION. 16 CAUSE: A legal option specified in the opt parameter of the RPMCREATE is not supported by the remote RPM software. ACTION: Modify the option, or update the remote RPM software to a version that supports the option. MESSAGE: RPMCREATE LENGTH ERROR. 17 CAUSE: An RPMCREATE resulted in a message that could not be handled by the remote node RPM software.
Remote Process Management Error Messages ACTION: Check that the parameter specifying string length is set to a positive integer in the RPMGETSTRING intrinsic. If the string length is positive, and you are getting the error anyway, submit an SR. See Appendix A, “Submitting an SR,” in this manual. MESSAGE: REMOTE SON ABORTED. 22 CAUSE: The remote process aborted abnormally. ACTION: Check the remote program to ascertain what caused the premature termination. MESSAGE: INSUFFICIENT STACK SPACE.
Remote Process Management Error Messages MESSAGE: RPM OR PTOP PROCESS AT LOCATION. 106 CAUSE: An RPM or PTOP created process already exists in the remote session specified by the location parameter. Because of the design of the RPM and PTOP services, only one RPM or PTOP process can exist in a remote session. ACTION: Terminate the first RPM or PTOP process, or change the location to a different remote session.
Remote Process Management Error Messages MESSAGE: RPMDAD DEAD ERROR. 112 CAUSE: RPMDAD is terminating and exiting the session because the session has been aborted or because all sons created by RPM have terminated. ACTION: Try again. A new RPMDAD and a new session are created at the next RPMCREATE request. MESSAGE: BAD RPMCONTROL STATE. 113 CAUSE: RPMCONTROL was unable to suspend the remote process.
Network Transport Protocol (PMERR) Error Messages 10 Network Transport Protocol (PMERR) Error Messages The following errors are returned by Transmission Control Protocol (TCP) as the 32-bit integer “PMERR” parameter in calls to IPCCHECK. They are also found in the “PARM” field of the TCP Statistics, PM Deactivated and PM Deactivated with Error logging entries. NOTE The Network Transport is technically not part of network services; it is a subsystem of the NS links.
Network Transport Protocol (PMERR) Error Messages ACTION: None. For notification purposes only. MESSAGE: SHUTDOWN COMPLETE 21 CAUSE: The graceful release shutdown for the connection has been completed. The connection has been released. ACTION: None. For notification purposes only. MESSAGE: IPC SHUTDOWN COMPLETE 22 CAUSE: The connection has been terminated by IPC. ACTION: None. For notification purposes only.
Network Transport Protocol (PMERR) Error Messages indicates warning.) Consult MPE/iX operating system error documentation if available, submit an SR with this information if necessary. MESSAGE: CONNECTION ENTRY ALLOCATION FAILED -20 CAUSE: TCP was unable to allocate a connection entry. Potential reasons include running out of memory space for resident data structures, table management failure, or TCP internal error. ACTION: Enable class 2 logging for NS Transport if not previously enabled.
Network Transport Protocol (PMERR) Error Messages MESSAGE: INCONSISTENT IPC STATE -40 CAUSE: A TCP operation was attempted which conflicts with expected (IPC/BSD sockets) operation in this state. ACTION: This is an internal error between TCP and the upper layer protocol (IPC or BSD Sockets). You should submit an SR on this defect. Please include the nature of the call being made, and some indication of the current connection state.
Network Transport Protocol (PMERR) Error Messages ACTION: This is an internal error between TCP and the upper layer protocol (IPC or BSD Sockets). You may wish to submit an SR for this defect. Please include the nature of the call being made, and some indication of the current connection state. If possible please include a copy of the program and the input which caused the error to aid resolution of the problem.
Network Transport Protocol (PMERR) Error Messages MESSAGE: RETRANSMISSION RETRIES EXCEEDED -80 CAUSE: A TCP connection did not receive any acknowledgment from the remote connection half for a data packet within the configured number of retransmissions. ACTION: There are many possible reasons for a retransmission time out to occur.
Network Transport Protocol (PMERR) Error Messages MESSAGE: PATH FAILURE -90 CAUSE: The operation failed because TCP was unable to resolve a path to the remote system. ACTION: Check for proper network configuration. If the configuration appears correct, enable Class 5 logging for NS Transport if not already enabled and locate matching logging entry. Logging event will indicate Class 5, Subsystem 3, Entity TCP, Location 104xx, path failure error. Parameter is path resolution error returned.
Network Transport Protocol (PMERR) Error Messages ACTION: This is a remote protocol violation. Fix or remove the offending remote implementation. MESSAGE: DATA BEFORE CONNECT -103 CAUSE: The remote connection half has begun to send data before the connection startup handshake has been completed (i.e. before the SYN/ACK was sent). ACTION: This is a remote protocol violation. Fix or remove the offending remote implementation.
FPARSE Error Messages 11 FPARSE Error Messages An FPARSE error code is a 32-bit negative integer returned in the result parameter of the FPARSE intrinsic. The FPARSE intrinsic parses a file designator to determine if it is syntactically correct. If so, then the result parameter returns a positive value. For more FPARSE information, see the “Remote File Access” section of Using NS 3000/iX Network Services. MESSAGE: -1 -1 CAUSE: Bad item values. ACTION: Provide a valid item (0–5).
FPARSE Error Messages MESSAGE: -9 -9 CAUSE: NS not present, but user specified envid. ACTION: Install NS or do not specify envid. MESSAGE: -101 -101 CAUSE: First character of filename not alphabetic. ACTION: Provide a valid MPE file starting character. MESSAGE: -102 -102 CAUSE: Filename expected in the string. ACTION: Provide a filename in the string. MESSAGE: -103 -103 CAUSE: Filename identifier too long. ACTION: Provide a filename 8 characters or less.
FPARSE Error Messages MESSAGE: -110 -110 CAUSE: First character of accountname not alphabetic. ACTION: Provide a valid alphabetic starting character for the account. MESSAGE: -111 -111 CAUSE: Accountname expected in the string. ACTION: Provide an account name in the string. MESSAGE: -112 -112 CAUSE: Accountname identifier too long. ACTION: Provide an accountname of 8 characters or less. MESSAGE: -113 -113 CAUSE: First character of envidname not alphabetic.
FPARSE Error Messages 114 Chapter 11
NETXPORTERR Error Messages 12 NETXPORTERR Error Messages NETXPORTERR messages are returned to $STDLIST when executing the NETCONTROL command. The NETCONTROL command initiates, terminates, and controls the operation of the Network Transport subsystem of the links. MESSAGE: TRANSPORT NOT ACTIVE. 0001 CAUSE: Issued NETCONTROL STATUS command on inactive transport. ACTION: Issue NETCONTROL START. MESSAGE: DIAG COMMAND NOT SUPPORTED. NETXPORT RUNNING IN UNSUPPORTED MODE. RESTART NETXPORT TO CLEAR CONDITION.
NETXPORTERR Error Messages ACTION: None. MESSAGE: TOO MANY PARMS IN COMMAND LINE. 4000 CAUSE: Certain NETCONTROL functions and entities are mutually exclusive and cannot be combined on the same command line. Multiples of the same function are not allowed. ACTION: Check the NS 3000/iX Operations and Maintenance Reference Manual for proper syntax. Correct and retry. MESSAGE: EXPECTED STATUS KEYWORD ALL. 4002 CAUSE: Typographical error. ACTION: Type the word ALL after STATUS =. Correct and retry.
NETXPORTERR Error Messages MESSAGE: BOTH START AND STOP ISSUED. 4009 CAUSE: Both parameters not allowed in a single NETCONTROL command. ACTION: Pick appropriate command. Correct and retry. MESSAGE: INVALID TRACE TYPE. EXPECTED COMBINATION OF D,H,M,B,N,S. 4011 CAUSE: Usually a typographical error. Recommended combination for trace type is HMD. ACTION: Check the NS 3000/iX Operations and Maintenance Reference Manual for proper syntax. Correct and retry. MESSAGE: INVALID TRACE DESTINATION. EXPECTED DISC.
NETXPORTERR Error Messages MESSAGE: TRACE OPEN ERROR. 4021 CAUSE: Usually, you are trying to open a trace on an already opened trace file. ACTION: Ensure that the trace file exists and is open. If it exists and is not open, then see Appendix A, “Submitting an SR,” of this manual. MESSAGE: BAD DIAG VALUE, EXPECTED SET(0–31) OR RST(0–31). 4023 CAUSE: Invalid DIAG value. ACTION: The DIAG keyword command is not for customer use. Contact your Hewlett-Packard representative.
NETXPORTERR Error Messages MESSAGE: NO FUNCTION KEYWORDS ENTERED. 4033 CAUSE: User typed an illegal command. Specifying an entity requires a function to act on it. ACTION: Check NS 3000/iX Operations and Maintenance Reference Manual for proper syntax. Correct and retry. MESSAGE: TRACE PREVIOUSLY ENABLED. 4034 CAUSE: Informative message. ACTION: None. MESSAGE: ENTITY WAS NOT TRACING. 4035 CAUSE: Informative message. ACTION: None. MESSAGE: VERSION ERROR: FIX NUMBERS DIFFER.
NETXPORTERR Error Messages MESSAGE: ALREADY STARTED. 4045 CAUSE: NETCONTROL START command issued for an already active entity. ACTION: None. MESSAGE: NOT STARTED. 4046 CAUSE: The NETCONTROL STOP command was issued when the network transport was never running. ACTION: Check the command for correctness. If it is correct, no further action is required. MESSAGE: TOO MANY MESSAGES TO BE DISPLAYED. 4047 CAUSE: The NETCONTROL error reporting mechanism has encountered more than 6 errors.
NETXPORTERR Error Messages ACTION: Issue the NETCONTROL VERSION=MOD command for more information. See Appendix A, “Submitting an SR,” of this manual. MESSAGE: ! DEVICE NOT CONFIGURED. 4053 CAUSE: The link name specified with the ADDLINK or DELLINK keyword in the NETCONTROL command line is not configured. ACTION: Check the command for correctness. If it appears correct and the link is configured correctly, see Appendix A, “Submitting an SR,” of this manual. MESSAGE: THE ENTITY IS NOT ACTIVE.
NETXPORTERR Error Messages MESSAGE: THIS UPDATE IS NOT ALLOWABLE FOR THIS ENTITY. 4060 CAUSE: The entity associated with the NETCONTROL UPDATE command may not be updated. ACTION: Consult the NS 3000/iX Operations and Maintenance Reference Manual for the correct syntax for the NETCONTROL command. Once the syntax has been corrected, retry the command. MESSAGE: CONFIGURATION FILE NOT VALID. 4061 CAUSE: Validation errors occurred on a NETCONTROL START or UPDATE commands.
NETXPORTERR Error Messages ACTION: Review the referenced NMERR elsewhere in this manual. Confirm that there have been no validation errors with this configuration file. If the error still occurs, see Appendix A, “Submitting an SR,” of this manual. MESSAGE: TRANSPORT NOT YET DOWN. 4101 CAUSE: Detected upon issuing a NETCONTROL START command. The prior NETCONTROL STOP command failed to completely terminate the Network Transport. ACTION: Perform the following steps: 1.
NETXPORTERR Error Messages ACTION: 1. Consult the SHERLOCK diagnostics to determine the cause of the link error. If no link error is indicated, see Appendix A, “Submitting an SR,” of this manual. 2. Consult the SHERLOCK diagnostics to determine the cause of the link error. If no link error is indicated, see Appendix A, “Submitting an SR,” of this manual. 3. Consult the SHERLOCK diagnostics to determine the cause of the link error.
NETXPORTERR Error Messages ACTION: Ensure that the DTC name and card number configured for this device are correct. Using the Openview DTC Manager, start X.25 for the appropriate DTC and card. MESSAGE: HOST LOST CONTACT WITH DTC FOR DEVICE linkname. 4210 CAUSE: The control connection between the host and the DTC was lost. ACTION: Verify that the DTC configured for this device is still functioning. MESSAGE: INVALID CARD NUMBER FOR DTC FOR DEVICE linkname.
NETXPORTERR Error Messages ACTION: Using NMMGR, update the path and validate the DTS subsystem. MESSAGE: CANNOT FIND DTC CONFIGURED FOR DEVICE linkname. 4216 CAUSE: This error may be caused by one of the following reasons: • The host has a non-existent DTC configured in the NMCONFIG.PUB.SYS path LINK.linkname. • The DTC configured in the NMCONFIG.PUB.SYS path LINK.linkname is down or flooded. ACTION: Check the configuration data and verify that it is correct. Restart the DTC if necessary.
NSCONTROL Error Messages 13 NSCONTROL Error Messages NSCONTROL messages are DSERR messages returned to $STDLIST by the :NSCONTROL command. (:NSCONTROL initiates, terminates, and controls the operation of the Network Services subsystem of NS 3000/iX.) These errors are reported during the execution of an NSCONTROL command. There may be several errors reported for one NSCONTROL. NSCONTROL error messages are held in CATALOG.PUB.SYS, message set 16 (DS errors).
NSCONTROL Error Messages MESSAGE: UNKNOWN SERVER servername. 656 CAUSE: An NSCONTROL command with a SERVER option was issued; the indicated server name is not a defined service. ACTION: Delete or correct the name and reissue the command. The NSCONTROL STATUS=SERVERS command will display the valid server names. MESSAGE: SERVER pin DOES NOT SUPPORT DEBUG. 657 CAUSE: An NSCONTROL command with a DEBUG=pinin option was issued, but the server selected by pin does not support the DEBUG option.
NSCONTROL Error Messages MESSAGE: INVALID DADCONF.NET.SYS CONFIGURATION FILE. 662 CAUSE: To be determined. ACTION: Check that the JCONFJOB job has been streamed. If not, issue the command STREAM JCONFJOB. MESSAGE: SERVICE NSservice DOES NOT SUPPORT AUTOLOGON. 663 CAUSE: You cannot automatically log on with the Network Service you are using. ACTION: Do not use the AUTOLOGON function with this service. MESSAGE: INSUFFICIENT STACK SPACE. 698 CAUSE: To be determined.
NSCONTROL Error Messages 130 Chapter 13
VALERR and VALWARN Messages 14 VALERR and VALWARN Messages VALERR messages are returned to $STDLIST as a result of using the configuration validation screen of NMMGR, or following the NETCONTROL START and UPDATE commands. See Using the Node Management Services (NMS) Utilities manual for information on using this screen. MESSAGE: NO DATA FOUND IN PATH RECORD. 1 CAUSE: No data has been entered for the specified path.
VALERR and VALWARN Messages MESSAGE: NO NETWORKS (NETWORK INTERFACES) CONFIGURED. 7 CAUSE: No network interfaces have been configured. ACTION: Configure the network interface, using the Network Interface Configuration screen (path NETXPORT.NI). MESSAGE: RETRANSMIT LOWER (n) BOUND MUST BE = UPPER BOUND (m). 8 CAUSE: Retransmission interval lower bound is set higher than upper bound in Transmission Control Protocol screen (path NETXPORT.GPROT.TCP).
VALERR and VALWARN Messages ACTION: Correct one of the two addresses such that their network portions match. MESSAGE: THIS LINK IS NOT ALLOWED FOR THIS NI TYPE. 20 CAUSE: You are configuring a LAP-B network interface link, but the link name specified corresponds to a non-LAP-B link. ACTION: Reconfigure the link in the Link Selection screen (LINK) as a LAP-B link type. MESSAGE: SECURITY ENABLED BUT NO SECURITY STRING CONFIGURED.
VALERR and VALWARN Messages MESSAGE: CONFIGURED REACHABLE NETS (n) MUST BE = IPU MAX NETS (m). 31 CAUSE: The maximum number of internet reachable networks configured for the specified network interface exceeds the maximum number of networks. ACTION: Use the NMMGR utility to reduce the number of reachable networks in NETXPORT.NI.NIname.INTERNET.gatename to be equal to or less than the maximum value. Validate the configuration again. MESSAGE: CONFIGURED GATEWAYS (n) MUST BE = IPU MAX GATES (m).
VALERR and VALWARN Messages MESSAGE: LINKTYPE MUST BE LAN802.3 IN LINK. 37 CAUSE: The NI type is LAN802.3, but the link configured corresponds to a non-LAN link in Link Configuration. ACTION: Configure a LAN802.3 type link on the NI Link Screen (NETXPORT.NI.NIname.LINK). MESSAGE: ONLY 1 WILD CARD ADDRESS MAPPING ALLOWED FOR EACH ROUTER NI. 39 CAUSE: There are two or more Router Mapping Screens with the wild card IP address “@” configured for the same router NI.
VALERR and VALWARN Messages ACTION: Use the NMMGR utility to add in configuration records CLAS0001 through CLAS0006. Validate the Network Transport again. MESSAGE: NOT A VALID LOGGING CLASS FOR SUBSYSTEM 3. 46 CAUSE: Some other configuration record besides CLAS0001 through CLAS0006 exists beneath the LOGGING.SUB0003 record of the configuration file. ACTION: Use the NMMGR utility to change the configuration file so that the only records beneath the LOGGING.SUB0003 path are CLAS0001 through CLAS0006.
VALERR and VALWARN Messages ACTION: Use the NMMGR utility to add the LOGGING.SUB0005 record to the configuration file so that logging for NetIPC will be configured. At this time logging classes 0 through 2 should also be added to the LOGGING.SUB0005 screen. Validate the Network Transport again. MESSAGE: THREE LOGGING CLASSES REQUIRED FOR SUBSYSTEM 5. 103 CAUSE: There are not three logging classes configured beneath the LOGGING.SUB0005 path in the configuration file.
VALERR and VALWARN Messages ACTION: Use NMMGR to change the configuration file so that at least one NETXPORT.NI.NIname.LINK.linkname record exists for this network. Validate the Network Transport again. MESSAGE: NO PHONE NUMBER REQUIRED FOR DC LINK. 108 CAUSE: Phone data has been erroneously configured for a direct connect link. ACTION: Delete the phone data, or correct the link type. MESSAGE: LOOPBACK ONLY CONFIGURATION NOT ALLOWED. 109 CAUSE: Loopback is the only NI configured.
VALERR and VALWARN Messages MESSAGE: FIVE LOGGING CLASSES REQUIRED FOR SUBSYSTEM 40. 114 CAUSE: All required logging classes are not configured for subsystem 40. Six logging classes configured: CLAS0000, CLAS0001, CLAS0002, CLAS0003, CLAS0004, CLAS0005. ACTION: Use NMMGR to configure all classes under the path LOGGING.SUB0040. Validate the network transport configuration again. MESSAGE: LINK TYPE FOR SNA NI MUST BE SNA. 115 CAUSE: A link of type SNA must be used when configuring an NI for NS over SNA.
VALERR and VALWARN Messages MESSAGE: PVC NUMBER pvc IS DEFINED MORE THAN ONCE. 324 CAUSE: A PVC number is defined more than once under the NETXPORT.NI.NIname.PROTOCOL.X25.PVCPATH path. ACTION: Make sure all PVC numbers are unique in a given PVC configuration path. MESSAGE: X.25 ADDRESS address is defined more than once. 325 CAUSE: An X.25 address is defined more than once under the NETXPORT.NI.NIname.PROTOCOL.X25.SVCPATH path. ACTION: Make sure all X.
VALERR and VALWARN Messages MESSAGE: NO STORE AND FORWARD BUFFERS CONFIGURED. 1004 CAUSE: 1. The specified router network has more than one link configured, but no store and forward buffers have been configured in the NETXPORT.NI.NIname.PROTOCOL.IP screen. It will not be possible to send inbound packets from one link out to another link without any store and forward buffers. 2. If this condition is not desired, use the NMMGR utility to configure store and forward buffers in the NETXPORT.NI.NIname.
VALERR and VALWARN Messages ACTION: This is not a problem if one of the LAP-B links configured for this path is not activated. However, if a LAP-B link is brought up while another such link is active at that physical path, an error will result during link startup. MESSAGE: X.25 INACTIVITY TIMER IS LESS THAN OR EQUAL TO TCP CONNECTION ASSURANCE TIMER. 1102 CAUSE: The X.25 timer is set too low. ACTION: Hewlett-Packard recommends that the X.
LAN, LAN/Console, Token Ring LAN Error Messages 15 LAN, LAN/Console, Token Ring LAN Error Messages Messages generated by the LAN, LAN/console, Token Ring LAN are the following type: Internal driver error in SYSLINK (LANWARN ###) or (LANERR ###) where ### is an error number. MESSAGE: Bad LINK ID. 2 CAUSE: An invalid LINK ID was passed to the link driver’s write initiator. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.
LAN, LAN/Console, Token Ring LAN Error Messages MESSAGE: A call to IO_CONFIG_INT failed during driver initialization. 7 CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative. MESSAGE: A call to IO_DECONFIG_INT failed during driver shutdown. 8 CAUSE: Unknown. Need more information.
LAN, LAN/Console, Token Ring LAN Error Messages MESSAGE: Unable to send I/O Services message frame to another process. 14 CAUSE: A call to a system message SEND routine returned an error. The destination port may belong to a process that no longer exists or is not operating with required capabilities. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative. MESSAGE: LAN console is not supported.
LAN, LAN/Console, Token Ring LAN Error Messages MESSAGE: Attempt to rendezvous with a link driver with SAP or SAP+XSAP or Ethernet Type already being used. 32 CAUSE: The user is trying to rendezvous twice with a link driver or two different users are using the same SAP, SAP+XSAP or Ethernet Type. ACTION: Write down the error information displayed on the console submit an SR and call your Hewlett-Packard representative. MESSAGE: Attempt to separate from the driver failed.
LAN, LAN/Console, Token Ring LAN Error Messages ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative. MESSAGE: The Middle Plane is in wrong state. 40 CAUSE: The Middle Plane state machine table is corrupted. ACTION: Write down the error information displayed on the console submit an SR, take a dump and call your Hewlett-Packard representative. MESSAGE: Missing inbound pool in the rendezvous request message.
LAN, LAN/Console, Token Ring LAN Error Messages MESSAGE: The NIO LAN/console card did not return to a ready state after a reset was issued. 50 CAUSE: The problem is caused by bad NIO LAN/console hardware. ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card. MESSAGE: The NIO LAN/console card register test failed during LAN/console card initialization. 52 CAUSE: The problem is caused by bad NIO LAN/console hardware.
LAN, LAN/Console, Token Ring LAN Error Messages MESSAGE: The NIO LAN/console card detects illegal bind request. 58 CAUSE: The problem is caused by a link driver internal problem. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative. CAUSE: The problem is caused by a bad NIO LAN/console backplane. ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card.
LAN, LAN/Console, Token Ring LAN Error Messages ACTION: Use NMMGR to verify that the configured Station Address is correct. CAUSE: The problem is caused by a bad NIO LAN/console backplane. ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card. MESSAGE: The NIO LAN/console card detects a bind request to already bound register. 63 CAUSE: The problem is caused by a link driver internal error.
LAN, LAN/Console, Token Ring LAN Error Messages ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative. MESSAGE: The NIO LAN/console card reports that expected CCMD_LINK was not found. 68 CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative. MESSAGE: The NIO LAN/console card reports that CCMD_IN was sent to an outbound only register set.
LAN, LAN/Console, Token Ring LAN Error Messages ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative. MESSAGE: The NIO LAN/console card detects a severe hardware error. 76 CAUSE: Unknown. Need more information. ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card. MESSAGE: The NIO LAN/console card detects a severe internal error. 77 CAUSE: Unknown. Need more information.
LAN, LAN/Console, Token Ring LAN Error Messages MESSAGE: The BDMARS transferred less DMA data than the host CCMD_IN or CCMD_OUT count requested. 83 CAUSE: The NIO LAN/console card did not have enough data bytes to completely fill the inbound buffer. Or the NIO/LAN console card did not accept all the data that the host tried to send; for example, the number of bytes were bigger than maximum LAN packet size.
LAN, LAN/Console, Token Ring LAN Error Messages MESSAGE: The NIO LAN/console card reports unknown soft error. 90 CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative. MESSAGE: The NIO LAN/console card detects unknown I/O command. 91 CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.
LAN, LAN/Console, Token Ring LAN Error Messages ACTION: Your Hewlett-Packard representative must run diagnostics on the CIO LAN card. MESSAGE: The CIO LAN card detects a fatal backplane error. 117 CAUSE: Unknown. Need more information. ACTION: Your Hewlett-Packard representative must run diagnostics on the CIO LAN card. MESSAGE: The Identity Request to the CIO LAN card failed. 118 CAUSE: Unknown. Need more information. ACTION: Your Hewlett-Packard representative must run diagnostics on the CIO LAN card.
LAN, LAN/Console, Token Ring LAN Error Messages MESSAGE: The driver detects unknown option in the 802.2 control field of a test or xid packet. 125 CAUSE: The problem is caused by a bad packet. ACTION: If this error appears repeatedly, write down the error information displayed on the console and call your Hewlett-Packard representative. MESSAGE: The CIO LAN configuration request failed. 128 CAUSE: Unknown. Need more information.
LAN, LAN/Console, Token Ring LAN Error Messages MESSAGE: Dump request received when driver is dumping. 144 CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative. MESSAGE: Message received in invalid state. 145 CAUSE: The link driver received an unexpected message. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.
LAN, LAN/Console, Token Ring LAN Error Messages MESSAGE: Unexpected timer event message. 151 CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative. MESSAGE: Unimplemented message received. 152 CAUSE: The message descriptor is not known to the driver. ACTION: Call your Hewlett-Packard representative and explain what you are trying to do. MESSAGE: Nil configuration pointer.
LAN, LAN/Console, Token Ring LAN Error Messages MESSAGE: Could not open NMCONFIG.PUB.SYS file. 228 CAUSE: The configuration file NMCONFIG.PUB.SYS was purged or renamed or the NMCONFIG.PUB.SYS configuration file may be opened with exclusive access. ACTION: Type a LISTF NMCONFIG.PUB.SYS to determine if the file has been opened with exclusive access. If it has, wait for the program or process that has this file opened exclusively to close it.
LAN, LAN/Console, Token Ring LAN Error Messages MESSAGE: A call to IO_UNCONFIG failed during driver deconfiguration. 235 CAUSE: Wrong physical path was specified in IO_UNCONFIG call due to configuration data corruption in the driver PDA. ACTION: Write down the error information displayed on the console, submit an SR, take a system dump, and call your Hewlett-Packard representative. MESSAGE: The LAN card is used by another link. 236 CAUSE: The card was configured by another link.
LAN, LAN/Console, Token Ring LAN Error Messages ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative. MESSAGE: Could not get Write Initiator label. 242 CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative. MESSAGE: Could not release Write Initiator label. 243 CAUSE: Unknown. Need more information.
LAN, LAN/Console, Token Ring LAN Error Messages MESSAGE: Could not receive config reply message. 249 CAUSE: An internal system ports problem has occurred. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative. MESSAGE: Timeout waiting for the config reply message. 250 CAUSE: The link software or the card could not be configured. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative.
100VG-AnyLAN and 100Base-T Error Messages 16 100VG-AnyLAN and 100Base-T Error Messages The following error messages gives the meaning of the first 8 bits of 32-bit status values produced by the 100VG-AnyLAN or 100Base-T link driver and its supporting modules. This is the so-called “SDI status” portion. All values are architected, and are intended to provide a generic indication of what the rest of the status means, in a module-independent way.
100VG-AnyLAN and 100Base-T Error Messages SDI Generic Status Values SDI Generic Status Values MESSAGE: No error, info only. 0 ($00) CAUSE: None ACTION: None MESSAGE: The driver detected an exception in hardware operation. 1 ($01) CAUSE: The driver detects an exception in hardware operation. At this state, the only type of requests that would be processed are the diagnostic requests or Module Deconfigurator Call. ACTION: Stop the normal operation and execute the diagnostic software.
100VG-AnyLAN and 100Base-T Error Messages SDI Generic Status Values MESSAGE: Inadequate resources available to satisfy a request. 7 ($07) CAUSE: There are inadequate SAP control block, buffers, or link stations available to satisfy the request. ACTION: According to the situation, close some SAPs/stations or wait. MESSAGE: An adapter card is not responding. 8 ($08) CAUSE: The driver detects an exception in hardware operation.
100VG-AnyLAN and 100Base-T Error Messages SDI Generic Status Values MESSAGE: Remote link has disconnected. 46 ($2E) CAUSE: For the Disconnect Event, the remote link station issued a Disconnect command to the link station, and the link station has replied that disconnect command and notified the subsystem. ACTION: According to the subsystem. MESSAGE: Link disconnected, although remote has not acknowledged.
100VG-AnyLAN and 100Base-T Error Messages SDI Generic Status Values MESSAGE: Error in interface with Trace Services. 84 ($54) CAUSE: A module Configurator/Deconfigurator failed to start/stop the TRACE MANAGER, however, the configuration/deconfiguration operation has the completed (example, The Driver has deallocated the Driver’s resources). ACTION: According to the subsystem. MESSAGE: Resource deallocation error.
100VG-AnyLAN and 100Base-T Error Messages SDI Generic Status Values MESSAGE: Link type of the named link is not supported. 125 ($7D) CAUSE: The Linkname passed by the Module Configuration Call or Deconfigurator Call is invalid. The particular driver is not configured. ACTION: Fix the configuration file and try again. MESSAGE: Link type of the named link is not supported.
100VG-AnyLAN and 100Base-T Error Messages SDI Generic Status Values MESSAGE: The specified local Protocol SAP was already opened. 133 ($85) CAUSE: For the Rendezvous Request, this error indicates that the LSAP has already opened. ACTION: Use an acceptable SAP value. MESSAGE: A request was not accepted due to current state of the link. 161 ($A1) CAUSE: The requested message cannot be accepted because of the existing state of the link station.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values SDI Driver Specific Status Values The following error messages gives the meaning of the second 8 bits of 32-bit status values produced by the 100VG-AnyLAN or 100Base-T link driver and its supporting modules. This is the so-called “driver status” portion. All values are driver-specific, and are intended to provide additional detail beyond the generic indication provided by the first 8 bits of status.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Link connected. 5 ($04) CAUSE: The first upper layer subsystem to bind to the driver triggered a link connect, which was successful. This event is also logged after the link or cable has been successfully reconnected after being disconnected, or on a link reconnect following a hub retrain, severe line hit, power failure, or other recoverable error. ACTION: This event is informational.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Subsystem is closing link. 11 ($0B) CAUSE: An upper level subsystem has called the link module deconfigurator, which has successfully located the link, and will now proceed to close it. ACTION: This event is informational. No action is required. MESSAGE: Powerfail detected.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Cannot release a system plabel. 17 ($11) CAUSE: During the final link-close operation by an upper level subsystem, the link module deconfigurator encountered an error while trying to release the link’s write initiator procedure. ACTION: This is an informational warning that some system memory resources may have been lost. The module deconfigurator reported an error, but attempted to continue with the close.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This error is mainly informational, since the driver did not dump, but may be indicative of other, possibly-related problems. The driver will still attempt to auto-reset itself, up to a total of 12 times or more. MESSAGE: Late dump-done message received. Dump took too long. 27 ($1B) CAUSE: The driver received a driver-dump completion message when it was not working on a dump. ACTION: This error is informational only.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This error indicates a bug in the link driver. The driver is designed to avoid this situation through use of various queues and checks. If the problem happens often, see Appendix A, “Submitting an SR.” MESSAGE: Driver is out of extra DMA quad resources.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values caused the error. Activate link tracing, reproduce the problem, then stop link tracing and save the resulting NMTCnnnn.PUB.SYS trace data file. See Appendix A, “Submitting an SR.” MESSAGE: A received frame could not be delivered. 43 ($2B) CAUSE: Just before delivering a received data frame to an upper layer protocol, the driver found that the rendezvous table entry specified in the buffer was not in the proper state.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Bad hardware ID or path. 51 ($33) CAUSE: During a link-open operation by an upper level subsystem, the link module configurator did not find a supported 100VG-AnyLAN or 100Base-T adapter card at the hardware path specified in NMCONFIG. ACTION: Verify the path in NMCONFIG is correct and complete, and matches the path where a supported 100VG-AnyLAN or 100Base-T adapter card is installed in the computer backplane.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values Support Representative may be able to use VGPBA diagnostics to modify your adapter card’s EEPROM to work temporarily with your older software. MESSAGE: Driver could not identify the expected PHY on card. 55 ($37) CAUSE: After verifying the PHY chip on the adapter card had been successfully reset, the driver checked the ID of the PHY, but found it did not match any ID expected for this kind of adapter card.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: EEPROM reads can be sensitive to software timing. If you have GLANCE or a similar tool, run it and check the CPU load on the system. If the load is high, try reducing the CPU load, then retry the operation. If the problem persists, the adapter card has probably failed; replace the adapter card. MESSAGE: EEPROM write error on adapter card.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values change NMCONFIG or contact your Hewlett-Packard Representative for assistance in determining paths or correcting bus hardware problems. MESSAGE: Adapter card found does not match software configuration.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This is a fatal software error. The number of available timers is not configurable, and the driver cannot operate without the necessary timers. Typically followed by another error giving more information about what kind of timer the driver needed; check log data for that error and look it up also. If you suspect a heavy load, you can try shutting some processes down, then restart the driver.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Error from upper layer protocol read completor. 81 ($51) CAUSE: The driver finished transferring a data frame and passed it to an upper layer protocol, but the protocol’s read completor returned an error which was not one of the expected, legal errors the driver was able to handle. ACTION: This is an informational error only. The driver incremented a statistic then attempted to continue.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Cannot load a system routine. 87 ($57) CAUSE: During a link-open operation by an upper level subsystem, the link module configurator encountered an error while trying to load code for the write initiator procedure needed for the link type configured in NMCONFIG. ACTION: Probably not all software required to operate this type of link is installed.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: The problem could indicate some serious internal problems within the buffer manager or its data structures, or with the way the system is configured. Note all log messages, especially the “Cause” status for this error, and see Appendix A, “Submitting an SR.”. If the problem persists, take a system memory dump immediately after the problem has occurred. MESSAGE: Cannot create a buffer pool.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: A driver request failed. 117 ($75) CAUSE: This is a generic software error, used when the driver receives a new request but cannot process it because of an earlier failure. It is used in the reply to the outside module which requested the operation, to indicate it could not be processed. ACTION: If this status is reported, it is because of some earlier failure.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: An unexpected transmit condition was encountered. 126 ($7E) CAUSE: While attempting to initiate DMA to send some transmit data to the adapter card, driver software found its data structures to be in an unexpected state. The state of all transmit queues was not one of the legal states predicted at design time. ACTION: This is a fatal software error.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: Run NMMAINT.PUB.SYS;PARM=74 or ;PARM=77, for 100VG-AnyLAN or 100Base-T respectively, and check that the multicast services are present. If present, try starting a ThinLAN link, to see if the same errors occur; or try restarting the system, then retry the operation.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Buffer pool table full. Too many unique pools. 149 ($95) CAUSE: When a new upper-layer protocol attempted to bind (rendezvous) to the link driver, the driver determined all available buffer pool table entries were already in use. Too many different pool ID’s are being specified by the protocols. The driver assumes a few pools will be shared by many protocols.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Configuration failed. 154 ($9A) CAUSE: This is a generic error, reported after successful or unsuccessful completion of initial hardware startup, if the driver encountered an error bringing up the adapter card, or when opening the link, or while attempting to send the reply to a pending configuration request from its module configurator. ACTION: This is a fatal software error.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Timeout while awaiting a link training transmit interrupt. 163 ($A3) CAUSE: During a 100VG-AnyLAN link connect attempt, the driver received a training frame from the 100VG-AnyLAN hub in response to a previous send, but no interrupt arrived for the last frame it sent within the 2 ms time allowed. ACTION: This error is informational only. The driver will retry the connect.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This error is informational only. The driver will retry the connect. If the problem happens every time, first check that the cable is good, is connected, and the hub is powered on. Try checking the hub port configuration, or replacing the cable and/or adapter card. MESSAGE: Link training failed. 172 ($AC) CAUSE: This is a generic error.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Hub reports link station address is already in use. 186 ($BA) CAUSE: The driver received a training frame from the hub with the “duplicate address” bit set in the frame. The hub is reporting that another adapter is already using the same MAC address as the link now trying to connect. Every card on a LAN network must have a unique MAC address. ACTION: The driver discarded this frame and sent another.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Unexpected loss of link signal from hub. 194 ($C2) CAUSE: While the link was supposedly connected, an event occurred causing the link driver to check if the link was connected, and when the PHY chip on the adapter card was checked, it was found that the link was not connected. Probably the cable was disconnected from the hub or card. ACTION: This event is informational. No action is required.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values there). If the link is being used with NS or DTS, use the VALIDATE function to validate the network configuration. Correct any configuration errors and retry the operation. MESSAGE: Cannot validate configuration file. 200 ($C8) CAUSE: After successfully reading configuration data for a link being started, the link module configurator checked the data and found it was not valid.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: If the linkname being started is a valid linkname, then there may be a problem with Link Support Services. Halt the system, take a system memory dump, then restart the system. If the problem still occurs, see Appendix A, “Submitting an SR.” MESSAGE: Cannot add to link table.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Cannot stop tracing. 209 ($D1) CAUSE: After a link-open operation by an upper level subsystem failed, the link module configurator tried to clean up, but encountered an error trying to disable driver tracing. ACTION: Probably the link driver returned an error reply when asked to disable tracing. The driver may have a problem, or may already have shut down.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: All such errors are caused by bugs in the upper layer protocol. Attempt to determine what protocol was trying to bind, then see Appendix A, “Submitting an SR.” MESSAGE: A data buffer is too long. 224 ($E0) CAUSE: During diagnostic loopback testing, the driver was asked to prepare a data block for transmission, but the block length or memory allocation was beyond the driver’s DMA capabilities.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values rebooted. Either there is a bug in the driver or upper layer protocol software, memory data corruption has occurred, or there is a system software mismatch. You may require additional software patches; contact your Hewlett-Packard Representative for assistance. MESSAGE: An illegal bind ID was encountered.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Bad message for current state. 239 ($EE) CAUSE: This is a generic error, reported when the driver received a request from outside when the driver was not in a state where it could process that type of request, or the when driver has already processed a message of this type and was not expecting another.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values Format the file on the system you took the trace or log on, or contact your Hewlett-Packard Representative to check if VGFOS patches are already available to correct this problem. MESSAGE: Incomplete data was encountered. 245 ($F5) CAUSE: The trace or log formatter attempted to decode an entry, but on inspection found that the entry did not contain at least the minimum length of data required for this version of the data.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values Retry the operation. If this does not help, try stopping all networks using the link, then retry. If the problem still persists, halt the system and take a memory dump, then see Appendix A, “Submitting an SR.” MESSAGE: An unexpected timeout occurred.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: If this error occurs, there may be additional driver-specific errors logged, giving more information about the problem. Attempt to locate those errors and look them up also. The open did not succeed. The module configurator cleaned up and returned an error to the subsystem. MESSAGE: No adapter card found on specified HP-PB bus.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: Correct the network configuration or plug in the correct type of adapter card, and retry the operation. The module configurator cleaned up and returned an error to the subsystem. MESSAGE: Cannot create a buffer pool.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Cannot load a system routine. 1170 CLAS0001 CAUSE: During a link-open operation by an upper level subsystem, the link module configurator encountered an error while trying to load code for the write initiator procedure needed for the link type configured in NMCONFIG (“Cause”= 32-bit status from the call to hpgetsysplabel). ACTION: Probably not all software required to operate this type of link is installed.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: The module configurator cleaned up and returned an error to the subsystem. Verify an NMCONFIG.PUB.SYS file exists. If so, try to verify its format matches rest of the operating system. If the system was updated, you may need to run NMMGRVER.PUB.SYS to convert the file to a newer format. If the system was backdated, you may need to restore an older copy of NMCONFIG from a backup tape.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values Using NMMGR, verify the path LINK.linkname exists in the NMCONFIG file and is either a 100VG-AnyLAN or 100Base-T link type. If the subsystem being started is NS, verify the link type matches the NI type for the network being started. If these are not the problem, an incorrect version of NMMGR may have been used to create the NMCONFIG file on your system. Run NMMAINT.PUB.SYS;PARM=24 to check versions of NMMGR components.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values If none of these suggestions solves the problem, contact your Hewlett-Packard Representative for assistance with configuring a 100VG-AnyLAN or 100Base-T link to enable tracing at startup. MESSAGE: Cannot send a trace request. 1620 CLAS0001 CAUSE: During a link-open operation by an upper level subsystem, the link module configurator found that the link was configured to enable tracing at startup.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values contains the multicast for 100VG-AnyLAN and 100Base-T) or obtain newer patches; contact your Hewlett-Packard Representative for assistance. If reinstalling software does not solve the problem, see Appendix A, “Submitting an SR.” MESSAGE: The link is already started.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Cannot send a port message. 1720 CLAS0001 CAUSE: During a link-close operation by an upper level subsystem, the link module deconfigurator was preparing to send updated configuration data to the driver, but encountered an error while trying to send the port message (“Cause”= 32-bit status from the call to send_msg).
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Subsystem is closing link. 1800 CLAS0001 CAUSE: An upper level subsystem has called the link module deconfigurator, which has successfully located the link, and will now proceed to close it. ACTION: None. This is an informational event only. A similar event was logged when the link was opened. MESSAGE: Cannot stop tracing.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Cannot remove driver from I/O system. 1900 CLAS0001 CAUSE: During the final link-close operation by an upper level subsystem, the link module deconfigurator attempted to delete an instance of the link driver, but encountered an I/O system error (“Cause”= 32-bit status from the call to io_unconfigure). ACTION: The deconfigurator stopped trying to close the link.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Cannot delete a buffer pool. 1980 CLAS0001 CAUSE: During a link-close operation by an upper level subsystem, the link module deconfigurator encountered an error while trying to delete a control buffer pool (“Cause”= 32-bit status from the call to bmgr_delete_pool). ACTION: This is an informational warning that some system memory resources may have been lost. Probably not all buffers were freed before the pool was deleted.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: A driver dump was suppressed. Too many dumps already. 2090 CLAS0001 CAUSE: During processing of a fatal driver error, the driver attempted a driver dump, but determined it had already dumped too many times since it was initially started (“Cause” is not used here). If this error is reported, it is because the driver has already encountered some other error.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: Typically preceded by another error giving better information about the original cause; check log data for that error and look it up also. This error is mainly informational, since the driver did not dump, but may be indicative of other, possibly-related problems. The driver will still attempt to auto-reset itself, up to a total of 12 times or more. MESSAGE: Cannot get a system timer.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values another error giving more information about what kind of timer the driver was releasing; check log data for that error and look it up also. If the problem happens every time, see Appendix A, “Submitting an SR.” MESSAGE: Pending message table full. Driver not finishing fast enough.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values reproduce the problem, and save the resulting trace file (NMTC####.PUB.SYS) for analysis by Hewlett-Packard. See Appendix A, “Submitting an SR.” MESSAGE: Illegal access to saved port message area.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Open table full. Too many driver users. 2710 CLAS0001 CAUSE: Too many subsystems are attempting to open the driver at the same time, or subsystems are shutting down without closing the driver (“Cause”= maximum number of driver opens allowed). ACTION: The driver allows 11 simultaneous opens. It was not opened by the additional subsystem. Shut down any networking subsystems that are not currently needed and try again.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values If the problem happens every time, enable link tracing via :LINKCONTROL then reproduce the link shutdown problem (the trace file will close automatically). Save the resulting trace file (NMTC####.PUB.SYS) on tape for Hewlett-Packard analysis, and see Appendix A, “Submitting an SR.” MESSAGE: Driver is shutting down. 2800 CLAS0003 CAUSE: The driver is being shut down. The last subsystem that was using the driver is now closing it.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: The driver did not start up. There is probably an MPE software installation problem, with incomplete or incompatible O/S software. Verify the system is running an MPE release which supports 100-Mbit link drivers. The only other cause is a software bug; see Appendix A, “Submitting an SR.” MESSAGE: Powerfail detected.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE 1: Powerfail detected. 2980 CLAS0001 CAUSE: During a 100VG-AnyLAN link connect attempt, the driver attempted to request a training interval from the hub, but detected all 1’s on an MII hardware register read, indicating a powerfail had already occurred. The driver was trying to read from a PHY status register to clear it, when the powerfail or error occurred. ACTION: None. This error can usually be ignored.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: None. This error can usually be ignored. Power failures can occur at any moment. The driver was executing at the moment power failed. Power then returned, and the driver ran to completion, noticing this error along the way. Upon exit, the driver was then officially notified of a powerfail by MPE. The driver then attempted powerfail recovery, and should now be operating the same as before. The link did not connect.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values However, if the link was supposed to be up or the message appears frequently while the link is up, this indicates possible cabling problems; make sure cabling is securely connected and properly routed away from sources of interference, and is of the proper UTP category or grade for the type of link (CAT-5 for 100Base-T, CAT-3 or -5 for 100VG-AnyLAN). MESSAGE: Driver is starting adapter card.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values command (such as :NETCONTROL STOP). If you wish, you may first try running the VGPBA diagnostic; execute the Reset function to see if that clears the problem. MESSAGE: Driver encountered a software problem. 3220 CLAS0001 CAUSE: During a 100VG-AnyLAN link connect attempt, the driver was unable to allocate and start or reset its training timer.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Configuration failed. 3340 CLAS0001 CAUSE: While processing a driver open from an upper layer subsystem, which was not the first open against the driver, the driver encountered an error during configuration (“Cause”= 32-bit status returned by the call to vg_dvr_port_msg_exec). Probably there are already too many opens against the driver.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: A driver request failed. 3430 CLAS0001 CAUSE: While attempting to forward a diagnostic request to its ISR, the driver encountered an error (“Cause”= 32-bit status returned by the call to vg_dvr_copy_send_to_isr). Probably no comm frame was available.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: A driver request failed. 3550 CLAS0001 CAUSE: While attempting to forward a disable-trace request to its ISR, the driver encountered an error (“Cause”= 32-bit status returned by the call to vg_dvr_copy_send_to_isr). Probably no comm frame was available.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: The driver sent an error reply in response to the message. Further action may not be required. If the problem occurs frequently, try to determine what operator commands or actions trigger the error, then see Appendix A, “Submitting an SR.” MESSAGE: Late dump-done message received. Dump took too long.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: Retry the same trace command later. An error reply was sent in response to the request. Trace was not started by this request this time, and remains off. MESSAGE: A driver request failed. 3790 CLAS0001 CAUSE: While processing a request to turn link trace on, the driver was unable to locate a free storage element in which to save reply information (“Cause”= 32-bit status returned by the call to vg_dvr_save_msg).
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Cannot get ADA memory object. 3910 CLAS0001 CAUSE: During initial startup, the driver attempted to obtain a memory object via the I/O system, but received a bad status in the reply for that request (“Cause”= 32-bit status from the reply message). ACTION: The link did not start, and the driver attempted to send back an error reply in response the configuration request from the module configurator.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Bad message for current state. 4030 CLAS0001 CAUSE: The driver received a release-memory reply message it was not expecting (“Cause”= 16-bit encoded value, giving driver input event code and current state: HP use only). ACTION: The driver may already have changed state because of a shutdown or another problem, in which case this message can be ignored. Otherwise, the I/O system may be confused.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values the driver is in the state it is currently in. If the reset was automatically generated by the driver in response to some serious error it detected, this log event means it is being ignored. MESSAGE: A driver request failed. 4130 CLAS0001 CAUSE: While attempting to forward a protocol separate (unbind) message to its ISR, the driver encountered an error (“Cause”= 32-bit status returned by the call to vg_dvr_copy_send_to_isr).
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Driver encountered a software problem. 4144 CLAS0001 CAUSE: Before attempting to forward a diagnostic or LINKCONTROL statistics request to its ISR, the driver discovered the ISR was already in a “dead” state and unable to process requests (“Cause”= 32-bit status stating the driver is “dying”). ACTION: If the operator already knows the driver is in the process of being closed, this error can be ignored.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values problem happens every time the same subsystem is closed, submit an SR against that subsystem, describing the problem; see Appendix A, “Submitting an SR.” MESSAGE: Cannot send a port message. 4240 CLAS0001 CAUSE: During a link close operation, the driver encountered an error while sending an unconfigure reply message to an upper layer subsystem (“Cause”= 32-bit status returned by the call to vg_dvr_send_reply).
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: A driver request failed. 4330 CLAS0001 CAUSE: While processing a diagnostic input-output request message, the driver encountered an error (“Cause”= 32-bit status returned by the call to vg_dvr_copy_send_to_isr). Probably no comm frame was available.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This informational error should be preceded by another error giving a more specific reason for the failure; check log data and look up that error also, for more actions to take. Most likely the previous error was fatal and the driver is about to “die”, then will either attempt an auto-reset or else require a manual shutdown and restart. MESSAGE: Bad message for current state.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values After this problem occurs, the driver will enter a “broken” state where is may not respond to further requests. If possible, run the VGPBA tool program, and use it to force a driver dump, then forward the resulting NETDMP##.PUB.SYS file to Hewlett-Packard for analysis. After a dump, the driver will attempt to auto-reset itself and continue.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values Collect binary copies of all dump files (NETDMP##.PUB.SYS) on tape for analysis by Hewlett-Packard and see Appendix A, “Submitting an SR.” MESSAGE: General error trying to get a buffer. 4790 CLAS0001 CAUSE: While attempting to request action from its DVR module, the driver’s ISR found that no available communication frames were available on the referenced queue (“Cause” is not used here).
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Driver could not identify the expected PHY on card. 4880 CLAS0001 CAUSE: After verifying the PHY chip on the adapter card had been successfully reset, the driver checked the ID of the PHY, but found it did not match any ID expected for this kind of adapter card (“Cause”= 32-bit PHY ID obtained from the card). ACTION: Replace the adapter card.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values adapter card or system HP-PB hardware may have failed. Replace the adapter card. Then, if the problem still persists, contact your Hewlett-Packard Service Representative for help in diagnosing your system hardware. MESSAGE: Card did not go ready after hard reset.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: If a power failure has actually occurred, this error can be ignored; the driver should recover automatically. Otherwise, the MII bus may have failed; replace the adapter card. If the same problem persists, see Appendix A, “Submitting an SR.” MESSAGE: Driver encountered a hardware problem.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This problem should only be seen in diagnostics, however it should not be occurring at all. Specify a shorter loopback length, and see Appendix A, “Submitting an SR.” MESSAGE: Driver encountered a software problem.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Driver encountered a software problem. 5330 CLAS0001 CAUSE: During a 100VG-AnyLAN link training sequence, the driver started to power up the PHY chip, but encountered an error while trying to get or reset a timer (“Cause”= 32-bit status from the call to vg_start_timer). This timer was to be used to wait for the PHY power-up to finish; the driver cannot connect the link if a PHY timer cannot be started.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: If a power failure has actually occurred, this error can be ignored; the driver should recover automatically. But if the same problem happens every time, see Appendix A, “Submitting an SR.” MESSAGE: Driver encountered a hardware problem.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Driver encountered a software problem. 5570 CLAS0001 CAUSE: During a 100VG-AnyLAN link training sequence, the driver requested a test interrupt, then encountered an error while trying to get or reset a timer (“Cause”= 32-bit status from the call to vg_start_timer). This timer was to be used to verify the test interrupt arrives; the driver cannot connect the link if a PHY timer cannot be started.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: Replace the adapter card. The link did not connect. If the problem persists with a known good card, see Appendix A, “Submitting an SR.” MESSAGE: Driver encountered a hardware problem.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values used to wait again for the PHY reset to finish; the driver cannot connect the link if a PHY timer cannot be started. If this error is reported, it is because the driver has already encountered some other error. ACTION: Typically preceded by another error message giving better information about the original cause; check log data for that error and look it up also.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values the system should continue to run, and the driver will probably retry the connect. If the problem happens every time, see Appendix A, “Submitting an SR.” MESSAGE: Driver encountered a hardware problem.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Driver encountered a software problem. 5990 CLAS0001 CAUSE: During a 100Base-T connect sequence, the driver found the link was not connected yet, but encountered an error while trying to get or reset a timer (“Cause”= 32-bit status from the call to vg_start_timer). This timer was to be used to wait again for the link connect to finish; the driver cannot connect the link if a PHY timer cannot be started.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: If a power failure has actually occurred, this error can be ignored; the driver should recover automatically. Otherwise, the MII bus may have failed; replace the adapter card. If the same problem persists, see Appendix A, “Submitting an SR.” MESSAGE: Driver encountered a hardware problem.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: If a power failure has actually occurred, this error can be ignored; the driver should recover automatically. Otherwise, the MII bus may have failed; replace the adapter card. If the same problem persists, see Appendix A, “Submitting an SR.” MESSAGE: Driver encountered a hardware problem.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Driver encountered a hardware problem. 6260 CLAS0001 CAUSE: While a 100Base-T link was connected, the driver received a notification the link may be down, but when it went to check, it encountered an error trying to read from the generic status register on the PHY chip (“Cause”= 32-bit status from the call to vg_mii_read16). Most likely a powerfail has occurred.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: Typically preceded by another error message giving better information about the original cause; check log data for that error and look it up also. The driver did not dump, but will still attempt to auto-reset itself, up to a total of 12 times or more. If the problem persists, the system may be low on timers; try stopping some applications before retrying again.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Driver encountered a hardware problem. 7190 CLAS0001 CAUSE: During a 10Base-T connect sequence on a 100VG-AnyLAN adapter card, the driver attempted to enable MII interrupts, but encountered an error trying to read from the serial I/O register on the LAN Controller chip (“Cause”= 32-bit status from the call to vg_dio_read8). Most likely a powerfail has occurred.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Driver encountered a software problem. 7310 CLAS0001 CAUSE: During a 10Base-T connect sequence on a 100VG-AnyLAN adapter card, the driver requested a test interrupt, then encountered an error while trying to get or reset a timer (“Cause”= 32-bit status from the call to vg_start_timer). This timer was to be used to verify the test interrupt arrives; the driver cannot connect the link if a PHY timer cannot be started.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This is a warning that some timer resources may have been lost. The link did not connect. Typically preceded by another error message giving better information about the original cause; check log data for that error and look it up also. Unless this happens constantly, the system should continue to run, and the driver will probably retry the connect. If the problem happens every time, see Appendix A, “Submitting an SR.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Driver encountered a software problem. 7550 CLAS0001 CAUSE: During a 10Base-T connect sequence on a 100VG-AnyLAN adapter card, when a timeout occurred instead of an interrupt, the driver noticed a remote fault condition, but encountered an error while trying to stop and release a timer (“Cause”= 32-bit status from the call to vg_stop_timer). This timer was used to wait for any interrupt to arrive.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values (“Cause”= 32-bit status from the call to vg_stop_timer). This timer was used to wait for the link to connect. If this error is reported, it is because the driver has already encountered some other error. ACTION: This is a warning that some timer resources may have been lost. The link did not connect.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values was fatal and the driver is about to “die”, then will either attempt an auto-reset or else require a manual shutdown and restart. The driver stopped trying to connect the link. MESSAGE: (Varies) 7830 CLAS0001 CAUSE: This is a generic logging location which reports the driver is having trouble connecting the link. The message varies depending on what the problem is.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Driver encountered a software problem. 7880 CLAS0001 CAUSE: After attempting to disconnect the link, the driver’s ISR module determined the link did disconnect, then encountered an error trying to notify the DVR module of the disconnect (“Cause”= 32-bit status from the call to Vg_isr_copy_send_to_dvr). Probably no comm frame was available.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values probably indicates a larger system problem or corruption of data structures. If this error is reported, it is because the driver has already encountered some other error. ACTION: Typically preceded by another error message giving better information about the original cause; check log data for that error and look it up also. The driver did not dump, but will still attempt to auto-reset itself, up to a total of 12 times or more.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values auto-reset itself, up to a total of 12 times or more, even though this happened during diagnostic testing. If the problem persists, the system may be low on timers; try stopping some applications before retrying again. MESSAGE: Driver encountered a software problem.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Driver encountered a software problem. 8120 CLAS0001 CAUSE: During a link connect attempt, an interval timer used to control the PHY chip on the adapter card popped and the driver passed that to a lower level, but the lower level returned an error (in older software, “Cause” is not used here; otherwise “Cause”= 32-bit status from the call to vg_isr_call_phy_state_machine).
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: One or more bad bind parms passed by upper level protocol. 8210 CLAS0001 CAUSE: The driver received a bind (rendezvous) from an upper layer protocol module, but the pointer to the information block was not specified (“Cause” is not used here). ACTION: This problem most likely occurred while starting a new network subsystem.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values Either there is a bug in the driver or upper layer protocol software, or there is a system software mismatch. You may require additional software patches; contact your Hewlett-Packard Representative for assistance. MESSAGE: One or more bad bind parms passed by upper level protocol.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This problem most likely occurred while starting a new network subsystem. Attempt to determine which subsystem was being started when the error occurred and, if possible, which upper layer protocol was binding. The bind failed. The driver logged the error, then attempted to send an error reply message back to the protocol module and continue.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values If a duplicate address is in the table already, either an attempt has been made to start the same subsystem twice, or a previous instance of that subsystem did not properly shut down; a system reboot may be required to shut it. Otherwise there could be a driver bug, if two protocols are truly different but the driver thinks they are the same. Shut down the network and restart it.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: Typically preceded by another error message giving better information about the original cause; check log data for that error and look it up also. The driver did not dump, but will still attempt to auto-reset itself, up to a total of 12 times or more. If the problem persists, the system may be low on timers; try stopping some applications before retrying again. MESSAGE: Driver encountered a hardware problem.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This problem most likely occurred while stopping a running network subsystem. Attempt to determine which subsystem was being stopped when the error occurred and, if possible, which upper layer protocol was unbinding. The unbind failed. The driver logged the error, then attempted to send an error reply message back to the protocol module and continue. The driver still thinks the protocol is bound.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This informational error should be preceded by another error giving a more specific reason for the failure; check log data and look up that error also, for more actions to take. Most likely the previous error was fatal and the driver is about to “die”, then will either attempt an auto-reset or else require a manual shutdown and restart. MESSAGE: Driver encountered a software problem.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Bad message for current state. 8840 CLAS0001 CAUSE: The driver received a utility register access request from an upper level tool program such as PVGUTIL, at a time when the driver was not able to process these requests, such as before initializing the adapter card, during shutdown, or after a fatal software error (“Cause”= 16-bit encoded value, giving driver input event code and current state: HP use only).
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Driver encountered a software problem. 8930 CLAS0001 CAUSE: The driver received a utility I/O request from an upper level tool program such as PVGUTIL, but encountered an error while trying to construct the necessary data structure (“Cause”= 32-bit status from the call to vg_isr_build_util_step). Probably no DMA step was available. ACTION: This problem most likely occurred while diagnosing some previous problem.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values the driver will attempt to auto-reset itself and continue. You may also use VGPBA to attempt a manual reset of the driver, after which it may be possible to continue. MESSAGE: An illegal bind ID was encountered.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: Error from upper layer protocol read completor. 9200 CLAS0001 CAUSE: The driver finished transferring a data frame, but encountered an error while trying to send the frame to an upper layer protocol via a port message (“Cause”= 32-bit status returned by the call to vg_send_msg). ACTION: This is an informational error only.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values (“Cause”= 32-bit address of the DMA step against which the corruption was detected). Probably the driver attempted to perform a DMA transfer which was not a 4-byte multiple in length. ACTION: This is a warning that some timer resources may have been lost. The link did not connect. Typically preceded by another error message giving better information about the original cause; check log data for that error and look it up also.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: The driver acknowledged and dropped the interrupt and the received packet. Many upper layer protocols typically retransmit lost packets, so operation of the system and applications may continue with only minimal degradation. Exhausting all receive resources would be a highly unusual condition.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values • Bit 21 is 1 if a high priority operation was in progress, 0 if normal priority. • Bit 20 is 1 if the controller was fetching an instruction, 0 if it was transferring frames. • Bit 19 is 1 if the controller was working on receiving inbound data, 0 if it was a transmitting outbound data. • Bit 18 is 1 if the controller was attempting to read from adapter card memory, 0 if it was writing.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values This code would only appear in the formatted PHY chip trace from a 100VG-AnyLAN link connect failure. It would not appear in a log event. Seeing this error implies you are already using link tracing to try to debug a problem, or are analyzing driver context data directly. ACTION: The driver cleared statistics already, so none should overflow during link training unless there is a problem.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values MESSAGE: (None) 9680 (None) CAUSE: 100VG-AnyLAN link training failed because the LAN Controller chip unexpectedly reported an interrupt of a type which the driver should have specifically disabled at startup. A hardware failure state was then signaled. This code would only appear in the formatted PHY chip trace from a 100VG-AnyLAN link connect failure. It would not appear in a log event.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values This code would only appear in the formatted PHY chip trace from a 100VG-AnyLAN link connect failure. It would not appear in a log event. Seeing this error implies you are already using link tracing to try to debug a problem, or are analyzing driver context data directly. ACTION: This probably indicates a driver bug.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values ACTION: If a power failure has actually occurred, this error can be ignored; the driver should recover automatically. If the problem happens every time, see Appendix A, “Submitting an SR.” MESSAGE: (None) 9890 (None) CAUSE: 100VG-AnyLAN link training failed because, after the LAN Controller chip reported a status interrupt, the driver tried to read the generic register on the PHY chip, but detected an error.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values If the problem remains, use NMMGR to modify the LINK configuration for this link, to enable link tracing at startup. Reproduce the problem, then shut down the link and save the resulting NMTCnnnn.PUB.SYS trace data file for analysis by Hewlett-Packard. See Appendix A, “Submitting an SR.” MESSAGE: Adapter card reported an HP-PB fatal error.
100VG-AnyLAN and 100Base-T Error Messages SDI Driver Specific Status Values 282 Chapter 16
FDDI Error Messages 17 FDDI Error Messages The following error messages may appear when using or installing FDDI on your system. The following list consists of error messages that you may be able to resolve yourself. Other error messages may appear, but require the help of your HP representative. If the message number does not appear in this list, either write down the error if it is displayed on your console, take a system dump, or run the diagnostics before calling your HP representative for help.
FDDI Error Messages MESSAGE: FDDI link ! found incorrect HW or SW ID. 73 CAUSE: The FDDI driver found an old or incorrect version of the firmware or hardware on the FDDI interface card. ACTION: Update the card to the correct version. MESSAGE: FDDI link ! could not read hardware ID. 74 CAUSE: The FDDI driver could not read the FDDI hardware identification codes. ACTION: Run the diagnostic program to see if the hardware has failed. If so, replace the card.
LAP-B Link Error Messages 18 LAP-B Link Error Messages Messages generated by the LAP-B Link Modules are the following types: • LAP-B Link Startup Error Messages These messages are preceded by the text WAN MODULE CONFIG (linkname) where linkname is the name of a configured LAP-B link. • LAP-B Link Driver Error Messages These messages are preceded by the text LAPB (linkname) where linkname is the name of a configured LAP-B link.
LAP-B Link Error Messages LAP-B Link Startup Error Messages LAP-B Link Startup Error Messages The following message will automatically be displayed on the operator’s console when a network transport tries to startup the WAN driver: WAN MODULE CONFIG (linkname) Version: A0001037 This section describes error messages that might occur when you are starting a LAP-B link.
LAP-B Link Error Messages LAP-B Link Startup Error Messages ACTION: Either restore the PSILAPB0.PUB.SYS file from a backup tape, or wait for the program or process that has this file opened exclusively to close it. MESSAGE: FGETINFO failed to return recsize and/or numrec. 6 CAUSE: The file PSILAPB0.PUB.SYS is corrupted. ACTION: Restore the file from a backup tape. MESSAGE: FREEZE of download file failed. 7 CAUSE: The system is experiencing memory shortage problems.
LAP-B Link Error Messages LAP-B Link Startup Error Messages MESSAGE: Could not receive the config reply message. 13 CAUSE: Internal system ports problem. ACTION: Please record the error information printed on the console and contact your Hewlett-Packard representative. MESSAGE: Timeout waiting for the config reply message. 14 CAUSE: Could not configure the link software or the card. ACTION: Please record the error information printed on the console and contact your Hewlett-Packard representative.
LAP-B Link Error Messages LAP-B Link Startup Error Messages MESSAGE: Could not create or bind with the driver. 20 CAUSE: Possible causes for this problem are as follows: 1. (Status = FAxx00D9) The I/O subsystem still has the card configured and marked active. 2. (Status = E0xx00D5) The Bus converter is not configured. 3. (Status = DAxx00D5) There is no card in the slot for the path number given. 4. (Status = CDxx00D5) The card is bad for the path number given. 5.
LAP-B Link Error Messages LAP-B Link Startup Error Messages MESSAGE: Could not unfreeze the download file ! 22 CAUSE: The system is experiencing memory problems. ACTION: Please record the error information printed on the console and contact your Hewlett-Packard representative. MESSAGE: Could not close download file ! 23 CAUSE: The system is experiencing file system problems. ACTION: Please record the error information printed on the console and contact your Hewlett-Packard representative.
LAP-B Link Error Messages LAP-B Link Driver Error Messages LAP-B Link Driver Error Messages This section describes error messages generated by the LAP-B Link Driver. They are displayed on the HP 3000 Series 900 operator’s console in the following format: LAPB (linkname) Message text LAPB (linkname) Error ErrorNum, Status = Status, Path: PhysPath MESSAGE: The download file is too small. 1000 CAUSE: Possible causes for this problem are as follows: 1. The download file is corrupt. 2.
LAP-B Link Error Messages LAP-B Link Driver Error Messages MESSAGE: PSI fatal error, dinmode. 1004 CAUSE: Possible causes for this problem are as follows: 1. The download file is corrupt. 2. Bad PSI hardware. ACTION: Possible actions for this problem are as follows: 1. Replace the download file from your latest system update tape. 2. Run the Sherlock diagnostics on the PSI and call your Hewlett-Packard representative if a failure is detected. MESSAGE: PSI fatal bus error.
LAP-B Link Error Messages LAP-B Link Driver Error Messages MESSAGE: The PSI received a bad command from the driver. 1010 CAUSE: Internal error. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative. MESSAGE: PSI received a bad DMA command from the driver. 1011 CAUSE: Internal error. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative.
LAP-B Link Error Messages LAP-B Link Driver Error Messages MESSAGE: Attempt to download to a bad card address. 1016 CAUSE: Possible causes for this problem are as follows: 1. The download file is corrupt. 2. There is an incorrect version of the download file. ACTION: Possible actions for this problem are as follows: 1. Replace the download file from your latest system update tape. 2. Check the version of the download file with NMMAINT and call your Hewlett-Packard representative if incorrect.
LAP-B Link Error Messages LAP-B Link Driver Error Messages ACTION: Possible actions for this problem are as follows: 1. Run the Sherlock diagnostics on the PSI and call your Hewlett-Packard representative if there is an error. 2. Verify the configured path name is correct in NMMGR. 3. Verify that the target card is a PSI card. MESSAGE: Unsupported software model in IODC. 1025 CAUSE: Possible causes for this problem are as follows: 1. Bad PSI hardware. 2. Wrong path name is NMMGR. 3. Wrong card type.
LAP-B Link Error Messages LAP-B Link Driver Error Messages ACTION: Run the Sherlock diagnostics on the PSI and call your Hewlett-Packard representative if a failure is detected. MESSAGE: User invoked dump caused the driver to fail. 1032 CAUSE: A user manually instructed the driver to dump via diagnostic utilities when the driver had not encountered previous errors.
LAP-B Link Error Messages LAP-B Link Driver Error Messages MESSAGE: Download file is incorrect for this driver. 1036 CAUSE: Hardware was successfully downloaded, but the downloaded code turned out to be for a different driver. Someone may have incorrectly renamed a download file to have the name of the file expected by the driver, or your download file or installed driver may be extremely old and not matched. ACTION: Run NMMAINT.PUB.SYS to verify the version of the download file and driver.
LAP-B Link Error Messages LAP-B Link Driver Error Messages ACTION: If you suspect your system may be low on timer resources due to heavy loading, try restarting the link later. If repeated attempts fail, warmstart your system. If the problem persists, a system dump will be required; call your Hewlett-Packard representative. MESSAGE: Unable to reset an I/O Services timer. 1041 CAUSE: The system rejected an attempt by the driver to reset a timer supposedly owned by the driver.
LAP-B Link Error Messages LAP-B Link Driver Error Messages ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative. MESSAGE: Attempted impossible state after a request or completion. 1047 CAUSE: The driver attempted to enter a state which it should never be able to get into, and ceased operations instead. Memory data corruption, a driver bug, or a problem with the execution priorities of the driver and/or its hardware may exist.
LAP-B Link Error Messages LAP-B Link Driver Error Messages ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative. MESSAGE: Request received in invalid state. 1053 CAUSE: The driver received a sequencing message at the wrong time. This was a startup, shutdown, or dump-control message which arrived out-of-sequence.
LAP-B Link Error Messages LAP-B Link Driver Error Messages MESSAGE: Input buffer passed in a message is too small. 1057 CAUSE: Data was requested from the driver but the length of the buffer specified in the request was too small to accept all the data. The driver is not capable of returning partial data. The driver also imposes a minimum-size limit on trace buffers. ACTION: If the problem occurred when starting trace, try specifying a larger trace-buffer size.
LAP-B Link Error Messages LAP-B Link Driver Error Messages ACTION: Check to see if the transport reported any initialization errors. Run NMMAINT.PUB.SYS to verify the versions of the driver, module configurator, and download file. If the problem cannot be solved from this information, call your Hewlett-Packard representative. MESSAGE: Bad top plane buffer pool in configuration data.
LAP-B Link Error Messages LAP-B Link Driver Error Messages MESSAGE: Unknown driver problem. 1066 CAUSE: The driver detected an error, but did not say what type of error was detected. ACTION: Write down the error information displayed on the console, submit an SR, and call your Hewlett-Packard representative. MESSAGE: Unknown error while attempting to autodial. 2013 CAUSE: Before attempting to autodial, the PSI detected something wrong.
LAP-B Link Error Messages LAP-B Link Driver Error Messages ACTION: Check to see if the cable is properly attached. If it is, try another cable. If you still get this error, write down the error information displayed on the console, submit an SR, and call you local Hewlett-Packard representative. MESSAGE: There was a read from the PSI which completed with a error. 2500 CAUSE: Possible causes for this problem are as follows: 1. The link is down. 2. You have a faulty PSI. 3.
LAP-B Link Error Messages LAP-B Link Driver Error Messages MESSAGE: PSI cannot send a frame across the line. 2505 CAUSE: Possible causes for this problem are as follows: 1. Link could be down. 2. Bad PSI hardware. 3. Internal PSI or driver error. ACTION: Possible actions for this problem are as follows: 1. Check the cabling and modem. 2. Run Sherlock diagnostics to determine the cause. 3. Write down the console error messages, submit an SR and call your Hewlett-Packard representative.
LAP-B Link Error Messages LAP-B Link Shutdown Error Messages LAP-B Link Shutdown Error Messages This section describes error messages that might occur when you are shutting down a LAP-B link. These messages appear when a NETCONTROL STOP command calls the WAN_Kill_Module and encounters an error.
LAP-B Link Error Messages LAP-B Link Shutdown Error Messages MESSAGE: Could not delete the auxiliary buffer pool. 56 CAUSE: There are many reasons why this could happen. The status indicator provides more detailed information as to the specific cause of the problem. ACTION: Please record the error information printed on the console and contact your Hewlett-Packard representative. MESSAGE: Could not determine the PSI path number IO Serv.
LAP-B Link Error Messages LAP-B Link Shutdown Error Messages 308 Chapter 18
Logging Location Codes 19 Logging Location Codes Logging records events such as errors and console commands. You configure logging for each of the subsystems of NS 3000/iX. Within each subsystem, there are different classes of events (such as internal errors). You can record logging to a disk, the system console, and/or the logon device of a user account.
Logging Location Codes Logging Formats Logging Formats Node Management Services automatically format logging records sent to the console. Logging records sent to a disk file are stored in coded form. These records are decoded and formatted by the NMS Trace/Log File Analyzer (NMDUMP), an NMS system utility program. Figure 19-1 shows a typical log record formatted by NMDUMP. To learn how to use NMDUMP see the Log and Trace Files section in Using the Node Management Services (NMS) Utilities manual.
Logging Location Codes Logging Subsystems Logging Subsystems Each subsystem of NS 3000/iX has its own set of classes for logging events.
Logging Location Codes Logging Subsystems Subsystem Name Class Name Events Lap B Link CLAS0012 Informational messages SUB0040 CLAS0001 Catastrophic errors Remote Link Manager CLAS0002 Serious errors CLAS0003 Notable errors CLAS0004 Nodal messages (start/stop) CLAS0005 Informative messages SUB0057 CLAS0001 Fatal errors SNMP CLAS0002 Serious errors CLAS0003 Warnings CLAS0004 Informational messages SUB0061 CLAS0001 Errors Token Ring Link CLAS0002 Warnings CLAS0003 Informatio
Logging Location Codes Logging Subsystems explanation for each logging location code includes the Internal Event description and Parm description, if relevant, as shown in the typical formatted log example in Figure 19-1. The Path Network Transport Entity logs no event information. PARM Value Many Network Transport logging records contain important information in the Parameter value. This Parameter number indicates the shutdown reason.
Logging Location Codes Logging Subsystems Entity Numbera Entity Description L2Resolve 140 Part of the process between NS Transport and SNA Transport that provides NS over SNA/XL functionality. (This product is obsolete.) LAN NI 0 The network interface for the LAN connection performs functions for IP store and forward over IEEE 802.3 and Ethernet links. Loopback NI 9 The network interface for software loopback performs loopback by converting outbound messages to inbound messages.
Logging Location Codes Logging Subsystems Entity Numbera Entity Description User Interface 101 The NETCONTROL command user interface. Interprets all Transport commands and passes them to the control process if they are valid, refer to. X.25 NI 6 The network interface for X.25 connections passes packets between TCP/IP and the Multiple Connection Manager module for X.25 devices, which in turn interfaces to the DTC. X.25 PM 118 Interfaces with TCP to provide X.25 protocol functions.
Logging Location Codes Logging Subsystems Entity Numbera Entity Description IP Module Configurator and Deconfigurator 154 These procedures create an instance of the L2Resolve protocol module when an NI is started, and destroy it when the NI is stopped. X25 Module Configurator and Deconfigurator 155 These procedures create an instance of the X.25 protocol module when an NI is started, and destroy it when the NI is stopped.
Logging Location Codes Logging Subsystems Table 19-3 Network Service Modules Module Description BFM The NS Buffer Management module provides for the allocation of buffers for the other NS modules. (The NS Buffer Management module is different from the Buffer Management software used by the transport and translator.) CX The Command Executor module parses and executes the NS commands DSLINE, REMOTE, and NSCONTROL.It is also the primary user interface (through the REMOTE command) to the VT service.
Logging Location Codes Logging Subsystems user on $STDLIST. However these messages are displayed on $STDLIST only if logging is enabled for the Network Services subsystem of NS 3000/iX. Other Network Services—such as Network File Transfer, Program-to-Program Communication, and Remote File Access, return error information to the user regardless of logging configuration for the Network Services subsystem of NS 3000/iX.
Logging Location Codes Using Log Files Using Log Files The key information in each log message is the log class and the location code number, which uniquely identify the logging message for that entity, and the Parm. You use these numbers to find the explanation and action in the tables in this section and other sections of this manual. The actions given should be performed. Only if there is no clear error reported or the recommended action fails should system level troubleshooting be performed.
Logging Location Codes Using Log Files Figure 19-2 Class 3, A Non-Critical Transport Error Statistics Logging Example An example of log class 6, statistics, is shown in Figure 19-3. Figure 19-3 shows a statistics log message for TCP. This example shows an informative, or Class 3, log message for TCP. The first part describes the log message, including the event, the entity, the internal event and the log class.
Logging Location Codes Using Log Files Figure 19-3 Logging Statistics Example The key information in each log message is the log class and the location code number, which uniquely identify the logging message for that entity, and the parameter. You use these numbers to find the explanation and action in this section and other sections of this manual.
Logging Location Codes Using Log Files • IPC Port ID. Gives the address of the NetIPC port associated with the TCP (or PXP) protocol module for this connection. This is the number to use in matching a TCP/PXP Statistic log message to a NetIPC log message. Look for the identical number called the Socket Port ID in the NetIPC log message. • Bytes sent/received. Shows the total number of bytes transmitted or received by the PM. • User pkts sent/recd. Shows the number of packets sent or received.
Logging Location Codes Using Log Files (reversed) to find the matching PM in the log file for the remote node. Specify a time range when formatting the remote node log file to narrow the search. • Flags/Flags1/Flags2. Internal state flags. • ICMP msgs recd. Total number of ICMP messages that this connection has received from the IP module. • Local/Remote IP addr. Shows the IP address for the local and remote node. • Source quenches. Shows the number of times this connection has been quenched.
Logging Location Codes ARP Logging Location Codes ARP Logging Location Codes MESSAGE: None 1 CLAS0002 CAUSE: A port message was received containing an invalid function code (PARM = function code). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 3 CLAS0004 CAUSE: ARP protocol started. ACTION: Informative message. MESSAGE: None 12 CLAS0003 CAUSE: An ARP packet with a bad ARP header was received from the link.
Logging Location Codes ARP Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 55 CLAS0002 CAUSE: Failed to locate ARP’s ICS filter routine in NL.PUB.SYS. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 56 CLAS0002 CAUSE: Failed to locate ARP’s timer routine in NL.PUB.SYS. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 57 CLAS0002 CAUSE: Failed to locate ARP’s port procedure in NL.PUB.SYS.
Logging Location Codes ARP Logging Location Codes MESSAGE: None 65 CLAS0002 CAUSE: Failed to send ARP request out over the network. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 66 CLAS0002 CAUSE: Failed to send ARP request out over the network. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 67 CLAS0002 CAUSE: An attempt to get a buffer failed due to an internal error in the buffer manager.
Logging Location Codes ARP Logging Location Codes ACTION: Either the packet was corrupted in transit or a remote node is not transmitting packets correctly. If the latter case is suspected, see Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 74 CLAS0002 CAUSE: Failed to update the NS Registry with ARP’s port. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 75 CLAS0002 CAUSE: Failed to remove ARP from the NS Registry.
Logging Location Codes Control Process Logging Location Codes Control Process Logging Location Codes Control Process logging location codes are generated by the NETCP process of Network Transport. For each of the logging explanations, any or all of the following may be present: PARM = Meaning of the parameter logged. PORT = Transport port number of the Control Process. NI = Network Interface Type against which the event was logged: • FDDI = Fiber Distributed Data Interface LAN.
Logging Location Codes Control Process Logging Location Codes ACTION: One or more network protocols were not completely started. Stop the network and use NMMGR to make sure a nodename is configured and the NMCONFIG file is validated. If the file looks good, try restarting the network. If the problem persists, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes MESSAGE: INTERNAL ERROR; Configuration file error 25 CLAS0002 CAUSE: While initially starting up, NETCP’s attempt to get the global information record from the NETXPORT.GLOBAL path in the NMCONFIG file failed (PARM = 32-bit status returned by the call to nmconfgetdata). ACTION: Transport did not start. Verify the configuration file exists, and if this is not the problem, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes MESSAGE: INTERNAL ERROR; Async request from link 33 CLAS0002 CAUSE: NETCP received an asynchronous event message containing a negative error status, from the DCLDM controlling one of the LAPB links on the network (PARM = 32-bit status field from the message). ACTION: NETCP stopped the device associated with the link, also stopping any attached protocols and driver. Run the PSIDAD diagnostic on the appropriate PSI card.
Logging Location Codes Control Process Logging Location Codes For X.25 links (and/or hardwired terminals), if a DTC link is in use the DTC and network links may have same physical path specified in NMMGR; try specifying separate physical LAN cards. Make sure the DTC configuration was validated with NMMGR.
Logging Location Codes Control Process Logging Location Codes ACTION: None. This is an informative message only. It is only logged after all outstanding replies have been received from the general protocols. This message does not imply that Transport is completely down, nor does it imply successful shutdown, only that there is very little cleanup left to do. It is possible that another instance of Transport can be successfully started before this message appears.
Logging Location Codes Control Process Logging Location Codes ACTION: This error in itself was not fatal, and shutdown continued. However, the NMCONFIG file may be inaccessible. If the problem occurs repeatedly, see Appendix A, “Submitting an SR,” of this manual. MESSAGE: INTERNAL ERROR; Bad/unknown port message 84 CLAS0002 CAUSE: A message with an unrecognized function code was received on the NETCP port while NETCP was idle and waiting for new commands (PARM = the 16-bit unknown message function code).
Logging Location Codes Control Process Logging Location Codes ACTION: No message to enable tracing was sent to the desired entity. Check that sufficient discspace is available on the system, and that trace filename specified in the link screen of the NMCONFIG file, or in the :NETCONTROL TRACEON command is legal and does not violate file system security rules. If this does not reveal the cause, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes Path Verify storms (a large number of Path Verify operations during a short time period) can occur if a heavily used high speed link suddenly fails. During storms, if NETCP receives new Path Verifies or any other requests while awaiting previous replies, they are queued for later execution if they are unique. If a new Path Verify is a duplicate of one already queued, the new one is counted and then discarded.
Logging Location Codes Control Process Logging Location Codes MESSAGE: STATIC UPDATE: Update 170 CLAS0005 CAUSE: NETCP is about to send a GATEWAY update message to IPU for a specific IP address, because a network is stopping (PARM = 32-bit IP address being updated). ACTION: None. This is an informative message only. IPU will use information in the message to update its tables.
Logging Location Codes Control Process Logging Location Codes ACTION: Though no DCN message was sent, network startup probably continued to completion, but connections over the affected network may not work. Probably all the NETCP buffers have somehow been used up, though it should have allowed for enough to support starting any supported network configuration. Stop Transport and use NMMGR to validate the NMCONFIG file and check for obvious file corruption, then restart the network.
Logging Location Codes Control Process Logging Location Codes ni_module_config). Always preceded by another error from the module configurator (having a different Entity number, such as 151–160), logging the reason for the original failure. ACTION: Record the previous error and this error. See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes the phone system; additional information may be gained by enabling logging classes 10 and 12 for link subsystem 28 (LAPB) and class 0 for subsystem 4 (DCLDM). MESSAGE: INBOUND; Device connected 258 CLAS0003 CAUSE: NETCP received an asynchronous event message from the DCLDM indicating that its LAPB PSI link has established a level 2 connection (PARM = 16-bit internal ldev number of the device). ACTION: None. This is an informative message only.
Logging Location Codes Control Process Logging Location Codes MESSAGE: INBOUND; INTERNAL ERROR; Async request from link 262 CLAS0005 CAUSE: NETCP received an asynchronous event message from the DCLDM indicating its LAPB PSI link reported some sort of miscellaneous warning (PARM = 16-bit internal ldev number of the device). ACTION: None. This is an informative message only.
Logging Location Codes Control Process Logging Location Codes MESSAGE: INTERNAL ERROR; Configuration file error 278 CLAS0002 CAUSE: While processing a :NETCONTROL command to start or update a network or add a link, NETCP successfully opened the NMCONFIG file, but was unable to lock it (PARM = 32-bit status returned by the call to nmconflockfile). ACTION: The command did not execute, and NETCP closed the open file.
Logging Location Codes Control Process Logging Location Codes ACTION: This problem in itself was not fatal, and link shutdown continued. However, there may be a problem with the link driver software or hardware. Most shutdown problems are warnings, not errors (see error 54).
Logging Location Codes Control Process Logging Location Codes MESSAGE: INTERNAL ERROR; NM Entry 286 CLAS0003 CAUSE: Near the end of NETCP’s early initial startup, it was unable to put its port number into a new entity named “NetCP” in the NS Registry (PARM = 32-bit status returned by the call to reg_add_entity). ACTION: This error was not fatal, and startup continued; use of the Registry here is not critical.
Logging Location Codes Control Process Logging Location Codes MESSAGE: BUFFER MANAGER; Buffer manager error 292 CLAS0002 CAUSE: While building a buffer containing all X25 configuration data for a network, NETCP successfully obtained a buffer of the supposedly correct size, but later encountered an error attempting to write a block of Network Directory address information to the buffer (PARM = 32-bit status returned by the call to bmgr_write_buffer).
Logging Location Codes Control Process Logging Location Codes ACTION: Turn on the autodial unit and check for power and correct cabling. Then attempt to dial out again. MESSAGE: OUTBOUND; Data line occupied 303 CLAS0003 CAUSE: NETCP received an asynchronous event message from the DCLDM indicating that its LAPB PSI autodial failed because the line was busy or a phone line was not available (PARM = 16-bit internal ldev number of the device). (Some pre-5.
Logging Location Codes Control Process Logging Location Codes indicating its LAPB PSI link reported that the remote side was establishing or had already established a connection (PARM = 16-bit connect event code from LAPB). ACTION: None. This is an informative error message only. The connection was successfully established, but through the initiative of the remote side, not the local. NETCP then disconnected the device at the local side.
Logging Location Codes Control Process Logging Location Codes MESSAGE: INTERNAL ERROR; Dial 316 CLAS0003 CAUSE: NETCP received a legal dial request message but encountered an error while downloading the phone number to the link (PARM = 32-bit status returned by the call to xp_driver_config_dial). ACTION: This event may follow a previous asynchronous link error, which may indicate the original problem. Another possibility is that the DCLDM or LAPB driver are hung.
Logging Location Codes Control Process Logging Location Codes possible too much frozen memory is being used by the system, but this can change with time. Use GLANCEXL or a similar utility to check memory usage by the system. If these are not the causes and the problem persists even if retried after a suitable waiting period, seeAppendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes MESSAGE: Overwrote X25 Addr/DDN 411 CLAS0003 CAUSE: While collecting configuration data for startup of an X25 network, NETCP found that a user had specified an X25 address for a remote node was on a DDN Network, but had also supplied the actual address. Instead, the X25 address should be derived from the IP address by the Transport code (PARM = 0). ACTION: Verify that the network interface started is actually for a DDN Network.
Logging Location Codes Control Process Logging Location Codes ACTION: This error in itself was not fatal, and NETCP continued operating. Some kind of timing condition may have occurred. Another possibility is NETCP or a DCLDM may be confused. If the problem occurs repeatedly, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes ACTION: The LAN network did not start. Use the LANDAD tool to verify the LAN hardware is functioning correctly. If it looks good, there may be a problem with the LAN driver software or a bug in NETCP; see Appendix A, “Submitting an SR,” of this manual. MESSAGE: INTERNAL ERROR; Device close 420 CLAS0002 CAUSE: While stopping an 802.
Logging Location Codes Control Process Logging Location Codes ACTION: None. This is an informative message only. In many cases the DTC will recover on its own. If this does not happen, use the DTC Manager to find the reason why levels 2/3 are not up. Once the problem is corrected on the DTC, the host will be informed and will start using the device. MESSAGE: LOGGING; Log 500 CLAS0005 CAUSE: NETCP has received a message instructing it to process one of the general :NETCONTROL commands (PARM = hex 330).
Logging Location Codes Control Process Logging Location Codes MESSAGE: Bad status 602 CLAS0002 CAUSE: While attempting to send an X25 restart request message to the X25 protocol module, NETCP encountered an error on the send (PARM = 32-bit status returned by the call to send_msg). ACTION: X25 did not receive the restart request. This will cause the X25 network to enter a bad state. Stop and restart that network. If this problem continues, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes ACTION: This error was not fatal, and network shutdown continued. However, since pool ID’s should always appear in both tables, NETCP is confused. Even if the pool ID in the device table was valid, NECP could not be sure, so to be safe the buffer pool was not deleted, and the NS Registry may still contain that pool ID. The amount of system memory used by this buffer pool may be inaccessible until the next system restart.
Logging Location Codes Control Process Logging Location Codes ACTION: This error in itself was not fatal, and shutdown continued. However, the entry should have been there. If the same error occurs again, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes pool were lost, or are still outstanding in modules which remain in the background after NETCP terminates. If the problem occurs repeatedly, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes MESSAGE: INTERNAL ERROR; Data dictionary error 617 CLAS0002 CAUSE: During the later phases of initial NETCP startup, NETCP encountered an error trying to add its own port number into a CM Port Dictionary entry named “NetCP”, for use by various CM transport modules such as PROBE (PARM = 16-bit result code returned by the call to dict_add). The CM Port Dictionary is an operating system lookup service used by, but not part of, Transport.
Logging Location Codes Control Process Logging Location Codes ACTION: This error was not fatal, and network startup continued. However, additional errors will occur later when NETCP tries to delete the linkname (see error 660). In addition, certain X25 operations may not work correctly. Restart the network. If this problem continues, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes 622 CLAS0002 CAUSE: While attempting to send a DCN start message to IPU in response to an X25 automatic restart or a user’s :NETCONTROL START or :NETCONTROL ADDLINK command, NETCP encountered an error on the send (PARM = 32-bit status returned by the call to send_msg). A DCN start message is required for a Directly Connected Network such as X25. ACTION: IPU did not receive the message, so it does not know the network is started.
Logging Location Codes Control Process Logging Location Codes pool were lost, or are still outstanding in link drivers or in Transport modules which had previously encountered errors. If the problem occurs repeatedly, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes them within a 15-second timeout period (PARM = 32-bit port number of the general protocol module which failed to reply). One of these errors will appear for each module that fails to reply. ACTION: This error in itself was not fatal, and NETCP processing continued. This can mean either that a temporary Path Verify storm is occurring because a heavily used link has failed, or it can mean there is a problem with the general protocol module.
Logging Location Codes Control Process Logging Location Codes problem with the path, and may continue to try to use it. In addition, PING commands from NETTOOL may report errors against the affected network. If the problem persists, see Appendix A, “Submitting an SR,”A of this manual.
Logging Location Codes Control Process Logging Location Codes hang. To clear this condition, first try a :NETCONTROL DELLINK=linkname; NET=niname command against the affected link, followed by a :NETCONTROL ADDLINK=linkname; NET=niname. If this does not help, a system restart will probably be required to clear the hang. If the problem occurs again, take a dump when the error is reported and before any attempts to recover, and see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes encountered an error trying to initialize the NETIPC Socket Timers module (PARM = 32-bit status returned by the call to sk_ti_start). May be preceded by another error from NETIPC, logging the reason for the original failure. ACTION: Newer versions of Transport treat this as a fatal error, and Transport startup will fail.
Logging Location Codes Control Process Logging Location Codes MESSAGE: INTERNAL ERROR; Module Deconfig Failed 641 CLAS0002 CAUSE: While shutting down Transport due to a system shutdown or a :NETCONTROL STOP command, NETCP detected an error or warning while attempting to stop the Net Timers module (PARM = 32-bit status returned by the call to nettmr_module_deconfig). Always preceded by other errors from Net Timers, indicating the cause of the original failure.
Logging Location Codes Control Process Logging Location Codes file may be corrupt, or there may be a bug in the NMS subsystem, NMMGR, or NETCP; see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes from the NMCONFIG file, then encountered an error trying to write that data into a buffer it obtained a short time earlier (PARM = 32-bit status returned by the call to bmgr_write_buffer). ACTION: NETCP was unable to write all the required data, and attempted to recover and free the buffer. The network operation that was being performed will not work correctly.
Logging Location Codes Control Process Logging Location Codes previous error and this error. Stop the network. If there is no hang, then try restarting the network. If the problem persists, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes mode was, at some time in the past, used to create the first NS configuration ever put into the NMCONFIG file, and that a bug in the Validation function of an earlier version of Transport then corrupted a hidden record in that file, which specifies IPU startup information. If you suspect “Unguided Config” mode was used, you can try to repair the hidden record. First make a copy of the old NMCONFIG file.
Logging Location Codes Control Process Logging Location Codes the network. If the problem still occurs, then depending on the error, it is possible too much frozen memory is being used by the system, but this can change with time. Use GLANCEXL or a similar utility to check memory usage by the system. If memory is not the cause and the problem persists even if retried after a suitable waiting period, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes ACTION: This secondary error is not the main concern, though it may indicate additional problems. The general protocols were started, but the specified network failed to start because of the first error. Retry the operation. If the problem persists, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes ACTION: This error in itself was not fatal, and network startup continued. However, X25 may not operate correctly. If X25 connections are not working, stop then restart the network. If the problem persists, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes ACTION: The second error in itself was not fatal, and Transport should continue to run. However, if the session which issued the :NETCONTROL STATUS command still exists, that session will now be hung. If the session does not exist, this also indicates a bug since supported HP commands to abort the session should have been disabled by NETUI. A system restart will be required to clear the session's hang.
Logging Location Codes Control Process Logging Location Codes 671 CLAS0002 CAUSE: During startup of the SNMP module, the configuration file was unlocked. But afterwards, NETCP tried for up to 2 minutes to lock the file again without success (PARM = status from NMConflockfile). The 2-minute timeout is not configurable. ACTION: Network startup was incomplete. Stop the network. Use :LISTF NMCONFIG.PUB.SYS,3 to verify the NMCONFIG file exists and is not opened.
Logging Location Codes Control Process Logging Location Codes ACTION: The new request message has probably been lost, and depending on the purpose of message, whatever module sent it may be expecting a reply which will never come, so that module or session may now be hung. For debugging purposes the message content was logged in the NM logfile along with this error, which may aid in debugging any hung modules.
Logging Location Codes Control Process Logging Location Codes which may aid in debugging any hung modules. If the problem occurs repeatedly or a general protocol bug is suspected, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes Because the buffer given to NETCP by the buffer manager should have been large enough to contain all data that was to be written, there may be a problem in either NETCP, the buffer manager, the NMS subsystem, NMMGR, or the NMCONFIG file may be corrupt. Use NMMGR to check the X25 configuration in the file. Stop the network and retry the operation. If the problem persists, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Control Process Logging Location Codes encountered an error trying to read other data entries to match up to the first one (PARM = 32-bit status returned by the call to bmgr_read_buffer). ACTION: The current matching operation stopped, then more merging of X25 mappings may have continued, possibly causing more errors, then the bad configuration data was passed to the X25 protocol module. The X25 network will probably not operate correctly now.
Logging Location Codes Control Process Logging Location Codes software installation problem, a bug in the NMS subsystem, or a corrupt NMCONFIG file; if necessary, see Appendix A, “Submitting an SR,” of this manual. MESSAGE: Module Deconfig Failed 689 CLAS0002 CAUSE: While shutting down Transport due to a system shutdown or a :NETCONTROL STOP command, NETCP encountered an error trying to delete the NETIPC Socket Registry module (PARM. (0:16) = error location within SOCKREG.NET.SYS and PARM.
Logging Location Codes NS Configurator Logging Location Codes NS Configurator Logging Location Codes Several NS Configurator modules are called by the NETCP process of Network Transport. Each of these is responsible for starting or stopping one Transport module, and performs only those module-specific actions which are needed.
Logging Location Codes NS Configurator Logging Location Codes MESSAGE: INTERNAL ERROR; Internal resource error 4 CLAS0002 CAUSE: When NETCP attempted to create a new NI or a new protocol module for an existing NI, after successfully creating a Port Data Area and locating a server plabel, an error occurred while trying to create a message port for the module (PARM = 32-bit status returned by the call to create_port).
Logging Location Codes NS Configurator Logging Location Codes MESSAGE: INTERNAL ERROR; Internal resource error 9 CLAS0002 CAUSE: When NETCP attempted to create a new protocol module for an existing NI, after successfully creating a message port for the module and sending other messages to it, an error occurred while trying to send an Information message (PARM = 32-bit status returned by the call to send_msg).
Logging Location Codes NS Configurator Logging Location Codes MESSAGE: INTERNAL ERROR; Internal resource error 16 CLAS0002 CAUSE: When NETCP attempted to create a new protocol module for an existing NI, an error occurred while trying to read the pool ID for that modules message port (PARM = 32-bit status returned by the call to xp_get_pool_id). ACTION: There may be a problem with the port_info call into the Ports subsystem of MPE. See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes NS Configurator Logging Location Codes ACTION: Resources allocated to the module were not released. Another module may have unexpectedly sent a message to the reply subqueue of NETCP’s Transport port, or the module which received the termination message may be confused. If this problem occurs every time, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes NS Configurator Logging Location Codes ACTION: The object may have already been released by MPE when the port was purged, indicating a bug in the Module Deconfigurator. Otherwise there may be a problem with the Virtual Space Management subsystem of MPE. If this problem occurs every time, seAppendix A, “Submitting an SR,” of this manual.
Logging Location Codes CX Logging Location Codes CX Logging Location Codes MESSAGE: None 1 CLAS0003 CAUSE: The NS keyword table was not allocated during system startup prior to an NS command execution. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 2 CLAS0003 CAUSE: The NS global data segment was not allocated during system startup, or has been lost. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 3 CLAS0003 CAUSE: Bad format in the ASCAT.NET.
Logging Location Codes CX Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 10 CLAS0003 CAUSE: A port for communication between the CI and CT server process could not be created. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 11 CLAS0002 CAUSE: A port DST entry could not be allocated for the port between the CI and VT server. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes CX Logging Location Codes MESSAGE: None 18 CLAS0002 CAUSE: A port message with the remote command could not be sent from the CI to the VT server process. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 19 CLAS0003 CAUSE: A port message send to DSDAD failed. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 21 CLAS0003 CAUSE: The DSLINE JCW, set to the DSLINE number by the NS software, could not be found.
Logging Location Codes DC/LDM Logging Location Codes DC/LDM Logging Location Codes DC/LDM (Data Comm Logical Device Manager) is a module between NS Transport and the LAP-B Driver, which helps provide NS over point-to-point Router networks. MESSAGE: Send_msg error 2 CLAS0000 CAUSE: While DC/LDM was attempting to send a message to another module, for some normal purpose (other than an error reply), the system routine send_msg reported an error. ACTION: No message was sent.
Logging Location Codes DC/LDM Logging Location Codes ACTION: No message was sent, so the CM module may not be aware any problem has occurred. This may affect other operations on the network. See Appendix A, “Submitting an SR,” of this manual. MESSAGE: Invalid CM request received in current state 17 CLAS0000 CAUSE: During error processing of an invalid write event, DC/LDM discovered the message it was working on was not a write event message.
Logging Location Codes DC/LDM Logging Location Codes ACTION: DC/LDM will continue operating, but if this situation continues, the network may run out of buffers. In addition, any subsequent network shutdown may hang. See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes DC/LDM Logging Location Codes MESSAGE: Asynchronous error event received from lower manager 33 CLAS0000 CAUSE: DC/LDM received a fatal error notification event message from a lower level LAN or LAP-B driver. This logs the error status reported by that driver. ACTION: DC/LDM is still operating, but the driver is probably not. It has flushed (replied to) any pending requests for the link which reported the error.
Logging Location Codes DC/LDM Logging Location Codes ACTION: DC/LDM continued stopping, but this could indicate a more serious problem in the High Level I/O system or the DC/LDM. If the problem occurs every time, see Appendix A, “Submitting an SR,”of this manual. CAUSE: While flushing its port subqueues, DC/LDM found an I/O request message on its port having a nonzero buffer ID, but when trying to free the BMGR buffer referenced by that message, the system routine bmgr_free_buffer reported an error.
Logging Location Codes Dial ID Logging Location Codes Dial ID Logging Location Codes MESSAGE: None 1 CLAS0001 CAUSE: A port message was received containing an invalid function code (PARM = function code). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 2 CLAS0004 CAUSE: Dial ID protocol started. ACTION: Informational message. MESSAGE: None 3 CLAS0002 CAUSE: The room allocated for the node name and path report is too small (PARM = required number of bytes needed).
Logging Location Codes Dial ID Logging Location Codes MESSAGE: None 9 CLAS0001 CAUSE: The sending of a link shut message to the Control Process using DICTSEND failed (PARM = result code of DICTSEND call). ACTION: Informational message. MESSAGE: None 10 CLAS0002 CAUSE: The status returned from the Control Process attempting to download the phone number to the device (PARM = result of NMLINKDIAL call). ACTION: Verify that the phone number is correct in the configuration file.
Logging Location Codes Dial ID Logging Location Codes (2) There is a dial request outstanding to a node with a different IP address than the one attempting connection. A reply rejecting the request is sent to the remote node. ACTION: Verify that there is a valid mapping entry in the configuration file for the remote node.
Logging Location Codes Dial ID Logging Location Codes MESSAGE: None 33 CLAS0002 CAUSE: The sequence number of a reply packet sent from a remote node does not match sequence number sent in the request packet sent from the local node. Either the reply packet has been corrupted or the remote node is not responding correctly to the Dial ID request packet (PARM = sequence number received in the reply message) ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Dial ID Logging Location Codes MESSAGE: None 41 CLAS0002 CAUSE: An acknowledgment packet was received but the Dial ID protocol was not in the correct internal state to receive an ack (PARM = state of the Dial ID protocol) ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 42 CLAS0002 CAUSE: The sequence number of an acknowledgment packet does not match sequence number sent in the reply packet.
Logging Location Codes Dial ID Logging Location Codes ACTION: Verify that the security string configured under the Dial ID protocol at the local node matches the one sent by the remote node. MESSAGE: None 48 CLAS0002 CAUSE: The security string contained in the remote node’s request packet does not match any of the strings configured at the local node.
Logging Location Codes Dial ID Logging Location Codes ACTION: It is possible that if the remote node is heavily congested the queue element can be deleted before the late packet arrives. This can be considered normal. If the problem does not appear to be related to this then see Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 55 CLAS0002 CAUSE: The sequence number of an ack-ack packet does not match sequence number sent in the acknowledgment packet.
Logging Location Codes Dial ID Logging Location Codes MESSAGE: None 86 CLAS0003 CAUSE: Dial is entering the TIME WAIT state after a normal ack-ack message. ACTION: None. Informational only. MESSAGE: None 87 CLAS0003 CAUSE: A link failure occurred, and Dial is cleaning up the resources (PARM = status). ACTION: None. Informational only. MESSAGE: None 88 CLAS0002 CAUSE: A call to BFMGETBUF failed when attempting to get an outbound buffer for a reply packet (PARM = result of BFMGETBUF).
Logging Location Codes Dial ID Logging Location Codes MESSAGE: None 94 CLAS0002 CAUSE: Received a CP reply message after the start request timer has expired. ACTION: None. MESSAGE: None 95 CLAS0002 CAUSE: MAP_CM_DIAL_INBOUND call failed with a MAP internal error. The MAP result code is in the parm field. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 96 CLAS0002 CAUSE: MAP_CM_DIAL_INBOUND call failed with an unknown error code. The error code is in the parm field.
Logging Location Codes DSDAD Logging Location Codes DSDAD Logging Location Codes MESSAGE: None 1 CLAS0003 CAUSE: Buffer space for DSDAD’s global data structure could not be created. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 2 CLAS0003 CAUSE: Header for the DSDAD data structure could not be created. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 3 CLAS0003 CAUSE: DSDAD log buffer could not be created.
Logging Location Codes DSDAD Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 11 CLAS0005 CAUSE: Attempt to create a socket failed. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 22 CLAS0003 CAUSE: Request for a server initiation could not be satisfied because of an invalid port message. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes DSDAD Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 31 CLAS0003 CAUSE: ServerInSession request could not be handled because server entry was not found. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 32 CLAS0003 CAUSE: Logoff entry could not be allocated. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes DSSERVER Logging Location Codes DSSERVER Logging Location Codes MESSAGE: None 1 CLAS0003 CAUSE: DSSERVER stack log buffer could not be allocated. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 2 CLAS0003 CAUSE: DSSERVER header for data structures could not be allocated. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 3 CLAS0003 CAUSE: Stack buffer space for DSSERVER data structures could not be created.
Logging Location Codes DSSERVER Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 11 CLAS0003 CAUSE: Could not find a wait entry for nowait I/O which completed. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 12 CLAS0003 CAUSE: The VT service reported an error. ACTION: Repair the VT error, if possible. MESSAGE: None 13 CLAS0003 CAUSE: RFA service reported an error. ACTION: Repair the error, if possible.
Logging Location Codes DSUTIL Logging Location Codes DSUTIL Logging Location Codes MESSAGE: None 8 CLAS0002 CAUSE: SYSTEM reached maximum allowable limit of NFT servers. Limit is set by the NSCONTROL command. Users request servers with the DSCOPY command or the DSCOPY intrinsic. ACTION: Wait until fewer DSCOPY applications are running on the system. Try again. Or ask the system manager to raise the limit of allowable NFT servers (via NSCONTROL).
Logging Location Codes ENV Logging Location Codes ENV Logging Location Codes MESSAGE: None 1 CLAS0002 CAUSE: Buffer space for DSLINE table could not be created. ACTION: Increase the number of configured DSTs. MESSAGE: None 2 CLAS0003 CAUSE: Trace file for an NS service could not be opened. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 3 CLAS0003 CAUSE: Trace file for an NS service could not be closed. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes ENV Logging Location Codes MESSAGE: None 10 CLAS0002 CAUSE: Extra data segment not available to create the session ID table. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 11 CLAS0003 CAUSE: No NS global table could be found. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 12 CLAS0002 CAUSE: Unable to get an entry in the session ID table. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes ICMP Type/Code Words ICMP Type/Code Words The following describes how to interpret the Parameter value (Parm Value) of a logging location that uses this value as the ICMP Type/Code Word. The Network Transport Entities PXP SIP and TCP SIP log the event that an ICMP message was received. The Parameter value, which is shown in hexadecimal, must be interpreted as a two byte value. The first byte indicates the ICMP message type and the second byte indicates the code.
Logging Location Codes ICMP Type/Code Words MESSAGE: Destination Unreachable. 302 CAUSE: The destination node was unable to deliver the IP datagram that originated from the node that logs this message. According to the destination node, the IP module cannot deliver the datagram because the indicated protocol (TCP or PXP) is not active. ACTION: This ICMP message should not occur in normal network operation between HP nodes. Contact your Hewlett-Packard representative for assistance.
Logging Location Codes ICMP Type/Code Words MESSAGE: Source Quench. 400 CAUSE: Several things can trigger source quench messages: (1) A gateway, intermediate router node or destination node was unable to forward or deliver the IP datagram because of lack of resources (e.g., buffers). (2) A gateway, intermediate router node or destination node was unable to forward or deliver the IP datagram because the capacity limit of resource (e.g., buffers) is being approached.
Logging Location Codes ICMP Type/Code Words through the network. Immediate action should be taken to correct the failure at the gateway or reconfigure the local node to route traffic for a given network through another gateway. MESSAGE: Time Exceeded. 600 CAUSE: A gateway or intermediate router node found that the Time-To-Live (TTL) field in the datagram is zero.
Logging Location Codes IP Logging Location Codes IP Logging Location Codes MESSAGE: None 101 CLAS0003 CAUSE: Received a port message containing an invalid function code (PARM = complete function code). ACTION: See Appendix A, “Submitting an SR,”of this manual. MESSAGE: None 102 CLAS0004 CAUSE: Log IP port initiation (PARM = PDA ptr). ACTION: Informative.
Logging Location Codes IP Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 111 CLAS0003 CAUSE: The packet length carried in the IP header is greater than the packet length supplied by the link device (PARM = upper 16 bits: header value; lower 16 bits: actual received). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes IP Logging Location Codes MESSAGE: None 121 CLAS0003 CAUSE: An inbound packet was discarded because it failed IP header validation tests (PARM not significant). ACTION: If this occurs frequently see Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 122 CLAS0003 CAUSE: An inbound packet was discarded because the IP header checksum failed (PARM = upper 16 bits = actual checksum; lower 16 bits = expected checksum).
Logging Location Codes IP Logging Location Codes MESSAGE: None 133 CLAS0002 CAUSE: A message fragment was discarded because of an internal failure of bmgr_append_buffer (PARM = bmgr_append_buffer result code). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 137 CLAS0003 CAUSE: A partially assembled message was discarded because the fragment assembly timer expired (PARM is not significant). ACTION: This will happen occasionally when a fragment is lost or discarded.
Logging Location Codes IP Logging Location Codes MESSAGE: None 147 CLAS0003 CAUSE: A store and forward packet was discarded because the next local destination address supplied from the routing tables was not in the strict source route list in the IP header (PARM unused). ACTION: Verify that the routing information about the destination node in the configuration file is correct. Verify that the links and NIs are started.
Logging Location Codes IP Logging Location Codes MESSAGE: None 162 CLAS0002 CAUSE: An outbound data packet that required fragmenting was discarded because an error occurred in a get buffer call (PARM = bmgr_get_buffer result code). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 165 CLAS0002 CAUSE: A store and forward packet was discarded because an error occurred creating a fragment with bmgr_copy_buffer (PARM = bmgr_copy_buffer result code).
Logging Location Codes IP Logging Location Codes MESSAGE: None 182 CLAS0002 CAUSE: The send by IP to NI for normal outbound data was unsuccessful (PARM = send_msg result). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 183 CLAS0002 CAUSE: Unable to read the IP header from the inbound buffer during normal inbound processing (PARM = bmgr_read_buffer result). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes IP Logging Location Codes MESSAGE: None 191 CLAS0002 CAUSE: An error was detected while attempting to start a timer for inbound reassembly (PARM = get_timer result). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 192 CLAS0002 CAUSE: An inbound buffer could not be freed while processing a partial datagram (reassembly) (PARM = bmgr_free_buffer result). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes IP Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 199 CLAS0002 CAUSE: IP was unable to add itself to the registry during initialization (PARM = reg_add_entity result). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 200 CLAS0004 CAUSE: IP was unable to terminate immediately because it has outstanding buffer or path resolution requests. When these complete IP will terminate. ACTION: Informative.
Logging Location Codes IPU Logging Location Codes IPU Logging Location Codes MESSAGE: None 1 CLAS0002 CAUSE: Received a port message containing an invalid format code or an invalid function code (PARM = complete function code). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 3 CLAS0004 CAUSE: Log port initiation. ACTION: Informative.
Logging Location Codes IPU Logging Location Codes ACTION: Shut down the transport (NETCONTROL STOP). Check the configuration file for a disparity between the number of networks configured and maximum networks specified. MESSAGE: None 15 CLAS0002 CAUSE: Network number in a Stop Net message not found in the DCN table (never started). ACTION: Error probably occurred when starting the network. See error at log location 12 above.
Logging Location Codes IPU Logging Location Codes MESSAGE: None 28 CLAS0002 CAUSE: Could not process a network start routing update because there was not enough room in the distance matrix table (PARM unused). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 29 CLAS0002 CAUSE: Could not process a network start routing update because the count of networks in the routing update exceeded configured maximum networks. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes L2Resolve Logging Location Codes L2Resolve Logging Location Codes L2Resolve is part of the process between NS Transport and SNA Transport which provides NS over SNA/XL functionality. MESSAGE: None 1 Log Class 2 CAUSE: Unable to send connect request. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 2 Log Class 2 CAUSE: Unable to send disconnect request. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes L2Resolve Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 15 Log Class 3 CAUSE: A connection request has been rejected. ACTION: Informative message. The network has been shut down, or a connection request has been refused by the other end. MESSAGE: None 17 Log Class 2 CAUSE: Invalid request from upper layers in current state. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes L2Resolve Logging Location Codes ACTION: Wait for L2Resolve to finish initialization and try the connection again. If the problem persists, see Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 25 Log Class 2 CAUSE: Incoming disconnect before L2Resolve is fully operational. ACTION: Wait for L2Resolve to finish initialization and try the connection again. If the problem persists, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes L2Resolve Logging Location Codes ACTION: Informative message. The network must be started for successful connection. MESSAGE: None 34 Log Class 2 CAUSE: Connection reply for an unknown connection. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 35 Log Class 2 CAUSE: Disconnect reply for an unknown connection and maximum number of connections exceeded. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes L2Resolve Logging Location Codes MESSAGE: None 44 Log Class 2 CAUSE: L2Resolve cannot be bound into MAP table. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 45 Log Class 4 CAUSE: L2Resolve is starting. ACTION: Informative message. MESSAGE: None 46 Log Class 2 CAUSE: Invalid message type for current L2Resolve state. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 47 Log Class 2 CAUSE: Error in starting or stopping L2Resolve.
Logging Location Codes Mapping Table Mapping Table MESSAGE: None 1 CLAS0004 CAUSE: Mapping table was created (PARM = Pointer to mapping table control block). ACTION: None. MESSAGE: 2 CLAS0004 CAUSE: Mapping table was deleted (PARM = Pointer to mapping table control block). ACTION: None. MESSAGE: None 3 CLAS0002 CAUSE: Error trying to obtain an entry from the pool of free mapping table entries (PARM = Status code from new_get_table_entry call).
Logging Location Codes Mapping Table ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 11 CLAS0002 CAUSE: Send message to Probe failed trying to update an aged station address mapping for an IP address. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 12 CLAS0002 CAUSE: Send message to ARP failed trying to get station address mapping for an IP address. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Net Timers Logging Location Codes Net Timers Logging Location Codes MESSAGE: Out of resources 1020 CLAS0003 CAUSE: A free-pool entry was needed for a timer-entry element, to hold information about a new net timer being obtained, but the pool was empty. A separate timer entry must exist for every net timer on the system. ACTION: No new timer was obtained. The system is probably operating under a heavy load.
Logging Location Codes Net Timers Logging Location Codes MESSAGE: Cannot reset a systimer 1080 CLAS0002 CAUSE: While attempting to stop, restart, or reschedule an existing system timer, the system routine Reset_timer_in_heartbeats failed or reported a status which was not expected given the current state of Net Timers. Resetting a system timer is a normal operation done whenever the first interval in a timer list changes (PARM = status from Reset_timer_in_heartbeats, PORT = address of timer list).
Logging Location Codes Net Timers Logging Location Codes associated with that net timer and others. A timer list’s system timer is normally reset whenever insertion of the new net timer changed the first interval in the list. (PORT = net timer ID). ACTION: Review information regarding the previous errors, for possible hints as to the cause. If necessary, submit an SR, noting this and previous Net Timers errors.
Logging Location Codes Net Timers Logging Location Codes ACTION: This probably means a Transport timer trap- routine has accidentally re-freed a timer it already freed. Another possibility is that a second processor has attempted to free the same timer while that trap routine was still executing; this might be unlikely due to timing constraints. If necessary, submit an SR.
Logging Location Codes Net Timers Logging Location Codes ACTION: No new timer was obtained. Review information regarding the previous errors, for possible hints as to the cause. If necessary, submit an SR, noting this and previous Net Timers errors. MESSAGE: Not up for processing 2160 CLAS0002 CAUSE: An attempt was made to reset a net timer before or during Net Timers startup, or during or after shutdown. Timers cannot be reset unless Net Timers is completely up. (PORT = net timer ID).
Logging Location Codes Net Timers Logging Location Codes MESSAGE: Cannot reset a timeout 2200 CLAS0002 CAUSE: This is supplemental logging to a previous Net Timers error. While attempting to reschedule a running net timer, there was a problem removing the timer from the old interval it was running in, or a problem restarting it. Both steps must succeed for the rescheduling to work. (PORT = net timer ID). ACTION: The timer has been left in an indeterminate state.
Logging Location Codes Net Timers Logging Location Codes MESSAGE: Accessed a freed timer 2260 CLAS0002 CAUSE: An attempt was made to restart a net timer which had already been freed, or a timer which was in some sort of bad state. Since freed net timers can be immediately reallocated to anyone, they cannot be safely restarted after freeing. (PORT = net timer ID). ACTION: If you suspect the timer has not been freed, another remote possibility is data corruption of the timer entry.
Logging Location Codes Net Timers Logging Location Codes ACTION: The operation of Net Timers should be unaffected. However, some other module on the system seems to be sending the wrong messages to the wrong places. Submit an SR, specifying the PARM value which was logged. MESSAGE: Failed reset-timer test 3140 CLAS0002 CAUSE: Reported by Hewlett-Packard internal tests only. This indicates resetting of a popping net timer yielded a status other than one indicating the timer was currently popping.
Logging Location Codes Net Timers Logging Location Codes ACTION: Net Timers will continue to run as normal, though no statistics data was obtained. Whichever utility was trying to read Net Timers information did not get it. Submit an SR. MESSAGE: Data truncated 3280 CLAS0003 CAUSE: A caller-specified statistics buffer was too small to hold the entire statistics block.
Logging Location Codes Net Timers Logging Location Codes MESSAGE: Cannot unfreeze memory 3360 CLAS0002 CAUSE: While attempting to unfreeze a caller- specified statistics buffer previously frozen into memory, the system routine Unfreeze reported an error. Unfreezing is necessary to avoid memory fragmentation over time (PARM = status from Unfreeze). ACTION: Net Timers will continue to run as normal, though no statistics data was obtained, and some memory space may be lost until the next system startup.
Logging Location Codes Net Timers Logging Location Codes ACTION: Net Timers will report the failure as a warning and continue with the shutdown. Unless there is corruption within system timers, this probably indicates a Net Timers bug. Another remote possibility is that the Net Timers port data has been corrupted from outside, so other, possibly serious problems may soon appear as well.
Logging Location Codes Net Timers Logging Location Codes MESSAGE: NMMGR fail, defaults used 4280 CLAS0004 CAUSE: While attempting to compute its configuration limits from the NETXPORT. GPROT. TCP node of the NMCONFIG. PUB. SYS file, the system routine Nmconfgetdata reported an error. Unable to read config data, a default configuration was selected as a backup just to get the network going (PARM = status from Nmconfgetdata).
Logging Location Codes Net Timers Logging Location Codes ACTION: Depending on the PARM value, your system load, and your current configuration, it is possible too much resident memory is already in use on your system to support the number of timers required by maximum the number of TCP connections currently configured in NMMGR, and thus the required PDA size. If this seems likely, you might try starting your network sooner after system startup, or possibly reducing the number of TCP connections configured.
Logging Location Codes Net Timers Logging Location Codes MESSAGE: Semaphore setup error 4420 CLAS0002 CAUSE: During startup initialization of the Net Timers context memory (port data area or PDA), the system routine Cb_init reported an error trying to clear the Net Timers semaphore. The semaphore is required because multiple callers can access the same timer list, and that list can pop at any time (PARM = status from Cb_init).
Logging Location Codes NETIPC Logging Location Codes NETIPC Logging Location Codes MESSAGE: None 0 CLAS0000 CAUSE: Invalid port message. ACTION: Examine “Info” section of log record. See Appendix A, “Submitting an SR,” of this manual. MESSAGE: Internal error. 1 CLAS0000 CAUSE: Unable to create port in data segment table. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: Internal error. 2 CLAS0000 CAUSE: Unable to locate known entry in the name registry.
Logging Location Codes NETIPC Logging Location Codes MESSAGE: Internal 14 CLAS0000 CAUSE: Unable to release timer. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: Internal error. 16 CLAS0000 CAUSE: Unable to create port message pool. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: Internal error. 17 CLAS0000 CAUSE: Call hpgetsysplabel failed. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: Internal error.
Logging Location Codes NETIPC Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: Internal error. 26 CLAS0000 CAUSE: Error in call to dict_find. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: Internal error. 27 CLAS0000 CAUSE: Unable to create socket record. ACTION: This is typically not an error condition. A total of at least 8000 socket records can be opened simultaneously on your system.
Logging Location Codes NETIPC Logging Location Codes MESSAGE: None 0 CLAS0001 CAUSE: Socket name registry full. ACTION: Call IPCNAMERASE to open slots in the socket name registry. MESSAGE: None 1 CLAS0001 CAUSE: Socket Give table full. ACTION: Call IPCGET to open slots in the socket give table. MESSAGE: Port DST table full. 2 CLAS0001 CAUSE: The Port DST table is a data structure internal to the NETIPC subsystem, not to be confused with MPE DST entries.
Logging Location Codes NFT Logging Location Codes NFT Logging Location Codes MESSAGE: None 1 CLAS0002 CAUSE: Attempt to open file NFCAT2 failed. Logging entry will also contain a file system error. ACTION: Act according to the file system error. For example, if the error is “non-existent permanent file”, then the system manager should place a copy of NFCAT2 in NET.SYS. MESSAGE: None 10 CLAS0002 CAUSE: Attempt to open file NFTCAT2 failed. Logging entry will also contain a file system error.
Logging Location Codes NI Logging Location Codes NI Logging Location Codes MESSAGE: None 1 CLAS0005 CAUSE: Device was idle for configured Idle Timeout and timer was enabled for this device. Device will be disconnected (PARM = device ldev). ACTION: None. MESSAGE: None 4 CLAS0002 CAUSE: Protocol ID in Protocol Stop message was not found in NI’s PID table (PARM = Protocol ID). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes NI Logging Location Codes MESSAGE: None 14 CLAS0002 CAUSE: On arrival of inbound data, a send_msg to the upper layer protocol failed (PARM = status from send_msg). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 15 CLAS0002 CAUSE: The NI received an inbound data message from a device that is not in the device table for this NI (PARM = LDEV). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes NI Logging Location Codes MESSAGE: None 25 CLAS0002 CAUSE: The protocol attempted to send data when no devices were active (PARM = Protocol ID). ACTION: Error should be preceded by other errors or a DELLINK message. If not, see Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 28 CLAS0004 CAUSE: Network Interface Started (PARM = NI port data address). ACTION: None. MESSAGE: None 29 CLAS0004 CAUSE: Network Interface Stopped (PARM = NI port data address). ACTION: None.
Logging Location Codes NI Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 52 CLAS0002 CAUSE: After receiving a connect confirmation event from a driver, send_msg failed trying to forward a similar message to the protocol (PARM = status from send_msg). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 53 CLAS0002 CAUSE: A driver acknowledged disconnection of a link which NI could not find in its tables (PARM = Protocol ID).
Logging Location Codes NI Logging Location Codes MESSAGE: None 63 CLAS0002 CAUSE: While trying to send outbound data to a driver, send_msg failed (PARM = status from send_msg). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 64 CLAS0002 CAUSE: NI received inbound data from a driver, for a link which NI could not find in its tables (PARM = link ID). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes NI Logging Location Codes MESSAGE: None 76 CLAS0002 CAUSE: NI request table is too small to hold information for the number of outstanding connect requests being attempted (PARM = request ID which was not connected). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 77 CLAS0002 CAUSE: NI request table is too small to hold information for the number of outstanding disconnect requests being attempted (PARM = request ID which was not disconnected).
Logging Location Codes NI Logging Location Codes MESSAGE: None 84 CLAS0002 CAUSE: While stopping a protocol or device, or after completing an outstanding request, NI attempted to free a request block, device- or protocol-table entry, but new_release_table_entry failed (PARM = status from new_release_table_entry). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 85 CLAS0002 CAUSE: During error recovery following a failure during transmission of outbound X.
Logging Location Codes NI Logging Location Codes MESSAGE: None 105 CLAS0002 CAUSE: After building a header for an outbound FDDI or Token Ring packet, NI encountered an error trying to write that header into the packet. ACTION: Something is wrong with the outbound buffer. See “Submitting an SR” in appendix A of this manual.
Logging Location Codes Path Result Code Table Path Result Code Table MESSAGE: None 0 CAUSE: Path resolved, path descriptor returned. ACTION: None. Informative message. MESSAGE: None 2 CAUSE: Path was verified path descriptor returned. ACTION: None. Informative message. MESSAGE: None 3 CAUSE: Path resolution has been deferred. ACTION: Wait for reply message on reply port. MESSAGE: None 5 CAUSE: Internal resource error. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Path Result Code Table MESSAGE: None 14 Cause: No suitable path reports. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 16 Cause: Bad mapping table sequence number. ACTION: See Map Result Code Table. MESSAGE: None 17 Cause: Mapping table entry has aged. ACTION: See Map Result Code Table. MESSAGE: None 18 Cause: Path is in disconnecting state. ACTION: See Map Result Code Table. MESSAGE: None 19 Cause: Mapping Table is in a bad state.
Logging Location Codes Probe Logging Location Codes Probe Logging Location Codes MESSAGE: None 7 CLAS0001 CAUSE: Bad or unexpected message received by PROBE Port (PARM = Message Function Code). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 14 CLAS0003 CAUSE: Retransmission timeout is faster than packet can be sent out to the node. This can happen if the node is congested. PARM indicates probe (%1) or proxy (%2) timer.
Logging Location Codes Probe Logging Location Codes MESSAGE: None 21 CLAS0002 CAUSE: Room allocated for node name and path report is too small (PARM = number of bytes short). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 22 CLAS0002 CAUSE: Timer popped which has no request outstanding (PARM = Time request ID). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Probe Logging Location Codes MESSAGE: None 33 CLAS0002 CAUSE: Attempt to map addresses failed (PARM = Path resolve error code). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 35 CLAS0004 CAUSE: PROBE Protocol Started. ACTION: Informative message. MESSAGE: None 36 CLAS0004 CAUSE: PROBE Protocol Stopped. ACTION: Informative message. MESSAGE: None 37 CLAS0004 CAUSE: PROBE Protocol Stopped (Delayed with Proxy). ACTION: None.
Logging Location Codes Probe Logging Location Codes MESSAGE: None 48 CLAS0002 CAUSE: Attempt to add PROBE to the mapping table during INIT message failed (PARM = mapping error code). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 49 CLAS0002 CAUSE: Could not delete the PROBE entity from the mapping table in a terminate sequence (PARM = mapping error code). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes PTOP Logging Location Codes PTOP Logging Location Codes MESSAGE: None 1 CLAS0003 CAUSE: Port Creation failed in response to a POPEN intrinsic. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: Internal error. 2 CLAS0003 CAUSE: Buffer Manager error. Port not allocated. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 3 CLAS0003 CAUSE: Socket connection failure. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes PXP PM Logging Location Codes PXP PM Logging Location Codes The PXP header is contained in the message frame logged on inbound packets. The header begins at word 18 of the message frame. MESSAGE: None 0 CLAS0001 CAUSE: Received an invalid NS format message (PARM = message function). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 1 CLAS0001 CAUSE: Received a port message before receiving the CP initialization message (PARM = message function).
Logging Location Codes PXP PM Logging Location Codes MESSAGE: None 9 CLAS0001 CAUSE: A PXP internal resource error has been encountered. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 10 CLAS0001 CAUSE: A PXP internal error has been encountered. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 11 CLAS0001 CAUSE: A PXP internal resource error has been encountered. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes PXP PM Logging Location Codes MESSAGE: None 18 CLAS0003 CAUSE: A PXP request packet has been retransmitted (PARM = number of retransmissions performed). ACTION: Repeated retransmissions suggest possible link or configuration problems. See PXP error code explanations. MESSAGE: None 19 CLAS0003 CAUSE: PXP request failed. Retransmission-retry maximum exceeded. Possible link or configuration problems.
Logging Location Codes PXP PM Logging Location Codes MESSAGE: None 46 CLAS0001 CAUSE: A PXP internal resource error has been encountered. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 48 CLAS0001 CAUSE: A PXP internal resource error has been encountered. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 50 CLAS0003 CAUSE: An inbound packet was discarded as part of the shutdown sequence. ACTION: Informative message.
Logging Location Codes PXP PM Logging Location Codes MESSAGE: None 69 CLAS0001 CAUSE: An error was returned on an NS'DICT'Delete call (PARM = error result returned). ACTION: See Appendix A, “Submitting an SR,”of this manual. MESSAGE: None 70 CLAS0003 CAUSE: Adding a PXP PM to the registry failed (PARM = error result returned by Reg'CM'Entity). ACTION: This is only a warning, but submit an SR anyway. See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes PXP SIP Logging Location Codes PXP SIP Logging Location Codes MESSAGE: None 0 CLAS0001 CAUSE: Received a port message before receiving the initialization message (PARM = message function). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 1 CLAS0001 CAUSE: Received an invalid CP message (PARM = message function). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes PXP SIP Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 9 CLAS0002 CAUSE: A socket could not be opened due to a port dst problem (PARM = error code). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 10 CLAS0002 CAUSE: A socket could not be opened due to a CREATEPORT' failure (PARM = PORT error code). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes PXP SIP Logging Location Codes MESSAGE: None 20 CLAS0006 CAUSE: Statistical summary for the deactivated PXP SIP. ACTION: None. Statistical information. MESSAGE: None 21 CLAS0004 CAUSE: The PXP SIP has been deactivated. ACTION: None. Nodal information. MESSAGE: None 22 CLAS0003 CAUSE: An inbound packet has been discarded because the destination PXP socket is not open. ACTION: None.
Logging Location Codes PXP SIP Logging Location Codes MESSAGE: None 34 CLAS0003 CAUSE: A PXP socket could not be opened because the maximum number configured has been reached. ACTION: Increase the number of PXP sockets configured. Use the PXP Data screen. MESSAGE: None 35 CLAS0002 CLAS0003 CAUSE: The PXP SIP received an ICMP message from the IP module (PARM = ICMP type word). ACTION: None.
Logging Location Codes RASERVER Logging Location Codes RASERVER Logging Location Codes There is an RASERVER created for each use of the RFA services. This process receives and processes protocol messages for the service and accesses files and terminals for the service. MESSAGE: None 1 CLAS003 CAUSE: RASERVER stack log buffer could not be allocated. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 2 CLAS003 CAUSE: RASERVER header for data structures could not be allocated.
Logging Location Codes RASERVER Logging Location Codes MESSAGE: None 10 CLAS003 CAUSE: Could not find a wait entry for nowait I/O which completed. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 11 CLAS003 CAUSE: No I/O pending when a nowait I/O completed. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 12 CLAS003 CAUSE: RFA services reported an error. ACTION: Repair the RFA error, if possible.
Logging Location Codes RASERVER Logging Location Codes MESSAGE: None 20 CLAS005 CAUSE: Could not make connection nowait. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 21 CLAS005 CAUSE: Could not disable connection timeouts. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 22 CLAS002 CAUSE: RASERVER connection buffer could not be deallocated. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes RASERVER Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 33 CLAS002 CAUSE: RASERVER failed to increase the size of its connection buffer. User requested more than 30000 bytes of data. ACTION: Decrease the request size below 30000 bytes. MESSAGE: None 34 CLAS002 CAUSE: RASERVER failed to find a file control block. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes RASERVER Logging Location Codes ACTION: Check correctness of node name. If problem still occurs, see Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 42 CLAS002 CAUSE: RASERVER could not allocate a compression buffer. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 43 CLAS002 CAUSE: RASERVER could not deallocate a compression buffer ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Remote Link Manager Logging Location Codes Remote Link Manager Logging Location Codes MESSAGE: None 1 CLAS0001 CAUSE: RLM’s data structures are corrupted. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 3 CLAS0002 CAUSE: Send_msg procedure returned a bad status to the RLM. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 4 CLAS0002 CAUSE: Link Error occurred in unexpected state.
Logging Location Codes Remote Link Manager Logging Location Codes MESSAGE: None 10 CLAS0003 CAUSE: RLM could not release some internal resources (PARM = Status returned by 'new_release_table_entry’). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 11 CLAS0001 CAUSE: RLM attempted to release a resource that had already been released. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Remote Link Manager Logging Location Codes MESSAGE: None 19 CLAS0002 CAUSE: RLM could not write outbound packet to buffer. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 20 CLAS0002 CAUSE: RLM could not read buffer containing inbound packet. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 21 CLAS0001 CAUSE: Mismatch in states between the DTC and the HP 3000. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Remote Link Manager Logging Location Codes ACTION: Check status of X.25 protocol on DTC. Possible causes include bad/disconnected cable between DTC and switch/X.25 network, or the switch/X.25 network is down. When problem is corrected, HP 3000 will display additional logging messages. MESSAGE: None 28 CLAS0002 CAUSE: Disconnect reply received from linkn contained bad status. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Remote Link Manager Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 38 CLAS0002 CAUSE: RLM could not free a buffer. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 39 CLAS0002 CAUSE: State mismatch between DTC and Host. ACTION: See Appendix A, “Submitting an SR,” of this manual. (Make sure a dump is taken of both the DTC and the HP 3000.
Logging Location Codes Remote Link Manager Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 48 CLAS0001 CAUSE: Interface problem between DTC and HP 3000. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 49 CLAS0002 CAUSE: Link sent a disconnect event for an unknown connection. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 50 CLAS0001 CAUSE: AFCP connection is in an invalid state for the event.
Logging Location Codes Remote Link Manager Logging Location Codes MESSAGE: None 59 CLAS0002 CAUSE: Could not release timer. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 60 CLAS0002 CAUSE: Invalid message received for current state. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 61 CLAS0003 CAUSE: Link has gone down. ACTION: Run appropriate diagnostics. If no error is found, see Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Remote Link Manager Logging Location Codes MESSAGE: None 69 CLAS0005 CAUSE: Contact with DTC was lost while attempting to shut down the DTC link. ACTION: Check status of DTC. MESSAGE: None 70 CLAS0005 CAUSE: Link went down abnormally during shutdown. ACTION: Check status of X.25 card on DTC. MESSAGE: None 71 CLAS0002 CAUSE: RLM could not release a semaphore. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Remote Link Manager Logging Location Codes MESSAGE: None 83 CLAS0002 CAUSE: RLM could not release semaphore pool. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 84 CLAS0002 CAUSE: RLM could not free buffer. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 85 CLAS0002 CAUSE: RLM could not delete semaphore pool. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Remote Link Manager Logging Location Codes ACTION: Check status of X.25 protocol on DTC. Possible causes include bad/disconnected cable between DTC and switch/X.25 network, or the switch/X.25 network is down. When problem is corrected, HP 3000 will display additional logging messages and the network will be usable. MESSAGE: None 100 CLAS0002 CAUSE: Could not create the RLM’s Port Data Area (PARM = 'create_object' status). Available virtual space may have been exhausted.
Logging Location Codes Remote Link Manager Logging Location Codes MESSAGE: None 107 CLAS0001 CAUSE: Error encountered while receiving information from RLM Server (PARM = status returned by 'extend_receive'). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 108 CLAS0001 CAUSE: Message received on process port if not the expected type. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 109 CLAS0002 CAUSE: Link buffer size is too small. ACTION: Check X.
Logging Location Codes Remote Link Manager Logging Location Codes MESSAGE: None 115 CLAS0003 CAUSE: RLM could not deconfigure AFCP protocol module (PARM = status returned by 'mcm_module_config'). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 116 CLAS0003 CAUSE: RLM could not release plabel for 'remote_link_manager' (PARM = status returned by 'hprelsysplabel'). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes Remote Link Manager Logging Location Codes MESSAGE: None 123 CLAS0003 CAUSE: RLM could purge its port (PARM = status returned by 'purge_port'). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 124 CLAS0003 CAUSE: RLM could not release its port data area object (PARM = status returned by 'release_object'). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 125 CLAS0004 CAUSE: RLM has been created (PARM = RLM’s port id).
Logging Location Codes RFA Logging Location Codes RFA Logging Location Codes MESSAGE: None 1 CLAS0003 CAUSE: RFA was unable to obtain a free DST for its buffers. ACTION: If system is overloaded, wait till resources free up; otherwise, see Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 2 CLAS0003 CAUSE: RFA was unable to deallocate one of its internal buffers.
Logging Location Codes RFA Logging Location Codes ACTION: Verify if the network transport has not been shutdown by the system operator on the local or remote system. If not see Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 10 CLAS0003 CAUSE: RFA encountered a NetIPC error while sending an RFA request to the remote system. ACTION: If the user attempted to FREAD or FWRITE more than 29980 bytes of data in one FREAD or FWRITE call, then the user has reached the resource limits of RFA.
Logging Location Codes RFA Logging Location Codes ACTION: Verify that the network transport has been started on the remote system. Verify that the remote system supports NS 3000/iX RFA. Also verify that the remote system has started the RFA service. If RFA is started then see Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 16 CLAS0003 CAUSE: RFA could not turn on NetIPC socket data tracing.
Logging Location Codes RFA Logging Location Codes 22 CLAS0003 CAUSE: Insufficient memory in the port DST to create a new port for NOWAIT IO. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 23 CLAS0003 CAUSE: Unexpected error while creating an IOWAIT port for NOWAIT IO. NOWAIT IO is not currently supported on XL. See Appendix A, “Submitting an SR,” of this manual. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes RFA Logging Location Codes 30 CLAS0003 CAUSE: While the RFA server was adopting in the remote session, it could not update information in the AS process table. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 31 CLAS0003 CAUSE: RFA was unable to allocate a buffer large enough to handle the user’s FREAD or FWRITE request.
Logging Location Codes RFA Logging Location Codes ACTION: The NS product has been installed improperly. See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 39 CLAS0003 CAUSE: One of many possible errors encountered in Native Mode RFA. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes RPM Logging Location Codes RPM Logging Location Codes MESSAGE: None 1 CLAS0002 CAUSE: Data segment for RPM table could not be allocated. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 2 CLAS0002 CAUSE: Insufficient stack space to set critical. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 3 CLAS0003 CAUSE: NS global data segment does not exist. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes RPM Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 11 CLAS0002 CAUSE: An invalid RPM message has been received. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 12 CLAS0005 CAUSE: Receive of an RPM Length Reply message failed. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 13 CLAS0005 CAUSE: Send of an RPM Create Request message failed.
Logging Location Codes RPM Logging Location Codes MESSAGE: None 21 CLAS0005 CAUSE: Receive of an RPM Kill Request message failed. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 22 CLAS0005 CAUSE: Send of an RPM Kill Reply message failed. Invalid port message. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 23 CLAS0005 CAUSE: Send of an RPM Length Reply message failed. ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes RPM Logging Location Codes MESSAGE: None 35 CLAS0003 CAUSE: RPMDAD adoption under DSDAD failed during a session shutdown. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 36 CLAS0003 CAUSE: RPMDAD was unable to adopt into the user's session. ACTION: If the RPM session was not aborted by the system operator, then see Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 37 CLAS0003 CAUSE: JSMAIN locking mechanism failed during an adopt.
Logging Location Codes TCP Logging Locations TCP Logging Locations The following is an explanation of the general format of TCP logging locations. An explanation of the individual TCP logging messages follows.
Logging Location Codes TCP Logging Locations 10- Attempted to delete from empty rtxq 11- Internal IPC State incorrect 12- Bad timer state 13- Data requested greater than buffer contents 14- Bad status from tcp_read_completor 15- Unmatched buffer pool in buffer reply 16- Unexpected Buffer reply 17- Bad buffer reply state 18- Resegmentation failure 20–29 Remote protocol errors—These errors indicate that the remote TCP to which this implementation is conversing has apparently generated a pa
Logging Location Codes TCP Logging Locations 34- Bad (Unknown) IPCcontrol 40–49 standard connection lost/shutdown errors 40- RTX Timeout (# of retries) 41- RTX Threshold exceeded 42- Remote abort 43- Connection Assurance Timeout 50–59 More External Errors—An error result was returned from a procedure call to a module outside of TCP. 50- Buffer Manager 59- Unexpected escape 60–79 standard informative errors (etc.
Logging Location Codes TCP Logging Locations 75- Bad Message Type/Function Code 76- Max connections exceeded 77- Wrong Father Pin (Not NMMON) 78- Max sockets exceeded 80–89 standard informative messages—Nodal and connection events 80- PM activated 81- PM Graceful released 82- PM Deactivated 83- Socket Created 84- Socket Deactivated 85- Protocol started 86- Protocol stopped 87- Network stopped 88- Driver Down Notification Complete 89- Path Verify Complete 98–99 Statistical Log
Logging Location Codes TCP Logging Locations MESSAGE: None 10003 CLAS0002 CAUSE: NWTM_SEND_MSG returned a bad status while trying to send an irrecoverable error message to IPC. ACTION: PARM is NWTM error returned. Submit an SR. MESSAGE: None 10004 CLAS0002 CAUSE: NWTM_SET_FILE_EVENT returned a bad status while trying to set the exception bit due to received urgent data. ACTION: PARM is NWTM error returned. Submit an SR.
Logging Location Codes TCP Logging Locations MESSAGE: None 10011 CLAS0002 CAUSE: NWTM_SEND_MSG returned a bad status while trying to send a send completion notification to IPC. ACTION: PARM is NWTM error returned. Submit an SR. MESSAGE: None 10012 CLAS0002 CAUSE: NWTM_SEND_MSG returned a bad status while trying to send an irrecoverable error message to a call socket. ACTION: PARM is NWTM error returned. Submit an SR.
Logging Location Codes TCP Logging Locations MESSAGE: None 10103 CLAS0002 CAUSE: Bad status returned from send_msg while forwarding an inbound packet for an unknown connection to the SIP. ACTION: PARM is ports error returned. Submit an SR. MESSAGE: None 10104 CLAS0002 CAUSE: Bad status returned from send_msg while trying to send a cleanup request to the SIP. ACTION: PARM is ports error returned. Submit an SR.
Logging Location Codes TCP Logging Locations MESSAGE: None 10113 CLAS0002 CAUSE: Bad status returned from create_port while trying to create a port for the TCP SIP. This was during protocol start. ACTION: PARM is ports error returned. Submit an SR. MESSAGE: None 10114 CLAS0002 CAUSE: Bad status returned from change_subqueue while trying to enable a subset of subqueues for TCP SIP’s port. ACTION: PARM is ports error returned. Submit an SR.
Logging Location Codes TCP Logging Locations MESSAGE: None 10120 CLAS0002 CAUSE: Bad status returned from send_msg while trying to send an outbound data message to the IP port. ACTION: PARM is ports error returned. Submit an SR. MESSAGE: None 10121 CLAS0002 CAUSE: Bad status returned from send_msg while trying to send a terminate reply message to NETCP. NETCP may be in a hung state. ACTION: PARM is ports error returned. Submit an SR.
Logging Location Codes TCP Logging Locations MESSAGE: None 10204 CLAS0002 CAUSE: New_get_table_entry returned a bad status while we were trying to allocate a socket entry. ACTION: PARM is table management error returned. Submit an SR. MESSAGE: None 10205 CLAS0002 CAUSE: New_get_table_entry returned a bad status while we were trying to allocate a vector queue entry. ACTION: PARM is table management error returned. Submit an SR.
Logging Location Codes TCP Logging Locations MESSAGE: None 10212 CLAS0002 CAUSE: There was a bad status returned from delete_table while releasing the TCP vector table. This would happen after network or system shutdown. ACTION: PARM is table management error returned. Submit an SR. MESSAGE: None 10213 CLAS0002 CAUSE: New_get_table_entry returned a bad status while we were trying to allocate a connection entry. This occurred while trying to process an inbound syn. The connection attempt will fail.
Logging Location Codes TCP Logging Locations MESSAGE: None 10403 CLAS0005 CAUSE: The Path reply came back with a bad status. We can’t get a route to establish connection. ACTION: PARM is path reply error returned. Possible nodal/media failure or misconfiguration. Diagnose path resolution failure. Submit an SR if necessary. MESSAGE: None 10404 CLAS0005 CAUSE: We have received numerous consecutive path replies, but we still haven’t received a good route to establish the connection.
Logging Location Codes TCP Logging Locations MESSAGE: None 10503 CLAS0002 CAUSE: Nettmr_get_timer call returned an error. ACTION: PARM is nettmr error returned. Submit an SR. MESSAGE: None 10504 CLAS0002 CAUSE: Nettmr_reset_timer call returned an error. ACTION: PARM is nettmr error returned. Submit an SR. MESSAGE: None 10601 CLAS0002 CAUSE: CB_INIT returned a bad status while initializing the hash table semaphore. CB_INIT was called during network startup. ACTION: PARM is semaphores error returned.
Logging Location Codes TCP Logging Locations ACTION: PARM is the NMS error returned. Submit an SR. MESSAGE: None 10803 CLAS0002 CAUSE: NMMONSTARTREQ call returned a bad status during network startup. ACTION: PARM is the NMS error returned. Submit an SR. MESSAGE: None 10804 CLAS0002 CAUSE: Bad status was returned in a message from the TCP SIP during network startup. The TCP SIP initialization has failed. ACTION: PARM is TCP SIP initialization error.
Logging Location Codes TCP Logging Locations MESSAGE: None 10811 CLAS0002 CAUSE: NMWRITETRACE call returned a bad status while tracing a resource interface. ACTION: PARM is the NMS error returned. Submit an SR. MESSAGE: None 10812 CLAS0002 CAUSE: NMWRITETRACE call returned a bad status while tracing a resource interface. ACTION: PARM is the NMS error returned. Submit an SR. MESSAGE: None 10813 CLAS0002 CAUSE: REG_DEL_ENTITY returned a bad status. It was called during network shutdown.
Logging Location Codes TCP Logging Locations ACTION: PARM is the returned error. Submit an SR. MESSAGE: None 10901 CLAS0003 CAUSE: A call to an SDI driver failed. ACTION: PARM is the call result status. Submit an SR. MESSAGE: None 10902 CLAS0002 CAUSE: TCP accepted a new ack, but no outstanding data was found on the retransmission queue. The connection is in an inconsistent state. ACTION: Submit an SR. MESSAGE: None 11001 CLAS0003 CAUSE: HPGETSYSPLABEL call failed to get plabel of TCP’s timer trap routine.
Logging Location Codes TCP Logging Locations MESSAGE: None 11401 CLAS0003 CAUSE: Bad status returned from a call to the tcp_read_completor in the loopback send path. ACTION: Submit an SR. MESSAGE: None 11402 CLAS0003 CAUSE: Bad status returned from a call to the tcp_read_completor in the loopback retransmissive send path. ACTION: Submit an SR. MESSAGE: None 11501 CLAS0005 CAUSE: We received a reply from buffer manager containing a buffer that is not part of our buffer pool. ACTION: Informative message.
Logging Location Codes TCP Logging Locations MESSAGE: None 11903 CLAS0002 CAUSE: Connection was removed from TCP’s temporary IP list table. See location 11901. ACTION: PARM is source IP address of connection. Check configuration for number of configured networks. If ok, then submit an SR. MESSAGE: None 12001 CLAS0003 CAUSE: A connection received a packet with a bad checksum. ACTION: Informative message. No action required. Bad checksums usually indicate poor transmission quality.
Logging Location Codes TCP Logging Locations MESSAGE: None 12103 CLAS0003 CAUSE: A TCP connection received a packet with precedence or security options which do not match those of the connection. The connection will abort. ACTION: Remote protocol error indication. Use tracing or line analysis to capture connection dialog. If precedence or security option of inbound packet changes report an error against the remote implementation. Otherwise, submit an SR.
Logging Location Codes TCP Logging Locations MESSAGE: None 12303 CLAS0003 CAUSE: A packet was received without the ACK flag set by a connection in a state in which such a packet is not acceptable. The packet will be ignored. This is a remote protocol violation. ACTION: Remote protocol error indication. Use tracing or line analysis to capture connection dialog. Report an error against remote implementation. MESSAGE: None 12401 CLAS0003 CAUSE: A packet was received with an invalid ACK status.
Logging Location Codes TCP Logging Locations MESSAGE: None 12502 CLAS0003 CAUSE: The remote connection half has sent data with a sequence number which exceeds the fin sequence number which the remote sent previously. This is a remote protocol violation. ACTION: Capture data traffic including offending fin and following data packet using tracing or a line analyzer. Report an error against the remote implementation.
Logging Location Codes TCP Logging Locations ACTION: Capture data traffic including offending fin and following data packet using tracing or a line analyzer. Report an error against the remote implementation. MESSAGE: None 12601 CLAS0003 CAUSE: A packet was received which contained a TCP header with a max tpdu option which had an incorrect option length in the option length field. ACTION: Capture data traffic including offending data packet using tracing or a line analyzer.
Logging Location Codes TCP Logging Locations MESSAGE: None 13202 CLAS0003 CAUSE: An attempt was made to open a TCP socket; however, the protocol was not active (i.e., was stopped). ACTION: Informative message. Start the network if needed. MESSAGE: None 13203 CLAS0003 CAUSE: We received an inbound syn packet we will not process because the transport is not up. ACTION: Informative message. Start the transport if needed.
Logging Location Codes TCP Logging Locations ACTION: Excessive retransmissions indicate a possible route/gate failure or possible end node failure or possible misconfiguration. Extreme network bottlenecks may also cause this type of problem although TCP should be able to adjust to most network conditions. A temporary work around may be to increase the configured number of maximum retransmissions. If a direct cause is not found consider further diagnosis with a line analyzer or submitting an SR.
Logging Location Codes TCP Logging Locations use this type of shutdown. Remote abortions also occur when errors are encountered on the remote system. In unexpected abortion situations inspection of the remote system for indications of error is suggested. MESSAGE: None 14301 CLAS0003 CAUSE: Connection Assurance timeout occurred for this connection. The remote node did not respond within the configured number of CA retries. ACTION: Suspect remote node failure, or possible network failure.
Logging Location Codes TCP Logging Locations ACTION: PARM is escape code of escape. Submit an SR. MESSAGE: None 15906 CLAS0002 CAUSE: An unexpected escape occurred within the procedure tcp_connection_shutdown or some procedural unit called by it. ACTION: PARM is escape code of escape. Submit an SR. MESSAGE: None 15906 CLAS0002 CAUSE: An unexpected escape occurred within the procedure tcp_connection_shutdown or some procedural unit called by it. ACTION: PARM is escape code of escape. Submit an SR.
Logging Location Codes TCP Logging Locations MESSAGE: None 15913 CLAS0002 CAUSE: An unexpected escape occurred within the procedure tcp_is_inbound_urgent or some procedural unit called by it. ACTION: PARM is escape code of escape. Submit an SR. MESSAGE: None 15914 CLAS0002 CAUSE: An unexpected escape occurred within the procedure tcp_module_config or some procedural unit called by it. ACTION: PARM is escape code of escape. Submit an SR.
Logging Location Codes TCP Logging Locations ACTION: PARM is escape code of escape. Submit an SR. MESSAGE: None 15922 CLAS0002 CAUSE: An unexpected escape occurred within the procedure tcp_sip_traceon or some procedural unit called by it. ACTION: PARM is escape code of escape. Submit an SR. MESSAGE: None 15923 CLAS0002 CAUSE: An unexpected escape occurred within the procedure tcp_sip_traceoff or some procedural unit called by it. ACTION: PARM is escape code of escape. Submit an SR.
Logging Location Codes TCP Logging Locations MESSAGE: None 15931 CLAS0002 CAUSE: An unexpected escape occurred within the procedure tcp_driver_down or some procedural unit called by it. ACTION: PARM is escape code of escape. Submit an SR. MESSAGE: None 15932 CLAS0002 CAUSE: An unexpected escape occurred within the procedure tcp_flush_sends or some procedural unit called by it. ACTION: PARM is escape code of escape. Submit an SR.
Logging Location Codes TCP Logging Locations MESSAGE: None 16103 CLAS0005 CAUSE: A connection tossed a packet because of an invalid sequence number. May be caused by inbound retransmissions, connection assurance packets, or window probes. ACTION: Informative message. No action required. Occasional occurrences normal. Excessive occurrences indicate abnormal software operation. MESSAGE: None 16104 CLAS0005 CAUSE: A connection tossed a packet because of an invalid sequence number.
Logging Location Codes TCP Logging Locations MESSAGE: None 16110 CLAS0005 CAUSE: The TCP SIP tossed a packet from a half open connection because it couldn’t get a route to send an outbound reset. ACTION: Informative message. No action required. Possibly diagnose route resolution failure. Likely link/gate/nodal failure or configuration error.
Logging Location Codes TCP Logging Locations ACTION: This indicates network congestion, or a noisy or loss prone network. Occasional occurrences are considered normal. Excessive occurrences resulting in connection disconnects may indicate nodal/media failure, misconfiguration, severe network bottlenecks, or software failure. MESSAGE: None 16401 CLAS0005 CAUSE: An excessive number of retransmissions has caused a negative advice indication has been sent to the TCP SIP.
Logging Location Codes TCP Logging Locations MESSAGE: None 17101 CLAS0005 CAUSE: The user or service (through IPC) has rejected the passive connection attempt, or an error has occurred on the connection since the passive open request was received. ACTION: Informative message. PARM is rejection reason. If PARM is 0, user/service rejected the connection. Otherwise, an error condition has been detected by TCP. Look for logging indication of other error on same connection.
Logging Location Codes TCP Logging Locations MESSAGE: None 17405 CLAS0002 CAUSE: TCP KSO pointer value was NIL. ACTION: Suspect error in protocol startup. Look for logging indication explaining TCP protocol startup failure. Submit an SR. MESSAGE: None 17501 CLAS0002 CAUSE: Bad port message of 'DS' type came to the TCP SIP. ACTION: Submit an SR. MESSAGE: None 17502 CLAS0002 CAUSE: Bad port message of unknown type came to the TCP SIP. ACTION: Submit an SR.
Logging Location Codes TCP Logging Locations MESSAGE: None 18301 CLAS0005 CAUSE: TCP socket opened. ACTION: Informational message. No action required. MESSAGE: None 18401 CLAS0005 CAUSE: TCP socket closed. ACTION: Informational message. No action required. MESSAGE: None 18501 CLAS0004 CAUSE: TCP protocol started. ACTION: Informational message. No action required. MESSAGE: None 18502 CLAS0005 CAUSE: The TCP SIP has been started. ACTION: Informational message. No action required.
Logging Location Codes TCP Logging Locations MESSAGE: None 18901 CLAS0005 CAUSE: Path_verify message from NETCP processed for parm> ip_addr. ACTION: Informational message. No action required. MESSAGE: None 19801 CLAS0006 CAUSE: The global TCP statistics are being recorded. ACTION: Statistical message. No action required. MESSAGE: None 19802 CLAS0006 CAUSE: Specific statistics related to the efficiency of the hash table are being recorded. ACTION: Statistical message. No action required.
Logging Location Codes UDP Logging Locations UDP Logging Locations MESSAGE: None 1 CLAS0002 CAUSE: Unable to free the buffer passed to NetIPC associated with the inbound datagram received (PARM = Result returned from bmgr_free_buffer). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 2 CLAS0002 CAUSE: The send of the datagram open reply message to NetIPC failed (PARM = Result code returned from send_msg). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes UDP Logging Locations MESSAGE: None 9 CLAS0002 CAUSE: Attempting to open a socket with a SAP (address) that is already in use (PARM = Address, which is already open, for this open request). ACTION: Check to ensure that unique or well-known SAPs are being used. If OK, then see Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 10 CLAS0002 CAUSE: Attempt to free an object to virtual space management failed (PARM = Result code from release_object call).
Logging Location Codes UDP Logging Locations MESSAGE: None 18 CLAS0002 CAUSE: Attempt to write the UDP header into a buffer on an outbound datagram failed (PARM = Status returned by bmgr_write_buffer). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 19 CLAS0004 CAUSE: Logging the start of the UDP module (PARM = UDP’s port ID). ACTION: Informative message.
Logging Location Codes UDP Logging Locations ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 27 CLAS0002 CAUSE: Received unknown message type (PARM = Message function code). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 28 CLAS0002 CAUSE: Conversion of IPU dst to a native mode pointer failed (PARM = Result code returned by convert_dst). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes UDP Logging Locations ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 36 CLAS0002 CAUSE: Attempt to write user’s data to outbound buffer failed (PARM = Result code returned by bmgr_write_buffer). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 37 CLAS0002 CAUSE: Attempt to write the IP options into the outbound buffer failed (PARM = Result code returned by bmgr_write_buffer).
Logging Location Codes UDP Logging Locations MESSAGE: None 45 CLAS0003 CAUSE: Failed in attempting to re-obtain a path descriptor on verification for a socket (PARM = Status returned by ns_path_resolve). ACTION: Check the IP address and the network being used. If OK then see Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 46 CLAS0003 CAUSE: Attempt to get a path descriptor for the destination in the datagram send request failed (PARM = Result code returned by ns_path_resolve).
Logging Location Codes UDP Logging Locations MESSAGE: None 51 CLAS0002 CAUSE: Failure in attempt to free the inbound buffer on a datagram for which no SAP is open and no ICMP is sent since it is a broadcast IP address (PARM = Status returned by bmgr_free_buffer). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes X.25 Logging Location Codes X.25 Logging Location Codes X.25 logging falls under the transport subsystem (SUB0006). It logs 4 different classes of errors. They are: Class 2 — Internal Errors. This usually means a bug somewhere. Class 3 — Resource Errors. These should be recoverable, but a configuration adjustment may be a good idea. Class 4 — Nodal information. This is just information about Phobos being started and stopped. Links going up and down etc. Class 5 — Informative.
Logging Location Codes X.25 Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 104 CLAS0005 CAUSE: X.25 received an outbound data packet from IP, but the connection is not in the correct state to send the message. This can occur when a connection is closing. If this happens consistently, it means that the X.25 and TCP tables are inconsistent (PARM = connection points). ACTION: Issue a NETCONTROL STOP followed by a NETCONTROL START to clear this condition.
Logging Location Codes X.25 Logging Location Codes MESSAGE: None 111 CLAS0002 CAUSE: X.25 received a message for an unknown connection (PARM = connection points). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 112 CLAS0002 CAUSE: Internal Error. Map_Add_Rout failed (PARM = status from Map_add_rout). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes X.25 Logging Location Codes MESSAGE: None 119 CLAS0002 CAUSE: Internal Error. Map_X25_Update failed (PARM = status from Map_X25_update). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 125 CLAS0002 CAUSE: Internal Error. Convert_dst failed (PARM = status from Convert_dst). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 126 CLAS0002 CAUSE: Internal Error. IPC sent zero bytes of data to X.25 for transmission.
Logging Location Codes X.25 Logging Location Codes MESSAGE: None 133 CLAS0002 CAUSE: The configuration file contains more than the allowed number of SVC paths (PARM = number of SVC paths). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 134 CLAS0002 CAUSE: An error occurred while reading an SVC path from the configuration file (PARM = length). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 135 CLAS0002 CAUSE: Internal Error.
Logging Location Codes X.25 Logging Location Codes MESSAGE: None 141 CLAS0004 CAUSE: Maximum number of link entries already in use. Cannot add another link entry. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 142 CLAS0002 CAUSE: Internal Error. Map_Del_Entity failed (PARM = Map_Del_Entity). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 143 CLAS0002 CAUSE: Internal Error. Bmgr_Delete_Pool failed (PARM = Bmgr_delete_pool).
Logging Location Codes X.25 Logging Location Codes ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 150 CLAS0002 CAUSE: X.25 received an unknown message format (PARM = message format). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 151 CLAS0002 CAUSE: X.25 received an initialization message from the Control Process when its port data area was non zero (PARM = control server state). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes X.25 Logging Location Codes MESSAGE: None 159 CLAS0005 CAUSE: An inbound IPC connection was opened (PARM = Device ID, VC number). ACTION: None. This is an informative message. MESSAGE: None 160 CLAS0005 CAUSE: A connection was closed (PARM = Device ID, VC number). ACTION: None. This is an informative message. MESSAGE: None 161 CLAS0003 CAUSE: A connection cannot be opened as X.25 has reached its limit for the number of connections (PARM = number of connections in use).
Logging Location Codes X.25 Logging Location Codes MESSAGE: None 166 CLAS0005 CAUSE: An incoming connection request was rejected because it requested throughput class negotiation, and this facility set does not negotiate throughout class (PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an informative message. If you want to negotiate throughput class, modify the facility set.
Logging Location Codes X.25 Logging Location Codes ACTION: None. This is an informative message. If you want to accept this call, modify the remote machine so that fast select restriction is not set. MESSAGE: None 172 CLAS0005 CAUSE: An incoming connection request was rejected because the IPC socket with the protocol relative address specified in the call has not been created (PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an informative message.
Logging Location Codes X.25 Logging Location Codes MESSAGE: None 178 CLAS0005 CAUSE: An outgoing TCP/IP connection request was rejected. The rejection may have come from the local DTC, the network, or the remote node (PARM = Device ID, VC number, cause, diagnostic). ACTION: Check the diagnostic code returned. Verify that all components are operational. MESSAGE: None 179 CLAS0005 CAUSE: An outgoing connection request was rejected because the AFCP connection was closed.
Logging Location Codes X.25 Logging Location Codes ACTION: Try again later, or increase the number of buffers configured. MESSAGE: None 186 CLAS0005 CAUSE: An outgoing IPC connection request was rejected because the specified facility set does not exist. ACTION: Define a new facility set for this configuration, or assign an existing facility set. MESSAGE: None 187 CLAS0005 CAUSE: An outgoing IPC connection request was rejected because the specified Call User Data field is too long.
Logging Location Codes X.25 Logging Location Codes MESSAGE: Internal Error. 192 CLAS0002 CAUSE: Netfc_Delete_Pool failed on expedited semaphore pool (PARM = status from Netfc_delete_pool). ACTION: A resource was lost. If this happens frequently, the transport will not be able to open new connections. See Appendix A, “Submitting an SR,” of this manual. MESSAGE: Internal Error. 193 CLAS0002 CAUSE: Netfc_Delete_Pool failed on regular semaphore pool (PARM = status from Netfc_delete_pool).
Logging Location Codes X.25 Logging Location Codes MESSAGE: None 201 CLAS0005 CAUSE: An N-Disconnect packet was sent because an incoming connection request was rejected (PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an informative message. MESSAGE: None 202 CLAS0005 CAUSE: An N-Disconnect packet was sent because an IPC user or application program called an IPCShutdown intrinsic (PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an informative message.
Logging Location Codes X.25 Logging Location Codes MESSAGE: Internal Error. 209 CLAS0002 CAUSE: A Buffer could not be obtained from the control buffer pool (PARM = status from Bmgr_get_buffer). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 210 CLAS0002 CAUSE: Reading the configuration buffer failed on a Netcontrol Update (PARM = status and length). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes X.25 Logging Location Codes MESSAGE: Internal Error. 217 CLAS0002 CAUSE: Netfc_delete_pool failed on regular semaphore pool (PARM = status from Netfc_delete_pool). ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: None 218 CLAS0005 CAUSE: An incoming connection request was rejected because it requests Fast Select and the facility does not allow Fast Select (PARM = Device ID, VC number, cause, diagnostic). ACTION: None. This is an informative message.
Logging Location Codes X.25 Logging Location Codes MESSAGE: Internal Error. 223 CLAS0002 CAUSE: Map_X25_Update failed on inbound connection establishment (PARM = Status from Map_X25_Update). ACTION: See Appendix A, “Submitting an SR,” of this manual.
Logging Location Codes X.25 Logging Location Codes MESSAGE: Internal Error. 231 CLAS0002 CAUSE: Unknown link while DELLINKing. (PARM= link id) ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: Internal Error. 232 CLAS0002 CAUSE: Unknown link. (PARM= link id) ACTION: See Appendix A, “Submitting an SR,” of this manual.
Submitting an SR A Submitting an SR For further assistance from Hewlett-Packard, document the problem as an SR (Service Request) and forward it to your Hewlett-Packard Service Representative. Include the following information: • A characterization of the problem. Describe the events and symptoms leading up to and including the problem. Attempt to describe the source of the problem.
Submitting an SR • Using NS 3000/iX Network Services for NS 3000/iX • Online Diagnostic Subsystems Utilities Manual for the IEEE 802.3 links • HP 36923 Central Bus Programmable Serial Interface Installation and Reference Guide for point-to-point links. • Issue the LINKCONTROL linkname; STATUS = command for each link. Retain the output for your Hewlett-Packard Service Representative to further analyze. • Document your interim, or “workaround” solution.
Subsystem Identifiers B Subsystem Identifiers This appendix contains Table B-1, which shows the MPE/iX subsystem identifiers. These identifiers can be used to determine which MPE/iX subsystem returned an error. This helps you to determine which course of action is best for troubleshooting the error.
Subsystem Identifiers 116 NM Linker 117 Low level I/O 118 HPIO Channel Manager 119 Disk System Label Management 120 HPIB Adapter Management 121 Mux Adapter Manager 122 Port (IPC) Facility 123 Dispatcher 124 Diagnostics 125 CM Stack Size Management 126 CM System Primitives 127 CIPER Device Manager 128 Terminal I/O 129 7978 Tape Device Manager 130 Page Printer Device Manager 131 I/O Configurator 132 NS transport identifiers (IND) 133 Measurement Interface 134 Terminal Dev
Subsystem Identifiers 150 PROGEN process 151 Transaction Management 153 Files system label management 154 CM Support Routines 155 Job &Session 156 Scanner / Parser 157 Sysmain Process 158 Break Handling 159 Reply Information Table 160 User Defined Commands 161 Command Interpreter 163 Volume Management 164 Alink Device Adapter Manager 165 Debug 166 CI Variable Management 167 CI string substitution 168 CI Help Subsystem 169 CM Debugger 170 IEEE 802 CSMA/CD Adapter Manager
Subsystem Identifiers 184 Data com I/O Trace Facility 185 Disk Storage Management 186 Avesta Management Down/Upload Services 187 MPE/iX Error Management 188 CM Emulator, Translator, etc.
Subsystem Identifiers 217 LAPB PSI Driver (IND) 218 PSI Diagnostic Driver (IND) 219 Data com Link Support Services 220 Working set logging 221 Intrinsic aborts 222 Intrinsic Manes 223 External interrupt handler 224 Support Process for Memory Management and VSM 225 Mapped File Windowing 226 SEL QA Testing 227 IND Reverse pass through 228 IND SNA/IMF 229 WAN PSI Driver Module Configurator (IND) 230 TurboIMAGE 231 Native mode device file 232 Workstation configurator (IND) 233
Subsystem Identifiers 508 Defines error codes returned by stubs in MPE V/E ports 509 XLDCP:MPEXL performance data collection program 510 NS/SNA (IND) 511 Multiple connection manager Avesta flow control protocol (IND) 512 Remote link manger (IND) 513 Mirrored disk, mirrored mount server 514 Mirrored disk, SPU failure override 515 Network systems company (3rd party) hardware controller number 716 516 Architected interface 600 LAN Network Interface 601 Gateway Half Network Interface 602
Subsystem Identifiers 715 CM General NI Module 716 CM IPC Module 717 CM X.25 Module 718 CM TCP SIP Module 719 CM DS MONS Module 720 CM SMS Module 721 CM PAP Module 722 CM MAP Table Module 723 CM Kitel Module 725 NetBIOS Module 726 LAN Manager 727 SNA DHCF/iX 728 NM Mapping Tables 729 General Buffer Pools 730 Inbound Buffer Pools 731 Outbound Buffer Pools 732 Subsys ID/error message 733 NS Transport 734 SNA X.
Subsystem Identifiers 748 Streams/iX 749 TIO Trace Manager 750 FDDI LAN Driver 751 DLPI Provider 752 NWIX 1111 NS Mapping Table 576 Appendix B
Native Mode and Compatibility Mode Buffer Manager Error Codes C Native Mode and Compatibility Mode Buffer Manager Error Codes These tables contain all of the error codes returned by the native mode and compatibility mode buffer manager interfaces. Table C-1 contains the native mode buffer error codes.
Native Mode and Compatibility Mode Buffer Manager Error Codes Error Code Meaning -10; bfm_illegal_buf_size -11; bfm_illegal_option -12; bfm_illegal_user_alloc -13; bfm_illegal_offset -14; bfm_illegal_2_offset -15; bfm_illegal_data_length -16; bfm_illegal_address -17; bfm_illegal_wait_opt -18; bfm_illegal_compact_opt -19; bfm_illegal_freeze_opt -20; bfm_illegal_thaw_opt -21; bfm_illegal_priority -22; bfm_illegal_info_type -23 bfm_pool_size_exceeded -24; bfm_max_users_exceeded
Native Mode and Compatibility Mode Buffer Manager Error Codes Error Code Meaning -40; bfm_offset_left_data -41; bfm_offset_right_data -42; bfm_illegal_set_length -43; bfm_illegal_trf_userid -44; bfm_buf_empty -45; bfm_pool_var_size -46; bfm_object_overflow -47; bfm_insuff_v_memory -48; bfm_insuff_ports -49; bfm_insuff_queue_space -50; bfm_illegal_dest_buffer -51; bfm_freeze_error -52; bfm_thaw_error -53; bfm_unsupported_function -54; bfm_internal_error -55; bfm_invalid_v_bl
Native Mode and Compatibility Mode Buffer Manager Error Codes Table C-2 contains the compatibility mode buffer error codes. Table C-2 Compatibility Mode Buffer Error Codes NS 3000/iX Native Mode Buffer Err Code Corresponding NS 3000/iX Compatibility Mode Buffer Err Code -58 1, { createbufpool bad buffer size } -57 8, { users max.
Native Mode and Compatibility Mode Buffer Manager Error Codes NS 3000/iX Native Mode Buffer Err Code Corresponding NS 3000/iX Compatibility Mode Buffer Err Code -30 12, { buf_2_shared, 2nd buffer shared } -29 11, { buf_shared, 1st buffer shared } -28 10, { diff_user_id, not same user } -27 13, { diff_buf_pool, not same pool } -26 2, { share_count_exceeded } -25 8, { users_alloc_exceeded } -24 10, { max_users_exceeded, ditto } -23 8, { pool_size_exceeded } -22 2, { illegal_info_type, ille
Native Mode and Compatibility Mode Buffer Manager Error Codes NS 3000/iX Native Mode Buffer Err Code Corresponding NS 3000/iX Compatibility Mode Buffer Err Code 0 0, { bfm_OK, ditto } 1 -11, { interdata_gap_warning, ditto } 2 -10, { data_overlaid_warning, ditto } 3 -5, { zero_length_warning } 4 255, { not_compact_warning } 5 -1, { multi_buf_warning } 6 0, { buf_frozen_warning } 7 255, { not_frozen_warning } 8 0, { same_user_warning } 9 255, { store_link_warning } 10 255, { cm_limit_w
Index Numerics 100Base-T, 163 100VG-AnyLAN, 163 B Byes sent/received, 322 C Checksum errors, 322 CI errors, 11 internal errors, 11 invalid options, 11 resource errors, 11 syntax errors, 11 warnings, 11 Cn ass pkts sent/recd, 322 D Data Communication Logical Device Manager DCLDM, 328 DCLDM, 328 DIAL, 381 Distributed Terminal Controller DTC, 328 driver status, 170 DTC, 328 E Ethernet LAN, 328 F FDDI, 328 fiber distributed data interface FADDI, 328 Flags/Flags1/Flags2, 323 G GATEHALF, 328 gateway half network
