Search <book_title>...

Veritas InfoScale 7.3.1 Release Notes - Windows

Last Published: 2017-12-15

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

Release notes for Veritas InfoScale

Several issues while you configure VCS on systems where Symantec Endpoint Protection (SEP) version 12.1 is installed

The following issues may occur while you install and configure VCS on systems where Symantec EndPoint Protection (SEP) version 12.1 is installed. (2439737, 2487369, 2574748, 2530343)

The VCS Cluster Configuration Wizard (VCW) may fail to connect to the systems while configuring the cluster.
The following error may be displayed:
```
WMI Connection failed. Error=800706BA
```
If LLT is configured over UDP on an IPv6 network, the status of the Veritas High Availability Engine (HAD) on all the remote nodes in the cluster remains in the REMOTE_BUILD state.
If you set up Disaster Recovery using the Global Cluster Option (GCO) in an IPv6 environment, the status of the remote cluster (cluster at the secondary site) shows as "initing".

Workaround:

Ensure that the required ports and services are not blocked by the firewall. Refer to the Installation and Upgrade Guide for list of ports and services used by the product.
For the VCW issue, add a custom rule to the SEP firewall policy and define the properties as follows:
- Rule name: Type VCS TCP 135 as the name.
- Action: Select Allow this traffic.
- Protocol: Select TCP from the drop-down list.
- Remote Ports: Type 135 in the field.
For IPv6 networks, configure the SEP firewall policy to allow IPv6 traffic on the cluster nodes.
Edit the Firewall Rules table and edit the following settings:
- Block IPv6: Change the Action field value to "Allow".
- Block IPv6 over IPv4 (Teredo): Change the Action field value to "Allow".
- Block IPv6 over IPv4 (ISATAP): Change the Action field value to "Allow".
  Refer to the SEP documentation for detailed instructions on how to edit the firewall policy.
For the LLT over UDP issue on IPv6 network (REMOTE_BUILD issue), perform these steps. Note that the steps require you to stop the Veritas High Availability Engine (HAD).
- Stop the VCS HAD in the cluster.
  From one of the cluster nodes, type the following on the command prompt:
  hastop -all -force
- Perform the following steps on all the cluster nodes, one node at a time:
  - Stop the LLT service on the cluster node.
    Type the following on the command prompt:
    net stop llt
  - Navigate to %VCS_root%\comms\llt and open the llttab.txt file in a text editor.
    Here, VCS_root typically resolves to C:\Program Files\Veritas.
  - Modify all the link entries in the llttab.txt file as follows:
    Change this entry: link <link#> udp6 - udp6 <udpport#> - <IPv6address> -
    to this: link <link#> udp6 - udp6 <udpport#> 1380 <IPv6address> -
    Note that "1380" is added to the link entry. This defines the MTU (packet size) that LLT uses for its communication.
    For example, a sample link entry is as follows: link Link1 udp6 - udp6 50000 1380 2001:db8:0:11:5c56:6867:e398:6152 -
  - Save and close the llttab.txt file.
- Start the VCS HAD in the cluster.
  From one of the cluster nodes, type the following on the command prompt:
  hastart -all