test

Sun Enterprise Server Alternate Pathing 2.0.1 Installation and Release Notes

Chapter 3 Alternate Pathing 2.0.1 Upgrade

This chapter contains upgrade instructions for Alternate Pathing (AP) 2.0.1 on the Sun Enterprise 10000 server. The upgrade process involves the following tasks:

Caution - Caution -

The SSP must be running the SSP 3.1 software to support AP 2.0.1. SSP 3.0 does not support AP 2.0.1.

General Issues

Installation of the packages on the enclosed CD-ROM requires approximately 2.7 megabytes of disk space on the host domain and 37 kilobytes on the SSP. The following table lists the total size of the AP software by file system:

Table 3-1 AP Software File-System Sizes

File System 

Size 

Domain: 

 

/opt

1.23-Mbytes 

/usr

158-Kbytes 

/

1.3-Mbytes 

SSP: 

 

/opt

37-Kbytes 

Backing Up Your Server

Always back up an existing server before you upgrade any software. The safest backup to perform is a level 0 dump (ufsdump(1M)) of the file systems connected to the server being upgraded. If you do not have an established backup procedure, see the System Administration Guide.

You do not need to back out installed patches before you perform the upgrade.

Checking Other Software Documentation

Check the documentation of other software you are running, such as any 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

Before you run the ap_upgrade_begin script, you must commit any uncommitted entries in the AP database. Any metadevices that were created, but not committed, are not preserved during the upgrade. Similarly, any metadevices that were deleted, but not committed, will exist after the upgrade.

Caution - Caution -

Before proceeding with the following procedure, read the release notes for AP as well as the release notes for any volume managers you may be using. Also, read through this entire procedure before proceeding.

To Prepare the Domain

  1. Open a netcon(1M) window.

  2. Log in to the domain as superuser.

  3. If necessary, commit the entries in the AP database.


    # apdb -C

  4. Terminate any processes that directly or indirectly access AP metadevices.

    You do not need to be concerned about the boot disk or networks configured in the /etc/hostname.metanetwork_name files that use AP metadevices. The ap_upgrade_begin script and the subsequent reboot will cause the boot disk and those networks to use physical paths rather than the AP metadevices.

  5. Disable any start-up scripts that reference AP metadevices.

    You can edit the start-up scripts so that they use the physical device names if you prefer to do so.

  6. Deconfigure any volume managers that are built on top of AP metadevices.

    These include SolsticeTM DiskSuiteTM (SDS) and Sun EnterpriseTM Volume Manager (SEVM). Follow the vendor's instructions for deconfiguring the volume manager. Keep the following points in mind:

    • Most likely, you should follow the deconfiguration steps within the procedure that upgrades the volume manager to a newer version.

    • After following the steps that deconfigure the volume manager's devices, you may be in the middle of a volume manager upgrade procedure. Do not proceed beyond the point of deconfiguring the volume manager.

    • Do not install new volume manager packages.

    • Be sure to reboot before continuing with this procedure. This assures that the deconfigured disk volumes are no longer active.

    • Return here and continue with this AP upgrade procedure immediately after deconfiguring the volume manager.

To Remove AP from the Domain

  1. Log in to the SSP as superuser.

  2. Insert the Sun Enterprise Sever Alternate Pathing 2.0.1 CD into the CD-ROM drive of the SSP.

    Wait for the volume manager to mount the CD.

  3. Share the CD-ROM so that it can be accessed over the network.


    ssp# share -o ro,anon=0 -F nfs /cdrom/cdrom0

  4. In the netcon window, create and mount the /cdrom directory.


    # mkdir /cdrom
# mount ssp_hostname:/cdrom/cdrom0 /cdrom

  5. Run the ap_upgrade_begin script to deconfigure AP and to save the AP configuration:


    # /cdrom/Tools/ap_upgrade_begin
...
ap_upgrade_begin has completed

    The script saves the current AP configuration information in the /var/tmp/ap* files. The script also generates executable shell scripts that you can use to regenerate your AP configuration. You may examine the /var/tmp/ap* files if you wish, but do not modify or remove them. Doing so can compromise the upgrade procedure.

  6. If any file systems shown in /etc/vfstab are still configured as AP metadevices, edit /etc/vfstab and reconfigure those file systems as physical devices.

    Caution - Caution -

    If you do not configure the file systems properly in /etc/vfstab, you could lose data when you reboot the domain.

  7. Use the pkgrm(1M) command to remove the existing AP 2.0 packages.

    You should remove the following packages:

    • SUNWapdoc

    • SUNWapr

    • SUNWapu

    • SUNWabap

  8. Reboot the domain.

To Update Your AP 2.0 Domain

Perform this procedure on all of the AP 2.0 domains that will remain in the server along with any AP 2.0.1 domains.

Caution - Caution -

If you want to run AP 2.0 on any domain in the platform, you must install, at a minimum, revision 11 of Patch 105029 on that domain. Revision 11 is on the Sun Enterprise Server Alternate Pathing 2.0.1 CD. Patch 105029 is a maintenace update patch that is updated periodically. You can check the patch revision level at http://www.sunsolve.com if you are interested in obtaining the latest version of Patch 105029; however, it is not necessary for this upgrade.

  1. Open a netcon(1M) window, and log in to the AP 2.0 domain as superuser.

  2. In the netcon window, create and mount the /cdrom directory.


    # mkdir /cdrom
# mount ssp_hostname:/cdrom/cdrom0 /cdrom

  3. Change to the /cdrom/Patches directory, and read the contents of the README file for Patch 105029-11.

  4. In the netcon window, install Patch 105029-11 by following the instructions in the README file.

  5. Unmount the CDROM directory and log out of the AP 2.0 domain.

    Repeat this section for all of the AP 2.0 domains that will remain on the server after the upgrade to AP 2.0.1 on the SSP.

To Upgrade AP on the SSP
Caution - Caution -

You should upgrade the SUNWapssp pacakge only if it is version 2.0. If you have installed a higher version of AP on the SSP (for example, AP 2.1 or 2.2), skip the steps in this section. You should not remove the existing version of the SUNWapssp package, nor should you kill the ap_ssp_daemon. The SUNWapssp package must be part of the highest version of AP on the entire server.

  1. Use pkgrm(1M) to remove the SUNWapssp package on the main SSP and the spare SSP (if you have one).

  2. In the SSP window, kill the ap_ssp_daemon process.

  3. Install the SUNWapssp package on both the main SSP and the spare SSP (if you have one).


    ssp# cd /cdrom/cdrom0/Product
ssp# pkgadd -d . SUNWapssp

  4. Start the ap_ssp_daemon on the main SSP.


    ssp# init q

    If you have upgraded the AP daemon on the SSP as part of the fresh-install of AP 2.0.1, return to "To Install AP 2.0.1 on the Domain".

To Upgrade To AP 2.0.1 on the Domain

  1. In the netcon window, install the AP packages.


    # cd /cdrom/Product
# pkgadd -d . SUNWapr SUNWapu SUNWapdoc SUNWabap

  2. Run the following script to restore the original AP configuration.


    # /cdrom/Tools/ap_upgrade_finish
...
ap_upgrade_finish has completed

  3. If there are any file systems shown in /etc/vfstab that are still configured as physical devices, and if you wish to build those file systems on AP metadevices, edit /etc/vfstab and reconfigure those file systems as AP metadevices.

    Caution - Caution -

    If you do not configure the file system properly in /etc/vfstab, you could lose data when you reboot the domain.

  4. Re-enable any start-up scripts that were disabled during this upgrade.

    If you edited any start-up scripts during this upgrade so that they use the physical device names, you need to edit them to use the metadevice names.

  5. Reboot the domain.

To Finish the Upgrade

  1. On the SSP, unshare the CD-ROM drive, and remove the Sun Enterprise Sever Alternate Pathing 2.0.1 CD.


    ssp# cd /
ssp# unshare /cdrom/cdrom0
ssp# eject cdrom

  2. Restore any volume managers that you deconfigured.

    Follow your vendor's instructions for restoring the volume manager configuration.

  3. If necessary, set the OBP boot-device variable to the primary boot device path.