G06.24 ReadMe

Cause: The NonStop TCP/IPv6 subsystem detects an unexpected migration

request. The application issuing the socket "ACCEPT_NW2" function call

has cancelled the request

Effect: The migration request will be dropped and the socket will not

be migrated to new processor.

Recovery: This is an informational message only; no corrective action

is needed.

213 (Critical Event)

module: TCP6MON Sock Migration Request Get MBUF failed, originated

from CPU cpu-num, Address ipv6-addr, from port port.

Cause: No memory is available to format the migration request.

Effect: The migration request will be dropped and the socket will not

be migrated to a new processor.

Recovery: This is an informational message only; no corrective action

is needed.

214 (Critical Event)

name: Filter Register For IPv6 Address ipv6-addr Failed,

Error= err-code, Filter Type = type, Local Port = port.

Cause: A filter registration failed on subnet name for ipv6-addr.

This event could be due to an improperly configured NonStop TCP/IPv6

subsystem or an internal NonStop TCP/IPv6 subsystem problem.

Effect: The NonStop TCP/IPv6 subsystem will attempt to re-register

the filter. If the filter registration is for a Subnet filter and the

problem continues, the Subnet becomes inaccessible. If the

registration is for a Port filter and the problem continues, filter

registration will fail.

Recovery: Determine the type and the cause of the failed registration

from the err-code value and take appropriate action.

215 (Critical Event)

if-name: Filter Register For IPv6 Address ipv6-addr Failed, Timed Out.

Cause: A register timeout occurred on subnet if-name for ipv6-addr.

Effect: None.

Recovery: The NonStop TCP/IPv6 subsystem will try the filter

registration at a later time. No operator invention is required.

216 (Critical Event)

name: Filter Register For IPv6 Address ipv6-addr Failed,

Already In Use, Filter Type = type, Local port = l

-port,

Cause: A filter register is already in use on name for ipv6-addr.

This event could be due to an improperly configured NonStop TCP/IPv6

subsystem or an internal subsystem problem.

Effect: No retry will be done by the NonStop TCP/IPv6 subsystem. The

application will receive a proper error code.

Recovery: Determine the type and the cause of the failed registration

from the err-code value and take the appropriate action

217 (Critical Event)

Page