NS 3000/iX Error Messages Reference Manual HP e3000 MPE/iX Computer Systems Edition 10 Manufacturing Part Number: 36923-90043 E0801 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 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.
Contents 19. FDDI Error Messages 20. LAP-B Link Error Messages LAP-B Link Startup Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .438 LAP-B Link Driver Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .443 LAP-B Link Shutdown Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .458 21. Logging Location Codes Logging Formats . . . . . . . . . . . . . . . .
Contents TCP Logging Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657 UDP Logging Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692 X.25 Logging Location Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698 A. Submitting a CR B. Subsystem Identifiers C.
Contents 6
Figures Figure 21-1. Formatted Log Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462 Figure 21-2. Non-Critical Transport Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 Figure 21-3. Logging Statistics Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 8
Tables Table 21-1. Logging Subsystems and Class Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 21-2. Network Transport Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 21-3. Network Service Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table B-1. Subsystem Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table C-1.
Tables 10
Preface This manual contains most messages and errors generated by NS 3000/iX subsystems. What if the Error If you have encountered an error that is not in this manual, here are is Not in this some ideas on how you might find the errors: Manual • If it is an NMMGR error, or error from any of the Node Management Services Utilities, refer to Appendix A in the Using the Node Management Services (NMS) Utilities manual.
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 a CR.” 5002 MESSAGE: INVALID ASCAT.NET.SYS MESSAGE CATALOG. 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. 5003 MESSAGE: INTERNAL DS ERROR — COULD NOT ALLOCATE KEYWORD BUFFER.
CIERR Error Messages 5009 MESSAGE: NON-ALPHANUMERIC CHARACTER IN FILE NAME. 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. 5010 MESSAGE: EXPECTED , ; OR RETURN. CAUSE: An invalid delimiter was found after a parameter for a command option. ACTION: Correct the syntax error and reissue the command. 5010 MESSAGE: EXPECTED , ; OR RETURN.
CIERR Error Messages 5017 MESSAGE: TOO MANY PARAMETERS IN TRACE OPTION. CAUSE: More than the five defined parameters were specified in a DSLINE TRACE option. ACTION: Correct the syntax and reissue the command. 5018 MESSAGE: EXPECTED “ OR ‘. 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 5025 MESSAGE: TOO MANY TRACE OPTIONS (MAXIMUM OF 10). 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. 5026 MESSAGE: DS/3000 DSLINE OPTION IS IGNORED FOR NS NODE. 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 5032 MESSAGE: INTERNAL DS ERROR — COULD NOT GET PORT DST. CAUSE: A port data segment entry could not be allocated for the port between the CI and the Virtual Terminal server. ACTION: See Appendix A , “Submitting a CR.” 5033 MESSAGE: INTERNAL DS ERROR — COULD NOT START VT. CAUSE: The Virtual Terminal service could not be initiated. ACTION: See Appendix A , “Submitting a CR.” 5034 MESSAGE: INTERNAL DS ERROR — RECEIVED BAD PORT MESSAGE.
CIERR Error Messages 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.) 5038 MESSAGE: VIRTUAL TERMINAL SERVICE DETECTED AN ERROR. CAUSE: An error was detected by the Virtual Terminal server process. The error message for the VT error will precede the CI error message.
CIERR Error Messages 5044 MESSAGE: ALL DSLINE OPTIONS BUT RESET ARE IGNORED. CAUSE: Other options besides RESET were specified in a DSLINE command. ACTION: None (the selected environment is closed). 5045 MESSAGE: DSLINE OPTION OVERRIDES PREVIOUS DSLINE OPTION. 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). 5046 MESSAGE: DSLINE OPTION IGNORED.
CIERR Error Messages 5051 MESSAGE: EXPECTED SERVER PROGRM FILE NAME. 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. 5052 MESSAGE: EXPECTED MINIMUM NUMBER OF SERVERS (>=0 AND =32767). CAUSE: The second parameter of a SERVER option in an NSCONTROL command was not the minimum number of servers, a positive integer. ACTION: Correct the SERVER option and reissue the command.
CIERR Error Messages 5060 MESSAGE: INTERNAL DS ERROR — COULD NOT SEND CONTROL MESSAGE. CAUSE: The port message with the NSCONTROL information could not be sent from the CI to the DSDAD process. ACTION: See Appendix A , “Submitting a CR.” 5061 MESSAGE: DSDAD.NET.SYS DOES NOT EXIST. CAUSE: The DSDAD.NET.SYS program file is missing. ACTION: Restore the DSDAD.NET.SYS file from the NS product tape. 5062 MESSAGE: INVALID CONTROL OPTION.
CIERR Error Messages ACTION: Delete the parameters and reissue the command. 5074 MESSAGE: EXPECTED ONE OF USERS, SERVICES, SERVERS, OR ALL. 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. 5075 MESSAGE: EXPECTED MAXIMUM NUMBER OF SERVERS (=> 0 and >32767). CAUSE: The third parameter of a SERVER option in an NSCONTROL command was not a maximum number of servers, a positive integer.
CIERR Error Messages ACTION: Correct the syntax and reissue the command. 5081 MESSAGE: INVALID VERSION OPTION: EXPECTED MOD. 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. 5082 MESSAGE: REMOTE HELLO FAILED. CAUSE: In a REMOTE HELLO command, the Virtual Terminal service was set up, but the logon failed on the remote node. The Virtual Terminal service is then terminated.
CIERR Error Messages 5088 MESSAGE: REMOTE SESSION CANNOT LOGOFF WHILE FRA/RDBA IS ACTIVE. CAUSE: You cannot logoff until RFA/RDBA terminates. ACTION: Logoff when RFA/RDBA terminates. 5089 MESSAGE: ANOTHER PROCESS IS EXECUTING A REMOTE COMMAND IN THIS ENVIRONMENT. CAUSE: Your process is attempting to use an environment that is already in use. Only one process can access an environment at a time. ACTION: Try again later. 5095 MESSAGE: NOT ENOUGH STACK SPACE TO EXECUTE NS COMMAND.
CIERR Error Messages ACTION: See Appendix A , “Submitting a CR,” of this manual. 5106 MESSAGE: NO NFT SERVERS ARE CURRENTLY AVAILABLE. CAUSE: Maximum allowable limit of NFT Servers reached on system. ACTION: Wait until fewer DSCOPY applications are running on the system, or ask the system manager to raise the maximum allowable limit of NFT Servers (via the NSCONTROL command). Try again. 5400 MESSAGE: NSCONTROL COMMAND ERROR. CAUSE: NSCONTROL error found.
CIERR Error Messages command, see Appendix A , “Submitting a CR,” of this manual. 5505 MESSAGE: INTERNAL ERROR — COULD NOT STORE REQ. ID IN DSTABLE. 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 a CR,” of this manual. 5506 MESSAGE: NO $BACK ENVIRONMENT IN THIS SESSION. CAUSE: The session executing the DSLINE command does not have $BACK environment.
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 627 MESSAGE: CANNOT OPEN TRACE FILE filename. 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. 628 MESSAGE: CANNOT CLOSE TRACE FILE filename. CAUSE: A DSLINE TRACE=OFF was issued, but the indicated trace file cannot be closed.
CIERR Error Messages Network Services Environment Error Messages 633 MESSAGE: ID OR NODE IN name IS GREATER THAN 16 CHARACTERS. 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. 634 MESSAGE: ID OR NODE IN name CONTAINS A NON-ALPHANUMERIC CHARACTER.
CIERR Error Messages Network Services Environment Error Messages 641 MESSAGE: ORGANIZATION IN name IS GREATER THAN 16 CHARACTERS. 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. 642 MESSAGE: ORGANIZATION IN name CONTAINS A NON-ALPHANUMERIC CHARACTER.
CIERR Error Messages Network Services Environment Error Messages environment). 687 MESSAGE: CANNOT CHANGE NS NODE NAME FROM nodename TO GIVEN DOMAIN NAME. 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. 688 MESSAGE: CANNOT CHANGE DOMAIN NODE NAME FROM nodename TO GIVEN NS NAME. CAUSE: The environment already exists with a 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 627 MESSAGE: CANNOT OPEN TRACE FILE filename. 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. 628 MESSAGE: CANNOT CLOSE TRACE FILE filename. CAUSE: A DSLINE TRACE=OFF was issued, but the indicated trace file cannot be closed. ACTION: Check the parameters for the TRACE option, correct if in error, and reissue the command.
DSERR Error Messages is longer than the allowed 16 characters. ACTION: Shorten the name and reissue the command. 634 MESSAGE: ID OR NODE IN name CONTAINS A NON-ALPHANUMERIC CHARACTER. 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 ?. ACTION: Correct the name and reissue the command. 635 MESSAGE: EXPECTED A DOMAIN AFTER THE NODE OR ID IN name.
DSERR Error Messages 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. 642 MESSAGE: ORGANIZATION IN name CONTAINS A NON-ALPHANUMERIC CHARACTER. CAUSE: The third (organization) part of a (fully qualified) environment ID or node name contains a character that is not alphabetic or numeric ACTION: Correct the name and reissue the command.
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. 6 MESSAGE: UNABLE TO CONNECT TO TARGET NODE. CAUSE: A connection could not be established to the computer where the target file resides.
NS/NFTERR and NS/NFTWARN Messages 13 MESSAGE: COUNTER OFFER. CAUSE: An internal error has occurred during negotiations between the source and target computers. ACTION: See Appendix A , “Submitting a CR,” of this manual. 14 MESSAGE: REQUESTED DATA TYPE WAS REFUSED. 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. 15 MESSAGE: REQUESTED RECORD WAS REFUSED.
NS/NFTERR and NS/NFTWARN Messages 20 MESSAGE: TARGET RECORD SIZE IS INVALID. CAUSE: Requested RSIZE is too large. ACTION: Specify a smaller record size. 21 MESSAGE: TARGET FILE SIZE IS INVALID. CAUSE: Requested FSIZE is too large. ACTION: Specify a smaller record size. 22 MESSAGE: DUPLICATE TARGET FILE. 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. 28 MESSAGE: UNABLE TO PURGE TARGET FILE. CAUSE: The existing target file could not be purged. ACTION: Refer to the qualifying file system error string to determine what to do. 29 MESSAGE: INVALID TARGET FILE. CAUSE: Check the target file name syntax and try again. ACTION: Refer to the qualifying file system error string to determine what to do. 30 MESSAGE: UNABLE TO PURGE SOURCE FILE.
NS/NFTERR and NS/NFTWARN Messages 35 MESSAGE: INVALID OR UNSUPPORTED TARGET DEVICE. 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. 36 MESSAGE: UNABLE TO CLOSE TARGET FILE. CAUSE: An unexpected file system error occurred in closing the target file.
NS/NFTERR and NS/NFTWARN Messages 45 MESSAGE: COMPRESSION WILL NOT BE DONE FOR THE CURRENT TRANSFER. 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. 46 MESSAGE: UNABLE TO TURN ON TRACING. CAUSE: Indicates that an internal error has occurred. File transfer will continue without tracing. ACTION: See Appendix A , “Submitting a CR,” of this manual.
NS/NFTERR and NS/NFTWARN Messages 57 MESSAGE: INCOMING CONNECTION HAS GONE DOWN. 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 Appendix A , “Submitting a CR.” 58 MESSAGE: MOVE NOT SUPPORTED. CAUSE: Source mainframe does not support the MOVE option. The transfer will take place, but the source file will not be purged. ACTION: None. 59 MESSAGE: UNABLE TO OPEN CHECKPOINT/RESTART FILE.
NS/NFTERR and NS/NFTWARN Messages 62 MESSAGE: UNABLE TO RESTART TRANSFER. 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. 63 MESSAGE: SOURCE AND TARGET CHECKPOINTS DO NOT MATCH.
NS/NFTERR and NS/NFTWARN Messages 67 MESSAGE: TARGET FILE BLOCK SIZE BEING CHANGED DUE TO FILE SYSTEM DIFFERENCES. 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. 0 MESSAGE: NO ERRORS WERE DETECTED. CAUSE: No errors occurred during the file transfer. ACTION: None. This is an informative message. 1 MESSAGE: UNABLE TO OPEN NFT MESSAGE CATALOG.
NFT/3000 Error Messages 5 MESSAGE: COMMAND LINE IS TOO LONG. 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. 6 MESSAGE: CALL TO GENMESSAGE FAILED. 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 ACTION: Retype and reissue the command. 14 MESSAGE: UNKNOWN KEYWORD: ! CAUSE: Usually a typographical error. ACTION: Retype and reissue the command. 15 MESSAGE: REMOTE ENVIRONMENT SPECIFIED BY USER DOES NOT EXIST. CAUSE: The session associated with the specified node or environment cannot be found. Either the session was aborted externally or an internal error occurred. ACTION: Ask your system manager if your session was aborted.
NFT/3000 Error Messages 25 MESSAGE: SCHAR AND ICHAR NOT ALLOWED AS GLOBAL SPECS. CAUSE: SCHAR and ICHAR may not follow “+” on the command line. ACTION: Specify these options for every transfer. 26 MESSAGE: INVALID RESTART SPEC. CAUSE: RESTART option syntax is incorrect. ACTION: See Using NS 3000/iX Network Services for correct syntax. 27 MESSAGE: FILE ID NOT ALLOWED AS GLOBAL SPECIFICATION. CAUSE: File ID cannot follow “+” on command line. All other specifications may be made global.
NFT/3000 Error Messages ACTION: None. 38 MESSAGE: ! OVERRIDES PREVIOUS DATA TYPE. CAUSE: Either BIN or ASC was specified when the other was already specified in the command line or globally. ACTION: None. 40 MESSAGE: INVALID FILE ID: ! CAUSE: Usually caused by blank characters in the file ID, or by omitting a delimiter or parameter. ACTION: Retype and reissue the command. 41 MESSAGE: INVALID NODE SPEC: ! CAUSE: Usually caused by blank characters in the node (or environment) specification.
NFT/3000 Error Messages ACTION: See Appendix A , “Submitting a CR,” of this manual. 48 MESSAGE: ATTEMPT TO PLACE NFT SERVER BACK IN SYSTEM ENVIRONMENT FAILED. CAUSE: Probable internal error. ACTION: See Appendix A , “Submitting a CR,” of this manual. 49 MESSAGE: BUFFER MANAGER ERROR. CAUSE: When an NFT process is initiated it attempts to place itself into the appropriate user session (or job). The error results when this attempt fails.
NFT/3000 Error Messages 56 MESSAGE: CREATION OF INTERNAL IPC PORT FAILED. CAUSE: Probable internal error. ACTION: See Appendix A , “Submitting a CR,” of this manual. 57 MESSAGE: ATTEMPT TO RECEIVE NFT CHANGE REQUEST FAILED. CAUSE: Probable internal error. ACTION: See Appendix A , “Submitting a CR,” of this manual. 58 MESSAGE: UNKNOWN INTERNAL MESSAGE WAS RECEIVED. CAUSE: Probable internal error. ACTION: See Appendix A , “Submitting a CR,” of this manual. 60 MESSAGE: NFT SERVER WAS ABORTED.
NFT/3000 Error Messages 66 MESSAGE: SOURCE DEVICE SPEC OVERRIDES GLOBAL SPEC. CAUSE: An existing global specification conflicts with a specification in the current transfer. The specification in the current transfer will override the global specification for the current transfer only. ACTION: None. 67 MESSAGE: TARGET NODE SPEC OVERRIDES GLOBAL SPEC. CAUSE: An existing global specification conflicts with a specification in the current transfer.
NFT/3000 Error Messages 74 MESSAGE: ERROR OCCURRED WHEN SETTING UP NFT SERVER. CAUSE: Probable internal error. ACTION: See Appendix A , “Submitting a CR,” of this manual. 75 MESSAGE: NO NFT SERVERS ARE CURRENTLY AVAILABLE. CAUSE: The number of active NFT servers (set via NSCONTROL) has reached its limit. ACTION: Adjust the maximum number of NFT servers allowed via NSCONTROL. If this is not possible, try to invoke NFT again as a server may have terminated.
NFT/3000 Error Messages 84 MESSAGE: INSUFFICIENT BUFFER SPACE FOR USER REQUEST. CAUSE: Probable system resource problem. ACTION: See Appendix A , “Submitting a CR,” of this manual. 85 MESSAGE: PM CAPABILITY IS REQUIRED FOR DEBUG. CAUSE: To enter debug in NFT, Privileged Mode (PM) capability is required. ACTION: Contact your system operator. 86 MESSAGE: CI COMMAND EXECUTION FAILED. CAUSE: Usually accompanied by an MPE error. ACTION: Fix the MPE error.
NFT/3000 Error Messages 93 MESSAGE: INVALID STRING FOLLOWING CLOSING QUOTE. CAUSE: One or more invalid characters follow a closing quote. A file name, node name, or logon name enclosed in quotes must be followed by an appropriate delimiter. ACTION: Re-enter the DSCOPY command using correct delimiters. 94 MESSAGE: BOUNDS VIOLATION. CAUSE: Internal error parameter out of bounds. ACTION: Check parameters passed to DSCOPY or DSCOPY MSG. 95 MESSAGE: SPLITSTACK MODE CALLS NOT ALLOWED.
NFT/3000 Error Messages 106 MESSAGE: ! IS AN INVALID DELIMITER AS USED IN RESTART SPEC. CAUSE: Typographical errors. ACTION: See Using NS3000/iX Network Services for the correct delimiters. 109 MESSAGE: INVALID COMMAND INPUT FORMAL FILE DESIGNATOR. CAUSE: Usually a typographical error. Either a right parenthesis is missing, or the formal file designator is too long. ACTION: Check the command syntax and try again. 110 MESSAGE: FILE COMMAND WITH ‘DEL’ OPT. NOT ALLOWED.
NFT/3000 Error Messages 116 MESSAGE: TARGET FILE CANNOT BE BYTE STREAM RECORD TYPE. CAUSE: Target file is a byte stream file. ACTION: NFT is POSIX aware, not POSIX compliant, and does not support byte stream files.
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. 0 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). 8 MESSAGE: INVALID OPTION IN THE opt RECORD. 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.
NetIPC (SOCKERRS) Error Messages ACTION: Contact your operator to see if the table can be expanded. 18 MESSAGE: FORMAT OF THE opt RECORD IS INCORRECT. CAUSE: NetIPC was unable to parse the specified opt record. ACTION: Check your INITOPT and ADDOPT calls. 19 MESSAGE: ERROR DETECTED WITH MAXIMUM MESSAGE SIZE OPTION. 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 28 MESSAGE: INVALID NAME LENGTH. CAUSE: Specified name length was too large or negative. ACTION: Check your name length parameter. Shorten the name if necessary. 29 MESSAGE: INVALID DESCRIPTOR. CAUSE: Specified descriptor is not a valid socket, connection, or destination descriptor. ACTION: Check the value being specified. 30 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 a CR,” of this manual. 37 MESSAGE: NAME NOT FOUND. 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 46 MESSAGE: UNABLE TO INTERPRET RECEIVED PATH REPORT. CAUSE: Unable to interpret the information returned by the remote socket registry process regarding the looked-up socket. ACTION: See Appendix A , “Submitting a CR,” of this manual. 47 MESSAGE: INVALID MESSAGE RECEIVED FROM REMOTE SERVER. CAUSE: The message received from the remote registry process does not appear to be a valid socket registry message. ACTION: See Appendix A , “Submitting a CR,” of this manual.
NetIPC (SOCKERRS) Error Messages 56 MESSAGE: CALL WOULD BLOCK WHILE USING SELECT ASYNCHRONOUS NODE. 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. 57 MESSAGE: ATTEMPT TO EXCEED LIMIT OF NOWAIT SENDS OUTSTANDING. 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 65 MESSAGE: CONNECTION ABORTED BY LOCAL PROTOCOL MODULE. 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 a CR,” of this manual. 66 MESSAGE: INVALID CONNECTION DESCRIPTOR. CAUSE: Supplied value is not that of a valid VC socket (connection) descriptor. ACTION: Check the value being given. 67 MESSAGE: CONNECTION FAILURE DETECTED.
NetIPC (SOCKERRS) Error Messages 76 MESSAGE: INVALID TIMEOUT VALUE. CAUSE: Value specified for the timeout is negative. ACTION: Modify the value. 77 MESSAGE: INVALID WAIT/NOWAIT MODE. CAUSE: Mode of socket cannot be used. ACTION: Use IPCCONTROL to specify correct mode. 78 MESSAGE: TRACING NOT ENABLED. CAUSE: Attempted to turn off trace when tracing was not on. ACTION: Remove the call. 79 MESSAGE: INVALID TRACE FILE NAME. CAUSE: Requested trace file name is not valid.
NetIPC (SOCKERRS) Error Messages ACTION: None, but no NetIPC or protocol module errors are available. 85 MESSAGE: INVALID SOCKET ERROR NUMBER. CAUSE: IPCERRMSG was called with an invalid NetIPC error code. ACTION: Check the value being passed. 86 MESSAGE: UNABLE TO OPEN ERROR CATALOG SOCKCAT.NET.SYS. CAUSE: The error message catalog does not exist, it is opened exclusively, or the caller does not have access rights to the file. ACTION: Notify your operator.
NetIPC (SOCKERRS) Error Messages ACTION: See Appendix A , “Submitting a CR,” of this manual. 96 MESSAGE: INTERNAL BUFFER MANAGER ERROR. CAUSE: Attempted use of the buffer manager by NetIPC or the protocol module resulted in an error. ACTION: See Appendix A , “Submitting a CR,” of this manual. 98 MESSAGE: INVALID DATA SEGMENT INDEX IN VECTORED DATA. CAUSE: Data segment index value in the vectored data array is not valid. ACTION: Check the value being supplied.
NetIPC (SOCKERRS) Error Messages ACTION: See Appendix A , “Submitting a CR,” of this manual. 106 MESSAGE: ADDRESS CURRENTLY IN USE BY ANOTHER SOCKET. CAUSE: Address being specified for use is already being used. ACTION: Stop application or choose a different socket address. 107 MESSAGE: TRANSPORT IS GOING DOWN. CAUSE: The transport is being shut down. ACTION: If you are a privileged user trying to specify a well known address, try again later.
NetIPC (SOCKERRS) Error Messages 114 MESSAGE: CREATION OF SOCKET REGISTRY PROCESS FAILED. CAUSE: Socket registry program missing. ACTION: Contact your Hewlett-Packard representative for assistance. 116 MESSAGE: DESTINATION UNREACHABLE. CAUSE: The transport was unable to route the packet to the destination. ACTION: Notify your operator. 117 MESSAGE: ATTEMPT TO ESTABLISH CONNECITON FAILED. CAUSE: Protocol module was unable to set up the requested connection.
NetIPC (SOCKERRS) Error Messages in value. 127 MESSAGE: UNABLE TO READ ENTRY FROM OPT RECORD. 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. ACTION: Check entry number, make sure the option record has not been written over and check output buffer length. 131 MESSAGE: PROTOCOL MODULE DOES NOT HAVE SUFFICIENT RESOURCES. CAUSE: Protocol module is temporarily out of buffers or internal data descriptors.
NetIPC (SOCKERRS) Error Messages field. The connection is still up and operational but some data may have been lost. 151 MESSAGE: COULD NOT OBTAIN A SEMAPHORE. CAUSE: The attempt to obtain a semaphore before sending a message to the protocol module failed. ACTION: See Appendix A , “Submitting a CR,” of this manual. 153 MESSAGE: SOCKET IS ALREADY IN USE. CAUSE: A single socket per network interface can be created with the catch-all capability. ACTION: Wait for catch-all socket to be released.
NetIPC (SOCKERRS) Error Messages 162 MESSAGE: X.25 PERMANENT VIRTUAL CIRCUIT DOES NOT EXIST. CAUSE: No PVC configured. ACTION: Check the configuration file for X.25. 163 MESSAGE: PERMANENT VIRTUAL CIRCUITALREADY ESTABLISHED. CAUSE: A connection request was issued on a PVC which is in use by another process. ACTION: Select a different PVC or retry later. 164 MESSAGE: ADDRESS VALUE IS OUT OF RANGE. CAUSE: Address specified in opt parameter is out of range.
NetIPC (SOCKERRS) Error Messages 172 MESSAGE: CONNECTION MUST BE REJECTED. CAUSE: An IPCCONTROL request 9, accept the connection, cannot be performed. ACTION: Use IPCCONTROL request 15 to reject the connection. 173 MESSAGE: MORE DATA IS AVAILABLE. CAUSE: Warning message. READOPT request was for less data than available. ACTION: Specify a greater length in READOPT.
NetIPC (SOCKERRS) Error Messages 78 Chapter 5
Virtual Terminal (VT ERROR) Error Messages 6 Virtual Terminal (VT ERROR) Error Messages 1 MESSAGE: RESOURCE NOT RELEASED ON TERMINATION. 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. 2 MESSAGE: INVALID STATUS FOUND. 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 7 MESSAGE: UNEXPECTED/BAD RESPONSE FROM VT. 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 CR. 8 MESSAGE: VT SERVER NOT ADOPTED.
Virtual Terminal (VT ERROR) Error Messages 16 MESSAGE: CR/LF SWITCH FAILED. 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. 17 MESSAGE: SET READ TIMEOUT FAILED. CAUSE: Setting of a timed read failed.
Virtual Terminal (VT ERROR) Error Messages 25 MESSAGE: SET DRIVER MODE FAILED. CAUSE: The File System did not alter the setting of the driver/terminal handshake mode. ACTION: Terminate the remote program. 26 MESSAGE: TERMINAL NOT ALLOCATED. CAUSE: The terminal could not be allocated for access. ACTION: Check the MPE configuration and retry the remote session. 27 MESSAGE: SET TERMINAL TYPE FAILED. 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. 34 MESSAGE: CANNOT ACCESS SESSION DEVICE. 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. 35 MESSAGE: VT INITIALIZATION FAILED. 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. 42 MESSAGE: REMOTE NOT RESPONDING, CONNECTION CLOSED. CAUSE: The remote VT closed the connection. The session has been terminated. ACTION: Attempt to re-logon to the remote machine. 43 MESSAGE: VT COULD NOT SECURE BUFFER SPACE. 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 51 MESSAGE: VT TERMINATED, COULD NOT FOPEN TERMINAL. 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 a CR,” of this manual. 52 MESSAGE: VT TERMINATED, INVALID DEVICE FOR SESSION. CAUSE: Your session device is not an acceptable MPE session device. ACTION: Verify the configuration in SYSGEN.
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. 500 MESSAGE: ENVIRONMENT envum: envid. CAUSE: The defined or affected environment has been assigned an environment number envum and environment ID envid.
Network Services Information Messages 504 MESSAGE: PLEASE ANSWER YES OR NO. 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. 505 MESSAGE: KILL RPM PROCESS ON envid? 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 510 MESSAGE: TRACE FILE FOR ALL SERVICES TO envid IS filename. 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 of environments, the TRACE FILE FOR ALL SERVICES TO envid IS filename message is displayed for each environment. ACTION: This is an informative message. 515 MESSAGE: TRACE FILE FOR RPM TO envid IS filename. CAUSE: A DSLINE with a TRACE=ON or TRACE=OFF option has been executed. These messages indicate which service to what environment is being (or has been) traced, and the fully qualified name of the trace file.
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. 49 MESSAGE: HIERARCHICAL OR BYTE STREAM FILES NOT ALLOWED THROUGH RFA. UNIMPLEMENTED FUNCTION.
Remote File Access Error Messages 214 MESSAGE: ILLEGAL USE OF NODE NAME. DS LINE WAS NOT OPENED WITH A USER :DSLINE COMMAND. (Actual Message Displayed) CAUSE: The node does not exist or the specified node name is invalid. ACTION: Correct the node name. 217 MESSAGE: NOT ENOUGH STACK SPACE FOR RFA. INSUFFICIENT AMOUNT OF USER STACK AVAILABLE. (Actual Message Displayed) CAUSE: The MPE PREP command allocated the default ;MAXDATA or STACK values to the program, which are too small.
Remote File Access Error Messages 240 MESSAGE: LOCAL COMMUNICATION LINE NOT OPENED BY OPERATOR. LOCAL COMMUNICATION LINE WAS NOT OPENED BY OPERATOR. (Actual Message Displayed) CAUSE: The RFA/RDBA service has not been started. ACTION: Use the NETCONTROL START command to open the line. 242 MESSAGE: INTERNAL ERROR. INTERNAL DS SOFTWARE ERROR ENCOUNTERED. (Actual Message Displayed) CAUSE: This is an internal error. ACTION: See Appendix A , “Submitting a CR,” 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 e3000 implementation of RPM. The first range (0–99) includes generic RPM errors.
Remote Process Management Error Messages 5 MESSAGE: ILLEGAL OPTION FORMAT. 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. 6 MESSAGE: INVALID LOGIN. 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 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. In this case the program’s descriptor is deleted when the program terminates, and a later RPMKILL receives the Invalid Program Descriptor error. ACTION: Depending on the cause: 1. Correct the program descriptor.
Remote Process Management Error Messages 11 MESSAGE: PROGRAM ACCESS ERROR. 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 16 MESSAGE: UNSUPPORTED OPTION. 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. 17 MESSAGE: RPMCREATE LENGTH ERROR. CAUSE: An RPMCREATE resulted in a message that could not be handled by the remote node RPM software.
Remote Process Management Error Messages positive, and you are getting the error anyway, submit an CR. See Appendix A , “Submitting a CR.” 22 MESSAGE: REMOTE SON ABORTED. CAUSE: The remote process aborted abnormally. ACTION: Check the remote program to ascertain what caused the premature termination. 100 MESSAGE: INSUFFICIENT STACK SPACE. CAUSE: The program calling RPMCREATED, RPMKILL, RPMCONTROL, or RPMGETSTRING could not expand its stack to accommodate the requirements of the RPM software.
Remote Process Management Error Messages 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. By means of the environment facility of Network Services, it is possible to have more than one remote session on the same remote node.
Remote Process Management Error Messages 113 MESSAGE: BAD RPMCONTROL STATE. CAUSE: RPMCONTROL was unable to suspend the remote process. A system process may have impeded the remote process, or the remote process may be waiting for a system resource. ACTION: Call RPMCONTROL again with the suspend option, or attempt to use another method of synchronization such as NetIPC. 114 MESSAGE: SWITCH FAILURE. CAUSE: RPM was unable to call a native mode procedure.
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. 21 MESSAGE: SHUTDOWN COMPLETE CAUSE: The graceful release shutdown for the connection has been completed. The connection has been released. ACTION: None. For notification purposes only. 22 MESSAGE: IPC SHUTDOWN COMPLETE CAUSE: The connection has been terminated by IPC. ACTION: None. For notification purposes only.
Network Transport Protocol (PMERR) Error Messages -20 MESSAGE: CONNECTION ENTRY ALLOCATION FAILED 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. Locate matching log instance for resource error if possible. Error message will indicate class 2, subsystem 3, entity TCP, location 102xx.
Network Transport Protocol (PMERR) Error Messages ACTION: This is an internal error between TCP and the upper layer protocol (IPC or BSD Sockets). You should submit an CR on 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 -45 MESSAGE: DATA SENT AFTER SHUTDOWN CAUSE: An attempt was made to send data after a simplex-in or graceful release lingering shutdown call had been executed. ACTION: This is an internal error between TCP and the upper layer protocol (IPC or BSD Sockets). The upper layer protocol should circumvent any further sends before they reach TCP. You may wish to submit an CR for this defect.
Network Transport Protocol (PMERR) Error Messages ACTION: There are many possible reasons for a retransmission time out to occur. Potential problems include severe network bottlenecks, remote system CPU starvation, incorrect or improperly tuned configuration, remote node failure, gateway or network failure, and servers which are not processing new connection requests (or which are becoming backlogged). Check for remote system and network failure first.
Network Transport Protocol (PMERR) Error Messages 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. Consult path resolution error listings to diagnose problem. -91 MESSAGE: PATH FAILURE CAUSE: Excessive retransmissions prompted TCP to test the path to the remote node (an algorithm called active rerouting or negative advice) and path was reported as lost.
Network Transport Protocol (PMERR) Error Messages -103 MESSAGE: DATA BEFORE CONNECT 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. -110 MESSAGE: SEND ATTEMPT BEFORE NETWORK START CAUSE: An attempt was made to send data before the network was started. ACTION: This is an IPC or BSD sockets internal error.
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. -1 MESSAGE: -1 CAUSE: Bad item values. ACTION: Provide a valid item (0–5).
FPARSE Error Messages -9 MESSAGE: -9 CAUSE: NS not present, but user specified envid. ACTION: Install NS or do not specify envid. -101 MESSAGE: -101 CAUSE: First character of filename not alphabetic. ACTION: Provide a valid MPE file starting character. -102 MESSAGE: -102 CAUSE: Filename expected in the string. ACTION: Provide a filename in the string. -103 MESSAGE: -103 CAUSE: Filename identifier too long. ACTION: Provide a filename 8 characters or less.
FPARSE Error Messages -110 MESSAGE: -110 CAUSE: First character of accountname not alphabetic. ACTION: Provide a valid alphabetic starting character for the account. -111 MESSAGE: -111 CAUSE: Accountname expected in the string. ACTION: Provide an account name in the string. -112 MESSAGE: -112 CAUSE: Accountname identifier too long. ACTION: Provide an accountname of 8 characters or less. -113 MESSAGE: -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. 0001 MESSAGE: TRANSPORT NOT ACTIVE. CAUSE: Issued NETCONTROL STATUS command on inactive transport. ACTION: Issue NETCONTROL START. 0011 MESSAGE: DIAG COMMAND NOT SUPPORTED. NETXPORT RUNNING IN UNSUPPORTED MODE.
NETXPORTERR Error Messages 2000 MESSAGE: TRACE FILE IS !. CAUSE: Informative message. ACTION: None. 4000 MESSAGE: TOO MANY PARMS IN COMMAND LINE. 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. 4002 MESSAGE: EXPECTED STATUS KEYWORD ALL. CAUSE: Typographical error.
NETXPORTERR Error Messages ACTION: Check the NS 3000/iX Operations and Maintenance Reference Manual for proper syntax. Correct and retry. 4009 MESSAGE: BOTH START AND STOP ISSUED. CAUSE: Both parameters not allowed in a single NETCONTROL command. ACTION: Pick appropriate command. Correct and retry. 4011 MESSAGE: INVALID TRACE TYPE. EXPECTED COMBINATION OF D,H,M,B,N,S. CAUSE: Usually a typographical error. Recommended combination for trace type is HMD.
NETXPORTERR Error Messages ACTION: Reissue the command after waiting a few minutes. If the problem persists, then see Appendix A , “Submitting a CR,” of this manual. 4021 MESSAGE: TRACE OPEN ERROR. 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 a CR,” of this manual. 4023 MESSAGE: BAD DIAG VALUE, EXPECTED SET(0–31) OR RST(0–31).
NETXPORTERR Error Messages ACTION: Reissue the NETCONTROL command using only one of the keywords. 4033 MESSAGE: NO FUNCTION KEYWORDS ENTERED. 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. 4034 MESSAGE: TRACE PREVIOUSLY ENABLED. CAUSE: Informative message. ACTION: None. 4035 MESSAGE: ENTITY WAS NOT TRACING. CAUSE: Informative message. ACTION: None.
NETXPORTERR Error Messages 4044 MESSAGE: VERSION ERROR: BAD MODULE (S). CAUSE: There may be no version stamp; file label may be overwritten, or possible bad software installation. ACTION: See Appendix A , “Submitting a CR,” of this manual. 4045 MESSAGE: ALREADY STARTED. CAUSE: NETCONTROL START command issued for an already active entity. ACTION: None. 4046 MESSAGE: NOT STARTED. CAUSE: The NETCONTROL STOP command was issued when the network transport was never running.
NETXPORTERR Error Messages 4052 MESSAGE: COMMAND NOT EXECUTED DUE TO VERSION MISMATCH. CAUSE: Missing software modules or module version number mismatch. ACTION: Issue the NETCONTROL VERSION=MOD command for more information. See Appendix A , “Submitting a CR,” of this manual. 4053 MESSAGE: ! DEVICE NOT CONFIGURED. 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.
NETXPORTERR Error Messages 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. 4060 MESSAGE: THIS UPDATE IS NOT ALLOWABLE FOR THIS ENTITY. 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.
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 a CR,” of this manual. 4101 MESSAGE: TRANSPORT NOT YET DOWN. 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 a CR,” 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 a CR,” of this manual. 3. Consult the SHERLOCK diagnostics to determine the cause of the link error.
NETXPORTERR Error Messages 4209 MESSAGE: X.25 NOT STARTED ON DTC FOR DEVICE linkname. CAUSE: The X.25 card on the DTC was reset, but X.25 was not restarted. 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. 4210 MESSAGE: HOST LOST CONTACT WITH DTC FOR DEVICE linkname. CAUSE: The control connection between the host and the DTC was lost.
NETXPORTERR Error Messages 4215 MESSAGE: DTC NAME NOT CONFIGURED IN NMCONFIG PATH “LINK.linkname”. CAUSE: The path LINK.linkname was created in NMCONFIG.PUB.SYS, but the DTC name was not added. ACTION: Using NMMGR, update the path and validate the DTS subsystem. 4216 MESSAGE: CANNOT FIND DTC CONFIGURED FOR DEVICE linkname. 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.
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 656 MESSAGE: UNKNOWN SERVER servername. 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. 657 MESSAGE: SERVER pin DOES NOT SUPPORT DEBUG. 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 662 MESSAGE: INVALID DADCONF.NET.SYS CONFIGURATION FILE. CAUSE: To be determined. ACTION: Check that the JCONFJOB job has been streamed. If not, issue the command STREAM JCONFJOB. 663 MESSAGE: SERVICE NSservice DOES NOT SUPPORT AUTOLOGON. CAUSE: You cannot automatically log on with the Network Service you are using. ACTION: Do not use the AUTOLOGON function with this service. 698 MESSAGE: INSUFFICIENT STACK SPACE. 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. 1 MESSAGE: NO DATA FOUND IN PATH RECORD. CAUSE: No data has been entered for the specified path.
VALERR and VALWARN Messages 7 MESSAGE: NO NETWORKS (NETWORK INTERFACES) CONFIGURED. CAUSE: No network interfaces have been configured. ACTION: Configure the network interface, using the Network Interface Configuration screen (path NETXPORT.NI). 8 MESSAGE: RETRANSMIT LOWER (n) BOUND MUST BE = UPPER BOUND (m). 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. 20 MESSAGE: THIS LINK IS NOT ALLOWED FOR THIS NI TYPE. 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. 25 MESSAGE: SECURITY ENABLED BUT NO SECURITY STRING CONFIGURED.
VALERR and VALWARN Messages 31 MESSAGE: CONFIGURED REACHABLE NETS (n) MUST BE = IPU MAX NETS (m). 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. 32 MESSAGE: CONFIGURED GATEWAYS (n) MUST BE = IPU MAX GATES (m).
VALERR and VALWARN Messages to a non-LAN link in Link Configuration. ACTION: Configure a LAN802.3 type link on the NI Link Screen (NETXPORT.NI.NIname.LINK). 39 MESSAGE: ONLY 1 WILD CARD ADDRESS MAPPING ALLOWED FOR EACH ROUTER NI. CAUSE: There are two or more Router Mapping Screens with the wild card IP address “@” configured for the same router NI. ACTION: Consult the discussion on the use of the wild card address on the Router Mapping Screen in the NS 3000/iX NMMGR Screens Reference Manual.
VALERR and VALWARN Messages 46 MESSAGE: NOT A VALID LOGGING CLASS FOR SUBSYSTEM 3. 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. Validate the Network Transport again. 49 MESSAGE: IP NODE ADDRESS CANNOT EQUAL ZERO.
VALERR and VALWARN Messages LOGGING.SUB0005 screen. Validate the Network Transport again. 103 MESSAGE: THREE LOGGING CLASSES REQUIRED FOR SUBSYSTEM 5. CAUSE: There are not three logging classes configured beneath the LOGGING.SUB0005 path in the configuration file. ACTION: Use the NMMGR utility to add in configuration records CLAS0000 through CLAS0002 so that all three logging classes are configured for NetIPC. Validate the Network Transport again. 104 MESSAGE: NOT A VALID LOGGING CLASS FOR SUBSYSTEM 5.
VALERR and VALWARN Messages 108 MESSAGE: NO PHONE NUMBER REQUIRED FOR DC LINK. CAUSE: Phone data has been erroneously configured for a direct connect link. ACTION: Delete the phone data, or correct the link type. 109 MESSAGE: LOOPBACK ONLY CONFIGURATION NOT ALLOWED. CAUSE: Loopback is the only NI configured. ACTION: Use NMMGR to add NIs for LAN or router networks and validate the Network Transport again. 110 MESSAGE: LINK TYPE MUST BE X.25 IN LINK CONFIGURATION.
VALERR and VALWARN Messages ACTION: Use NMMGR to configure all classes under the path LOGGING.SUB0040. Validate the network transport configuration again. 115 MESSAGE: LINK TYPE FOR SNA NI MUST BE SNA. CAUSE: A link of type SNA must be used when configuring an NI for NS over SNA. ACTION: Use NMMGR to configure a link of type SNA. Validate Transport again. 300 MESSAGE: FACILITY SET setname DOES NOT EXIST. CAUSE: In the SVCPATH configuration an X.25 address key is mapped to an undefined facility set.
VALERR and VALWARN Messages 325 MESSAGE: X.25 ADDRESS address is defined more than once. CAUSE: An X.25 address is defined more than once under the NETXPORT.NI.NIname.PROTOCOL.X25.SVCPATH path. ACTION: Make sure all X.25 addresses are unique in a given SVC configuration path. 350 MESSAGE: MORE THAN 1024 SVCPATHS CONFIGURED. CAUSE: The number of SVC entries under the NETXPORT.NI.NIname.PROTOCOL.X25.SVCPATH path exceeds the maximum of 1024 allowed. ACTION: Delete the excess SVC entries.
VALERR and VALWARN Messages 2. If this condition is not desired, use the NMMGR utility to configure store and forward buffers in the NETXPORT.NI.NIname.PROTOCOL.IP screen, and validate the Network Transport again. ACTION: 1. More than one non-loopback network is configured, but no store and forward buffers have been configured in the NETXPORT.NI.NIname.PROTOCOL.IP screen.
VALERR and VALWARN Messages timer (or the TCP Connection Assurance timer) so that the X.25 timer has a greater value than the TCP timer. 1103 MESSAGE: SVCPATH HAS NO X.25 ADDRESS—THIS IS VALID ONLY FOR DDN. CAUSE: At least one SVCPATH entry does not have an X.25 address key configured. This configuration will work only if the link is connected to a DDN. ACTION: If the link is not connected to a DDN, make sure all SVCPATH entries have an address key configured under the path NETXPORT.NI.NIname.PROTOCOL.
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. 2 MESSAGE: Bad LINK ID. 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 CR, and call your Hewlett-Packard representative.
LAN, LAN/Console, Token Ring LAN Error Messages 7 MESSAGE: A call to IO_CONFIG_INT failed during driver initialization. CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative. 8 MESSAGE: A call to IO_DECONFIG_INT failed during driver shutdown. CAUSE: Unknown. Need more information.
LAN, LAN/Console, Token Ring LAN Error Messages 14 MESSAGE: Unable to send I/O Services message frame to another process. 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 CR, and call your Hewlett-Packard representative. 16 MESSAGE: LAN console is not supported.
LAN, LAN/Console, Token Ring LAN Error Messages 32 MESSAGE: Attempt to rendezvous with a link driver with SAP or SAP+XSAP or Ethernet Type already being used. 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 CR and call your Hewlett-Packard representative. 33 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. 40 MESSAGE: The Middle Plane is in wrong state. CAUSE: The Middle Plane state machine table is corrupted. ACTION: Write down the error information displayed on the console submit an CR, take a dump and call your Hewlett-Packard representative. 41 MESSAGE: Missing inbound pool in the rendezvous request message.
LAN, LAN/Console, Token Ring LAN Error Messages 50 MESSAGE: The NIO LAN/console card did not return to a ready state after a reset was issued. CAUSE: The problem is caused by bad NIO LAN/console hardware. ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card. 52 MESSAGE: The NIO LAN/console card register test failed during LAN/console card initialization. CAUSE: The problem is caused by bad NIO LAN/console hardware.
LAN, LAN/Console, Token Ring LAN Error Messages 58 MESSAGE: The NIO LAN/console card detects illegal bind request. CAUSE: The problem is caused by a link driver internal problem. ACTION: Write down the error information displayed on the console, submit an CR, 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. 63 MESSAGE: The NIO LAN/console card detects a bind request to already bound register. 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. 68 MESSAGE: The NIO LAN/console card reports that expected CCMD_LINK was not found. CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative. 69 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. 76 MESSAGE: The NIO LAN/console card detects a severe hardware error. CAUSE: Unknown. Need more information. ACTION: Your Hewlett-Packard representative must run diagnostics on the LAN/console card. 77 MESSAGE: The NIO LAN/console card detects a severe internal error. CAUSE: Unknown. Need more information.
LAN, LAN/Console, Token Ring LAN Error Messages of bytes were bigger than maximum LAN packet size. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative. 84 MESSAGE: The BDMARS expected more DMA data to be transferred than the host CCMD_IN or CCMD_OUT count requested. CAUSE: The NIO LAN/console card was prepared to send more data bytes to the host, but the host did not provide enough buffers.
LAN, LAN/Console, Token Ring LAN Error Messages 91 MESSAGE: The NIO LAN/console card detects unknown I/O command. CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative. 112 MESSAGE: The CIO bottom plane is unable to obtain buffer manager buffer. CAUSE: Buffers have not been freed or some other process has obtained buffers reserved for the driver. ACTION: Warmstart the system and correct the user programs.
LAN, LAN/Console, Token Ring LAN Error Messages 117 MESSAGE: The CIO LAN card detects a fatal backplane error. CAUSE: Unknown. Need more information. ACTION: Your Hewlett-Packard representative must run diagnostics on the CIO LAN card. 118 MESSAGE: The Identity Request to the CIO LAN card failed. CAUSE: Unknown. Need more information. ACTION: Your Hewlett-Packard representative must run diagnostics on the CIO LAN card. 119 MESSAGE: The CIO LAN card reports an invalid hardware ID.
LAN, LAN/Console, Token Ring LAN Error Messages 125 MESSAGE: The driver detects unknown option in the 802.2 control field of a test or xid packet. 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. 128 MESSAGE: The CIO LAN configuration request failed. CAUSE: Unknown. Need more information.
LAN, LAN/Console, Token Ring LAN Error Messages 144 MESSAGE: Dump request received when driver is dumping. CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative. 145 MESSAGE: Message received in invalid state. CAUSE: The link driver received an unexpected message. ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.
LAN, LAN/Console, Token Ring LAN Error Messages 151 MESSAGE: Unexpected timer event message. CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative. 152 MESSAGE: Unimplemented message received. CAUSE: The message descriptor is not known to the driver. ACTION: Call your Hewlett-Packard representative and explain what you are trying to do. 160 MESSAGE: Nil configuration pointer.
LAN, LAN/Console, Token Ring LAN Error Messages 228 MESSAGE: Could not open NMCONFIG.PUB.SYS file. 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 235 MESSAGE: A call to IO_UNCONFIG failed during driver deconfiguration. 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 CR, take a system dump, and call your Hewlett-Packard representative. 236 MESSAGE: The LAN card is used by another link. 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. 242 MESSAGE: Could not get Write Initiator label. CAUSE: Unknown. Need more information. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative. 243 MESSAGE: Could not release Write Initiator label. CAUSE: Unknown. Need more information.
LAN, LAN/Console, Token Ring LAN Error Messages 249 MESSAGE: Could not receive config reply message. CAUSE: An internal system ports problem has occurred. ACTION: Write down the error information displayed on the console and call your Hewlett-Packard representative. 250 MESSAGE: Timeout waiting for the config reply message. 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 HP-PB 100Base-T Error Messages 16 100VG-AnyLAN and HP-PB 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 HP-PB 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 HP-PB 100Base-T Error Messages SDI Generic Status Values SDI Generic Status Values 0 ($00) MESSAGE: No error, info only. CAUSE: None ACTION: None 1 ($01) MESSAGE: The driver detected an exception in hardware operation. 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 HP-PB 100Base-T Error Messages SDI Generic Status Values 7 ($07) MESSAGE: Inadequate resources available to satisfy a request. 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. 8 ($08) MESSAGE: An adapter card is not responding. CAUSE: The driver detects an exception in hardware operation.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Generic Status Values 46 ($2E) MESSAGE: Remote link has disconnected. 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. 47 ($2F) MESSAGE: Link disconnected, although remote has not acknowledged.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Generic Status Values Driver’s resources). ACTION: According to the subsystem. 85 ($55) MESSAGE: Resource deallocation error. CAUSE: For the error shutdown handling, all SAPs and all associated link stations are deallocated, and the driver is deconfigured. ACTION: None 86 ($56) MESSAGE: One or more still active resources were deallocated.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Generic Status Values ACTION: Fix the configuration file and try again. 126 ($7E) MESSAGE: Link type of the named link is not supported. CAUSE: The linktype that stored in the NMCONFIG file which associated with the Linkname in a Module Configurator call is unsupported. The particular driver is not configured. ACTION: Fix the Configuration file and try again. 127 ($7F) MESSAGE: An invalid subsystem open ID was specified.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Generic Status Values 161 ($A1) MESSAGE: A request was not accepted due to current state of the link. CAUSE: The requested message cannot be accepted because of the existing state of the link station. (example, A write event message will not be accepted if the link is in the disconnected, opening or closed state). ACTION: According to the subsystem. 201 ($C9) MESSAGE: A formatter error was detected.
100VG-AnyLAN and HP-PB 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 HP-PB 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 HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 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 HP-PB 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This event is informational. No action is required. 13 ($0D) MESSAGE: Powerfail detected. CAUSE: The driver was notified of a power failure by the I/O system, or detected all 1’s on a hardware register read, and, upon checking further, saw that its hardware I/O address space was disabled, indicating a powerfail had already occurred. ACTION: This event is informational. No action is required.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values time, see Appendix A , “Submitting a CR.” 18 ($12) MESSAGE: Cannot close NM logging. CAUSE: The link module configurator or deconfigurator attempted to close access to the NM logging facility, but encountered an error. ACTION: This is an informational warning that the logfile may still be open. Use of the :SWITCHNMLOG command should not be affected, however there may be a delay at system shutdown time.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This error is informational only. Probably the Network Dump Process was delayed by other system processing, such that it exceeded the time limit set by the driver. The resulting dump file may or may not be incomplete. A more serious driver problem has already occurred, after which the driver will now attempt to auto-reset and continue.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values transmission, on the assumption some extra quads will free up. 35 ($23) MESSAGE: Driver is out of card memory resources. CAUSE: The driver attempted to dequeue a card memory buffer entry from a specific queue, but the queue was empty. ACTION: None. This is an internal error used to detect the empty queue condition. In most cases, the driver already knows the queue is not empty, and does not check for this error.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 46 ($2E) MESSAGE: Link tracing is already enabled. CAUSE: The driver received a request to turn link tracing on when it was already on. ACTION: This event is informational. No action is required. An error reply was sent in response to the request. Trace was not started by this request this time, but it remains on. 47 ($2F) MESSAGE: Link tracing is already disabled.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values heavy DMA load, the HP-PB chip might encounter a timeout while trying to complete an HP-PB slave transaction, and post a fatal error. Try to reduce other bus activity by pausing applications. If the system has multiple HP-PB busses, move the card to a less active bus. If the problem persists, there may be a hardware problem with the HP-PB bus itself.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values perform a dump of all host context data structures and adapter card memory, then reset itself and continue. This error is not meaningful without the accompanying “Cause” status. Locate and decode that “Cause” to determine the next action to take (see sublocation 9470 discussion for more information). 57 ($39) MESSAGE: MII read error on adapter card.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 61 ($3D) MESSAGE: Adapter card produced an illegal interrupt. CAUSE: The link driver has received an interrupt from the card during normal operation, but the driver should have specifically disabled that interrupt at startup. ACTION: The driver will attempt to perform a dump of all host context data structures and adapter card memory, then reset itself and continue. Save the resulting NETDMP##.PUB.
100VG-AnyLAN and HP-PB 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 a CR.” 76 ($4C) MESSAGE: Cannot get ADA memory object.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values error and look it up also. If the problem happens every time, see Appendix A , “Submitting a CR.” 80 ($50) MESSAGE: Cannot send a port message. CAUSE: This is a generic error saying that the link driver, module configurator or deconfigurator, or other module of the link subsystem encountered an error when trying to send a port message. This error could be caused by the target module having been already shut down.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values matches the path where a supported 100VG-AnyLAN or HP-PB 100Base-T adapter card is installed in your computer backplane. If the path passes through bus converters, verify the SYSGEN configuration has entries for the higher-level bus converters leading to that path. If necessary, change NMCONFIG or contact your Hewlett-Packard Representative for assistance in determining paths or correcting bus hardware problems.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 90 ($5A) MESSAGE: Did not receive an expected port message. CAUSE: This is a generic error that during a link-open or some other operation by an upper level subsystem, link software sent a port message to the driver, then encountered an error while awaiting the correct reply message. ACTION: Severity and side effects of this error are dependent upon the purpose of the message that was not received.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values descriptive of the problem. This error is often seen as a result of previous errors from intrinsics, reply messages, or validity checks. ACTION: When this error occurs as a result of previous errors, it mainly serves as a way to track the sequence of the failure back to what was happening at the time. Check for those errors and look them up for an additional explanation of the problem.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 125 ($7D) MESSAGE: Driver has detected data corruption. CAUSE: A driver receive-frame DMA operation completed, but in doing a quick check of the DMA’ed data, the driver found all ones in the first 4 words, indicating some kind of driver/ adapter card bug has occurred. Probably the driver attempted to perform a DMA transfer which was not a 4-byte multiple in length. ACTION: This is a fatal error.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values packets, so operation of the system and applications may continue with only minimal degradation. Exhausting all receive resources would be a highly unusual condition. If all receive resources have really been exhausted, network load may be extremely high, and/or the HP-PB bus may be preventing frames from being returned to the card in a timely manner; incoming frames are probably now being dropped.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 147 ($93) MESSAGE: Open table full. Too many driver users. CAUSE: Too many subsystems are attempting to open the driver at the same time, or subsystems are shutting down without closing the driver. ACTION: Shut down any networking subsystems that are not currently needed and try again.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values about what kind of comm the driver was trying to send; check log data for that error and look it up also. Collect binary copies of all NETDMP##.PUB.SYS dump files on tape for analysis by Hewlett-Packard and see Appendix A , “Submitting a CR.” 152 ($98) MESSAGE: Driver initialization failed. CAUSE: While processing its very first startup message, the driver encountered a problem.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 161 ($A1) MESSAGE: Card did not go ready after hard reset. CAUSE: After performing a hard reset of the adapter card during startup, the HP-PB interface chip did not report “ready” status, or reported an error. ACTION: Replace the adapter card. If the same problem persists even after replacement with a known good card, contact Hewlett-Packard: your software could be out of date, but a patch may be available.
100VG-AnyLAN and HP-PB 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, try replacing the cable and/or adapter card. 170 ($AA) MESSAGE: Hub did not report link up within time allowed. CAUSE: During a 100VG-AnyLAN link connect attempt, the driver exchanged 24 training frames with the hub, but afterward the LINK signal still did not appear within the 4 ms time allowed.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 184 ($B8) MESSAGE: Hub reports access is disallowed for this link. CAUSE: The driver received a training frame from the hub with the “no access” bit set in the frame. The hub is disallowing access to this link. ACTION: The driver discarded this frame and sent another. However, it is likely the hub will report this in every frame.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 188 ($BC) MESSAGE: Autonegotiation reports link settings are incompatible with hub. CAUSE: If this error occurs, it is probably because the link has reported a remote fault. Usually this means the adapter card and the hub or switch to which it is connected, have failed to agree on a link speed and duplex setting acceptable to both.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values the file. Perform a :DSTAT ALL command and make sure the disk drive the file resides on is present and mounted. Make sure the file resides on Ldev 1. If not, use Fcopy and a file equation with a “;DEV=1” option to force a copy of the file onto Ldev 1. Perform a :SHOWPROC 1;TREE;SYSTEM command and verify an NMFILE process exists. If not, shut down and restart the system, and retry the operation.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values NMCONFIG file. Using NMMGR, verify the path LINK.linkname exists in the NMCONFIG file and is the exact same linkname which is now being started. Verify the “Data=Y” flag is set at the top of that LINK screen (meaning that ENTER has been pressed to save the configuration data there). If the link is being used with NS or DTS, use the VALIDATE function to validate the network configuration.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values verify it is a legal MPE filename. A group and account may need to be specified. Make sure the user starting the link has the necessary capabilities to create that file in the group and account specified. Check whether the system is low on disk space. Check whether too many NMTCnnnn.PUB.SYS trace data files already exist. Purge files as necessary to free up disk space, or add more disks.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values ACTION: There is a problem in the upper-layer protocol. Attempt to determine which application produced the error, then see Appendix A , “Submitting a CR.” 223 ($DF) MESSAGE: One or more bad bind parms passed by upper level protocol. CAUSE: This is a generic error, reported when the driver received a bind (rendezvous) from an upper layer protocol, but the parameters in the request were not satisfactory to the driver.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values legal rendezvous ID values for this driver, or the corresponding rendezvous table entry state indicated no bind had occurred or an unbind had already occurred. The protocol was supposed to pass a rendezvous ID value previously returned to it by the driver, when that protocol did a bind. The protocol may be trying to unbind twice, or unbind from the wrong link.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values binding. 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 HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 244 ($F4) MESSAGE: Error encountered while decoding an entry. CAUSE: The trace or log formatter encountered an entry having an unrecognized entry tag value. The formatter cannot decode entries of this type. ACTION: The formatter will attempt to print this entry in raw form. You may be trying to format a trace or log file taken on a different system that has newer software than the system you are formatting on.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values message (“Cause” = 32-bit status from the call to send_msg). ACTION: There may be a system problem, or another subsystem has already shut the driver down while this one was trying to start it. The open did not succeed. The module configurator cleaned up and returned an error to the subsystem. Retry the operation. If this does not help, try stopping all networks using the link, then retry.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 1100 CLAS0001 MESSAGE: (Varies) CAUSE: During a link-open operation by an upper level subsystem, the link module configurator sent configuration data to the driver, but the driver returned an error in the reply message (“Cause” is not used here). 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.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 1130 CLAS0001 MESSAGE: Adapter card found does not match software configuration. CAUSE: During a link-open operation by an upper level subsystem, the link module configurator found a supported adapter card at the path specified in NMCONFIG, but it was not the right type of card for the link being started. ACTION: Correct the network configuration or plug in the correct type of adapter card, and retry the operation.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values purchase additional software or install newer patches. Reinstall the link software or contact your Hewlett-Packard Representative for assistance. 1170 CLAS0001 MESSAGE: Cannot load a system routine.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 1400 CLAS0001 MESSAGE: Cannot open configuration file. CAUSE: During a link-open operation by an upper level subsystem, the link module configurator encountered an error while trying to open the configuration file (“Cause” = 32-bit status from the call to nmconfopen). ACTION: The module configurator cleaned up and returned an error to the subsystem. Verify an NMCONFIG.PUB.SYS file exists.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values ACTION: The module configurator cleaned up and returned an error to the subsystem. Using NMMGR, verify the path LINK.linkname exists in the NMCONFIG file and is either a 100VG-AnyLAN or HP-PB 100Base-T link type. If the subsystem being started is NS, verify the link type matches the NI type for the network being started.
100VG-AnyLAN and HP-PB 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 HP-PB 100Base-T link to enable tracing at startup. 1620 CLAS0001 MESSAGE: Cannot send a trace request. 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 HP-PB 100Base-T Error Messages SDI Driver Specific Status Values contains the multicast for 100VG-AnyLAN and HP-PB 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 a CR.” 1650 CLAS0001 MESSAGE: The link is already started.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values to send the port message (“Cause” = 32-bit status from the call to send_msg). ACTION: There may be a system problem, or another subsystem has already shut the driver down while this one was trying to close it. The driver did not receive the updated configuration data. The module deconfigurator reported an error, but attempted to continue with the close. If this happens every time, see Appendix A , “Submitting a CR.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values ACTION: None. This is an informational event only. A similar event was logged when the link was opened. 1820 CLAS0001 MESSAGE: Cannot stop tracing. CAUSE: During a link-close operation by an upper level subsystem, the link module deconfigurator encountered an error trying to disable driver tracing (“Cause” = 32-bit status from the call to sio_trace_req). This is an informational error that tracing was not disabled.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values or the system I/O configuration may have been altered. If this happens frequently, see Appendix A , “Submitting a CR.” 1920 CLAS0001 MESSAGE: Cannot delete from link table. CAUSE: During the final link-close operation by an upper level subsystem, the link module deconfigurator attempted to delete the link from the link table, but encountered an error (“Cause” = 32-bit status from the call to lsslktbldelete).
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 2030 CLAS0001 MESSAGE: Cannot send a port message. CAUSE: During final processing of a fatal driver error, the driver attempted a standard auto-reset instead of dying. However, its attempt to send a reset message to itself failed (“Cause” = 32-bit status returned by the call to send_msg). If this error is reported, it is because the driver has already encountered some other error.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 2120 CLAS0001 MESSAGE: Internal error while initiating a dump. Dump failed. CAUSE: During processing of a fatal driver error, the driver attempted a driver dump, but encountered an error while trying to get or reset a timer (“Cause” = 32-bit status returned by the call to vg_start_timer).
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values If you suspect a heavy load, you can try shutting some processes down, then restart the driver. Otherwise use Control-B at the console to halt the system, take a memory dump, and reboot. See Appendix A , “Submitting a CR.” 2240 CLAS0001 MESSAGE: Cannot reset a system timer.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values driver was unable to find an unused entry (“Cause” is not used here). ACTION: This fatal software error is only caused by a bug, since message port subqueue controls should have prevented the table from filling. After reporting this error, the driver will die, then will either attempt an auto-reset or else require a manual shutdown and restart. Most likely some subsystem has sent a message to an incorrect subqueue.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values operate if frames run out. ACTION: This is a fatal software error. After reporting this error, the driver will attempt a driver dump, then will auto-reset and attempt to continue. Typically followed by another error giving more information about what kind of comm the driver was trying to send; check log data for that error and look it up also. Collect binary copies of all NETDMP##.PUB.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values applications or subsystems, then retry link startup. If the problem persists, shut down the system to clear memory, then reboot but try starting the link earlier, before too many other applications get going. If still low on memory, you may need to add more memory hardware. First, however, Hewlett-Packard can try to determine if more memory would help, or if instead there is a bug.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 2860 CLAS0001 MESSAGE: Bad hardware ID or path. CAUSE: During initial driver startup, a supported 100VG-AnyLAN or HP-PB 100Base-T adapter card was not found at the hardware path specified in NMCONFIG. ACTION: The driver did not start up. Verify the path in NMCONFIG is correct and complete, and matches the path where a supported 100VG-AnyLAN or HP-PB 100Base-T adapter card is installed in the computer backplane.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values does not help, replace the adapter card. 2950 CLAS0001 MESSAGE 2: MII read error on adapter card. CAUSE: During a 100VG-AnyLAN link connect attempt, the driver attempted to request a training interval from the hub, but its read from an MII hardware register on the adapter card failed to return the proper acknowledgment bit. ACTION: The link did not connect. MII reads can be sensitive to software timing.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values ACTION: None. This error can 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.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values link (CAT-5 for HP-PB 100Base-T, CAT-3 or -5 for 100VG-AnyLAN). 3100 CLAS0002 MESSAGE: Link disconnected.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values the pending config request message, if any, logged this error, then died (“Cause” = 32-bit status giving the reason startup failed). ACTION: This event indicates a fatal driver software condition. May be preceded by other errors giving more information about the original failure, which may help you determine whether it was a hardware or software problem.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 3310 CLAS0001 MESSAGE: Configuration failed. CAUSE: During initial driver startup, the driver encountered an error during configuration, while attempting to request ADA memory from the MPE I/O system (“Cause” = 32-bit status returned by the call to vg_dvr_port_msg_exec). Probably a port message could not be sent.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values operation. If the problem persists, the driver may be broken; run the VGPBA diagnostic and attempt a Reset function. If the problem still persists, run VGPBA, attempt a Dump function, and save the resulting file (NETDMP##.PUB.SYS) for analysis by Hewlett-Packard. If the driver still does not become usable after this, use Control-B at the console to halt the system, take a memory dump, and reboot.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 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. 3550 CLAS0001 MESSAGE: A driver request failed.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values and current state: HP use only). 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 a CR.” 3670 CLAS0001 MESSAGE: Late dump-done message received. Dump took too long.
100VG-AnyLAN and HP-PB 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. 3790 CLAS0001 MESSAGE: A driver request failed. 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 HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 3910 CLAS0001 MESSAGE: Cannot get ADA memory object. 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 HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 4030 CLAS0001 MESSAGE: Bad message for current state. 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 HP-PB 100Base-T Error Messages SDI Driver Specific Status Values this log event means it is being ignored. 4130 CLAS0001 MESSAGE: A driver request failed. 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). Probably no comm frame was available.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values ACTION: If the operator already knows the driver is in the process of being closed, this error can be ignored. The driver attempted to send an error reply for the statistics request. The ISR may also be “dead” as a result of a serious previous error. A diagnostic reset action may clear this condition. 4150 CLAS0001 MESSAGE: Driver encountered a software problem.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values subsystem (“Cause” = 32-bit status returned by the call to vg_dvr_send_reply). 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. The subsystem’s access to the link was closed, but the subsystem did not get the reply; reaction to this situation is subsystem-dependent.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values reply to this request; if not, the session which sent it may hang. 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. 4360 CLAS0001 MESSAGE: Bad message for current state.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values ACTION: If the operator already knows the driver is in the process of being closed, this error can be ignored. The driver attempted to send an error reply for the diagnostic request. The ISR may also be “dead” as a result of a serious previous error. A diagnostic reset action may clear this condition. 4420 CLAS0001 MESSAGE: Bad message for current state.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values any messages having that descriptor (“Cause” = 32-bit value of the message descriptor field). ACTION: The driver took no action on the message, and dropped it. However, if the problem occurs frequently, your system may not be set up properly. The driver traces the message which it received. If you can repeat the problem, first enable link tracing.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 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 a CR.” If the problem persists, take a system memory dump immediately after the problem has occurred. 4820 CLAS0001 MESSAGE: General error trying to get a buffer.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 4910 CLAS0001 MESSAGE: Driver could not identify LAN controller on card. CAUSE: After initializing the PCI bus on the adapter card, the driver checked the ID of the LAN controller chip, but found it did not match any of the known ID’s expected (“Cause” = 32-bit chip ID obtained from the card). ACTION: Replace the adapter card. The link did not start.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values available. It is unlikely this would be caused by a system HP-PB bus hardware problem. 5030 CLAS0001 MESSAGE: Driver encountered a hardware problem. CAUSE: While attempting to alter the loopback mode during diagnostic testing, the driver read from the network command register on the LAN controller chip of the adapter card, but encountered an error.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 5150 CLAS0001 MESSAGE: Driver encountered a hardware problem. CAUSE: While attempting to alter 10Base-T loopback mode during diagnostic testing of a 100VG-AnyLAN adapter card, the driver read from a PHY control register in the LAN controller chip of the card, but encountered an error. Most likely the chip has failed, but a power failure may have occurred (“Cause” = 32-bit status returned by the call to vg_mii_read16).
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values If the problem persists, the system may be low on timers; try stopping some applications before retrying again. 5270 CLAS0001 MESSAGE: Driver encountered a software problem. CAUSE: During a 100VG-AnyLAN link training sequence, the driver found the PHY chip was not reset yet, and started to reset it again, but encountered an error while trying to get or reset a timer (“Cause” = 32-bit status from the call to vg_start_timer).
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 5360 CLAS0001 MESSAGE: Driver encountered a hardware problem. CAUSE: During a 100VG-AnyLAN link training sequence, after powering up the PHY chip, the driver encountered an error while trying to read the PHY ID (“Cause” = 32-bit status from the call to vg_isr_init_phy_id). If this error is reported, it is because the driver has already encountered some other error.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values read from the PHY status register on the PHY chip (“Cause” = 32-bit status from the call to vg_mii_read16). Most likely a powerfail has occurred. 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 a CR.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 5600 CLAS0001 MESSAGE: Driver encountered a software problem. CAUSE: During a 100VG-AnyLAN link training sequence, the driver received the expected test interrupt, 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 the test interrupt to arrive.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 5720 CLAS0001 MESSAGE: Driver encountered a hardware problem. CAUSE: During a 100VG-AnyLAN link training sequence, the driver attempted to signal a training failure, but encountered an error trying to read from the PHY control 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 HP-PB 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This is a fatal hardware error. Replace the adapter card. The driver cannot connect the link if the PHY will not reset. The driver will enter a “broken” state and await a manual shutdown by the operator. If you wish you may try running the VGPBA diagnostic and attempt a reset, however it is unlikely this will fix the problem. If the problem persists with a known good card, see Appendix A , “Submitting a CR.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 5930 CLAS0001 MESSAGE: Driver encountered a hardware problem. CAUSE: During a HP-PB 100Base-T connect sequence, the driver attempted to check for presence of a link signal, but 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 HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 6020 CLAS0001 MESSAGE: Hub did not report link up within time allowed. CAUSE: If this error occurs, it is because the link did not connect within 25 to 30 seconds after it was instructed to do so. ACTION: Verify that the cable is securely connected to the adapter card at one end, and to a 100Base-TX or 10Base-T hub at the other. Verify the cable is a correctly wired, Category-5 UTP cable.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 6110 CLAS0001 MESSAGE: Driver encountered a hardware problem. CAUSE: During a HP-PB 100Base-T connect sequence after the link came up, the driver attempted to check the final connect settings, but encountered an error trying to read from the autonegotiation advertisement 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 HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 6200 CLAS0001 MESSAGE: Driver encountered a hardware problem. CAUSE: During a HP-PB 100Base-T connect sequence, the driver attempted to adjust the duplex setting of the LAN controller chip, but encountered an error trying to read from the network command register on that chip (“Cause” = 32-bit status from the call to vg_dio_read8). Most likely a powerfail has occurred.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 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. 7040 CLAS0001 MESSAGE: Driver encountered a hardware problem.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 7130 CLAS0001 MESSAGE: Driver encountered a software problem. CAUSE: During a 10Base-T connect sequence on a 100VG-AnyLAN adapter card, 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).
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 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 a CR.” 7250 CLAS0001 MESSAGE: Driver encountered a hardware problem.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 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. 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.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 7490 CLAS0001 MESSAGE: Driver encountered a hardware problem. CAUSE: During a 10Base-T connect sequence on a 100VG-AnyLAN adapter card, when a timeout occurred instead of an interrupt, the driver attempted to check for presence of a link signal, but 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).
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values If a crossover cable is being used, make sure it is correctly wired, and that you have software version A00550B0 or later. Check the configuration of the hub or switch port to which the adapter card is connected. Adjust that configuration and, if necessary, use NMMGR to adjust the configuration of the link, so that something will match.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 7700 CLAS0001 MESSAGE: Driver encountered a hardware problem. CAUSE: While a 10Base-T link on a 100VG-AnyLAN adapter card 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 HP-PB 100Base-T Error Messages SDI Driver Specific Status Values Check the configuration of the hub or switch port to which the adapter card is connected. Adjust that configuration and, if necessary, use NMMGR to adjust the configuration of the link, so that something will match. If necessary, specify a forced speed and duplex setting, and disable autonegotiation, at both ends. 7850 CLAS0001 MESSAGE: Driver encountered a software problem.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 7940 CLAS0001 MESSAGE: Heartbeat timeout. Adapter card appears to be hung. CAUSE: The LAN Controller chip on the adapter card has failed to produce any interrupt from normal activity for over 5 seconds. It has also failed, for an additional 5 seconds, to respond to the driver’s inquiry by producing a test interrupt. The driver has decided the card is dead or hung (“Cause” is not used here).
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This informational error is typically preceded by another error message giving better information about the original cause; check log data for that error and look it up also. Depending on the cause of that error, you may decide that replacement of the adapter card is necessary. Since diagnostic testing is in progress, the driver should report the error, then attempt to continue.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values data for that error and look it up also. At this level, the error is just logged, then the driver will attempt to continue, if the lower level error was not already fatal. 8090 CLAS0001 MESSAGE: Driver encountered a software problem.
100VG-AnyLAN and HP-PB 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 HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 8270 CLAS0001 MESSAGE: One or more bad bind parms passed by upper level protocol. CAUSE: The driver received a bind (rendezvous) from an upper layer protocol module, but the specified length of the information block body was not the length expected (“Cause” = 32-bit value giving the bad length which was specified). ACTION: This problem most likely occurred while starting a new network subsystem.
100VG-AnyLAN and HP-PB 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. 8360 CLAS0001 MESSAGE: One or more bad bind parms passed by upper level protocol.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values protocol’s address (SAP), a lower-level routine reported an error, as described by the Message (“Cause” = 32-bit encoded value of the SAP being bound). Most likely either the address is already in the driver’s table, or the table is full. ACTION: This problem most likely occurred while starting a new network subsystem.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 8510 CLAS0001 MESSAGE: Driver encountered a software problem. CAUSE: While beginning a driver start or restart operation, the driver tried to set the heartbeat timer, but encountered an error (“Cause” = 32-bit status from the call to vg_start_timer). This timer was to be used to periodically awaken the driver so it could verify card health; the driver cannot start if a PHY timer cannot be started.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values Hewlett-Packard Representative for assistance. 8600 CLAS0001 MESSAGE: One or more bad unbind parms passed by upper level protocol. CAUSE: The driver received an unbind (separate) from an upper layer protocol module, but the driver’s corresponding rendezvous table entry state indicated no bind had occurred or an unbind had already occurred (“Cause” = 32-bit value giving the bad ID which was specified).
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 8690 CLAS0001 MESSAGE: Driver encountered a software problem. CAUSE: After completing a trace enable request, the driver’s ISR then encountered an error trying to notify the DVR module of the request completion (“Cause” = 32-bit status from the call to Vg_isr_copy_send_to_dvr). Probably no comm frame was available.
100VG-AnyLAN and HP-PB 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 a CR.” 8840 CLAS0001 MESSAGE: Bad message for current state.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 8930 CLAS0001 MESSAGE: Driver encountered a software problem. 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 HP-PB 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. 9050 CLAS0001 MESSAGE: An illegal bind ID was encountered.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values vg_send_msg). ACTION: This is an informational error only. The driver has incremented a statistic, logged the error, and will now attempt to free the receive buffer and continue. However, the protocol may not have received the inbound frame, therefore some applications could be hung. There is probably a problem in the upper layer protocol.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 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 a CR.” 9320 CLAS0001 MESSAGE: Powerfail detected.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values are probably now being dropped. Otherwise there may be a bug in the link driver. If the problem happens often, see Appendix A , “Submitting a CR.” 9440 CLAS0001 MESSAGE: Frame received when no queue entry was available. CAUSE: When processing an interrupt for a received diagnostic loopback data frame, the driver was not able to locate the adapter card data memory frame containing the data (“Cause” is not used here).
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values • Bit 18 is 1 if the controller was attempting to read from adapter card memory, 0 if it was writing. • Bits 7–0 contain an error code, as follows: — $01 = Bus master data parity error: replace hardware. — $02 = Bus address parity error: replace hardware. — $03 = Master abort: replace hardware first. If problem continues, contact Hewlett-Packard. — $04 = Target abort: replace hardware first.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values transceiver module in the switch if it has one. If this does not solve the problem, replace the adapter card. 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 a CR.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values ACTION: Replace the adapter card. If the problem continues, there may be a driver startup bug; see Appendix A , “Submitting a CR.” 9710 (None) MESSAGE: (None) CAUSE: 100VG-AnyLAN link training failed because, after the LAN Controller chip reported a training frame was sent, the driver tried to check if the frame was completely transferred out of adapter card memory, but detected a powerfail instead.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 9800 (None) MESSAGE: (None) CAUSE: 100VG-AnyLAN link training failed because, after the LAN Controller chip reported a status interrupt, the driver tried to read the network status register, but detected a powerfail instead. A power 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 HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 9920 (None) MESSAGE: (None) CAUSE: 100VG-AnyLAN link training failed because the LAN Controller chip reported a status interrupt, then when the driver tried to read the channel parameter register from the chip, a powerfail was detected instead. A hardware failure state was then signaled. ACTION: If a power failure has actually occurred, this error can be ignored; the driver should recover automatically.
100VG-AnyLAN and HP-PB 100Base-T Error Messages SDI Driver Specific Status Values 9980 CLAS0001 MESSAGE: Adapter card reported an HP-PB fatal error. CAUSE: The driver’s ISR module awoke to process a DVR request or an interrupt, but after reading status from the HP-PB interface chip on the adapter card, the driver discovered a fatal error bit had been set (“Cause” = 32-bit status value read from the chip: HP use only). ACTION: The driver already verified the bit was not set because of a power failure.
PCI 100Base-T Error Messages 17 PCI 100Base-T Error Messages The following error messages gives the meaning of the first 8 bits of 32-bit status values produced by the PCI 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.
PCI 100Base-T Error Messages SDI Generic Status Values SDI Generic Status Values 0 ($00) MESSAGE: No error, info only. CAUSE: None ACTION: None 1 ($01) MESSAGE: The driver detected an exception in hardware operation. 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.
PCI 100Base-T Error Messages SDI Generic Status Values 7 ($07) MESSAGE: Inadequate resources available to satisfy a request. 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. 8 ($08) MESSAGE: An adapter card is not responding. CAUSE: The driver detects an exception in hardware operation.
PCI 100Base-T Error Messages SDI Generic Status Values associated connections. ACTION: Disconnect all the associated connections and try again. 45 ($2D) MESSAGE: Link has lost its connection to the remote link. CAUSE: After the link has been established and both link stations are in open state, a link station detected an inoperative condition in either the remote link station or in the transmission medium (the recovery attempt has failed).
PCI 100Base-T Error Messages SDI Generic Status Values ACTION: According to the subsystem. 83 ($53) MESSAGE: Error in interface with Link Support Services. CAUSE: A module Configurator/Deconfigurator failed in calling Link Support Services (LSS) procedures. ACTION: According to the subsystem. 84 ($54) MESSAGE: Error in interface with Trace Services.
PCI 100Base-T Error Messages SDI Generic Status Values ACTION: According to the subsystem. 124 ($7C) MESSAGE: Link did not understand the optional parameters supplied. CAUSE: The Driver did not understand the optional parameter in the request message. ACTION: Check Driver ES and make sure you talk to the right Driver. 125 ($7D) MESSAGE: Link type of the named link is not supported. CAUSE: The Linkname passed by the Module Configuration Call or Deconfigurator Call is invalid.
PCI 100Base-T Error Messages SDI Generic Status Values 132 ($84) MESSAGE: An invalid or redundant protocol SAP address was specified. CAUSE: For the Rendezvous Request, the LSAP value is the NULL or Global SAP. For the connect request, this error indicates that this SAP already has a link to the specified RSAP and destination address combination, or the remote SAP specified was the null SAP, global SAP, or a group SAP. ACTION: Use an acceptable SAP and Destination Address.
PCI 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 PCI 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.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This event is informational. No action is needed unless the message appears frequently while the link is up, indicating 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 UTP 100Base-T). 7 ($07) MESSAGE: Link disconnected.
PCI 100Base-T Error Messages SDI Driver Specific Status Values following an error. ACTION: None required, this status is informational only. An upper layer protocol previously asked to be notified if a reset occurred in the link driver, and such a reset has occurred, possibly as a result of running diagnostics. However, an earlier error may have also occurred. 13 ($0D) MESSAGE: Powerfail detected.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 18 ($12) MESSAGE: Cannot close NM logging. CAUSE: The link module configurator or deconfigurator attempted to close access to the NM logging facility, but encountered an error. ACTION: This is an informational warning that the logfile may still be open. Use of the :SWITCHNMLOG command should not be affected, however there may be a delay at system shutdown time. If this happens every time, see Appendix A , “Submitting a CR.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 26 ($1A) MESSAGE: Internal error while initiating a dump. Dump failed. CAUSE: During processing of some other fatal driver error, the driver attempted a driver dump, but encountered an error. 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.
PCI 100Base-T Error Messages SDI Driver Specific Status Values suppressed. No attempt is made to determine whether the dumps are duplicates of the same problem. The driver did not dump, but will still attempt to auto-reset itself, up to a total of 12 times or more. There is apparently something wrong, since many driver dumps are occurring. Collect binary copies of all dump files (NETDMP##.PUB.SYS) on tape for analysis by Hewlett-Packard and see Appendix A , “Submitting a CR.
PCI 100Base-T Error Messages SDI Driver Specific Status Values protocol, the driver found that the rendezvous table entry specified in the buffer was not in the proper state. ACTION: This is an internal error which detects a normal race condition. Probably the protocol separated from the driver while a frame destined for it was in motion. The frame was not delivered, and the buffer was silently released. No action is required. 46 ($2E) MESSAGE: Link tracing is already enabled.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: The adapter card or system I/O hardware may have failed. Contact your Hewlett-Packard Representative for hardware assistance. 54 ($36) MESSAGE: Unable to read from adapter card PCI configuration space.
PCI 100Base-T Error Messages SDI Driver Specific Status Values adapter card, but the read failed to return one of the necessary acknowledgment bits. This indicates good data was not returned. 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.
PCI 100Base-T Error Messages SDI Driver Specific Status Values Appendix A , “Submitting a CR.” 76 ($4C) MESSAGE: Cannot get ADA memory object. 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. ACTION: Probably the amount of frozen memory on the system is very high; if you have the GLANCE tool you can try to check memory usage.
PCI 100Base-T Error Messages SDI Driver Specific Status Values and see Appendix A , “Submitting a CR.” 81 ($51) MESSAGE: Error from upper layer protocol read completor. 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.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 87 ($57) MESSAGE: Cannot load a system routine. 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.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: The driver will attempt to continue, and it will attempt to log the error unless a system abort occurs first. If the problem occurs repeatedly, too many system I/O resources may become lost; take a memory dump and see Appendix A , “Submitting a CR.” 95 ($5F) MESSAGE: Could not allocate or reassign an I/O virtual address.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: Check the log file for additional errors related to a specific sublocation in the code, and look up those sublocation errors for more specific information, see Appendix A , “Submitting a CR.” 101 ($65) MESSAGE: Link common reported a protocol unbind problem. CAUSE: Varies. The driver encountered an error condition when attempting to unbind from an upper layer protocol.
PCI 100Base-T Error Messages SDI Driver Specific Status Values “Submitting a CR.” 108 ($6C) MESSAGE: Cannot delete a buffer pool. CAUSE: During a link-close operation by an upper level subsystem, the link module deconfigurator encountered an error while trying to delete an outbound buffer pool or control buffer 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.
PCI 100Base-T Error Messages SDI Driver Specific Status Values all timers due to heavy system load, or by system software either failing to release timers, or having some other bug. ACTION: This is a fatal software error. The number of available timers is not configurable, and the driver cannot operate reliably without the ability to monitor the card. The same problem will likely prevent attempts to get other required timers also.
PCI 100Base-T Error Messages SDI Driver Specific Status Values error, the driver will die, then will either attempt an auto-reset or else require a manual shutdown and restart. If the problem persists, take a link trace of the problem, then see Appendix A , “Submitting a CR.” 130 ($82) MESSAGE: Cannot read current multicast list.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 150 ($96) MESSAGE: Pending message table full. Driver not finishing fast enough. CAUSE: While processing a new blocking request (requiring a driver exit and later reply) and scanning a table in which to save the request, the driver found an unused entry, but an entry counter indicated the table was full. ACTION: This fatal software error is only caused by a bug, because the in use flags and counters should match.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This is a fatal software error. It might be caused by a bad adapter card, by having too many driver users, by a heavy CPU load, or by attempting to operate the network subsystem or tool which started the link at too low of a CPU process priority, causing a timeout.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This error should not occur. If it happens frequently, see Appendix A , “Submitting a CR.” 183 ($B7) MESSAGE: Driver bug prevents link training. File CR. CAUSE: During an attempt to establish the proper stack context within which to begin 100VG-AnyLAN link training, the driver tried repeatedly to run without the ISR underneath it, but failed to even after 4 retries. ACTION: Shut down the link and restart it.
PCI 100Base-T Error Messages SDI Driver Specific Status Values that the user starting the link has the necessary access rights to open the file. Perform a :DSTAT ALL command and make sure the disk drive the file resides on is present and mounted. Make sure the file resides on Ldev 1. If not, use Fcopy and a file equation with a “;DEV=1” option to force a copy of the file onto Ldev 1. Perform a :SHOWPROC 1;TREE;SYSTEM command and verify an NMFILE process exists.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: If the link is already started, LSS tries to read the link type from its own link table. Otherwise, it tries to read it from the NMCONFIG file. Using NMMGR, verify the path LINK.linkname exists in the NMCONFIG file and is the exact same linkname which is now being started. Verify the “Data=Y” flag is set at the top of that LINK screen (meaning that ENTER has been pressed to save the configuration data there).
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: Using NMMGR, check if a filename was configured. If so, verify it is a legal MPE filename. A group and account may need to be specified. Make sure the user starting the link has the necessary capabilities to create that file in the group and account specified. Check whether the system is low on disk space. Check whether too many NMTCnnnn.PUB.SYS trace data files already exist.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: There is a problem in the upper-layer protocol. Attempt to determine which application produced the error, then see Appendix A , “Submitting a CR.” 223 ($DF) MESSAGE: One or more bad bind parms passed by upper level protocol. CAUSE: This is a generic error, reported when the driver received a bind (rendezvous) from an upper layer protocol, but the parameters in the request were not satisfactory to the driver.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: All such errors are caused by bugs in the upper layer protocol or mismatched software revisions. Attempt to determine which protocol was trying to send, then see Appendix A , “Submitting a CR.” 239 ($EE) MESSAGE: Bad message for current state.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 243 ($F3) MESSAGE: Unknown data version. CAUSE: The trace or log formatter attempted to decode a record header to obtain general information such as link type and link name, but on inspection found that the version of that data was not supported by his formatter, thus no other fields could be decoded. ACTION: The formatter will attempt to print this record in the raw form.
PCI 100Base-T Error Messages SDI Driver Specific Status Values Logging Sublocation Codes The following are the logging sublocation codes reported by the 100Base-T link drivers, including sublocation code, log class, log message, and the appropriate cause of and action to take for each. For meanings of 32-bit status values generated by the driver, refer to the sections on status values. 1020 CLAS0001 MESSAGE: Cannot freeze a memory area.
PCI 100Base-T Error Messages SDI Driver Specific Status Values Hewlett-Packard what actions the driver took. See Appendix A , “Submitting a CR.” 1080 CLAS0001 MESSAGE: Did not receive an expected port message. CAUSE: During a link-open operation by an upper level subsystem, the link module configurator sent configuration data to the driver, then encountered an error while awaiting the correct reply message (“Cause” = 32-bit status from the call to extend_receive).
PCI 100Base-T Error Messages SDI Driver Specific Status Values 1120 CLAS0001 MESSAGE: Bad hardware ID or path. CAUSE: During a link-open operation by an upper level subsystem, the link module configurator did not find a supported 100Base-T adapter card at the hardware path specified in NMCONFIG. ACTION: The module configurator cleaned up and returned an error to the subsystem.
PCI 100Base-T Error Messages SDI Driver Specific Status Values assistance. 1170 CLAS0001 MESSAGE: Cannot load a system routine. 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.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: The module configurator cleaned up and returned an error to the subsystem. Verify the path in NMCONFIG is correct and complete, and matches the path where a supported 100Base-T adapter card is installed in your computer backplane. If the path passes through bus converters, verify the SYSGEN configuration has entries for the higher-level bus converters leading to that path.
PCI 100Base-T Error Messages SDI Driver Specific Status Values NMCONFIG file and is the exact same linkname which is now being started. Verify the “Data=Y” flag is set at the top of that LINK screen (meaning that ENTER has been pressed to save the configuration data 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. 1440 CLAS0001 MESSAGE: Cannot validate configuration file.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This is an informational error that tracing was not started. The link came up, but the error was returned to the upper level subsystem, which may decide to shut the link back down again. Using NMMGR, check if a filename was configured. If so, verify it is a legal MPE filename. A group and account may need to be specified.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 1640 CLAS0001 MESSAGE: Cannot read current multicast list. CAUSE: During a link-open operation by an upper level subsystem, the link module configurator tried to read the current list of multicast addresses produced by the subsystem, but encountered an error on the read (“Cause” = 32-bit status from the call to ieee_multicast_read). ACTION: The module configurator cleaned up and returned an error to the subsystem. Run NMMAINT.PUB.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: The system may be low on available memory. Try closing any unnecessary applications or sessions and retry the operation. The driver did not receive the updated configuration data. The module deconfigurator attempted to continue with the close. If this happens every time, see Appendix A , “Submitting a CR.” 1720 CLAS0001 MESSAGE: Cannot send a port message.
PCI 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 module deconfigurator reported an error, but attempted to continue with the close. If this happens every time, see Appendix A , “Submitting a CR.” 1800 CLAS0001 MESSAGE: Subsystem is closing link.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 1920 CLAS0001 MESSAGE: Cannot delete from link table. CAUSE: During the final link-close operation by an upper level subsystem, the link module deconfigurator attempted to delete the link from the link table, but encountered an error (“Cause” = 32-bit status from the call to lsslktbldelete). ACTION: The module deconfigurator reported an error, but attempted to continue with the close. Network management services may have been shut down.
PCI 100Base-T Error Messages SDI Driver Specific Status Values the system, take a memory dump, and reboot. See Appendix A , “Submitting a CR.” 2230 CLAS0001 MESSAGE: Internal error while initiating a dump. Dump failed. CAUSE: While processing a request from an upper level diagnostic took, the dump surrogate for the PCI 100Base-T driver encountered an error. Additional messages may have been directed to the console by the dump surrogate process which provide more detail about the error.
PCI 100Base-T Error Messages SDI Driver Specific Status Values the problem happens every time, see Appendix A , “Submitting a CR.” 2600 CLAS0001 MESSAGE: Cannot send a port message. CAUSE: While notifying upper level subsystems that the driver detected a serious error, powerfail, or reset, an attempt to send an asynchronous event message to one of those subsystems failed (“Cause” = 32-bit status returned by the call to send_msg).
PCI 100Base-T Error Messages SDI Driver Specific Status Values on tape for analysis by Hewlett-Packard and see Appendix A , “Submitting a CR.” 2690 CLAS0001 MESSAGE: Internal error while initiating a dump. Dump failed. CAUSE: During processing of a fatal driver error, the driver attempted a driver dump, but encountered an error while trying to get or reset a timer (“Cause” = 32-bit status returned by the call to lnk_timer_start).
PCI 100Base-T Error Messages SDI Driver Specific Status Values configured. Although the driver may attempt to continue using the previously read multicast address list, the failure to allocate a data buffer and send a new setup frame to the PCI 100Base-T card could result in some network services/upper layer protocols (ULPs) not operating properly (data frames intended for those ULPs may not be recognized by the 100Base-T card).
PCI 100Base-T Error Messages SDI Driver Specific Status Values 3070 CLAS0003 MESSAGE: Pending message table full. Driver not finishing fast enough. CAUSE: While processing a new blocking request (requiring a driver exit and later reply) and scanning a table in which to save the request, the driver was unable to find an unused entry (“Cause” is not used here). ACTION: This fatal software error is only caused by a bug, since message port subqueue controls should have prevented the table from filling.
PCI 100Base-T Error Messages SDI Driver Specific Status Values “Submitting a CR.” ACTION: This fatal software error is only caused by a bug, since message port subqueue controls should have prevented the table from filling. After reporting this error, the driver will die, then will either attempt an auto-reset or else require a manual shutdown and restart. Most likely some subsystem has sent a message to an incorrect subqueue.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 3220 CLAS0001 MESSAGE: (Varies) CAUSE: When preparing to send a setup frame to the PCI 100Base-T card, the DVR was unable to reserve an available transmit descriptor from the descriptor ring. This could be a temporary bottleneck condition because of heavy data traffic on the network, or it could indicate an internal problem in the driver or with the PCI 100Base-T card. ACTION: No action is immediately needed.
PCI 100Base-T Error Messages SDI Driver Specific Status Values obtain the proper virtual address mapping for the data (“Cause” = 32-bit status returned by the call to Lnk_load_io_addr_for_virt). ACTION: No immediate action is required. This could be a temporary condition caused by heavy system load and I/O resource contention. The driver will continue operating and will try the transmit operation again periodically until the required system resources are available.
PCI 100Base-T Error Messages SDI Driver Specific Status Values The problem can be caused either by lack of memory or by a bug. If you suspect high memory usage and have the GLANCE tool, run it and check system memory usage. If usage is high, try closing some applications or subsystems, then retry link startup. If the problem persists, shut down the system to clear memory, then reboot but try starting the link earlier, before too many other applications get going.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 3550 CLAS0001 MESSAGE: Driver is shutting down. CAUSE: During initial driver startup, a supported 100Base-T adapter card was not found at the hardware path specified in NMCONFIG. ACTION: The driver did not start up. Verify the path in NMCONFIG is correct and complete, and matches the path were a supported 100Base-T adapter card is installed in the computer backplane.
PCI 100Base-T Error Messages SDI Driver Specific Status Values request this time, but it remains off. 3870 CLAS0001 MESSAGE: A driver request failed. 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 pbt_dvr_save_msg).
PCI 100Base-T Error Messages SDI Driver Specific Status Values 3960 CLAS0001 MESSAGE: Bad message for current state. 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.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 4050 CLAS0001 MESSAGE: Driver encountered a software problem. 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.
PCI 100Base-T Error Messages SDI Driver Specific Status Values with the system software installation; the software may need to be reinstalled, or additional software patches may be required, see Appendix A , “Submitting a CR,” or contact your Hewlett-Packard Representative to verify you have the required level of software installed. 4170 CLAS0001 MESSAGE: Driver encountered a software problem.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 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). 4260 CLAS0003 MESSAGE: Driver is starting adapter card.
PCI 100Base-T Error Messages SDI Driver Specific Status Values clears the problem. 4350 CLAS0001 MESSAGE: Configuration failed. CAUSE: During initial driver startup, the driver encountered an error during configuration (“Cause” = 32-bit status returned by the call to pbt_dvr_port_msg_exec). Probably there are already too many opens against the driver.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 4470 CLAS0001 MESSAGE: Configuration failed. 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 pbt_dvr_send_reply). Probably a port message could not be sent. ACTION: The driver allows 11 simultaneous opens. The open attempt by the additional subsystem failed.
PCI 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 for that error and look it up also, for more actions to take. The driver will attempt to send an error reply for the startup request. It then enters a “broken” state and awaits a shutdown, which the module configurator should attempt automatically. 4620 CLAS0001 MESSAGE: Driver initialization failed.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 4740 CLAS0001 MESSAGE: Cannot send a port message. CAUSE: The driver was unable to successfully unbind from its lower manager. Probably an underlying call to send_msg failed. ACTION: No action is required; this is an informational message. This error may be preceded by other errors in the log file giving a more specific reason for the failure. Check the log data and look up additional errors for more possible actions.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 4860 CLAS0001 MESSAGE: Cannot initiate a dump. Already dumping. CAUSE: A user attempted to force a driver dump while a previous driver dump was still occurring (“Cause” = 32-bit status saying a driver dump is starting). ACTION: A dump of your problem is already being produced. Wait a minute or two for the dump to finish. Forward the resulting NETDMP##.PUB.SYS to Hewlett-Packard for analysis if necessary, and see Appendix A , “Submitting a CR.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ignored. Otherwise, the I/O system may be confused. Either way, some memory may have been lost. The driver will drop this message without further action. If the problem occurs frequently, see Appendix A , “Submitting a CR.” 5010 CLAS0001 MESSAGE: Cannot release ADA memory object.
PCI 100Base-T Error Messages SDI Driver Specific Status Values problem happens every time the same subsystem is closed, submit an CR against that subsystem, describing the problem; see Appendix A , “Submitting a CR.” 5130 CLAS0001 MESSAGE: Cannot send a port message. 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 pbt_dvr_send_reply).
PCI 100Base-T Error Messages SDI Driver Specific Status Values be possible to continue. 5250 CLAS0001 MESSAGE: Driver received an unknown port message. CAUSE: Some module on the system has sent the driver a message having an unknown message descriptor. The driver does not implement any messages having that descriptor (“Cause” = 32-bit value of the message descriptor field). ACTION: The driver took no action on the message, and dropped it.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 5710 CLAS0001 MESSAGE: Cannot send a port message. CAUSE: During ISR processing, an attempt by the ISR to send a reply to a previously received message failed (“Cause” = 32-bit status returned by the call to send_msg). ACTION: This error is likely an indication of a more serious system software problem, and may be followed by a system abort. Probably all message frames have been exhausted by some module running on the system.
PCI 100Base-T Error Messages SDI Driver Specific Status Values the descriptor ring should be in a newly initialized state. ACTION: The driver did not start up, though it may attempt an auto-reset. Check to see if the driver was able to generate a dump file (NETDMP##.PUB.SYS) file, and send the file to Hewlett-Packard for analysis; see Appendix A , “Submitting a CR.” 5830 CLAS0001 MESSAGE: Driver has detected data corruption.
PCI 100Base-T Error Messages SDI Driver Specific Status Values auto-reset. This error could indicate a problem with the PCI 100Base-T adapter card. Check all connections, make sure the card is properly seated in the PCI slot, and try to restart the link. If the problem persists, try replacing the card. 5950 CLAS0001 MESSAGE: EEPROM read error on adapter card.
PCI 100Base-T Error Messages SDI Driver Specific Status Values different slot, may not be making proper contact with the PCI backplane, or may not be responding. If the I/O slot has a power indicator, verify it is on. Reseat the board, and if necessary call your Hewlett-Packard representative for hardware assistance. If the problem persists, the adapter card may be bad; try replacing the card. 6070 CLAS0001 MESSAGE: Unable to read from adapter card PCI configuration space.
PCI 100Base-T Error Messages SDI Driver Specific Status Values configuration space, but the I/O system reported an error. (“Cause” = 32-bit status returned from io_pci_cfg_write_bit32). ACTION: The adapter card may have been removed, moved to a different slot, may not be making proper contact with the PCI backplane, or may not be responding. If the I/O slot has a power indicator, verify it is on. Reseat the board, and if necessary call your Hewlett-Packard representative for hardware assistance.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: The driver may have become unusable and may try to auto-reset. If necessary, stop and restart the link manually. If the problem persists, the PHY chip may have gone bad; try replacing the PCI 100Base-T adapter card. 6480 CLAS0001 MESSAGE: Driver encountered a software problem.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: The driver may become unusable or may try and auto-reset. If necessary, stop and restart the link manually. Check for any driver dump files (NETDMP##.PUB.SYS) and if present, send to Hewlett-Packard for analysis; see Appendix A , “Submitting a CR.” 6630 CLAS0001 MESSAGE: Driver detected a hardware problem.
PCI 100Base-T Error Messages SDI Driver Specific Status Values reset a timer (“Cause” = 32-bit status from the call to lnk_timer_start). 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. If this error is reported, it is because the driver has already encountered some other error.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: The driver may have become unusable and may try to auto-reset. If necessary, stop and restart the link manually. If the problem persists, the PHY chip may have gone bad; try replacing the PCI 100Base-T adapter card. 6870 CLAS0001 MESSAGE: Driver encountered a hardware problem. CAUSE: While the ISR was attempting perform autonegotiation, a read of the PHY’s ANLPAR register failed.
PCI 100Base-T Error Messages SDI Driver Specific Status Values card, but received an error. (“Cause” = 32-bit status from pbt_isr_stop_rx). Additional errors may have been logged with more information about the failure. ACTION: The driver may become unusable or attempt an auto-reset. If the driver appears to hang, try to shutdown the network manually and then restart it. Most likely, once the reset is complete and the driver has “reinitialized” the hardware (card), the driver can resume operating normally.
PCI 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. 7050 CLAS0001 MESSAGE: Driver encountered a hardware problem.
PCI 100Base-T Error Messages SDI Driver Specific Status Values attempt a reset, however it is unlikely this will fix the problem. If the problem persists with a known-good card, see Appendix A , “Submitting a CR.” 7140 CLAS0001 MESSAGE: Driver encountered a software problem. CAUSE: During a 100Base-T connect sequence, the driver attempted to power up the PHY, but encountered an error while trying to get or reset a timer (“Cause” = 32-bit status from the call to lnk_timer_start).
PCI 100Base-T Error Messages SDI Driver Specific Status Values 7230 CLAS0001 MESSAGE: Driver encountered a hardware problem. CAUSE: During a 100Base-T connect sequence, the driver attempted to check for presence of a link signal, but encountered an error trying to read from the generic status register on the PHY chip (“Cause” = 32-bit status from the call to pbt_mii_read16). ACTION: If an interruption in power has occurred, this error can be ignored; the driver should recover automatically.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 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. If the problem persists, the system may be low on timers; try stopping some applications before retrying again.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 7470 CLAS0001 MESSAGE: Driver encountered a hardware problem. CAUSE: While the ISR was attempting perform autonegotiation, a read of the PHY’s ANLPAR register failed. ACTION: The driver may have become unusable and may try to auto-reset. If necessary, stop and restart the link manually. If the problem persists, the PHY chip may have gone bad; try replacing the PCI 100Base-T adapter card.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 7610 CLAS0001 MESSAGE: Unimplemented operation attempted. CAUSE: While attempting to enable a loopback mode at the request of a diagnostic tool, the driver detected that the specified mode of looback support is not available on the PHY. ACTION: Not all PHY chips support all loopback modes; make sure that the proper diagnostic request was issued, and that the driver supports the operation requested.
PCI 100Base-T Error Messages SDI Driver Specific Status Values restart it. Most likely, once the reset is complete and the driver has “reinitalized” the hardware (card), the driver can resume operating normally. If the problem persists, it may indicate a bad adapter card; try replacing the card. 7710 CLAS0001 MESSAGE: Driver encountered a hardware problem.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 7820 CLAS0001 MESSAGE: Driver encountered a software problem. CAUSE: After attempting to connect the link, the driver’s ISR module determined the link did come up, then encountered an error trying to notify the DVR module of the connect (“Cause” = 32-bit status from the call to pbt_isr_copy_send_to_dvr). Probably no comm frame was available.
PCI 100Base-T Error Messages SDI Driver Specific Status Values that error also, for more actions to take. If a power failure has occurred, this error may be ignored; the driver will soon attempt to recover. Otherwise, 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. 7890 CLAS0001 MESSAGE: Driver encountered a software problem.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 7980 CLAS0001 MESSAGE: Driver encountered a software problem. CAUSE: The driver was in the middle of a periodic check of whether the card is still healthy, but encountered an error while trying to get or reset a timer (“Cause” = 32-bit status from the call to lnk_timer_start).
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This informational error is typically preceded by another error message giving better information about the original cause; check log data for that error and look it up also. At this level, the error is just logged, then the driver will attempt to continue, if the lower level error was not already fatal. 8100 CLAS0001 MESSAGE: Driver encountered a software problem.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 8360 CLAS0001 MESSAGE: Driver encountered a software problem. CAUSE: While processing a restart request, the ISR attempted to stop the previously enabled heartbeat timer, but was returned an error (“Cause” = 32-bit status from lnk_timer_stop). ACTION: The restart can not be completed if the driver can not successfully reinitialize the heartbeat timer. The driver may do an MESSAGE: auto-reset.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 8600 CLAS0001 MESSAGE: One or more bad bind parms passed by upper level protocol. CAUSE: The driver received a bind (rendezvous) from an upper layer protocol module, but the specified SDI address family was not one of the values supported by the driver (“Cause” = 32-bit value giving the bad address family which was specified). ACTION: This problem most likely occurred while starting a new network subsystem.
PCI 100Base-T Error Messages SDI Driver Specific Status Values software patches; contact your Hewlett-Packard Representative for assistance. 8690 CLAS0003 MESSAGE: Subsystem is binding to link driver. CAUSE: An upper-layer protocol has successfully bound (rendezvoused) to the link driver (“Addr” = 32-bit encoded protocol address (SAP) value for this protocol module). Being bound means the driver can now route incoming data frames to this protocol. ACTION: None. This is an informational message only.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 8810 CLAS0001 MESSAGE: Driver received an unknown port message. CAUSE: The driver received a port message which it does not implement, or containing a function code which it does not implement (“Cause” = 32-bit ISR state machine input event tag value (Hewlett-Packard use only). ACTION: This is an informational error only. If this error occurred as part of a driver reset operation, it may be ignored.
PCI 100Base-T Error Messages SDI Driver Specific Status Values register (data field) from the adapter card’s PCI configuration space. (“Cause” = 32-bit status returned from io_pci-cfg_read_bit32). ACTION: The adapter card may have been removed, moved to a different slot, may not be making proper contact with the PCI backplane, or may not be responding. If the I/O slot has a power indicator, verify it is on. Reseat the board, and if necessary call your Hewlett-Packard representative for hardware assistance.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 9390 CLAS0001 MESSAGE: Internal driver error. CAUSE: While processing a received frame, the ISR detected an unsupported packet format. (“Cause” = 32-bit status returned from Lnk_recv_strip_hdr). Because this should have been caught during the rendezvous with the upper level system (SAP), this is an unexpected error condition. ACTION: This is an informational error only.
PCI 100Base-T Error Messages SDI Driver Specific Status Values reproduce the problem, then stop link tracing and save the resulting NMTC####.PUB.SYS file for analysis by Hewlett-Packard, and see Appendix A , “Submitting a CR.” 9480 CLAS0001 MESSAGE: Cannot send a port message. 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 send_msg).
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This problem most likely occurred while diagnosing some previous problem. It an informational error only, and the driver will log it and attempt to continue. If this happens frequently, see Appendix A , “Submitting a CR.” 9630 CLAS0001 MESSAGE: General buffer manager error encountered.
PCI 100Base-T Error Messages SDI Driver Specific Status Values ACTION: This error is informational. The driver will continue to shutdown. However, if the error persists, there could be data corruption in the driver or the I/O system. Depending on how frequently the error is seen, or if other similar errors are noted, this may require a system dump file to diagnose; see Appendix A , “Submitting a CR.” 9780 CLAS0001 MESSAGE: Could not unmap and I/O virtual address.
PCI 100Base-T Error Messages SDI Driver Specific Status Values 9840 CLAS0001 MESSAGE: Driver encountered a software problem. CAUSE: While processing a receive completion interrupt from the adapter card, the ISR encountered an error (“Cause” = 32-bit status from Pbt_isr_receive_frame). ACTION: This error is informational; if possible the driver will log the error and continue. There may be additional error information and messages logged which provides more information about the error.
PCI LAPBMUX Link Error Messages 18 PCI LAPBMUX Link Error Messages The following error messages gives the meaning of the first 8 bits of 32-bit status values produced by the PCI LAPBMUX 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.
PCI LAPBMUX Link Error Messages SDI Generic Status Values SDI Generic Status Values 0 ($00) MESSAGE: No error, info only. CAUSE: None ACTION: None 1 ($01) MESSAGE: The driver detected an exception in hardware operation. 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.
PCI LAPBMUX Link Error Messages SDI Generic Status Values 7 ($07) MESSAGE: Inadequate resources available to satisfy a request. 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. 8 ($08) MESSAGE: An adapter card is not responding. CAUSE: The driver detects an exception in hardware operation.
PCI LAPBMUX Link Error Messages SDI Generic Status Values 46 ($2E) MESSAGE: Remote link has disconnected. 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. 47 ($2F) MESSAGE: Link disconnected, although remote has not acknowledged.
PCI LAPBMUX Link Error Messages SDI Generic Status Values 85 ($55) MESSAGE: Resource deallocation error. CAUSE: For the error shutdown handling, all SAPs and all associated link stations are deallocated, and the driver is deconfigured. ACTION: None 86 ($56) MESSAGE: One or more still active resources were deallocated. CAUSE: For the error shutdown handling, all SAPs and all associated link stations are deallocated, and the driver is deconfigured. ACTION: None 87 ($57) MESSAGE: Link is already active.
PCI LAPBMUX Link Error Messages SDI Generic Status Values ACTION: Make the appropriate changes and reissue the request. 129 ($81) MESSAGE: An invalid connection ID was specified. CAUSE: The requested Connection ID does not exist. ACTION: Make the appropriate changes and reissue the request. 130 ($82) MESSAGE: Link did not understand the specified address family. CAUSE: The Driver detected an error in the address family in the request message. ACTION: Fix the configuration file and then try again.
PCI LAPBMUX Link 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 WAN ACC Sync MUX 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.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values disconnected, or on a link reconnect following a hub retrain, severe line hit, power failure, or other recoverable error. ACTION: This event is informational. No action is needed unless the message appears frequently while the link is up, indicating possible cabling problems; make sure cabling is securely connected and properly routed away from sources of interference. 7 ($07) MESSAGE: Link disconnected.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values 14 ($0E) MESSAGE: Cannot release ADA memory object. CAUSE: During shutdown, the driver requested the I/O system to release a memory object, but received an error reply in response. ACTION: This error should not occur. The driver may be confused, or there is a system problem. However, the driver will ignore the error and attempt to continue with the shutdown.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values before. 25 ($19) MESSAGE: Cannot release a system plabel. 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.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values suppressed. No attempt is made to determine whether the dumps are duplicates of the same problem. The driver did not dump, but will still attempt to auto-reset itself, up to a total of 12 times or more. There is apparently something wrong, since many driver dumps are occurring. Collect binary copies of all dump files (NETDMP##.PUB.SYS) on tape for analysis by Hewlett-Packard and see Appendix A , “Submitting a CR.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values 61 ($3D) MESSAGE: Bad hardware ID or path. CAUSE: During a link-open operation by an upper level subsystem, the link module configurator did not find a supported WAN ACC Sync MUX 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 WAN ACC Sync MUX adapter card is installed in the computer backplane. Verify the Power LED is lit on that adapter.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values WAN ACC Sync MUX link drivers. The only other cause is a software bug; see Appendix A , “Submitting a CR.” 77 ($4D) MESSAGE: Cannot send a port message. CAUSE: This is a generic error saying that the link driver, module configurator or deconfigurator, or other module of the link subsystem encountered an error when trying to send a port message. This error could be caused by the target module having been already shut down.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values ACTION: Severity and side effects of this error are dependent upon the purpose of the message that was not sent. Attempt to determine the conditions that led to the error. If it occurred during a shutdown, possibly this error can be ignored. Otherwise, if the same problem happens repeatedly, or if a system abort occurs, take a memory dump and see Appendix A , “Submitting a CR.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values may have been altered. If this happens frequently, see Appendix A , “Submitting a CR.” 87 ($57) MESSAGE: Cannot load a system routine. 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.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values outbound buffer pool or control buffer pool. ACTION: The system may be low on available memory. Try stopping some applications or sessions and retry the operation. If the problem persists, stop all networking and restart it, or restart the system. The buffer size and pool size are not configurable. If the problem still occurs, there could be a problem with the buffer manager. See Appendix A , “Submitting a CR.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values the reason this error is now occurring. 120 ($78) MESSAGE: Module Configurator cannot access its context area. CAUSE: During a link-close operation by an upper level subsystem, the link module deconfigurator checked its context memory area for validity, but did not find the expected data. ACTION: The module deconfigurator’s context memory area is being overwritten, or is not working properly. The deconfigurator did not perform the close.
PCI LAPBMUX Link 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 for that error and look it up also, for more actions to take. The driver will attempt to send an error reply for the startup request. It then enters a “broken” state and awaits a shutdown, which the module configurator should attempt automatically. 154 ($9A) MESSAGE: Configuration failed.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values 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. Perform a :LISTF,3 command and make sure the file is not protected by a lockword, and that the user starting the link has the necessary access rights to open the file.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values 203 ($CB) MESSAGE: Cannot determine link type. CAUSE: Early in a link open operation by an upper level subsystem, the link module configurator encountered an error while attempting to use Link Support Services to determine the type of link being started. Probably the link is not completely configured. ACTION: If the link is already started, LSS tries to read the link type from its own link table.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values 207 ($CF) MESSAGE: Cannot update to link table. CAUSE: During a link-open operation by an upper level subsystem, the link module configurator successfully started the driver, but encountered an error trying to update the link to the link table (“Cause” = 32-bit status from the call to lsslktbladd). ACTION: The module configurator cleaned up and returned an error to the subsystem. Possibly too many links are started.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values ACTION: Probably the link driver returned an error reply when asked to enable tracing. The driver may have a problem. Check for other, driver-specific error messages which may give more information about the problem, and look them up also. If no other errors are found, see Appendix A , “Submitting a CR.” 216 ($D8) MESSAGE: Driver received an unknown port message.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values 228 ($E4) MESSAGE: One or more bad unbind parms passed by upper level protocol. CAUSE: The driver received an unbind (separate) from an upper layer protocol module, but the specified rendezvous ID was out of range of legal rendezvous ID values for this driver, or the corresponding rendezvous table entry state indicated no bind had occurred or an unbind had already occurred.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values 239 ($EE) MESSAGE: Bad message for current state. 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.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values 245 ($F5) MESSAGE: Incomplete data was encountered. 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. ACTION: The trace or log file may be corrupted, or you may be trying to format a trace or log file taken on a different system that has newer software than the system you are formatting on.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values Logging Sublocation Codes The following are the logging sublocation codes reported by the WAN ACC Sync MUX link drivers, including sublocation code, log class, log message, and the appropriate cause of and action to take for each. For meanings of 32-bit status values generated by the driver, refer to the sections on status values. 1020 CLAS0001 MESSAGE: Cannot freeze a memory area.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values Hewlett-Packard what actions the driver took. See Appendix A , “Submitting a CR.” 1080 CLAS0001 MESSAGE: Did not receive an expected port message. CAUSE: During a link-open operation by an upper level subsystem, the link module configurator sent configuration data to the driver, then encountered a timeout while awaiting the correct reply message (“Cause” = 32-bit status from the call to extend_receive).
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values ACTION: There may be a system problem, or another subsystem has already shut the driver down while this one was trying to start it. The open did not succeed. The module configurator cleaned up and returned an error to the subsystem. 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 a CR.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values subsystem. 1220 CLAS0001 MESSAGE: No adapter card found on specified PCI bus. CAUSE: During a link-open operation by an upper level subsystem, the link module configurator attempted to create a new instance of the link driver, but encountered an error which was not one of the legal errors the configurator was able to handle (“Cause” = 32-bit status from the call to io_configure).
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values Verify the path in NMCONFIG is correct and complete, and matches the path where a supported WAN ACC Sync MUX adapter card is installed in the computer backplane. Verify the Power LED is lit on that adapter. If necessary, reseat the board or contact your Hewlett-Packard Representative for hardware assistance. 1280 CLAS0001 MESSAGE: No adapter card found on specified PCI bus.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values 1340 CLAS0001 MESSAGE: Cannot create a buffer pool. CAUSE: During a link-open operation by an upper level subsystem, the link module configurator encountered an error while trying to create an outbound buffer pool (“Cause” = 32-bit status from the call to bmgr_create_pool). ACTION: The system may be low on available memory. The module configurator cleaned up and returned an error to the subsystem.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values link software or contact your Hewlett-Packard Representative for assistance. 1420 CLAS0001 MESSAGE: Cannot add driver to I/O system. CAUSE: During a link-open operation by an upper level subsystem, the link module configurator attempted to create a new instance of the link driver, but encountered an error which was not one of the legal errors the configurator was able to handle (“Cause” = 32-bit status from the call to io_configure).
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values hardware configuration. If necessary, change NMCONFIG or contact your Hewlett-Packard Representative for assistance in determining paths or correcting bus hardware problems. 1480 CLAS0001 MESSAGE: Cannot open configuration file. CAUSE: During a link-open operation by an upper level subsystem, the link module configurator encountered an error while trying to open the configuration file (“Cause” = 32-bit status from the call to nmconfopen).
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values 1520 CLAS0001 MESSAGE: Cannot validate configuration file. CAUSE: After successfully reading configuration data for a link being started, the link module configurator checked the data and found it was not valid (“Cause” is not used here). For NS/3000, probably the link type and NI type do not match. ACTION: The module configurator cleaned up and returned an error to the subsystem. Using NMMGR, verify the path LINK.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values Using NMMGR, check if a filename was configured. If so, verify it is a legal MPE filename. A group and account may need to be specified. Make sure the user starting the link has the necessary capabilities to create that file in the group and account specified. Check whether the system is low on disk space. Check whether too many NMTCnnnn.PUB.SYS trace data files already exist.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values Probably the link driver returned an error reply when asked to enable tracing. The driver may have a problem. Check for other, driver-specific error messages which may give more information about the problem, and look them up also. If no other errors are found, see Appendix A , “Submitting a CR.” 1620 CLAS0001 MESSAGE: The subsys link products are not installed.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values ACTION: This is an informational warning only. The module configurator will leave the link driver up and stop trying to start it again. Usually preceded by another error. 1720 CLAS0001 MESSAGE: Cannot add to link table.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values every time, see Appendix A , “Submitting a CR.” 1780 CLAS0001 MESSAGE: Cannot send a port message. 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).
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values 1860 CLAS0001 MESSAGE: Subsystem is closing link. 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. 1880 CLAS0001 MESSAGE: Module Configurator cannot access its context area.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values resources may have been lost. The module deconfigurator reported an error, but attempted to continue with the close. If this happens every time, see Appendix A , “Submitting a CR.” 1960 CLAS0001 MESSAGE: Cannot remove driver from I/O system.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values different slot, may not be making proper contact with the PCI backplane, or may not be responding. If the I/O slot has a power indicator, verify it is on. Re-seat the board, and if necessary, contact your HP Representative for hardware assistance. 2080 CLAS0001 MESSAGE: Unable to write to adapter card PCI configuration space.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values shutting down or doing a dump, wait until that completes. Retry the operation. If the driver still does not become usable after this, use Control-B at the console to halt the system, take a memory dump, and reboot, see Appendix A , “Submitting a CR.” 2240 CLAS0001 MESSAGE: Bad message for current state.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values ACTION: This error is sometimes fatal, causing the remainder of the driver's processing to be skipped. May be followed by another error giving more information about what kind of reply the driver was trying to send; check log data for that error and look it up also. If the link does not seem to be responding, attempt to shut down and restart the network and/or link.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values 2440 CLAS0001 MESSAGE: Cannot send a port message. CAUSE: While shutting down the link, the driver attempted to free ADA memory previously obtained from the MPE I/O system, but encountered an error trying to send a memory request message to the I/O Memory Port (“Cause” = 32-bit status from the call to send_msg). ACTION: This is a warning that some memory resources may have been lost. The driver will attempt to continue.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values 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. Check the system console; if the driver is shutting down or doing a dump, wait until that completes. In these cases, several protocols may experience this same error. If the driver is not shutting down or dying, the protocol may be sending binds to the driver at the wrong time.
PCI LAPBMUX Link 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.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values If any errors occur as a result of the unbind, they will appear after, not before, this log event; the unbind will still complete, and the protocol will be successfully unbound. 2840 CLAS0001 MESSAGE: Driver encountered a software problem. CAUSE: When attempting to separate during a protocol separate (unbind), the driver gets an error from its state machine (“Cause” = 32-bit status stating the driver is “dying”).
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values ACTION: None. This error can 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.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values ACTION: This is an informational error only. The driver incremented a statistic, logged the error, then attempted to free the read buffer and continue. However, the protocol may not have received the inbound frame, therefore some applications could be hung. There may be a problem in the upper layer protocol. Also, if the protocol had already freed the buffer, this may have resulted in a SysAbort from the Buffer Manager.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values If upper level network subsystems appear hung, try shutting them down manually, or shutting down and restarting the network link; if the problem persists, see Appendix A , “Submitting a CR.” 3240 CLAS0001 MESSAGE: Driver encountered a hardware problem. CAUSE: This is a generic hardware error, reported when any of the driver’s hardware access routines reports an error. By itself it is not descriptive of the problem.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values look it up also, for more actions to take. The driver will attempt to send an error reply for the startup request. It then enters a “broken” state and awaits a shutdown, which the module configurator should attempt automatically. 3640 CLAS0001 MESSAGE: Bad message for current state.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values ACTION: No action is required; this error is informational only. An error reply was sent in response to the request. Trace was not stopped by this request this time, but it remains off. 3850 CLAS0001 MESSAGE: Cannot initiate a dump. Already dumping. CAUSE: A user attempted to force a driver dump while a previous driver dump was still occurring (“Cause” = 32-bit status saying a driver dump is starting).
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values mechanism. ACTION: No action is required; this error is informational only. An error reply was sent in response to the request. Trace was not stopped by this request this time, but it remains off. 4040 CLAS0001 MESSAGE: Bad message for current state. CAUSE: The driver received a trace enable request, at a time the driver was not able to process these requests.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values 5040 CLAS0001 MESSAGE: A data buffer is too long. CAUSE: During the receive, the driver got a receive buffer of length greater than the configured value in NMMGR. (“Cause” = 32-bit total length of the requested transmission). ACTION: Try to check the NMMGR configuration. Try to set the buffer size greater than 2048 for SDLCMUX link.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values (bring level-1 down) on the ports. By itself it is not descriptive of the problem. This error is often seen as a result of firmware crash. ACTION: If this problems happens repeatedly, then halt the system, take a memory dump, and reboot, see Appendix A , “Submitting a CR.” 5280 CLAS0001 MESSAGE: Driver encountered a hardware problem.
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values appropriate operator command (for example, :NETCONTROL STOP) and then restart it. 6040 CLAS0001 MESSAGE: A driver dump was suppressed. Too many dumps already. 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).
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values 6160 CLAS0001 MESSAGE: Internal error while initiating a dump. Dump failed. CAUSE: During processing of some other fatal driver error, the driver attempted a driver dump, but encountered an error. It then encountered this second error while trying to clean up, when attempting to release a dump timer it had obtained (“Cause” = 32-bit status returned by the call to lnk_stop_timer).
PCI LAPBMUX Link Error Messages SDI Driver Specific Status Values 434 Chapter 18
FDDI Error Messages 19 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 73 MESSAGE: FDDI link ! found incorrect HW or SW ID. 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. 74 MESSAGE: FDDI link ! could not read hardware ID. 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 20 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. 6 MESSAGE: FGETINFO failed to return recsize and/or numrec. CAUSE: The file PSILAPB0.PUB.SYS is corrupted. ACTION: Restore the file from a backup tape. 7 MESSAGE: FREEZE of download file failed. CAUSE: The system is experiencing memory shortage problems.
LAP-B Link Error Messages LAP-B Link Startup Error Messages 13 MESSAGE: Could not receive the config reply message. CAUSE: Internal system ports problem. ACTION: Please record the error information printed on the console and contact your Hewlett-Packard representative. 14 MESSAGE: Timeout waiting for the config reply message. 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 20 MESSAGE: Could not create or bind with the driver. 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 22 MESSAGE: Could not unfreeze the download file ! CAUSE: The system is experiencing memory problems. ACTION: Please record the error information printed on the console and contact your Hewlett-Packard representative. 23 MESSAGE: Could not close download file ! 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 e3000 operator’s console in the following format: LAPB (linkname) Message text LAPB (linkname) Error ErrorNum, Status = Status, Path: PhysPath 1000 MESSAGE: The download file is too small. 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 1004 MESSAGE: PSI fatal error, dinmode. 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. 1005 MESSAGE: PSI fatal bus error.
LAP-B Link Error Messages LAP-B Link Driver Error Messages 1010 MESSAGE: The PSI received a bad command from the driver. CAUSE: Internal error. ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative. 1011 MESSAGE: PSI received a bad DMA command from the driver. CAUSE: Internal error. ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative.
LAP-B Link Error Messages LAP-B Link Driver Error Messages 1016 MESSAGE: Attempt to download to a bad card address. 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. 1025 MESSAGE: Unsupported software model in IODC. 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 1030 MESSAGE: PSI register test failed during PSI initialization. CAUSE: Bad PSI hardware. ACTION: Run the Sherlock diagnostics on the PSI and call your Hewlett-Packard representative if a failure is detected. 1032 MESSAGE: User invoked dump caused the driver to fail. 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 raw dump file along with the error information displayed on the console, call your Hewlett-Packard representative, and submit an CR. 1036 MESSAGE: Download file is incorrect for this driver. CAUSE: Hardware was successfully downloaded, but the downloaded code turned out to be for a different driver.
LAP-B Link Error Messages LAP-B Link Driver Error Messages 1040 MESSAGE: Unable to obtain an I/O Services timer. CAUSE: A call to obtain a timer resource returned in error. Too many timers may be in use. 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.
LAP-B Link Error Messages LAP-B Link Driver Error Messages 1046 MESSAGE: Attempting to find I/O Services message on port failed. CAUSE: The system rejected an attempt by the driver to locate message frames on its own port. Memory data corruption may have occurred. ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative. 1047 MESSAGE: Attempted impossible state after a request or completion.
LAP-B Link Error Messages LAP-B Link Driver Error Messages incorrect port subqueues may have created excessive pending hardware activity. ACTION: Write down the error information displayed on the console, submit an CR, and call your Hewlett-Packard representative. 1053 MESSAGE: Request received in invalid state. 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 1057 MESSAGE: Input buffer passed in a message is too small. 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 this information, call your Hewlett-Packard representative. 1062 MESSAGE: Bad top plane buffer pool in configuration data. CAUSE: The driver requires the valid buffer-pool ID of a pool to be used for card trace and other internal I/O, to appear in a configuration buffer passed during startup, but the ID it found was zero. The module configurator should not have sent the configure message if the buffer pool could not be opened.
LAP-B Link Error Messages LAP-B Link Driver Error Messages 1066 MESSAGE: Unknown driver problem. 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 CR, and call your Hewlett-Packard representative. 2013 MESSAGE: Unknown error while attempting to autodial. CAUSE: Before attempting to autodial, the PSI detected something wrong.
LAP-B Link Error Messages LAP-B Link Driver Error Messages 2018 MESSAGE: Cannot autodial because of cabling problems. CAUSE: Either no cable is attached, a non-autodial cable is attached, or a bad autodial cable is attached. 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 CR, and call you local Hewlett-Packard representative.
LAP-B Link Error Messages LAP-B Link Driver Error Messages 2505 MESSAGE: PSI cannot send a frame across the line. 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 CR 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 56 MESSAGE: Could not delete the auxiliary buffer pool. 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. 57 MESSAGE: Could not determine the PSI path number IO Serv.
LAP-B Link Error Messages LAP-B Link Shutdown Error Messages 460 Chapter 20
Logging Location Codes 21 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 21-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. The subsystem logging classes are summarized in Table 21-1.
Logging Location Codes Logging Subsystems Table 21-1 Logging Subsystems and Class Names Subsystem Name Class Name Events SUB0028 CLAS0010 Errors 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
Logging Location Codes Logging Subsystems includes the Internal Event description and Parm description, if relevant, as shown in the typical formatted log example in Figure 21-1. Table 21-2 Network Transport Entities Entity Entity Number Description ARP 124 The address resolution protocol for use on FDDI, Token Ring, and Ethernet LAN networks. Control Process 66 NETCP is created by the NETCONTROL command. It handles network startup and shutdown.
Logging Location Codes Logging Subsystems Table 21-2 Network Transport Entities Entity Entity Number Description SNA NI 10 The network interface for SNA connections. (This product is obsolete.) TCP PM 103 The TCP protocol module is responsible for connection-oriented protocol functions. There is one TCP PM for each side of a connection. This protocol handles reliable end-to-end packet transmission and reordering.
Logging Location Codes Logging Subsystems Table 21-2 Network Transport Entities Entity Entity Number Description ARP Read Completor 148 This is a procedure which is called by the link driver to pass incoming ARP packets into Transport. PROBE Read Completor 149 This is a procedure which is called by the link driver to pass incoming PROBE packets into Transport.
Logging Location Codes Logging Subsystems PARM Value Many Network Transport logging records contain important information in the Parameter value. This Parameter number indicates the shutdown reason. In the Network Transport logging location explanations which follow, certain Parameter values refer you to other tables in this manual. “Message Path Error” Internal Events, for example, refer to the Path Result Code Table in this chapter for definition of the Parameter value.
Logging Location Codes Logging Subsystems Network IPC Subsystem Logging Logging for the NetIPC subsystem (SUB0005) of the associated links should be configured only if users on your system are writing their own NetIPC applications with the intrinsics described in the NetIPC 3000/XL Programmer’s Reference Manual. NetIPC subsystem logging provides the network manager with a “system check” to determine which NetIPC applications are operating, if any.
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 21-2 Non-Critical Transport Error Statistics Logging Example An example of log class 6, statistics, is shown in Figure 21-3. Figure 21-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 21-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. The “Statistics:” section displays the following fields: • IPC Port ID.
Logging Location Codes Using Log Files 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. May be more than the number of User Sends/Receives because TCP may need to fragment the message into link-size packets. • PM pkts sent/recd.
Logging Location Codes Using Log Files • 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. A connection is quenched when it receives a source quench ICMP message from IP.
Logging Location Codes ARP Logging Location Codes ARP Logging Location Codes 1 CLAS0002 MESSAGE: None CAUSE: A port message was received containing an invalid function code (PARM = function code). ACTION: See Appendix A , “Submitting a CR,” of this manual. 3 CLAS0004 MESSAGE: None CAUSE: ARP protocol started. ACTION: Informative message. 12 CLAS0003 MESSAGE: None CAUSE: An ARP packet with a bad ARP header was received from the link.
Logging Location Codes ARP Logging Location Codes 54 CLAS0002 MESSAGE: None CAUSE: Unable to create object for ARP port data area. ACTION: See Appendix A , “Submitting a CR,” of this manual. 55 CLAS0002 MESSAGE: None CAUSE: Failed to locate ARP’s ICS filter routine in NL.PUB.SYS. ACTION: See Appendix A , “Submitting a CR,” of this manual. 56 CLAS0002 MESSAGE: None CAUSE: Failed to locate ARP’s timer routine in NL.PUB.SYS. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes ARP Logging Location Codes ACTION: Verify that the NMCONFIG.PUB.SYS file exists. If the file exists, see Appendix A , “Submitting a CR,” of this manual. 65 CLAS0002 MESSAGE: None CAUSE: Failed to send ARP request out over the network. ACTION: See Appendix A , “Submitting a CR,”of this manual. 66 CLAS0002 MESSAGE: None CAUSE: Failed to send ARP request out over the network. ACTION: See Appendix A , “Submitting a CR,” of this manual.
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 a CR,” of this manual. 74 CLAS0002 MESSAGE: None CAUSE: Failed to update the NS Registry with ARP’s port. ACTION: See Appendix A , “Submitting a CR,” of this manual. 75 CLAS0002 MESSAGE: None 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 a CR,” of this manual.
Logging Location Codes Control Process Logging Location Codes 25 CLAS0002 MESSAGE: INTERNAL ERROR; Configuration file error 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 a CR,” of this manual.
Logging Location Codes Control Process Logging Location Codes 33 CLAS0002 MESSAGE: INTERNAL ERROR; Async request from link 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 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 84 CLAS0002 MESSAGE: INTERNAL ERROR; Bad/unknown port message 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). ACTION: The message was ignored and NETCP went back to waiting for the next new command.
Logging Location Codes Control Process Logging Location Codes 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 a CR,” of this manual. 136 CLAS0002 MESSAGE: INTERNAL ERROR; Device open CAUSE: While attempting to rendezvous a specific protocol to the link driver, NETCP encountered an error (PARM = 32-bit status returned by the call to ns_rendezvous_to_driver). ACTION: NETCP assumed the rendezvous failed.
Logging Location Codes Control Process Logging Location Codes 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. Later, after all replies arrive or a timeout occurs, the oldest queued Path Verify is executed (PARM = number of duplicates of this Path Verify received and discarded while awaiting replies; nonzero indicates a storm is occurring, and larger numbers mean more severe storms).
Logging Location Codes Control Process Logging Location Codes 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 restart the network. If the problem persists, see Appendix A , “Submitting a CR,” of this manual. 238 CLAS0002 MESSAGE: INTERNAL ERROR: Configuration file error CAUSE: During NETCP processing of a network start or update command, after an earlier successful validation of the NMCONFIG file a later validation of the file failed (PARM = 16-bit result code returned by the call to validatenetxport). ACTION: The specified network was not started.
Logging Location Codes Control Process Logging Location Codes 254 CLAS0002 MESSAGE: INTERNAL ERROR; Configuration file error CAUSE: NETCP tried to search the NMCONFIG file to determine if an NI having a specific name was configured or not, but was unable to open the file (PARM = 32-bit status returned by the call to nmconfopen). ACTION: Check that the NMCONFIG file exists and is not already opened by some other user, such as a STORE process or someone running NMMGR.
Logging Location Codes Control Process Logging Location Codes ACTION: None. This is an informative message only. The LAPB link is now successfully engaged in protocol handshaking, and will stay up unless an error, disconnect, or idle timeout occurs, or the network is stopped. 259 CLAS0003 MESSAGE: INBOUND; Device disconnected CAUSE: NETCP received an asynchronous event message from the DCLDM indicating that its LAPB PSI link was disconnected by its remote side (PARM = 0).
Logging Location Codes Control Process Logging Location Codes ACTION: None. The network was not started. See Appendix A , “Submitting a CR,” of this manual. 266 CLAS0002 MESSAGE: INTERNAL ERROR; Configuration file error CAUSE: NETCP tried to search the NMCONFIG file to determine if an NI having a specific name was configured or not, but after successfully opening the file it was unable to close it (PARM = 32-bit status returned by the call to nmconfclose).
Logging Location Codes Control Process Logging Location Codes 280 CLAS0002 MESSAGE: INTERNAL ERROR; Configuration file error CAUSE: While processing a :NETCONTROL command to start or update a network or add a link, NETCP was unable to open the NMCONFIG file (PARM = 32-bit status returned by the call to nmconfopen). ACTION: The command did not execute. Check that the NMCONFIG file exists and is not already opened by some other user, such as someone running NMMGR.
Logging Location Codes Control Process Logging Location Codes failed. If you wish to pursue the cause further, stop Transport and enable all available logging for the link subsystem corresponding to the NI type of the network reporting the error, then restart and stop the same network again to reproduce the problem, monitoring logged data for any problems.
Logging Location Codes Control Process Logging Location Codes 289 CLAS0003 MESSAGE: INTERNAL ERROR; NM Entry CAUSE: While creating a network NI for which IP Store and Forward was enabled, NETCP was unable to put the new Store and Forward buffer pool ID into a new entity, having the same name as the NI, 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 293 CLAS0002 MESSAGE: INTERNAL ERROR; Auto dial failure CAUSE: NETCP received an asynchronous event message from the DCLDM indicating that its LAPB PSI’s autodial operation failed due to an internal autodialer problem (PARM = 16-bit internal ldev number of the device). ACTION: Check the autodialer cabling and strapping or configuration, and diagnose the autodialer hardware. Then retry the operation.
Logging Location Codes Control Process Logging Location Codes 304 CLAS0003 MESSAGE: Device restarting CAUSE: NETCP received an asynchronous event message from the DCLDM indicating that its LAPB PSI link experienced a power failure, resulting in a disconnect of the phone line (PARM = 16-bit internal ldev number of the device). May be followed by informative error 101 if outbound data was queued when the error occurred. ACTION: None. This is an informative error message only.
Logging Location Codes Control Process Logging Location Codes asynchronous DCLDM event message indicating its LAPB PSI link reported another failure (PARM = upper 16 bits of status from the call to xp_connect_the_driver: usually the connect event code from LAPB). ACTION: NETCP disconnected the device and notified protocols that the link went down. This is most likely a link level problem. Consult the link diagnostics and check the modems. Confirm that the link connection is working for the affected link.
Logging Location Codes Control Process Logging Location Codes driver, through the DCLDM (PARM = 32-bit adjusted status returned by the call to xp_connect_the_driver: add decimal 256 to get the actual status). 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. Also check the validity of the phone number in the configuration.
Logging Location Codes Control Process Logging Location Codes device because its network was being started, NETCP was unable to put that pool ID into a new entity, having a name that is the ASCII version of the decimal buffer size, 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 host. This error message is only printed once per startup, even if multiple X25 addresses have this problem. 412 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error CAUSE: NETCP received an unrecognized message on port subqueue 2 or 4, which are only designed for asynchronous event messages (PARM = first 16 bits of message, which should give the message type.
Logging Location Codes Control Process Logging Location Codes ACTION: This error in itself was not fatal, and NETCP continued operating. However, some other modules on the system may still be waiting for the event message that mistakenly went to NETCP, and this could cause problems in those other modules. If disc logging was enabled, NETCP logged the entire received message to the current NM logfile, which may aid in diagnosis. If necessary, see Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Control Process Logging Location Codes ACTION: This error in itself was not fatal, and device shutdown continued. After shutdown, use the LANDAD tool to verify the LAN hardware is functioning correctly. If it looks good but the problem persists, then see Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Control Process Logging Location Codes ACTION: None. This is an informative message only. 501 CLAS0005 MESSAGE: LOGGING; Log CAUSE: NETCP has received a message instructing it to process a :NETCONTROL STATUS command (PARM = hex 332). ACTION: None. This is an informative message only.
Logging Location Codes Control Process Logging Location Codes error on the send (PARM = 32-bit status returned by the call to send_msg). ACTION: This will prevent SNA from establishing any connections. Stop and restart the network. If this problem continues, see Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Control Process Logging Location Codes command, NETCP encountered an error trying to send a trace disable message to that module (PARM = 32-bit status returned by the call to send_msg). ACTION: This error was not fatal, and network operation continued. Though it is not possible to tell from console logging which module was affected, disc logging will show the entire message, including the interface code of the entity being sent to.
Logging Location Codes Control Process Logging Location Codes 611 CLAS0002 MESSAGE: INTERNAL ERROR; Module Deconfig Failed CAUSE: While shutting down Transport due to a system shutdown or a :NETCONTROL STOP command, NETCP encountered an error when trying to stop one of the general protocols (PARM = 32-bit escape code returned by the call to the module deconfigurator that failed).
Logging Location Codes Control Process Logging Location Codes future :NETCONTROL commands may either hang or cause a system abort. See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Control Process Logging Location Codes error trying to add the name of the file into a CM Port Dictionary entry named “NMCONFIG” (PARM = 16-bit result code returned by the call to dict_add). The entry was used as a way to partially lock the file, so NMMGR could tell Transport was up and running. The CM Port Dictionary is an operating system lookup service used by, but not part of, Transport. ACTION: This error was not fatal, and network startup continued.
Logging Location Codes Control Process Logging Location Codes 620 CLAS0002 MESSAGE: Bad status CAUSE: While attempting to send a device start message to an existing NI in response to a :NETCONTROL command, NETCP encountered an error on the send (PARM = 32-bit status returned by the call to send_msg). ACTION: The device was started at the NETCP and MAP layers, but not at the NI layer.
Logging Location Codes Control Process Logging Location Codes establish connections with it may fail. Restart the network. If this problem persists, see Appendix A , “Submitting a CR,” of this manual. 624 CLAS0002 MESSAGE: Bad status CAUSE: While attempting to send a device stop message to the DIAL module because protocols on an existing ROUTER network are being shut down, NETCP encountered an error on the send (PARM = 32-bit status returned by the call to send_msg).
Logging Location Codes Control Process Logging Location Codes 627 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error CAUSE: While stopping an NI because a network was being shut down, NETCP encountered an error trying to delete a mapping table it had previously created for the NI (PARM = 32-bit status returned by the call to map_create_table). ACTION: This error in itself was not fatal, and shutdown continued.
Logging Location Codes Control Process Logging Location Codes 630 CLAS0002 MESSAGE: Bad status CAUSE: While processing a Path Verify operation because NETCP detected a possible problem or change in state of a certain network, or because of a Path Verify message received from IPU in response to a redirect packet IPU received from a GATEWAY, NETCP encountered an error trying to send a Path Verify message to one of the general protocols (PARM = 32-bit status returned by the call to send_msg).
Logging Location Codes Control Process Logging Location Codes 633 CLAS0002 MESSAGE: Bad status CAUSE: While attempting to send a device stop message to notify the DIAL module that an existing ROUTER network was being shut down, because of a :NETCONTROL DELLINK command or a previous asynchronous link error, NETCP encountered an error on the send (PARM = 32-bit status returned by the call to send_msg).
Logging Location Codes Control Process Logging Location Codes 636 CLAS0002 MESSAGE: Bad status CAUSE: While attempting to send a debug message to one of the Transport protocol modules in response to a :NETCONTROL DIAG command, NETCP encountered an error on the send (PARM = 32-bit status returned by the call to send_msg). ACTION: This error was not fatal, and NETCP continued running. However, the desired module did not receive its debug message, and will not respond as expected.
Logging Location Codes Control Process Logging Location Codes ACTION: It is not possible to tell from the console logging what function code NETCP received, however if disc logging was enabled, the entire received message was logged, which may aid debugging. The flow of normal NETCP operations has been interrupted, and a network hang may be imminent, especially if new :NETCONTROL commands are issued. It may be necessary to restart the system to clear this problem.
Logging Location Codes Control Process Logging Location Codes ni_module_deconfig). Always preceded by another error from another entity (having a different Entity number, such as 151–160), indicating the cause of the original failure. ACTION: This error in itself was not fatal, and shutdown continued. However, some system resources may be lost until after the next system restart. Inspect the previous error and if necessary, see Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Control Process Logging Location Codes 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. However, creation of the NS Registry by NETCP may have failed (see error 285), or the Registry may be full. If the message occurs every time, see Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Control Process Logging Location Codes restarting the network. If the problem persists, see Appendix A , “Submitting a CR,” of this manual. 650 CLAS0002 MESSAGE: INTERNAL ERROR; Module Deconfig Failed CAUSE: During the final phases of shutdown because of a :NETCONTROL STOP command or a system shutdown, NETCP encountered and error while attempting to stop the ICMP Server module it previously started (PARM = 32-bit status returned by the call to icmp_server_module_deconfig).
Logging Location Codes Control Process Logging Location Codes NETCP encountered an error trying to start the PXP protocol module (PARM = 32-bit status returned by the call to tcp_module_config). Always preceded by another error from a different entity (having a different Entity number, such as 151–160), the configurator, logging the reason for the original failure. ACTION: This error in itself was not fatal, and general protocol startup continued. However, dynamic name resolution will fail.
Logging Location Codes Control Process Logging Location Codes 655 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error CAUSE: While attempting to start all the general protocols because a :NETCONTROL command was starting a new instance of Transport, NETCP successfully started some modules, then encountered an error trying to start the ICMP (PING) Server module (PARM = 32-bit escape code returned by the call to pxp_module_config).
Logging Location Codes Control Process Logging Location Codes 658 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error CAUSE: While attempting to start all network specific protocols, required for a given network, such as IP, because a :NETCONTROL command was issued, NETCP encountered an error, either from a protocol’s module configurator, or while trying to rendezvous a protocol to the link driver. (PARM = 32-bit status returned by the call to a module configurator, or from cp_rendezvous_protocol).
Logging Location Codes Control Process Logging Location Codes 661 CLAS0002 MESSAGE: Bad status CAUSE: After successfully starting a LAN 802.3 or Ethernet link and all its network specific protocols because a :NETCONTROL command was issued, NETCP encountered an error trying to send a broadcast information message to the UDP protocol module (PARM = 32-bit status returned by the call to send_msg). ACTION: This error in itself was not fatal, and network startup continued.
Logging Location Codes Control Process Logging Location Codes ACTION: This 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 new autodial connections cannot be established, and sessions which attempt it may 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.
Logging Location Codes Control Process Logging Location Codes 674 CLAS0002 MESSAGE: INTERNAL ERROR; Wrong autodial cable OUTBOUND; occupied CAUSE: NETCP received an asynchronous event message from the DCLDM indicating that its LAPB PSI’s autodial operation was not completed, because the cable attached to the PSI card is not the proper cable required for autodial operations (PARM = 16-bit internal ldev number of the device).
Logging Location Codes Control Process Logging Location Codes message content was logged in the NM logfile along with this error, which may aid in debugging any hung modules. If the received message looks like a Path Verify reply, there is a message length bug in the general protocol module which sent it; this is not serious though it may result in error 629 later.
Logging Location Codes Control Process Logging Location Codes 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 684 CLAS0002 MESSAGE: BUFFER MANAGER; Buffer manager error CAUSE: After NETCP successfully wrote configuration data for an X25 network into a buffer it obtained earlier, because a :NETCONTROL command was issued, while trying to crossmatch the X25 mappings NETCP encountered an error trying to read a data entry out of that same buffer (PARM = 32-bit status returned by the call to bmgr_read_buffer).
Logging Location Codes Control Process Logging Location Codes operate correctly. Verify you have all the required patches, especially a coherent set of patches required to support 2048 X25 SVC paths under NMMGR and NS Transport. Also verify that the number of X25 paths configured in the NMCONFIG file is within the supported limits. If the problem still cannot be found, see Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Control Process Logging Location Codes 691 CLAS0002 MESSAGE: INTERNAL ERROR; No DEVS CAUSE: While starting an X.25 network due to a :NETCONTROL START command, or while updating it due to a :NETCONTROL UPDATE command, NETCP found that none of the X.25 address keys in the Network Directory file matched any keys in the NMCONFIG file’s SVC or PVC configurations for that X.25 network (PARM = 0). ACTION: This error in itself was not fatal, and startup continued.
Logging Location Codes Control Process Logging Location Codes status in its reply. ACTION: NETCP may fail to properly stop the network and/or the driver. But this may not affect other networks on the system. Try to restart the network and if it fails, see Appendix A , “Submitting a CR.” 762 CLAS0002 MESSAGE: Bad status CAUSE: NETCP encountered an error while sending a connect message to LAPBMUX link driver.
Logging Location Codes Control Process Logging Location Codes “Submitting a CR.” 769 CLAS0002 MESSAGE: INTERNAL ERROR; Async request from link CAUSE: NETCP received an asynchronous event message containing an error status, from the LAPBMUX driver. ACTION: NETCP stopped the device associated with the link, also stopped any attached protocol and drivers. It may be possible to restart the device using :NETCONTROL ADDLINK=linkname; NET=niname. If the problem persists, see Appendix A , “Submitting a CR.
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 port for the module (PARM = 32-bit status returned by the call to create_port). ACTION: There may be a problem with the Ports subsystem of MPE, or the system may be low on memory. If necessary, see Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes NS Configurator Logging Location Codes 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). ACTION: There may be a problem with the Ports subsystem of MPE or a bug in the Module Configurator. See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes NS Configurator Logging Location Codes manual. 17 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error CAUSE: When NETCP attempted to create a new protocol module for an existing NI, after successfully creating a message port for the module, an error occurred while trying to release ownership of the port (PARM = 32-bit status returned by the call to port_control). ACTION: There may be a problem with the Ports subsystem of MPE or a bug in the Module Configurator.
Logging Location Codes NS Configurator Logging Location Codes function code in the reply was not for a termination message (PARM = 0). 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 a CR,” of this manual.
Logging Location Codes CX Logging Location Codes CX Logging Location Codes 1 CLAS0003 MESSAGE: None CAUSE: The NS keyword table was not allocated during system startup prior to an NS command execution. ACTION: See Appendix A , “Submitting a CR,” of this manual. 2 CLAS0003 MESSAGE: None CAUSE: The NS global data segment was not allocated during system startup, or has been lost. ACTION: See Appendix A , “Submitting a CR,” of this manual. 3 CLAS0003 MESSAGE: None CAUSE: Bad format in the ASCAT.NET.
Logging Location Codes CX Logging Location Codes ACTION: See Appendix A , “Submitting a CR,” of this manual. 10 CLAS0003 MESSAGE: None CAUSE: A port for communication between the CI and CT server process could not be created. ACTION: See Appendix A , “Submitting a CR,” of this manual. 11 CLAS0002 MESSAGE: None CAUSE: A port DST entry could not be allocated for the port between the CI and VT server. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes CX Logging Location Codes 18 CLAS0002 MESSAGE: None 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 a CR,” of this manual. 19 CLAS0003 MESSAGE: None CAUSE: A port message send to DSDAD failed. ACTION: See Appendix A , “Submitting a CR,” of this manual. 21 CLAS0003 MESSAGE: None 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. 2 CLAS0000 MESSAGE: Send_msg error 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 a CR,” of this manual. 17 CLAS0000 MESSAGE: Invalid CM request received in current state 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 subsequent network shutdown may hang. See Appendix A , “Submitting a CR,” of this manual. 23 CLAS0000 MESSAGE: Error in releasing write buffer in current state CAUSE: Upon entering into a “sick” state because of some other problem, DC/LDM attempted to clean up after the last message it received, in this case a read event message, but in trying to free the buffer in that message, the system routine bmgr_free_buffer reported an error.
Logging Location Codes DC/LDM Logging Location Codes 33 CLAS0000 MESSAGE: Asynchronous error event received from lower manager 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 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. ACTION: DC/LDM will continue stopping, but if this situation continues, the network may run out of buffers. In addition, any subsequent network shutdown may hang.
Logging Location Codes Dial ID Logging Location Codes Dial ID Logging Location Codes 1 CLAS0001 MESSAGE: None CAUSE: A port message was received containing an invalid function code (PARM = function code). ACTION: See Appendix A , “Submitting a CR,” of this manual. 2 CLAS0004 MESSAGE: None CAUSE: Dial ID protocol started. ACTION: Informational message. 3 CLAS0002 MESSAGE: None 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 9 CLAS0001 MESSAGE: None CAUSE: The sending of a link shut message to the Control Process using DICTSEND failed (PARM = result code of DICTSEND call). ACTION: Informational message. 10 CLAS0002 MESSAGE: None 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 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. 20 CLAS0002 MESSAGE: None CAUSE: A remote node is attempting connection and the network number of its IP address does not match the network number of the network interface over which the Dial ID protocol is active.
Logging Location Codes Dial ID Logging Location Codes 33 CLAS0002 MESSAGE: None 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 a CR,” of this manual.
Logging Location Codes Dial ID Logging Location Codes 41 CLAS0002 MESSAGE: None 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 a CR,” of this manual. 42 CLAS0002 MESSAGE: None 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 protocol at the local node matches the one sent by the remote node. 48 CLAS0002 MESSAGE: None CAUSE: The security string contained in the remote node’s request packet does not match any of the strings configured at the local node. ACTION: Verify that the security string sent by the remote node matches one in the list of security strings configured under the Dial ID protocol 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 a CR,” of this manual. 55 CLAS0002 MESSAGE: None 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 86 CLAS0003 MESSAGE: None CAUSE: Dial is entering the TIME WAIT state after a normal ack-ack message. ACTION: None. Informational only. 87 CLAS0003 MESSAGE: None CAUSE: A link failure occurred, and Dial is cleaning up the resources (PARM = status). ACTION: None. Informational only. 88 CLAS0002 MESSAGE: None 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 94 CLAS0002 MESSAGE: None CAUSE: Received a CP reply message after the start request timer has expired. ACTION: None. 95 CLAS0002 MESSAGE: None 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 a CR,” of this manual. 96 CLAS0002 MESSAGE: None 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 1 CLAS0003 MESSAGE: None CAUSE: Buffer space for DSDAD’s global data structure could not be created. ACTION: See Appendix A , “Submitting a CR,” of this manual. 2 CLAS0003 MESSAGE: None CAUSE: Header for the DSDAD data structure could not be created. ACTION: See Appendix A , “Submitting a CR,” of this manual. 3 CLAS0003 MESSAGE: None CAUSE: DSDAD log buffer could not be created.
Logging Location Codes DSDAD Logging Location Codes ACTION: See Appendix A , “Submitting a CR,” of this manual. 11 CLAS0005 MESSAGE: None CAUSE: Attempt to create a socket failed. ACTION: See Appendix A , “Submitting a CR,” of this manual. 22 CLAS0003 MESSAGE: None CAUSE: Request for a server initiation could not be satisfied because of an invalid port message. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes DSDAD Logging Location Codes 31 CLAS0003 MESSAGE: None CAUSE: ServerInSession request could not be handled because server entry was not found. ACTION: See Appendix A , “Submitting a CR,” of this manual. 32 CLAS0003 MESSAGE: None CAUSE: Logoff entry could not be allocated. ACTION: See Appendix A , “Submitting a CR,” of this manual. 33 CLAS0003 MESSAGE: None CAUSE: Internal error — No Server entry found for PIN in CnctRecved msg.
Logging Location Codes DSSERVER Logging Location Codes DSSERVER Logging Location Codes 1 CLAS0003 MESSAGE: None CAUSE: DSSERVER stack log buffer could not be allocated. ACTION: See Appendix A , “Submitting a CR,” of this manual. 2 CLAS0003 MESSAGE: None CAUSE: DSSERVER header for data structures could not be allocated. ACTION: See Appendix A , “Submitting a CR,” of this manual. 3 CLAS0003 MESSAGE: None CAUSE: Stack buffer space for DSSERVER data structures could not be created.
Logging Location Codes DSSERVER Logging Location Codes ACTION: See Appendix A , “Submitting a CR,” of this manual. 11 CLAS0003 MESSAGE: None CAUSE: Could not find a wait entry for nowait I/O which completed. ACTION: See Appendix A , “Submitting a CR,” of this manual. 12 CLAS0003 MESSAGE: None CAUSE: The VT service reported an error. ACTION: Repair the VT error, if possible. 13 CLAS0003 MESSAGE: None CAUSE: RFA service reported an error. ACTION: Repair the error, if possible.
Logging Location Codes DSUTIL Logging Location Codes DSUTIL Logging Location Codes 8 CLAS0002 MESSAGE: None 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 1 CLAS0002 MESSAGE: None CAUSE: Buffer space for DSLINE table could not be created. ACTION: Increase the number of configured DSTs. 2 CLAS0003 MESSAGE: None CAUSE: Trace file for an NS service could not be opened. ACTION: See Appendix A , “Submitting a CR,” of this manual. 3 CLAS0003 MESSAGE: None CAUSE: Trace file for an NS service could not be closed. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes ENV Logging Location Codes 10 CLAS0002 MESSAGE: None CAUSE: Extra data segment not available to create the session ID table. ACTION: See Appendix A , “Submitting a CR,” of this manual. 11 CLAS0003 MESSAGE: None CAUSE: No NS global table could be found. ACTION: See Appendix A , “Submitting a CR,” of this manual. 12 CLAS0002 MESSAGE: None CAUSE: Unable to get an entry in the session ID table. ACTION: See Appendix A , “Submitting a CR,” 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 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. 303 MESSAGE: Destination Unreachable. CAUSE: The destination node was unable to deliver the IP datagram that originated from the node that logs this message.
Logging Location Codes ICMP Type/Code Words was unable to forward or deliver the IP datagram because the capacity limit of resource (e.g., buffers) is being approached. In this case, the IP datagram is NOT discarded. On receipt of a source quench ICMP message, the source will cut back its rate of TCP traffic to the destination node specified in the ICMP message. Source quench messages are sent to the source of the traffic and therefore logged at the source.
Logging Location Codes ICMP Type/Code Words Time-To-Live is too short. ACTION: If after verifying all links are operational, it may be necessary to increase the Reachable Hop Count in the Static Neighbor Gateway Reachable Network screen during configuration. If the destination node is on a router network it may be necessary to increase the Network Hop Count in its Router Network Interface screen. 601 MESSAGE: Time Exceeded.
Logging Location Codes IP Logging Location Codes IP Logging Location Codes 101 CLAS0003 MESSAGE: None CAUSE: Received a port message containing an invalid function code (PARM = complete function code). ACTION: See Appendix A , “Submitting a CR,” of this manual. 102 CLAS0004 MESSAGE: None CAUSE: Log IP port initiation (PARM = PDA ptr). ACTION: Informative.
Logging Location Codes IP Logging Location Codes ACTION: See Appendix A , “Submitting a CR,” of this manual. 111 CLAS0003 MESSAGE: None 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 a CR,” of this manual.
Logging Location Codes IP Logging Location Codes 121 CLAS0003 MESSAGE: None 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 a CR,” of this manual. 122 CLAS0003 MESSAGE: None 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 133 CLAS0002 MESSAGE: None 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 a CR,” of this manual. 137 CLAS0003 MESSAGE: None 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 147 CLAS0003 MESSAGE: None 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 162 CLAS0002 MESSAGE: None 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 a CR,” of this manual. 165 CLAS0002 MESSAGE: None 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 182 CLAS0002 MESSAGE: None CAUSE: The send by IP to NI for normal outbound data was unsuccessful (PARM = send_msg result). ACTION: See Appendix A , “Submitting a CR,” of this manual. 183 CLAS0002 MESSAGE: None 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 a CR,” of this manual.
Logging Location Codes IP Logging Location Codes 191 CLAS0002 MESSAGE: None CAUSE: An error was detected while attempting to start a timer for inbound reassembly (PARM = get_timer result). ACTION: See Appendix A , “Submitting a CR,” of this manual. 192 CLAS0002 MESSAGE: None CAUSE: An inbound buffer could not be freed while processing a partial datagram (reassembly) (PARM = bmgr_free_buffer result). ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes IP Logging Location Codes ACTION: See Appendix A , “Submitting a CR,” of this manual. 199 CLAS0002 MESSAGE: None CAUSE: IP was unable to add itself to the registry during initialization (PARM = reg_add_entity result). ACTION: See Appendix A , “Submitting a CR,” of this manual. 200 CLAS0004 MESSAGE: None 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 1 CLAS0002 MESSAGE: None CAUSE: Received a port message containing an invalid format code or an invalid function code (PARM = complete function code). ACTION: See Appendix A , “Submitting a CR,” of this manual. 3 CLAS0004 MESSAGE: None 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. 15 CLAS0002 MESSAGE: None 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 12. 16 CLAS0006 MESSAGE: None CAUSE: Log statistics prior to port termination (PARM unused).
Logging Location Codes IPU Logging Location Codes 28 CLAS0002 MESSAGE: None 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 a CR,” of this manual. 29 CLAS0002 MESSAGE: None 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 a CR,” 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. 1 Log Class 2 MESSAGE: None CAUSE: Unable to send connect request. ACTION: See Appendix A , “Submitting a CR,” of this manual. 2 Log Class 2 MESSAGE: None CAUSE: Unable to send disconnect request. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes L2Resolve Logging Location Codes 15 Log Class 3 MESSAGE: None 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. 17 Log Class 2 MESSAGE: None CAUSE: Invalid request from upper layers in current state. ACTION: See Appendix A , “Submitting a CR,” of this manual. 18 Log Class 2 MESSAGE: None CAUSE: Invalid request from lower layers in current state.
Logging Location Codes L2Resolve Logging Location Codes 25 Log Class 2 MESSAGE: None 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 a CR,” of this manual. 26 Log Class 2 MESSAGE: None CAUSE: Unknown event before L2Resolve is fully operational. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes L2Resolve Logging Location Codes 34 Log Class 2 MESSAGE: None CAUSE: Connection reply for an unknown connection. ACTION: See Appendix A , “Submitting a CR,” of this manual. 35 Log Class 2 MESSAGE: None CAUSE: Disconnect reply for an unknown connection and maximum number of connections exceeded. ACTION: See Appendix A , “Submitting a CR,” of this manual. 36 Log Class 2 MESSAGE: None CAUSE: Disconnect reply message received for an unknown connection.
Logging Location Codes L2Resolve Logging Location Codes 45 Log Class 4 MESSAGE: None CAUSE: L2Resolve is starting. ACTION: Informative message. 46 Log Class 2 MESSAGE: None CAUSE: Invalid message type for current L2Resolve state. ACTION: See Appendix A , “Submitting a CR,” of this manual. 47 Log Class 2 MESSAGE: None CAUSE: Error in starting or stopping L2Resolve. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued 22 Logging Location Codes Continued 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 Continued Mapping Table Mapping Table 1 CLAS0004 MESSAGE: None CAUSE: Mapping table was created (PARM = Pointer to mapping table control block). ACTION: None. 2 CLAS0004 MESSAGE: CAUSE: Mapping table was deleted (PARM = Pointer to mapping table control block). ACTION: None. 3 CLAS0002 MESSAGE: None 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 Continued Mapping Table ACTION: See Appendix A , “Submitting a CR,” of this manual. 11 CLAS0002 MESSAGE: None CAUSE: Send message to Probe failed trying to update an aged station address mapping for an IP address. ACTION: See Appendix A , “Submitting a CR,” of this manual. 12 CLAS0002 MESSAGE: None CAUSE: Send message to ARP failed trying to get station address mapping for an IP address. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued Net Timers Logging Location Codes Net Timers Logging Location Codes 1020 CLAS0003 MESSAGE: Out of resources 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 Continued Net Timers Logging Location Codes 1080 CLAS0002 MESSAGE: Cannot reset a systimer 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.
Logging Location Codes Continued 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 CR, noting this and previous Net Timers errors.
Logging Location Codes Continued Net Timers Logging Location Codes constraints. If necessary, submit an CR. 2080 CLAS0002 MESSAGE: Accessed a freed timer CAUSE: An attempt was made to free 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 freed twice. (PORT = net timer ID).
Logging Location Codes Continued Net Timers Logging Location Codes 2160 CLAS0002 MESSAGE: Not up for processing 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). ACTION: If this occurs during network shutdown, it can probably be ignored. If it occurs at any other time, submit an CR. Whether the net timer ID being freed was valid or not is not known.
Logging Location Codes Continued Net Timers Logging Location Codes ACTION: The timer has been left in an indeterminate state. Review information regarding the previous errors, for possible hints as to the cause. If necessary, submit an CR, noting this and previous Net Timers errors. 2220 CLAS0002 MESSAGE: Cannot start a timeout CAUSE: This is supplemental logging to a previous Net Timers error. A problem occurred while attempting to restart a stopped net timer.
Logging Location Codes Continued Net Timers Logging Location Codes 2300 CLAS0002 MESSAGE: Accessed a freed timer CAUSE: An attempt was made to stop 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 stopped 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 Continued Net Timers Logging Location Codes ACTION: This should never been seen outside the factory; submit an CR. 3160 CLAS0002 MESSAGE: Failed trap-call test CAUSE: Reported by Hewlett-Packard internal tests only. This indicates a net timer trap- routine reported a false error, leading to release of the popped timer. ACTION: This should never been seen outside the factory; submit an CR.
Logging Location Codes Continued Net Timers Logging Location Codes ACTION: No statistics were returned. If this error was reported by a Hewlett-Packard-supplied program, submit an CR against that program. 3300 CLAS0003 MESSAGE: Data truncated CAUSE: A caller specified statistics buffer was large enough to hold statistics, but not large enough to hold all the timer map data. Net Timers ran out of room trying to record a timer list head. Partial reads of timer map data are not recommended.
Logging Location Codes Continued Net Timers Logging Location Codes Control operations cannot be performed unless Net Timers is completely up. ACTION: No control operation was performed. If this occurs during network shutdown, it can probably be ignored. If it occurs at any other time, submit an CR. 3400 CLAS0003 MESSAGE: Bad/unknown function code CAUSE: An unrecognized or unsupported function code was passed in a call to NETTMR_CONTROL. Only supported control functions can be acted on.
Logging Location Codes Continued Net Timers Logging Location Codes ACTION: Net Timers will report the failure as a warning and continue with the shutdown. One message port may have been lost, but probably not any message frames; if this continues, the system could eventually run out of ports. Submit an CR.
Logging Location Codes Continued Net Timers Logging Location Codes are not allowed. ACTION: No harm was done, however some other module on the system, possibly CP, seems to be confused. If necessary, submit an CR. 4320 CLAS0002 MESSAGE: Create Object Failed CAUSE: After Net Timers computed its configuration during startup, an attempt to allocate context memory (port data area or PDA) using the system routine Create_object, failed.
Logging Location Codes Continued Net Timers Logging Location Codes 4380 CLAS0002 MESSAGE: Create Port Failed CAUSE: During startup, while attempting to create a message port to receive system-timer timeout messages, the system routine Create_port failed. The port is needed as a destination for timeout messages for the system timers which drive Net Timers (PARM = status from Create_port). ACTION: Net Timers failed to start; instead it cleaned up after itself and reported an error.
Logging Location Codes Continued NETIPC Logging Location Codes NETIPC Logging Location Codes 0 CLAS0000 MESSAGE: None CAUSE: Invalid port message. ACTION: Examine “Info” section of log record. See Appendix A , “Submitting a CR,” of this manual. 1 CLAS0000 MESSAGE: Internal error. CAUSE: Unable to create port in data segment table. ACTION: See Appendix A , “Submitting a CR,” of this manual. 2 CLAS0000 MESSAGE: Internal error. CAUSE: Unable to locate known entry in the name registry.
Logging Location Codes Continued NETIPC Logging Location Codes 14 CLAS0000 MESSAGE: Internal CAUSE: Unable to release timer. ACTION: See Appendix A , “Submitting a CR,” of this manual. 16 CLAS0000 MESSAGE: Internal error. CAUSE: Unable to create port message pool. ACTION: See Appendix A , “Submitting a CR,” of this manual. 17 CLAS0000 MESSAGE: Internal error. CAUSE: Call hpgetsysplabel failed. ACTION: See Appendix A , “Submitting a CR,” of this manual. 18 CLAS0000 MESSAGE: Internal error.
Logging Location Codes Continued NETIPC Logging Location Codes ACTION: See Appendix A , “Submitting a CR,” of this manual. 26 CLAS0000 MESSAGE: Internal error. CAUSE: Error in call to dict_find. ACTION: See Appendix A , “Submitting a CR,” of this manual. 27 CLAS0000 MESSAGE: Internal error. 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 Continued NETIPC Logging Location Codes 0 CLAS0001 MESSAGE: None CAUSE: Socket name registry full. ACTION: Call IPCNAMERASE to open slots in the socket name registry. 1 CLAS0001 MESSAGE: None CAUSE: Socket Give table full. ACTION: Call IPCGET to open slots in the socket give table. 2 CLAS0001 MESSAGE: Port DST table full. 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 Continued NFT Logging Location Codes NFT Logging Location Codes 1 CLAS0002 MESSAGE: None 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. 10 CLAS0002 MESSAGE: None CAUSE: Attempt to open file NFTCAT2 failed. Logging entry will also contain a file system error.
Logging Location Codes Continued NI Logging Location Codes NI Logging Location Codes 1 CLAS0005 MESSAGE: None CAUSE: Device was idle for configured Idle Timeout and timer was enabled for this device. Device will be disconnected (PARM = device ldev). ACTION: None. 4 CLAS0002 MESSAGE: None CAUSE: Protocol ID in Protocol Stop message was not found in NI’s PID table (PARM = Protocol ID). ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued NI Logging Location Codes 14 CLAS0002 MESSAGE: None 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 a CR,” of this manual. 15 CLAS0002 MESSAGE: None 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 a CR,” of this manual.
Logging Location Codes Continued NI Logging Location Codes 25 CLAS0002 MESSAGE: None 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 a CR,” of this manual. 28 CLAS0004 MESSAGE: None CAUSE: Network Interface Started (PARM = NI port data address). ACTION: None. 29 CLAS0004 MESSAGE: None CAUSE: Network Interface Stopped (PARM = NI port data address).
Logging Location Codes Continued NI Logging Location Codes ACTION: See Appendix A , “Submitting a CR,” of this manual. 52 CLAS0002 MESSAGE: None 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 a CR,” of this manual.
Logging Location Codes Continued NI Logging Location Codes 63 CLAS0002 MESSAGE: None CAUSE: While trying to send outbound data to a driver, send_msg failed (PARM = status from send_msg). ACTION: See Appendix A , “Submitting a CR,” of this manual. 64 CLAS0002 MESSAGE: None 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 a CR,” of this manual.
Logging Location Codes Continued NI Logging Location Codes 76 CLAS0002 MESSAGE: None 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 a CR,” of this manual. 77 CLAS0002 MESSAGE: None 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 Continued NI Logging Location Codes 84 CLAS0002 MESSAGE: None 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 a CR,” of this manual. 85 CLAS0002 MESSAGE: None CAUSE: During error recovery following a failure during transmission of outbound X.
Logging Location Codes Continued NI Logging Location Codes 105 CLAS0002 MESSAGE: None 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 Appendix A , “Submitting a CR.
Logging Location Codes Continued Path Result Code Table Path Result Code Table 0 MESSAGE: None CAUSE: Path resolved, path descriptor returned. ACTION: None. Informative message. 2 MESSAGE: None CAUSE: Path was verified path descriptor returned. ACTION: None. Informative message. 3 MESSAGE: None CAUSE: Path resolution has been deferred. ACTION: Wait for reply message on reply port. 5 MESSAGE: None CAUSE: Internal resource error. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued Path Result Code Table 14 MESSAGE: None Cause: No suitable path reports. ACTION: See Appendix A , “Submitting a CR,” of this manual. 16 MESSAGE: None Cause: Bad mapping table sequence number. ACTION: See Map Result Code Table. 17 MESSAGE: None Cause: Mapping table entry has aged. ACTION: See Map Result Code Table. 18 MESSAGE: None Cause: Path is in disconnecting state. ACTION: See Map Result Code Table. 19 MESSAGE: None Cause: Mapping Table is in a bad state.
Logging Location Codes Continued Probe Logging Location Codes Probe Logging Location Codes 7 CLAS0001 MESSAGE: None CAUSE: Bad or unexpected message received by PROBE Port (PARM = Message Function Code). ACTION: See Appendix A , “Submitting a CR,” of this manual. 14 CLAS0003 MESSAGE: None 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 Continued Probe Logging Location Codes 21 CLAS0002 MESSAGE: None CAUSE: Room allocated for node name and path report is too small (PARM = number of bytes short). ACTION: See Appendix A , “Submitting a CR,” of this manual. 22 CLAS0002 MESSAGE: None CAUSE: Timer popped which has no request outstanding (PARM = Time request ID). ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued Probe Logging Location Codes 33 CLAS0002 MESSAGE: None CAUSE: Attempt to map addresses failed (PARM = Path resolve error code). ACTION: See Appendix A , “Submitting a CR,” of this manual. 35 CLAS0004 MESSAGE: None CAUSE: PROBE Protocol Started. ACTION: Informative message. 36 CLAS0004 MESSAGE: None CAUSE: PROBE Protocol Stopped. ACTION: Informative message. 37 CLAS0004 MESSAGE: None CAUSE: PROBE Protocol Stopped (Delayed with Proxy). ACTION: None.
Logging Location Codes Continued Probe Logging Location Codes 48 CLAS0002 MESSAGE: None CAUSE: Attempt to add PROBE to the mapping table during INIT message failed (PARM = mapping error code). ACTION: See Appendix A , “Submitting a CR,” of this manual. 49 CLAS0002 MESSAGE: None CAUSE: Could not delete the PROBE entity from the mapping table in a terminate sequence (PARM = mapping error code). ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued PTOP Logging Location Codes PTOP Logging Location Codes 1 CLAS0003 MESSAGE: None CAUSE: Port Creation failed in response to a POPEN intrinsic. ACTION: See Appendix A , “Submitting a CR,” of this manual. 2 CLAS0003 MESSAGE: Internal error. CAUSE: Buffer Manager error. Port not allocated. ACTION: See Appendix A , “Submitting a CR,” of this manual. 3 CLAS0003 MESSAGE: None CAUSE: Socket connection failure. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued 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. 0 CLAS0001 MESSAGE: None CAUSE: Received an invalid NS format message (PARM = message function). ACTION: See Appendix A , “Submitting a CR,” of this manual. 1 CLAS0001 MESSAGE: None CAUSE: Received a port message before receiving the CP initialization message (PARM = message function).
Logging Location Codes Continued PXP PM Logging Location Codes 9 CLAS0001 MESSAGE: None CAUSE: A PXP internal resource error has been encountered. ACTION: See Appendix A , “Submitting a CR,” of this manual. 10 CLAS0001 MESSAGE: None CAUSE: A PXP internal error has been encountered. ACTION: See Appendix A , “Submitting a CR,” of this manual. 11 CLAS0001 MESSAGE: None CAUSE: A PXP internal resource error has been encountered. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued PXP PM Logging Location Codes ACTION: Repeated retransmissions suggest possible link or configuration problems. See PXP error code explanations. 19 CLAS0003 MESSAGE: None CAUSE: PXP request failed. Retransmission-retry maximum exceeded. Possible link or configuration problems. ACTION: See error 10 in the Chapter 10 , “Network Transport Protocol (PMERR) Error Messages.
Logging Location Codes Continued PXP PM Logging Location Codes 48 CLAS0001 MESSAGE: None CAUSE: A PXP internal resource error has been encountered. ACTION: See Appendix A , “Submitting a CR,” of this manual. 50 CLAS0003 MESSAGE: None CAUSE: An inbound packet was discarded as part of the shutdown sequence. ACTION: Informative message. 53 CLAS0002 MESSAGE: None CAUSE: An error result was returned on an N-Mclosetrace call for NetIPC tracing (PARM = NM error code).
Logging Location Codes Continued PXP PM Logging Location Codes 70 CLAS0003 MESSAGE: None 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 CR anyway. See Appendix A , “Submitting a CR.
Logging Location Codes Continued PXP SIP Logging Location Codes PXP SIP Logging Location Codes 0 CLAS0001 MESSAGE: None CAUSE: Received a port message before receiving the initialization message (PARM = message function). ACTION: See Appendix A , “Submitting a CR,” of this manual. 1 CLAS0001 MESSAGE: None CAUSE: Received an invalid CP message (PARM = message function). ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued PXP SIP Logging Location Codes 8 CLAS0004 MESSAGE: None CAUSE: The PXP PM has been started. ACTION: See Appendix A , “Submitting a CR,” of this manual. 9 CLAS0002 MESSAGE: None CAUSE: A socket could not be opened due to a port dst problem (PARM = error code). ACTION: See Appendix A , “Submitting a CR,” of this manual. 10 CLAS0002 MESSAGE: None CAUSE: A socket could not be opened due to a CREATEPORT' failure (PARM = PORT error code).
Logging Location Codes Continued PXP SIP Logging Location Codes ACTION: None. Informational message. 20 CLAS0006 MESSAGE: None CAUSE: Statistical summary for the deactivated PXP SIP. ACTION: None. Statistical information. 21 CLAS0004 MESSAGE: None CAUSE: The PXP SIP has been deactivated. ACTION: None. Nodal information. 22 CLAS0003 MESSAGE: None CAUSE: An inbound packet has been discarded because the destination PXP socket is not open. ACTION: None.
Logging Location Codes Continued PXP SIP Logging Location Codes ACTION: See PATH error explanations. 34 CLAS0003 MESSAGE: None 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. 35 CLAS0002 CLAS0003 MESSAGE: None CAUSE: The PXP SIP received an ICMP message from the IP module (PARM = ICMP type word). ACTION: None.
Logging Location Codes Continued 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. 1 CLAS003 MESSAGE: None CAUSE: RASERVER stack log buffer could not be allocated. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued RASERVER Logging Location Codes 10 CLAS003 MESSAGE: None CAUSE: Could not find a wait entry for nowait I/O which completed. ACTION: See Appendix A , “Submitting a CR,” of this manual. 11 CLAS003 MESSAGE: None CAUSE: No I/O pending when a nowait I/O completed. ACTION: See Appendix A , “Submitting a CR,” of this manual. 12 CLAS003 MESSAGE: None CAUSE: RFA services reported an error. ACTION: Repair the RFA error, if possible.
Logging Location Codes Continued RASERVER Logging Location Codes 20 CLAS005 MESSAGE: None CAUSE: Could not make connection nowait. ACTION: See Appendix A , “Submitting a CR,” of this manual. 21 CLAS005 MESSAGE: None CAUSE: Could not disable connection timeouts. ACTION: See Appendix A , “Submitting a CR,” of this manual. 22 CLAS002 MESSAGE: None CAUSE: RASERVER connection buffer could not be deallocated. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued RASERVER Logging Location Codes ACTION: See Appendix A , “Submitting a CR,” of this manual. 33 CLAS002 MESSAGE: None 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. 34 CLAS002 MESSAGE: None CAUSE: RASERVER failed to find a file control block. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued RASERVER Logging Location Codes 42 CLAS002 MESSAGE: None CAUSE: RASERVER could not allocate a compression buffer. ACTION: See Appendix A , “Submitting a CR,” of this manual. 43 CLAS002 MESSAGE: None CAUSE: RASERVER could not deallocate a compression buffer ACTION: See Appendix A , “Submitting a CR,” of this manual. 44 CLAS003 MESSAGE: None CAUSE: RASERVER detected an error while compressing data. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued Remote Link Manager Logging Location Codes Remote Link Manager Logging Location Codes 1 CLAS0001 MESSAGE: None CAUSE: RLM’s data structures are corrupted. ACTION: See Appendix A , “Submitting a CR,”of this manual. 3 CLAS0002 MESSAGE: None CAUSE: Send_msg procedure returned a bad status to the RLM. ACTION: See Appendix A , “Submitting a CR,” of this manual. 4 CLAS0002 MESSAGE: None CAUSE: Link Error occurred in unexpected state.
Logging Location Codes Continued Remote Link Manager Logging Location Codes 10 CLAS0003 MESSAGE: None CAUSE: RLM could not release some internal resources (PARM = Status returned by “new_release_table_entry”). ACTION: See Appendix A , “Submitting a CR,” of this manual. 11 CLAS0001 MESSAGE: None CAUSE: RLM attempted to release a resource that had already been released. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued Remote Link Manager Logging Location Codes 19 CLAS0002 MESSAGE: None CAUSE: RLM could not write outbound packet to buffer. ACTION: See Appendix A , “Submitting a CR,” of this manual. 20 CLAS0002 MESSAGE: None CAUSE: RLM could not read buffer containing inbound packet. ACTION: See Appendix A , “Submitting a CR,” of this manual. 21 CLAS0001 MESSAGE: None CAUSE: Mismatch in states between the DTC and the HP e3000.
Logging Location Codes Continued Remote Link Manager Logging Location Codes display additional logging messages. 28 CLAS0002 MESSAGE: None CAUSE: Disconnect reply received from linkn contained bad status. ACTION: See Appendix A , “Submitting a CR,” of this manual. 29 CLAS0002 MESSAGE: None CAUSE: Subsystem specified a bad parameter in a connect or disconnect request. ACTION: See Appendix A , “Submitting a CR,” of this manual. 30 CLAS0001 MESSAGE: None CAUSE: Control mismatch between DTC and HP e3000.
Logging Location Codes Continued Remote Link Manager Logging Location Codes 38 CLAS0002 MESSAGE: None CAUSE: RLM could not free a buffer. ACTION: See Appendix A , “Submitting a CR,” of this manual. 39 CLAS0002 MESSAGE: None CAUSE: State mismatch between DTC and Host. ACTION: See Appendix A , “Submitting a CR,” of this manual. (Make sure a dump is taken of both the DTC and the HP e3000.) 40 CLAS0002 MESSAGE: None CAUSE: DTC sent unknown packet to HP e3000.
Logging Location Codes Continued Remote Link Manager Logging Location Codes 48 CLAS0001 MESSAGE: None CAUSE: Interface problem between DTC and HP e3000. ACTION: See Appendix A , “Submitting a CR,” of this manual. 49 CLAS0002 MESSAGE: None CAUSE: Link sent a disconnect event for an unknown connection. ACTION: See Appendix A , “Submitting a CR,” of this manual. 50 CLAS0001 MESSAGE: None CAUSE: AFCP connection is in an invalid state for the event.
Logging Location Codes Continued Remote Link Manager Logging Location Codes ACTION: See Appendix A , “Submitting a CR,” of this manual. 60 CLAS0002 MESSAGE: None CAUSE: Invalid message received for current state. ACTION: See Appendix A , “Submitting a CR,” of this manual. 61 CLAS0003 MESSAGE: None CAUSE: Link has gone down. ACTION: Run appropriate diagnostics. If no error is found, see Appendix A , “Submitting a CR,” of this manual. 62 CLAS0001 MESSAGE: None CAUSE: Internal State Error.
Logging Location Codes Continued Remote Link Manager Logging Location Codes ACTION: Check status of DTC. 70 CLAS0005 MESSAGE: None CAUSE: Link went down abnormally during shutdown. ACTION: Check status of X.25 card on DTC. 71 CLAS0002 MESSAGE: None CAUSE: RLM could not release a semaphore. ACTION: See Appendix A , “Submitting a CR,” of this manual. 73 CLAS0002 MESSAGE: None CAUSE: RLM’s port is out of message frames. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued Remote Link Manager Logging Location Codes 84 CLAS0002 MESSAGE: None CAUSE: RLM could not free buffer. ACTION: See Appendix A , “Submitting a CR,” of this manual. 85 CLAS0002 MESSAGE: None CAUSE: RLM could not delete semaphore pool. ACTION: See Appendix A , “Submitting a CR,” of this manual. 88 CLAS0004 MESSAGE: None CAUSE: Link went down in an error condition. ACTION: Check the status of the DTC. 90 CLAS0002 MESSAGE: None CAUSE: RLM could not release semaphore.
Logging Location Codes Continued Remote Link Manager Logging Location Codes exhausted. ACTION: Contact your Hewlett-Packard representative and/or see Appendix A , “Submitting a CR,” of this manual. 101 CLAS0002 MESSAGE: None CAUSE: Could not obtain plabel for NL.PUB.SYS procedure “remote_link_manager.” Possible software installation problem (PARM = status returned by “hpgetsysplabel”). ACTION: Check the status of the DTC.
Logging Location Codes Continued Remote Link Manager Logging Location Codes ACTION: See Appendix A , “Submitting a CR,” of this manual. 109 CLAS0002 MESSAGE: None CAUSE: Link buffer size is too small. ACTION: Check X.25 and DTC Link configuration. If no problems are found, see Appendix A , “Submitting a CR,” of this manual. 110 CLAS0003 MESSAGE: None CAUSE: Could not open the file NMCONFIG.PUB.SYS (PARM = status returned by “nmconfopen”). ACTION: Check the nmconfig.pub.sys with the program “FSCHECK”.
Logging Location Codes Continued Remote Link Manager Logging Location Codes ACTION: See Appendix A , “Submitting a CR,” of this manual. 117 CLAS0003 MESSAGE: None CAUSE: RLM could not delete the RLM’s entry from the CM port dictionary (PARM = status returned by “dict_delete”). ACTION: See Appendix A , “Submitting a CR,” of this manual. 118 CLAS0002 MESSAGE: None CAUSE: RLM could not create the outbound buffer pool (PARM = status returned by “bmgr_create_pool”).
Logging Location Codes Continued Remote Link Manager Logging Location Codes 125 CLAS0004 MESSAGE: None CAUSE: RLM has been created (PARM = RLM’s port ID). ACTION: None. 126 CLAS0004 MESSAGE: None CAUSE: RLM has been shutdown. ACTION: None.
Logging Location Codes Continued RFA Logging Location Codes RFA Logging Location Codes 1 CLAS0003 MESSAGE: None 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 a CR,” of this manual. 2 CLAS0003 MESSAGE: None CAUSE: RFA was unable to deallocate one of its internal buffers.
Logging Location Codes Continued RFA Logging Location Codes system operator on the local or remote system. If not see Appendix A , “Submitting a CR.” 10 CLAS0003 MESSAGE: None 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. If user has enabled data compression for RFA transfers, this limit is 29000 bytes.
Logging Location Codes Continued RFA Logging Location Codes 16 CLAS0003 MESSAGE: None CAUSE: RFA could not turn on NetIPC socket data tracing. ACTION: If the local system is not out of disk space then see Appendix A , “Submitting a CR,” of this manual. 17 CLAS0003 MESSAGE: None CAUSE: RFA could not update information in the NS DSLINE table. ACTION: RFA may have run out of stack space. Run the program with an additional 2000 words of stack space.
Logging Location Codes Continued RFA Logging Location Codes NOWAIT IO is not currently supported on XL. See Appendix A , “Submitting a CR,” of this manual. ACTION: See Appendix A , “Submitting a CR,” of this manual. 24 CLAS0003 MESSAGE: None CAUSE: Unexpected error while creating an IOWAIT port for NOWAIT IO. ACTION: See Appendix A , “Submitting a CR,” of this manual. 25 CLAS0003 MESSAGE: None CAUSE: RFA was unable to create or delete an entry in the DSSERVER’s stack.
Logging Location Codes Continued RFA Logging Location Codes ACTION: If the user’s program a has opened too many NOWAIT RFA files or if it is attempting to read large blocks of data for each FREAD (16000 bytes per FREAD) then the program has reached RFA’s resource limits. If the program does neither then see Appendix A , “Submitting a CR,” of this manual. 32 CLAS0003 MESSAGE: None CAUSE: The RFA Server’s state tables indicate it is in an expected state.
Logging Location Codes Continued RPM Logging Location Codes RPM Logging Location Codes 1 CLAS0002 MESSAGE: None CAUSE: Data segment for RPM table could not be allocated. ACTION: See Appendix A , “Submitting a CR,” of this manual. 2 CLAS0002 MESSAGE: None CAUSE: Insufficient stack space to set critical. ACTION: See Appendix A , “Submitting a CR,” of this manual. 3 CLAS0003 MESSAGE: None CAUSE: NS global data segment does not exist. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued RPM Logging Location Codes ACTION: See Appendix A , “Submitting a CR,” of this manual. 11 CLAS0002 MESSAGE: None CAUSE: An invalid RPM message has been received. ACTION: See Appendix A , “Submitting a CR,” of this manual. 12 CLAS0005 MESSAGE: None CAUSE: Receive of an RPM Length Reply message failed. ACTION: See Appendix A , “Submitting a CR,” of this manual. 13 CLAS0005 MESSAGE: None CAUSE: Send of an RPM Create Request message failed.
Logging Location Codes Continued RPM Logging Location Codes 21 CLAS0005 MESSAGE: None CAUSE: Receive of an RPM Kill Request message failed. ACTION: See Appendix A , “Submitting a CR,” of this manual. 22 CLAS0005 MESSAGE: None CAUSE: Send of an RPM Kill Reply message failed. Invalid port message. ACTION: See Appendix A , “Submitting a CR,” of this manual. 23 CLAS0005 MESSAGE: None CAUSE: Send of an RPM Length Reply message failed. ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued RPM Logging Location Codes 35 CLAS0003 MESSAGE: None CAUSE: RPMDAD adoption under DSDAD failed during a session shutdown. ACTION: See Appendix A , “Submitting a CR,” of this manual. 36 CLAS0003 MESSAGE: None 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 a CR,” of this manual. 37 CLAS0003 MESSAGE: None CAUSE: JSMAIN locking mechanism failed during an adopt.
Logging Location Codes Continued 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 is a 5-digit decimal field with the following sub-fields: NMMMM where N is the transport module number and MMMM is defined by the logging module.
Logging Location Codes Continued TCP Logging Locations 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 packet which is in error or which violated the protocol or had to be ignored due to the local state.
Logging Location Codes Continued TCP Logging Locations 50- Buffer Manager 59- Unexpected escape 60–79 standard informative errors (etc.
Logging Location Codes Continued TCP Logging Locations 98–99 Statistical Logging 98- SIP statistics 99- PM Statistics 10001 CLAS0002 MESSAGE: None CAUSE: NWTM_SEND_MSG returned a bad status while trying to send the inbound connection shut request (remote fin received indication) to IPC. ACTION: PARM is NWTM error returned. Submit an CR.
Logging Location Codes Continued TCP Logging Locations ACTION: PARM is NWTM error returned. Submit an CR. 10009 CLAS0002 MESSAGE: None CAUSE: NWTM_RESET_FILE_EVENT returned a bad status while trying to reset the write bit for a connection due to becoming unwritable. ACTION: PARM is NWTM error returned. Submit an CR. 10010 CLAS0002 MESSAGE: None CAUSE: NWTM_SET_FILE_EVENT returned a bad status while trying to set the write bit for a connection due to becoming writable. ACTION: PARM is NWTM error returned.
Logging Location Codes Continued TCP Logging Locations 10017 CLAS0002 MESSAGE: None CAUSE: NWTM_SET_FILE_EVENT returned a bad status while trying to set the readable and writable bits due to a connection shutting down. ACTION: PARM is NWTM error returned. Submit an CR. 10101 CLAS0002 MESSAGE: None CAUSE: Bad status returned from send_msg while sending a negative advice message to the TCP SIP. ACTION: PARM is ports error returned. Submit an CR.
Logging Location Codes Continued TCP Logging Locations 10111 CLAS0002 MESSAGE: None CAUSE: Bad status returned from purge_port while trying to delete the TCP SIP port. This was during a system shutdown. ACTION: PARM is ports error returned. Submit an CR. 10112 CLAS0002 MESSAGE: None CAUSE: Bad status returned from create_pool while trying to create a message pool for the TCP SIP. This was during protocol start. ACTION: PARM is ports error returned. Submit an CR.
Logging Location Codes Continued TCP Logging Locations further NETCONTROL commands will also hang. ACTION: PARM is ports error returned. Submit an CR. Reboot if necessary to restart transport. 10119 CLAS0002 MESSAGE: None CAUSE: Bad status returned from send_msg while trying to send a traceoff_reply message to NETCP. NETCP may be in a hung state, if so further NETCONTROL commands will also hang. ACTION: PARM is ports error returned. Submit an CR. Reboot if necessary to restart transport.
Logging Location Codes Continued TCP Logging Locations 10202 CLAS0002 MESSAGE: None CAUSE: New_release_table_entry returned a bad status while we were trying to deallocate a connection entry. ACTION: PARM is table management error returned. Submit an CR. 10203 CLAS0002 MESSAGE: None CAUSE: New_release_table_entry returned a bad status while we were trying to deallocate a socket entry. ACTION: PARM is table management error returned. Submit an CR.
Logging Location Codes Continued TCP Logging Locations 10210 CLAS0002 MESSAGE: None CAUSE: There was a bad status returned from delete_table while releasing the TCP connection table. This would happen after network or system shutdown. ACTION: PARM is table management error returned. Submit an CR. 10211 CLAS0002 MESSAGE: None CAUSE: There was a bad status returned from delete_table while releasing the TCP socket table. This would happen after network or system shutdown.
Logging Location Codes Continued TCP Logging Locations 10401 CLAS0005 MESSAGE: None CAUSE: PATHs failed to resolve a path to the requested destination. The connection request has failed. ACTION: PARM is path resolution status. Possible nodal/media failure or misconfiguration. Diagnose path resolution failure. Submit an CR if necessary. 10402 CLAS0005 MESSAGE: None CAUSE: PATHs failed to resolve a path to the requested destination. The passive connection attempt has failed.
Logging Location Codes Continued TCP Logging Locations will abort. ACTION: Informative message. No action required. Try to determine why route to remote host has failed. Possibilities include node/media failure and misconfiguration. 10501 CLAS0002 MESSAGE: None CAUSE: Nettmr_reset_timer call returned an error. ACTION: PARM is nettmr error returned. Submit an CR. 10502 CLAS0002 MESSAGE: None CAUSE: Nettmr_free_timer call returned an error. ACTION: PARM is nettmr error returned. Submit an CR.
Logging Location Codes Continued TCP Logging Locations 10704 CLAS0002 MESSAGE: None CAUSE: Attempt to unfreeze user data vector failed. ACTION: PARM is memory manager error returned. Submit an CR. 10801 CLAS0002 MESSAGE: None CAUSE: NMCLOSETRACE returned a bad status during an IPCCONTROL traceoff call. ACTION: PARM is the NMS error returned. Submit an CR. 10802 CLAS0002 MESSAGE: None CAUSE: NMOPENLOG returned a bad status during network startup. ACTION: PARM is the NMS error returned. Submit an CR.
Logging Location Codes Continued TCP Logging Locations 10809 CLAS0002 MESSAGE: None CAUSE: NMWRITETRACE call returned a bad status while tracing a reset packet being sent out by the TCP SIP. ACTION: PARM is the NMS error returned. Submit an CR. 10810 CLAS0002 MESSAGE: None CAUSE: NMWRITETRACE call returned a bad status while tracing an ICMP message. ACTION: PARM is the NMS error returned. Submit an CR.
Logging Location Codes Continued TCP Logging Locations ACTION: PARM is NWS error returned. Submit an CR. 10818 CLAS0002 MESSAGE: None CAUSE: NWWRITETRACE returned a bad status while attempting to write a message or procedure call trace record for the TCP SIP. ACTION: PARM is NWS error returned. Submit an CR. 10819 CLAS0002 MESSAGE: None CAUSE: DICT_DELETE returned a bad status while attempting to remove the TCP SIP from the cm port dictionary during shutdown. ACTION: PARM is the returned error.
Logging Location Codes Continued TCP Logging Locations 11201 CLAS0002 MESSAGE: None CAUSE: TCP internal timer state was inconsistent with actual timer activity. ACTION: Submit an CR. 11301 CLAS0003 MESSAGE: None CAUSE: TCP wanted to adjust the length of data of a composite buffer beyond the end of the last buffer in the chain. ACTION: Submit an CR. 11401 CLAS0003 MESSAGE: None CAUSE: Bad status returned from a call to the tcp_read_completor in the loopback send path. ACTION: Submit an CR.
Logging Location Codes Continued TCP Logging Locations 11901 CLAS0002 MESSAGE: None CAUSE: Attempt to add a network to TCP’s IP list table when the table is full. Connection is added to temporary list. ACTION: PARM is source IP address of connection. Check configuration for number of configured networks. If OK, then submit an CR. 11902 CLAS0002 MESSAGE: None CAUSE: Connection could not be found in TCP’s IP list table when it is shutting down. ACTION: PARM is source IP address of connection. Submit an CR.
Logging Location Codes Continued TCP Logging Locations Otherwise, submit an CR. 12102 CLAS0003 MESSAGE: None 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 CR.
Logging Location Codes Continued TCP Logging Locations ACTION: Remote protocol error indication. Use tracing or line analysis to capture connection dialog. Report an error against remote implementation. 12302 CLAS0003 MESSAGE: None 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.
Logging Location Codes Continued TCP Logging Locations 12501 CLAS0003 MESSAGE: None 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 Continued TCP Logging Locations packet using tracing or a line analyzer. Report an error against the remote implementation. 12507 CLAS0003 MESSAGE: None 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.
Logging Location Codes Continued TCP Logging Locations 13201 CLAS0005 MESSAGE: None CAUSE: An attempt was made to start a TCP connection; however, the protocol was not active (i.e., was stopped). ACTION: Informative message. Start the network if needed. 13202 CLAS0003 MESSAGE: None 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.
Logging Location Codes Continued TCP Logging Locations ACTION: PARM is value of offending control parameter. Fix offending program/service. 14001 CLAS0003 MESSAGE: None CAUSE: Number of configured retransmission retries exceeded. Connection will abort. ACTION: Excessive retransmissions indicate a possible route/gate failure or possible end node failure or possible misconfiguration.
Logging Location Codes Continued TCP Logging Locations 14203 CLAS0005 MESSAGE: None CAUSE: A valid reset packet was received on a connection. The connection will abort. ACTION: Informative message. No action required. This message normally appears because the remote connection half was terminated abruptly by the user through an abortive IPC shutdown. Many services use this type of shutdown. Remote abortions also occur when errors are encountered on the remote system.
Logging Location Codes Continued TCP Logging Locations ACTION: PARM is escape code of escape. Submit an CR. 15905 CLAS0002 MESSAGE: None CAUSE: An unexpected escape occurred within the procedure tcp_passive_open_reply or some procedural unit called by it. ACTION: PARM is escape code of escape. Submit an CR. 15906 CLAS0002 MESSAGE: None 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 CR.
Logging Location Codes Continued TCP Logging Locations 15912 CLAS0002 MESSAGE: None CAUSE: An unexpected escape occurred within the procedure tcp_receive_reply or some procedural unit called by it. ACTION: PARM is escape code of escape. Submit an CR. 15913 CLAS0002 MESSAGE: None 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 CR.
Logging Location Codes Continued TCP Logging Locations ACTION: PARM is escape code of escape. Submit an CR. 15921 CLAS0002 MESSAGE: None CAUSE: An unexpected escape occurred within the procedure tcp_sip_icmp_req or some procedural unit called by it. ACTION: PARM is escape code of escape. Submit an CR. 15922 CLAS0002 MESSAGE: None 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 CR.
Logging Location Codes Continued TCP Logging Locations 15930 CLAS0002 MESSAGE: None CAUSE: An unexpected escape occurred within the procedure tcp_module_deconfig or some procedural unit called by it. ACTION: PARM is escape code of escape. Submit an CR. 15931 CLAS0002 MESSAGE: None 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 CR.
Logging Location Codes Continued TCP Logging Locations 16102 CLAS0005 MESSAGE: None 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. 16103 CLAS0005 MESSAGE: None CAUSE: A connection tossed a packet because of an invalid sequence number.
Logging Location Codes Continued TCP Logging Locations 16108 CLAS0005 MESSAGE: None CAUSE: The TCP SIP tossed a packet from a half open connection because the TCP SIP was already processing another such packet. ACTION: Informative message. No action required. 16109 CLAS0005 MESSAGE: None CAUSE: The TCP SIP tossed a packet from a half open connection because the TCP SIP was already processing another such packet. ACTION: Informative message. No action required.
Logging Location Codes Continued TCP Logging Locations 16202 CLAS0005 MESSAGE: None CAUSE: An attempt was made to retransmit a packet in loopback. ACTION: Repeated occurrences indicated a software problem. 16301 CLAS0005 MESSAGE: None CAUSE: The retransmission interval for a packet has expired without receipt of an acknowledgment from the remote connection half. ACTION: This indicates network congestion, or a noisy or loss prone network. Occasional occurrences are considered normal.
Logging Location Codes Continued TCP Logging Locations 17002 CLAS0005 MESSAGE: None CAUSE: We received an inbound syn for a connection that has already been established (same local and destination SAPS and IP addresses). We will ignore this SYN packet. ACTION: Informative message. No action required. 17101 CLAS0005 MESSAGE: None 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.
Logging Location Codes Continued TCP Logging Locations Submit an CR. 17404 CLAS0002 MESSAGE: None CAUSE: Error in protocol initialization. ACTION: Look for logging indication explaining TCP SIP initialization failure. Submit an CR. 17405 CLAS0002 MESSAGE: None CAUSE: TCP KSO pointer value was NIL. ACTION: Suspect error in protocol startup. Look for logging indication explaining TCP protocol startup failure. Submit an CR. 17501 CLAS0002 MESSAGE: None CAUSE: Bad port message of “DS” type came to the TCP SIP.
Logging Location Codes Continued TCP Logging Locations ACTION: Informational message. No action required. 18201 CLAS0005 MESSAGE: None CAUSE: TCP connection deactivated without error. ACTION: Informational message. No action required. 18301 CLAS0005 MESSAGE: None CAUSE: TCP socket opened. ACTION: Informational message. No action required. 18401 CLAS0005 MESSAGE: None CAUSE: TCP socket closed. ACTION: Informational message. No action required. 18501 CLAS0004 MESSAGE: None CAUSE: TCP protocol started.
Logging Location Codes Continued TCP Logging Locations 18901 CLAS0005 MESSAGE: None CAUSE: Path_verify message from NETCP processed for parm> ip_addr. ACTION: Informational message. No action required. 19801 CLAS0006 MESSAGE: None CAUSE: The global TCP statistics are being recorded. ACTION: Statistical message. No action required. 19802 CLAS0006 MESSAGE: None CAUSE: Specific statistics related to the efficiency of the hash table are being recorded. ACTION: Statistical message. No action required.
Logging Location Codes Continued UDP Logging Locations UDP Logging Locations 1 CLAS0002 MESSAGE: None 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 a CR,” of this manual. 2 CLAS0002 MESSAGE: None CAUSE: The send of the datagram open reply message to NetIPC failed (PARM = Result code returned from send_msg). ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued UDP Logging Locations request). ACTION: Check to ensure that unique or well-known SAPs are being used. If OK, then see Appendix A , “Submitting a CR,” of this manual. 10 CLAS0002 MESSAGE: None CAUSE: Attempt to free an object to virtual space management failed (PARM = Result code from release_object call). ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued UDP Logging Locations 19 CLAS0004 MESSAGE: None CAUSE: Logging the start of the UDP module (PARM = UDP’s port ID). ACTION: Informative message. 20 CLAS0002 MESSAGE: None CAUSE: Attempt to add UDP to the ports data dictionary failed (PARM = Result code from the dict_add call). ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued UDP Logging Locations ACTION: See Appendix A , “Submitting a CR,” of this manual. 28 CLAS0002 MESSAGE: None CAUSE: Conversion of IPU dst to a native mode pointer failed (PARM = Result code returned by convert_dst). ACTION: See Appendix A , “Submitting a CR,” of this manual. 30 CLAS0002 MESSAGE: None CAUSE: Attempt to write user data into the buffer for the outbound datagram failed (PARM = Result code returned by bmgr_write_buffer).
Logging Location Codes Continued UDP Logging Locations ACTION: See Appendix A , “Submitting a CR,” of this manual. 37 CLAS0002 MESSAGE: None CAUSE: Attempt to write the IP options into the outbound buffer failed (PARM = Result code returned by bmgr_write_buffer). ACTION: See Appendix A , “Submitting a CR,” of this manual. 38 CLAS0002 MESSAGE: None CAUSE: Attempt to free a buffer when closing associated socket failed (PARM = Result code returned by bmgr_write_buffer).
Logging Location Codes Continued UDP Logging Locations 46 CLAS0003 MESSAGE: None CAUSE: Attempt to get a path descriptor for the destination in the datagram send request failed (PARM = Result code returned by ns_path_resolve). ACTION: Check the IP address of the destination specified in the IPCSENDTO call. Also make sure the necessary networks are started. If problems persist then see Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued 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.
Logging Location Codes Continued X.25 Logging Location Codes ACTION: See Appendix A , “Submitting a CR,” of this manual. 104 CLAS0005 MESSAGE: None 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).
Logging Location Codes Continued X.25 Logging Location Codes 111 CLAS0002 MESSAGE: None CAUSE: X.25 received a message for an unknown connection (PARM = connection points). ACTION: See Appendix A , “Submitting a CR,” of this manual. 112 CLAS0002 MESSAGE: None CAUSE: Internal Error. Map_Add_Rout failed (PARM = status from Map_add_rout). ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued X.25 Logging Location Codes 119 CLAS0002 MESSAGE: None CAUSE: Internal Error. Map_X25_Update failed (PARM = status from Map_X25_update). ACTION: See Appendix A , “Submitting a CR,” of this manual. 125 CLAS0002 MESSAGE: None CAUSE: Internal Error. Convert_dst failed (PARM = status from Convert_dst). ACTION: See Appendix A , “Submitting a CR,” of this manual. 126 CLAS0002 MESSAGE: None CAUSE: Internal Error. IPC sent zero bytes of data to X.25 for transmission.
Logging Location Codes Continued X.25 Logging Location Codes 133 CLAS0002 MESSAGE: None CAUSE: The configuration file contains more than the allowed number of SVC paths (PARM = number of SVC paths). ACTION: See Appendix A , “Submitting a CR,” of this manual. 134 CLAS0002 MESSAGE: None CAUSE: An error occurred while reading an SVC path from the configuration file (PARM = length). ACTION: See Appendix A , “Submitting a CR,”of this manual. 135 CLAS0002 MESSAGE: None CAUSE: Internal Error.
Logging Location Codes Continued X.25 Logging Location Codes 141 CLAS0004 MESSAGE: None CAUSE: Maximum number of link entries already in use. Cannot add another link entry. ACTION: See Appendix A , “Submitting a CR,” of this manual. 142 CLAS0002 MESSAGE: None CAUSE: Internal Error. Map_Del_Entity failed (PARM = Map_Del_Entity). ACTION: See of this manual. 143 CLAS0002 MESSAGE: None CAUSE: Internal Error. Bmgr_Delete_Pool failed (PARM = Bmgr_delete_pool).
Logging Location Codes Continued X.25 Logging Location Codes ACTION: See Appendix A , “Submitting a CR,” of this manual. 150 CLAS0002 MESSAGE: None CAUSE: X.25 received an unknown message format (PARM = message format). ACTION: See Appendix A , “Submitting a CR,” of this manual. 151 CLAS0002 MESSAGE: None 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 a CR,” of this manual.
Logging Location Codes Continued X.25 Logging Location Codes 159 CLAS0005 MESSAGE: None CAUSE: An inbound IPC connection was opened (PARM = Device ID, VC number). ACTION: None. This is an informative message. 160 CLAS0005 MESSAGE: None CAUSE: A connection was closed (PARM = Device ID, VC number). ACTION: None. This is an informative message. 161 CLAS0003 MESSAGE: None 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 Continued X.25 Logging Location Codes 166 CLAS0005 MESSAGE: None 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 Continued X.25 Logging Location Codes 172 CLAS0005 MESSAGE: None 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. Check that the program with this socket address is running.
Logging Location Codes Continued X.25 Logging Location Codes ACTION: Check the diagnostic code returned. Verify that all components are operational. 179 CLAS0005 MESSAGE: None CAUSE: An outgoing connection request was rejected because the AFCP connection was closed. ACTION: Check that the DTC is operational. Try again later. 180 CLAS0005 MESSAGE: None CAUSE: An incoming IPC connection request was rejected by the DTC (PARM = Device ID, VC number, cause, diagnostic).
Logging Location Codes Continued X.25 Logging Location Codes ACTION: Define a new facility set for this configuration, or assign an existing facility set. 187 CLAS0005 MESSAGE: None CAUSE: An outgoing IPC connection request was rejected because the specified Call User Data field is too long. ACTION: Either decrease the size of the call user data field or use the fast select facility, or use the “no address” flag.
Logging Location Codes Continued X.25 Logging Location Codes a CR,” of this manual. 193 CLAS0002 MESSAGE: Internal Error. CAUSE: Netfc_Delete_Pool failed on regular semaphore pool (PARM = status from Netfc_delete_pool). ACTION: If this happens frequently, the transport will not be able to open new connections. See Appendix A , “Submitting a CR,” of this manual. 194 CLAS0002 MESSAGE: Internal Error. CAUSE: Netfc_Create_Pool failed right after a Netfc_Delete_Pool (PARM = status from Netfc_create_pool).
Logging Location Codes Continued X.25 Logging Location Codes 202 CLAS0005 MESSAGE: None 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. 203 CLAS0005 MESSAGE: None CAUSE: An N-Disconnect packet was sent because an IPC user or application rejected an incoming connection request (PARM = Device ID, VC number, cause, diagnostic). ACTION: None.
Logging Location Codes Continued X.25 Logging Location Codes 210 CLAS0002 MESSAGE: None CAUSE: Reading the configuration buffer failed on a Netcontrol Update (PARM = status and length). ACTION: See Appendix A , “Submitting a CR,” of this manual. 211 CLAS0002 MESSAGE: None CAUSE: There are more facility sets in the configuration file than allowed (PARM = number of facility sets). ACTION: See Appendix A , “Submitting a CR,” of this manual.
Logging Location Codes Continued X.25 Logging Location Codes 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. If you want Fast Select, modify the facility set.
Logging Location Codes Continued X.25 Logging Location Codes connection request was received by the system. (PARM = Status from Map_find_best_device). ACTION: Verify that the link between the system and the DTC is up: From the system, check for a non-zero LDEV in the NETCONTROL STATUS;NI=x25niname> display. From OpenView DTC Manager, check the host entries at the end of the X.25 level 3 status display. If the link is up, try the connection again.
Submitting a CR A Submitting a CR For further assistance from Hewlett-Packard, document the problem as a CR (Change 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 a CR — 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 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 Table B-1 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 Measur
Subsystem Identifiers Table B-1 Subsystem Identifiers 149 System Memory Dump 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
Subsystem Identifiers Table B-1 Subsystem Identifiers 182 Data com Network Management Services 183 Data com Version Control 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 Table B-1 Subsystem Identifiers 214 NM to CM intrinsic stubs 215 RJE Bisync PSI Driver (IND) 216 SDLC PSI Driver (IND) 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
Subsystem Identifiers Table B-1 Subsystem Identifiers 504 HPUX Symbolic Debugger (CLL) 505 FORTRAN run time library 506 Compiler library (CLL) 507 Scientific library (CLL) 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 Netwo
Subsystem Identifiers Table B-1 Subsystem Identifiers 711 CM Probe Module 712 CM Dial Module 713 CM Paths Module 714 CM General Protocol Module 715 CM General NI Module 716 CM IPC Module 717 CM X.
Subsystem Identifiers Table B-1 Subsystem Identifiers 743 Net Sockets 744 Central Configurator Manager 745 NS Control Process 746 NS ARP 747 NS Net Timers 748 Streams/iX 749 TIO Trace Manager 750 FDDI LAN Driver 751 DLPI Provider 752 NWIX 1111 NS Mapping Table 724 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 Table C-1 Native Mode NS 3000/iX Buffer Error Codes Error Code Meaning -9; bfm_illegal_max_users -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;
Native Mode and Compatibility Mode Buffer Manager Error Codes Table C-1 Native Mode NS 3000/iX Buffer Error Codes Error Code Meaning -38; bfm_no_next_buf -39; bfm_illegal_append_offset -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_
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 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 -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_
Native Mode and Compatibility Mode Buffer Manager 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 -01 1, { invalid_pool_id, ditto } 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
Index Numerics 100Base-T, 163, 279, 377 100VG-AnyLAN, 163, 279, 377 B Byes sent/received, 473 C Checksum errors, 473 CI errors, 13 internal errors, 13 invalid options, 13 resource errors, 13 syntax errors, 13 warnings, 13 Cn ass pkts sent/recd, 473 D Data Communication Logical Device Manager DCLDM, 479 DCLDM, 479 DIAL, 534 Distributed Terminal Controller DTC, 479 driver status, 170, 286, 383 DTC, 479 E Ethernet LAN, 479 F FDDI, 479 fiber distributed data interface FADDI, 479 Flags/Flags1/Flags2, 474 G GATE
Index U UDP, 534 User pkts sent/recd, 473 User sends/receives, 473 Using Log Files, 470 X X.25, 479, 534 X.
