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

VCS engine HAD may not accept client connection requests even after the cluster is configured successfully

This issue may occur after you run the VCS Cluster Configuration Wizard (VCW) to configure a cluster to use single sign-on authentication. Even though VCW indicates that the cluster is configured successfully, the Veritas High Availability Engine (HAD) fails to accept client connection requests. This may happen if VCW fails to configure the VCS authentication service on one or more cluster nodes. (2609395)

You may observe one or more of the following:

If you try to launch any of the VCS service group configuration wizards, you will see the following error:

The VCS engine (HAD) is not running on the cluster nodes.
Failed to get the required cluster information.

The wizard will quit.

Error V-16-13-160

If you run the hasys - display command to check the status of HAD in the cluster, you will see the following error on the command prompt:
```
VCS ERROR V-16-1-53007 Error returned from engine: 
HAD on this node not accepting clients.
```

If you try to connect to the cluster using the Cluster Manager (Java Console), you will see the following error:

VCS ERROR V-16-10-106
Could not connect to a live system in the cluster localhost:14141.
Please check the application event log for more details.
Closing all windows.

If you run VCW again to reconfigure the cluster, you will see the following error on the Edit Cluster Options panel:

Failed to connect to the cluster.
Error reason: Failed to open socket connection to port 14141 on 
host <node_name> (1)

Workaround: In the following steps we manually modify the cluster that was configured to use single sign-on authentication to use VCS authentication instead and then reconfigure the cluster using VCS Cluster Configuration Wizard (VCW).

Perform the following steps:

Stop the Veritas High Availability Engine (HAD) on all the cluster nodes.
On each cluster node, type the following on the command prompt:
```
net stop had
```
Perform the remaining steps on one of the cluster nodes.
Navigate to %VCS_home%\conf\config and locate and delete the .secure file from that directory.
Here, %VCS_home% is the installation directory for VCS, typically C:\Program Files\Veritas\Cluster Server.
From %VCS_home%\conf\config directory, locate the configuration file main.cf and open it in a text editor.
In main.cf, search for the text "SecureClus=1" and delete that line altogether.
Save the file and close the text editor.
Start the VCS engine (HAD) locally on the node where you performed the earlier steps.
Type the following on the command prompt:
```
hastart
```
Set the cluster configuration to read/write mode.
Type the following on the command prompt:
```
haconf -makerw
```
Add a user to the cluster and assign it with cluster administrator privileges.
Type the following command:
```
hauser -add <username> -priv Administrator
```
Enter the password for the user, when prompted.
Save and make the cluster configuration read-only.
Type the following on the command prompt:
```
haconf -dump -makero
```
Start the Veritas High Availability Engine (HAD) on the remaining cluster nodes.
Type the following on the command prompt:
```
hastart -all
```

Use the cluster user you added in earlier steps to connect to the cluster. If required, run the VCS Cluster Configuration Wizard (VCW) and reconfigure the cluster to use single sign-on authentication.