Storage Foundation 8.0 Administrator's Guide - Windows
- Overview
- Setup and configuration
- Function overview
- About the client console for Storage Foundation
- Recommendations for caching-enabled disks
- Configure basic disks (Optional)
- About creating dynamic disk groups
- About creating dynamic volumes
- Set desired preferences
- Using the GUI to manage your storage
- Working with disks, partitions, and volumes
- Adding storage
- Disk tasks
- Remove a disk from the computer
- Veritas Disk ID (VDID)
- General Partition/Volume tasks
- Mount a volume at an empty folder (Drive path)
- Expand a dynamic volume
- Shrink a dynamic volume
- Basic disk and volume tasks
- Automatic discovery of SSD devices and manual classification as SSD
- Volume Manager space allocation is SSD aware
- Dealing with disk groups
- Disk groups overview
- Delete a dynamic disk group
- Detaching and attaching dynamic disks
- Importing and deporting dynamic disk groups
- Partitioned shared storage with private dynamic disk group protection
- Fast failover in clustered environments
- iSCSI SAN support
- Settings for monitoring objects
- Event monitoring and notification
- Event notification
- Configuring Automatic volume growth
- Standard features for adding fault tolerance
- Performance tuning
- FlashSnap
- FlashSnap components
- FastResync
- Snapshot commands
- Dynamic Disk Group Split and Join
- Dynamic disk group join
- Using Dynamic Disk Group Split and Join with a cluster on shared storage
- Dynamic Disk Group Split and Join troubleshooting tips
- Fast File Resync
- Volume Shadow Copy Service (VSS)
- Using the VSS snapshot wizards with Microsoft Exchange
- Using the VSS snapshot wizards with Enterprise Vault
- Using the VSS snapshot wizards with Microsoft SQL
- Copy on Write (COW)
- Using the VSS COW snapshot wizards with Microsoft Exchange
- Using the VSS COW snapshot wizards with Microsoft SQL
- Configuring data caching with SmartIO
- Typical deployment scenarios
- About cache area
- Configuring SmartIO
- Frequently asked questions about SmartIO
- Dynamic Multi-Pathing
- Configuring Cluster Volume Manager (CVM)
- Configuring a CVM cluster
- Administering CVM
- Access modes for cluster-shared volumes
- Storage disconnectivity and CVM disk detach policy
- Unconfiguring a CVM cluster
- Command shipping
- About I/O Fencing
- Administering site-aware allocation for campus clusters
- SFW for Hyper-V virtual machines
- Introduction to Storage Foundation solutions for Hyper-V environments
- Live migration support for SFW dynamic disk group
- Preparing the host machines
- Configuring the SFW storage
- Administering storage migration for SFW and Hyper-V virtual machine volumes
- Optional Storage Foundation features for Hyper-V environments
- Microsoft Failover Clustering support
- Configuring a quorum in a Microsoft Failover Cluster
- Implementing disaster recovery with Volume Replicator
- Troubleshooting and recovery
- Using disk and volume status information
- Resolving common problem situations
- Commands or procedures used in troubleshooting and recovery
- Rescan command
- Repair volume command for dynamic mirrored volumes
- Additional troubleshooting issues
- Disk issues
- Volume issues
- Disk group issues
- Connection issues
- Issues related to boot or restart
- Cluster issues
- Dynamic Multi-Pathing issues
- vxsnap issues
- Other issues
- CVM issues
- Appendix A. Command line interface
- Overview of the command line interface
- vxclustadm
- vxvol
- vxdg
- vxclus
- vxdisk
- vxassist
- vxassist (Windows-specific)
- vxsd
- vxedit
- vxdmpadm
- vxcbr
- vxsnap
- vxscrub
- sfcache
- Tuning SFW
- Appendix B. VDID details for arrays
One or more nodes have invalid configuration or are not running or reachable
This is regarding various CVM cluster configuration-related issues where one or more cluster nodes have invalid or are not running or reachable.
This section provides information on the following two error messages:
Error V-194-311-701: One or more systems in the cluster have an invalid configuration. For details, select a system and view its status details or see the log file. Resolve the configuration issues on such systems or remove them from Microsoft failover cluster, and then retry the operation.
This error occurs for one or more of the following reasons:
WMI issues
Connectivity/authentication issues
One or more nodes are not running or reachable
Firewall issues
For the reasons listed above, the SFW Configuration Wizard for Microsoft Failover Cluster or the ffconfigcli utility do not let you perform any further operations. To resolve these issues, do one or more of the following as required:
- Recommended Solution: Try to resolve the connectivity issues and bring up the affected node. Then, re-launch the wizard and perform the desired operations.
- If a single node cannot be brought up, then do the following:
Remove the node from the Microsoft failover cluster.
Remove the node from the CVM cluster by running the ffconfigcli -removenode <NodeName> command.
If you want to use this node again, then you first need to clean up the configuration by running the ffconfigcli -removenode <NodeName> command on the node.
- If multiple nodes cannot be brought up, then do the following:
Remove the nodes from the Microsoft failover cluster.
Bring all the running applications offline.
Unconfigure the CVM cluster using the wizard or by running the ffconfigcli -unconfigure command.
Re-configure the CVM cluster with the healthy nodes using the wizard or by running the ffconfigcli -autoconfigure command.
Bring all the applications online.
If you want to use these nodes again, then you first need to clean up the configuration by running the ffconfigcli -removenode <NodeName> command on each node.
Warning V-194-311-256: Errors were encountered while removing the node CVMCLUSNODE4 from the CVM cluster. You may need to clean up the SFW configuration on the node. This error occurs if the node that you were trying to remove is not running or reachable.
This error occurs if the node that you try to remove is not running or reachable.
To resolve this issue, once the node is up, remove the faulty node by re-launching the wizard or by running the ffconfigcli -removenode <NodeName> command on the node.