148
Solaris 7 11/99 Sun Hardware Platform Guide • November 1999
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
upgrade to the Solaris 7 11/99 operating environment, you need to be aware of the
issues described in this section.
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 from a domain. If that
system board hosts I/O controllers, and other higher numbered system boards in the
domain 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.
If you do not have a good understanding of device numbering, either perform a
fresh install and recreate your AP configuration from scratch, or ask your service
representative for assistance. In general, you should avoid changing your hardware
in ways that can result in controller renumbering.
AP Database Partitions
The AP upgrade scripts attempt to recreate the AP databases in the same partitions
that they occupied before the upgrade to Solaris 7 11/99 operating environment.
Note, however, that the Solaris 7 11/99 operating environment requires more disk
space than earlier Solaris versions. Because of this, you may choose to modify the
boot disk partitioning scheme during
suninstall
. If you place file systems in all
Содержание Solaris 7 11/99
Страница 12: ...xii Solaris 7 11 99 Sun Hardware Platform Guide November 1999...
Страница 24: ...12 Solaris 7 11 99 Sun Hardware Platform Guide November 1999...
Страница 34: ...22 Solaris 7 11 99 Sun Hardware Platform Guide November 1999...
Страница 70: ...58 Solaris 7 11 99 Sun Hardware Platform Guide November 1999...
Страница 128: ...116 Solaris 7 11 99 Sun Hardware Platform Guide November 1999...
Страница 150: ...138 Solaris 7 11 99 Sun Hardware Platform Guide November 1999...
Страница 172: ...160 Solaris 7 11 99 Sun Hardware Platform Guide November 1999...
Страница 212: ...200 Solaris 7 11 99 Sun Hardware Platform Guide November 1999...
Страница 220: ...208 Solaris 7 11 99 Sun Hardware Platform Guide November 1999...
Страница 224: ...212 Solaris 7 11 99 Sun Hardware Platform Guide November 1999...