Veritas Storage Foundation and High Availability Solutions Release Notes
Share Embed Flag
Download ePaper

Veritas Storage Foundation and High Availability Solutions Release Notes

Veritas Storage Foundation™ and High ... - SORT - Symantec Veritas Storage Foundation™ and High ... - SORT - Symantec

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

88About Veritas Storage Foundation and High Availability SolutionsKnown issuesVerification with ha -verify shows no errors when ContainerInfo andResContainerInfo are set with service groups having multiple zones[2859495]When defining ResContainerInfo for any resource in group in main.cf, if you alsodefine ContainerInfo the corresponding group in main.cf then ContainerInfo isused instead of ResContainerInfo when main.cf is loaded. Verification of theconfiguration file using ha -verify at this stage shows no errors.Workaround: Make sure ContainerInfo is not defined while definingResContainerInfo for corresponding group in main.cf .NFS client reports error when server is brought down using shutdowncommand [2872741]On Solaris 11, when the VCS cluster node having the NFS share service group isbrought down using shutdown command, NFS clients may report "Stale NFS filehandle" error. During shutdown, the SMF service svc:/network/shares un-sharesall the shared paths before taking down the virtual IP. Thus, the NFS clientsaccessing this path get stale file handle error.Workaround: Before you shutdown the VCS cluster node, disable thesvc:/network/shares SMF service, so that only VCS controls the un-sharing of theshared paths during the shutdown operation.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.Missing host names in engine_A.log file (1919953)The GUI does not read the engine_A.log file. It reads the engine_A.ldf file, getsthe message id from it, and then queries for the message from the bmc file of theappropriate locale (Japanese or English). The bmc file does not have system namespresent and so they are read as missing.The hacf -cmdtocf command generates a broken main.cf file [1919951]The hacf -cmdtocf command used with the -dest option removes the includestatements from the types files.Workaround: Add include statements in the main.cf files that are generated usingthe hacf -cmdtocf command.types.cf error after rollback 6.0.3 to 6.0.1(3067510)On Solaris 10, if you rollback Storage Foundation and High Availability Solutions6.0.3 to 6.0.1, the DomainFailurePolicy attribute, which is a new attribute in 6.0.3,

About Veritas Storage Foundation and High Availability SolutionsKnown issues89cannot be automatically removed in the VCS configuration files types.cf andmain.cf. This causes types.cf verification to fail and had not to start after theuninstallation because the DomainFailurePolicy attribute is not identified bySFHA 6.0.1.Workaround:1. Stop the cluster.2. Remove all the occurrences of the DomainFailurePolicy attribute in thetypes.cf and main.cf files at /etc/VRTSvcs/conf/config.3. Start the cluster from the node where the configuration files are modified.4. Start VCS on all other nodes.Issues related to the bundled agentsSolaris mount agent fails to mount Linux NFS exported directoryThe Solaris mount agent mounts the mount directories. At this point, if it triesto mount a Linux NFS exported directory, the mount fails showing the followingerror:nfs mount: mount: : Not ownerThis is due to system NFS default version mismatch between Solaris and Linux.The workaround for this is to configure MountOpt attribute in mount resourceand set vers=3 for it.Exampleroot@north $ mount -F nfs south:/test /logo/nfs mount: mount: /logo: Not ownerroot@north $Mount nfsmount ()MountPoint = "/logo"BlockDevice = "south:/test"FSType = nfsMountOpt = "vers=3"Process and ProcessOnOnly agent rejects attribute values with white spaces[2303513]Process and ProcessOnOnly agent does not accept Arguments attribute valuesthat are separated by multiple whitespaces. The Arguments attribute specifiesthe set of arguments for a process. If a script controls the process, the script is

88About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Known issuesVerification with ha -verify shows no errors when ContainerInfo <strong>and</strong>ResContainerInfo are set with service groups having multiple zones[2859495]When defining ResContainerInfo for any resource in group in main.cf, if you alsodefine ContainerInfo the corresponding group in main.cf then ContainerInfo isused instead of ResContainerInfo when main.cf is loaded. Verification of theconfiguration file using ha -verify at this stage shows no errors.Workaround: Make sure ContainerInfo is not defined while definingResContainerInfo for corresponding group in main.cf .NFS client reports error when server is brought down using shutdowncomm<strong>and</strong> [2872741]On Solaris 11, when the VCS cluster node having the NFS share service group isbrought down using shutdown comm<strong>and</strong>, NFS clients may report "Stale NFS fileh<strong>and</strong>le" error. During shutdown, the SMF service svc:/network/shares un-sharesall the shared paths before taking down the virtual IP. Thus, the NFS clientsaccessing this path get stale file h<strong>and</strong>le error.Workaround: Before you shutdown the VCS cluster node, disable thesvc:/network/shares SMF service, so that only VCS controls the un-sharing of theshared paths during the shutdown operation.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.Missing host names in engine_A.log file (1919953)The GUI does not read the engine_A.log file. It reads the engine_A.ldf file, getsthe message id from it, <strong>and</strong> then queries for the message from the bmc file of theappropriate locale (Japanese or English). The bmc file does not have system namespresent <strong>and</strong> so they are read as missing.The hacf -cmdtocf comm<strong>and</strong> generates a broken main.cf file [1919951]The hacf -cmdtocf comm<strong>and</strong> used with the -dest option removes the includestatements from the types files.Workaround: Add include statements in the main.cf files that are generated usingthe hacf -cmdtocf comm<strong>and</strong>.types.cf error after rollback 6.0.3 to 6.0.1(3067510)On Solaris 10, if you rollback <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>6.0.3 to 6.0.1, the DomainFailurePolicy attribute, which is a new attribute in 6.0.3,

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

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

Saved successfully!

Ooh no, something went wrong!