Sun Enterprise Server ™ Alternate
Pathing 2.3.1 Installation and
Release Notes
Sun Microsystems, Inc.
901 San Antonio Road
Palo Alto,CA 94303-4900
U.S.A. 650-960-1300
Part No. 806-4152-10
September 2000, Revision A
Send comments about this document to: docfeedback@sun.com
Copyright 2000Sun Microsystems,Inc., 901San AntonioRoad, PaloAlto, California 94303-4900U.S.A. Allrights reserved.
This product ordocument isprotected bycopyright and distributedunder licensesrestricting itsuse, copying,distribution, and decompilation.
No partof thisproduct ordocument maybe reproducedin anyform byany means withoutprior writtenauthorization ofSun and itslicensors,
if any.Third-party software,including fonttechnology,is copyrightedand licensedfrom Sunsuppliers.
Parts ofthe productmay bederived fromBerkeley BSDsystems, licensedfrom theUniversity of California.UNIX isa registeredtrademark in
the U.S.and othercountries, exclusivelylicensed throughX/Open Company, Ltd.For NetscapeCommunicator™, thefollowing notice applies:
(c) Copyright1995 NetscapeCommunications Corporation.All rightsreserved.
Sun, SunMicrosystems, theSun logo,AnswerBook2, docs.sun.com,and Solarisare trademarks,registered trademarks,or service marks of Sun
Microsystems,Inc. in theU.S. andother countries.All SPARC trademarksare usedunder licenseand aretrademarks or registered trademarks
of SPARCInternational, Inc.in the U.S.and othercountries. Productsbearing SPARC trademarksare basedupon anarchitecture developedby
Sun Microsystems, Inc.
The OPENLOOK andSun™ GraphicalUser Interfacewas developed bySun Microsystems,Inc. forits usersand licensees. Sun acknowledges
the pioneeringefforts ofXerox inresearchingand developing theconcept ofvisual orgraphical user interfaces for thecomputer industry.Sun
holds anon-exclusive licensefrom Xeroxto theXerox GraphicalUser Interface,which licensealso covers Sun’slicensees whoimplement OPEN
LOOK GUIsand otherwisecomply withSun’s writtenlicense agreements.
RESTRICTEDRIGHTS:Use, duplication,or disclosureby theU.S. Governmentis subject torestrictions ofFAR52.227-14(g)(2)(6/87) andFAR
52.227-19(6/87), orDFAR252.227-7015(b)(6/95) andDFAR227.7202-3(a).
DOCUMENTATIONIS PROVIDED “ASIS” ANDALL EXPRESSOR IMPLIEDCONDITIONS, REPRESENTATIONSAND WARRANTIES,
INCLUDING ANYIMPLIED WARRANTYOF MERCHANTABILITY,FITNESS FORA PARTICULARPURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED,EXCEPT TOTHE EXTENTTHATSUCH DISCLAIMERSARE HELD TOBE LEGALLYINVALID.
Copyright 2000Sun Microsystems,Inc., 901San AntonioRoad, PaloAlto, Californie 94303Etats-Unis. Tous droits réservés.
Ce produitou documentest protégépar uncopyright etdistribué avecdes licences quien restreignentl’utilisation, lacopie, ladistribution, etla
décompilation. Aucunepartie dece produitou documentne peutêtre reproduitesous aucuneforme, parquelque moyen quece soit,sans
l’autorisation préalableet écritede Sunet deses bailleurs delicence, s’ily ena. Lelogiciel détenu pardes tiers,et quicomprend latechnologie
relativeaux polices decaractères, estprotégé parun copyrightet licenciépar desfournisseurs de Sun.
Des partiesde ceproduit pourrontêtre dérivéesdes systèmesBerkeley BSDlicenciés parl’Université de Californie.UNIX estune marque
déposée auxEtats-Unis etdans d’autrespays etlicenciée exclusivementpar X/Open Company,Ltd. Lanotice suivante est applicable à
Netscape Communicator™:(c) Copyright1995 NetscapeCommunications Corporation.Tousdroits réservés.
Sun, SunMicrosystems, lelogo Sun,AnswerBook2, docs.sun.com,et Solarissont des marquesde fabriqueou desmarques déposées,ou
marquesde service, deSun Microsystems,Inc. auxEtats-Unis etdans d’autrespays. Toutes lesmarques SPARCsont utilisées souslicence et
sont desmarques defabrique oudes marquesdéposées deSPARCInternational, Inc.aux Etats-Unis etdans d’autrespays. Lesproduits portant
les marques SPARC sontbasés surune architecturedéveloppée parSun Microsystems,Inc.
L’interfaced’utilisation graphiqueOPEN LOOKet Sun™a été développéepar SunMicrosystems, Inc.pour sesutilisateurs et licenciés. Sun
reconnaîtles effortsde pionniers deXerox pourla rechercheet ledéveloppement duconcept desinterfaces d’utilisation visuelle ou graphique
pour l’industriede l’informatique.Sun détientune licencenon exclusive deXerox surl’interface d’utilisationgraphique Xerox,cette licence
couvrant égalementles licenciésde Sunqui mettenten place l’interfaced’utilisation graphiqueOPEN LOOKet qui en outre seconforment aux
licences écritesde Sun.
CETTE PUBLICATIONEST FOURNIE "ENL’ETAT"ET AUCUNEGARANTIE, EXPRESSEOU IMPLICITE,N’EST ACCORDEE, YCOMPRIS
DES GARANTIESCONCERNANT LAVALEURMARCHANDE, L’APTITUDE DELA PUBLICATION AREPONDRE AUNE UTILISATION
PARTICULIERE, OULE FAIT QU’ELLENE SOITPASCONTREFAISANTEDE PRODUITDE TIERS. CEDENI DEGARANTIE NE
S’APPLIQUERAIT PAS,DANS LAMESURE OU ILSERAIT TENUJURIDIQUEMENT NULET NONAVENU.
Please
Recycle
Sun Enterprise10000 SSPAttributions:
This software iscopyrighted bythe Regents ofthe Universityof California, SunMicrosystems, Inc.,and otherparties. Thefollowing terms
apply toall filesassociated withthe softwareunless explicitly disclaimedin individualfiles.
The authorshereby grantpermission touse, copy,modify,distribute, and licensethis softwareand itsdocumentation forany purpose,
provided thatexisting copyrightnotices areretained inall copiesand that this notice isincluded verbatimin anydistributions. No written
agreement, license,or royaltyfee isrequired forany ofthe authorizeduses. Modifications tothis softwaremay becopyrighted bytheir authors
and neednot followthe licensingterms describedhere, providedthat the newterms areclearly indicatedon thefirst page ofeach filewhere
they apply.
Contents
1. Alternate Pathing 2.3.1 on the Sun Enterprise servers 1
Preparing to Install or Upgrade 1
▼ To Install or Upgrade From the Web 2
▼ To Install or Upgrade From a CD-ROM 2
▼ To Mount a CD-ROM over NFS™ 3
Performing an Initial Installation of AP 5
ssd Patch 6
▼ To Install AP 2.3.1 Using Web Start 7
▼ To Manually Install AP 2.3.1 9
▼ To Configure AP 10
Installing the AP 2.3.1 AnswerBook2 Collection 16
AP 2.3.1 AnswerBook2 Collection 16
▼ To Install the AP 2.3.1 AnswerBook2 Collection 16
Before Performing an Upgrade of AP 17
Backing Up Your Server 18
Uncommitted AP Database Entries 19
Checking Other Software Documentation 19
Simultaneously Upgrading AP and Solaris Software 19
AP Database Partitions 19
v
Root Disk Partitions 20
ssd Patch 20
Performing an Upgrade of AP 21
▼ To Upgrade to AP 2.3.1 21
2. AP 2.3.1 on Sun Enterprise Servers 27
AP 2.3.1 on Sun Enterprise Servers 27
Installation Issues 27
General Issues 29
Supported Devices 29
SunFDDI and Gigabit Ethernet Devices 30
Sun StorEdge A3000 31
Sun StorEdge A5000 31
Sun StorEdge A7000 31
Sun StorEdge T3 31
Software Compatibility 31
Dynamic Reconfiguration (DR) Issues 32
Boot Disk Issues 32
IPMP Issues 32
Sun Fibre Channel Port Driver (usoc/fp) Issues 32
AP Documentation Locations 33
Known Bugs/RFEs 33
Fixed Bugs 33
Other Bugs 35
Fixed Other Bugs 35
vi Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
CHAPTER
1
Alternate Pathing 2.3.1 on the Sun Enterprise servers
This chapter contains initial installation and upgrade instructions for Alternate
Pathing (AP) 2.3.1. With the introduction of AP 2.3.1, both the initial install
instructions and the upgrade instructions now apply to the Sun Enterprise™ 3x00,
4x00, 5x00, 6x00 and 10000 servers.
Preparing to Install or Upgrade
The AP packages require approximately 2.7 megabytes of disk space on the server.
The following table lists the total size of the AP software by file system.
TABLE1-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 with at least 300 Kbytes be dedicated to
each database copy. For more detailed information on partitioning for the AP
databases, see Chapter 2, “Alternate Pathing Database” in the Alternate Pathing 2.3.1
User Guide.
1
The installation instructions in this section assume that your system is running the
Solaris 2.6, Solaris 7 or Solaris 8 operating environment. AP 2.3.1 will not run under
software releases earlier than Solaris 2.6 environment.
▼ To Install or Upgrade From the Web
1. Using your web browser, go to http://www.sun.com/servers/sw/
2. Click the Enterprise Alternate Pathing (AP) link.
3. Click the Click here to download link.
The file that is then downloaded is named ap_2_3_1_sparc.zip.
4. Log in as superuser.
5. Change directory to the location where you downloaded the software:
# cd /download_directory
6. Extract the downloaded file by typing:
# unzip -v ap2_3_1_sparc.zip
The AP 2.3.1 packages are located in /download_directory/ap_2_3_1_sparc/
Product and the install and upgrade scripts are located in
/download_directory/ap_2_3_1_sparc/Tools.
7. Proceed to “Performing an Initial Installation of AP” on page 5 or “Before
Performing an Upgrade of AP” on page 17.
▼ To Install or Upgrade From a CD-ROM
1. Insert the “Software Supplement for the Solaris 8 Operating Environment” CDROM into the CD-ROM drive.
Allow time for the volume manager to mount the CD-ROM.
2 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
Note – If your CD-ROM drive is not local to your system (for example, on a Sun
Enterprise 10000) and you are not familiar with remote installation using a CDROM, see “To Mount a CD-ROM over NFS™” on page 3 or refer to your Solaris
System Administration Guide.
The AP 2.3.1 packages are located in:
/cdrom/cdrom0/Alternate_Pathing_2.3.1/Product
The install and upgrade scripts are located in:
/cdrom/cdrom0/Alternate_Pathing_2.3.1/Tools
2. Become superuser and cd to the Product installation directory:
# cd /cdrom/cdrom0/Alternate_Pathing_2.3.1/Product
3. Proceed to “Performing an Initial Installation of AP” on page 5 or “Before
Performing an Upgrade of AP” on page 17.
▼ To Mount a CD-ROM over NFS™
1. Log in as superuser and verify that the volume manager is running on your machine:
# ps -ef | grep vold
2. If you see an entry containing /usr/sbin/vold, volume manager is running on your system.
■ If volume manager is running, skip to Step 3.
■ If volume manager is not running on your system, type:
# /etc/init.d/volmgt start
3. Check to see if NFS is running on your system:
# ps -ef | grep nfsd
Chapter 1 Alternate Pathing 2.3.1 on the Sun Enterprise servers 3
■ If you see an entry containing /usr/lib/nfs/nfsd then nfsd is running on
your system. Type:
# share -F nfs -o ro /cdrom/cdrom0/Alternate_Pathing_2.3.1
■ If nfsd is not running, type:
# /etc/init.d/nfs.server start
# share -F nfs -o ro /cdrom/cdrom0/Alternate_Pathing_2.3.1
4. Log in to target machine as superuser and cd to the source machine:
# cd /net/source_machine/cdrom/cdrom0/Alternate_Pathing_2.3.1
If you cannot change to that directory and you do not have automounter on your
network, create a mount point on the target machine and mount the Product
directory:
# mkdir /remote_products
# /usr/sbin/mount -F nfs -r source_machine:/cdrom/cdrom0/
Alternate_Pathing_2.3.1 /remote_products
# cd /remote_products
5. At this point you may proceed with the install, “Performing an Initial Installation
of AP” on page 5 or “Before Performing an Upgrade of AP” on page 17.
Once you have completed installation you can umount the CD-ROM using:
# umount source_machine/cdrom
4 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
Performing an Initial Installation of AP
The initial installation instructions in this section are for environments where AP is
not currently installed and configured. If any version of AP is currently installed and
configured, you can use the instructions in “Before Performing an Upgrade of AP”
on page 17 to install AP 2.3.1. That procedure uses scripts that save your current AP
configuration, and then restores that configuration after you install the AP 2.3.1
packages.
The installation instructions in this section assume that your system is running the
Solaris 2.6, Solaris 7 or Solaris 8 operating environment. AP 2.3.1 will not run under
software releases earlier than the Solaris 2.6 environment.
Note – AP 2.3.1 software installation is based on your operating environment. If, at
a later date, you upgrade your Solaris operating environment, you must re-install
AP 2.3.1 following the AP 2.3.1 upgrade procedure. See “Before Performing an
Upgrade of AP” on page 17. For information on performing a simultaneous
upgrade, see “Simultaneously Upgrading AP and Solaris Software” on page 19.
Chapter 1 Alternate Pathing 2.3.1 on the Sun Enterprise servers 5
ssd Patch
AP 2.3.1 requires an ssd(7D) patch. AP 2.3.1 installation checks for the presence of
this patch. If the patch is not present then, depending on your configuration, the
following message maybe displayed:
Alternate Pathing Subsystem Drivers
(sparc) 2.3.1,REV=2000.05.09.11.28
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
Determining patch requirements...
Verifying required patches are installed...
Required patches not installed: 109524-01
###
### Patch verification failed.
### Alternate Pathing 2.3.1 requires this package.
### You MUST apply the required patches before
### proceeding.
###
### PACKAGE INSTALLATION FAILED.
###
checkinstall script suspends
Installation of <SUNWapdv> was suspended (administration).
No changes were made to the system.
The required patches are as follows:
■ Patch 105356-15 for Solaris 2.6,
■ Patch 107458-09 for Solaris 7
■ Patch 109524-01 for Solaris 8
You can obtain these patches from SunSolve at: http://sunsolve.sun.com.
Note – For information on this patch, see Section “Fixed Other Bugs” on page 35
(Sun BugID 4295457).
You can use Web Start to install the AP 2.3.1 software and optionally the AP 2.3.1
AnswerBook2 collection or you can manually install the AP and AnswerBook
packages using pkgadd.
To manually install AP 2.3.1 proceed to “To Manually Install AP 2.3.1” on page 9. To
manually install the AP 2.3.1 AnswerBook see “To Install the AP 2.3.1 AnswerBook2
Collection” on page 16.
6 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
If you have a third party volume manager installed on your system, you must
deconfigure it, according to your vendor’s instructions, before installing AP 2.3.1.
Once you have finished deconfiguring or if you do not have a volume manager
installed, proceed to “To Install AP 2.3.1 Using Web Start” on page 7 for the Web
Start procedure or “To Manually Install AP 2.3.1” on page 9 for the manual
procedure.
▼ To Install AP 2.3.1 Using Web Start
You can use Web Start to perform a fresh install from CD-ROM or from files you
have downloaded from the Web.
1. Log in as superuser.
2. Set the DISPLAY environment variable.
For sh(1) or ksh(1), type:
# DISPLAY=hostname:0
# export DISPLAY
Where hostname is the host name of the machine used to graphically display Web
Start.
3. Change directory to the location of the AP 2.3.1 package:
■ If you downloaded software from the Web:
# cd /download_directory/ap_2_3_1_sparc/Product
■ If you are installing the upgrade from the CD-ROM:
# cd /cdrom/cdrom0/Alternate_Pathing_2.3.1/Product
4. Begin Web Start by typing:
# ./installer
5. Select Custom Install, then select the Alternate Pathing 2.3.1 software and
optionally the Alternate Pathing 2.3.1 AnswerBook2 product.
With custom installation, only the products that you select are installed.
Chapter 1 Alternate Pathing 2.3.1 on the Sun Enterprise servers 7
Note – You can install the packages in any order you wish but you must install
them all. Package installation depends on the ssd patch being present. See “ssd
Patch” on page 6 for more information
6. Verify that you have sufficient disk space to cover the requirements displayed on
the Ready to Install dialog.
7. Click the Install Now button.
Wait until the installation is complete and the Installation Summary dialog is
displayed.
Note – If your Sun Enterprise server is not configured to support a particular
feature or device that is supported by Alternate Pathing, simply adding AP to your
server will not enable it to use that feature or device.
8. Configure AP.
For an example of the steps you need to follow, see “To Configure AP” on page 10.
Also see the Alternate Pathing 2.3.1 User Guide.
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 3.
8 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
▼ To Manually Install AP 2.3.1
1. Log in as superuser.
2. Change directory to the location of the AP 2.3.1 package:
■ If you downloaded software from the Web:
# cd /download_directory/ap_2_3_1_sparc/Product
■ If you are installing the upgrade from the CD-ROM:
# cd /cdrom/cdrom0/Alternate_Pathing_2.3.1/Product
3. Install the AP 2.3.1 domain packages on the server:
# pkgadd -d . SUNWapdoc SUNWapdv SUNWapr SUNWapu
Note – You can install the packages in any order you wish but you must install
them all. Package installation depends on the ssd patch being present. See “ssd
Patch” on page 6 for more information
The software briefly displays copyright, trademark, and license information for each
package, then displays messages about pkgadd(1M) actions taken to install the
package, 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 at each successive prompt to continue.
When this portion of the installation is complete, the AP 2.3.1 packages have been
installed and the superuser prompt is displayed.
Chapter 1 Alternate Pathing 2.3.1 on the Sun Enterprise servers 9
Note – If your Sun Enterprise server is not configured to support a particular
feature or device that is supported by Alternate Pathing, simply adding AP to your
server will not enable it to use that feature or device.
4. Remove the Sun Computer Systems Supplement CD from the CD-ROM drive, if applicable:
# cd /
# eject cdrom
5. Configure AP.
For an example of the steps you need to follow, see “To Configure AP” on page 10.
Also see the Alternate Pathing 2.3.1 User Guide.
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 3.
▼ To Configure AP
1. Create three to five AP databases:
# apdb -c raw_disk_slice
Note – See the Alternate Pathing 2.3.1 User Guide for information on disk partitions
for the AP database.
2. Create the AP metadisks.
You must know the configuration of the host hardware so that you know which two
ports are connected to the same disk array. The following steps use sf ports. Your
ports may vary, depending on the configuration of the host.
10 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
a. Display all of the ports and their disk device nodes:
# apinst
sf:0
/dev/dsk/c1t0d0
/dev/dsk/c1t1d0
/dev/dsk/c1t2d0
/dev/dsk/c1t3d0
/dev/dsk/c1t4d0
/dev/dsk/c1t5d0
sf:1
/dev/dsk/c2t0d0
/dev/dsk/c2t1d0
/dev/dsk/c2t2d0
/dev/dsk/c2t3d0
/dev/dsk/c2t4d0
/dev/dsk/c2t5d0
b. Create an uncommitted disk pathgroup:
# apdisk -c -p sf:0 -a sf:1
# 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 apconfig(1M) as shown above.
c. Commit the database entries:
# apdb -C
As shown, you can verify the results of that command by using apconfig -S.
Chapter 1 Alternate Pathing 2.3.1 on the Sun Enterprise servers 11
d. 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.
e. 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 using umount and mount respectively.
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 – You must be a knowledgeable system administrator to edit /etc/
vfstab. If you do not configure your file systems properly in /etc/vfstab,itis
possible that you can lose data and/or leave the server unbootable.
12 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
3. Create AP metanetworks (for nonprimary networks).
Note – The following steps should be applied to all networks that you want to
alternately path except the primary network.
a. Create the network pathgroup:
# apnet -c -a network_interface -a network_interface
# apconfig -N -u
...
As shown, you can verify the results of the apnet(1M) command by using
apconfig(1M).
b. Commit the network pathgroup entries in the database.
# apdb -C
You can verify the results of the apdb(1M) command by using the
apconfig(1M) command with the -N option.
c. 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.
d. Create an /etc/hostname.metherx (for example,hostname.mether0) file for
any metanetworks that you want to configure when the server 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 3.
Chapter 1 Alternate Pathing 2.3.1 on the Sun Enterprise servers 13
4. Create the AP metanetwork for the primary network. a. View the contents of the /etc/nodename and /etc/hostname.xxxxx files (for
example, hostname.hme0) to verify that the interface name is the same.
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 3.
b. Create the primary network pathgroup:
# apnet -c -a network_interface1 -a network_interface2
where:
-c creates the new primary network pathgroup
-a designates the first alternate network path
-a designates the second alternate network path
c. Commit the network pathgroup entry in the database:
# apdb -C
# apconfig -N
As shown, you can verify the results of the apdb(1M) command by using
apconfig(1M).
d. Rename the /etc/hostname.xxxx file to /etc/hostname.metherx to
configure the network when you reboot the server.
For example:
# mv hostname.hme0 hostname.mether0
14 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
5. If you plan to use a volume manager, such as Solstice DiskSuite™ (SDS) or
VERITAS Volume Manager™ (VxVM) configure the volume manager according to
the vendor’s instructions.
Note – Make sure that your volume manager is supported under your version of
the Solaris operating environment (either version 2.6, version 7, or version 8).
■ SDS Issues
If you want to build your SDS volumes on top of AP, configure your volumes
using AP metadisk paths rather than physical paths. SDS recognizes and properly
installs on existing AP metadevices with no special action required.
■ VxVM Issues
If you want to build your VxVM volumes on top of AP, configure your volumes
using AP metadisk paths rather than physical paths. VxVM recognizes and
properly installs on existing AP metadevices with no special action required.
VxVM can encapsulate both nonboot disks and boot disks that are configured as
AP metadevices. VxVM can encapsulate AP databases without any impact on AP.
Note, however, that the standard VxVM requirements for encapsulation apply:
■ There must be an s2 slice that represents the entire disk.
■ There must be two free partitions. The partition requirement may necessitate
giving up an AP database, which is often placed in slice s4.
■ There must be a "small amount" of free disk space at the beginning or end of
the disk.
Software installation of VxDMP and AP are mutually exclusive. You can only
install one or the other. VxDMP does not work with DR.
6. Reboot the server (if necessary).
If you just rebooted the server after configuring a volume manager, this step is
unnecessary.
Chapter 1 Alternate Pathing 2.3.1 on the Sun Enterprise servers 15
Installing the AP 2.3.1 AnswerBook2 Collection
This section explains how to manually install the AP 2.3.1 AnswerBook2 document
collection using the standard installation utility, pkgadd.
AP 2.3.1 AnswerBook2 Collection
Before you can install the AP 2.3.1 AnswerBook2 document collection, you must
have the AnswerBook2 server software installed. For instructions on installing the
AnswerBook2 server software, see “Installing and Administering an AnswerBook2
Server” in the AnswerBook2 Help Collection on docs.sun.com. The server
software can be obtained from the following sources:
■ The Documentation CD for Solaris 7 and Solaris 8 environments
■ The Web (http://www.sun.com/software/ab2/index.html)
▼ To Install the AP 2.3.1 AnswerBook2 Collection
1. Log in as superuser on the machine where the AP 2.3.1 AnswerBook2 collection is to be installed.
2. If you have a previous version of the SUNWabap package installed, remove it
using the pkgrm command:
# pkgrm SUNWabap
3. Change directory to the location of the AP 2.3.1 AnswerBook package:
■ If you downloaded software from the Web:
# cd /download_directory/ap_2_3_1_sparc/Product
■ If you are installing the upgrade from the CD-ROM:
# cd /cdrom/cdrom0/Alternate_Pathing_2.3.1/Product
16 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
4. Add the SUNWabap package by typing:
# pkgadd -d . SUNWabap
5. When you are requested to select an installation option, type
2 (heavy
installation):
Select an installation option: 2
6. When you are asked to specify the parent path for the AnswerBook2 collection,
type the path to the directory in which you want to put the AP 2.3.1 AnswerBook2.
It is suggested that you install the AP AnswerBook2 Collection in /opt.
Specify the parent path of this AnswerBook2 Collection directory: /opt
7. Type y at the following prompt:
This package contains scripts which will be executed with super-user
permission during the process of installing this package.
Do you want to continue with the installation of <SUNWabap> [y,n,?] y
A message indicates that the SUNWabap package was successfully installed.
For instructions on launching the AnswerBook2 viewer and viewing document
collections, see “Viewing Online Documentation Using the AnswerBook2 System” in
the AnswerBook2 Help Collection on docs.sun.com.
Before Performing an Upgrade of AP
This section provides information and recommendations concerning an upgrade to
AP 2.3.1 on the Sun Enterprise servers.
AP 2.0, 2.0.1, 2.1 and 2.2 are not supported under the Solaris 8 operating
environment.
The upgrade process involves:
■ Saving your current configuration
■ Deconfiguring AP
Chapter 1 Alternate Pathing 2.3.1 on the Sun Enterprise servers 17
■ Removing the earlier version of AP
■ Installing a set of core AP packages
■ Restoring your AP configuration
Scripts are provided to simplify this process in /download_directory/
ap_2_3_1_sparc/Tools from the web or on CD-ROM in /cdrom/cdrom0/
Alternate_Pathing_2.3.1/Tools.
Note – If you are upgrading to AP 2.3.1 on all Sun Enterprise 10000 domains, then
you can safely remove the SUNWapssp package software from the SSP workstation
using pkgrm. If, however, any domain will remain at an earlier version of AP, then
you must not remove the AP software on the SSP workstation. In either case, leaving
AP software on SSP workstations will have no effect on AP 2.3.1.
Installation of the packages requires approximately 2.7 megabytes of disk space. The
following table lists the total size of the AP software by file system.
TABLE1-2 AP Software File System Sizes
File System Size
/usr 317 Kbytes
/ 1.3 Mbytes
/etc 13 Kbytes
/kernel 1528 Kbytes
/sbin 1481 Kbytes
Note – When partitioning the hard drive during the Solaris software installation,
you must dedicate an entire disk partition with at least 300 Kbytes to each database
copy. For more detailed information on partitioning for the AP databases, see
Chapter 2, “Alternate Pathing Database” in the Alternate Pathing 2.3.1 User Guide.
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.
18 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
Note – If you wish to add or remove any hardware included in an AP path group,
do so either before you begin the upgrade process or after you have completed it. In
general, avoid changing your hardware in ways that result in controller
renumbering.
Uncommitted AP Database Entries
Before you run ap_upgrade_begin, 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 continue to exist after the upgrade.
Checking Other Software Documentation
Check the documentation of other software you are running, such as 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.
Simultaneously Upgrading AP and Solaris Software
The AP upgrade procedures in this section use two scripts, ap_upgrade_begin and
ap_upgrade_finish. The first script saves your current AP configuration. The
second script restores that exact configuration after you install the AP 2.3.1
packages. It is possible that you will upgrade the Solaris software at the same time
you upgrade to AP 2.3.1, since AP 2.3.1 supports Solaris 2.6, Solaris 7, and Solaris 8.
Because the AP configuration is restored exactly as it was before you upgraded the
Solaris operating environment, you need to be aware of the issues described in the
following sections.
AP Database Partitions
The AP upgrade scripts attempt to recreate the AP databases in the same partitions
that they occupied before the upgrade of the Solaris operating environment. Note,
however, that Solaris 7 and Solaris 8 require more disk space than earlier versions of
Chapter 1 Alternate Pathing 2.3.1 on the Sun Enterprise servers 19
the Solaris operating environment. Because of this, you can choose to modify the
boot disk partitioning scheme during suninstall.Donot modify the AP database
partitions. If you are upgrading from Solaris 7 to Solaris 8 operating environment
this will not be an issue. If, however, you are upgrading from an earlier version of
Solaris and you place file systems in all partitions that were previously used for AP
databases, ap_upgrade_finish is not able to recreate any databases and the
upgrade process fails.
Caution – If you place a file system in any partition that was previously used for an
AP database, and if for some reason that file system is not mounted at the time you
run ap_upgrade_finish, that file system is overwritten by a copy of the AP
database.
Root Disk Partitions
The AP upgrade facility assumes that the partitioning of the root disk (the disk
containing the / (root) partition) is not modified during the upgrade. Solaris 7 and
Solaris 8 software require more disk space than earlier versions. One way to acquire
the additional space is to repartition the original disk or to split the root disk into
two disks using standard commands prior to the Solaris upgrade. If you need to
repartition the root disk, do so before performing the AP 2.3.1 upgrade procedure.
If there is insufficient space when you run suninstall, you have the option to
modify the disk partitioning layout to acquire more space. However, during
suninstall, you must not relocate the / (root) or /usr partitions to another disk
as this will cause the AP upgrade script to fail.
ssd Patch
AP 2.3.1 requires an ssd(7D) patch. AP 2.3.1 installation checks for the presence of
this patch.
The required patches are as follows:
■ Patch 105356-15 for Solaris 2.6,
■ Patch 107458-09 for Solaris 7
■ Patch 109524-01 for Solaris 8
You can obtain these patches from SunSolve at: http://sunsolve.sun.com.
20 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
Performing an Upgrade of AP
The upgrade installation instructions in this section are for environments where AP
is currently installed and configured.
Note – If your Sun Enterprise server is not configured to support a particular
feature or device that is supported by Alternate Pathing, simply adding AP to your
server will not enable it to use that feature or device.
The installation instructions in this section assume that your system is running the
Solaris 2.6, Solaris 7 or Solaris 8 operating environment. AP 2.3.1 will not run under
software releases earlier than Solaris 2.6 environment.
Note – AP 2.3.1 software installation is based on your operating environment. If, at
a later date, you upgrade your Solaris operating environment, you must re-install
AP 2.3.1 following this AP 2.3.1 upgrade procedure. See “Before Performing an
Upgrade of AP” on page 17. For information on simultaneous upgrade, see
“Simultaneously Upgrading AP and Solaris Software” on page 19.
▼ To Upgrade to AP 2.3.1
1. If necessary, log in as superuser and commit any uncommitted entries in the AP database:
# apdb -C
2. Terminate any processes that directly or indirectly access AP metadevices.
If you have a third party volume manager installed on your system, deconfigure it
now using the documentation provided by the specific vendor.
With regard to AP, no additional steps need to be taken to do this other than those
recommended by the manufacturer to deconfigure the volume manager.
Chapter 1 Alternate Pathing 2.3.1 on the Sun Enterprise servers 21
Caution – Once the volume manager has been deconfigured, if you are instructed
to install the new OS, stop at that point and remove your previous version of AP. Do
not install Solaris 8 software at this time.
You do not need to be concerned if your mounted ufs file systems or TCP/IP
networks are using AP metadevices.
The ap_upgrade_begin script, which you will run later in this procedure, and the
subsequent reboot will cause the ufs file systems and any swap devices
configured in /etc/vfstab to use physical paths rather than AP metadevices.
Likewise, ap_upgrade_begin will also take care of renaming any TCP/IP network
interfaces (/etc/hostname.xxxx) that may be using AP metadevices.
Note – This is true for any ufs file system configured in vfstab or any network
configured with /etc/hostname.xxxx files.
3. Remove the current AP configuration. a. Log in to the server as superuser and run the following script to deconfigure AP
(and save the AP configuration so that it can be restored later):
# /path/Alternate_Pathing_2.3.1/Tools/ap_upgrade_begin
...
ap_upgrade_begin complete. (State saved in /var/tmp/apstate.) Now
you can safely remove the old AP packages, upgrade Solaris if
necessary, and install new AP packages. Run the ap_upgrade_finish
script when you’re done to restore the AP configuration. Please
read the upgrade directions in the Sun Enterprise Server Alternate
Pathing 2.3 Installation and Release Notes for specific details.
This script saves the current AP configuration information in the file
/var/tmp/apstate. you may examine the /var/tmp/apstate file if you wish,
but do not modify or remove it. Doing so can compromise the upgrade
procedure.
b. Remove the packages SUNWapdoc, SUNWapr, SUNWapu, SUNWabap and
SUNWapdv (if applicable) by using the pkgrm(1M) command.
c. If you are not upgrading your Solaris operating environment, reboot before
proceeding to Step 6.
4. Upgrade the Solaris operating environment (if applicable) now.
22 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
Note – You must upgrade the Solaris operating environment if you are running a
version prior to Solaris 2.6.
Caution – Make sure you upgrade the correct slice. If you were previously using a
volume manager to mirror the boot disk, and if you were also using AP to
alternately path each boot disk mirror, then there are four physical paths that were
previously potential paths to the boot disk (two alternate paths for each boot disk
mirror). Now that both AP and the volume manager have been deconfigured,
examine /etc/vfstab to determine the physical path that corresponds to the root
(/) file system. When you run suninstall, specify that path as the disk to upgrade.
Later, when you restore your volume manager, be sure to designate that disk as the
primary mirror. See your volume manager documentation for information on
determining which physical slice is used when booting.
Note – When partitioning the hard drive during the Solaris software installation,
you must dedicate an entire disk partition that has at least 300 Kbytes to each
database copy. For more detailed information on partitioning for the AP databases,
see Chapter 2, “Alternate Pathing Database” in the Alternate Pathing 2.3.1 User Guide.
See “Upgrading a System” in Solaris 8 (SPARC Platform Edition) Installation Library.
Note that you must choose the upgrade option to perform an upgrade of the Solaris
operating environment.
Chapter 1 Alternate Pathing 2.3.1 on the Sun Enterprise servers 23
5. When the Solaris installation process is completely finished, install the correct ssd patch.
Note – If you have not upgraded the Solaris operating environment or you did not
reboot as part of the upgrade or Step 3, do so now.
AP 2.3.1 installation checks for the presence of an ssd patch. If the patch is not
present then, depending on your configuration, the following message maybe
displayed:
Alternate Pathing Subsystem Drivers
(sparc) 2.3.1,REV=2000.05.09.11.28
Copyright 2000 Sun Microsystems, Inc. All rights reserved.
## Executing checkinstall script.
Determining patch requirements...
Verifying required patches are installed...
Required patches not installed: 109524-01
###
### Patch verification failed.
### Alternate Pathing 2.3.1 requires this package.
### You MUST apply the required patches before
### proceeding.
###
### PACKAGE INSTALLATION FAILED.
###
checkinstall script suspends
Installation of <SUNWapdv> was suspended (administration).
No changes were made to the system.
See Section “ssd Patch” on page 20 for the required patches if you have not already
done so.
Note – For information on this patch, see Section “Fixed Other Bugs” on page 35
(Sun BugID 4295457).
6. Upgrade to AP 2.3.1. a. Log in as superuser and type:
■ If you downloaded software from the web:
# cd /download_directory/ap_2_3_1_sparc/Tools
24 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
■ If you are installing the upgrade from the CD-ROM:
# cd /cdrom/cdrom0/Alternate_Pathing_2.3.1/Tools
b. Install the required AP 2.3.1 packages:
# pkgadd -d . SUNWapdoc SUNWapdv SUNWapr SUNWapu
Note – You can install the packages in any order you wish but you must install
them all. Package installation depends on the ssd(7D) patch being present. See
Section “ssd Patch” on page 20 for more information.
c. Run the following script to restore the original AP configuration:
Note – Be sure to read “Simultaneously Upgrading AP and Solaris Software” on
page 19 before performing the following command.
# /path/Alternate_Pathing_2.3.1.1/Tools/ap_upgrade_finish
...
ap_upgrade_finish complete. (State saved in /var/tmp/apstate.) Now
you can upgrade and configure any volume managers or other software
to use AP metadevices. Please read the upgrade directions in the
Sun Enterprise Server Alternate Pathing 2.3 Installation and
Release Notes for specific details.
d. Reboot.
7. If you have a third party volume manager, install and configure it according to
manufacturer’s instructions now.
Note – If your boot disk is mirrored, make sure you specify the upgraded disk as
the primary mirror.
Upgrade is now complete.
Chapter 1 Alternate Pathing 2.3.1 on the Sun Enterprise servers 25
26 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
CHAPTER
2
AP 2.3.1 on Sun Enterprise Servers
AP 2.3.1 on Sun Enterprise Servers
This section contains the release notes for Alternate Pathing (AP) 2.3.1 on Sun
Enterprise 3x00, 4x00, 5x00, 6x00 and 10000 servers.
AP enables you to define and control alternate physical paths to peripheral devices,
adding increased availability and a level of fault recovery to your server. If a
physical path to a device becomes unavailable, an alternate path can be used. For
more information, see the Sun Enterprise Server AP 2.3.1 User Guide in the Sun
Alternate Pathing 2.3.1 Collection AnswerBook2™.
Installation Issues
If you are upgrading from Solaris 2.6 or Solaris 7 software to Solaris 8 software and
have AP 2.1 or AP 2.2 on your system, you must upgrade to AP 2.3 or AP 2.3.1.
Because most systems have a volume manager installed we have included references
to them.
Note – AP 2.3.1 installation is Solaris operating environment specific. If you have
already installed AP 2.3.1 on your system and choose to upgrade your operating
system at a later date, you must follow the upgrade procedure to remove the AP
2.3.1 software using pkgrm and re-install AP 2.3.1.
This section contains an overview of the entire upgrade process, which requires you
to use several sections from different publications. You should ensure that you have
the following publications before you start the upgrade:
27
■ Sun Enterprise Server Alternate Pathing 2.3.1 User Guide (available in the
AnswerBook2 format in the SUNWabap package)
■ Your Volume Manager User Guide
■ Your Volume Manager Installation and Product Notes
Note – Before attempting an upgrade, verify that your volume manager supports
the Solaris 8 software.
Caution – You must follow the sequence given here to successfully complete the
upgrade.
In general, you will perform the following tasks:
■ Deconfigure your volume manager
■ Remove the previous version of AP.
■ Upgrade to the Solaris 8 operating environment.
■ Install AP 2.3.1.
■ Install and reconfigure your volume manager
Specifically, you must perform the following tasks:
1. Read “Performing an Upgrade of AP” on page 21.
2. Commit any uncommitted AP metadevices (see Step 1 in “To Upgrade to AP
2.3.1” on page 21).
3. Deconfigure your volume manager using the documentation provided by the specific vendor.
Note – With regard to AP, no additional steps need to be taken to do this other than
those recommended by the manufacturer to deconfigure the volume manager.
Caution – When the volume manager has been deconfigured and you are
instructed to install the new OS, stop at that point and remove your previous version
of AP. Do not install Solaris 8 software at this time.
4. Remove the current AP configuration using “Remove the current AP
configuration.” on page 22.
5. Upgrade to Solaris 8 using “Upgrade the Solaris operating environment (if
applicable) now.” on page 22.
6. Upgrade to AP 2.3 using “Upgrade to AP 2.3.1.” on page 24.
28 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
7. Install your volume manager according to your manufacturer’s instructions.
General Issues
This section contains general issues that involve AP on Sun Enterprise servers. Read
this section before you attempt to install or configure AP.
Note – If you are upgrading to AP 2.3.1 on all Sun Enterprise 10000 domains then
you can safely remove the SUNWapssp package software from the SSP workstation
using pkgrm. If, however, any domain will remain at an earlier version of AP, then
you must not remove the AP software on the SSP workstation. In either case, leaving
AP software on SSP workstations will have no effect on AP 2.3.1.
Supported Devices
The following devices are supported by the AP software on Sun Enterprise servers:
■ SPARCstorage™ Arrays recognized by AP using the pln(soc) controllers
■ Sun™ StorEdge™ A5000 recognized by AP using sf(socal) or fp(usoc)
controllers
■ Sun™ StorEdge™ T3 recognized by AP using sf(socal) or fp(usoc) controllers
■ Sun Enterprise™ E3500 internal drives recognized by using sf(socal)or
fp(usoc) controllers
■ SunFastEthernet™ 2.0 (hme)
■ SunFDDI/S™ 6.0 (nf) SAS (Single-Attach Station) and DAS (Dual-Attach Station)
■ SCSI-2/Buffered Ethernet FSBE/S and DSBE/S (le)
■ Quad Ethernet (qe)
■ Sun™ Quad FastEthernet™ (qfe)
■ Sun Gigabit Ethernet 2.0 (ge)
■ QLogic 2202 controller card
The following table lists which devices are supported in which releases:
Chapter 2 AP 2.3.1 on Sun Enterprise Servers 29
TABLE2-1 AP Support Matrix
AP
Version
Solaris
Release NICs
Disk
Controllers
Storage
Products
ge hme le nf bf hi qe qfe vge
2.0 2.5.1 X XXXXX X pln/soc SSA
2.0.1 2.5.1 X XXXXX X pln/soc,
sf/socal
2.1 2.6 X X X X X X X pln/soc,
sf/soc
2.2 7 X X X X X X pln/soc,
sf/socal,
fp/usoc*
2.6, X X X X X X X pln/soc,
sf/socal
7, X X X X X X pln/soc,
2.3
8 X X X X X pln/soc,
2.3.1 8 X X X X X pln/soc,
* - fp/usoc support for AP 2.2 requires a patch for Solaris 7 (included in Solaris 7 11/99) and for AP 2.2.
Refer to www.sunsolve.com for more information
† - fp/usoc support requires Solaris 7 11/99 or Solaris 8.
sf/socal,
fp/usoc†
sf/socal,
fp/usoc
sf/socal,
fp/usoc
SSA,
A5000
SSA,
A5000
SSA,
A5000
SSA,
A5000,
SSA,
A5000,
T3§
SSA,
A5000,
T3§
SSA,
A5000,
T3
§ - AP 2.3 has not been optimized for T3 support.
SunFDDI and Gigabit Ethernet Devices
AP 2.3.1 validation tests were performed on SunFDDI/S (revision 7.0) and Gigabit
Ethernet (revision 2.0). If you install either of these devices, you must use the
revision level that was tested, unless a higher revision level exists. In addition, you
must install all of the available patches for these devices. Refer to
http://www.sunsolve.sun.com for more information about the patches.
30 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
Sun StorEdge A3000
The Sun StorEdge A3000 supports failover capabilities that are similar to those
provided by AP 2.3.1. Because of this, AP 2.3.1 does not support the Sun StorEdge
A3000. See that product’s documentation for more information about its failover
support.
Sun StorEdge A5000
AP 2.3.1 supports the Sun StorEdge A5000 for this release.
Sun StorEdge A7000
AP 2.3.1 does not support the Sun StorEdge A7000 for this release.
Sun StorEdge T3
AP 2.3.1 supports the Sun StorEdge T3 in a path optimized AP configuration with
this release. Path optimization refers to the efficient distribution of I/O traffic for the
T3.
Software Compatibility
The following lists includes the possible combinations of AP and Solaris software
you can install on a Sun Enterprise server.
■ Solaris 8 with AP 2.3.1 and DR
■ Solaris 8 with AP 2.3 and DR
■ Solaris 7 with AP 2.3.1 and DR
■ Solaris 7 with AP 2.3 and DR
■ Solaris 7 with AP 2.2 and DR
■ Solaris 2.6 with AP 2.3.1 and DR
■ Solaris 2.6 with AP 2.3 and DR
■ Solaris 2.6 with AP 2.1 and DR
■ Solaris 2.5.1 with AP 2.0.1 and DR (Sun Enterprise 10000 server only)
■ Solaris 2.5.1 with AP 2.0 and DR (Sun Enterprise 10000 server only)
Chapter 2 AP 2.3.1 on Sun Enterprise Servers 31
Dynamic Reconfiguration (DR) Issues
The DR Attach operation can complete without the controller being immediately
accessible to AP. You must verify that the physical device is present before switching
to the new controller using apconfig.
A Sun Enterprise 10000 Server running the Solaris 2.6 operating environment
requires Patch 106284-02 for AP 2.3.1 to run correctly with the dr_daemon.
Boot Disk Issues
AP 2.3.1 provides support for only one alternately pathed boot disk plus a mirror
disk per domain.
In order to fix inconsistencies in boot recovery behavior device aliases for the boot
disk are not supported.
Boot recovery is architecture generic in AP 2.3.1. Boot recovery works on Sunfire as
well as Starfire platforms.
IPMP Issues
IPMP/AP path groups are not supported for this release.
Sun Fibre Channel Port Driver (usoc/fp) Issues
A SENA device which uses the usoc/fp drivers is considered a different physical
device than a SENA device which uses the socal/sf stack. SENA devices do not
support mixed configurations where usoc/fp and socal/sf drivers service a single
SENA device. Therefore, the two cannot be combined in an AP metadevice.
Revising the firmware on a physical SENA device using socal/sf drivers to use
usoc/fp drivers for your fibre-channel controllers is the same as replacing the
hardware with a different type of controller. (The converse is also true.) You must
deconfigure Alternate Pathing on such controllers before you revise the firmware. For
example:
# apdisk -d sf:0
# apdb -C
Revise the SENA firmware.
32 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
After you’ve performed the revision, recreate your pathgroups using the new device
names, for example:
# apdisk -c -pfp:0 -a fp:1
# apdb -C
Caution – If you change firmware without deconfiguring AP, file systems available
from the new alternately-pathed controllers may not be accessible. If those file
systems are required during boot, your system can become unbootable.
AP Documentation Locations
Documentation for AP 2.0 and 2.0.1 can be found in their respective collections
under Hardware -> Enterprise Servers at docs.sun.com.
AP 2.1 and 2.2, however are in the Hardware -> Solaris on Sun Hardware
Answerbook collection at docs.sun.com.
AP 2.3 and 2.3.1 are in their own collections under Hardware -> Enterprise Servers.
Known Bugs/RFEs
4361968 - panic while switching unplumbed metanetwork.
Fixed Bugs
This section contains the synopses and Sun BugID number of the more important
bugs that have been fixed since the AP 2.3 release (Solaris 8). This list does not
include all of the fixed bugs.
4265982 - (RFE) an immediate switch of path using AP after DR configure forces it
into a ‘T’ state.
4276330 - (RFE) AP handling for individual target failure, FC hubs/fabric, and daisy
chaining.
4297492 - (RFE) hang on e3500 with mirrored internal disk pull out with ap and sds.
4342963 - read/write errors during ctrl failover w/ purple partner group or 2x2
expansion.
Chapter 2 AP 2.3.1 on Sun Enterprise Servers 33
4347014 - Multiple ".probe" execution causes LUNs on unix host to fail with
ENODEV.
4347016 - ENXIO from T3 ONLINE Master immediately after .probe initiated ctlr
failure.
34 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
Other Bugs
This section contains the synopses and Sun BugID number of the more important
bugs that have been discovered regarding AP 2.3.1 and the Solaris 8 operating
system. This list does not include all bugs.
Fixed Other Bugs
4295457 - ssd: serial number should be obtained from the Unit Serial Number page.
AP depends on Sun Device ID functions; specifically ddi_devid_compare(). Any
device that AP supports must adequately interface with the Sun Device ID. This
leads to a direct dependency on the resolution of SUNBugID 4295457. Hence, there is
a dependency on three separate patches:
■ Patch 105356-15 for Solaris 2.6,
■ Patch 107458-09 for Solaris 7
■ Patch 109524-01 for Solaris 8
You can obtain these patches from SunSolve at:http://sunsolve.sun.com.
Chapter 2 AP 2.3.1 on Sun Enterprise Servers 35
36 Sun Enterprise Server Alternate Pathing 2.3.1 Installation Guide and Release Notes • September 2000
Loading...