Error Message

V-106-58644-550 Operation timed out. The configuration server may be busy or down

Many VVR commands need to be executed on both primary and secondary nodes. The error is seen when the command does return to the originating node within the timeout period.

Reasons for this can include:

• The processing of the command may have been delayed if another command is still being executed or stuck.
• Some operations require active read or write requests on the volumes to be completed before the command can be interpreted.
• Network congestion (This should be associated with other VVR failures to transmit data such as logs growing and rlink connect/disconnect messages.) 
• This error may be encountered when replicating across some firewalls or VPN if the replication packet size is too large for the network.

Perform the following operations in order:

1. Check any network components that are capable of packet filtering (such as firewalls) to determine if replication packets are being dropped because the packet size exceeds a limit that has been specified by the network component. Default VVR packet size is 1400 bytes.

   1. Review VVR Admin guide for steps on changing packet size.

2. Restart Veritas Enterprise Administrator Service (vxsvc) to clear any stuck commands, then retry the operation.

   1. Follow steps in How to restart the Veritas Enterprise Administrator Service for Veritas InfoScale products

As a last resort, increase VVR timeout period.

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

1. In the Windows registry, locate the following key:

2. Find the DWORD value under this key with the name AE_TIMEOUT. Set its valus equal to 90 (decimal).

3. Run the following command:

vxassist refresh

Note:

• If timeouts are still experienced after setting this value to 90, this can be increased further as required. However it might be more appropriate to determine why the commands are timing out to determine if this is the best course of action.

• A reboot is not required for these changes to take effect.