NS 3000/iX Error Messages Reference Manual HP 3000 MPE/iX Computer Systems Edition 9 36923-90041 E1098 Printed in: U.S.A. October 1998 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. Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard. This document contains proprietary information which is protected by copyright. All rights reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws. Restricted Rights Legend Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Rights for non-DOD U.S. Government Departments and Agencies are as set forth in FAR 52.227-19 (c) (1,2). Acknowledgments UNIX is a registered trademark of The Open Group. Hewlett-Packard Company 3000 Hanover Street Palo Alto, CA 94304 U.S.A. © Copyright 1988–1994, and 1998 by Hewlett-Packard Company Contents 1. CIERR Error Messages Network Services Environment Error Messages . 26 2. DSERR Error Messages 3. NS/NFTERR and NS/NFTWARN Messages 4. NFT/3000 Error Messages 5. NetIPC (SOCKERRS) Error Messages 6. Virtual Terminal (VT ERROR) Error Messages 7. Network Services Information Messages 8. Remote File Access Error Messages 9. Remote Process Management Error Messages 10. Network Transport Protocol (PMERR) Error Messages 11. FPARSE Error Messages 12. NETXPORTERR Error Messages 13. NSCONTROL Error Messages 14. VALERR and VALWARN Messages 15. LAN, LAN/Console, Token Ring LAN Error Messages 16. 100VG-AnyLAN and 100Base-T Error Messages SDI Generic Status Values . 164 SDI Driver Specific Status Values . 170 Logging Sublocation Codes . 200 17. FDDI Error Messages 18. LAP-B Link Error Messages LAP-B Link Startup Error Messages . 286 LAP-B Link Driver Error Messages . 291 LAP-B Link Shutdown Error Messages . 306 3 Contents 19. Logging Location Codes Logging Formats . 310 Logging Subsystems . 311 Network Transport Subsystem Logging . 312 PARM Value . 313 Network Services Subsystem Logging . 316 Network IPC Subsystem Logging . 318 Using Log Files . 319 Internal Errors . 319 Informative and Non-Critical Errors. 319 Statistics Logging Example . 320 ARP Logging Location Codes . 324 Control Process Logging Location Codes . 328 NS Configurator Logging Location Codes . 381 CX Logging Location Codes. 387 DC/LDM Logging Location Codes. 390 Dial ID Logging Location Codes . 395 DSDAD Logging Location Codes. 404 DSSERVER Logging Location Codes . 407 DSUTIL Logging Location Codes . 409 ENV Logging Location Codes . 410 ICMP Type/Code Words. 412 IP Logging Location Codes . 416 IPU Logging Location Codes . 425 L2Resolve Logging Location Codes. 428 Mapping Table . 433 Net Timers Logging Location Codes. 435 NETIPC Logging Location Codes . 449 NFT Logging Location Codes . 453 NI Logging Location Codes . 454 Path Result Code Table . 462 Probe Logging Location Codes . 464 PTOP Logging Location Codes . 468 PXP PM Logging Location Codes . 469 PXP SIP Logging Location Codes . 474 RASERVER Logging Location Codes . 478 Remote Link Manager Logging Location Codes . 483 RFA Logging Location Codes . 496 RPM Logging Location Codes . 502 TCP Logging Locations . 506 UDP Logging Locations. 542 X.25 Logging Location Codes . 549 A. Submitting an SR B. Subsystem Identifiers C. Native Mode and Compatibility Mode Buffer Manager Error Codes 4 Figures Figure 19-1 . A Formatted Log Record . .310 Figure 19-2 . Class 3, A Non-Critical Transport Error . .320 Figure 19-3 . Logging Statistics Example. .321 5 Figures 6 Tables Table 19-1. Logging Subsystems and Class Names . .311 Table 19-2. Network Transport Entities. .313 Table 19-3. Network Service Modules. .317 Table B-1. Subsystem Identifiers . .569 Table C-1. Native Mode NS 3000/iX Buffer Error Codes. .577 Table C-2. Compatibility Mode Buffer Error Codes . .580 Preface This manual contains most messages and errors generated by NS 3000/iX subsystems for the MPE/iX 6.0 release. What if the Error Is If you have encountered an error that is not in this manual, here are Not in this Manual some ideas on how you might find the error: • If it is an NMMGR error, or error from any of the Node Management Services Utilities, refer to Appendix A in Using The Node Management Services (NMS) Utilities. • If you have PCs using NS to connect to the MPE/iX system, consult the terminal emulator or networking manuals for your PC software for the error. • If you cannot find the error at all, submit an SR and call your Hewlett-Packard representative. (See Appendix A, “Submitting an SR.”) Special Note MPE/iX, Multiprogramming Executive with Integrated POSIX, is the latest in a series of forward-compatible operating systems for the HP 3000 line of computers. In HP documentation and in talking with HP 3000 users, you will encounter references to MPE XL, the direct predecessor of MPE/iX. MPE/iX is a superset of MPE XL. All programs written for MPE XL will run without change under MPE/iX. You can continue to use MPE XL system documentation, although it may not refer to features added to the operating system to support POSIX (for example, hierarchical directories). Finally, you may encounter references to MPE V, which is the operating system for HP 3000s, not based on the PA-RISC architecture. MPE V software can be run on the PA-RISC HP 3000 (Series 900) in what is known as compatibility mode. 9 10 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. For the Network Service commands, more than one CI error may be displayed (although only in a session; a job aborts when the first CI error is detected). These CI errors are held in CATALOG.PUB.SYS, message set 2 (CI errors). When a CI error is detected, the CIERR job control word is set to the error number. The CI errors fit into four categories: • Syntax errors or invalid options: These errors result from user errors when issuing the command, and can be readily corrected. • Warnings: Warnings are issued when a command is still executable, but the results may not be what you intended. These result from cases where conflicting options are specified. The warning informs you which option was actually used (or not used). • Resource errors: These errors occur when a system resource needed for the execution of the command is not available. They should be rare. If they occur, you can wait and reissue the command later, when the resource may be available. If resource errors happen frequently, the configuration or resource allocation of the system may be inadequate. The system manager and SE should then look into the problem. Resource errors are also logged using Network Management logging, to log class 6, subclass 2. • Internal errors: These errors indicate that the Network Service software is malfunctioning. If they ever occur, an HP representative should be notified. Internal errors are also logged using Network Management logging, to log class 6, subclass 3. MESSAGE: INTERNAL DS ERROR — NO KEYWORD TABLE. 5000 CAUSE: The NS Keyword Table was not allocated during system startup or prior to an NS command execution. ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: INTERNAL DS ERROR — NO ASGLOBAL DST. 5001 CAUSE: The NS global data segment was not allocated during system startup, or has been lost. Chapter 1 11 CIERR Error Messages ACTION: See Appendix A, “Submitting an SR,” of this manual. MESSAGE: INVALID ASCAT.NET.SYS MESSAGE CATALOG. 5002 CAUSE: The ASCAT.NET.SYS message catalog exists, but is not in the proper format. It may have been overwritten by a file that is not a properly prepared message catalog. ACTION: Check that the message sets of the ASCAT.NET.SYS catalog are correct. Run the MAKECAT utility to prepare the message catalog properly. MESSAGE: INTERNAL DS ERROR — COULD NOT ALLOCATE KEYWORD BUFFER. 5003 CAUSE: The NS Keyword Table is not large enough to contain all the keywords from the ASCAT.NET.SYS catalog. ACTION: See Appendix A, “Submitting an SR,”of this manual. MESSAGE: ASCAT.NET.SYS MESSAGE CATALOG DOES NOT EXIST. 5004 CAUSE: The ASCAT.NET.SYS catalog file is missing; the NS command keywords cannot be loaded. ACTION: Inform your system manager; install ASCAT.NET.SYS from the NS product tape. MESSAGE: INTERNAL DS ERROR — COULD NOT CREATE KEYWORD TABLE. 5005 CAUSE: The NS Keyword Table extra data segment could not be allocated, because of insufficient memory or free DSTs. ACTION: Inform your system manager; increase the number of configured DSTs or obtain more memory. MESSAGE: NON-NUMERIC CHARACTER IN ENVIRONMENT NUMBER. 5006 CAUSE: Syntax error in an environment number #Lxxx (in DSLINE)or xxx (in REMOTE), where one or more of the values for x is not numeric. ACTION: Correct the syntax error and reissue the command. MESSAGE: NON-ALPHANUMERIC CHARACTER IN ENVIRONMENT ID OR NODE NAME. 5007 CAUSE: Syntax error in an environment identifier in a DSLINE or REMOTE, where one or more characters are not alphanumeric.