HP 3000 Manuals HP 3000 Manuals
Logging Subsystems
Each subsystem of NS3000/iX has its own set of classes for logging
events. Table 18-1 summarizes the subsystem logging classes.
Table 18-1. Logging Subsystems and Class Names
------------------------------------------------------------------------------
| |
| Subsystem Name Class Name Events |
| |
------------------------------------------------------------------------------
| |
| SUB0000 CLAS0000 Informative messages |
| |
- -
| SUB0003 CLAS0001 Serious internal error |
| |
| Network Transport CLAS0002 Internal error/operator attention |
| |
| CLAS0003 Non-critical errors |
| |
| CLAS0004 Nodal messages (start/stop) |
| |
| CLAS0005 Informative messages |
| |
| CLAS0006 Statistical information |
| |
- -
| SUB0004 CLAS0000 Notable events |
| |
| DC/LDM |
| |
- -
| SUB0005 CLAS0000 Internal errors |
| |
| Network IPC CLAS0001 Resource errors |
| |
| CLAS0002 Informative messages |
| |
- -
| SUB0006 CLAS0002 Resource errors |
| |
| Network Services CLAS0003 Internal errors |
| |
| CLAS0004 Detailed events (enable with NSCONTROL |
| LOG) |
| |
| CLAS0005 NetIPC internal errors |
| |
- -
| SUB0008 CLAS0000 Internal errors |
| |
| Link Mgr |
| |
- -
| SUB0018 CLAS0000 Errors |
| |
| Trace Mgr |
| |
- -
| SUB0024 CLAS0001 Informational messages |
| |
| NMMGR |
| |
- -
| SUB0025 CLAS0001 Errors |
| |
| LAN driver CLAS0002 Warnings |
| |
| CLAS0003 Informational messages |
| |
------------------------------------------------------------------------------
Table 18-1. Logging Subsystems and Class Names (cont'd)
------------------------------------------------------------------------------
| |
| Subsystem Name Class Name Events |
| |
------------------------------------------------------------------------------
| |
| SUB0028 CLAS0010 Errors |
| |
| Lap B Link CLAS0012 Informational messages |
| |
- -
| SUB0040 CLAS0001 Catastrophic errors |
| |
| Remote Link CLAS0002 Serious errors |
| Manager |
| |
| CLAS0003 Notable errors |
| |
| CLAS0004 Nodal messages (start/stop) |
| |
| CLAS0005 Informative messages |
| |
- -
| SUB0057 CLAS0001 Fatal errors |
| |
| SNMP CLAS0002 Serious errors |
| |
| CLAS0003 Warnings |
| |
| CLAS0004 Informational messages |
| |
- -
| SUB0061 CLAS0001 Errors |
| |
| Token Ring Link CLAS0002 Warnings |
| |
| CLAS0003 Informational messages |
| |
- -
| SUB0067 CLAS0001 Errors |
| |
| FDDI Lan |
| |
------------------------------------------------------------------------------
All logging is configured in NMCONFIG.PUB.SYS. See Using the Node
Management Services (NMS) Utilities manual for more details on logging
and configuration.
Network Transport Subsystem Logging
Logging location codes are used by all modules of the Network Transport
(SUB0003) to give uniqueness to each and every point at which an event is
logged. Location codes make it easy to locate the logging call in the
source code, as well as to be able to explain a particular instance of an
error. Since the same error code, for example, may be logged in
different parts of the same module, the error may be the same, but the
meaning and action to take may be different.
Logging is the only source of information for Network Transport
activities. The user or network manager cannot monitor Network Transport
events if logging is not enabled for that subsystem.
Table 18-2 describes the Network Transport entities and lists their
corresponding tables found in this section. Each Network Transport
logging table contains a list of the logging location code, logging
class, explanation, and action for an individual logging message. The
explanation for each logging location code includes the Internal Event
description and Parm description, if relevant, as shown in the typical
formatted log example in Figure 18-1.
The Path Network Transport Entity logs no event information.
PARM Value.
Many Network Transport logging records contain important information in
the Parameter value. This Parameter number indicates the shutdown
reason.
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.
Parameter meanings for the "PXP Deactivated," "PXP Deactivated w/Error,"
and "PXP Statistics" internal events are listed in the "Network Transport
Protocol Errors" in Chapter 10 of this manual, which are the Protocol
module errors returned by IPCCHECK. In general, refer to a specific
logging location code explanation for definition of Parameter meaning.
For definition of the Parameter value of an ICMP logging location, refer
to the "ICMP Type/Code Words" in this chapter.
NOTE In most instances, the Parm value supplied with the explanations in
this chapter will be of interest only to your Hewlett-Packard
representative.
Table 18-2. Network Transport Entities
------------------------------------------------------------------------------
| |
| Entity Entity Description |
| Number* |
| |
------------------------------------------------------------------------------
| |
| 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. |
| |
| Dial ID 112 The DIAL protocol is used only for |
| point-to-point links including |
| gateway-half links. It manages |
| autodialing of telephone numbers and |
| connection establishment security. |
| |
| Gateway Half NI 1 The network interface for gateway half |
| connections such as LAP-B links. |
| |
| IP 109 Internet Protocol. It handles packet |
| fragmentation assembly and store-forward, |
| compatible with industry standards. |
| |
| IP Update 110 IPU maintains IP internet routing tables |
| and manages gateway. |
| |
| L2Resolve 140 Part of the process between NS Transport |
| and SNA Transport that provides NS over |
| SNA/XL functionality. (This product is |
| obsolete.) |
| |
| LAN NI 0 The network interface for the LAN |
| connection performs functions for IP store |
| and forward over IEEE802.3 and Ethernet |
| links. |
| |
| Loopback NI 9 The network interface for software |
| loopback performs loopback by converting |
| outbound messages to inbound messages. |
| |
| Mapping TabIe 128 A collection of procedures for the |
| maintenance of intranetwork routing |
| information. |
| |
| Path 113 The path resolution procedures determine |
| the outbound path and resources for a |
| connection. |
| |
| Point-to-Point 3 The network interface for the |
| (Router) NI point-to-point connections to LAP-B |
| devices, both direct-connect and dial. |
| |
------------------------------------------------------------------------------
Table 18-2. Network Transport Entities (cont'd)
------------------------------------------------------------------------------
| |
| Entity Entity Description |
| Number* |
| |
------------------------------------------------------------------------------
| |
| Probe 111 The Probe protocol is a proprietary |
| address-resolution protocol used to |
| resolve nodenames on IEEE802.3 networks. |
| |
| PXP PM 105 The Packet Exchange Protocol module |
| performs certain internal protocol |
| functions for Paths and NetIPC. |
| |
| PXP SIP 106 The PXP Socket Interface Port functions as |
| a controller for the PXP protocol. It |
| handles the creation of sockets and |
| connections. |
| |
| 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. |
| |
| TCP SIP 104 The TCP socket interface port functions as |
| a controller for the TCP protocol. It |
| handles the creation of sockets and |
| connections, tracing, and other operations |
| not possible on the ICS. |
| |
| UDP 141 The UDP module is responsible for handling |
| connectionless protocol functions, for |
| transmission of datagram packets, for |
| applications not requiring reliable |
| connections. |
| |
| User Interface 101 The NETCONTROL command user interface. |
| (NETCONTROL Interprets all Transport commands and |
| ERRORS, refer to passes them to the control process if they |
| chapter 12) are valid. |
| |
| X.25 NI 6 The network interface for X.25 connections |
| passes packets between TCP/IP and the |
| Multiple Connection Manager module for |
| X.25 devices, which in turn interfaces to |
| the DTC. |
| |
------------------------------------------------------------------------------
Table 18-2. Network Transport Entities (cont'd)
------------------------------------------------------------------------------
| |
| Entity Entity Description |
| Number* |
| |
------------------------------------------------------------------------------
| |
| X.25 PM 118 Interfaces with TCP to provide X.25 |
| protocol functions. |
| |
| Token Ring NI 11 The network interface for Token Ring |
| connections performs functions for IP |
| store and forward over these links. |
| |
| FDDI NI 12 The network interface for Fiber |
| Distributed Data Interface connections |
| performs functions for IP store and |
| forward over these links. |
| |
| ICMP 138 The ICMP server process echoes Ping |
| packets back to other systems. |
| |
| PXP Read Completor 143 This is a procedure which is called by IP |
| to process incoming packets. |
| |
| UDP Read Completor 144 This is a procedure which is called by IP |
| to process incoming packets. |
| |
| TCP Read Completor 145 This is a procedure which is called by IP |
| to process incoming packets. |
| |
| ICMP Read 146 This is a procedure which is called by IP |
| Completor to process incoming packets. |
| |
| IP Read Completor 147 This is a procedure which is called by the |
| link driver to pass incoming packets into |
| Transport. |
| |
| ARP Read Completor 148 This is a procedure which is called by the |
| link driver to pass incoming ARP packets |
| into Transport. |
| |
| PROBE Read 149 This is a procedure which is called by the |
| Completor link driver to pass incoming PROBE packets |
| into Transport. |
| |
| IP Module 151 These procedures create an instance of the |
| Configurator and IP protocol module when an NI is started, |
| Deconfigurator and destroy it when the NI is stopped. |
| |
| UDP Module 152 These procedures create the UDP general |
| Configurator and protocol when Transport starts, and |
| Deconfigurator destroy it when Transport stops. |
| |
------------------------------------------------------------------------------
Table 18-2. Network Transport Entities (cont'd)
------------------------------------------------------------------------------
| |
| Entity Entity Description |
| Number* |
| |
------------------------------------------------------------------------------
| |
| ICMP Server Module 153 These procedures create the ICMP Server |
| Config- urator and process when Transport starts, and destroy |
| Deconfigurator it when Transport stops. |
| |
| IP Module 154 These procedures create an instance of the |
| Configurator and L2Resolve protocol module when an NI is |
| Deconfigurator started, and destroy it when the NI is |
| stopped. |
| |
| X25 Module 155 These procedures create an instance of the |
| Configurator and X.25 protocol module when an NI is |
| Deconfigurator started, and destroy it when the NI is |
| stopped. |
| |
| NI Module 156 These procedures create and destroy an NI |
| Configurator and which will operate in a mode specific to |
| Deconfigurator the type of link it is configured to use. |
| |
| PROBE Module 157 These procedures create an instance of the |
| Config- urator and PROBE protocol module when an NI is |
| Deconfigurator started, and destroy it when the NI is |
| stopped. |
| |
| IPU Module 158 These procedures create the IP Update |
| Configurator and module when Transport starts, and destroy |
| Deconfigurator it when Transport stops. |
| |
| DIAL Module 159 These procedures create an instance of the |
| Configurator and DIAL protocol module when an NI is |
| Deconfigurator started, and destroy it when the NI is |
| stopped. |
| |
| PXP Module 160 These procedures create the PXP general |
| Configurator and protocol when Transport starts, and |
| Deconfigurator destroy it when Transport stops. |
| |
| Net Timers 161 This module provides increased capacity |
| and control over timers used by the TCP |
| and ARP Transport modules. |
| |
------------------------------------------------------------------------------
* In the tables above, the entity numbers are not normally needed.
However, they may appear in logging messages or formatted logfile output
under some circumstances.
Network Services Subsystem Logging
The Network Services subsystem (SUB0006) modules are described in Table
18-3. Table 18-3 also lists the corresponding Network Services Logging
table for each module.
Table 18-3. Network Service Modules
-----------------------------------------------------------------------------
| |
| Module Description |
| |
-----------------------------------------------------------------------------
| |
| BFM The NS Buffer Management module provides for the |
| allocation of buffers for the other NS modules. (The |
| NS Buffer Management module is different from the |
| Buffer Management software used by the transport and |
| translator.) |
| |
| CX The Command Executor module parses and executes the NS |
| commands DSLINE, REMOTE, and NSCONTROL.It is also the |
| primary user interface (through the REMOTE command) to |
| the VT service. |
| |
| DSDAD The DSDAD process controls the initiation and |
| termination of network services, including creation of |
| server processes. |
| |
| DSSERVER There is a DSSERVER process created for each use of |
| the RFA, VT, or RPM services. The DSSERVER process |
| receives and processes protocol messages for the |
| service, and accesses files and terminals required by |
| the service. |
| |
| DSUTIL The DSUTIL module contains miscellaneous procedures |
| used by the other NS modules. Included are routines |
| for management of certain NS data structures and |
| handling of process and session termination. |
| |
| ENV The Environment module manages the information from |
| DSLINE commands that is used by the various Network |
| Services. This includes environment attributes, |
| remote sessions, and various service-related |
| information. |
| |
| NFT Network File Transfer |
| |
| RASERVER There is an RASERVER process 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. |
| |
| RFA Remote File Access and Remote Database (IMAGE) Access. |
| |
| RPM Remote Process Management |
| |
| VT Virtual Terminal |
| |
-----------------------------------------------------------------------------
Logging Messages for the Network Services (SUB0006) are listed under each
individual service.
The NS Buffer Management module (BFM) logs no event information.
The logging messages for NS Subsystem Modules are listed in this chapter.
However, event messages for the VT module are listed in the "Virtual
Terminal Errors (VT ERRORs)" section of this manual. Each error message
number listed in the VT error message table in Chapter 6 is identical to
a logging message error number found in the log file for the VT module.
"Actions" advised for individual VT errors listed in Chapter 6 apply to
individual VT logging messages.
As described in Chapter 6, VT and ENV messages are displayed to the user
on $STDLIST. However these messages are displayed on $STDLIST only if
logging is enabled for the Network Services subsystem of NS3000/iX.
Other Network Services - such as Network File Transfer,
Program-to-Program Communication, and Remote File Access - return error
information to the user regardless of logging configuration for the
Network Services subsystem of NS3000/iX.
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 NetIPC3000/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. Most user-repairable errors are
returned in the result parameter of the NetIPC intrinsics. These error
codes are listed in the "NetIPC (SOCKERR) Errors" in Chapter 5 of this
manual.
Logging codes for the NetIPC subsystem of the associated links are listed
in this chapter in the section called "NetIPC Logging Location Codes."