Veritas Cluster Server Release Notes

Veritas Cluster Server Release Notes
Known issues
42
LVM SG transition fails in all paths disabled status [2081430]
If you have disabled all the paths to the disks, the LVM2 vg commands stop
responding and wait until at least one path to the disks is restored. As
LVMVolumeGroup agent uses LVM2 commands, this behavior causes online and
offline entry points of LVMVolumeGroup agent to time out and clean EP stops
responding for an indefinite time. Because of this, the service group cannot fail over
to another node.
Workaround: You need to restore at least one path.
SG goes into Partial state if Native LVMVG is imported and
activated outside VCS control
If you import and activate LVM volume group before starting VCS, the
LVMVolumeGroup remains offline though the LVMLogicalVolume resource comes
online. This causes the service group to be in a partial state.
Workaround: You must bring the VCS LVMVolumeGroup resource offline manually,
or deactivate it and export the volume group before starting VCS.
Some VCS components do not work on the systems where a
firewall is configured to block TCP traffic
The following issues may occur if you install and configure VCS on systems where
a firewall is installed:
■
■
■
If you set up Disaster Recovery using the Global Cluster Option (GCO), the
status of the remote cluster (cluster at the secondary site) shows as "initing".
If you configure fencing to use CP server, fencing client fails to register with the
CP server.
Setting up trust relationships between servers fails.
Workaround:
■
■
Ensure that the required ports and services are not blocked by the firewall. Refer
to the Veritas Cluster Server Installation Guide for the list of ports and services
used by VCS.
Configure the firewall policy such that the TCP ports required by VCS are not
blocked. Refer to your respective firewall or OS vendor documents for the
required configuration.