test

Trusted Solaris 7 Installation and Configuration on the Sun Enterprise 10000

Chapter 5 Trusted Solaris Alternate Pathing 2.2 on the Sun Enterprise 10000 Server

This chapter contains install instructions for Trusted Solaris Alternate Pathing (AP) 2.2 on the Sun Enterprise 10000 server.

The Trusted Solaris version of AP 2.2 shipped on the Trusted Solaris 7 supplemental CD requires a Trusted Solaris 7 operating environment. The procedures given in this chapter assume that the SSP and the domains are running Trusted Solaris 7.

Installing Trusted Solaris AP

The Trusted Solaris AP 2.2 release includes one package that must be installed on the Trusted Solaris SSP and a set of core packages that must be installed on the Sun Enterprise 10000 domain running Trusted Solaris software.

The Trusted Solaris AP packages require approximately 2.7 megabytes of disk space on the domain and 37 kilobytes on the SSP. The following table lists the total size of the AP software by file system:

Table 5-1 AP Disk Space Requirements by File System

File System 

Size 

SSP: 

 

/opt

31 Kbytes 

Host: 

 

/usr

317 Kbytes 

/

1.3 Mbytes 

/etc

13 Kbytes 

/kernel

1528 Kbytes 

/sbin

1481 Kbytes 

 

 

To Install Trusted Solaris AP 2.2

The Trusted Solaris AP software must be installed on a Trusted Solaris 7 system.

  1. On the main SSP, log in as a user who can assume the root role , and assume it.

  2. In the root role, at label admin_low, use the Device Allocation Manager to allocate the CDROM drive, but do not mount it.

    Do not try to use the Volume Manager; it is disabled in the Trusted Solaris environment.

    1. Click the triangle above the Style Manager on the Front Panel to display the Trusted Desktop subpanel. Click Device Allocation.

    2. Double-click the CDROM device to move it to the Allocated Devices list.

    3. Write down the device name for the CDROM drive as indicated in the "Insert disk into" message in the Device Allocation window.

      For example, if the message reads: 

      Insert disk into /dev/dsk/c0t2d0s0.
      Make sure disk is labeled ADMIN_LOW [ADMIN_LOW].
      Press RETURN when cdrom_0 is ready, or ^C to cancel.
      then write down the device name, /dev/dsk/c0t2d0s0, before continuing.

    4. Insert the Trusted Solaris Supplemental CD into the CDROM drive and press the Return key.

    5. Answer "n" to the question: Do you want cdrom_0 mounted: (y/n)? n

      Note -

      This differs from the instructions in Trusted Solaris Installation and Configuration. Follow the instructions here; do not mount the CDROM.

  3. In the root role, at label admin_low, make sure that /cdrom/root exists. If not, create it. 


    ssp# mkdir -p /cdrom/root

  4. Mount the CDROM with all allowed and forced privileges.


    ssp# mount -F hsfs -o ro -S "allowed=all;forced=all" \ 
cdrom_device /cdrom/root

    For example, for the CDROM on device /dev/dsk/c0t2d0s0, type:


    ssp# mount -F hsfs -o ro -S "allowed=all;forced=all" \ 
/dev/dsk/c0t2d0s0  /cdrom/root

  5. Check that the mount succeeded with the df(1M) command:


    ssp# df -k grep | cdrom
/dev/dsk/c0t2d0s0  544100  544100 0 100%  /cdrom/root

  6. Share /cdrom/root by issuing the share(1M) command:


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

  7. Use the showmount(1M) command to confirm that the /cdrom/root filesystem is being shared:


    ssp# showmount -e
export list for bermuda:
/cdrom/root (everyone)

  8. Install the Trusted Solaris AP packages on the SSP (and spare SSP, if applicable)

    1. Change to the AP 2.2 product directory and execute the pkgadd(1M) command to add the SUNWapssp package onto the SSP.


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

    2. Start the ap_ssp_daemon. 


      ssp# init q

    3. If you have a spare SSP, perform the above steps on the spare SSP.

  9. Install Trusted Solaris AP on the domain.

    1. From the Trusted Solaris SSP's root role, rlogin(1) to the domain.

      You are now logged in to the domain in the root role.

    2. Create and mount the /cdrom directory.


      # mkdir /cdrom
# mount ssp_hostname:/cdrom/root /cdrom

    3. Install the AP 2.2 host packages on the domain.


      # pkgadd -d /cdrom/Product SUNWapdoc  \
SUNWapu SUNWapr SUNWapdv

  10. Unmount and remove the CDROM.

    1. Unmount the CDROM on the domain.


      # cd /
# umount /cdrom

    2. On the SSP, assume the root role. At label admin_low, unshare then unmount /cdrom/root:


      ssp# cd /
ssp# unshare /cdrom/root
ssp# umount /cdrom/root

    3. In the root role, at label admin_low, use the Device Allocation Manager to deallocate the CDROM drive and remove the Trusted Solaris Supplemental CD.

      Do not use the Volume Manager; it is disabled in the Trusted Solaris environment.

  11. Configure Trusted Solaris AP.

    For an example of the steps you need to follow, see "To Configure a Trusted Solaris AP". Also see the Sun Enterprise Server Alternate Pathing User's Guide.

To Configure a Trusted Solaris AP

All procedures are performed on the domain, in the role root at the label admin_low.

  1. Create three to five AP databases.


    ssp# apdb -c raw_disk_slice -f

  2. Create AP metadisks.

    You must know the configuration of the domain's hardware so that you know which two ports are connected to the same disk array. The following examples use pln ports. Your ports may vary, depending on the configuration of the domain.

    1. Display all of the ports and their disk device nodes. 

      # apinst
pln0
	/dev/dsk/c1t0d0
	/dev/dsk/c1t1d0
	/dev/dsk/c1t2d0
	/dev/dsk/c1t3d0
	/dev/dsk/c1t4d0
	/dev/dsk/c1t5d0
pln1
	/dev/dsk/c2t0d0
	/dev/dsk/c2t1d0
	/dev/dsk/c2t2d0
	/dev/dsk/c2t3d0
	/dev/dsk/c2t4d0
	/dev/dsk/c2t5d0

    2. Create an uncommitted disk pathgroup.


      ssp# apdisk -c -p pln0 -a pln1
ssp# apconfig -S -u

      where:

      -c causes the pathgroup to be created

      -p designates the primary path

      -a designates the alternate path.

      You can verify the results by using the apconfig command as shown above.

    3. Commit the database entries.


      # apdb -C

      You can verify the results of the above command by using apconfig -S.

    4. Rebuild the devices directories. 

      ssp# drvconfig -i ap_dmd
ssp# ls -l /devices/pseudo/ap_dmd*
...

      As shown above, you can verify the results of the drvconfig(1M) command by listing the contents of /devices/pseudo/ap_dmd*.

    5. Create symbolic links from the devices directory /devices/pseudo to the special metadisk files in /dev/ap/dsk and /dev/ap/rdsk. 

      ssp# apconfig -R
ssp# ls -l /dev/ap/dsk
...

      As shown above, you can verify the results of the apconfig command by listing the contents of /dev/ap/dsk to view the symbolic links.

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

      # apboot metadisk_name

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

    7. Modify any references that use a physical device node (that is, a path that begins with /dev/dsk or /dev/rdsk) to use the corresponding metadisk device node (that is, a path that begins with /dev/ap/dsk or /dev/ap/rdsk).

      If a partition is mounted under a physical path, unmount and remount it under the metadisk path.

      Examine /etc/vfstab for any physical devices that should be changed to AP metadevices. If necessary, edit /etc/vfstab to make the necessary modifications.

      Caution - Caution -

      You must be a knowledgeable system administrator to edit /etc/vfstab. If you do not configure your file systems properly in /etc/vfstab, it is possible that you will lose data the next time you boot the domain.

  3. Create AP metanetworks (for non-primary networks).

    Note -

    The following steps should be applied to all networks that you want to alternately path except the primary network.

    1. Create the network pathgroup. 

      ssp# apnet -c -p network_interface -a network_interface
ssp# apconfig -N -u
...

      As shown above, you can verify the results of the apnet command by using apconfig.

    2. Commit the network pathgroup entries in the database. 

      # apdb -C

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

    3. Remove all direct usage of both members of the network pathgroups.

      If the physical interface is currently plumbed, and it is not the interface that you will be using as you run commands to configure the metanetwork, you can unplumb the physical interface by using the ifconfig(1M) command.

    4. Create an /etc/hostname.mnetwork_interface_name file for any metanetworks that you want to configure when the domain is rebooted.

  4. Create the AP metanetwork for the primary network.

    1. View the contents of the /etc/nodename and /etc/hostname.interface_name files to verify that the interface name is the same.

    2. Create the primary network pathgroup. 

      ssp# apnet -c -p network_interface -a network_interface

      In this example, -c creates the new primary network pathgroup, -p designates the primary network path, and -a designates the alternate path.

    3. Commit the network pathgroup entry in the database. 

      ssp# apdb -C
ssp# apconfig -N

      As shown above, you can verify the results of the apdb command by using apconfig.

    4. Create the new /etc/hostname.minterface_name file to configure the network when you reboot the domain.

      For example, /etc/hostname.minterface_name might contain hmb.

    5. Remove the configuration files that correspond to the metanetwork interface. 

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

  5. Reboot the domain.