G06.24 ReadMe

Route Dest Address route-addr.

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

TCP/IPv6 subsystem either failed to create or failed to look up a new

address in the ARP table.

Effect: Because the ARP cache lookup failed, a new attempt to connect

will also fail, and existing connections might be temporarily lost.

If the problem continues, all the existing connections will be lost.

Recovery: Examine the command that failed to create the route and

subsequently generated this event. If a route associated with the ARP

entry already exists, then this event is just for informational

purposes. If no route associated with the ARP cache exists, send the

information about the routing tables to your service provider for

analysis.

28 (Critical Event)

module: Route Not Freed, Route route-name,

Reference count -cnt.

Cause: An attempt to free a routing structure has failed because the

reference count of the route entry was negative.

Effect: The route associated with this event becomes unusable. The

connections through this route may experience abnormal behavior. A

memory leak might also occur.

Recovery: This event is an indication that the reference count of

that route was incremented or decremented incorrectly. Make a copy of

the routing tables in the processor where this event occurred and send

the information to your service provider for further analysis.

29 (Noncritical Event)

module: Trace buffer is full on CPU cpu-num.

Cause: One of the QIO buffers used for TCP6MON/TCPLIB trace buffering

does not have enough room for another trace record.

Effect: None.

Recovery: This event is for information. If the problem persists,

please report this problem to your service provider.

30 (Critical Event)

module: TCP6MON failed to update a record to CONFIG DB

error: err-code, Record-Type: type on CPU cpu-num.

Cause: An internal error occurred during configuration database

management.

Effect: This error may lead to inconsistent subnet or route

structures among processors.

Recovery: Examine the subnet and routing topology in all processors

running NonStop TCP/IPv6. If any inconsistency exists among the

processors, disable the configuration database for NonStop TCP/IPv6

and re-configure the subnets and routes.

31 (Critical Event)

module: TCP6MON failed to fetch record from CONFIG DB

error: err-code, Record-Type: type on CPU cpu-num.

Page