solaris san configuration and multi pa thing guide

8/6/2019 Solaris SAN Configuration and Multi Pa Thing Guide

1/104

Solaris SAN Confguration andMultipathing Guide

Sun Microsystems, Inc.4150 Network CircleSanta Clara, CA 95054U.S.A.

PartNo: 8201931November 2007


2/104

Copyright2007 SunMicrosystems, Inc. 4150 Network Circle, Santa Clara,CA 95054 U.S.A. Allrightsreserved.

SunMicrosystems, Inc. hasintellectual property rightsrelatingto technology embodied in theproduct that is describedin this document.In particular, andwithoutlimitation, these intellectualpropertyrights mayinclude oneor more U.S. patents or pending patentapplications in theU.S. andin other countries.

U.S. Government Rights Commercial sotware. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicableprovisionso theFARand itssupplements.

This distribution may include materials developed by thirdparties.Partso theproduct maybe derived rom Berkeley BSDsystems, licensed rom theUniversity o Caliornia. UNIXis a registered trademarkin theU.S. andothercountries, exclusivelylicensed through X/OpenCompany, Ltd.

Sun, SunMicrosystems, theSun logo, theSolaris logo, theJavaCofee Cuplogo,docs.sun.com, Java,StorEdge, StorageTek, OpenBoot, andSolaris aretrademarks orregistered trademarks o SunMicrosystems, Inc. in theU.S. andothercountries. AllSPARC trademarks areused under licenseand aretrademarks or registeredtrademarks o SPARCInternational,Inc. in theU.S. andothercountries. Products bearing SPARCtrademarks arebasedupon an architecturedeveloped by SunMicrosystems, Inc.

The OPENLOOKandSunTM GraphicalUser Interacewas developedby SunMicrosystems, Inc. orits users andlicensees. Sunacknowledges thepioneering efortso Xerox in researching anddeveloping theconcept o visualor graphicaluser interaces orthe computer industry.Sun holds a non-exclusive licenseromXeroxtotheXeroxGraphical UserInterace,whichlicense also coversSun'slicenseeswho implementOPEN LOOK GUIs andotherwise complywith Sun's written licenseagreements.

Products covered by andinormationcontained in this publication arecontrolled by U.S. ExportControl laws andmay be subjectto theexport or importlaws inother countries. Nuclear,missile,chemicalor biological weapons or nuclear maritime enduses or endusers,whether director indirect,are strictly prohibited. Exportor reexport to countriessubject to U.S. embargo or to entities identiedon U.S. exportexclusion lists,including, butnot limited to,the deniedpersons andspeciallydesignated nationals lists is strictly prohibited.

DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIEDCONDITIONS, REPRESENTATIONSAND WARRANTIES, INCLUDINGANYIMPLIEDWARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED,EXCEPT TOTHEEXTENTTHAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Copyright2007 SunMicrosystems, Inc. 4150 Network Circle, Santa Clara,CA 95054 U.S.A. Tous droitsrservs.

SunMicrosystems, Inc. dtient lesdroits de propritintellectuellerelatis la technologie incorpore dans le produit quiest dcritdans ce document.En particulier,et ce sans limitation, cesdroits de propritintellectuellepeuvent inclure un ou plusieursbrevets amricains ou desapplications de breveten attente auxEtats-Uniset dans d'autres pays.

Cette distribution peut comprendredes composants dveloppspar des tierces personnes.

Certainescomposants de ce produit peuvent tre drives du logiciel Berkeley BSD, licencispar l'Universitde Caliornie. UNIXest unemarque dpose auxEtats-Uniset dans d'autres pays; elle estlicencie exclusivementpar X/OpenCompany,Ltd.

Sun, SunMicrosystems, le logo Sun, le logo Solaris, le logo Java Cofee Cup, docs.sun.com,Java, StorEdge, StorageTek, OpenBoot, et Solaris sont desmarques deabrique ou desmarques dposes de SunMicrosystems, Inc. auxEtats-Uniset dans d'autres pays. Toutesles marques SPARCsont utilisessous licence et sont desmarques de abrique ou desmarques dposes de SPARC International, Inc. auxEtats-Uniset dans d'autres pays. Les produits portant lesmarques SPARC sont basssur une architecture dveloppepar Sun Microsystems, Inc.

L'interace d'utilisation graphiqueOPEN LOOK et Suna tdveloppe parSun Microsystems, Inc. pour ses utilisateurset licencis. Sunreconnat leseforts depionniersde Xerox pour la rechercheet le dveloppement du concept desinteraces d'utilisation visuelle ou graphiquepour l'industrie de l'inormatique.Sun dtientunelicence nonexclusive de Xerox surl'interaced'utilisation graphiqueXerox, cette licence couvrant galementles licencisde Sunqui mettent en place l'interaced'utilisation graphiqueOPEN LOOK et qui, en outre,se conorment auxlicencescrites de Sun.

Les produits quiont l'objet de cette publication et lesinormations qu'il contient sontrgispar la legislation amricaine en matire de contrle desexportations etpeuvent tre soumisau droit d'autres pays dans le domaine desexportations et importations. Les utilisationsnales, ou utilisateursnaux, pour desarmesnuclaires,des missiles, des armeschimiques ou biologiquesou pour le nuclaire maritime, directementou indirectement, sont strictementinterdites. Les exportations ourexportations vers despays sous embargo desEtats-Unis,ou vers desentits gurantsur leslistes d'exclusion d'exportation amricaines, y compris, mais de manirenonexclusive, la liste de personnesqui ontobjet d'un ordre de ne pasparticiper,d'uneaondirecte ou indirecte, auxexportations desproduitsou desservicesquisont rgispar la legislationamricaine en matire de contrle des exportations et la listede ressortissants spciquement designs, sont rigoureusement interdites.

LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS, DECLARATIONSET GARANTIES EXPRESSES OU TACITESSONT FORMELLEMENT EXCLUES, DANS LA MESUREAUTORISEE PAR LA LOIAPPLICABLE, Y COMPRISNOTAMMENTTOUTE GARANTIEIMPLICITERELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE A UNEUTILISATION PARTICULIEREOU A L'ABSENCE DE CONTREFACON.

071115@19028


3/104

Contents

Preace ...................................................................................................................................................11

1 ProductOverview ................................................................................................................................15

Sotware Features ................................................................................................................................ 16

Fibre Channel Sotware Features ............................................................................................... 16

SAS Sotware Features ................................................................................................................. 16

Multipathing Sotware Features ................................................................................................. 17

Supported Standards ........................................................................................................................... 18

2 Fibre Channel Confguration Overview ...........................................................................................21

Conguration Task Overview ........................................................................................................... 21

Conguration Considerations ........................................................................................................... 22

3 AdministeringMultipathing DevicesThrough mpathadm Commands ........................................ 23

Administering Multipathing Devices ............................................................................................... 23

To Get a List o Multipathing Support That Can Be Administered by the mpathadmCommand ..................................................................................................................................... 23

To Get the Multipathing Support Properties ............................................................................ 23

To Get a List o Initiator Ports Discovered on the System ...................................................... 25

To Get the Properties o a Particular Initiator Port .................................................................. 25To Get a List o Logical Units Discovered on the System ........................................................ 25

To Get the Properties and Associated Path Inormation o a Particular Logical Unit byName ............................................................................................................................................. 26

To List All Logical Units Associated With a Particular Target Port ....................................... 27

To List a Logical Unit With a Particular Name Derived From the Hardware Used by theSystem ............................................................................................................................. ............... 29

To Congure Auto-Failback or a Particular Multipathing Support ..................................... 30To Fail Over a Logical Unit ......................................................................................................... 32

3


4/104

To Enable a Path .......................................................................................................................... . 34

To Disable a Path ......................................................................................................................... . 36

4 Confguring Multipathing Sotware .................................................................................................39

Conguring Multipathing .................................................................................................................. 39

Multipathing Considerations ............................................................................................................. 40

Enabling and Disabling Multipathing .............................................................................................. 41

To Enable Multipathing .............................................................................................................. 41

To Disable Multipathing ............................................................................................................. 42

Enabling or Disabling Multipathing on a Per-Port Basis ................................................................ 43

Port Conguration Considerations ........................................................................................... 43

To Congure Multipathing by Port .................................................................................... 44

Conguring Third-Party Storage Devices ........................................................................................ 46

Third-Party Device Conguration Considerations ................................................................. 46

Conguring Third-Party Storage Devices: New Devices ........................................................ 46To Congure New Third-Party Devices ............................................................................ 47

Conguring Third-Party Storage Devices: Disabling Devices ............................................... 48

To Disable Third-Party Devices ......................................................................................... 48

Displaying Device Name Changes ............................................................................................. 48

Conguring Automatic Failback ....................................................................................................... 49

To Congure Automatic Failback .............................................................................................. 50

5 ConfguringSAN Devices ....................................................................................................................51

SAN Device Considerations ............................................................................................................... 51

Adding SAN Devices .......................................................................................................................... . 52

To Add a SAN Device .................................................................................................................. 52

Conguring Fabric Boot Devices on SPARC ................................................................................... 53

Boot Considerations .................................................................................................................... 53

6 ConfguringSAS Domains ..................................................................................................................55

SAS Multipathing Considerations ..................................................................................................... 55

Dynamic Discovery o SAS Devices .................................................................................................. 55

Conguring SAS Boot Devices .......................................................................................................... 56

Contents

Solaris SAN Confguration and Multipathing Guide November 20074


5/104

7 Confguring IPFC SAN Devices ...........................................................................................................57

IPFC Considerations ........................................................................................................................... 57

Determining Fibre Channel Adapter Port Instances ............................................................... 58To Determine Port Instances .............................................................................................. 58

To Plumb an IPFC Instance ................................................................................................ 59

Invoking and Conguring IPFC ........................................................................................................ 60

To Start a Network Interace Manually ..................................................................................... 60

To Congure the Host or Automatic Plumbing Upon Reboot ............................................. 61

8 SunSolaris 10 Update 1 x86/x64 Fibre Channel Operating System Booting Procedure .........63

Setup Requirements ............................................................................................................................ 64

Installation Overview .......................................................................................................................... 64

Installation Procedure ......................................................................................................................... 65

To Summarize the Procedure ..................................................................................................... 65

To Perorm a CD ROM, DVD ROM, or Network-Based OS Installation ............................. 65

Post-Installation Patches or the Sun Solaris 10 Update 1 OS ........................................................ 72

9 Persistent Binding orTape Devices ................................................................................................. 73

Persistent Binding Overview .............................................................................................................. 73

Creating Tape Links ............................................................................................................................ 74

Conguration Steps ..................................................................................................................... 75

A Manual Confgurationor Fabric-Connected Devices ................................................................... 77

Manual Conguration ........................................................................................................................ 77

To Congure Manually ............................................................................................................... 78

Fabric Device Node Conguration ................................................................................................... 78

Ensuring That LUN Level Inormation Is Visible .................................................................... 79To Ensure LUN Level Inormation is Visible .................................................................... 79

To Detect Fabric Devices Visible on a Host ....................................................................... 79

Conguring Device Nodes Without Multipathing Enabled .......................................................... 80

To Congure an Individual Device Without Multipathing .................................................... 80

To Congure Multiple Devices Without Multipathing .......................................................... 82

Conguring Device Nodes With Solaris Multipathing Sotware Enabled ................................... 83

To Congure Individual Devices With Sun StorageTek Trac Manager Sotware ............ 84

Contents

5


6/104

To Congure Multiple Devices With Multipathing ................................................................ 85

Unconguring Fabric Devices ........................................................................................................... 87

Unconguring a Fabric Device .................................................................................................. 87To Uncongure a Fabric Device ......................................................................................... 87

To Uncongure All Fabric Devices on a Fabric-Connected Host Port .......................... 88

To Uncongure a Fabric Device Associated With Sun StorageTek Trac ManagerMultipathing-Enabled Devices ........................................................................................... 89

To Uncongure One Path to a Multipathing Device ....................................................... 90

To Uncongure All Fabric-Connected Devices With Multipathing Enabled .............. 91

B SupportedFC-HBA API .......................................................................................................................93

Supported Fibre Channel HBA API .................................................................................................. 93

C MultipathingTroubleshooting .........................................................................................................97

System Fails to Boot During stmsboot ............................................................................................. 97To Recover From Single User Mode .......................................................................................... 97

System Crashes During stmsboot ..................................................................................................... 98

To Recover rom a System Crash ............................................................................................... 98

Index ................................................................................................................................................... 101

Contents



7/104

Figures

FIGURE 81 System BIOS or Selecting Disk, CD-ROM, or Network Boot Device Priority .. 66

FIGURE 82 Selecting an FC-based Boot Disk During Disk Selection .....................................67

FIGURE 83 luxadm display Command and Output ...............................................................68

FIGURE 84 HBA BIOS Screen or an HBA WWN .....................................................................70

FIGURE 85 HBABIOS Screenor Enabling Boot From the FC LUN ...................................... 71

FIGURE 86 Example System BIOS or Enabling Booting rom an FC LUN ........................... 72

7


8/104

8


9/104

Tables

TABLE 21 Tasks to Congure Solaris OS FC and Sun StorageTek Trac Manager Sotware

...................................................................................................................................... 21TABLE 71 IPFC (NFS/NAS and SNDR) .................................................................................... 57

TABLE B1 Supportedand Unsupported FC-HBA Interaces .................................................93

9


10/104

10


11/104

Preace

The Solaris SAN Confguration and Multipathing Guide provides an overview o the Sun

StorageTekTM

Trac Manager sotware as an integrated part o the Sun SolarisTM

10 OperatingSystem (OS). This guide includes instructions about how to install and congure the sotwareand devices.

This guide is intended or system, storage and network administrators who create and maintainFibre Channel (FC) storage area networks (SANs) and serial attached SCSI (SAS) Domains. Ahigh level o expertise in the management and maintenance o SANS and SAS Domains isassumed.

BeoreYou Read This DocumentBeore you read this book, read the latest Solaris 10 Operating System Release Notes.

How This Document Is OrganizedChapter 1, Product Overview, provides an overview o the Sun StorageTek Trac Managersotware.

Chapter 2, Fibre Channel Conguration Overview, provides an overview o conguring theSun StorageTek Trac Manager sotware.

Chapter 3, Administering Multipathing Devices Through mpathadm Commands, explains

how to use the mpathadm command to enable multipathing administration through the ANSIstandard Multipath Management API.

Chapter 4, Conguring Multipathing Sotware,explains how to congure the multipathingeature or FC devices provided in the Solaris 10 OS.

Chapter 5, Conguring SAN Devices, provides high level overviews o the steps used tocongure SAN devices.

Chapter 6, Conguring SAS Domains,provides high-level overviews o the steps used tocongure SAS domains.

11


12/104


13/104

Documentation, Support, andTraining

The Sun web site provides inormation about the ollowing additional resources:

Documentation (http://www.sun.com/documentation/) Support (http://www.sun.com/support/) Training (http://www.sun.com/training/)

Typographic Conventions

The ollowing table describes the typographic conventions that are used in this book.

TABLE P1 TypographicConventions

Typeace Meaning Example

AaBbCc123 The names o commands, les, anddirectories,

and onscreen computer output

Edit your .login le.

Use ls -a to list all les.

machine_name% you have mail.

AaBbCc123 What youtype, contrasted with onscreen

computer outputmachine_name% su

Password:

aabbcc123 Placeholder: replace with a real name or value The command to remove a le is rm

flename.

AaBbCc123 Book titles,new terms, and terms to beemphasized

ReadChapter 6 in the User's Guide.

A cache is a copy that is stored

locally.

Do notsave the le.

Note: Some emphasized items

appear bold online.

Shell Prompts in Command Examples

The ollowing table shows the deault UNIX system prompt and superuser prompt or the C

shell, Bourne shell, and Korn shell.

Preace

13
http://www.sun.com/documentation/http://www.sun.com/documentation/http://www.sun.com/documentation/http://www.sun.com/support/http://www.sun.com/support/http://www.sun.com/support/http://www.sun.com/training/http://www.sun.com/training/http://www.sun.com/training/http://www.sun.com/training/http://www.sun.com/support/http://www.sun.com/documentation/


14/104

TABLE P2 Shell Prompts

Shell Prompt

C shell machine_name%

C shell or superuser machine_name#

Bourne shell andKorn shell $

Bourne shell andKorn shell or superuser #

Preace



15/104

Product Overview

This chapter provides an overview o the Sun StorageTek Trac Manager sotware.

The Sun StorageTek Trac Manager sotware enables multipathing connections or Sun Solaris10 OS hosts. Both Fibre Channel (FC) and Serial Attached SCSI (SAS) are supported. Thesotware resides on the host and identies the storage devices on your SAN or SAS Domain. The

sotware enables you to attach Fibre Channel storage in either loop or abric mode. Thesotware provides a common interace or managing both Fibre Channel and SAS storage.

In the Sun Solaris 10 OS, abric-connected devices are congured and made available to the hostautomatically during install and boot time.

Note I you are perorming an upgrade and want to make any Fibre Channel (FC) devices

unavailable ater upgrade, those devices have to be manually uncongured using cfgadm -cunconfigure commands. However, to make those devices permanently unavailable to thesystem, you may want to consider using switch zoning or LUN masking. The changes made bycfgadm -c unconfigure do not persist ater a reboot unless manual conguration orabric-connected devices has been turned on. To nd out how to disable the abric devicesdiscovery during boot or install, please reer to Appendix A, Manual Conguration orFabric-Connected Devices

The ollowing topics are discussed:

Sotware Features on page 16 Supported Standards on page 18

1C H A P T E R 1

15


16/104

Sotware FeaturesThe Sun StorageTek Trac Manager sotware enables multipathing connections or the Sun

Solaris 10 OS hosts. Both Fibre Channel (FC) and Serial Attached SCSI (SAS) are supported.The sotware resides on the host and identies the storage devices on your SAN or SAS Domain.The sotware enables you to attach Fibre Channel storage in either loop or abric mode. Thesotware provides a common interace or managing both Fibre Channel and SAS storage.

Fibre Channel Sotware Features

The Sun StorageTek Trac Manager sotware provides the ollowing key eatures:

Dynamic Storage Discovery The sotware automatically recognizes devices and anymodications made to device congurations. This eature makes devices available to thesystem without requiring you to reboot or manually change inormation in congurationles.

Persistent Device Naming Devices that are congured within the sotware maintain theirdevice naming through reboots or reconguration. The only exception to this policy are

tape devices ound in /dev/rmt that will not change unless they are removed and laterregenerated.

Fibre Channel Arbitrated Loop (FCAL) Support OpenBootTM PROM (OBP) commandsthat are used on servers can access FCAL attached storage or scanning the FC loop.

Fabric Booting The Solaris OS supports booting rom abric devices as well as non-abricFibre Channel devices. Fabric topologies with Fibre Channel switches provide higher speed,more connections, and port isolation.

FC-HBA Library What was previously known as the Storage Networking IndustryAssociation Fibre Channel host bus adapter (SNIA FC-HBA) library is now known as theFC-HBA library. The FC-HBA library application programming interace (API) enablesmanagement o FC HBAs and provides a standards-based interace or other applications(such as Sun StorEdgeTM Enterprise Storage Manager) that can be used to gatherinormation about FC HBAs.

Man pages or common FC-HBA APIs are included in the Solaris 10 OS inlibhbaapi(3LIB). For additional inormation about FC specications, reer tohttp://www.t11.org.

SAS Sotware Features Dynamic Storage Discovery The Solaris OS Storage Multipathing sotware automatically

recognizes devices and any modications made to device congurations. This makes

devices available to the system without requiring you to reboot or manually changeinormation in conguration les

Sotware Features



17/104

Persistent Device Naming Dynamic Storage Discovery Devices that are congured withinthe Solaris OS Storage Multipathing sotware maintain their device naming through rebootsor reconguration

Multipathing Sotware Features

The Solaris 10 OS contains the Sun StorageTek Trac Manager sotware. The sotware isenabled by deault or x86-based platorms and optional or SPARC-based platorms. Thesotware contains the ollowing eatures:

Path management The Sun StorageTek Trac Manager sotware dynamically managesthe paths to any storage devices it supports. The addition or removal o paths to a device isdone automatically when a path is brought online or removed rom a service. This eatureenables hosts congured with the sotware to begin with a single path to a device and addmore host controllers, increasing bandwidth and RAS, without changing device names ormodiying applications. Sun storage does not require conguration les to manage ordatabases to keep current. For storage other than Sun, contact your storage vendor ormethods to enable support and to ensure it is qualied with the Sun StorageTek Trac

Manager sotware. Single Device Instances Unlike other multipathing solutions, the Sun StorageTek Trac

Manager sotware is ully integrated with the Solaris 10 OS. The sotware displays multipathdevices as single device instances instead o as one device, or device link, per path. Thiseature reduces the cost o managing complex storage architectures utilities such asformat(1M) or higher level applications such as the Sun Solaris OS Volume Manager tosee one representation o a storage device instead o a separate device or each path.

Failover support Implementing higher levels o RAS requires redundant hostconnectivity to storage devices. The Sun StorageTek Trac Manager sotware manages theailure o storage paths while maintaining host I/O connectivity through available secondarypaths.

Symmetrical/Asymmetrical device support The Sun StorageTek Trac Managersotware supports the ollowing disk storage devices:

All Sun disk storage, both symmetric and asymmetric

All T10/T11 standards-compliant non-Sun symmetrical disk devices Many non-Sun asymmetrical disk arrays.

Please contact your storage vendor to see whether your device is supported.

In addition, T10 ALUA support has been added or those asymmetrical devices that supportthis T10 standard.

I/O load balancing In addition to providing simple ailover support, the Sun StorageTek

Trac Manager sotware can use any active paths to a storage device to send and receiveI/O. With I/O routed through multiple host connections, bandwidth can be increased by the

Sotware Features

Chapter 1 Product Overview 17


18/104

addition o host controllers. The sotware uses a round-robin load-balancing algorithm bywhich individual I/O requests are routed to active host controllers in a series one ater theother.

Queue depth SCSI storage arrays present storage to a host in the orm o a logical unitnumber (LUN). LUNs have a nite set o resources available, such as the amount o data thatcan be stored, as well as the number o active commands that a device or LUN can process atone time. The number o active commands that can be issued beore a device blocks urtherI/O is known as queue depth. When the Sun StorageTek Trac Manager sotware isenabled, a single queue is created or each LUN regardless o the number o distinct orseparate paths it may have to the host. This eature enables the disk driver to maintain andbalance one queue to the LUN, efectively managing queue depth. No other multipathingsotware available or the Solaris 10 OS has this ability.

stmsboot command The Solaris 10 OS includes the stmsboot(1M) command, whichallows you to enable or disable the Solaris OS Multipathing sotware on your boot deviceater the OS installation has been completed. This command is available or both SPARCand x86/x64 systems, and provides support or SAS multipathing with the Solaris 10 Update5 OS.

SAS multipathing is not enabled by deault in the Solaris 10 Update 5 OS or either SPARC

or x86/x64 hosts, so use o the stmsboot command is required as a post-installation step iyou wish to enable Multipathing.

SPARC hosts do not enable multipathing or Fibre Channel devices by deault, so use o thestmsboot command is required as a post-installation step.

X86/x64 hosts do enable multipathing o Fibre Channel devices by deault, so the use o thestmsboot command is not mandatory as a post-installation step.

Dynamic reconfguration The Sun StorageTek Trac Manager sotware supports theSolaris 10 OS dynamic reconguration (DR).

Supported StandardsThe Sun StorageTek Trac Manager sotware is based on open standards or communicatingwith devices and device management, ensuring interoperability with other standards-based

devices and sotware. The ollowing standards are supported by the Sun StorageTek TracManager sotware:

ANSI Standard: Inormation Technology SNIA Multipath Management API Specication(ANSI INCITS 412-2006)

T10 standards, including SCSI-3, SAM, FCP, SPC, and SBC

T11.3 FC standards, including FC-PH, FC-AL, FC-LS, and FC-GS

T11.5 storage management standards, including FC-HBA

IETF standards, including RFC 2625

Supported Standards



19/104

Serial Attached SCSI-2 (SAS2)

Supported Standards

Chapter 1 Product Overview 19


20/104

20


21/104

Fibre Channel Confguration Overview

This chapter provides inormation about conguring the Solaris OS Fibre Channel (FC) and

Storage Multipathing sotware. The ollowing topics are discussed:

Conguration Task Overview on page 21 Conguration Considerations on page 22

Confguration Task Overview

This section provides a high level overview o the tasks that you should perorm to congure the

Sun StorageTek Trac Manager sotware.

The ollowing table lists the conguration tasks, description about each task and the reerenceinormation where you can nd the procedures to perorm each task.

TABLE 21 Tasks to Congure Solaris OS FC and Sun StorageTek Trac Manager Sotware

Confguration Task Task Description Reerence Inormation

Enable Multipathing Multipathing capability is provided by the Sun

StorageTek Trac Manager sotware in the

Solaris 10 OS. This sotware enablesmultipathing: By deault, or Fibre Channel-attached

devices on x86/x64 platorms

By manual conguration on SPARC

platorms

By manual conguration or SAS devices

The steps orenabling

multipathing are outlined in

Chapter 4, ConguringMultipathing Sotware.

2C H A P T E R 2

21

ConfgurationConsiderations


22/104

TABLE 21 Tasks to Congure Solaris OS FC and Sun StorageTek Trac Manager Sotware(Continued)

Confguration Task Task Description Reerence Inormation

Congure FibreChannel Devices

In the Solaris 10 OS, FCAL andabric-connecteddevices are made available to the host. This

eature difers rom previous versions o the Sun

StorageTek Trac Manager sotware running onthe Solaris 8 or 9 OS. Inthose versions, manual

conguration steps were required to achieve

abric-connected device availability on theSolaris host.

Chapter 5, Conguring SANDevices,

Set up FCBootDevice The Sun StorageTek Trac Manager sotwareenables a Solaris server to boot rom a abric

device.

SAN Device Considerations onpage 51

Congure IPFC SAN

devices

You can congure host recognition o IPFC

devices and implementation o IP over FC in a

SAN. Conguration o IPFC depends on theinstance o the Fabric Port (FP) driver or the FC

adapter ports.

Chapter 7, Conguring IPFC

SAN Devices,

Congure SAS Devices Inthe Solaris 10Update 5 OS, multipathing oSAS devices is supported.

Confguration ConsiderationsBeore you congure the Sun StorageTek Trac Manager sotware, consider the ollowing:

Congure ports and zones according to the vendor-specic documentation or storage andswitches.

LUN masking enables specic LUNs to be seen by specic hosts. See your vendor-specicstorage documentation that describes masking.

Power management needs to be disabled or hosts and devices on a SAN. Seepower.conf (4) or details about power management.

The STMS Boot utility is included with the Sun StorageTek Trac Manager sotware that

manages the enable and disable process needed or SAN booting. Issuing the stmsbootcommand allows the automatic update o/etc/vfstab and the dump conguration toreect device name changes when enabling or disabling the Sun StorageTek Trac Managersotware. Note that the sotware is disabled by deault with SPARC devices and enabled bydeault with x86 devices.

ConfgurationConsiderations



23/104

Administering Multipathing Devices Throughmpathadm Commands

You determine and congure Solaris OS multipathing support by using mpathadm commands.Starting with the Solaris 10 Update 3 OS, the mpathadm command enables multipathingadministration through the ANSI standard Multipath Management API. The terms used in thischapter to denote a path, initiator port, target port, and logical unit are consistent with the T10specication.

Administering Multipathing DevicesPerorm the ollowing tasks to administer any multipathing devices.

To Get a List o Multipathing SupportThat Can BeAdministered by the mpathadm Command

The multipathing support is identied with the Multipath Management API plug-in libraryname.

List the multipathing support by typing the mpathadm list mpath-support command.

# mpathadm list mpath-support

mpath-support: libmpscsi_vhci.so

(Only one result is shown in the preceding example.)

To Get the Multipathing Support Properties

The multipathing support properties are associated with Multipath Management API plug-inproperties.

3C H A P T E R 3

23

AdministeringMultipathing Devices


24/104

List the multipathing support by typing the mpathadm list mpath-support command.

# mpathadm list mpath-support


(Only one mpath support name result is shown in the preceding output list example.)

Choose the mpath support name rom the output list.

Listthe multipathing support properties ora specifed mpath supportname by typingthe

mpathadm show mpath-support mpath-support-name command.

# mpathadm show mpath-support libmpscsi_vhci.so


Vendor: Sun Microsystems

Driver Name: scsi_vhci

Default Load Balance: round-robin

Supported Load Balance Types:

round-robin

logical-block

Allows To Activate Target Port Group Access: yes

Allows path Override: noSupported Auto Failback Config: yes

Auto Failback: on

Failback Polling Rate (current/max): 0/0

Supported Auto Probing config: no

Auto Probing: NA

probing Polling Rate (current/max): NA/NA

Supported Devices:

Vendor: SUN

Product: T300

Revision:


round-robin

Vendor: SUN

Product: T4

Revision:


round-robin

The command output also shows a list o device products that is supported by the multipathing

support sotware. The multipathing support libmpscsi_vhci.so supports T10 target port

group compliant devices by deault.

1

2

3

g p g




25/104

To Get a List o Initiator Ports Discovered on theSystem

An initiator port is part o a path that consists o an initiator port, target port, and a logical unit.

Run the mpathadm list initiator-port command.

# mpathadm list initiator-port

Initiator-Port: iqn.1986-03.com.sun:01:080020b7ac2b.437a3b3e,4000002affff

Initiator-Port: 2000000173018713

To Get the Properties o a Particular Initiator PortDisplay the properties o an initiator port by typing the show command.

Run the mpathadm list initiator-port command.

# mpathadm list initiator-port

Initiator-Port: iqn.1986-03.com.sun:01:080020b7ac2b.437a3b3e,4000002affffInitiator-Port: 2000000173018713

Select an initiatorport to userom the output.

Run the mpathadm show initiator-port initiator-port-name command.

# mpathadm show initiator-port 2000000173018713

initiator-port: 2000000173018713Transport Type: Fibre Channel

OS Device File: /devices/pci@1f,2000/SUNW,glc@4/fp@0,0

To Get a List o Logical Units Discovered on the System

Thempathadm list lu

command displays the list o logical units attached to the initiator. Thislist displays the number o paths and the operational path count to each logical unit listed.

Run the mpathadm list lu command.

# mpathadm list lu

/dev/rdsk/c4t60020F20000035AF4267CCCB0002CEE2d0s2

Total Path Count: 2

Operational Path Count: 2

/dev/rdsk/c4t60003BA27D2120004204AC2B000DAB00d0s2

Total Path Count: 2

1

2

3

Chapter 3 Administering Multipathing DevicesThrough mpathadm Commands 25



26/104


/dev/rdsk/c4t60003BA27D2120004204AC1A000F1D6Cd0s2

Total Path Count: 2


To Get the Properties and Associated Path Inormationo a Particular Logical Unit by Name

Display the list o logical units, along with the properties or each logical unit through the

mpathadm command. The list o logical units contains logical unit names that in turn can beused to display the properties o a particular logical unit.


# mpathadm list lu


Total Path Count: 2


/dev/rdsk/c4t60003BA27D2120004204AC2B000DAB00d0s2Total Path Count: 2



Total Path Count: 2


Select a logical unit name rom theoutput.

Run the mpathadm show lu logical-unit-name command.

# mpathadm show lu /dev/rdsk/c4t60003BA27D2120004204AC2B000DAB00d0s2

logical unit: /dev/rdsk/c4t60003BA27D2120004204AC2B000DAB00d0s2

mpath-support libmpscsi_vhci.so

Vendor: SUN

Product: T4

Revision: 0301

Name Type: SCSI Inquiry VPD page 83 type 3

Name: 60003ba27d2120004204ac2b000dab00

Asymmetric: yes

Current Load Balance: round-robin

Logical Unit Group ID: NA

Auto Failback: on

Auto Probing: NA

Paths:

Initiator Port Name: 2000000173818713

1

2

3




27/104

Target Port Name: 20030003ba27d212

Override Path: NA

Path State: OK

Disabled: no



Override path: NA

Path State: OK

Disabled: no

Target Port Groups:

ID: 2Explicit Failover: yes

Access State: standby

Target Ports:

Name: 20030003ba27d212

Relative ID: 0

ID: 5

Explicit Failover: yes

Access State: activeTarget Ports:

Name: 20030003ba27d095

Relative ID: 0

To List All Logical Units Associated With a Particular

Target PortTo list paths through a target port use the show command o a logical unit. First, retrieve the listo target ports associated with a logical unit. Then, use the target port to list all logical unitsassociated with this target port.


# mpathadm list lu


Total Path Count: 2



Total Path Count: 2



Total Path Count: 2


1




28/104


Run the mpathadm show lu command.

# mpathadm show lu /dev/rdsk/c4t60003BA27D2120004204AC2B000DAB00d0s2logical unit: /dev/rdsk/c4t60003BA27D2120004204AC2B000DAB00d0s2


Vendor: SUN

Product: T4

Revision: 0301


Name: 60003ba27d2120004204ac2b000dab00

Asymmetric: yes



Auto Failback: on

Auto Probing: NA

Paths:



Override Path: NAPath State: OK

Disabled: no



Override path: NA

Path State: OK

Disabled: no

Target Port Groups:

ID: 2



Target Ports:

Name: 20030003ba27d212

Relative ID: 0

ID: 5


Access State: active

Target Ports:

Name: 20030003ba27d095

Relative ID: 0

Select a target portrom theoutput list.

2

3

4




29/104

Run the mpathadm list lu -t command.

# mpathadm list lu -t 20030003ba27d212


Total Path Count: 2Operational Path Count: 2


Total Path Count: 2


To List a Logical Unit With a Particular Name DerivedFrom the Hardware Used by the System


# mpathadm list lu


Total Path Count: 2

Operational Path Count: 2/dev/rdsk/c4t60003BA27D2120004204AC2B000DAB00d0s2

Total Path Count: 2



Total Path Count: 2







Vendor: SUN

Product: T4

Revision: 0301Name Type: SCSI Inquiry VPD page 83 type 3

Name: 60003ba27d2120004204ac2b000dab00

Asymmetric: yes



Auto Failback: on

Auto Probing: NA

Paths:

5

1

2

3




30/104



Override Path: NA

Path State: OK

Disabled: no



Override path: NA

Path State: OK

Disabled: no

Target Port Groups:ID: 2



Target Ports:

Name: 20030003ba27d212

Relative ID: 0

ID: 5



Target Ports:

Name: 20030003ba27d095

Relative ID: 0

Select an inquiry-string-nameromthe output.

Run the mpathadm list Lu -n inquiry-string-name command.

# mpathadm list lu -n 60003ba27d2120004204ac2b000dab00



Total Path Count: 2


To Confgure Auto-Failback or a ParticularMultipathing Support

Symmetrical devices allow or automatic ailback to a possible optimal path. I a ailover occurson the initial path, the standby path becomes the new online path. Usually the standby path is asuboptimal path. When auto-ailback is enabled, the initial path comes back online, ailover to

the initial path automatically occurs.

4

5



31/104



32/104

To Fail Over a Logical UnitThis operation is applicable only to devices in the ollowing two categories:

Asymmetric devices with a proprietary ailover mechanism recognized and supported bymultipathing support

Devices conorming to the T10 Standard Target Port Group Support libmpscsi_vhci.soand providing explicitmode asymmetric logical unit access


# mpathadm list lu

/dev/rdsk/c4t60020F20000035AF4267CCCB0002CEE2d0s2Total Path Count: 2



Total Path Count: 2



Total Path Count: 2







Vendor: SUNProduct: T4

Revision: 0301


Name: 60003ba27d2120004204ac2b000dab00

Asymmetric: yes



Auto Failback: on

Auto Probing: NA

Paths:



Override Path: NA

Path State: OK

Disabled: no


1

2

3




33/104


Override path: NA

Path State: OK

Disabled: no

Target Port Groups:

ID: 2



Target Ports:

Name: 20030003ba27d212

Relative ID: 0

ID: 5



Target Ports:

Name: 20030003ba27d095

Relative ID: 0

Run the mpathadm failover lu logical-unit-name command.

# mpathadm failover lu /dev/rdsk/c4t60003BA27D2120004204AC2B000DAB00d0s2

I this operation is successul, the access state o the devices target port groups changes as aresult o the logical unit ailover.

Run the mpathadm show lu logical-unit-name command to veriy the access state change.



mpath-support libmpscsi_vhci.soVendor: SUN

Product: T4

Revision: 0301


Name: 60003ba27d2120004204ac2b000dab00

Asymmetric: yes



Auto Failback: onAuto Probing: NA

Paths:



Override Path: NA

Path State: OK

Disabled: no

4

5




34/104



Override path: NA

Path State: OK

Disabled: no

Target Port Groups:

ID: 2



Target Ports:

Name: 20030003ba27d212

Relative ID: 0

ID: 5



Target Ports:

Name: 20030003ba27d095

Relative ID: 0

To Enable a PathI the path to a logical unit is disabled, the enable command changes the path back to enabled.The ull path must be specied using the initiator port name, target port name, and the logicalunit. To veriy the change, run the show command or the logical unit.

Run the mpathadm list lu command.# mpathadm list lu


Total Path Count: 2



Total Path Count: 2



Total Path Count: 2






1

2

3




35/104


Vendor: SUN

Product: T4

Revision: 0301


Name: 60003ba27d2120004204ac2b000dab00

Asymmetric: yes



Auto Failback: on

Auto Probing: NA

Paths:



Override Path: NA

Path State: OK

Disabled: no


Target Port Name: 20030003ba27d095Override path: NA

Path State: OK

Disabled: no

Target Port Groups:

ID: 2


Access State: standbyTarget Ports:

Name: 20030003ba27d212

Relative ID: 0

ID: 5



Target Ports:

Name: 20030003ba27d095

Relative ID: 0

Select an initiatorport anda target port name.

Run the mpathadm enable path -i initiator-port-name -t target-port-name -l

logical-unit-name command.

# mpathadm enable path -i 2000000173018713 -t 20030003ba27d095 -l /dev/rdsk/c4t60003BA27D2120004204AC2B000DAB00d

4

5




36/104

To Disable a PathThis operation makes the path unavailable or the logical unit, regardless o its operational state.

Note The disabled state is not persistent across rebooting. I the path is operational beore thenext boot sequence, it is enabled by deault.

Note This operation is not allowed when the given path is the last operational path remaining.


# mpathadm list lu


Total Path Count: 2



Total Path Count: 2


/dev/rdsk/c4t60003BA27D2120004204AC1A000F1D6Cd0s2Total Path Count: 2




# mpathadm show lu /dev/rdsk/c4t60003BA27D2120004204AC2B000DAB00d0s2logical unit: /dev/rdsk/c4t60003BA27D2120004204AC2B000DAB00d0s2


Vendor: SUN

Product: T4

Revision: 0301


Name: 60003ba27d2120004204ac2b000dab00

Asymmetric: yes

Current Load Balance: round-robinLogical Unit Group ID: NA

Auto Failback: on

Auto Probing: NA

Paths:



Override Path: NA

Path State: OK

1

2

3




37/104

Disabled: no



Override path: NA

Path State: OK

Disabled: no

Target Port Groups:

ID: 2



Target Ports:Name: 20030003ba27d212

Relative ID: 0

ID: 5



Target Ports:

Name: 20030003ba27d095

Relative ID: 0

Select an initiatorport anda target port name.

Run the mpathadm disable path -i initiator-port-name -t target-port-name -llogical-unit-name command.

# mpathadm disable path -i 2000000173018713 -t 20030003ba27d095

-l /dev/rdsk/c4t60003BA27D2120004204AC2B000DAB00d0s2

4

5



38/104

38


39/104

Confguring Multipathing Sotware

This chapter explains how to congure the Sun StorageTek Trac Manager sotware that is

provided in the Solaris 10 OS or Fibre Channel (FC) devices . It also provides the

considerations while enabling or disabling the multipathing eature on SPARC based systems,

x86 based systems, per-port basis and third-party storage devices.

The ollowing topics are discussed: Conguring Multipathing on page 39 Multipathing Considerations on page 40 Enabling and Disabling Multipathing on page 41 Enabling or Disabling Multipathing on a Per-Port Basis on page 43 Conguring Third-Party Storage Devices on page 46 Conguring Automatic Failback on page 49

Confguring Multipathing

The multipathing eature or FC devices can be congured to control all Sun supported FC

HBAs. Multipathing is disabled by deault or FC devices on SPARC based systems, but is

enabled by deault on x86 based systems. Conguration o the multipathing sotware depends

on how you intend to use your system.

Note The multipathing eature is not available or parallel SCSI devices but is available or FC

disk devices. Multipathing is not supported on tape drives or libraries, or on IP over FC.

Beore you congure third-party devices or multipathing, be aware o the ollowing:

4C H A P T E R 4

39


40/104

Enabling and Disabling Multipathing

Enabling and Disabling Multipathing


41/104

Enabling and Disabling MultipathingWith the release o the Solaris 10 Update 4 OS, the stmsboot(1m) command is now available or

use on SPARC, x86, and x64 based systems to enable or disable multipathing or Fibre Channel(FC) and SAS devices. The stmsboot command updates the /etc/vfstab le and dumpconguration to reect device name changes during the next reboot. You do not need tomanually edit the /kernel/drv/fp.conf or /kernel/drv/mpt.conf les.

The ollowing considerations apply to the stmsboot -e, -d, and -u options:

You should reboot immediately ater running the stmsboot command.

Ensure that eeprom(1m) boot device is set to boot rom your current boot device. This isrequired since the stmsboot command reboots the machine to complete the operation.

The stmsboot command saves a copy o your original /kernel/drv/fp.conf,/kernel/drv/mpt.conf and /etc/vfstab les beore modiying them. See Appendix C,Multipathing Troubleshooting i you encounter unexpected problems while usingstmsboot.

Note The behavior o the stmsboot command in the Solaris 10 OS difers rom the stmsbootcommand provided by Sun StorEdge SAN Foundation sotware in the Solaris 8 and Solaris 9OS. In the Solaris 8 and Solaris 9 OS, the stmsboot command is used to enable or disablemultipathing on the boot device only or SPARC based hosts only. In the Solaris 10 OS, thecommand is used to enable or disable multipathing on all capable devices.

The stmsboot command is available on both SPARC and x86/x64-based systems rom theSolaris 10 Update 4 OS onwards. In the Solaris 10 Update 5 OS the stmsboot command is usedto enable, disable or update multipathing or Serial-Attached SCSI devices as well as FC devices.

To Enable MultipathingPerorm the ollowing steps to enable multipathing on all multipath-capable devices on SPARCor x86/x64 based systems. I you want to enable multipathing only on specic FC or SAS HBAports, reer to Enabling or Disabling Multipathing on a Per-Port Basis on page 43.

The multipathing sotware automatically recognizes Sun supported devices. I you want toenable multipathing on third-party devices, add entries to the /kernel/drv/scsi_vhci.confle as described byDevice Name Change Considerations in Multipathing Considerations onpage 40.

Run the stmsboot -e command:

# stmsboot -e

WARNING: stmsboot operates on each supported multipath-capable controller

detected in a host. In your system, these controllers are

1

Chapter 4 Confguring Multipathing Sotware 41

Enabling and DisablingMultipathing


42/104

/devices/pci@780/pci@0/pci@8/SUNW,qlc@0/fp@0,0

/devices/pci@780/pci@0/pci@8/SUNW,qlc@0,1/fp@0,0

/devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@1



/devices/pci@7c0/pci@0/pci@9/LSILogic,sas@0


If you do NOT wish to operate on these controllers, please quit stmsboot

and re-invoke with -D { fp | mpt } to specify which controllers you wish

to modify your multipathing configuration for.

Do you wish to continue? [y/n] (default: y) y

Checking mpxio status for driver fp

Checking mpxio status for driver mpt

WARNING: This operation will require a reboot.

Do you want to continue ? [y/n] (default: y) y

The changes will come into effect after rebooting the system.

Reboot the system now ? [y/n] (default: y) y

Note During the reboot, /etc/vfstab and the dump conguration are updated to reect thedevice name changes.

(Optional) Ater the reboot, i necessary, confgure your applications to use newdevice names

as described by Device Name Change Considerations in Multipathing Considerationsonpage 40.

To Disable MultipathingPerorm the ollowing steps to disable multipathing on all multipath-capable devices on SPARCor x86/x64 based systems. I you want to disable multipathing only on specic FC or SAS HBAports, reer to Enabling or Disabling Multipathing on a Per-Port Basis on page 43.

Run the stmsboot -d command.

# stmsboot -dWARNING: stmsboot operates on each supported multipath-capable controller

detected in a host. In your system, these controllers are

/devices/pci@780/pci@0/pci@8/SUNW,qlc@0/fp@0,0

/devices/pci@780/pci@0/pci@8/SUNW,qlc@0,1/fp@0,0





2

1



43/104

Load balancing is controlled by the global load-balance property in

Enabling or Disabling Multipathing on a Per-Port Basis


44/104

g y g p p y/kernel/drv/scsi_vhci.conf le and is not controlled on a per-port basis.

Ia device has more than one path to the host, all paths to the device must be congured

with multipathing enabled or disabled. Conguring multipathing by port enables the multipathing sotware to co-exist with other

multipathing solutions like Symantec (VERITAS) Dynamic Multipathing (DMP), or EMCPowerPath. However, devices and paths should not be shared between the multipathingsotware and other multipathing solutions.

To Confgure Multipathing by Port

Depending on how many ports you want the multipathing sotware to control, you can enableor disable multipathing globally or or specied ports.

Log in as root (su - root).

Determine the HBA controllerports that youwant the multipathingsotware to control.

For example, to select the desired device, perorm an ls -l command on /dev/cfg directory.The ollowing example shows the ls -l command output.

lrwxrwxrwx 1 root root 50 Jan 29 21:33 c0 ->

../../devices/pci@7c0/pci@0/pci@1/pci@0/ide@8:scsi


../../devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@1:scsi


../../devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2:scsi


../../devices/pci@7c0/pci@0/pci@9/LSILogic,sas@0:scsi

lrwxrwxrwx 1 root root 54 Apr 16 20:28 c5 ->../../devices/pci@780/pci@0/pci@8/SUNW,qlc@0/fp@0,0:fc

lrwxrwxrwx 1 root root 56 Apr 16 20:28 c6 ->

../../devices/pci@780/pci@0/pci@8/SUNW,qlc@0,1/fp@0,0:fc

Note Controllers c5 and c6 are ports A and B on a dual-port FC HBA. Controllers c1 and c3are single port SAS HBA ports. Controller c2 is the internal SAS controller in a Sun FireTM

T2000 server.

Once you have determined which port(s) you want to explicitly enable or disable multipathingor, go to the next step.

Enableor disable specifc ports as ollows:

FCHBAports

a. Editfle /kernel/drv/fp.conf

1

2

3


b. Add the ollowing lineor eachFC HBA port thatis tobe enabled:

Enabling or Disabling Multipathing on a Per-Port Basis


45/104

name="fp" parent="parent name" port=port-number mpxio-disable="no";

whereparent name is the port device name, andport-numberis the FC HBA port

number.

For example, the ollowing entries disable multipathing on all FC HBA controller portsexept or the two specied ports:

mpxio-disable="yes";

name="fp" parent="/pci@6,2000/SUNW,qlc@2" port=0 mpxio-disable="no";

name="fp" parent="/pci@13,2000/pci@2/SUNW,qlc@5" port=0 mpxio-disable="no";

c. Add the ollowing lineor eachFC HBA port thatis to bedisabled:

name="fp" parent="parent name" port=port-number mpxio-disable="yes";

For example:

name="fp" parent="/pci@6,2000/SUNW,qlc@2" port=0 mpxio-disable="yes";

SASHBA ports

a. Editfle /kernel/drv/mpt.conf

b. Add the ollowing lineor eachSAS HBA port thatis tobe enabled:

name="mpt" parent="parent name" port=port-number mpxio-disable="no";

whereparent name is the port device name, andport-numberis the SAS HBA portnumber.

For example, the ollowing entries disables multipathing on all SAS HBA ports except orthe specied port:

mpxio-disable="yes";

name="mpt" parent="/pci@7c0/pci@0/pci@9" port=0 mpxio-disable="no";

c. Add the ollowing lineor eachSAS HBA port thatis tobe disabled:

name="mpt" parent="parent name" port=port-number mpxio-disable="yes";

For example:

name="mpt" parent="/pci@7c0/pci@0/pci@9" port=0 mpxio-disable="yes";

Type stmsboot -u to start the reboot and confguration process.

You are prompted to reboot. During the reboot, the /etc/vfstab le and your dump device

conguration are updated to reect any device name changes.

4


(Optional) Ater thereboot, i necessary, confgure your applicationsto usenew devicenames asd ib di M l i hi C id i 40

5

ConfguringThird-PartyStorageDevices


46/104

describedin Multipathing Considerationson page40.

ConfguringThird-Party Storage Devices

Note Beore conguring any third-party device, ensure that they are supported. Reer to yourthird-party user documentation, or third-party vendor or inormation on proper vendor andproduct IDs, modes and various settings required or the device to work with multipathingsotware.

Third-Party Device Confguration Considerations

Beore you congure third-party devices or multipathing, be aware o the ollowing:

The device must support the REPORT_LUNS SCSI command, and SCSI-3 INQUIRY commandVPD Device Identication Page (0x83).

You will need the vendor ID (VID) and product ID (PID) o the device. You can obtainthem by using the format command ollowed by the inquiry option on your system. See theformat(1M) man page.

When multipathing is enabled, the multipath access still depends on a device specicscsi_vhci ailover implementation accepting the device. The deault way this occurs,automatically, is or the scsi_vhci code to call aprobe unction in each ailoverimplementation, looking or the rstprobe result that indicates the device is supported.

Aprobe implementation determines support based on some combination oscsi_inquiry(9S)data. A device with INQUIRY data indicating T10 Target-Port-Group-Support (TPGS)compliance will use the standards-based TPGS ailover implementation. For non-compliantdevices, a ailover implementation's probe will typically determine support based on VID/PIDmatch against a private compiled-in table.

To override theprobe process, the scsi_vhci.conf le supports ascsi-vhci-failover-override property. The value oscsi-vhci-failover-override can be

used to establish support or a device not currently accepted byprobe, overrideprobe support,or disable multipath support or a device.

Confguring Third-Party Storage Devices: New Devices

Multipathing can be congured on third-party symmetric storage devices. A symmetric storagedevice is dened as a storage device in which all paths to the storage device are active and I/O

commands can be issued through any path.


To Confgure NewThird-Party Devices

ConfguringThird-PartyStorage Devices


47/104

Perorm the ollowing steps to congure third-party devices i your system already has

multipathing enabled. I your system has multipathing disabled, you can congure third-party

devices while enabling multipathing as described earlier in this chapter.

Add the vendor ID and product ID entries to the /kernel/drv/scsi_vhci.conf fle.

The vendor ID and product ID are the vendor and product identication strings that the device

returns in SCSI INQUIRY data. The vendor ID must be eight characters long. You must speciy

all eight characters even i the trailing characters are spaces.

The product ID can be up to 16 characters long.

device-type-scsi-options-list =

"VendorID1ProductID1", "enable-option",

"VendorID2ProductID2", "enable-option",

...

"VendorIDnProductIDn", "enable-option";

enable-option = 0x1000000;

Note that the entries are separated by the , character and the last vendor/product entry is

terminated by the ; character.

For example, to add a device rom a ACME vendor with a product ID o MSU, and to add a

device rom vendor XYZ vendor with a product ID o ABC, you would add the ollowing

lines to le /kernel/drv/scsi_vhci.conf :

To add a device rom a XYZ vendor with a product ID o ABC, you would add:


"ACME MSU", "enable-option",

"XYZ ABC", "enable-option";

enable-option = 0x1000000;

Save andexit the scsi_vhci.conf fle.


You are prompted to reboot. During the reboot, the /etc/vfstab le and the dump

conguration are updated to reect the device name changes.

I necessary, perormdevice name updates as describedin Enablingand Disabling

Multipathingon page41.

1

2

3

4


Confguring Third-Party Storage Devices: Disabling

ConfguringThird-PartyStorageDevices


48/104

Devices

Multipathing can be disabled or all devices o a certain Vendor ID/Product ID combinationrom Inquiry data. This exclusion is specied in the scsi_vhci.conf le.

To Disable Third-Party Devices

Add the vendorID and product ID entries tothe /kernel/drv/scsi_vhci.conf fle.

The vendor ID and product ID are the vendor and product identication strings that the device

returns in SCSI INQUIRY data. The vendor ID must be eight characters long. You must speciyall eight characters even i the trailing characters are spaces. The product ID can be up to 16characters long.


"VendorID1ProductID1", "disable-option",

"VendorID2ProductID2", "disable-option",

...

"VendorIDnProductIDn", "disable-option";

disable-option = 0x7000000;

The entries in the preceding example are separated by the , character and the lastvendor/product entry is terminated by the ; character. For example, to add a device romvendor ACME with a product ID o MSU, and a vendor device rom vendor XYZ withproduct ID ABC, you would add the ollowing lines to the le /kernel/drv/scsi_vhci.conf :


"ACME MSU", "disable-option",

"XYZ ABC

",

"disable-option

";

disable-option = 0x7000000;

Save andexit the scsi_vhci.conf fle.


You are prompted to reboot. During the reboot, the /etc/vfstab le and the dumpconguration are updated to reect the device name changes.

I necessary, perormthe devicename updates as described in Enablingand DisablingMultipathingon page 41.

Displaying Device Name Changes

The stmsboot(1M) command, available on Solaris OS 10 Update 5 SPARC, x86 and x64

platorms, can be used to display the mapping between non-multipathed and multipathed

1

2

3

4


device names, ater the changes made to the multipath conguration by invoking stmsboot

with the -e -d or -u option Both the non-multipathed and the multpathed device names must

Confguring AutomaticFailback


49/104

with the -e, -d, or -u option. Both the non-multipathed and the multpathed device names must

exist in order to show the mapping.

The -L option displays the mapping o devices on all controllers.

# stmsboot -L

non-STMS device name STMS device name

----------------------------------------------------------------

/dev/rdsk/c2t8d0 /dev/rdsk/c10t500000E01046DEE0d0

/dev/rdsk/c2t0d0 /dev/rdsk/c10t500000E01046B070d0

/dev/rdsk/c2t3d0 /dev/rdsk/c10t20000020372A40AFd0

/dev/rdsk/c2t12d0 /dev/rdsk/c10t500000E01046DEF0d0

/dev/rdsk/c2t11d0 /dev/rdsk/c10t500000E01046E390d0



/dev/rdsk/c3t3d0 /dev/rdsk/c10t20000020372A40AFd0

/dev/rdsk/c3t12d0 /dev/rdsk/c10t500000E01046DEF0d0


The -l option displays the mapping o devices on only the specied controller. The ollowingexample displays the mapping o controller 3.

# stmsboot -l3

non-STMS device name STMS device name

----------------------------------------------------------------



/dev/rdsk/c3t3d0 /dev/rdsk/c10t20000020372A40AFd0/dev/rdsk/c3t12d0 /dev/rdsk/c10t500000E01046DEF0d0


Confguring Automatic Failback

Some storage devices have controllers congured as PRIMARY and SECONDARY as part othe array conguration. The secondary paths may operate at a lower perormance level than the

primary paths. The multipathing sotware uses the primary path to talk to the storage device

and keeps the secondary path on standby. In the event o a primary path ailure, the

multipathing sotware automatically directs all I/O trac over the secondary path, with the

primary path taken oine. This process is called a ailover operation. When the ailure

associated with the primary path has been repaired, the multipathing sotware automatically

directs all I/O trac over the primary path and keeps the secondary path standby as beore. This

process is called a ailback operation.


You can disable the automatic ailback operation so the multipathing sotware does notautomatically ailback to the primary path. Later, ater the ailure associated with the primary

Confguring AutomaticFailback


50/104

automatically ailback to the primary path. Later, ater the ailure associated with the primarypath has been repaired, you can do a manual ailback operation using the luxadm(1M)command.

To Confgure Automatic Failback

Open the /kernel/drv/scsi_vhci.conf fle in a text editor.

To disable automatic ailback capability, change the auto-ailback entry to:

auto-failback="disable";

To enable automatic ailback capability (i you disabled it beore), change the auto-ailbackentry to:

auto-failback="enable";

Save andexit thefle.

Reboot the system.

# shutdown -g0 -y -i6

1

2

3

4


5C H A P T E R 5


51/104

Confguring SAN Devices

This chapter provides the high level overview o the steps used to congure SAN devices. In the,

FCAL and abric-connected devices are made available to the host automatically. This eature

difers rom previous versions o the SAN Foundation sotware running on the Solaris 8 or the

Solaris 9 OS. In those versions, manual conguration steps were required to achieve

abric-connected device availability on the host. To nd out how to manually congure

abric-connected devices, reer to Appendix A, Manual Conguration or Fabric-ConnectedDevices.

The ollowing topics are discussed:

SAN Device Considerations on page 51 Adding SAN Devices on page 52 Conguring Fabric Boot Devices on SPARC on page 53

SAN Device Considerations

Be aware o the ollowing considerations beore conguring the Sun StorageTek Trac

Manager sotware.

Congure ports and zones according to the vendor-specic documentation or storage and

switches. With the Solaris 10 OS you no longer have to manually congure devices unless you enable

manual device conguration.

LUN masking enables specic LUNs to be seen by specic hosts. See your vendor-specic

storage documentation that describes masking.

Turn of power management on servers connected to the SAN to prevent unexpected results

as one server attempts to power down a device while another attempts to gain access. See

power.conf(1M) man page or details about power management.

5

51

Connect arrays and other storage devices to the SAN with or without multipathingcapability. The Sun StorageTek Trac Manager sotware is an associated application that is

Adding SAN Devices


52/104

bundled with the product name.

The STMS Boot utility is included with the Sun StorageTek Trac Manager sotware thatmanages the enable and disable process needed or SAN booting. Issuing the stmsbootcommand allows the automatic update o/etc/vfstab and the dump conguration toreect device name changes when enabling or disabling the Sun StorageTek Trac Managersotware. Note that the sotware is disabled by deault with SPARC devices and enabled bydeault with x86 devices.

Adding SAN DevicesAdding and removing SAN devices requires knowledge o the ollowing commands:

luxadm(1M)

format(1M)

fsck(1M)

newfs(1M)

cfgadm(1M) and cfgadm_fp(1M)

Note I you use the format command when the Sun StorageTek Trac Manager sotwaremultipathing eature is enabled, you will see only one instance o a device identier or eachLUN. Without the Sun StorageTek Trac Manager sotware enabled, you will see oneidentier or each path.

The cfgadm and cfgadm_fp commands are used most requently to congure storage devices ona SAN. Reer to the appropriate man page or detailed instructions about how to use eachcommand.

ToAddaSANDevice

Create theLUNsdesired on theSAN device.

I necessary, apply LUN masking orHBA control on theSAN device.

Connect thestoragedevice to thesystem.

I necessary, create port-basedor WWNzones on theswitch on theSAN device.

Runthe fsck or newfs commands on thedevice, i used orfle systems.

1

2

3

4

5



53/104


54/104

54

6C H A P T E R 6


55/104

Confguring SAS Domains

This chapter provides overviews o SAS Domain considerations, SAS device discovery, and SASboot device conguration.

SAS Multipathing Considerations SAS multipathing is supported with the Solaris 10 Update 5 OS release when using the

bundled mpt(7d) driver.

SAS expanders are not supported with the Solaris 10 Update 5 OS release.

LUN masking is not supported with SAS-attached devices in the Solaris 10 Update 5 OSrelease.

Turn of power management on hosts connected to the SAS Domain in order to preventunexpected results as one server attempts to power down a device while another attempts togain access. See pmconfig(1m) and power.conf(4) or details about power management.

Dynamic Discovery o SAS Devices

Adding and removing SAS devices is perormed dynamically when using the mpt(7d) driver.You are no longer required to edit the sd.conf le to enable your system to detect specictargets and LUNs attached with the mpt driver. See mpt(7d) or more inormation.

You are no longer required to edit the sd.conf le to enable your system to detect specictargets and LUNs attached with the mpt driver.

I you add or remove a device in your SAS domain, messages will be written to the/var/adm/messages le indicating presence or removal. I a device has been added, it is visible

to and available by the format(1m) command.

55

Confguring SAS Boot DevicesThe Solaris Multipathed IO sotware allows Solaris 10 Update 5 OS hosts to boot rom a

ConfguringSAS BootDevices


56/104

The Solaris Multipathed IO sotware allows Solaris 10 Update 5 OS hosts to boot rom amultipathed SAS device, or rom a SATA device connected to a SAS controller. Only thebundled mpt driver is supported or SAS multipathing in the Solaris 10 Update 5 OS release.

Some SAS and SATA devices might not support multipathing but will still unction asnon-multipathed devices. See http://sunsolve.sun.com or more inormation.

http://sunsolve.sun.com/http://sunsolve.sun.com/


57/104

Any standard network commands can be used ater IPFC is attached. These commands(telnet, ping, or ftp) are used in this environment in the same way as in an Ethernet setup.

IPFC Considerations


58/104

Determining Fibre Channel Adapter Port Instances

This section explains how to congure the desired host system or IPFC. It includes theprocedures to determine the port instance and to plumb an IPFC instance.

To Determine Port Instances

Determinethe HBAPCI adapter slot andthe I/Oboard PCIslot.

You need this inormation to perorm the calculation in Determining Fibre Channel AdapterPort Instances on page 58.

For example, assume you have an array with an HBA card located in PCI adapter slot 5, and thePCI adapter is in slot 1 o the I/O board.

Determine the instancenumber.

a. Search or the fp driver binding name in

solaris san configuration and multi pa thing guide

Documents