TCP/IP Management Programming Manual

Event Management
HP NonStop TCP/IP Management Programming Manual—529636-001
7-2
Critical Events
Critical Events
Events reported by the TCP/IP subsystem are divided into two classes: critical events
and noncritical events. Critical events are errors and warnings for which the
consequences could be serious, such as a hardware failure or a software error from
which there is no automatic recovery. Noncritical events are often expected events that
are informational, such as a summary state change.
To determine whether or not an event message reports a critical event, examine the
value of the event-message token ZEMS-TKN-EMPHASIS. If the value is
ZSPI-VAL-TRUE, the event message reports a critical event. If the value is
ZSPI-VAL-FALSE, the event is not critical. In addition, check the value of the token
19 NEW-PROC-ERR LISTNER could not start a new process
20 XFER-ERR TRANSFER error
21 PARAM-ERR Parameter error
22 ADDR-ERR Address error
23 SOCK-ERR Socket error
24 PROTO-ERR Prototype error
25 RECV-OPEN-FAIL $RECEIVE open failed
26 SSINT-FAILED SPI buffer initialization error
27 CANT-HANDLE-AF Protocol not supported
28 OUT-OF-MBUF No buffer space for request
29 TRACE-STOP-ERR DSM trace stop failed
30 SSINT-FAILED1 SPI initialization error
31 NEW-CL-MBUF No buffer space for request
32 NON-ZERO-RUN-SOCK Scheduling sockets failure
33 NO-BACKUP TCP/IP no longer has a backup process
34 INVALID-CPU-NUM Invalid backup CPU specified
35 CANT-START-BACKUP Could not start new backup process
36 BACKUP-IS-DEAD Backup process has abended
37 BACKUP-IS-STARTED Backup process has started
38 CONN-ESTAB-GATE X.25 connection established using gateway
39 CHKPT-FAILED Checkpoint to backup process failed
40 NO-BACKUP-CPU No backup CPU specified
41 IOP-QIO-ERR Error occurred on QIO driver call
42 QIOMODE-ON Subnet is now using QIO direct mode
Table 7-1. TCP/IP Event Messages (page 2 of 2)
Event
Number
Symbolic Name
(ZTCI-EVT- ) Description