G06.24 ReadMe

Effect: None. This event is informational only.
Recovery: This is an informational message only; no corrective
action is needed.
206 (Noncritical Event)
TCP6MON Process tcp6mon-name started on CPU cpu-num.
Cause: The operator started a TCP6MON or brought up a processor in
which a TCP6MON was configured.
Effect: None. This event is informational only.
Recovery: This is an informational message only; no corrective
action is needed.
207 (Noncritical Event)
TCP6MON Process tcp6mon-name stopped on CPU cpu-num.
Cause: An operator stopped the monitor using SCF.
Effect: None. This event is informational only.
Recovery: This is an informational message only; no corrective
action is needed.
208 (Noncritical Event)
Master TCP6MON switched from process tcp6mon-name1 on CPU
cpu-number1 to process tcp6mon-name2 on CPU cpu-number2.
Cause: The old Master TCP6MON was stopped.
Effect: The default filter is moved to the new Master TCP6MON.
Recovery: None.
209 (Critical Event)
No Master TCP6MON Process on system.
Cause: An operator stopped either the NonStop TCP/IPv6 subsystem or
the only TCP6MON in the system.
Effect: No NonStop TCP/IPv6 subsystem is running.
Recovery: Restart the TCP6MON processes.
211 (Critical Event)
Subnet subnet Duplicate IPv6 address ipv6-addr detected for addr-type.
Cause: The neighbor discovery protocol has detected another node on
the network that is using the same IPv6 address.
Effect: The address will be unusable on this machine until the
problem is resolved.
Recovery: Determine which machine is assigned the wrong IPv6 address
and change the configuration.
212 (Critical Event)
module: TCP6MON Unexpected Sock Migration Request,
originated from CPU cpu-num, Address ipv6-addr, from port port
Page
18
of
21