VCS is not providing the cluster name to Tivoli Storage Manager.

Assumptions:

• CLUSTERNODE YES is set in the dsm.opt file to indicate that the node is a cluster node.
• 'This is a cluster node' is checked during the setup of the scheduler service in the Client GUI wizard.

During the setup of the scheduler service on a Windows Tivoli Storage Manager Client in a VCS environment, the setup fails with:
"ANS1482E An unexpected error (-1) occurred while the program was trying to obtain the cluster name from the system."

The above error message can be attributed to one of the following causes:
a) the main.cf file does not exist or is not valid
b) the VCS configuration is opened in read/write mode and the configuration is stale
c) the VCS service is not running.

To check the status of the cluster, issue the following command:

HASYS -STATE

If the state of the cluster member is not 'RUNNING', Veritas will not be able to return the cluster information to Tivoli Storage Manager. If that is the case, Veritas should be contacted to verify why VCS is not providing the Cluster Name to Tivoli Storage Manager.