Veritas Storage Foundation and High Availability Solutions Release Notes

More documents

Recommendations

Info

114About Veritas Storage Foundation and High Availability SolutionsKnown issuesWorkaround: No workaround.AMF displays StartProgram name multiple times on the console without aVCS error code or logs [2872064]When VCS AMF prevents a process from starting, it displays a message on theconsole and in syslog. The message contains the signature of the process that wasprevented from starting. In some cases, this signature might not match thesignature visible in the PS output. For example, the name of the shell script thatwas prevented from executing will be printed twice.Workaround: No workaround.Terminating the imfd daemon orphans the vxnotify process [2728787]If you terminate imfd daemon using the kill -9 command, the vxnotify processcreated by imfd does not exit automatically but gets orphaned. However, if youstop imfd daemon with the amfconfig -D command, the corresponding vxnotifyprocess is terminated.Workaround: The correct way to stop any daemon is to gracefully stop it with theappropriate command (which is amfconfig -D command in this case), or toterminate the daemon using Session-ID. Session-ID is the -PID (negative PID) ofthe daemon.For example:# kill -9 27824Stopping the daemon gracefully stops all the child processes spawned by thedaemon. However, using kill -9 pid to terminate a daemon is not a recommendedoption to stop a daemon, and subsequently you must kill other child processes ofthe daemon manually.Issues related to the Cluster Manager (Java Console)This section covers the issues related to the Cluster Manager (Java Console).Some Cluster Manager features fail to work in a firewall setup [1392406]In certain environments with firewall configurations between the Cluster Managerand the VCS cluster, the Cluster Manager fails with the following error message:V-16-10-13 Could not create CmdClient. Command Servermay not be running on this system.Workaround: You must open port 14150 on all the cluster nodes.
About Veritas Storage Foundation and High Availability SolutionsKnown issues115Unable to log on to secure VCS clusters on Solaris 11 using Java GUI(2718943)Connecting to secure clusters deployed on Solaris 11 systems using VCS Java GUIis not supported in VCS 6.0PR1. The system displays the following error whenyou attempt to use the Java GUI:Incorrect username/passwordWorkaround: No workaround.Issues related to virtualizationLocale message displayed on Solaris 11 system for solaris10 brand zonesWhen you run the zlogin command on a Solaris 11 system, the system logs thefollowing error message:Could not set locale correctly.The default locale for Solaris 11 is en_US.UTF-8 and that of Solaris 10 is C. Withsolaris10 brand zone, en_US.UTF-8 is not installed inside the zone by default.Therefore, the error message is logged.Workaround: This message can be safely ignored as there is no functionality issue.To avoid this message, install en_US.UTF-8 locale on solaris10 brand zone.Veritas Storage Foundation and High Availability known issuesFor known issues of Veritas Storage Foundation and High Availability in thisrelease, see Veritas Storage Foundation known issues and Veritas Cluster Serverknown issues .Veritas Storage Foundation Cluster File System High Availability knownissuesThis section describes the Veritas Storage Foundation Cluster File System HighAvailability known issues in 6.0.3 and 6.0.1.The vxfsckd resource fails to start when vxfsckd is killedmanually and the cluster node is rebooted (2720034)If you kill the vxfsckd resource manually and reboot the node, vxfsckd does notcome up and the cvm services are faulted.Workaround:
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:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64: About Veritas Storage Foundation an
Page 113: 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 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?