Veritas Cluster Server Release Notes

Veritas™ Cluster Server Release Notes: Linux - SORT - Symantec Veritas™ Cluster Server Release Notes: Linux - SORT - Symantec

d1mj3xqaoh14j0.cloudfront.net
from d1mj3xqaoh14j0.cloudfront.net More from this publisher
17.08.2015 Views

Veritas Cluster Server Release Notes Known issues 64 Fencing may show the RFSM state as replaying for some nodes in the cluster (2555191) Fencing based on coordination point clients in Campus cluster environment may show the RFSM state as replaying for some nodes in the cluster. Workaround: Restart fencing on the node that shows RFSM state as replaying. The vxfentsthdw utility fails to launch before you install the VRTSvxfen package (2858190) Before you install the VRTSvxfen package, the file of /etc/vxfen.d/script/vxfen_scriptlib.sh where stores the vxfentsthdw utility does not exist. In this case, the utility bails out. Workaround: Besides installing the VRTSvxfen package, run the vxfentsthdw utility directly from the installation DVD. Veritas Cluster Server agents for Veritas Volume Replicator known issues The following are new additional Veritas Cluster Server agents for Veritas Volume Replicator known issues in 6.0.2 release. fdsetup cannot correctly parse disk names containing characters such as "-" (1949294) The fdsetup cannot correctly parse disk names containing characters such as "-". Stale entries observed in the sample main.cf file for RVGLogowner and RVGPrimary agent [2872047] Stale entries are found in sample main.cf file for RVGLogowner agent and RVGPrimary agent. The stale entries are present in the main.cf.seattle and main.cf.london files on the RVGLogowner agent which includes CFSQlogckd resource. However, CFSQlogckd is not supported since VCS 5.0. On RVGPrimary agent, the stale entries are present in file main.cf.seattle and main.cf.london and the stale entry includes the DetailMonitor attribute.

Veritas Cluster Server Release Notes Known issues 65 Workaround 1 For main.cf.seattle for RVGLogowner agent in the cvm group: ■ Remove the following lines. CFSQlogckd qlogckd ( Critical = 0 ) cvm_clus requires cvm_vxconfigd qlogckd requires cvm_clus vxfsckd requires qlogckd // resource dependency tree // // group cvm // { // CFSfsckd vxfsckd // { // CFSQlogckd qlogckd // { // CVMCluster cvm_clus // { // CVMVxconfigd cvm_vxconfigd // } // } // } // } ■ Replace the above lines with the following: cvm_clus requires cvm_vxconfigd vxfsckd requires cvm_clus // resource dependency tree // // group cvm // { // CFSfsckd vxfsckd // { // CVMCluster cvm_clus // {

<strong>Veritas</strong> <strong>Cluster</strong> <strong>Server</strong> <strong>Release</strong> <strong>Notes</strong><br />

Known issues<br />

64<br />

Fencing may show the RFSM state as replaying for some nodes<br />

in the cluster (2555191)<br />

Fencing based on coordination point clients in Campus cluster environment may<br />

show the RFSM state as replaying for some nodes in the cluster.<br />

Workaround:<br />

Restart fencing on the node that shows RFSM state as replaying.<br />

The vxfentsthdw utility fails to launch before you install the<br />

VRTSvxfen package (2858190)<br />

Before you install the VRTSvxfen package, the file of<br />

/etc/vxfen.d/script/vxfen_scriptlib.sh where stores the vxfentsthdw utility<br />

does not exist. In this case, the utility bails out.<br />

Workaround:<br />

Besides installing the VRTSvxfen package, run the vxfentsthdw utility directly from<br />

the installation DVD.<br />

<strong>Veritas</strong> <strong>Cluster</strong> <strong>Server</strong> agents for <strong>Veritas</strong> Volume Replicator known<br />

issues<br />

The following are new additional <strong>Veritas</strong> <strong>Cluster</strong> <strong>Server</strong> agents for <strong>Veritas</strong> Volume<br />

Replicator known issues in 6.0.2 release.<br />

fdsetup cannot correctly parse disk names containing<br />

characters such as "-" (1949294)<br />

The fdsetup cannot correctly parse disk names containing characters such as "-".<br />

Stale entries observed in the sample main.cf file for<br />

RVGLogowner and RVGPrimary agent [2872047]<br />

Stale entries are found in sample main.cf file for RVGLogowner agent and<br />

RVGPrimary agent.<br />

The stale entries are present in the main.cf.seattle and main.cf.london files on the<br />

RVGLogowner agent which includes CFSQlogckd resource. However, CFSQlogckd<br />

is not supported since VCS 5.0.<br />

On RVGPrimary agent, the stale entries are present in file main.cf.seattle and<br />

main.cf.london and the stale entry includes the DetailMonitor attribute.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!