Veritas Storage Foundation and High Availability Solutions Release Notes

More documents

Recommendations

Info

94About Veritas Storage Foundation and High Availability SolutionsKnown issuesWorkaround: Change the ForceAttach attribute of Zone resource from 1 to 0. Withthis configuration, you are recommended to keep the default value ofDetachZonePath as 1.Error message is seen for Apache resource when zone is in transient state[2703707]If the Apache resource is probed when the zone is getting started, the followingerror message is logged:Argument "VCS ERROR V-16-1-10600 Cannot connect to VCS engine\n"isn't numeric in numeric ge (>=) at /opt/VRTSvcs/bin/Apache/Apache.pmline 452.VCS ERROR V-16-1-10600 Cannot connect to VCS engineLogInt(halog call failed):TAG:E:20314 SecondLevelMonitorTimeOut must be less than MonitorTimeOut.Workaround: You can ignore this message. When the zone is started completely,the halog command does not fail and Apache agent monitor runs successfully.Monitor falsely reports NIC resource as offline when zone is shutting down(2683680)If a NIC resource is configured for an Exclusive IP zone, the NIC resource ismonitored inside the zone when the zone is functional. If the NIC monitor programis invoked when the zone is shutting down, the monitor program may falselyreport the NIC resource as offline. This may happen if some of the networkingservices are offline but the zone is not completely shut down. Such reports canbe avoided if you override and set the ToleranceLimit value to a non-zero value.Workaround: When a NIC resource is configured for an Exclusive IP zone, you arerecommended to set the ToleranceLimit attribute to a non-zero value.Calculate the ToleranceLimit value as follows:Time taken by a zone to completely shut down must be less than or equal to NICresource's MonitorInterval value + (MonitorInterval value x ToleranceLimit value).For example, if a zone take 90 seconds to shut down and the MonitorInterval forNIC agent is set to 60 seconds (default value), set the ToleranceLimit value to 1.Apache resource does not come online if the directory containing Apachepid file gests deleted when a node or zone restarts (2680661)The directory in which Apache http server creates PidFile may get deleted whena node or zone restarts. Typically the PidFile is located at/var/run/apache2/httpd.pid. When the zone reboots, the /var/run/apache2directory may get removed and hence the http server startup may fail.
About Veritas Storage Foundation and High Availability SolutionsKnown issues95Workaround: Make sure that Apache http server writes the PidFile to an accessiblelocation. You can update the PidFile location in the Apache http configurationfile (For example: /etc/apache2/httpd.conf).Online of LDom resource may fail due to incompatibility of LDomconfiguration file with host OVM version (2814991)If you have a cluster running LDom with different OVM versions on the hosts,then the LDom configuration file generated on one host may display error messageswhen it is imported on the other host with a different OVM version. Thus, theonline of LDom resource may also fail.For example, if you have a cluster running LDom with OVM versions 2.2 on oneand OVM 2.1 on the other node, the using XML configuration generated on thehost with OVM 2.2 may display errors when the configuration is imported on thehost with OVM 2.1. Thus, the online of LDom resource fails.The following error message is displayed:ldm add-domain failed with error Failed to add device/ldom1/ldom1 as ld1_disk1@primary-vds0 because this deviceis alreadyexported on LDom primary. Volume ld1_disk1already exists in vds primary-vds0.Workaround: If the CfgFile attribute is specified, ensure that the XML configurationgenerated is compatible with the OVM version installed on the nodes.Online of IP or IPMultiNICB resource may fail if its IP address specifieddoes not fit within the values specified in the allowed-address property(2729505)While configuring an IP or IPMultiNICB resource to be run in a zone, if the IPaddress specified for the resource does not match the values specified in theallowed-address property of the zone configuration, then the online of IP resourcemay fail. This behavior is seen only on Solaris 11 platform.Workaround: Ensure that the IP address is added to allowed-address property ofthe zone configuration.Application resource running in a container with PidFiles attribute reportsoffline on upgrade to VCS 6.0 or later [2850927]Application resource configured to run in a container configured with PidFilesattribute reports state as offline after upgrade to SF 6.0 or later versions.When you upgrade SF from lower versions to 6.0 or later, if application resourcesare configured to run in a container with monitoring method set to PidFiles, thenupgrade may cause the state of the resources to be reported as offline. This is dueto changes introduced in the Application agent where if the resource is configured
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:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44: About Veritas Storage Foundation an
Page 93: About Veritas Storage Foundation an
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

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

Delete template?

Save as template?