Preparing the Domain

This section contains instructions for preparing the domain to be upgraded to the Solaris 7 operating environment. You must perform the following instructions before you attempt the upgrade.

1. Log in to each domain as superuser and backup the domain.

   Using ufsdump(1M), backup all operating-system file systems.

2. Comment out all file systems in the /etc/vfstab file except root (/), /usr, /export,/var, /opt, /proc, /dev/fd, /tmp, and swap.

3. Comment out all swap partitions that are not on the same controller as the root disk.

   During an upgrade, the suninstall utility attempts to mount all file systems listed in the /etc/vfstab file on the root file system being upgraded. If the suninstall utility cannot mount a file system, it reports the failure and exits.

4. If any file systems shown in the /etc/vfstab file are metadevices (for example, mirrored, striped, concatenated) for Solstice DiskSuite, Veritas, or Alternate Pathing and have not already been commented out, reconfigure them as non-metadevices for the upgrade.

   This step is necessary because the suninstall utility cannot handle metadevices. For more information about these products, refer to their respective user's guides.

   ---

   Caution -

   Make certain that all metadevices are commented out. If any are not, the upgrade will fail.

   ---

5. Save all of the information regarding pathgroups (for example, apconfig -S and apconfig -N) for later retrieval.

   ---

   Note -

   AP 2.0 and 2.1 are not supported by Solaris 7; therefore, if you have either version of AP installed, you must convert all of the AP metadevices to physical devices. Refer to the Sun Enterprise Server Alternate Pathing User's Guide for more information on how to convert metadevices.

   ---

6. If you do not plan to upgrade the AP software to AP 2.2 Beta, convert metanetworks to their respective physical network device.

7. If you do not plan to upgrade the AP software to AP 2.2 Beta, convert metadevices to their respective physical devices.

8. If the boot device is under AP control, use the apboot(1M) command to convert the boot device to a physical device.

9. Reboot the domain:

   ---

   domain_name# init 6

   ---

10. Remove all of the AP databases.

11. Kill the ap_daemon process.

12. Remove all of the AP packages from the domain by using the pkgrm(1M) command.

    You should remove the following packages from the domain:

    • SUNWapu

    • SUNWapr

    • SUNWapdoc

13. If you are upgrading from Solaris 2.5.1, remove the SUNWxntp packages by using the pkgrm(1M) command.

14. Remove duplicate boot-device entries.

    1. If you are at the ok prompt, use the OBP setenv command to set the default boot-device alias to the correct device.

       ---

       ok setenv boot-device boot_device_alias
       

       ---

       Where boot_device_alias corresponds to the correct default boot-device alias.

    2. If diag-switch? is set to true, use the OBP setenv command to set the diag-device variable to the correct device.

       ---

       ok setenv diag-device boot_device_alias
       

       ---

       ---

       Note -

       If diag-switch? is set to true, OBP uses diag-device and diag-file as the default boot parameters. If diag-switch? is false, OBP uses boot-device and boot-file as the default boot parameters.

       ---

    3. If you are at the domain prompt, log in as superuser on the domain, then use the eeprom(1M) command to set the boot-device variable:

       ---

       domain_name# eeprom boot-device=boot_device_alias
       

       ---

15. Shut down the domain before you begin the upgrade:

    ---

    domain_name# cd /
    domain_name# lockfs -fa
    domain_name# shutdown -i0 -g60 -y
    

    ---

    ---

    Note -

    The lockfs -fa command is unnecessary when running 2.5.1 kernel update 103640-12.

    ---