Veritas Storage Foundation and High Availability Solutions Release Notes

More documents

Recommendations

Info

104About Veritas Storage Foundation and High Availability SolutionsKnown issuesBoth these variables are integers. With constant traffic, recvbytes hits and rollsover MAX_INT quickly. This can cause the value of recvbytes to be less than thevalue of recvcnt.This does not impact the LLT functionality.GAB known issuesThis section covers the known issues related to GAB in this release.Cluster panics during reconfiguration (2590413)While a cluster is reconfiguring, GAB broadcast protocol encounters a racecondition in the sequence request path. This condition occurs in an extremelynarrow window which eventually causes the GAB master to panic.Workaround: There is no workaround for this issue.GAB SMF service sometimes fails to start after reboot (2724565)In SFRAC environments, sometimes GAB might fail to start because of the racebetween GAB and LMX in calling add_drv.Workaround: Start the GAB SMF service and all other dependent services manuallyusing:# svcadm enable gab# svcadm enable vxfen# svcadm enable vcsGAB may fail to stop during a phased upgrade on Oracle Solaris 11(2858157)While performing a phased upgrade on Oracle Solaris 11 systems, GAB may failto stop. However, CPI gives a warning and continues with stopping the stack.Workaround: Reboot the node after the installer completes the upgrade.Cannot run pfiles or truss files on gablogd (2292294)When pfiles or truss is run on gablogd, a signal is issued to gablogd. gablogd isblocked since it has called an gab ioctl and is waiting for events. As a result, thepfiles command hangs.Workaround: None.(Oracle Solaris 11) On virtual machines, sometimes the common productinstaller (CPI) may report that GAB failed to start and may exit (2879262)GAB startup script may take longer than expected to start up. The delay in startup can cause the CPI to report that GAB failed and exits.
About Veritas Storage Foundation and High Availability SolutionsKnown issues105Workaround: Manually start GAB and all dependent services.While deinitializing GAB client, "gabdebug -R GabTestDriver" commandlogs refcount value 2 (2536373)After you unregister the gtx port with -nodeinit option, the gabconfig -Ccommand shows refcount as 1. But when forceful deinit option (gabdebug -RGabTestDriver) is run to deinitialize GAB client, then a message similar to thefollowing is logged.GAB INFO V-15-1-20239Client GabTestDriver with refcount 2 forcibly deinited on user requestThe refcount value is incremented by 1 internally. However, the refcount valueis shown as 2 which conflicts with the gabconfig -C command output.Workaround: There is no workaround for this issue.Fail to stop GAB when upgrading the second sub cluster (3066737)On Solaris 11, in the phased upgrade scenario which includes the Veritas ClusterServer components, the GAB kernel driver may fail to unload on some nodes insome cases. The script based installer will display the following message in suchsituation:gab failed to stop on sys1It is recommended to reboot the systems sys1 to resolvethe failures and then retry. If issues persist after reboot,contact Symantec technical support or refer toinstallation guide for further troubleshooting.Do you want to continue? [y,n,q] (n) yWorkaround:Continue to upgrade the second sub cluster, then execute/usr/sbin/shutdown-y -i6 -g0 to restart the nodes when the whole upgrade is completed.I/O fencing known issuesThis section covers the known issues related to I/O fencing in this release.Delay in rebooting Solaris 10 nodes due to vxfen service timeout issues(1897449)When you reboot the nodes using the shutdown -i6 -g0 -y command, thefollowing error messages may appear:
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:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54: About Veritas Storage Foundation an
Page 103: About Veritas Storage Foundation an
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?