Veritas Storage Foundation and High Availability Solutions Release Notes

More documents

Recommendations

Info

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
Page 1 and 2:
Veritas Storage Foundationand High
Page 3 and 4:
Symantec Corporation350 Ellis Stree
Page 5 and 6:
■■■■■■■Hardware infor
Page 7 and 8:
ContentsTechnical Support .........
Page 9 and 10:
Contents9Chapter 4 Upgrading to 6.0
Page 11 and 12:
Chapter1About Veritas StorageFounda
Page 13 and 14:
About Veritas Storage Foundation an
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38: About Veritas Storage Foundation an
Page 87: About Veritas Storage Foundation an
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Chapter2Installing the products for
Page 151 and 152:
Installing the products for the fir
Page 153 and 154:
Installing the products for the fir
Page 155 and 156:
Chapter3Installing the productsusin
Page 157 and 158:
Installing the products using JumpS
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Chapter4Upgrading to 6.0.3This chap
Page 165 and 166:
Upgrading to 6.0.3Upgrading to 6.0.
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Upgrading to 6.0.3Verifying softwar
Page 195 and 196:
Chapter5Uninstalling version 6.0.3T
Page 197 and 198:
Uninstalling version 6.0.3Rolling b
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
AppendixAConfiguring VCS to managea
Page 223 and 224:
Configuring VCS to manage a Logical
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
show all

Veritas Storage Foundation and High Availability Solutions Release Notes

Create successful ePaper yourself

Delete template?

Save as template?