Veritas Storage Foundation and High Availability Solutions Release Notes

More documents

Recommendations

Info

86About Veritas Storage Foundation and High Availability SolutionsKnown issuesStartup trust failure messages in system logs [2721512]If you configure a cluster with security enabled, there might be some messageslogged in system message logs related to Symantec authentication. These messagescan be ignored and have no effect on functionality.Workaround: No workaround.Elevated TargetCount prevents the online of a service group with hagrp-online -sys command [2871892]When you initiate an offline of a service group and before the offline is complete,if you initiate a forced flush, the offline of the service group which was initiatedearlier is treated as a fault. As start bits of the resources are already cleared,service group goes to OFFLINE|FAULTED state but TargetCount remains elevated.Workaround: No workaround.Auto failover does not happen in case of two successive primary andsecondary cluster failures [2858187]In case of three clusters (clus1, clus2, clus3) in a GCO with steward not configured,if clus1 loses connection with clus2, it sends the inquiry to clus3 to check the stateof clus2 one of the following condition persists:1. If it is able to confirm that clus2 is down, it will mark clus2 as FAULTED.2. If it is not able to send the inquiry to clus3, it will assume that a networkdisconnect might have happened and mark clus2 as UNKNOWNIn second case, automatic failover does not take place even if theClusterFailoverPolicy is set to Auto. You need to manually failover the globalservice groups.Workaround: Configure steward at a geographically distinct location from theclusters to which the above stated condition is applicable.The ha commands may fail for non-root user if cluster is secure [2847998]The ha commands fail to work if you first use a non-root user without a homedirectory and then create a home directory for the same user.Workaround1 Delete /var/VRTSat/profile/.2 Delete /home/user_name/.VRTSat.3 Delete /var/VRTSat_lhc/ file which same non-root user owns.4 Run ha command with same non-root user (this will pass).
About Veritas Storage Foundation and High Availability SolutionsKnown issues87Older ClusterAddress remains plumbed on the node while modifyingClusterAddress [2858188]If you execute gcoconfig to modify ClusterAddress when ClusterService groupis online, the older ClusterAddress remains plumbed on the node.Workaround: Un-plumb the older ClusterAddress from the node manually oroffline ClusterService group by executing the following command before runninggcoconfig:hagrp -offline -force ClusterService -anyorhagrp -offline -force ClusterService -sys VRTSvcs package may give error messages for package verification onSolaris 11 [2858192]VRTSvcs package may give error messages for package verification on Solaris 11.This is because some of the VCS configuration files are modified as part of productconfiguration. This error can be ignored.Workaround: No workaround.GCO clusters remain in INIT state [2848006]GCO clusters remain in INIT state after configuring GCO due to :■Trust between two clusters is not properly set if clusters are secure.■ Firewall is not correctly configured to allow WAC port (14155).Workaround: Make sure that above two conditions are rectified. Refer to VeritasCluster Server Administrator's Guide for information on setting up Trustrelationships between two clusters.Older ClusterAddress remains plumbed on the node while modifyingClusterAddress [2847997]If you execute gcoconfig to modify ClusterAddress when ClusterService groupis online, the older ClusterAddress remains plumbed on the node.Workaround: Un-plumb the older ClusterAddress from the node manually oroffline ClusterService group by executing the following command before runninggcoconfig:hagrp -offline -force ClusterService
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: About Veritas Storage Foundation an
Page 85: About Veritas Storage Foundation an
Page 137 and 138:
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?