Search <book_title>...

Veritas InfoScale 7.3.1 Release Notes - Windows

Last Published: 2017-12-15

Product(s): InfoScale & Storage Foundation (7.3.1)

Live migration of a VM, which is part of a VCS cluster where LLT is configured over Ethernet, from one Hyper-V host to another may result in inconsistent HAD state

Consider the following scenario:

Two or more Hyper-V hosts are set up, between which live migration can be performed.
Two or more virtual machines (for example, VM1 and VM2) are configured as nodes of a VCS cluster on one of the hosts.
In the VCS cluster, LLT is configured over Ethernet.

Perform live migration of one of the virtual machines (say VM1, which may be the active node).

After live migration, the HAD state is reported as follows:

Events such as the following may be seen in the System Event Viewer for VM1 (one event for each LLT link):

LLT ERROR V-14-1-10085 LLT protocol is unbinding from link adapterID

This issue does not occur when LLT is configured over UDP. (3053241, 3056450)

Workaround: To avoid this issue, you might want to configure LLT over UDP.

If you choose to configure LLT over Ethernet and if you encounter this issue, perform the following steps after live migration:

Forcibly stop the Veritas High Availability Engine (HAD) service on the migrated node using the following command:
```
taskkill /f /im had.exe
```
If the HAD service starts again, stop it using the following command:
```
hastop -local
```
Verify that the HAD service is in the stopped state.
Run the following commands sequentially on the migrated node:
```
net stop vcscomm
```
```
net stop gab
```
```
net stop llt
```
On the migrated node, restart the VCS cluster using the following command:
```
hastart
```
Verify that all the cluster nodes report a consistent state for the HAD service using the following command:
```
hasys -state
```