Veritas Storage Foundation and High Availability Solutions Release Notes
Veritas Storage Foundation⢠and High ... - SORT - Symantec Veritas Storage Foundation⢠and High ... - SORT - Symantec
40About Veritas Storage Foundation and High Availability SolutionsKnown issuesProcessing profileERROR: This slice can't be upgraded because of missing usr packages forthe following zones:ERROR: zone1ERROR: zone1ERROR: This slice cannot be upgraded because of missing usr packages forone or more zones.The Solaris upgrade of the boot environment failed.This is a known issue with the Solaris luupgrade command.Workaround: Check with Oracle for possible workarounds for this issue.Live Upgrade to 6.0.1 on Solaris 10 with dmp_native_supportenabled fails (2632422)During Live Upgrade to 6.0.1 on Solaris 10, the vxlustart command fails ifdmp_native_support is enabled. Veritas Dynamic Multi-Pathing (DMP) supportfor native devices requires that the naming scheme be set to enclosure-basednaming (EBN). DMP 6.0.1 does not allow changing the naming scheme from EBNwhen support for native devices is enabled.Due to a bug in DMP 5.1 Service Pack 1 (5.1SP1), the naming scheme could be setto operating-system based naming (OSN). However, this is not a supportedconfiguration. With the naming scheme set to OSN, the vxlustart command fails.Workaround: Disable dmp_native_support on all nodes.On Solaris 10, a flash archive installed through JumpStart maycause a new system to go into maintenance mode on reboot(2379123)If a Flash archive is created on a golden host with encapsulated root disks, whenthis Flash archive is installed onto another host through JumpStart, the newsystem may go to maintenance mode when you initially reboot it.This problem is caused by the predefined root disk mirror in the Flash archive.When the archive is applied to a clone system, which may have different harddrives, the newly cloned system may get stuck at root disk mirroring during reboot.Workaround: Create the Flash archive on a golden host with no encapsulatedroot disks. Run vxunroot to clean up the mirrored root disks before you createthe Flash archive.
About Veritas Storage Foundation and High Availability SolutionsKnown issues41Web installer does not ask for authentication after the firstsession if the browser is still open (2509330)If you install or configure SF and then close the Web installer, if you have otherbrowser windows open, the Web installer does not ask for authentication in thesubsequent sessions. Since there is no option to log out of the Web installer, thesession remains open as long as the browser is open on the system.Workaround: Make sure that all browser windows are closed to end the browsersession and subsequently log in again.Stopping the Web installer causes Device Busy error messages(2633924)If you start the Web installer, and then perform an operation (such as prechecking,configuring, or uninstalling), you may get an error message saying the device isbusy.Workaround: Do one of the following:■■Kill the start.pl process.Start the webinstaller again. On the first Web page you see that the session isstill active. Either take over this session and finish it or terminate it directly.Perl module error on completion of SF installation (2873102)When you install, configure, or uninstall SF, the installer prompts you to optionallyupload installation logs to the Symantec Web site. If the installer encountersconnectivity problems, you may see an error similar to the following:Status read failed: Connection reset by peer at/../perl/lib/5.14.2/Net/HTTP/Methods.pm line 269.Workaround:Ignore this error. It is harmless.Installed 5.0 MP3 without configuration, then upgrade to 6.0.1,installer cannot continue (2016346)If you install the 5.0 MP3 release without configuring the product, then you cannotupgrade to the 6.0.1 release. This upgrade path is not supported.Workaround: Uninstall 5.0 MP3, and then install 6.0.1.
- 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: About Veritas Storage Foundation an
- Page 17 and 18: About Veritas Storage Foundation an
- Page 19 and 20: About Veritas Storage Foundation an
- Page 21 and 22: About Veritas Storage Foundation an
- Page 23 and 24: About Veritas Storage Foundation an
- Page 25 and 26: About Veritas Storage Foundation an
- Page 27 and 28: About Veritas Storage Foundation an
- Page 29 and 30: About Veritas Storage Foundation an
- Page 31 and 32: About Veritas Storage Foundation an
- Page 33 and 34: About Veritas Storage Foundation an
- Page 35 and 36: About Veritas Storage Foundation an
- Page 37 and 38: About Veritas Storage Foundation an
- Page 39: About Veritas Storage Foundation an
- Page 43 and 44: About Veritas Storage Foundation an
- Page 45 and 46: About Veritas Storage Foundation an
- Page 47 and 48: About Veritas Storage Foundation an
- Page 49 and 50: About Veritas Storage Foundation an
- Page 51 and 52: About Veritas Storage Foundation an
- Page 53 and 54: About Veritas Storage Foundation an
- Page 55 and 56: About Veritas Storage Foundation an
- Page 57 and 58: About Veritas Storage Foundation an
- Page 59 and 60: About Veritas Storage Foundation an
- Page 61 and 62: About Veritas Storage Foundation an
- Page 63 and 64: About Veritas Storage Foundation an
- Page 65 and 66: About Veritas Storage Foundation an
- Page 67 and 68: About Veritas Storage Foundation an
- Page 69 and 70: About Veritas Storage Foundation an
- Page 71 and 72: About Veritas Storage Foundation an
- Page 73 and 74: About Veritas Storage Foundation an
- Page 75 and 76: About Veritas Storage Foundation an
- Page 77 and 78: About Veritas Storage Foundation an
- Page 79 and 80: About Veritas Storage Foundation an
- Page 81 and 82: About Veritas Storage Foundation an
- Page 83 and 84: About Veritas Storage Foundation an
- Page 85 and 86: About Veritas Storage Foundation an
- Page 87 and 88: About Veritas Storage Foundation an
- Page 89 and 90: About Veritas Storage Foundation an
40About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Known issuesProcessing profileERROR: This slice can't be upgraded because of missing usr packages forthe following zones:ERROR: zone1ERROR: zone1ERROR: This slice cannot be upgraded because of missing usr packages forone or more zones.The Solaris upgrade of the boot environment failed.This is a known issue with the Solaris luupgrade comm<strong>and</strong>.Workaround: Check with Oracle for possible workarounds for this issue.Live Upgrade to 6.0.1 on Solaris 10 with dmp_native_supportenabled fails (2632422)During Live Upgrade to 6.0.1 on Solaris 10, the vxlustart comm<strong>and</strong> fails ifdmp_native_support is enabled. <strong>Veritas</strong> Dynamic Multi-Pathing (DMP) supportfor native devices requires that the naming scheme be set to enclosure-basednaming (EBN). DMP 6.0.1 does not allow changing the naming scheme from EBNwhen support for native devices is enabled.Due to a bug in DMP 5.1 Service Pack 1 (5.1SP1), the naming scheme could be setto operating-system based naming (OSN). However, this is not a supportedconfiguration. With the naming scheme set to OSN, the vxlustart comm<strong>and</strong> fails.Workaround: Disable dmp_native_support on all nodes.On Solaris 10, a flash archive installed through JumpStart maycause a new system to go into maintenance mode on reboot(2379123)If a Flash archive is created on a golden host with encapsulated root disks, whenthis Flash archive is installed onto another host through JumpStart, the newsystem may go to maintenance mode when you initially reboot it.This problem is caused by the predefined root disk mirror in the Flash archive.When the archive is applied to a clone system, which may have different harddrives, the newly cloned system may get stuck at root disk mirroring during reboot.Workaround: Create the Flash archive on a golden host with no encapsulatedroot disks. Run vxunroot to clean up the mirrored root disks before you createthe Flash archive.
Change language