Messages related to RLINKs

Table: Messages related to RLINKs shows messages related to RLINKs.

Table: Messages related to RLINKs

Unique Message Identifier (UMI)

Message

Message definition

V-5-0-114

Disconnecting rlink rlink_name to permit transaction to proceed.

Ignore message if seen occasionally.

Action: If the message persists, contact Veritas Customer Support.

V-5-0-208

Log over 80% full for rlink rlink_name

This indicates that SRL is almost full.

Action: Check that the srlprot attribute is set correctly in order to avoid failing of writes, throttling of writes or overflow of SRL.

V-5-0-267

Rlink rlink_name disconnecting due to ack timeout on msg type message

Ignore message if seen occasionally.

Action: If the message persists, contact Veritas Customer Support.

V-5-0-329

Unable to connect rlink rlink_name on rvg rvg_name: Unknown error (errno)

VVR encountered an unknown error.

Action: Contact Veritas Customer Support.

V-5-0-330

Unable to connect to rlink rlink_name on rvg rvg_name: Disk group or rlink not found on remote

The Primary RLINK indicates a Secondary disk group and RLINK combination that does not exist on the Secondary.

Action: Ensure that the disk group and the RLINK specified by the Primary RLINK exist on the Secondary.

V-5-0-330

Unable to connect to rlink rlink_name on rvg rvg_name: Rlink detached on remote

The RLINK on the Secondary node is in the DETACHED or STALE state.

Action: Attach the RLINK and retry.

V-5-0-330

Unable to connect to rlink rlink_name on rvg rvg_name:

Not ready on remote

VVR was not able to connect the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-330

Unable to connect to rlink rlink_name on rvg rvg_name:

Rlink already connected on remote

VVR was not able to connect the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-330

Unable to connect to rlink rlink_name on rvg rvg_name:

Stream error on remote

VVR was not able to connect the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-330

Unable to connect to rlink rlink_name on rvg rvg_name:

Checksum error on remote

VVR was not able to connect the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-330

Unable to connect to rlink rlink_name on rvg rvg_name:

Unexpected command on remote

VVR was not able to connect the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-330

Unable to connect to rlink rlink_name on rvg rvg_name:

Out of space on remote

VVR was not able to connect the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-330

Unable to connect to rlink rlink_name on rvg rvg_name:

Port closing on remote

VVR was not able to connect the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-330

Unable to connect to rlink rlink_name on rvg rvg_name:

Too many threads on remote

VVR was not able to connect the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-330

Unable to connect to rlink rlink_name on rvg rvg_name:

Invalid port on remote

VVR was not able to connect the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-330

Unable to connect to rlink rlink_name on rvg rvg_name:

Send error on remote

VVR was not able to connect the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-330

Unable to connect rlink rlink_name on rvg rvg_name:

KTLI connect failed

VVR was not able to connect the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-330

Unable to connect to rlink rlink_name on rvg rvg_name:

Time out on remote

The Secondary machine is unreachable. Will clear up when the network or the Secondary node recovers.

V-5-0-448

Disconnecting rlink rlink_name due to error in sending (error-code)

VVR disconnected the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-830

Header checksum error

These errors are caused by transient network issues.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-843

Disconnecting rlink rlink_name due to error : error-code

VVR disconnected the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-847

Disconnecting rlink rlink_name due to pending transaction

These errors are caused by transient network issues.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-848

Data checksum error. Received message id message-id with data checksum : checksum-value expected checksum : checksum-value

These errors are caused by transient network issues.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-850

Disconnecting rlink rlink_name as Secondary data volumes are stopped

VVR disconnected the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-851

Disconnecting rlink rlink_name due to bad message.

VVR disconnected the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-853

Disconnecting rlink rlink_name due to header checksum error

VVR disconnected the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-854

Disconnecting rlink rlink_name due to loss of TCP connection

VVR disconnected the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-855

Disconnecting rlink rlink_name due to stream error

VVR disconnected the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-856

Disconnecting rlink rlink_name due to unexpected message

VVR disconnected the named RLINK for the reason mentioned in the message.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-858

Received from unexpected port. Expected from port port, received from port port

These errors are caused by transient network issues.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-859

Received unexpected message. Expected message with opcode operation-code, received opcode operation-code

These errors are caused by transient network issues.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-915

Disconnecting rlink rlink_name remote already connected

These errors are caused by transient network issues.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.

V-5-0-0

Data checksum error for handshake message id (message-id), data checksum computed (checksum-value) but header contains (checksum-value)

These errors are caused by transient network issues.

Action: Ignore message if seen occasionally. VVR automatically recovers from the error.

If the errors persist, they may indicate a problem with the network configuration.