Veritas Cluster Server Release Notes

More documents

Recommendations

Info

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.
Veritas Cluster Server Release Notes Known issues 43 Switching service group with DiskGroup resource causes reservation conflict with UseFence set to SCSI3 and powerpath environment set [2749136] If UseFence is set to SCSI3 and powerpath environment is set, then switching the service group with DiskGroup resource may cause following messages to appear in syslog: reservation conflict This is not a VCS issue. In case UseFence is set to SCSI3, the diskgroups are imported with the reservation. This message gets logged while releasing and reserving the disk. Workaround: See the tech note available at http://www.symantec.com/business/support/index?page=content&id=TECH171786. Issues related to the VCS engine Extremely high CPU utilization may cause HAD to fail to heartbeat to GAB [1744854] When CPU utilization is very close to 100%, HAD may fail to heartbeat to GAB. The hacf -cmdtocf command generates a broken main.cf file [1919951] The hacf -cmdtocf command used with the -dest option removes the include statements from the types files. Workaround: Add include statements in the main.cf files that are generated using the hacf -cmdtocf command. Trigger does not get executed when there is more than one leading or trailing slash in the triggerpath [2368061] The path specified in TriggerPath attribute must not contain more than one leading or trailing '\' character. Workaround: Remove the extra leading or trailing '\' characters from the path. Service group is not auto started on the node having incorrect value of EngineRestarted [2653688] When HAD is restarted by hashadow process, the value of EngineRestarted attribute is temporarily set to 1 till all service groups are probed. Once all service groups are
Page 1 and 2: Veritas Cluster Server Release Note
Page 3: Symantec Corporation 350 Ellis Stre
Page 6 and 7: Support agreement resources If you
Page 41: Veritas Cluster Server Release Note

Veritas Cluster Server Release Notes

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?