test

Trusted Solaris 8 Installation and Configuration on the Sun Enterprise 10000

Chapter 7 Trusted Solaris Alternate Pathing 2.3 on an E10000 Domain

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

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

Installing Trusted Solaris AP

The Trusted Solaris AP 2.3 release includes a set of packages that are to be installed on the Sun Enterprise 10000 domain running Trusted Solaris software.

The following table lists the total size of the AP software by file system:

Table 7–1 AP Software Approximate File System Sizes

File System 

Size 

/usr

317 Kbytes 

/

1.3 Mbytes 

/etc

13 Kbytes 

/kernel

1528 Kbytes 

/sbin

1481 Kbytes 

AP requires that an entire disk partition that has at least 300 Kbytes be dedicated to each database copy. For more detailed information on partitioning for the AP database, see “Alternate Pathing Database” in Sun Enterprise Server Alternate Pathing 2.3 User Guide.

To Install Trusted Solaris AP 2.3

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

  1. On the main SSP, log in as user ssp. Assume the system administrator role, hereafter called the admin role.

  2. Use the Device Allocation Manager to allocate the CD-ROM drive, then mount the “Software Supplement for the Trusted Solaris 8 Operating Environment” CD with all privileges.

    You should perform all tasks in Setting up a CD-ROM:

    .

  3. Share /cdrom/admin-cdrom_0 by issuing the share(1M) command:


    $ share -F nfs -o ro,anon=0 /cdrom/admin-cdrom_0/trusted_sol_8_sup1

  4. Use the showmount(1M) command to confirm that the /cdrom/admin-cdrom_0/trusted_sol_8_sup1 file system is being shared: 

       ssp$ showmount -e
export list for bermuda:
/cdrom/admin-cdrom_0/trusted_sol_8_sup1 (everyone)

  5. Install Trusted Solaris AP on the domain.

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

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

    2. Mount the /cdrom/admin-cdrom_0 directory.


      $ /usr/sbin/mount ssp_hostname:/cdrom/admin-cdrom_0/trusted_sol_8_sup1 /mnt

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


      $ pkgadd -d /mnt/Alternate_Pathing_2.3/Product  \
SUNWapdoc SUNWapu SUNWapr SUNWapdv

      The AP 2.3 packages are located in /mnt/Alternate_Pathing_2.3/Product.

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

    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. y

  6. Unmount and remove the CD-ROM.

    1. Unmount the CD-ROM on the domain.


      $ cd /
$ umount /cdrom/admin-cdrom_0

    2. On the SSP, assume the admin role. At label admin_low, unshare /cdrom/admin-cdrom_0/trusted_sol_8_sup1:


      ssp$ cd /
ssp$ unshare /cdrom/admin-cdrom_0/trusted_sol_8_sup1

    3. Use the Device Allocation Manager to deallocate the CD-ROM drive. Remove the Trusted Solaris 8 Supplement CD.

  7. Configure Trusted Solaris AP.

    For an example of the steps you need to follow, see the next section. Also see the Sun Enterprise Server Alternate Pathing 2.3 User Guide.

To Configure a Trusted Solaris AP

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

  1. Assign the Host Alternate Pathing right to an administrative role.

    Follow the procedure To Enable the System Administrator to Install SSP 3.3 and AP 2.3. Use Step h as a guide.

  2. Create three to five AP databases.


    $ /sbin/apdb -c raw_disk_slice -f

  3. 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 using the apinst(1M) command. 

      $ 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 using the apdisk(1M) command.


      $ /sbin/apdisk -c -p pln0 -a pln1
$ /sbin/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(1M) command as shown above.

    3. Commit the database entries.


      $ /sbin/apdb -C

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

    4. Rebuild the devices directories.


      $ drvconfig -i ap_dmd
$ 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.


      $ /sbin/apconfig -R
$ ls -l /dev/ap/dsk

      As shown above, you can verify the results of the apconfig(1M) 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(1M) to define the new AP boot device.


      $ /sbin/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.

  4. 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.


      $ /sbin/apnet -c -p network_interface -a network_interface
$ /sbin/apconfig -N -u

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

    2. Commit the network pathgroup entries in the database.


      $ /sbin/apdb -C

      You can verify the results of the apdb(1M) 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.metherx (for example, hostname.mether0) file for any metanetworks that you want to configure when the domain is rebooted.

    Note –

    If you are using IPv6, your /etc/hostname files will have the name /etc/hostname6.xxx. While the content of the IPv6 files is different than IPv4, as far as AP installation is concerned, the /etc/hostname6.xxx files can be treated in exactly the same manner as the /etc/hostname.xxx files. For more information on IPv6, refer to System Administration Guide, Volume 2.

  5. Create the AP metanetwork for the primary network.

    1. View the contents of the /etc/nodename and /etc/hostname.xxx files (for example, hostname.hme0) to verify that the interface name is the same.

    2. Create the primary network pathgroup.


      ssp$ /sbin/apnet -c -p network_interface1 -a network_interface2

      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.


      $ /sbin/apdb -C
$ /sbin/apconfig -N

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

    4. Rename the /etc/hostname.xxx file to /etc/hostname.metherx to configure the network when you reboot the domain.

      For example, 


      $ mv hostname.hme0 hostname.mether0