Veritas InfoScale™ 8.0.2 Release Notes - Windows
- Introduction and product requirements
- Changes introduced in this release
- Executive Order logging
- Limitations
- Deployment limitations
- Cluster management limitations
- Storage management limitations
- Multi-pathing limitations
- Replication limitations
- Solution configuration limitations
- Internationalization and localization limitations
- Interoperability limitations
- Known issues
- Deployment issues
- Cluster management issues
- Cluster Server (VCS) issues
- Cluster Manager (Java Console) issues
- Global service group issues
- VMware virtual environment-related issues
- Cluster Server (VCS) issues
- Storage management issues
- Storage Foundation issues
- VEA console issues
- Snapshot and restore issues
- Snapshot scheduling issues
- Multi-pathing issues
- Replication issues
- Solution configuration issues
- Disaster recovery (DR) configuration issues
- Fire drill (FD) configuration issues
- Quick recovery (QR) configuration issues
- Internationalization and localization issues
- Interoperability issues
- Miscellaneous issues
- Fibre Channel adapter issues
- Deployment issues
VMwareDisks agent resource goes into an unknown state if disk UUID is not provided (4113979)
The VMwareDisks agent resource may fail to come online or go offline and may eventually go into the unknown state. This issue is observed if the disk UUID is not specified for the disks that are configured in the DiskPaths attribute of the agent.
The following errors appear in the agent log:
VCS ERROR V-16-1-53006 Unable to connect to VCS engine securely VCS ERROR V-16-10061-22503 VMwareDisks:res_vmware1:offline: Failed to login to ESX with error 'Failed to decrypt the password 9b:e2:12:46:a5:fc:6b:77:24:3c:ce:28:a6:0c:65:98:c3 Error = 1.' VCS WARNING V-16-2-13102 Thread(1404) Resource (res_vmware1) received unexpected event info in state GoingOfflineWaiting
Workaround: Provide the disk UUID for each disk that the VMwareDisks agent monitors and then bring the resource online.
Perform the following steps:
- Sign into the VMware vSphere Client or the vCenter Server and navigate to the virtual machines that are a part of the InfoScale cluster.
- For each virtual machine, locate the disks that are configured in the cluster and make a note of each disk's device node.
For example,
Hard Disk 1
orSCSI (1:0)
. - On the VMware datastore, locate and then download the virtual machine's configuration file (file with a .vmdk extension).
- Open the .vmdk configuration file in a text editor and search for the disk entry that corresponds to the device node that you noted in the earlier step.
Locate the line that starts with the device node, for example:
scsi0:1.fileName
orscsiX:Y.fileName
.Here, X represents the SCSI adapter and Y represents the disk unit number. For example,
scsi0:1.fileName = "MyVirtualDisk.vmdk"
. - Make a note of the disk UUID that appears under the device node entry.
A string of alphanumeric characters that are enclosed in quotes represent the disk UUID.
For example,
ddb.uuid = "60 00 C2 94 cc cc b7 da-0e 2d 89 7a ef"
. - Specify the disk UUID in the DisksPaths attribute of the VMwareDisks agent resource that is configured for the virtual machine.
Ensure that you provide only the alphanumeric sequence of the UUID. Do not include "ddb.uuid =" in the DiskPaths attribute.
For example,
"60 00 C2 94 cc cc b7 da-0e 2d 89 7a ef"
. - Similarly, repeat this process for all the other disks that are configured on the virtual machines that are part of the cluster.
- Bring the VMwareDisks agent resources online.