G06.24 ReadMe

Cause: The Address Resolution Protocol (ARP) module of the NonStop

TCP/IPv6 subsystem has detected that another machine on the network

is broadcasting the same IP address.

Effect: The IP-address conflict might cause packets to go to the

wrong machine.

Recovery: Determine which machine is broadcasting incorrectly and

reassign a unique IP address to that machine.

3 (Critical Event)

ARP: Ethernet broadcast address (FF.FF.FF.FF.FF.FF) used by IP address

ip-addr.

Cause: The Address Resolution Protocol (ARP) module of the NonStop

TCP/IPv6 subsystem has detected that another machine on the Ethernet

LAN is using the broadcast address (FF.FF.FF.FF.FF.FF) as its

Ethernet address.

Effect: All packets sent to the broadcast address are received by

all machines on the Ethernet LAN. Performance on all machines is

adversely affected. In addition, some implementations of TCP/IP might

try to forward the packet(s) back over the Ethernet LAN, flooding the

LAN and crashing most machines on the LAN.

Recovery: Determine which machine is using the broadcast address as

its Ethernet address and fix the machine. Note that you cannot

reassign an Ethernet address.

4 (Critical Error)

TCPIPv6 monitor failed to open $Receive, CPU cpu-num, err err-code.

Cause: The NonStop TCP/IPv6 monitor process in the NonStop TCP/IPv6

subsystem failed to open the $RECEIVE during the initialization

Effect: The NonStop TCP/IPv6 subsystem no longer exists in that

processor.

Recovery: Restart the NonStop TCP/IPv6 subsystem in the processor in

which the event occurred and send the online processor dump file to

your service provider for analysis. This event is an indication that

a system internal problem occurred.

5 (Critical Event)

en if-unit: can't handle af family.

Cause: The loopback module of the NonStop TCP/IPv6 subsystem detected

an unsupported protocol family.

Effect: All the NonStop TCP/IPv6 subsystem activities related to the

loopback interface no longer function.

Recovery: Restart the NonStop TCP/IPv6 subsystem in the processor in

which the event occurred and send the online processor dump file to

your service provider for analysis.

6 (Critical Event)

in_cksum: out of mbufs

Cause: Checksum failed in the checksum routine for Internet Protocol

family headers.

Effect: The connection may have been lost.

Page