Sun Microsystems Solaris 7 11/99, Hardware Platform Manual

Page: 149 / 224

Chapter 8 Alternate Pathing 2.2 on the Sun Enterprise 3x00, 4x00, 5x00, and 6x00 Servers 137
9. Optionally set the OBP
boot-device
variable to any available boot device path.
There may be as many as four boot device paths if you have a mirrored boot disk
that is also alternately pathed. (Earlier in this procedure, when both AP and the
volume manager were deconfigured, it was necessary for
boot-device
to point to
the physical path to root (
/
) as specified in
/etc/vfstab
.)
Upgrading to AP 2.2 and a Volume Manager
Other Than Solstice DiskSuite 4.2
If you are upgrading to AP 2.2 and you are also upgrading to a volume manager
other than Solstice DiskSuite 4.2, follow the general guidelines in this section.
Caution –
Make sure that your volume manager is supported in the Solaris 7 11/99
operating environment (which is required for AP 2.2).
Use the procedure “To Upgrade To AP 2.2 and SDS 4.2” on page 134 as an example.
However, two of the steps are different:
■
Instead of Step 2, “Deconfigure Solstice DiskSuite (SDS)”, use the following
general guidelines:
1. Most likely, you should follow the deconfiguration steps within a procedure that
upgrades the volume manager to a newer version.
2. After following the steps that deconfigure the volume manager devices, you may
be in the middle of a volume manager upgrade procedure. Do not proceed
beyond the point of deconfiguring the volume manager.
3. Do not install new volume manager packages.
4. Do not run
suninstall
.
5. Continue with Step 3 of “To Upgrade To AP 2.2 and SDS 4.2” on page 134
immediately after deconfiguring the volume manager.
■
Instead of Step 8, “Install and Configure Solstice DiskSuite 4.2”, follow your
vendor’s instructions for restoring the volume manager configuration. Most
likely, you should continue with the procedure you were following in the bullet
point above.