G06.24 ReadMe

Recovery: .Report the incident to your service provider.
7 (Critical Event)
Error err-code on LIF lif-name.
Cause: The NonStop TCP/IPv6 subsystem failed to communicate with the
underlying LIF.
Effect: The NonStop TCP/IPv6 subsystem either tries to register/de-
register the filter or to repeat the last I/O operation. If this
problem continues, the LIF becomes inaccessible.
Recovery: An operator may need to check that the processor has
access to the LIF, that the LIF is in the proper working state, and
that the QIO subsystem is in the proper working state. If the error
recurs after problems are found and corrected, report the incident
to your service provider.
8 (Critical Event)
COULD NOT CREATE QIO QUEUE For Subnet subnet, Error err-code.
Cause: The QIO interface module of the NonStop TCP/IPv6 subsystem
failed to create an inbound queue for filters to use
Effect: The subnet configured in the NonStop TCP/IPv6 subsystem
remains nonfunctional until the problem is resolved.
Recovery: Check the state of the QIO subsystem to make sure it is in
a proper working state. If the error recurs after problems are found
and corrected, report the incident to your service provider.
9 (Critical Event)
LIF lif-name Not in STARTED State in CPU cpu-num.
Cause: The LIF is not in the STARTED state.
Effect: The LIF configured in the NonStop TCP/IPv6 subsystem is not
functional until the problem is resolved.
Recovery: Make sure that the LIF is in the STARTED state.
10 (Critical Event)
lif-name Access Down in CPU cpu-num.
Cause: The LIF is not accessible
Effect: The LIF configured in the NonStop TCP/IPv6 subsystem is not
functional until the problem is resolved.
Recovery: Make sure that the access state of the LIF is UP.
11 (Noncritical Event)
info-text.
Cause: This event is informational only.
Effect: None.
Recovery: None.
12 (Critical Event)
Page
11
of
21