Veritas Storage Foundation and High Availability Solutions Release Notes

46About Veritas Storage Foundation and High Availability SolutionsKnown issuesWorkaround: On the Solaris system, make sure that all non-global zones arestarted and in the running state before you install the VRTSvlic package.VRTSvcsea package cannot be uninstalled from alternate diskin manual live upgradeDescription: In manual live upgrade procedure from 5.1x to 5.1SP1 , all packagesare copied to an alternate root disk. However, VRTSvcsea package cannot beuninstalled from alternate disk to upgrade it to 5.1SP1.Workaround : Instead of removing the VRTSvcsea package, you must apply apatch to upgrade this package to 5.1SP1 version.VCS Zone users must be added after upgrade to VCS 6.0If you upgrade your configuration containing Zone resources to VCS 6.0 from:■■VCS 5.1SP1RP1 or later VCS releases with DeleteVCSZoneUser attribute ofZone agent set to 1VCS 5.1SP1 or ealier VCS releasesYou may see the following issue.Zone agent offline/clean entry points delete VCS Zone users from configuration.After upgrade to VCS 6.0, VCS Zone users need to be added to the configuration.VCS Zone users can be added by running hazonesetup utility with new syntaxafter upgrade. See the Veritas Storage Foundation and High Availability SolutionsVirtualization Guide for Solaris for more information on hazonesetup utility andsee the Veritas Storage Foundation and High Availability Solutions VirtualizationGuide for Solaris.VCS installation with CPI fails when a non-global zone is ininstalled state and zone root is not mounted on the node(2731178)On Solaris 10, CPI tries to boot a zone in installed state during installation/ oruninstallation. The boot fails if the underlying storage for zone root is not importedand mounted onto the node, causing the installation or uninstallation to fail.Workaround: Make sure that the non-global zones are in running or configuredstate when CPI is invoked for installation or uninstallation.