HP 3PAR Solaris Implementation Guide Abstract This implementation guide provides information for establishing communications between an HP 3PAR StoreServ Storage system and a Solaris 8, 9, 10, or 11 host running on the SPARC, x64, and x86 platforms. General information is also provided on the basic steps required to allocate storage on the HP 3PAR StoreServ Storage that can then be accessed by the Solaris host.
© Copyright 2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Introduction...............................................................................................6 Supported Configurations..........................................................................................................6 HP 3PAR OS Upgrade Considerations.........................................................................................6 Audience................................................................................................................................
Persistent Target Binding for QLogic qla Drivers......................................................................36 Persistent Target Binding for Solaris qlc and emlxs Drivers.......................................................37 System Settings for Minimizing I/O Stall Times on VLUN Paths......................................................37 6 Configuring the Host for an FCoE Connection..............................................39 Solaris Host Server Requirements..............................
Growing a VxVM Volume...................................................................................................74 VxDMP Command Examples....................................................................................................76 Displaying I/O Statistics for Paths........................................................................................76 Managing Enclosures.........................................................................................................
1 Introduction This implementation guide provides information for establishing communications between an HP 3PAR StoreServ Storage system and a Solaris 8, 9, 10, or 11 host running on the SPARC, x64, and x86 platforms. General information is also provided on the basic steps required to allocate storage on the HP 3PAR StoreServ Storage that can then be accessed by the Solaris host.
For complete details about supported host configurations and interoperability, consult the HP SPOCK website: HP SPOCK Audience This implementation guide is intended for system and storage administrators who monitor and direct system configurations and resource allocation for the HP 3PAR StoreServ Storage. The tasks described in this guide assume that the administrator is familiar with Solaris and the HP 3PAR OS.
2 Configuring the HP 3PAR StoreServ Storage for Fibre Channel This chapter explains how to establish a Fibre Channel connection between the HP 3PAR StoreServ Storage and a Solaris host and covers HP 3PAR OS 3.1.x and 2.3.x. For information on setting up the physical connection for a particular HP 3PAR StoreServ Storage, see the appropriate HP installation manual.
1. To determine whether a port has already been configured for a host port in fabric mode, issue showport -par on the HP 3PAR StoreServ Storage. 2. If the port has not been configured, take the port offline before configuring it for connection to a host server. To take the port offline, issue the HP 3PAR OS CLI command controlport offline . # controlport offline 1:5:1 3.
2. To verify that the host has been created, issue the showhost command.
Fibre Channel switch vendors support the zoning of the fabric end-devices in different zoning configurations. There are advantages and disadvantages with each zoning configuration. Choose a zoning configuration based on your needs. The HP 3PAR StoreServ Storage arrays support the following zoning configurations: • One initiator to one target per zone • One initiator to multiple targets per zone (zoning by HBA). This zoning configuration is recommended for the HP 3PAR StoreServ Storage.
The following fill-word modes are supported on a Brocade 8 G/s switch running FOS firmware 6.3.
HP 3PAR Priority Optimization The HP 3PAR Priority Optimization feature introduced in HP 3PAR OS versions 3.1.2.MU2 is a more efficient and dynamic solution for managing server workloads and can be utilized as an alternative to setting host server I/O throttles. Using this feature, a storage administrator is able to share storage resources more effectively by enforcing quality of service limits on the array.
For information regarding the Persistent Ports feature for an FCoE initiator to FC target configuration (FCoE to FC switched), see “Configuring the HP 3PAR StoreServ Storage for Fibre Channel” (page 8).
3 Configuring the HP 3PAR StoreServ Storage for an FCoE Connection This chapter explains how to establish FCoE-to-FC connectivity between the HP 3PAR StoreServ Storage and the Solaris host. At this time, the only configuration supported is an FCoE initiator on a Solaris host to an FC target on an HP 3PAR StoreServ Storage. An FCoE target is not supported by the Solaris OS.
4 Configuring the HP 3PAR StoreServ Storage for iSCSI This chapter explains how to establish an iSCSI connection between the HP 3PAR StoreServ Storage and the Solaris host. For information on setting up the physical connection, see the appropriate HP 3PAR installation manual. Configuring the HP 3PAR StoreServ Storage iSCSI Ports This section applies to configurations based on installed NICs, up to and including 10 Gb port speed. NOTE: HP 3PAR StoreServ 10000/7000 Storage supports 10 Gb iSCSI target.
NOTE: A 10 Gb iSCSI (only) requires a one-time configuration using the controlport command. Use the showport and showport -i commands to verify the configuration setting. Example: If State=config_wait or Firmware=0.0.0.0, use the controlport config iscsi command to configure. Use the showport and showport -i commands to verify the configuration setting.
NOTE: Make sure the IP switch ports, (where the HP 3PAR StoreServ Storage iSCSI target ports and iSCSI Initiators host are connected), are able to communicate with each other. If the host is already connected to the IP fabric or switch and its Ethernet interface has been configured, you can use the ping command for this purpose on the Solaris host. 3.
For information on setting up target discovery on the Solaris host, see Section (page 44). Creating an iSCSI Host Definition on an HP 3PAR StoreServ Storage Running HP 3PAR OS 3.1.x or 2.3.x NOTE: 10 Gb iSCSI is supported only on HP 3PAR OS 3.1.x and on the HP 3PAR StoreServ 10000/7000 Storage. You will need the host iqn name/names to create the iSCSI host definition on the HP 3PAR StoreServ Storage. # iscsiadm list initiator-node Initiator node name: iqn.1986-03.com.sun:01:ba7a38f0ffff.
NOTE: HP recommends host persona 2 (Generic-ALUA) for Solaris 11 and host persona 1 (Generic) for Solaris 8, 9, and 10 (all supported MU levels). Host persona 1 for Solaris 10 is required to enable Host Explorer functionality. Host persona 1 enables 3PAR Host Explorer, which requires the SESLun element of Host persona 1. Newly exported VLUNs can be seen in format by issuing devfsadm -i iscsi. To register the data VLUN 254 on Solaris format, a host reboot is required.
NOTE: The CHAP secret length must be between 12 and 16 characters. The following example sets host_secret0 as the host secret key. # sethost initchap -f host_secret0 solarisiscsi b. Verify the host CHAP secret. # showhost -chap Id Name -Initiator_CHAP_Name- -Target_CHAP_Name1 solarisiscsi solarisiscsi - c. Set the secret key host_secret0 on the host. NOTE: The secret key used at the HP 3PAR StoreServ Storage should match on the host.
f. Create a new iSCSI connection session. Example: If you are using SendTargets as a discovery method, remove and add back the discovery address to create a new connection session. # iscsiadm remove discovery-address 11.1.0.110:3260 # iscsiadm add discovery-address 11.1.0.110:3260 Or to apply for all connected targets: # iscsiadm modify discovery --sendtargets disable # iscsiadm modify discovery --sendtargets enable g. Invoke devfsadm to discover the devices after the host is verified by the target.
Initial Ready To Transfer (R2T): yes/Max Burst Length: 262144/Max Outstanding R2T: 1/Max Receive Data Segment Length: 8192/Max Connections: 1/Header Digest: NONE/NONE Data Digest: NONE/NONE Configured Sessions: 1 Target: iqn.2000-05.com.
NOTE: The Target Chap name is set by default to the HP 3PAR StoreServ Storage name. Use the HP 3PAR OS CLI showsys command to determine the HP 3PAR StoreServ Storage name. 2. Enter the Host Chap secret key host_secret0 on the host. # iscsiadm modify initiator-node --CHAP-secret 3. Enable the Host CHAP authentication after the secret key is set. # iscsiadm modify initiator-node --authentication CHAP 4. Enable target or bidirectional authentication for each connected target port.
- # iscsiadm list target-param -v Target: iqn.2000-05.com.3pardata:20310002ac00003e Alias: Bi-directional Authentication: enabled Authentication Type: CHAP CHAP Name: -S062 Login Parameters (Default/Configured): 9. Remove and create a new iSCSI session and invoke devfsadm -i iscsi to discover the targets and all the LUNs. NOTE: CHAP authentication will not be in effect for the most recently added devices until the current connection is removed and a new connection session is enabled.
Target Port Limits and Specifications To avoid overwhelming a target port and ensure continuous I/O operations, observe the following limitations on a target port: • I/O queue depth on each HP 3PAR StoreServ Storage HBA model, as follows: ◦ QLogic 1G: 512 (HP 3PAR T-Class and HP 3PAR F-Class) ◦ QLogic 10G: 2048 (HP 3PAR StoreServ 10000 and HP 3PAR StoreServ 7000 systems only) • The I/O queues are shared among the connected host server HBA ports on a first-come, first-served basis.
HP Support Center • the HP 3PAR Command Line Interface Administrator’s Manual, “Using Persistent Ports for Nondisruptive Online Software Upgrades” This document is available on the following HP SC website: HP Support Center iSCSI Starting with HP 3PAR OS 3.1.3, the HP 3PAR OS Persistent Ports feature is supported for iSCSI. The HP 3PAR OS Persistent Ports feature is enabled by default for HP 3PAR StoreServ Storage iSCSI ports during node-down events.
5 Configuring the Host for a Fibre Channel Connection This chapter describes the procedures that are required to set up a Solaris host to communicate with an HP 3PAR StoreServ Storage over a Fibre Channel connection using a supported HBA. Installing the HBA Before setting up the Solaris host, make sure the host adapters are installed and operating properly. If necessary, consult the documentation provided by the HBA vendor.
NOTE: The SAN package may have an updated release of the emlxs /qlc drivers (also known as the Leadville drivers). See the HP SPOCK website: HP SPOCK Installation Notes for Emulex lpfc Drivers The following notes apply when connecting to a Solaris host that utilizes an Emulex HBA with an lpfc driver: The default or as installed parameter settings will allow the host to connect in either direct or fabric modes. Direct Connect Configured by editing /kernel/drv/lpfc.
NOTE: Emulex lpfc drivers 6.20 and above do not require LUN and Target entries in the /kernel/drv/sd.conf file. The lpfc driver can support up to 256 targets, with a maximum of 256 LUNs per target; additional LUNs will not be visible on the host. Solaris 8/9 LUN discovery for driver 6.21g requires the following command: /opt/HBAnyware/hbacmd RescanLuns HBAnyware software is available from the Emulex lpfc driver download site: Emulex NOTE: When adding specific entries in the sd.
WARNING! Any changes to the driver configuration file must be tested before going into a production environment. WARNING! DO NOT LOWER the qla2300.conf variable hba0-link-down-timeout below 30 seconds for Solaris 9 hosts. Installation Notes for Solaris qlc and emlxs Drivers The following notes apply when connecting to a Solaris host that utilizes a QLogic or Emulex HBA and relies on the qlc or emlxs drivers supplied as part of the Solaris SAN installation.
Using Symantec Veritas Storage Foundation VxDMP Multipathing As an option, you can use VxDMP for multipath load balancing and failover. Install a supported version of Symantec Veritas Storage Foundation VxVM/VxDMP using the Installation and Administrator's guides.
3pardata4_5878 If the virtual volumes in use report a 16-byte WWN, the ASL extracts an AVID number of 0 for all VVs, and Symantec sequentially enumerates the DMP devices to generate a unique DMP disk name. In this case, the resulting disk names would be: 3pardata4_0 3pardata4_0_1 3pardata4_0_2 The name scheme used does not impact DMP functionality. However, if you want the DMP name to contain the VV AVID number, Symantec provides updated ASLs that will properly extract the AVID number.
WARNING! Failure to claim the HP 3PAR StoreServ Storage as an HP 3PAR array will affect the way devices are discovered by the multipathing layer. WARNING! The minimum supported software installation version for VxDMP_5.0MP3 is VxDMP_5.0MP3_RP1_HF3 with vxdmpadm settune dmp_fast_recovery=off. This tunable can be left at default values with later versions VxDMP_5.0MP3_RP2_HF1 and VxDMP_5.0MP3_RP3.
Oracle Enabling SSTM/MPxIO Multipathing for Solaris 8 and 9 To enable SSTM globally for all HBAs in the system, edit the /kernel/drv/scsi_vhci.conf file by changing the mpxio-disable parameter to a value of no. mpxio-disable="no"; This step requires a host reboot. For detailed installation instructions, consult the Solaris Fiber Channel and Storage Multipathing Administration Guide.
However, in configurations where multiple HP 3PAR StoreServ Storage ports are available for discovery, some specific target binding may be necessary. The following section describes considerations for implementing persistent binding for each type of HBA that is supported by the Solaris OS. Persistent Target Binding for Emulex lpfc Drivers By having the automap parameter set to a value of 1 and the fcp-bind-method set to a value of 2 in the /kernel/drv/lpfc.
non-binded devices hba0-persistent-binding-by-port-ID=0; # Persistent binding by FC port ID disabled The current HBA driver instance matching to discovered target WWPN associations (for connected devices) can be obtained from entries in the /var/adm/messages file generated from the last server boot. # grep fibre-channel-port /var/adm/messages sunb1k-01 qla2300: [ID 558211 kern.info] hba0-SCSI-target-id-0-fibre-channel-portname="20310002ac000040"; sunb1k-01 qla2300: [ID 558211 kern.
NOTE: This section does not apply to Solaris 11. There is a delay of fp_offline_ticker before fp tells fcp about the link outage (default 90 seconds). There is a further delay of fcp_offline_delay before fcp offlines LUNs (default 20 seconds). You can change these setting by making the necessary edits to the /kernel/drv/ fcp.conf and /kernel/drv/fp.conf files. For example, you could edit the fcp.
6 Configuring the Host for an FCoE Connection This chapter describes the procedures that are required to set up a Solaris host to communicate with an HP 3PAR StoreServ Storage over an FCoE initiator on the Solaris host to an FC target on the HP 3PAR StoreServ Storage.
To configure a CNA and an FCoE Forwarder switch, follow these guidelines: NOTE: For complete and detailed instructions for configuring a server with a given CNA, see the CNA manufacturer documentation. The FCoE switch or FCoE forwarder must be able to convert FCoE traffic to FC and also be able to trunk this traffic to the fabric that the HP 3PAR StoreServ a Storage target ports are connected to. FCoE switch VLANs and routing setup and configuration are beyond the scope of this document.
7 Configuring the Host for an iSCSI Connection This chapter describes the procedures that are required to set up a Solaris host to communicate with an HP 3PAR StoreServ Storage over a 1 Gb or 10 Gb NIC iSCSI connection. Solaris Host Server Requirements To use an iSCSI connection, the Solaris host must meet the following software requirements.
5 executables 1005 blocks used (approx) # modinfo | grep iscsi 104 7bee0000 2b7e8 96 1 iscsi (Sun iSCSI Initiator v20071207-0) Setting Up the Ethernet Switch 1. 2. Connect the Solaris (iSCSI Initiator) host’s CAT5/Fiber cables and the HP 3PAR StoreServ Storage iSCSI target port's CAT5/Fiber cables to the Ethernet switches.
inet 10.112.2.174 netmask ffffc000 broadcast 10.112.63.255 ether 0:23:8b:f3:d2:20 net2: flags=1000843 mtu 9000 index 4 inet 10.100.11.3 netmask ffffff00 broadcast 10.100.11.255 ether 0:0:c9:bb:cc:b5 net3: flags=1000843 mtu 9000 index 4 inet 10.100.12.3 netmask ffffff00 broadcast 10.100.12.255 ether 0:0:c9:bb:cc:b6 lo0: flags=2002000849 mtu 8252 index 1 inet6 ::1/128 4.
2. Check that the iSCSI interfaces are created and configured correctly. # ifconfig -al o0: flags=2001000849mtu 8232 index 1 inet 127.0.0.1 netnask ff000000 bge0: flags=1000843 mtu 1500 index 2 inet 192.168.10.205 netmask ffffff00 broadcast 192.168.10.255 ether 0:14:4f:b0:53:4c bge1: flags-1000843 mtu 1500 index 3 inet 10.105.1.10 netmask ffffff00 broadcast 10.106.1.
The HP 3PAR StoreServ Storage supports all of the above discovery methods. For details on iSCSI initiator configuration, see the System Administration Guide: Devices and File Systems and refer to the chapter “Solaris iSCSI Initiators (Tasks),” available on the following website: Oracle CAUTION: Configuring both static and dynamic device discovery for a given target is not recommended since it can cause problems communicating with the iSCSI target device.
3. Enable the SendTargets discovery method. # iscsiadm modify discovery --sendtargets enable 4. Verify that the SendTargets discovery is enabled. # iscsiadm list discovery Discovery: Static: disabled Send Targets: enabled iSNS: disabled Using the iSNS Discovery Method The following example shows how to configure the Solaris host for an HP 3PAR StoreServ Storage target port using the iSNS discovery method.
automatically discover the target without the need to issue devfsadm. However, if any change is made in the target discovery address or method, a devfsadm command must be issued to reconfigure the altered discovery address. 2. Verify the discovered targets. # iscsiadm list target Target: iqn.2000-05.com.3pardata:21310002ac00003e Alias: TPGT: 131 ISID: 4000002a0000 Connections: 1 3.
--Login Parameters (Negotiated): --Max Receive Data Segment Length: 65536 --- 4. Issue the iscsiadm list target -v command to list all the negotiated login parameters: # iscsiadm list target -v Target: iqn.2000-05.com.3pardata:21310002ac00003e Alias: TPGT: 1 ISID: 4000002a0000 Connections: 1 CID: 0 IP address (Local): 11.1.0.40:33672 IP address (Peer): 11.1.0.
1. For Solaris 10 only, edit the /kernel/drv/scsi_vhci.conf file and add the following entry to enable Solaris I/O multipathing globally on all the HP 3PAR StoreServ Storage target ports: device-type-scsi-options-list = "3PARdataVV", "symmetric-option", "3PARdataSES", "symmetric-option"; symmetric-option = 0x1000000; 2. For Solaris 10 and 11, make sure that multipathing is enabled in the iSCSI configuration file /kernel/drv/iscsi.
8 Allocating Storage for Access by the Solaris Host This chapter describes the basic procedures that are required to create and export virtual volumes so they can be utilized by the Solaris host and provides specific details for various connection configurations. For complete details on creating and managing storage on the HP 3PAR StoreServ Storage, consult the appropriate HP 3PAR documentation.
Consult the HP 3PAR Management Console User’s Guide and the HP 3PAR Command Line Interface Reference for complete details on creating volumes for the HP 3PAR OS version that is being used on the HP 3PAR StoreServ Storage. These documents are available on the HP SC website: HP Support Center NOTE: The commands and options available for creating a virtual volume may vary for earlier versions of the HP 3PAR OS.
Consult the HP 3PAR Management Console User’s Guide and the HP 3PAR Command Line Interface Reference for complete details on exporting volumes and available options for the HP 3PAR OS version that is being used on the HP 3PAR StoreServ Storage. These documents are available on the HP SC website: HP Support Center NOTE: The commands and options available for creating a virtual volume may vary for earlier versions of the HP 3PAR OS.
For configurations that use Veritas Volume Manager for multipathing, virtual volumes should be exported down multiple paths to the host server simultaneously. To do this, create a host definition on the HP 3PAR StoreServ Storage that includes the WWNs of multiple HBA ports on the host server. NOTE: All I/O to an HP 3PAR StoreServ Storage port should be stopped before running any HP 3PAR OS CLI controlport commands on that port.
HP 3PAR StoreServ Storage volume serial number (VV_WWN). LUN number 50 was used for the first time to present a device. # showvv -d Id Name Rd Mstr Prnt Roch Rwch PPrnt PBlkRemain -----VV_WWN--- -----CreationTime---10 demo.50 RW 1/2/3 --- --- --- --- - 50002AC01188003E Fri Aug 18 10:22:57 PDT 2006 20 checkvol RW 1/2/3 --- --- --- --- - 50002AC011A8003E Fri Aug 18 10:22:57 PDT 2006 # showvlun -t Lun VVname Host ------------Host_WWN/iSCSI_Name------------- Port Type 50 demo.
New VLUNs that are exported while the Solaris host is running will not be registered on the host until the following host command is issued on a Solaris 8, 9 Host: # devfsadm -i sd Before they can be used, newly-discovered VLUNs need to be labeled using the Solaris format or format -e command. Discovering LUNs for Solaris qlc and emlxs Drivers In direct-connect mode, new VLUNs that are exported while the Solaris host is running will be discovered automatically.
NOTE: The HP 3PAR StoreServ Storage targets appear with their World Wide Port Names associated with the C number of the host HBA port they are logically connected to. The host server port WWNs will now appear on the HP 3PAR StoreServ Storage in the output of the showhost command. NOTE: The configuration will fail for visible targets that do not present any LUNs. At least one VLUN must be exported from each HP 3PAR StoreServ Storage port before its associated host port is configured.
in the output of cfgadm for an HP 3PAR StoreServ Storage port that has no VVs exported from it.
Discovering LUNs for Veritas Volume Manager’s DMP (VxDMP) If you are using the Veritas Volume Manager's DMP driver, make the newly registered and labeled VLUNs visible to the DMP layer by issuing the following command: # vxdctl enable After issuing this command, the volume can be admitted to and used by Veritas Volume Manager. Discovering LUNs on iSCSI Connections To discover new LUNs, issue the Solaris devfsadm -i iscsi command on the host.
Product: VV OS Device Name: /dev/rdsk/c5t50002AC010A7003Ed0s2 The iscsiadm command can be used to remove and modify targets and their parameters, as in the following examples: # iscsiadm remove discovery-address 10.106.2.12:3260 # iscsiadm modify initiator-node -d CRC32 Removing Volumes for Fibre Channel Connections After removing the VLUN exported from the HP 3PAR StoreServ Storage, the VLUN removal from the Solaris host is performed in different ways depending on the HBA driver and the OS version.
/scsi_vhci/ssd@g50002ac007f100af 4. c5t5000c5000AC007F200AFd0 <3PARdata-VV-0000 cyl 4309 alt 2 hd 8 sec 304> /scsi_vhci/ssd@g50002ac007f200af 5. c5t5000c5000AC007F300AFd0 <3PARdata-VV-0000 cyl 4309 alt 2 hd 8 sec 304> /scsi_vhci/ssd@g50002ac007f300af 6. c5t5000c5000AC007F400AFd0 <3PARdata-VV-0000 cyl 4309 alt 2 hd 8 sec 304> /scsi_vhci/ssd@g50002ac007f400af 7. c5t5000c5000AC007F500AFd0 /scsi_vhci/ssd@g50002ac007f500af 8.
9 Using the Solaris Cluster Server For Solaris 10, a Solaris MPXIO patch is required that contains MPXIO fixes applicable for SCSI3 reservations in a if Solaris Cluster configuration. For SPARC-based servers, use patch 127127-11 and for x86 based servers use patch 127128-11.
10 Using the Veritas Cluster Server There are no specific settings required on the HP 3PAR array to work with Veritas Cluster server. For further information, see the Veritas documentation, which can be found on the following website: Symantec NOTE: 62 It is recommended that I/O Fencing be enabled.
11 Booting from the HP 3PAR StoreServ Storage This chapter describes the procedures that are required to boot the Solaris OS from the SAN. Preparing a Bootable Solaris Image for Fibre Channel There are two methods for installing the Solaris boot image on a Fibre Channel storage device attached externally using Solaris HBAs and drivers, as described in the following sections.
3. 4. 5. Create the host definition on the HP 3PAR StoreServ Storage, which represents the host server's HBA port WWN. Export the VLUN to the host server using any LUN number. Prepare a Solaris OS install server on the same network as the host server, or use the Solaris OS CD install media. NOTE: For a Solaris 8 and 9 install image, the required Solaris StorEdge SAN software must also be added to the install server boot image. 6.
NOTE: If multiple paths to the LUNs have been used, the LUN appears as multiple instances in the install program 8. Restart the Solaris interactive installation program. NOTE: Continue the Solaris installation with appropriate responses, including selecting the HP 3PAR StoreServ Storage LUN as an install target. A LUN will appear as multiple instances if multiple paths have been used. Select one instance for the Solaris OS installation.
5. Edit the /kernel/drv/scsi_vhci.conf file to register the HP 3PAR devices. # # mpxio-disable="no";# for solaris 8 & 9 # symmetric-option = 0x1000000; device-type-scsi-options-list = "3PARdataVV", "symmetric-option"; symmetric-option = 0x1000000; "3PARdataSES", "symmetric-option"; 6. Use the Solaris stmsboot command to enable multipathing for the boot device. The host server will be rebooted when stmsboot –e is run. # stmsboot -e WARNING: This operation will require a reboot.
The hardware path for the second path must be derived and passed to OpenBoot when the host server needs to boot from the second path. The second path can be deduced and constructed using the information from the Solaris luxadm display command: # luxadm display /dev/rdsk/c7t50002AC000300040d0s2 DEVICE PROPERTIES for disk: /dev/rdsk/c7t50002AC000300040d0s2 . . .
x86 The ability to boot from either path is configured in the BIOS by adding the paths to the boot priority. NOTE: The host server in use should be updated to the newest version of OpenBoot available from Oracle and tested for booting under failed path scenarios.
(Note the space after the first double-quote.) ok set-sfs-boot ok reset-all ok show-devs The lpfc@1 path should now be emlx@1. Repeat for the other path: ok " /pci@1c,600000/lpfc@1,1" select-dev ok set-sfs-boot ok reset-all ok show-devs ok setenv auto-boot? true 8. Create the boot aliases for the boot VLUN.
12 Configuration Examples This chapter provides sample configurations used successfully for HP testing purposes. Example of Discovering a VLUN Using qlc/emlx Drivers with SSTM The following example shows how to discover a VLUN on a Solaris 9 host that is using the qlc and emlxs drivers and SSTM over a direct Fibre Channel connection. 1. Make sure the host is in a clean state before you start. # # # # 2. cfgadm -o show_FCP_dev -al luxadm probe devfsadm -Cv format Export a VLUN to the host.
HBACMD_RescanLuns: Success # ./hbacmd RescanLuns 10:00:00:00:C9:7B:C5:D6 21:53:00:02:AC:00:00:AF HBACMD_RescanLuns: Success # ./hbacmd RescanLuns 10:00:00:00:C9:7B:C5:D6 20:52:00:02:AC:00:00:AF HBACMD_RescanLuns: Success # .
# zfs create /name_2> # cd /name>/ You create file systems with the newfs command. The newfs command accepts only logical raw device names. The syntax is as follows: # newfs [ -v ] [ mkfs-options ] raw-special-device For example, to create a file system on the disk slice c0t3d0s4, you would use the following command: # newfs -v /dev/rdsk/c0t3d0s4 The -v option prints the actions in verbose mode. The newfs command calls the mkfs command to create a file system.
Label the LUN: format> label 4. Create and mount the file system. For example: # newfs /dev/rdsk/c2t50002AC000010032d0s2 # mkdir /mnt/test # mount /dev/dsk/c2t50002AC000010032d0s2 /mnt/test 5. Grow the LUN: On the HP 3PAR StoreServ Storage, use the growvv command to grow the LUN. Increase the LUN by 10 GB (for example): # growvv 10G 6. 7. Rescan the device tree on the host as shown above. Use the luxadm command to verify the new LUN size.
Check the new size: # df -k /mnt/test Summary: • Create and export the initial LUN • Scan the device tree on the host • Run 'format' to configure the LUN (set type and label) • Create and mount the file system on the host • Grow the LUN on the HP 3PAR StoreServ Storage • Rescan the device tree on the host • Unmount the file system on the host • Run 'format' to reconfigure the LUN (set type and label) • Mount and grow the file system Growing a VxVM Volume The vxdisk resize command can upda
3. Create a Veritas disk group with the two LUNs: # vxdisk list # vxdg init = # vxdg -g adddisk = ('vxdiskadm' can also be used.) If you cannot initialize the LUNs, check the paths are enabled: # vxdisk path Create a VxVM volume and mount it: # # # # 4.
• Rescan the device tree on the host. • Grow the file system. VxDMP Command Examples This section provides information on some common commands used to configure VxDMP. For detailed information on Veritas SF and configuration, see the following website: Symantec CAUTION: Commands may vary with each version of Veritas Storage foundation. Always refer to the version release notes.
Check current I/O policy attributes: # vxdmpadm getattr enclosure iopolicy=policy Here are some policies that can be set: adaptive – automatically determin
To display paths connected to a LUN, use the vxdmpadm(1m) utility with the getsubpaths option: # vxdmpadm getsubpaths dmpnodename=node_name Here is an example: # vxdmpadm getsubpaths dmpnodename=c2t21d36 NAME STATE PATH-TYPE CTLR-NAME ENCLR-TYPE ENCLR-NAME ============================================================================= c2t21d36s2 ENABLED c2 3PARdata 3pardata0 c2t23d36s2 ENABLED c2 3PARdata 3pardata0 c3t20d36s2 DISABLED c3 3PARdata 3pardata0 c3t22d36s2 DISABLED c3 3PARdata 3pardata0 To displa
13 Patch/Package Information This appendix provides minimum patch requirements for various versions of Solaris and other associated drivers. Minimum Patch Requirements for Solaris Versions The following tables list the minimum patch requirements based on the Solaris version. Table 3 Solaris 10 MU Minimum Patch Requirements SPARC x86 11.1 SPARC 11.1 x86 Patches included in OS release Patches included in OS release 11.0 SPARC 11.
Table 3 Solaris 10 MU Minimum Patch Requirements (continued) 80 SPARC x86 MU6 SPARC 10/2008 MU6 x86 10/2008 127127-11 127128-11 120222-31 (-29 has an issue) 120223-31 (-29 has an issue) 118833-36 118855-36 119130-33 also 125166-07 (qlc) 119131-33 also 125165-07 (qlc) MU7 SPARC 5/2009 MU7 x86 5/2009 127127-11 127128-11 139608-02 (emlxs) 139609-02 (emlxs) 118833-36 118855-36 139606-01 (qlc) 139607-01 (qlc) MU8 SPARC 10/2009 MU8 x86 10/2009 127127-11 127128-11 141876-05 (emlxs) 141
For the Emulex OCe10102 CNA card, the following minimum patch revisions are required (MU9): 145098-04 (emlxs) 145099-04 (emlxs) For the QLogic QLE8142 CNA card, the following minimum patch revisions are required (MU9): 143957-05 (qlc) 144486-05 (qlc) 143958-05 (qlc) 144487-05 (qlc) Table 4 Solaris 9 Minimum Patch Requirements Patch Comment 118558-06 113277-01 Table 5 Solaris 8 Minimum Patch Requirements Patch Comment 108974-02 NOTE: Always install a SAN package with additions.
WARNING! The SAN version "additions" above are required at a minimum. HBA Driver/DMP Combinations Table 8 (page 82) lists Supported HBA driver and DMP combinations.
x86 Platform • 120223-27 was the minimum; now 144189-02 emlxs on Sol10 Default MU level Leadville Driver Table Table 9 (page 83) shows the version and package number for the applicable Leadville driver. Table 9 Leadville Driver Version and Package Solaris OS Version Leadville Driver Released MU Driver Level (Oracle patch) Solaris 10 SPARC MU11 (1/13) qlc 20120717-4.01 (patch: 149175-02) emlxs 2.80.8.0 (patch: 149173-03) qlc 20120717-4.01 (patch: 149176-02) emlxs 2.80.8.
Table 9 Leadville Driver Version and Package (continued) Solaris OS Version Leadville Driver Released MU Driver Level (Oracle patch) Replace 2.31h—with patch 120222-31 emlxs 2.31p (patches: 120222-31) (not default driver) Solaris 10 x86 MU6 (10/08) qlc 2.29 v20080617-2.29 (patches: 125165-12) emlxs 2.31h v20080616-2.31h (patches: 120223-29) qlc 2.26 v20071220-2.26 (patches: 125166-10) emlxs 2.30h v20080116-2.30h (patches:120222-26) qlc 2.26 v20071220-2.26 (patches: 125165-10) emlxs 2.
14 Support and Other Resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
For information about: See: Migrating data from one HP 3PAR storage system to another HP 3PAR-to-3PAR Storage Peer Motion Guide 86 Configuring the Secure Service Custodian server in order to monitor and control HP 3PAR storage systems HP 3PAR Secure Service Custodian Configuration Utility Reference Using the CLI to configure and manage HP 3PAR Remote Copy HP 3PAR Remote Copy Software User’s Guide Updating HP 3PAR operating systems HP 3PAR Upgrade Pre-Planning Guide Identifying storage system compo
For information about: See: Planning for HP 3PAR storage system setup Hardware specifications, installation considerations, power requirements, networking options, and cabling information for HP 3PAR storage systems HP 3PAR 7200, 7400, and 7450 storage systems HP 3PAR StoreServ 7000 Storage Site Planning Manual HP 3PAR StoreServ 7450 Storage Site Planning Manual HP 3PAR 10000 storage systems HP 3PAR StoreServ 10000 Storage Physical Planning Manual HP 3PAR StoreServ 10000 Storage Third-Party Rack Physic
Typographic conventions Table 10 Document conventions Convention Element Bold text • Keys that you press • Text you typed into a GUI element, such as a text box • GUI elements that you click or select, such as menu items, buttons, and so on Monospace text • File and directory names • System output • Code • Commands, their arguments, and argument values • Code variables • Command variables Bold monospace text • Commands you enter into a command line interface • Syste
15 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
