Veritas Cluster Server Release Notes
Veritas⢠Cluster Server Release Notes: Linux - SORT - Symantec
Veritas⢠Cluster Server Release Notes: Linux - SORT - Symantec
- No tags were found...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Veritas</strong> <strong>Cluster</strong> <strong>Server</strong> <strong>Release</strong> <strong>Notes</strong><br />
VCS: Issues fixed in 6.0.1<br />
30<br />
Table 1-13<br />
Incident<br />
2850904<br />
2794175<br />
2728802<br />
2850905<br />
2850916<br />
2822920<br />
2679251<br />
2800021<br />
2846389<br />
Bundled agents fixed issues<br />
Description<br />
Concurrency violation and data corruption of a Volume resource may<br />
occur, if storage connectivity is lost or all paths under VxDMP are<br />
disabled and PanicSystemOnDGLoss is set to 0.<br />
Fire drill for Mount agent does not accurately portray a failover scenario.<br />
If the 'httpd' binary or the 'ab' binary is not present at the location that<br />
you specified in the 'httpdDir' attribute, the Apache agent cannot perform<br />
detail monitoring or start the HTTP server.<br />
IMF registration for Mount resource for file systems type other than<br />
VxFS and NFS should be blocked.<br />
Mount resource does not get registered with IMF if the attributes<br />
BlockDevice and/or MountPoint have a trailing slash in their values.<br />
DNSAgent goes to UNKNOWN state if the Top Level Domain (TLD) is<br />
more than 4 characters in length.<br />
After stopping the VCS forcefully (hastop -local -force), if disk reservation<br />
resource is configured then user may observe a system panic.<br />
Clean entry point fails due to discrepancy in command path on RHEL<br />
5.<br />
In releases prior to VCS 6.0.1, the upper bound value of FaultTolerance<br />
attribute of the CoordPoint agent was the one less than the number of<br />
coordination points. If the majority number of coordination points fault,<br />
the entire cluster panicked under network partition scenario. Therefore,<br />
the upper bound value of the FaultTolerance attribute of CoordPoint<br />
agent had to be set to less than the majority of the coordination points.<br />
Subsequent to VCS 6.0.1, the FaultTolerance attribute of CoordPoint<br />
agent is less than the majority of coordination points.<br />
VCS engine fixed issues in 6.0.1<br />
Table 1-14 lists the fixed issues for VCS engine.<br />
Table 1-14<br />
Incident<br />
2832754<br />
VCS engine fixed issues<br />
Description<br />
When a Global <strong>Cluster</strong> Option (GCO) is configured across clusters<br />
having duplicate system names, command-line utility hagrp gives<br />
incorrect output with the "-clear", "-flush", "-state" options.
Change language