HPlogo NS 3000/iX Error Messages Reference Manual > Chapter 21 Logging Location Codes

Logging Subsystems

MPE documents

Complete PDF
Table of Contents
Index

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 Subsystems and Class Names"

Table 21-1 Logging Subsystems and Class Names

Subsystem Name

Class Name

Events
SUB0000CLAS0000Informative messages
SUB0003CLAS0001Serious internal error
Network TransportCLAS0002Internal error/operator attention
CLAS0003Non-critical errors
CLAS0004Nodal messages (start/stop)
CLAS0005Informative messages
CLAS0006Statistical information
SUB0004CLAS0000Notable events
DC/LDM
SUB0005CLAS0000Internal errors
Network IPCCLAS0001Resource errors
CLAS0002Informative messages
SUB0006CLAS0002Resource errors
Network ServicesCLAS0003Internal errors
CLAS0004Detailed events (enable with NSCONTROL LOG)
CLAS0005NetIPC internal errors
SUB0008CLAS0000Internal errors
Link Mgr
SUB0018CLAS0000Errors
Trace Mgr
SUB0024CLAS0001Informational messages
NMMGR
SUB0025CLAS0001Errors
LAN driverCLAS0002Warnings
CLAS0003Informational messages
SUB0028CLAS0010Errors
Lap B LinkCLAS0012Informational messages
SUB0040CLAS0001Catastrophic errors
Remote Link ManagerCLAS0002Serious errors
CLAS0003Notable errors
CLAS0004Nodal messages (start/stop)
CLAS0005Informative messages
SUB0057CLAS0001Fatal errors
SNMPCLAS0002Serious errors
CLAS0003Warnings
CLAS0004Informational messages
SUB0061CLAS0001Errors
Token Ring LinkCLAS0002Warnings
CLAS0003Informational messages
SUB0067CLAS0001Errors
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.

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 21-1 "Formatted Log Record".

Table 21-2 Network Transport Entities

Entity

Entity Number

Description

ARP124The address resolution protocol for use on FDDI, Token Ring, and Ethernet LAN networks.
Control Process66NETCP is created by the NETCONTROL command. It handles network startup and shutdown.
Dial ID112The 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 NI1The network interface for gateway half connections such as LAP-B links.
IP109Internet Protocol. It handles packet fragmentation assembly and store-forward, compatible with industry standards.
IP Update110IPU maintains IP internet routing tables and manages gateway.
L2Resolve140Part of the process between NS Transport and SNA Transport that provides NS over SNA/XL functionality. (This product is obsolete.)
LAN NI0The network interface for the LAN connection performs functions for IP store and forward over IEEE 802.3 and Ethernet links.
Loopback NI9The network interface for software loopback performs loopback by converting outbound messages to inbound messages.
Mapping Table128A collection of procedures for the maintenance of intranetwork routing information.
Path113The path resolution procedures determine the outbound path and resources for a connection.
Point-to-Point (Router) NI3The network interface for the point-to-point connections to LAP-B devices, both direct-connect and dial.
Probe111The Probe protocol is a proprietary address-resolution protocol used to resolve nodenames on IEEE 802.3 networks.
PXP PM105The Packet Exchange Protocol module performs certain internal protocol functions for Paths and NetIPC.
PXP SIP106The PXP Socket Interface Port functions as a controller for the PXP protocol. It handles the creation of sockets and connections.
SNA NI10The network interface for SNA connections. (This product is obsolete.)
TCP PM103The 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 SIP104The 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.
UDP141The UDP module is responsible for handling connectionless protocol functions, for transmission of datagram packets, for applications not requiring reliable connections.
User Interface 101The NETCONTROL command user interface. Interprets all Transport commands and passes them to the control process if they are valid, refer to.
X.25 NI6The network interface for X.25 connections passes packets between TCP/IP and the Multiple Connection Manager module for X.25 devices, which in turn interfaces to the DTC.
X.25 PM118Interfaces with TCP to provide X.25 protocol functions.
Token Ring NI11The network interface for Token Ring connections performs functions for IP store and forward over these links.
FDDI NI12The network interface for Fiber Distributed Data Interface connections performs functions for IP store and forward over these links.
ICMP138The ICMP server process echoes Ping packets back to other systems.
PXP Read Completor143This is a procedure which is called by IP to process incoming packets.
UDP Read Completor144This is a procedure which is called by IP to process incoming packets.
TCP Read Completor145This is a procedure which is called by IP to process incoming packets.
ICMP Read Completor146This is a procedure which is called by IP to process incoming packets.
IP Read Completor147This is a procedure which is called by the link driver to pass incoming packets into Transport.
ARP Read Completor148This is a procedure which is called by the link driver to pass incoming ARP packets into Transport.
PROBE Read Completor149This is a procedure which is called by the link driver to pass incoming PROBE packets into Transport.
IP Module Configurator and Deconfigurator151These procedures create an instance of the IP protocol module when an NI is started, and destroy it when the NI is stopped.
UDP Module Configurator and Deconfigurator152These procedures create the UDP general protocol when Transport starts, and destroy it when Transport stops.
ICMP Server Module Configurator and Deconfigurator153 These procedures create the ICMP Server process when Transport starts, and destroy it when Transport stops.
IP Module Configurator and Deconfigurator154These procedures create an instance of the L2Resolve protocol module when an NI is started, and destroy it when the NI is stopped.
X25 Module Configurator and Deconfigurator155These procedures create an instance of the X.25 protocol module when an NI is started, and destroy it when the NI is stopped.
NI Module Configurator and Deconfigurator156These procedures create and destroy an NI which will operate in a mode specific to the type of link it is configured to use.
PROBE Module Configurator and Deconfigurator157These procedures create an instance of the PROBE protocol module when an NI is started, and destroy it when the NI is stopped.
IPU Module Configurator and Deconfigurator158These procedures create the IP Update module when Transport starts, and destroy it when Transport stops.
DIAL Module Configurator and Deconfigurator159These procedures create an instance of the DIAL protocol module when an NI is started, and destroy it when the NI is stopped.
PXP Module Configurator and Deconfigurator160These procedures create the PXP general protocol when Transport starts, and destroy it when Transport stops.
Net Timers161This module provides increased capacity and control over timers used by the TCP and ARP Transport modules.

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 Chapter 10 "Network Transport Protocol (PMERR) Error Messages" in 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.

Network Services Subsystem Logging

The Network Services subsystem (SUB0006) modules are described in Table 21-3 "Network Service Modules". It also lists the corresponding Network Services Logging table for each module.

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 Chapter 6 "Virtual Terminal (VT ERROR) Error Messages" section of this manual. Each error message number listed in the VT error message table 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 "Virtual Terminal (VT ERROR) Error Messages" apply to individual VT logging messages. As described, 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 NS 3000/iX.

Other Network Services — such as Network File Transfer, Program-to-Program Communication, and Remote File Access, return error information to the user regardless of logging configuration for the Network Services subsystem of NS 3000/iX.

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. Most user-repairable errors are returned in the result parameter of the NetIPC intrinsics. These error codes are listed in Chapter 5 "NetIPC (SOCKERRS) Error Messages" of this manual.

Table 21-3 Network Service Modules

Module

Description
BFMThe NS Buffer Management module provides for the allocation of buffers for the other NS modules. (The NS Buffer Management module is different fro the Buffer Management software used by the transport and translator.)
CXThe 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.
DSDADThe DSDAD process controls the initiation and termination of network services, including creation of server processes.
DSSERVERThere is a DSSERVER process created for each use of the RFA, VT, or RPM services. The DSSERVER process receives and accesses files and terminals required by the service.
DSUTILThe 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.
ENVThe 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.
NFTNetwork File Transfer
RASERVERThere 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.
RFARemote File Access and Remote Database (IMAGE) Access.
RPMRemote Process Management
VTVirtual Terminal

Logging codes for the NetIPC subsystem of the associated links are listed in this chapter in the section called "NetIPC Logging Location Codes."



Logging Formats

Using Log Files