HP 3000 Manuals HP 3000 Manuals
NI Logging Location Codes
1 CLAS0005 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 Cause: Protocol ID in Protocol Stop message was not
found in NI's PID table (PARM = Protocol ID).
Action: See "Submitting an SR" in appendix A of this
manual.
5 CLAS0002 Cause: PID table is too small for the number of
protocols being started for this NI (PARM = Protocol
ID which could not be started).
Action: See "Submitting an SR" in appendix A of this
manual.
6 CLAS0002 Cause: CP asked NI to stop a device which NI could
not locate in its device tables (PARM = device ID).
Action: See "Submitting an SR" in appendix A of this
manual.
7 CLAS0002 Cause: Device table is too small for the number of
devices being started for this NI, or a device was
started twice by CP (PARM = Device ID).
Action: See "Submitting an SR" in appendix A of this
manual.
11 CLAS0002 Cause: NI received data on a Protocol ID which has no
match in PID table (PARM = Protocol ID).
Action: See "Submitting an SR" in appendix A of this
manual.
13 CLAS0002 Cause: Dial Protocol owns the device, but another
protocol was sent data from the remote node (PARM =
Violating Protocol ID).
Action: If this happens frequently, carefully check
the configurations on both the local and remote
systems. See "Submitting an SR" in appendix A of this
manual.
14 CLAS0002 Cause: On arrival of inbound data, a send_msg to the
upper layer protocol failed (PARM = status from
send_msg).
Action: See "Submitting an SR" in appendix A of this
manual.
15 CLAS0003 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 "Submitting an SR" in appendix A of this
manual.
18 CLAS0002 Cause: A bad or unexpected message was received by
the NI (PARM = Message Function Code).
Action: See "Submitting an SR" in appendix A of this
manual.
19 CLAS0002 Cause: While trying to send outbound loopback data
back, a send_msg failed (PARM = status from send_msg).
Action: See "Submitting an SR" in appendix A of this
manual.
21 CLAS0002 Cause: While trying to send outbound data to a router
driver via DC/LDM, a send_msg failed (PARM = status
from send_msg).
Action: See "Submitting an SR" in appendix A of this
manual.
22 CLAS0002 Cause: Transport sent outbound data to NI for a
Protocol ID which has no match in the PID table for
this NI (PARM = Protocol ID).
Action: See "Submitting an SR" in appendix A of this
manual.
23 CLAS0003 Cause: While attempting to send outbound data, NI
discovered the route ID in the message was out of
date, so the outbound packet was discarded (PARM =
route ID from route table).
Action: See "Submitting an SR" in appendix A of this
manual.
24 CLAS0002 Cause: A protocol other than PROBE attempted to send
a multicast packet, disallowed by the NI (PARM =
Protocol ID).
Action: See "Submitting an SR" in appendix A of this
manual.
25 CLAS0002 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 "Submitting an SR" in
appendix A of this manual.
28 CLAS0004 Cause: Network Interface Started (PARM = NI port data
address).
Action: None.
29 CLAS0004 Cause: Network Interface Stopped (PARM = NI port data
address).
Action: None.
30 CLAS0002 Cause: Trouble starting the idle device timer of the
NI (PARM = status from get_timer).
Action: See "Submitting an SR" in appendix A of this
manual.
44 CLAS0002 Cause: While trying to send a connect request to a
driver, a send_msg failed (PARM = status from
send_msg).
Action: See "Submitting an SR" in appendix A of this
manual.
46 CLAS0002 Cause: CP asked NI to disconnect a device which NI
could not find in its device table (PARM = connect
ID).
Action: See "Submitting an SR" in appendix A of this
manual.
48 CLAS0002 Cause: While trying to send a disconnect request to a
driver, a send_msg failed (PARM = status from
send_msg).
Action: See "submitting an SR" in appendix A of this
manual.
49 CLAS0002 Cause: CP asked NI to connect a device which NI could
not find in its device table (PARM = link ID).
Action: See "Submitting an SR" in appendix A of this
manual.
51 CLAS0002 Cause: After receiving a connect confirmation event
from a driver, NI could not find the protocol for that
device type, either X.25 or SNA, in its PID table.
Action: See "Submitting an SR" in appendix A of this
manual.
52 CLAS0002 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 "Submitting an SR" in appendix A of this
manual.
53 CLAS0002 Cause: A driver acknowledged disconnection of a link
which NI could not find in its tables (PARM = Protocol
ID).
Action: See "Submitting an SR" in appendix A of this
manual.
55 CLAS0002 Cause: After receiving a disconnect confirmation
event from a driver, NI could not find the protocol
for that device type, either X.25 or SNA, in its PID
table.
Action: See "Submitting an SR" in appendix A of this
manual.
56 CLAS0002 Cause: After receiving a disconnect confirmation
event from a driver, send_msg failed trying to forward
a similar message to the protocol (PARM = status from
send_msg).
Action: See "Submitting an SR" in appendix A of this
manual.
58 CLAS0002 Cause: After receiving a connect reply from a driver,
send_msg failed trying to forward a similar message to
the sender of the original connect (PARM = status from
send_msg).
Action: See "Submitting an SR" in appendix A of this
manual.
59 CLAS0002 Cause: After receiving a disconnect reply from a
driver, NI could not locate information about the
original request in its tables (PARM = message ID).
Action: See "Submitting an SR" in appendix A of this
manual.
60 CLAS0002 Cause: After receiving a disconnect reply from a
driver, send_msg failed trying to forward a similar
message to the sender of the original disconnect (PARM
= status from send_msg).
Action: See "Submitting an SR" in appendix A of this
manual.
63 CLAS0002 Cause: While trying to send outbound data to a
driver, send_msg failed (PARM = status from send_msg).
Action: See "Submitting an SR" in appendix A of this
manual.
64 CLAS0002 Cause: NI received inbound data from a driver, for a
link which NI could not find in its tables (PARM =
link ID).
Action: See "Submitting an SR" in appendix A of this
manual.
67 CLAS0002 Cause: While processing inbound data from a driver,
send_msg failed trying to forward the data to the
protocol (PARM = status from send_msg).
Action: See "Submitting an SR" in appendix A of this
manual.
68 CLAS0002 Cause: CP asked NI to connect a device which NI could
not find in its device table (PARM = device ID).
Action: See "Submitting an SR" in appendix A of this
manual.
71 CLAS0002 Cause: When attempting to create a free pool of
device and protocol entries, new_create_table failed
(PARM = status from new_create_table).
Action: See "Submitting an SR" in appendix A of this
manual.
72 CLAS0002 Cause: When attempting to create a table to hold
information about outstanding X.25 requests,
new_create_table failed (PARM = status from
new_create_table).
Action: See "Submitting an SR" in appendix A of this
manual.
73 CLAS0002 Cause: While processing inbound data from a driver,
NI was able to locate the input device in its device
table, but then could not locate the corresponding
protocol in the protocol table.
Action: See "Submitting an SR" in appendix A of this
manual.
75 CLAS0002 Cause: Bad or unexpected function code received by NI
port in a control reply message from driver (PARM =
function code).
Action: See "Submitting an SR" in appendix A of this
manual.
76 CLAS0002 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 "Submitting an SR" in appendix A of this
manual.
77 CLAS0002 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).
Action: See "Submitting an SR" in appendix A of this
manual.
78 CLAS0002 Cause: While trying to delete one of NI's tables
during shutdown, delete_table failed (PARM = status
from delete_table).
Action: See "Submitting an SR" in appendix A of this
manual.
79 CLAS0002 Cause: After receiving a connect reply from a driver,
NI could not locate information about the original
request in its tables (PARM = message ID).
Action: See "Submitting an SR" in appendix A of this
manual.
80 CLAS0002 Cause: Bad or unexpected function code received by NI
port in a async event message from driver (PARM =
function code).
Action: See "Submitting an SR" in appendix A of this
manual.
81 CLAS0002 Cause: Bad or unknown message received by NI port on
inbound data subqueues (PARM = message descriptor).
Action: See "Submitting an SR" in appendix A of this
manual.
82 CLAS0002 Cause: During error recovery processing of a failed
disconnect request, send_msg failed trying to report
the problem back to the sender of the original
disconnect (PARM = status from send_msg).
Action: See "Submitting an SR" in appendix A of this
manual.
83 CLAS0002 Cause: During error recovery processing of a failed
connect request, send_msg failed trying to report the
problem back to the sender of the original connect
(PARM = status from send_msg).
Action: See "Submitting an SR" in appendix A of this
manual.
84 CLAS0002 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 "Submitting an SR" in appendix A of this
manual.
85 CLAS0002 Cause: During error recovery following a failure
during transmission of outbound X.25 data,
netfc_release failed (PARM = status from
netfc_release).
Action: See "Submitting an SR" in appendix A of this
manual.
86 CLAS0002 Cause: During error recovery following a failure
during reception of inbound X.25 data, netfc_release
failed (PARM = status from netfc_release).
Action: See "Submitting an SR" in appendix A of this
manual.
101 CLAS0002 Cause: When attempting to create a table to hold
information about outstanding SNA requests,
new_create_table failed (PARM = status from
new_create_table).
Action: See "Submitting an SR" in appendix A of this
manual.
102 CLAS0002 Cause: While starting an FDDI device, NI was unable
to read the FDDI station address.
Action: The station address should be available any
time the FDDI driver has been started. See
"Submitting an SR" in appendix A of this manual.
103 CLAS0002 Cause: An attempt was made to send a packet over a
LAPB link which did not have extended addressing
specified in the packet.
Action: Extended addressing is always required for
LAPB links. See "Submitting an SR" in appendix A of
this manual.
104 CLAS0002 Cause: After forming the extended address for an
outbound LAPB packet, NI encountered an error tyring
to write that address into the packet.
Action: Something is wrong with the outbound buffer.
See "Submitting an SR" in appendix A of this manual.
105 CLAS0002 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 "Submitting an SR" in appendix A of this manual.
106 CLAS0002 Cause: When NI attempted to send an outbound LAN,
FDDI, or Token Ring packet by calling the driver's
outbound write initiator routine, that routine
reported an error.
Action: Something is wrong with the driver or the SDI
address passed with the packet. See "Submitting an
SR" in appendix A of this manual.