Cluster Server (VCS) issues
This section lists the known issues related to the Cluster Server (VCS) component.
Related information
Cluster management issues
Cluster reconfiguration may fail post InfoScale installation (4117528)The VCS Cluster Configuration Wizard may not be able to delete a cluster if it fails to stop HADDeleting a node from a cluster using the VCS Cluster Configuration Wizard may not remove it from main.cfNetAppSnapDrive resource may fail with access denied errorMount resource fails to bring file share service group onlineMount agent may go in unknown state on virtual machinesAutoStart may violate limits and prerequisites Load PolicyEnterprise Vault Configuration Wizard may fail to connect to SQL ServerFile Share Configuration Wizard may create dangling VMDg resourcesFor volumes under VMNSDg resource, capacity monitoring and automatic volume growth policies do not get available to all cluster nodesFor creating VMNSDg resources, the VMGetDrive command not supported to retrieve a list of dynamic disk groupsFirst failover attempt might fault for a NativeDisks configurationResource fails to come online after failover on secondaryUpgrading a secure cluster may require HAD restartNew user does not have administrator rights in Java GUIHTC resource probe operation fails and reports an UNKNOWN stateResources in a parent service group may fail to come online if the AutoStart attribute for the resources is set to zeroVCS wizards may fail to probe resourcesChanges to referenced attributes do not propagateArgListValue attribute may not display updated valuesThe Cluster Server High Availability Engine (HAD) service fails to stopEngine may hang in LEAVING stateTiming issues with AutoStart policyThe VCS Cluster Configuration Wizard (VCW) supports NIC teaming but the InfoScale High Availability Configuration Wizard does notVCS engine HAD may not accept client connection requests even after the cluster is configured successfullyHyper-V DR attribute settings should be changed in the MonitorVM resource if a monitored VM is migrated to a new volumeOne or more VMNSDg resources may fail to come online during failover of a large service groupVDS error reported while bringing the NativeDisks and Mount resources online after a failoverSQL Server service resource does not fault even if detail monitoring failsDelay in refreshing the VCS Java ConsoleNetBackup may fail to back up SQL Server database in VCS cluster environment