Solaris SAN Configuration and Multipathing Guide Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A.
Copyright 2009 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more U.S. patents or pending patent applications in the U.S. and in other countries. U.S. Government Rights – Commercial software.
Contents Preface ...................................................................................................................................................11 1 Product Overview ................................................................................................................................15 About Sun StorageTek Traffic Manager ........................................................................................... 15 Software Features ..........................................
Contents ▼ To Fail Over a Logical Unit ......................................................................................................... 34 ▼ To Enable a Path ........................................................................................................................... 36 ▼ To Disable a Path .......................................................................................................................... 38 4 4 Configuring Multipathing Software ..............................
Contents Determining Fibre Channel Adapter Port Instances ............................................................... 60 Invoking and Configuring IPFC ........................................................................................................ 62 ▼ To Start a Network Interface Manually ..................................................................................... 62 ▼ To Configure the Host for Automatic Plumbing Upon Reboot .............................................
Contents C Multipathing Troubleshooting .........................................................................................................99 System Fails to Boot During stmsboot ............................................................................................. 99 ▼ To Recover From Single User Mode .......................................................................................... 99 System Crashes During stmsboot ....................................................................
Figures FIGURE 8–1 FIGURE 8–2 FIGURE 8–3 FIGURE 8–4 FIGURE 8–5 FIGURE 8–6 System BIOS for Selecting Disk, CD-ROM, or Network Boot Device Priority .. 68 Selecting an FC-based Boot Disk During Disk Selection ..................................... 69 luxadm display Command and Output ............................................................... 70 HBA BIOS Screen for an HBA WWN ..................................................................... 72 HBA BIOS Screen for Enabling Boot From the FC LUN ........
Tables TABLE 2–1 TABLE 7–1 TABLE B–1 Tasks to Configure Solaris OS FC and Sun StorageTek Traffic Manager Software ...................................................................................................................................... 21 IPFC (NFS/NAS and SNDR) .................................................................................... 59 Supported and Unsupported FC-HBA Interfaces .................................................
Preface The Solaris SAN Configuration and Multipathing Guide provides an overview of the Sun StorageTekTM Traffic Manager software as an integrated part of the Sun SolarisTM 10 Operating System (OS). This guide includes instructions about how to install and configure the software and devices. This guide is intended for system, storage and network administrators who create and maintain Fibre Channel (FC) storage area networks (SANs) and serial attached SCSI (SAS) Domains.
Preface Chapter 7, “Configuring IPFC SAN Devices,” explains considerations when configuring IPFC SAN Devices. Chapter 8, “Sun Solaris 10 Update 6 x86/x64 Fibre Channel Operating System Booting Procedure”describes how to manually install the Solaris 10 OS, x86/x64 FC Operating System. Chapter 9, “Persistent Binding for Tape Devices”describes how you can specify tape binding in the Solaris 10 OS while retaining the benefits of automatic discovery for disk-based devices.
Preface Documentation, Support, and Training The Sun web site provides information about the following additional resources: ■ ■ ■ Documentation (http://www.sun.com/documentation/) Support (http://www.sun.com/support/) Training (http://www.sun.com/training/) Sun Welcomes Your Comments Sun is interested in improving its documentation and welcomes your comments and suggestions. To share your comments, go to http://docs.sun.com and click Feedback.
Preface Shell Prompts in Command Examples The following table shows the default UNIX system prompt and superuser prompt for the C shell, Bourne shell, and Korn shell.
1 C H A P T E R 1 Product Overview This chapter provides an overview of the Sun StorageTek Traffic Manager software, and covers the following topics: ■ ■ ■ “About Sun StorageTek Traffic Manager” on page 15 “Software Features” on page 16 “Supported Standards” on page 18 About Sun StorageTek Traffic Manager The Sun StorageTek Traffic Manager software enables multipathing connections for Sun Solaris 10 OS hosts.
Software Features Software Features The Sun StorageTek Traffic Manager software enables multipathing connections for the Sun Solaris 10 OS hosts, with the following software features: ■ ■ ■ “Fibre Channel Software Features” on page 16 “SAS Software Features” on page 16 “Multipathing Software Features” on page 17 Fibre Channel Software Features The Sun StorageTek Traffic Manager software provides the following key features: ■ Dynamic Storage Discovery – The software automatically recognizes devices and a
Software Features ■ Persistent Device Naming – Dynamic Storage Discovery Devices that are configured within the Solaris OS Storage Multipathing software maintain their device naming through reboots or reconfiguration. Multipathing Software Features The Solaris 10 OS contains the Sun StorageTek Traffic Manager software. The software is enabled by default for x86-based platforms and optional for SPARC-based platforms.
Supported Standards addition of host controllers. The software uses a round-robin load-balancing algorithm by which individual I/O requests are routed to active host controllers in a series one after the other. ■ Queue depth – SCSI storage arrays present storage to a host in the form of a logical unit number (LUN). LUNs have a finite set of resources available, such as the amount of data that can be stored, as well as the number of active commands that a device or LUN can process at one time.
Supported Standards ■ Serial Attached SCSI-2 (SAS2) Chapter 1 • Product Overview 19
2 C H A P T E R 2 Fibre Channel Configuration Overview This chapter provides information about configuring the Solaris OS Fibre Channel (FC) and Storage Multipathing software. The following topics are discussed: ■ ■ “Configuration Task Overview” on page 21 “Configuration Considerations” on page 22 Configuration Task Overview This section provides a high level overview of the tasks that you should perform to configure the Sun StorageTek Traffic Manager software.
Configuration Considerations TABLE 2–1 Tasks to Configure Solaris OS FC and Sun StorageTek Traffic Manager Software (Continued) Configuration Task Task Description Reference Information Configure Fibre Channel Devices In the Solaris 10 OS, FCAL, fabric, and point-to-point connected devices are made available to the host. This feature differs from previous versions of the Sun StorageTek Traffic Manager software running on the Solaris 8 or 9 OS.
Configuration Considerations Note – If you are performing an upgrade and want to make any Fibre Channel (FC) devices unavailable after upgrade, those devices have to be manually unconfigured using cfgadm -c unconfigure commands. However, to make those devices permanently unavailable to the system, you may want to consider using switch zoning or LUN masking. The changes made by cfgadm -c unconfigure do not persist after a reboot unless manual configuration for fabric-connected devices has been turned on.
3 C H A P T E R 3 Administering Multipathing Devices Through mpathadm Commands You determine and configure Solaris OS multipathing support by using mpathadm commands. Starting with the Solaris 10 Update 3 OS, the mpathadm command enables multipathing administration through the ANSI standard Multipath Management API. The terms used in this chapter to denote a path, initiator port, target port, and logical unit are consistent with the T10 specification.
Administering Multipathing Devices 1 List the multipathing support by typing the mpathadm list mpath-support command. # mpathadm list mpath-support mpath-support: libmpscsi_vhci.so (Only one mpath support name result is shown in the preceding output list example.) 2 Choose the mpath support name from the output list. 3 List the multipathing support properties for a specified mpath support name by typing the mpathadm show mpath-support mpath-support-name command.
Administering Multipathing Devices ▼ To Get a List of Initiator Ports Discovered on the System An initiator port is part of a path that consists of 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.
Administering Multipathing Devices Operational Path Count: 2 /dev/rdsk/c4t60003BA27D2120004204AC1A000F1D6Cd0s2 Total Path Count: 2 Operational Path Count: 2 ▼ To Get the Properties and Associated Path Information of a Particular Logical Unit by Name Display the list of logical units, along with the properties for each logical unit through the mpathadm command. The list of logical units contains logical unit names that in turn can be used to display the properties of a particular logical unit.
Administering Multipathing Devices Target Port Name: 20030003ba27d212 Override Path: NA Path State: OK Disabled: no Initiator Port Name: 2000000173018713 Target Port Name: 20030003ba27d095 Override path: NA Path State: OK Disabled: no Target Port Groups: ID: 2 Explicit Failover: yes Access State: standby Target Ports: Name: 20030003ba27d212 Relative ID: 0 ID: 5 Explicit Failover: yes Access State: active Target Ports: Name: 20030003ba27d095 Relative ID: 0 ▼ To List All Logical Units Associated With a Par
Administering Multipathing Devices 2 Select a logical unit name from the output. 3 Run the mpathadm show lu command. # mpathadm show lu /dev/rdsk/c4t60003BA27D2120004204AC2B000DAB00d0s2 logical unit: /dev/rdsk/c4t60003BA27D2120004204AC2B000DAB00d0s2 mpath-support libmpscsi_vhci.
Administering Multipathing Devices 5 Run the mpathadm list lu -t command. # mpathadm list lu -t 20030003ba27d212 /dev/rdsk/c4t60003BA27D2120004204AC2B000DAB00d0s2 Total Path Count: 2 Operational Path Count: 2 /dev/rdsk/c4t60003BA27D2120004204AC1A000F1D6Cd0s2 Total Path Count: 2 Operational Path Count: 2 ▼ 1 To List a Logical Unit With a Particular Name Derived From the Hardware Used by the System Run the mpathadm list lu command.
Administering Multipathing Devices Initiator Port Name: 2000000173818713 Target Port Name: 20030003ba27d212 Override Path: NA Path State: OK Disabled: no Initiator Port Name: 2000000173018713 Target Port Name: 20030003ba27d095 Override path: NA Path State: OK Disabled: no Target Port Groups: ID: 2 Explicit Failover: yes Access State: standby Target Ports: Name: 20030003ba27d212 Relative ID: 0 ID: 5 Explicit Failover: yes Access State: active Target Ports: Name: 20030003ba27d095 Relative ID: 0 4 Select an
Administering Multipathing Devices 1 Run the mpathadm list mpath-support command. # mpathadm list mpath-support mpath-support: libmpscsi_vhci.so 2 Select an mpath support name from the output list. 3 Run the mpathadm modify mpath-support -a [on | off] mpath-support-name command. # mpathadm modify mpath-support -a off libmpscsi_vhci.so 4 Run the mpathadm show mpath-support mpath-support-name command to check the change. # mpathadm show mpath-support libmpscsi_vhci.so mpath-support: libmpscsi_vhci.
Administering Multipathing Devices ▼ To Fail Over a Logical Unit This operation is applicable only to devices in the following two categories: 1 ■ Asymmetric devices with a proprietary failover mechanism recognized and supported by multipathing support ■ Devices conforming to the T10 Standard Target Port Group Support libmpscsi_vhci.so and providing explicit mode asymmetric logical unit access Run the mpathadm list lu command.
Administering Multipathing Devices Target Port Name: 20030003ba27d095 Override path: NA Path State: OK Disabled: no Target Port Groups: ID: 2 Explicit Failover: yes Access State: standby Target Ports: Name: 20030003ba27d212 Relative ID: 0 ID: 5 Explicit Failover: yes Access State: active Target Ports: Name: 20030003ba27d095 Relative ID: 0 4 Run the mpathadm failover lu logical-unit-name command.
Administering Multipathing Devices Initiator Port Name: 2000000173018713 Target Port Name: 20030003ba27d095 Override path: NA Path State: OK Disabled: no Target Port Groups: ID: 2 Explicit Failover: yes Access State: active Target Ports: Name: 20030003ba27d212 Relative ID: 0 ID: 5 Explicit Failover: yes Access State: standby Target Ports: Name: 20030003ba27d095 Relative ID: 0 ▼ To Enable a Path If the path to a logical unit is disabled, the enable command changes the path back to enabled.
Administering Multipathing Devices mpath-support libmpscsi_vhci.
Administering Multipathing Devices ▼ To Disable a Path This operation makes the path unavailable for the logical unit, regardless of its operational state. Note – The disabled state is not persistent across rebooting. If the path is operational before the next boot sequence, it is enabled by default. This operation is not allowed when the given path is the last operational path remaining. 1 Run the mpathadm list lu command.
Administering Multipathing Devices Target Port Name: 20030003ba27d095 Override path: NA Path State: OK Disabled: no Target Port Groups: ID: 2 Explicit Failover: yes Access State: standby Target Ports: Name: 20030003ba27d212 Relative ID: 0 ID: 5 Explicit Failover: yes Access State: active Target Ports: Name: 20030003ba27d095 Relative ID: 0 4 Select an initiator port and a target port name. 5 Run the mpathadm disable path -i initiator-port-name -t target-port-name -l logical-unit-name command.
4 C H A P T E R 4 Configuring Multipathing Software This chapter explains how to configure the Sun StorageTek Traffic Manager software that is provided in the Solaris 10 OS for Fibre Channel (FC) devices . It also provides the considerations while enabling or disabling the multipathing feature on SPARC based systems, x86 based systems, per-port basis and third-party storage devices.
Multipathing Considerations Multipathing Considerations Before you change multipathing configuration note the following considerations. Then follow the instructions for your machine architecture (SPARC or x86) described in the subsequent sections. Some devices need to be properly configured to work with the multipathing software. Refer to your storage array documentation for details on the device specific configuration for your device.
Enabling and Disabling Multipathing The following considerations apply to the stmsboot -e, -d, and -u options: ■ You should reboot immediately after running the stmsboot command. ■ Ensure that eeprom(1m) boot device is set to boot from your current boot device. This is required since the stmsboot command reboots the machine to complete the operation. ■ The stmsboot command saves a copy of your original /kernel/drv/fp.conf, /kernel/drv/mpt.conf and /etc/vfstab files before modifying them.
Enabling and Disabling Multipathing 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.
Enabling or Disabling Multipathing on a Per-Port Basis 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 configuration are updated to reflect the device name changes.
Enabling or Disabling Multipathing on a Per-Port Basis ▼ To Configure Multipathing by Port Depending on how many ports you want the multipathing software to control, you can enable or disable multipathing globally or for specified ports. 1 Log in as root (su - root). 2 Determine the HBA controller ports that you want the multipathing software to control. For example, to select the desired device, perform an ls -l command on /dev/cfg directory. The following example shows the ls -l command output.
Configuring Third-Party Storage Devices For example, the following entries disable multipathing on all FC HBA controller ports except for the two specified 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.
Configuring Third-Party Storage Devices A probe implementation determines support based on some combination of scsi_inquiry(9S) data. A device with INQUIRY data indicating T10 Target-Port-Group-Support (TPGS) compliance will use the standards-based TPGS failover implementation. For noncompliant devices, a failover implementation's probe will typically determine support based on VID/PID match against a private compiled-in table. To override the probe process, the scsi_vhci.
Configuring Third-Party Storage Devices To add a device from a “XYZ” vendor with a product ID of “ABC”, you would add: device-type-scsi-options-list = "ACME MSU", "enable-option", "XYZ ABC", "enable-option"; enable-option = 0x1000000; 2 Save and exit the scsi_vhci.conf file. 3 Type stmsboot -u to start the reboot and configuration process. You are prompted to reboot. During the reboot, the /etc/vfstab file and the dump configuration are updated to reflect the device name changes.
Configuring Third-Party Storage Devices "XYZ ABC", "disable-option"; disable-option = 0x7000000; 2 Save and exit the scsi_vhci.conf file. 3 Type stmsboot -u to start the reboot and configuration process. You are prompted to reboot. During the reboot, the /etc/vfstab file and the dump configuration are updated to reflect the device name changes. 4 If necessary, perform the device name updates as described in “Enabling and Disabling Multipathing”on page 42.
Configuring Automatic Failback /dev/rdsk/c3t12d0 /dev/rdsk/c3t11d0 /dev/rdsk/c10t500000E01046DEF0d0 /dev/rdsk/c10t500000E01046E390d0 Configuring Automatic Failback Some storage devices have controllers configured as PRIMARY and SECONDARY as part of the array configuration. The secondary paths may operate at a lower performance level than the primary paths. The multipathing software uses the primary path to talk to the storage device and keeps the secondary path on standby.
5 C H A P T E R 5 Configuring SAN Devices This chapter provides the high level overview of the steps used to configure SAN devices. In the Solaris 10 OS, FCAL, fabric, and point-to-point connected devices are made available to the host automatically. This feature differs from previous versions of the SAN Foundation software running on the Solaris 8 or the Solaris 9 OS. In those versions, manual configuration steps were required to achieve fabric-connected device availability on the host.
Adding SAN Devices ■ Connect arrays and other storage devices to the SAN with or without multipathing capability. The Sun StorageTek Traffic Manager software is an associated application that is bundled with the product name. ■ The STMS Boot utility is included with the Sun StorageTek Traffic Manager software that manages the enable and disable process needed for SAN booting.
Configuring Fabric Boot Devices on SPARC 6 Mount any existing file systems available on the storage device’s LUNs or disk groups. Note – You might need to run the fsck command to repair any errors in the LUNs listed in the /etc/vfstab file. Configuring Fabric Boot Devices on SPARC The Sun StorageTek Traffic Manager software allows a Solaris 10 OS SPARC server to be booted from a fabric disk device.
6 C H A P T E R 6 Configuring SAS Domains This chapter provides overviews of SAS Domain considerations, SAS device discovery, and SAS boot device configuration. 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 OS release.
Configuring SAS Boot Devices Configuring SAS Boot Devices The Solaris Multipathed IO software allows Solaris 10 Update 5 OS hosts to boot from a multipathed SAS device, or from a SATA device connected to a SAS controller. Only the bundled mpt driver is supported for SAS multipathing in the Solaris 10 Update 5 OS release. Some SAS and SATA devices might not support multipathing but will still function as non-multipathed devices. See http://sunsolve.sun.com for more information.
7 C H A P T E R 7 Configuring IPFC SAN Devices Configuring Internet Protocol over Fibre Channel (IPFC) on the host system describes host recognition of IPFC devices and implementation of IP over FC in a SAN. The IPFC driver is based on RFC 2625 and allows IP traffic to run over FC. This chapter contains the following topics: ■ ■ “IPFC Considerations” on page 59 “Invoking and Configuring IPFC” on page 62 IPFC Considerations The following table shows the supported features available for IPFC.
IPFC Considerations ■ Any standard network commands can be used after IPFC is attached. These commands (telnet, ping, or ftp) are used in this environment in the same way as in an Ethernet setup. Determining Fibre Channel Adapter Port Instances This section explains how to configure the desired host system for IPFC. It includes the procedures to determine the port instance and to plumb an IPFC instance. ▼ To Determine Port Instances 1 Determine the HBA PCI adapter slot and the I/O board PCI slot.
IPFC Considerations iv. Search for the fp entry with pci@ hex where hex is the number you derived in Step iii. The following table shows the elements of the device path for a PCI single FC network adapter device that has the following path: "/pci@b,2000/SUNW,qlc@2/fp@0,0" 7 "fp" Entry Item Entry Value Physical Name /pci@b,2000/SUNW,qlc@2/fp@0,0 Instance Number 7 Driver Binding Name fp c. Manually plumb each FP instance. Use the ifconfig interface-number plumb command.
Invoking and Configuring IPFC 3 List the physical path of the originating HBA port from which you can see the destination HBA port, where originating-hba-link is a variable for the link determined in Step 2. # ls -l /dev/fc/fp originating-hba-link In the following example, 0 is the number for the originating-hba-link: # ls -l /dev/fc/fp 0 lrwxrwxrwx 1 root root 51 Sep 4 08:23 /dev/fc/fp0 -> ../../devices/pci@8,600000/SUNW,qlc@1/fp@0,0:devctl 4 Search the physical path identified in Step 3.
Invoking and Configuring IPFC 1 Use the ifconfig command with the appropriate interface. Ask your network administrator for an appropriate IP address and netmask information. For example, to enable an IPFC interface associated with fp instance 0 and an IP address of 192.9.201.10, type: # touch /etc/notrouter # ifconfig fcip0 inet 192.9.201.10 netmask 255.255.255.0 up The ifconfig command is described in more detail in the ifconfig(1M) man page.
Invoking and Configuring IPFC 3 Edit the /etc/nsswitch.conf file so that all uncommented entries have the word files before any other name service. The /etc/nsswitch.conf specifies which name service to use for a particular machine. The following code shows an example of an /etc/nsswitch.conf file.
8 C H A P T E R 8 Sun Solaris 10 Update 6 x86/x64 Fibre Channel Operating System Booting Procedure Starting with Sun Solaris 10 Update 6, x86/x64 Operating System (OS), Fibre Channel (FC) devices now appear in the disk selection portion of Solaris SunInstall. An interactive Solaris 10 Update 6 installation is now required due to the potentially large number of devices that might appear in the disk selection portion of Solaris SunInstall.
Setup Requirements Setup Requirements You must have the following items for installation.
Installation Procedure Installation Procedure ▼ 1 To Summarize the Procedure Install the HBA hardware. Follow the instructions in the appropriate Sun HBA installation guide found at http://docs.sun.com/app/docs?q=StorageTek+Host+Bus+Adapter.
Installation Procedure FIGURE 8–1 System BIOS for Selecting Disk, CD-ROM, or Network Boot Device Priority 3 68 Install the Sun Solaris OS using the Solaris Interactive Installation (SunInstall). See Figure 8–2 for an example of one of several SunInstall screens.
Installation Procedure FIGURE 8–2 Selecting an FC-based Boot Disk During Disk Selection 4 During installation, select a desired array and its associated LUN. 5 Select Manual Reboot at the end of the SunInstall utility screens and then verify your selections to start the Sun Solaris OS installation. 6 Before rebooting after the installation completes, issue the luxadm display command on the boot LUN. See Figure 8–3.
Installation Procedure Host controller port WWN 210100e08b206812 Class primary State ONLINE Controller /dev/cfg/c11 Device Address 213600015d207200,0 Host controller port WWN 210100e08b30a2f2 Class primary State ONLINE FIGURE 8–3 luxadm display Command and Output The following luxadm command output from the example in the figure can be used to map the MPxIO based c#t#d# to the HBA WWN and array WWN: ■ ■ ■ 70 MPxIO c#t#d# = c0t600015d00020280000000000000001142d0 Array WWN = 213600015d207200, LUN 0 HBA
Installation Procedure 7 During the reboot process, watch the monitor so you can enter the HBA #1 BIOS screen and specify the boot device to be the FC LUN onto which you just installed the Sun Solaris OS. Follow this step for each HBA to be used for multipathing, and specify the boot device to be the FC LUN on which you installed the Sun Solaris OS. See Figure 8–4 and Figure 8–5. ■ For the QLogic HBA BIOS, perform the following steps. a.
Installation Procedure FIGURE 8–4 72 HBA BIOS Screen for an HBA WWN Solaris SAN Configuration and Multipathing Guide • April 2009
Installation Procedure FIGURE 8–5 HBA BIOS Screen for Enabling Boot From the FC LUN Note – The figure shows the following modifications: ■ ■ ■ ■ Selectable boot = Enabled ARRAY WWN = 213600015d207200 ARRAY LUN = 0 HBA WWN = 210100e08b206812 8 Repeat the appropriate modifications for all HBAs and all LUNs. 9 Type the system BIOS per the vendor’s access method and specify the boot device to be the FC LUN on which you installed the Solaris 10 Update 6 OS.
Post-Installation Patches for the Sun Solaris 10 Update 6 OS FIGURE 8–6 Example System BIOS for Enabling Booting from an FC LUN 10 Reboot to the newly installed Solaris 10 Update 6 OS using the FC LUN specified in the system BIOS.
9 C H A P T E R 9 Persistent Binding for Tape Devices To simplify management of servers in SAN-based data-centers, the Sun StorageTekTM SAN Foundation software stack in the Solaris OS dynamically detects devices in a SAN and builds associated /dev tree entries without requiring you to edit configuration files. In most cases, this process greatly simplifies SAN management.
Creating Tape Links Creating Tape Links The /etc/devlink.tab file is called the default device table file. It specifies rules that devfsadm uses to create links in the /dev directory. Type man devlinks on the command-line interface (CLI) for more information. This file does not contain any entries for tapes because devfsadm is already able to create links for tape drives, but rules can be added that will modify the default behavior for creating tape links.
Creating Tape Links ▼ 1 Configuration Steps Create the entries in /etc/devlink.tab as described in “Creating Tape Links”on page 76. If devfsadm has previously discovered the devices, you must determine the device address by running the ls -l command on the existing link. Note – Be sure to assign /dev/rmt/ N numbers to avoid conflicts with any automatically configured devices, as described above. 2 Remove existing links from /dev/rmt by running the rm /dev/rmt/* command. 3 Run devfsadm.
A A P P E N D I X A Manual Configuration for Fabric-Connected Devices This appendix explains about configuring and unconfiguring the fabric devices in the Solaris 10 OS. It explains how the visible fabric devices on a host are detected and configured with and without enabling the Sun StorageTek Traffic Manager software.
Fabric Device Node Configuration ▼ 1 To Configure Manually To enable manual configuration, make sure that the following line in the/kernel/drv/fp.conf file does not start with an initial # character: manual_configuration_only=1; Refer to the fp(7D) man page and the cfgadm_fp(1M) man page for further information on this setting. 2 Reboot the host.
Fabric Device Node Configuration Ensuring That LUN Level Information Is Visible ▼ To Ensure LUN Level Information is Visible 1 Use the cfgadm command to identify LUN level information. If you issue the cfgadm -al -o show_SCSI_LUN controller-ID command immediately after a system boots up, the output might not show the Fibre Channel Protocol (FCP) SCSI LUN level information.
Configuring Device Nodes Without Multipathing Enabled c0::50020f2300006107 disk c1 fc-private c1::220203708b69c32b disk c1::220203708ba7d832 disk c1::220203708b8d45f2 disk c1::220203708b9b20b2 disk connected connected connected connected connected connected unconfigured configured configured configured configured configured unknown unknown unknown unknown unknown unknown Note – The cfgadm -l command displays information about FC host ports.
Configuring Device Nodes Without Multipathing Enabled c0::50020f2300006107 disk c1 fc-private c1::220203708b69c32b disk c1::220203708ba7d832 disk c1::220203708b8d45f2 disk c1::220203708b9b20b2 disk 3 connected connected connected connected connected connected unconfigured configured configured configured configured configured unknown unknown unknown unknown unknown unknown Configure the fabric device. # cfgadm -c configure c0::50020f2300006077 4 Verify that the selected fabric device is configured.
Configuring Device Nodes Without Multipathing Enabled ▼ To Configure Multiple Devices Without Multipathing Make sure you first identify the devices visible to the host with the procedure “Ensuring That LUN Level Information Is Visible” on page 81. This procedure describes how to configure all unconfigured fabric devices that are attached to a fabric-connected host port. The port used as an example is c0. 1 Log in as root (su - root). 2 Identify the devices to be configured.
Configuring Device Nodes With Solaris Multipathing Software Enabled 5 Use the show_SCSI_LUN command to display FCP SCSI LUN information for multi-LUN SCSI devices. The following code example shows that the physical devices represented by c0::50020f2300006077 and c0::50020f2300006107 each have four LUNs configured. The physical devices represented by c0::50020f23000063a9 and c0::50020f2300005f24 each have two LUNs configured.
Configuring Device Nodes With Solaris Multipathing Software Enabled ▼ To Configure Individual Devices With Sun StorageTek Traffic Manager Software This sample procedure uses fabric-connected host ports c0 and c2 to configure fabric devices as multipath devices on a host that has the Sun StorageTek Traffic Manager software enabled. The cfgadm -c configure command for fabric devices is the same regardless of whether multipathing is enabled. 1 Log in as root (su - root)..
Configuring Device Nodes With Solaris Multipathing Software Enabled c1::220203708b8d45f2 c1::220203708b9b20b2 c2 c2::50020f2300005f24 c2::50020f2300006107 disk disk fc-fabric disk disk connected connected connected connected connected configured configured configured unconfigured configured unknown unknown unknown unknown unknown Notice that the Occupant column of c0 and c0::50020f2300006077 specifies configured, which indicates that the c0 port has at least one configured occupant and that the c0::50
Configuring Device Nodes With Solaris Multipathing Software Enabled 2 Identify the fabric-connected host port to be configured.
Unconfiguring Fabric Devices c2::50020f2300005f24,1 disk c2::50020f2300006107,0 disk c2::50020f2300006107,1 disk connected connected connected configured configured configured unknown unknown unknown Unconfiguring Fabric Devices This section provides information about unconfiguring the Sun StorageTek Traffic Manager software. Unconfiguring a Fabric Device Before you unconfigure a fabric device, stop all activity to the device and unmount any file systems on the fabric device.
Unconfiguring Fabric Devices c0::50020f23000063a9 disk c1 fc-private c1::220203708b69c32b disk c1::220203708ba7d832 disk connected connected connected connected configured configured configured configured unknown unknown unknown unknown ▼ To Unconfigure All Fabric Devices on a Fabric-Connected Host Port This procedure describes how to unconfigure all configured fabric devices that are attached to a fabric-connected host port. 1 Log in as root (su - root)..
Unconfiguring Fabric Devices Notice that the Occupant column of c0 and all the fabric devices attached to it are displayed as unconfigured. ▼ To Unconfigure a Fabric Device Associated With Sun StorageTek Traffic Manager Multipathing-Enabled Devices This procedure shows fabric-connected host ports c0 and c2 to illustrate how to unconfigure fabric devices associated with Sun StorageTek Traffic Manager software devices. 1 2 Log in as root (su - root)..
Unconfiguring Fabric Devices 5 Verify that the selected devices are unconfigured.
Unconfiguring Fabric Devices 3 Unconfigure the Ap_Id associated with the device. Note – If the Ap_Id represents the last configured path to the device, stop all activity to the path and unmount any file systems on it. If the multipathing device is under any volume manager’s control, see the documentation for your volume manager for maintaining the fabric device.
Unconfiguring Fabric Devices 2 Identify the devices to be unconfigured.
B A P P E N D I X B Supported FC-HBA API This appendix contains the list of supported and unsupported FC-HBA Interfaces. For further information regarding the API, refer to the Sun StorageTek Traffic Manager multipathing “Software Features” on page 16.
Supported Fibre Channel HBA API TABLE B–1 96 Supported and Unsupported FC-HBA Interfaces (Continued) FC - HBA Interfaces Supported or Not Supported by Sun StorageTek Traffic Manager Software HBA_SendCTPassThruV2 Supported HBA_RefreshInformation Supported HBA_GetFcpTargetMapping Supported HBA_SendScsiInquiry Supported HBA_SendReportLuns Supported HBA_SendReadCapacity Supported HBA_GetPortStatistics Supported HBA_ResetStatistics Not supported HBA_GetFcpPersistentBinding Not supported
Supported Fibre Channel HBA API TABLE B–1 Supported and Unsupported FC-HBA Interfaces (Continued) FC - HBA Interfaces Supported or Not Supported by Sun StorageTek Traffic Manager Software HBA_RegisterForAdapterEvents Supported HBA_RegisterForAdapterAddEvents Supported HBA_RegisterForAdapterPortEvents Supported HBA_RegisterForAdapterPortStatEvents Not supported HBA_RegisterForTargetEvents Supported HBA_RegisterForAdapterLinkEvents Not supported HBA_RegisterForAdapterTargetEvents Supported
C A P P E N D I X C Multipathing Troubleshooting This appendix provides solutions to potential problems that might occur while running the Sun StorageTek Traffic Manager software.
System Crashes During stmsboot System Crashes During stmsboot During the reboot following stmsboot enable (-e), disable (-d), or update (-u) operations, if your system hangs, panics, or fails to boot, follow the instructions below to recover your original configuration. ▼ To Recover from a System Crash 1 Boot the system from another disk, CD, DVD, or over the network. 2 Run the fsck your-root-device command where your-root-device is your original root device.
System Crashes During stmsboot 7 If the system is running on a Solaris 10 Update 4 OS (or later) x86 based system, perform the following steps: a. Restore your original /boot/solaris/bootenv.rc file. # cp /mnt/etc/mpxio/bootenv.rc /mnt/boot/solaris/bootenv.rc The /mnt/etc/mpxio/bootenv.rc file is a copy your original /boot/solaris/bootenv.rc file that the stmsboot command saved prior to updating your bootenv.rc file. A /mnt/etc/mpxio/bootenv.
Index Numbers and Symbols 24-bit FC addressing devices, 80 A ANSI standard Multipath Management API, 25-39 Ap_Id, 81 automatic failback, configuration, 51 B boot disk, 55 Booting, 16 broadcasting, 59 C cfgadm, 54 cfgadm -al -o show_SCSI_LUN, 81 cfgadm -c unconfigure, 91 cfgadm(1M), 81 cfgadm configure, 82 cfgadm_fp(1M), 85 cfgadm -c, 83 -l, 81, 82 configuration device, 81 dump, 42 fabric devices, 82 configuration (Continued) Fibre Channel overview, 21-23 manual, 79-80 multipathing, 42 SAS devices, 58 t
Index device asymmetrical, 17 configuration, 82 devices, tape, 16 device storage, 17 disabling, multipathing, 42-45 discovery dynamic, 57 SAS devices, 57 E enabling, multipathing, 42-45 F fabric-connected host ports, 81, 86 fabric device configuration, 82 fc-fabric, 86 FCAL, 16 Fibre Channel arbitrated loop, 16 booting Solaris 10 x86/x64, 65-74 configuration overview, 21-23 configuring IPFC SAN devices, 59-64 determining adapter port instances, 60-62 enabling and disabling multipathing, 42-45 HBA, 16 IPF
Index multipathing (Continued) support, 25-39 troubleshooting, 99-101 P T T10 standard, 25-39 T11 standard, 16 tape device persistent binding, 75-77 To Detect Fabric Devices Visible on a Host, 87 troubleshooting, multipathing, 99-101 per-port configuration considerations, 45-47 enabling and disabling multipathing, 45-47 persistent binding of tape devices, 75-77 physical device, 83 Promiscuous mode, 59 R REPORT LUNS command, 47 S SAS devices configuration, 58 dynamic discovery, 57 multipathing consider
