Sun Microsystems Solaris 7 11/99, Руководство по аппаратной платформе

Страница: 141 / 224

Chapter 8 Alternate Pathing 2.2 on the Sun Enterprise 3x00, 4x00, 5x00, and 6x00 Servers 129
Checking Other Software Documentation
Check the documentation of other software you are running, such as disk volume
managers, before you use the
upgrade
option in the
suninstall
utility. There may
be additional instructions you need to follow to preserve existing configurations.
Also, be sure to check the release notes for AP and any volume managers you are
using.
Upgrading AP and Solaris Software
Simultaneously
The AP upgrade procedures in this section use two scripts,
ap_upgrade_begin
and
ap_upgrade_finish
. The first script saves your current AP configuration. The
second script restores that exact configuration after you install the AP 2.2 packages.
It is likely that you will upgrade to the Solaris 7 11/99 operating environment at the
same time you upgrade to AP 2.2, since AP 2.2 requires the Solaris 7 11/99 operating
environment. Because the AP configuration is restored exactly as it was before you
upgraded to Solaris 7 11/99 software, you need to be aware of the issues described
in the following sections.
Controller Renumbering
In general, avoid changing your hardware in ways that can result in controller
renumbering.
If I/O controller renumbering occurs, the AP upgrade scripts will not work. I/O
controller renumbering can occur if you alter your hardware configuration in certain
ways, and then perform a reconfigure boot (
boot -R
) or otherwise cause a
drvconfig(1M)
command to be executed. For example, you might use Dynamic
Reconfiguration (DR) to logically detach a system board. If that system board hosts
I/O controllers, and other higher numbered system boards also host I/O controllers,
the next reconfigure boot operation may cause the controllers to be renumbered. For
example,
pln5
may become
pln3
.
The
suninstall
procedure requires a reconfigure boot operation. If this causes
controllers to be renumbered, you cannot use
ap_upgrade_finish
to complete the
AP upgrade. However, you may still choose to use
ap_upgrade_begin
. The reason
for this is that
ap_upgrade_begin
saves information about your AP configuration
in the files
/var/tmp/ap*
. If you have a deep understanding of the way device
numbering works, you can recreate your AP configuration by referencing those files
under
/var/tmp
, and manually remapping the old AP configuration after taking
into consideration how the underlying physical controllers have been renumbered.