test

Sun Enterprise Server Alternate Pathing 2.0.1 Installation and Release Notes

Chapter 2 Alternate Pathing 2.0.1 Fresh Install

This chapter contains fresh install instructions for Alternate Pathing (AP) 2.0.1 on the Sun Enterprise 10000 server. If you have AP 2.0 installed on the server, refer to Chapter 3, Alternate Pathing 2.0.1 Upgrade. The fresh-install 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. Additionally, AP 2.0.1 runs on Solaris 2.5.1 only; however, the data format that it uses to communicate with the SSP is compatible with other versions of AP running on other domains.

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 2-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 install any software. The safest backup to perform is a level 0 dump (ufsdump(1M)) of the file systems connected to the server. 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 installation.

Checking Other Software Documentation

Check the documentation of other software you are running, such as any disk volume managers, before you install the AP packages. 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.

Caution - Caution -

Before you proceed with the following procedures, read the release notes for AP 2.0.1, as well as the release notes for any volume managers you may be using.

Installing AP

This section contains instructions on how to install the AP 2.0.1 packages. You should read this entire section before you attempt to install the AP packages. You must also perform the procedures in the exact order in which they appear.

Before you install the AP software on the SSP, you must determine which of the following conditions apply to your situation. The following list includes references to the sections you must complete in the order they are presented (all of the sections are in this chapter unless otherwise noted):

To Prepare for the Installation

  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

To Update Your AP 2.0 Domain

  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 CD-ROM directory and log out of the AP 2.0 domain.

    Repeat this section for each AP 2.0 domain that will remain on the server after the upgrade to AP 2.0.1 on the SSP.

To Install AP 2.0.1 on the SSP

  1. If needed, log in to the SSP as supersuser.

  2. Install the SUNWapssp package on the main SSP and the spare SSP if you have one.


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

  3. Start the ap_ssp_daemon on the main SSP.


    ssp# init q

To Install AP 2.0.1 on the Domain

  1. In the netcon(1M) window, log in to the domain as superuser.

  2. In the netcon(1M) window, create and mount the /cdrom directory.


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

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


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

    The software briefly displays copyright, trademark, and license information for each package, then messages about pkgadd(1M) actions taken to install the package, including a list of the files and directories being installed. Depending on your configuration, you may see the following message: 


    This package contains scripts which will be executed with superuser permission during the process of installing this package.Do you want to continue with the installation of this package [y,n,?]

    Type y to continue.

    When this portion of the installation is complete, the AP 2.0.1 packages have been installed and the superuser prompt is displayed.

To Configure the Domain

To complete this procedure, you must know the hardware configuration of the domain so that you know which two interface ports to use for each disk array.

  1. Use apdb(1M) to create all of the AP databases.


    # apdb -c raw_disk_slice -f

  2. Create all of the AP metanetworks.

    1. Use apnet(1M) with the -c, -p, and -a options to create the network pathgroups.


      # apnet -c -p network_interface -a network_interface

      You can verify the results of the apnet(1M) command by using the apconfig(1M) command with the -N and -u options.

    2. Use apdb(1M) to commit to using the network pathgroups.


      # apdb -C

      You can verify the results of the apdb(1M) command by using the apconfig(1M) command with the -N option.

  3. Create an /etc/hostname.metanetwork_interface_name file for any metanetworks that you want to configure when the domain is booted.

  4. Create the configuration file for the primary network interface.

    1. Use cat(1M) to verify the name of the primary network.

      You should view the contents of the /etc/nodename and /etc/hostname.interface_name files to verify that the hostname is the same. In the following example, hmb represents the hostname.


      # cat /etc/nodename
hmb
# cat /etc/hostname.network_interface_name
hmb
#

    2. Use cat(1M) to create the new hostname.metanetwork_interface_name file to configure the network when you reboot the domain.


      # cat > /etc/hostname.metanetwork_interface_name
hmb
^D
# cat /etc/hostname.metanetwork_interface_name
hmb

    3. Remove the configuration files for the physical interfaces that are components of metanetworks.


      # rm -f /etc/hostname.primary_interface_name \/etc/hostname.alternate_interface_name

  5. Create the AP metadisks.

    To complete this step, you must know the hardware configuration of the domain so that you know which two ports to use for each disk array.

    1. Use apinst(1M) to display all of the ports and their disk-device nodes.

    2. Use apdisk(1M) with the -c, -p, and -a options to create an uncommitted disk pathgroup.


      # apdisk -c -p port_name0 -a port_name1

      In this example, -c causes the pathgroup to be created, -p designates the primary path, and -a designates the alternate path. You can verify the results of the apdisk(1M) command by using the apconfig(1M) command.

    3. Use apdb(1M) with the -C option to commit the uncommitted database entries.

      You can verify the results of the apdb(1M) command by using the apconfig(1M) command with the -S option.

    4. Use drvconfig(1M) to build the devices directories.


      # drvconfig -i ap_dmd

      You can verify the results of the drvconfig(1M) command by using the ls(1) command with /devices/psuedo/ap_dmd* as the option to the ls(1) command.

    5. Use apconfig(1M) with the -R option to create symbolic links from the devices directories, /dev/ap/dsk and /dev/ap/rdsk, to the special, metadisk file in /devices/pseudo.

      You can verify the results of the apconfig(1M) command by using the ls(1) command with -l /dev/ap/dsk as its options to view the symbolic links.

  6. If you are placing the boot disk under AP control, use apboot(1M) to define the new AP boot device.


    # apboot metadisk_name

    The apboot(1M) command modifies the /etc/vfstab file and the /etc/system file. The metadisk_name must be in the form: mcxtxdx.

  7. If applicable, configure references to AP metadisks for any other file systems or disk devices that were not configured in the above steps.

  8. Reboot the domain to begin using the newly configured AP metadevices.

To Finish the Installation

  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. If necessary, set the OBP boot-device variable to the primary boot device path.