HP 3PAR Red Hat Enterprise Linux and Oracle Linux Implementation Guide Abstract This implementation guide provides the information you need to configure an HP 3PAR StoreServ Storage with Red Hat Enterprise Linux (RHEL) 4, RHEL 5, RHEL 6, and Oracle Linux (OL). 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 RHEL 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...............................................................................................7 Supported Configurations..........................................................................................................7 HP 3PAR OS Upgrade Considerations.........................................................................................8 Audience................................................................................................................................
Configuring the QLogic HBA Using the SCLI Utility.................................................................41 Installing the Brocade HBA......................................................................................................42 Building the Brocade Driver.................................................................................................42 Setting up the NVRAM and BIOS with the Brocade HBA.........................................................
Building the Broadcom Driver..............................................................................................97 Initializing and Configuring Broadcom FCoE.........................................................................97 Configuring RHEL 6 FCoE Settings with Device-mapper Multipathing.............................................99 8 Allocating Storage for Access by the RHEL Host..........................................103 Creating Storage on the HP 3PAR StoreServ Storage.............
Typographic conventions.......................................................................................................143 HP 3PAR branding information...............................................................................................143 18 Documentation feedback.......................................................................
1 Introduction This implementation guide provides the information you need to configure an HP 3PAR StoreServ Storage with Red Hat Enterprise Linux (RHEL) 4, RHEL 5, RHEL 6, and Oracle Linux (OL). 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 RHEL host. NOTE: All references to RHEL also apply to Oracle Linux unless stated otherwise.
Table 2 HP 3PAR Storage Products (continued) Product See...
2 Configuring the HP 3PAR StoreServ Storage for Fibre Channel This chapter describes how to establish a connection between an HP 3PAR StoreServ Storage and an RHEL host using Fibre Channel and how to set up the fabric when running HP 3PAR OS 3.1.x, OS 2.3.x, or OS 2.2.x. For information on setting up the physical connection for a particular HP 3PAR StoreServ Storage, see the appropriate HP 3PAR installation manual.
2. After all ports have been configured, verify that the ports are configured for a host in a direct connection by issuing the showport -par command on the HP 3PAR StoreServ Storage.
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. To take the port offline, issue the HP 3PAR OS CLI command controlport offline . # controlport offline 1:5:1 3.
RHEL uses the generic host persona of 1 (UARepLun,SESLun) for HP 3PAR OS 3.1.2, 3.1.1, or earlier. Beginning with 3PAR OS 3.1.3, HP recommends using host persona 2 (UARepLUN, SESLun, ALUA). 1. To create host definitions, issue the createhost [options] [...] command. For example: # createhost -persona 1 redhathost 1122334455667788 1122334455667799 NOTE: Changing an existing host persona from 1 to 2 is an offline process that requires a host reboot for the changes to take effect.
Required The following setup must be completed before connecting the HP 3PAR StoreServ Storage port to a device. Configuring Ports for a Direct Connection To configure the HP 3PAR StoreServ Storage ports for a direct connection, complete the following steps. 1. Set each HP 3PAR StoreServ Storage port to port persona 1 by issuing controlport persona 1 , where is the port location, expressed as node:slot:port. 2. Issue controlport vcn disable -f . 3.
2. To verify the host definition, issue the showhost command. For example: # showhost 2 redhathost 1122334455667788 4:0:1 1122334455667799 5:0:1 Connecting the HP 3PAR StoreServ Storage to the Host During this stage, connect the HP 3PAR StoreServ Storage to the host directly or to the fabric. This set of tasks includes physically cabling the HP 3PAR StoreServ Storage to the host or fabric.
For more information about using one initiator to multiple targets per zone, see Zoning by HBA in the Best Practices chapter of the HP SAN Design Reference Guide. This document is available on the HP SC website: HP SAN Design Reference Guide If you use an unsupported zoning configuration and an issue occurs, HP may require that you implement one of the supported zoning configurations as part of the troubleshooting or corrective action.
In addition, some HP switches, such as the HP SN8000B 8-slot SAN backbone director switch, the HP SN8000B 4-slot SAN director switch, the HP SN6000B 16 Gb FC switch, or the HP SN3000B 16 Gb FC switch automatically select the proper fill-word mode 3 as the default setting. • McDATA switch or director ports should be in their default modes as G or GX-port (depending on the switch model), with their speed setting permitting them to autonegotiate.
arrays, see the HP 3PAR Priority Optimization technical whitepaper, which is available on the HP SC website: HP 3PAR Priority Optimization HP 3PAR OS Persistent Ports The HP 3PAR OS Persistent Ports (or virtual ports) feature minimizes I/O disruption during an HP 3PAR StoreServ Storage online upgrade or node-down event (online upgrade, node reboot, or cable pull test). Port shutdown or reset events do not trigger this feature.
Figure 1 Initiator FCoE to FC Target NOTE: For Figure 1 (page 18), the FCoE switch must be able to convert FCoE traffic to FC and must also be able to trunk this traffic to the fabric that the HP 3PAR StoreServ Storage target ports are connected to. FCoE switch VLANs and routing setup and configuration are beyond the scope of this implementation guide. Consult your switch manufacturer's documentation for instructions of how to set up VLANs and routing.
Figure 2 Initiator FCoE to Target FCoE FCoE-to-FC Connectivity 19
3 Configuring the HP 3PAR StoreServ Storage for iSCSI Configuring Ports for an iSCSI Connection To configure an iSCSI target port on the HP 3PAR StoreServ Storage for connection to an iSCSI Initiator, complete the following steps: NOTE: The method for configuring software iSCSI on the HP 3PAR StoreServ Storage is the same as for configuring hardware iSCSI. 1. 10 Gb iSCSI ports on HP 3PAR StoreServ 10000 and HP 3PAR StoreServ 7000 arrays require a one-time configuration using the controlport command.
4. Set up the IP address and netmask address of the iSCSI target ports by issuing controliscsiport addr [-f] . # controliscsiport addr 10.100.0.101 255.255.0.0 -f 0:3:1 # controliscsiport addr 10.101.0.201 255.255.0.0 -f 1:3:1 5. Verify the changed settings by issuing showport -iscsi. NOTE: Make sure that VLAN connectivity is working properly. See “Setting Up the Switch and iSCSI Initiator” (page 57) 6.
To set up a hardware iSCSI host definition, see “Setting Up Hardware iSCSI for RHEL 6 or RHEL 5” (page 60). NOTE: If multiple initiator ports are used, add the following to /etc/sysctl.conf: net.ipv4.conf.all.arp_filter = 1 NOTE: To be able to establish an iSCSI Initiator connection/session with the iSCSI target port from the host, you must create a host definition entry, create the iSCSI host definition, and configure the HP 3PAR StoreServ Storage iSCSI target port(s).
Use the qaucli command to find the MAC address for the 10 Gb CNA, followed by assigning an IP address to the 10 Gb NIC port. 2. You can verify that the iSCSI Initiator is connected to the iSCSI target port by using the HP 3PAR OS CLI showhost command. # showhost Id Name -- Persona ----------WWN/iSCSI_Name----------- Port iqn.1994-05.com.redhat:a3df53b0a32d 0:3:1 iqn.1994-05.com.
Example for an HP 3PAR array running HP 3PAR OS 2.3.x or OS 3.1.2 or earlier: NOTE: For an HP 3PAR StoreServ Storage system running HP 3PAR OS 2.2.x, the output of showhost appears differently, since there are no Persona fields. Example of showhost output for an HP 3PAR StoreServ Storage system running HP 3PAR OS 2.2.x: # showhost Id Name -----------WWN/iSCSI_Name------------ Port 0 linux iqn.1994-05.com.redhat:a3df53b0a32d 0:3:1 iqn.1994-05.com.
• Remove iSCSI node: • Remove iSCSI targets: # iscsiadm -m discovery -o delete -p 10.0.0.10 • Display iSCSI node configuration: # iscsiadm -m node -T iqn.2000-05.com.3pardata:21110002ac0001a6 -p 10.0.0.20:3260 • Show all records in discovery database: # iscsiadm -m discovery • Show discovery record setting: # iscsiadm -m discovery -p 10.0.0.
Target Port Limits and Specifications for iSCSI 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 ◦ QLogic 10G: 2048 (HP 3PAR StoreServ 10000 and HP 3PAR StoreServ 7000 systems only) • The I/O queues are shared among the connected host 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 HP 3PAR OS Persistent Ports Setup and Connectivity Guidelines for iSCSI Starting with HP 3PAR OS 3.1.3, the HP 3PAR OS Persistent Ports feature is supported for iSCSI.
4 Configuring the HP 3PAR StoreServ Storage for FCoE Setting Up the FCoE Switch, FCoE Initiator, and FCoE target ports Connect the Linux host FCoE initiator port(s) and the HP 3PAR StoreServ Storage FCoE target ports to the FCoE switch(es). NOTE: FCoE switch VLANs and routing setup and configuration is beyond the scope of this document. Consult your switch manufacturer's documentation for instructions of how to set up VLANs and routing. 1.
NOTE: If changing the config from iSCSI to FCoE, follow the steps below. 1. Issue the showportcommand. # showport 0:3:1 target 0:3:2 target 2. ready ready - 000E1E05BEE6 iscsi 000E1E05BEE2 iscsi iSCSI iSCSI - - - Turn off the iSCSI ports: # controlport offline 0:3:1 # controlport offline 0:3:2 showport 0:3:1 target offline - 000E1E05BEE2 iscsi iSCSI0:3:2 target offline 000E1E05BEE2 iscsi iSCSI 3.
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 CNA: 1748 (HP 3PAR StoreServ 10000 and HP 3PAR StoreServ 7000 systems only) • The I/O queues are shared among the connected host HBA ports on a first-come, first-served basis.
For a more complete description of the HP 3PAR OS Persistent Ports feature, its operation, and a complete list of required setup and connectivity guidelines, see: • the HP Technical white paper HP 3PAR StoreServ Persistent Ports (HP document #F4AA4-4545ENW) This document is available on the following HP SC website: 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 H
5 Configuring a Host with Fibre Channel This chapter describes the tasks necessary for connecting the host to Fibre Channel. NOTE: For RHEL 6.x, follow the instructions for RHEL 5.x, unless otherwise noted. When tasks are specific to the version of the RHEL OS, headings refer to RHEL 4, RHEL 5, or RHEL 6. Checking the Host for Required Packages If you are installing and building the Emulex driver, make sure the Developmental Tool package that contains the gcc compiler is installed on the RHEL server.
3. Change to the driver source directory by issuing cd lpfc_ _driver_kit-. For example: # cd 4. lpfc_2.6_driver_kit-8.2.0.29-1 Run the lpfc-install script that builds and installs the lpfc driver. Check the installed README for more details. # ./lpfc-install The script performs the following: a. The driver source is installed at /usr/src/lpfc from the installed rpm packages lpfcdriver-_. For example: # ls /usr/src/lpfc/lpfcdriver* lpfcdriver-2.
1. Before building the ramdisk, add the following HBA parameters to the/etc/modprobe.conf file, depending on your version of RHEL. These HBA options settings are required for desired multipath failover/failback operation: • For RHEL 6: NOTE: The /etc/modprobe.conf file has been deprecated in RHEL 6. In order to make changes to the ramdisk, follow these steps: 1. Create the /etc/modprobe.d/modprobe.conf file. 2. If the HP 3PAR array is running HP 3PAR OS 3.1.
is running an older HP 3PAR OS version (one that is not HP 3PAR OS 3.1.1 or later), set the lpfc_devloss_tmo setting to 1. # cat /etc/modprobe.
The following example shows a ramdisk build: # /sbin/dracut -v -f /boot/initrd-2.6.18-53.el5.img 2.6.18-53.el5 Creating initramfs Looking for deps of module scsi_mod Looking for deps of module sd_mod scsi_mod Looking for deps of module scsi_transport_spi: scsi_mod . . . copy from `/lib/modules/2.6.18-8.el5/kernel/drivers/scsi/scsi_transport_fc.ko' [elf64-x86-64] to `/tmp/initrd.l13681/lib/scsi_transport_fc.ko' [elf64-x86-64] copy from `/lib/modules/2.6.18-8.el5/kernel/drivers/scsi/lpfc/lpfc.
Setting up the NVRAM and BIOS with the Emulex HBA This section describes setting up the NVRAM and BIOS with the Emulex HBA. Configure the following NVRAM settings using the Emulex Lightpulse BIOS utility. Access the BIOS utility by hard booting the server and, when prompted, perform the procedures in this section. NOTE: The NVRAM settings on Emulex HBAs can be changed by any server in which they are installed. These settings will persist for an HBA even after it is removed from a server.
To configure many of these parameters you must identify the HBA to work on using its WWPN. These can be obtained by using the following command: # hbacmd ListHBAs This will produce output similar to the following: Manageable HBA List Port WWN Node WWN Fabric Name Flags Host Name Mfg Serial No. Port Number Mode PCI Function Port Type Model : : : : : : : : : : : : 10:00:00:00:c9:69:d6:cc 20:00:00:00:c9:69:d6:cc 00:00:00:00:00:00:00:00 8000fe0d dl360g7-16.3pardata.
Modifying the /etc/modprobe.conf file and Building the Ramdisk NOTE: The /etc/modprobe.conf file has been deprecated in RHEL 6. In order to make changes to the ramdisk, create the /etc/modprobe.d/modprobe.conf file. 1. If the HP 3PAR array is running HP 3PAR OS 3.1.1 or later, modify the options qla2xxx line to include qlport_down_retry=10, as shown below. The modified output of /etc/modprobe.conf should include the following when the 3PAR array is running HP 3PAR OS 3.1.
For example: # mkinitrd -f -v /boot/initrd-2.6.18-53.el5.img 2.6.18-53.el5 NOTE: For RHEL 6, rebuild the ramdisk image using the dracut command: # /sbin/dracut -v -f /boot/ 4. Perform one of the two following actions to verify that all the required drivers are added to the ramdisk image: • Check the verbose output. For example: Creating initramfs . . . . . . . . Looking for deps of Looking for deps of . . . . . . . . Looking for deps of Looking for deps of . . . .
2. 3. 4. Select a host adapter from the main menu. Restore the default settings of the HBA as follows: Configuration Settings→Restore Default Settings. Make the following setting changes: NOTE: The parameters provided in these menu options might vary between different QLogic HBA models, and may not appear as shown here. 5.
For example, to set the HBA ports 1 and 3 to Point to Point/Fabric topology, run the following commands: # /opt/Qlogic_Corporation/SANsurferCLI/scli -n 1 CO 1 # /opt/Qlogic_Corporation/SANsurferCLI/scli -n 3 CO 1 To set the same HBA ports 1 and 3 to Direct topology, run the following commands: # /opt/Qlogic_Corporation/SANsurferCLI/scli -n 1 CO 0 # /opt/Qlogic_Corporation/SANsurferCLI/scli -n 3 CO 0 You can verify the setting by running the following command: # /opt/Qlogic_Corporation/SANsurferCLI/scli -I
1. Download the driver package from the following website: Brocade Extract the driver contents by issuing tar xvzf brocade_driver_linux-.tar.gz. Make sure to do this in a temporary location. For example: # tar zxvf brocade_driver_linux_rhel6_v3-2-1-0.tar.gz bfa_driver_linux-3.2.1.0-0.noarch.rpm bfa_util_linux_noioctl-3.2.1.0-0.noarch.rpm bna_driver_linux-3.2.1.0-0.noarch.rpm bna-snmp-3.2.1.0-rhel6.i386.rpm bna-snmp-3.2.1.0-rhel6.x86_64.rpm brocade_install_rhel.sh brocade_install.
Configure the following NVRAM settings using the Brocade BIOS utility Access the BIOS utility by hard booting the server and, when prompted, perform the procedures in this section. NOTE: The NVRAM settings on Brocade HBAs can be changed by any server in which they are installed. These settings will persist for an HBA even after it is removed from a server.
1. This is a per-port setting.
2. Create udev rules 56_3par_timeout.rules under /etc/udev/rules.d with the following contents: /etc/udev/rules.d/56-3par.timeout.rules KERNEL="sd*[!0-9]", SYSFS{vendor}="3PARdata", PROGRAM="/bin/sh -c 'echo 60 > /sys/block/%k/device/timeout'" NAME="%k" Required Make sure there is no break between the two lines in the 56-3par-timeout.rules. The udev rule number 56-3par-timeout.rules should follow after the 51-by-id.rules. Change the udev rule number accordingly. The 56-3par-timeout.
Using QLogic Scripts to Set the SCSI Timeout The following script changes the SCSI timeout value to 60 seconds for LUNs discovered by each of the QLogic HBA ports. Use this script if you are running Remote Copy. If you have implemented the timeout value change using the udev method, then do not use this script. When you run the script, the SCSI timeout value for each of the current LUNs discovered will be changed immediately.
Using Emulex Scripts to Set the SCSI Timeout If the udev rule was not implemented, you can change the SCSI timeout value from 30 seconds to 60 seconds by running the set_target_timeout.sh. You can download this shell script from the following website: Emulex Selecting Linux Tools on the Emulex Linux driver download website. The timeout value is a dynamic variable and can be changed even while I/O is being served on the devices. Example: Emulex changing timeout script: # ./set_target_timeout.
You can use the following commands to configure multipath devices: • multipath inspects Linux devices to see if there are multiple paths to the same device and communicates to the kernel device-mapper to set up a device map (dm) device for the device and is responsible for the path coalescing and device map creation. • The multipathd daemon checks path health and will reconfigure the multipath map whenever a path comes up or goes down so as to maintain correctly the path mapping state.
NOTE: The sysfsutils-xx package contains the libsysfs.so.1 library. If any upgrades are made to this package, the new library file should be copied over to the /lib directory. Modifying the /etc/multipath.conf File The /etc/multipath.conf file is used by Device-mapper where the multipathing parameters have been set. The default installed /etc/multipath.conf file must be edited with the following changes for a minimum configuration connecting to an HP 3PAR StoreServ Storage array.
For RHEL 6.1 # cat /etc/multipath.conf defaults { polling_interval max_fds } 10 8192 devices { device { vendor "3PARdata" product "VV" no_path_retry 18 features "0" hardware_handler "0" path_grouping_policy multibus getuid_callout "/lib/udev/scsi_id --whitelisted path_selector rr_weight rr_min_io path_checker failback --device=/dev/%n" "round-robin 0" uniform 1 tur immediate } } For RHEL 5.6 or Later # cat /etc/multipath.
hardware_handler "0" path_grouping_policy multibus getuid_callout "/sbin/scsi_id -g -u -s path_selector "round-robin 0" rr_weight uniform rr_min_io 100 path_checker tur failback immediate polling_interval 10 /block/%n" } } NOTE: If the HP 3PAR array that the RHEL server is connecting to is running an HP 3PAR OS version earlier than 3.1.1, you must change the no_path_retry setting to 12 rather than 18, and the polling_interval setting to 5 rather than 10.
For the ALUA Setting in RHEL 6.1 or Later For the ALUA Setting in RHEL 5.8 Later Enabling Multipath Perform the following actions to enable multipath. 1. Invoke the multipath command for any name changes to be effective.
2. Verify that the multipathd daemon is enabled by the rc script to run on every host boot up. The following output shows that it is enabled for run-level 3, 4 and 5. Enable it appropriately for your configuration: # chkconfig --list multipathd multipathd 0:off 1:off 2:off 3:on 4:on 5:on 6:off 3. Check that the appropriate rc scripts have been created for each run level. The start number(s) may not match those shown here. # ls /etc/rc3.d/*multi* /etc/rc3.d/S13multipathd # ls /etc/rc5.d/*multi* /etc/rc5.
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.
4. To confirm that the Veritas vxdmp driver has registered and claimed the HP 3PAR StoreServ Storage, issue the following Veritas command: # vxddladm listsupport libname=libvx3par.so ATTR_NAME ATTR_VALUE ======================================================================= LIBNAME libvx3par.so VID 3PARdata PID VV ARRAY_TYPE A/A ARRAY_NAME 3PARDATA If you are using the Veritas Storage Foundation version 5.0mp3 or higher, then you do not need to install the ASL for the HP 3PAR StoreServ Storage.
6 Configuring a Host with iSCSI Setting Up the Switch and iSCSI Initiator Connect the Linux host iSCSI initiator port(s) and the HP 3PAR StoreServ Storage iSCSI target ports to the switch(es). If you are using VLANs, make sure that the switch ports which connect to the HP 3PAR StoreServ Storage iSCSI target ports and iSCSI initiator ports reside in the same VLANs and/or that you can route the iSCSI traffic between the iSCSI initiator ports and the HP 3PAR StoreServ Storage iSCSI target ports.
Connect the RHEL host iSCSI initiator port(s) and the HP 3PAR StoreServ Storage iSCSI target ports to the switch(es). If you are using VLANs, make sure that the switch ports which connect to the HP 3PAR StoreServ Storage iSCSI target ports and iSCSI initiator ports reside in the same VLANs and/or that you can route the iSCSI traffic between the iSCSI initiator ports and the HP 3PAR StoreServ Storage iSCSI target ports.
3. To control how often a ping is sent by the iSCSI initiator to the iSCSI target, change the following parameter. node.conn[0].timeo.noop_out_interval = [replacement_timeout] To detect problems quickly in the network, the iSCSI layer sends iSCSI pings to the target. If the ping times out, the iSCSI layer responds by failing running commands on the path where the pings failed. 4. Set this parameter to 10 seconds. node.conn[0].timeo.noop_out_interval = 10 5.
Storage arrays that have a smaller target port queue depth of 512. These situations can be mitigated by reducing the values for parameters node.session.cmds_max and node.session.queue_depth on each host that shares the array target port. 9. As an option, you can also enable the Header and Data Digest for error handling and recovery within the connection. Typically, whenever a CRC error occurs, the SCSI layer tries to recover by disabling the connection and recovering.
Figure 4 Adding IP addresses 2. In the Network Configuration pane, select Configure Static IP Address.
Figure 5 Configuring Static IP Address 3. 62 In the IP Address field of the Static IP Address pane, enter the IP Address, Subnet Mask, and Default Gateway.
Figure 6 Entering the IP Address, Subnet Mask, and Default Gateway 4. Save the changes and reboot the server. Using the OneCommand Manager GUI To configure hardware iSCSI using the OneCommand Manager GUI, follow these steps: 1. Issue the /usr/sbin/ocmanager/ocmanager & command to open the OneCommand Manager and configure hardware iSCSI.
Figure 7 Configuring hardware iSCSI 2. 64 On the Adapter information tab, in the Personality pane, make sure that Personality is set to iSCSI.
Figure 8 Setting Personality to iSCSI 3. Add the target portal on port 0:2:1.
Figure 9 Adding the Target Portal NOTE: 4. 66 To list the HP 3PAR StoreServ target ports, issue the showport -iscsi command: Highlight the target.
Figure 10 Highlighting the Target 5. Click Target Login... and accept the default settings.
Figure 11 Selecting the Default 6. 68 Highlight the now-connected target.
Figure 12 Highlighting the Connected Target 7. To view the established sessions, click Target Sessions....
Figure 13 Listing the Target Session Use the initiator name to create the host definition by issuing the HP 3PAR OS CLI createhost -iscsi -persona command: • On an HP 3PAR StoreServ Storage running HP 3PAR OS 3.1.2 or earlier, or OS 2.3.x, use the createhost command with the -persona 1 option: # createhost -iscsi -persona 1 redhathost iqn.1990-07.com.emulex:28-92-4a-af-f5-61 • HP 3PAR StoreServ Storage running HP 3PAR OS 3.1.
Make sure to use the correct hbacmd utility version to configure hardware iSCSI.
To check the hardware iSCSI session information, issue the following command: Use the BIOS to add IP addresses, and use the OneCommand Manager GUI or the hbacmd utility to configure hardware iSCSI.
A SAN boot on hardware iSCSI requires the SAN boot driver for the installation. • "linux dd" can be used to load the driver disk source during the installation. • A networking device, IP address, gateway, and DNS are also required during the install. • Select Specialized Storage Devices to discover the iSCSI boot LUN. See Figure 14 (page 73). Figure 14 Specialized Storage Devices • Once the boot LUN is discovered, select the multipath devices to install the RHEL (Figure 15 (page 74)).
Figure 15 Multipath Devices For more information, see the RedHat Enterprise Linux 6 Storage Administration Guide, available at the following website: Red Hat Configuring RHEL 6 or RHEL 5 iSCSI Settings with Device-mapper Multipathing The /etc/multipath.conf file is used by Device-mapper where the multipathing parameters have been set. The default installed /etc/multipath.conf file must be edited with the following changes for a minimum configuration connecting to an HP 3PAR array.
polling_interval max_fds 5 8192 } devices { device { vendor product no_path_retry features hardware_handler path_grouping_policy path_selector rr_weight rr_min_io_rq path_checker failback "3PARdata" "VV" 12 "0" "0" multibus "round-robin 0" uniform 1 tur immediate } } For RHEL 6.1 # cat /etc/multipath.
For ALUA Settings in RHEL 6.1 or Later For RHEL 5.6 or Later # cat /etc/multipath.
For ALUA Settings in RHEL 5.8 For RHEL 5.0 through RHEL 5.5 NOTE: The following multipath settings for the RHEL server apply regardless of the HP 3PAR OS version running on the HP 3PAR StoreServ Storage array with a persona 1 setting: # cat /etc/multipath.
When changing from HP 3PAR host persona 1 to host persona 2 or vice versa: • A change from persona 1 to persona 2, or from persona 2 to persona 1, requires that the array ports affected be taken offline, or that the host for which the persona is being changed be not connected (not logged in). This is an HP 3PAR OS requirement. • For existing devices targeted in a persona to be claimed, the host must be rebooted. Use 1. 2. 3. 4. 5.
2. You can check the state of the open-iSCSI service run level information with the chkconfig command. Run level 5 should be on.
2. The contents of the discovery can be viewed using the iscsiadm -m discovery command. For example: # iscsiadm -m discovery 10.100.0.101:3260 via sendtargets 3. Issue the iscsiadm -m node command: # iscsiadm -m node 10.100.1.101:3260,31 iqn.2000-05.com.3pardata:20320002ac000121 4. Identify the iSCSI node login that record has been discovered from the discovery process. iscsiadm -m node -T -p : -l. For example: # iscsiadm -m node -T iqn.2000-05.com.
NOTE: The RHEL 5 iSCSI iface setup describes how to bind a session to a NIC port using iSCSI software. Running iscsiadm -m iface reports iface configurations setup in /var/ lib/iscsi/ifaces. For more details, refer to the RHEL 5 U4 open-iscsi release note. Configuring RHEL 4 for iSCSI This section discusses the necessary tasks for setting up iSCSI for RHEL 4. Installing iSCSI on RHEL 4 Install the software iSCSI initiator software package if it has not been installed.
NOTE: Dynamic Driver Reconfiguration: Configuration changes can be made to the iSCSI driver without having to stop it or to reboot the host system. To dynamically change the configuration of the driver, insert the /etc/init.d/iscsi reload to the /etc/iscsi/ iscsid.conf file. This will cause the iSCSI daemon to re-read the iscsi.conf file and to create any new Discovery Address connections it finds. Those discovery sessions will then discover targets and create new target connections. 6.
vendor product no_path_retry features hardware_handler path_grouping_policy path_selector rr_weight rr_min_io path_checker failback polling_interval "3PARdata" "VV" 12 "0" "0" multibus "round-robin 0" uniform 100 tur immediate 5 } } 4. 5. Run the multipath command for any name changes to be effective. Verify that the multipathd daemon is enabled by the rc script to run on every host boot up. The following output shows that it is enabled for run-level 3, 4 and 5.
For HP 3PAR OS 3.1.x and OS 2.3.x, the output shows: # showhost Id Name 0 redhatlinux Persona ----------WWN/iSCSI_Name----------- Port Generic iqn.1994-05.com.redhat:a3df53b0a32d --- For HP 3PAR OS 2.2.x, the output shows: # showhost Id Name -----------WWN/iSCSI_Name------------ Port 0 linux iqn.1994-05.com.redhat:a3df53b0a32d -iqn.1994-05.com.redhat:a3df53b0a32d The following example uses the host CHAP password host_secret0 for the host. Be aware that CHAP secret must be at least 12 characters long.
3. Perform discovery and login as described in “Discovering Devices with a Software iSCSI Connection” (page 112). If the targets have been discovered previously, you must logout of the iSCSI sessions, delete the node and send target records before performing discovery and logins by completing the following steps: a. Perform an iSCSI Logout: # iscsiadm -m node --logoutall=all b. Remove the iSCSI Node: # iscsiadm -m node -o delete -T iqn.2000-05.com.3pardata:20310002ac000079 -p 10.100.0.101,3260 c.
2. Check to see if the iscsid daemon is running by using the script /etc/init.d/iscsi status. # /etc/init.d/iscsi status iscsid (pid 30532 30529) is running... (RedHat 4) Checking for service iSCSI driver is loaded Setting Up the Bidirectional CHAP on the HP 3PAR StoreServ Storage To set bidirectional CHAP (mutual), complete the following steps. The HP 3PAR OS CLI sethost initchap and sethost targetchap commands must be used to set bidirectional CHAP on the HP 3PAR StoreServ Storage. 1.
NOTE: Notice that two DiscoveryAddress variables with the same IP address for the HP 3PAR StoreServ Storage iSCSI target port are required. One for the host CHAP username and password variables (OutgoingUsername and OutgoingPassword) and another one for target CHAP username and password variables (IncomingUsername and IncomingPassword). 1. Perform the CHAP configuration settings for the host initiator: # To enable CHAP authentication set node.session.auth.authmethod # to CHAP. The default is None. node.
3. Perform discovery and login as describe in “Discovering Devices with a Software iSCSI Connection” (page 112). If the targets have been discovered previously, you must logout of the iSCSI sessions, delete the node and send target records before performing discovery and logins by completing the following steps: a. Perform an iSCSI Logout. # iscsiadm -m node --logoutall=all b. Remove the iSCSI Node. # iscsiadm -m node -o delete -T iqn.2000-05.com.3pardata:20310002ac000079 -p 10.100.0.101,3260 c.
1. Go to the iSCSI Initiator host console, or, at a terminal, edit the /etc/iscsi/iscsid.conf file and configure the host and target CHAP passwords. DiscoveryAddress=10.0.0.10 DiscoveryAddress=10.0.0.20 OutgoingUsername=redhatlinux OutgoingPassword=host_secret0 DiscoveryAddress=10.0.0.10 DiscoveryAddress=10.0.0.
Using the iSNS Server to Create a Discovery Domain Follow these steps: 1. Click Start→Administrative Tools→iSNS Server→Discovery Domains tab. 2. In the window that appears, click the Create button. 3. In the Create Discovery Domain popup, enter the discovery domain or select the default, and then click OK. Configuring the iSCSI Initiator and Target for iSNS Server Usage Configuring the HP 3PAR StoreServ Storage Follow these steps to configure the HP 3PAR StoreServ Storage: 1.
Start the service by issuing the following command: # service isnsd start Create a new ISNS interface by issuing the following command # iscsiadm -m iface -o new -I isns_iface Update the interface to use TCP/IP by issuing the following command: # iscsiadm -m iface -o update -I isns_iface -n iface.transport_name -v tcp Discover the ISNS server by issuing the following commands. Example: # iscsiadm -m discoverydb -t isns -p : -o new # iscsiadm -m discoverydb -t isns -p 10.107.66.
7 Configuring a Host with FCoE This chapter describes the procedures that are required to set up a Linux host to communicate with an HP 3PAR StoreServ Storage server over an FCoE initiator on a Linux host to a FCoE target on the HP 3PAR StoreServ Storage server. Linux Host Requirements The Linux host needs to meet the following software requirements.
Figure 16 Configuring FCoE 2. In the System Options pane, select NIC Personality Options. Figure 17 NIC Personality Options 3. In the PCI Slot 2 Pane, select FCoE for both Port 1 and Port 2.
Figure 18 Configuring the PCI Slots 4. PCI Slot 2 Port 1 and Port 2 now display FCoE. Figure 19 PCI Slot 1 and Slot 2 Configured for FCoE 5. 94 Save the changes and exit the BIOS.
Figure 20 Exiting the BIOS Utility Configuring the FCoE host personality on Broadcom CNA To configure the FCoE host personality on Broadcom CNA, follow these steps: 1. When the Broadcom BIOS message (shown in Figure 21 (page 95)) appears, enter Ctrl-S. Figure 21 HP ProLiant Broadcom BIOS Message The Comprehensive Configuration Management window appears. 2. Select the appropriate device, as shown in Figure 22 (page 96).
Figure 22 Select the Appropriate Device 3. Select Device Hardware Configuration, as shown in Figure 23 (page 96). Figure 23 Select Device Hardware Configuration 4. 96 Set Storage Personality to FCoE, as shown in Figure 24 (page 97).
Figure 24 Set Storage Personality to FCoE Installing and Configuring the Broadcom HBA for FCoE Connectivity Install the Broadcom HBA(s) in the host in accordance with the documentation provided with the HBAs and host. NOTE: Supported Servers • Gen 8 only • Most Gen 8 DL, BL and select ML Servers are supported; see server quick specs for specifics.
4. Find the FCoE Ethernet instances using ifconfig or the Network Manager on the GUI. 5. Create configuration files for all FCoE ethX interfaces: # cd /etc/fcoe # cp cfg-ethx cfg- 6. Modify /etc/fcoe/cfg- by setting DCB_REQUIRED to yes and DCB_REQUIRED to no. For example: 7. Turn on all ethX interfaces # ifconfig up 8. Disable lldpad on Broadcom CNA interfaces.
9. Make sure that /var/lib/lldpad/lldpad.conf is created, and that each block either does not specify adminStatus or is set to 0. 10. Restart lldpad service to apply new settings: # service lldpad restart 11. Restart FCoE service to apply new settings: # service fcoe restart 12. To verify all created FCoE interfaces, issue the fcoeadm –I command: If no FCoE interfaces are present, then ensure that operating system is configured to automatically enable the required network interfaces.
For Broadcom FCoE and the ALUA Setting in RHEL 6.3 or Later For RHEL 6.
For the ALUA Setting in RHEL 6.2 or Later For the ALUA Setting in RHEL 5.10 or later 3. 4. Restart the multipathd daemon for any changes to be effective. Verify that the multipathd daemon is enabled by the rc script to run on every host boot up. The following output shows that it is enabled for run-level 3, 4 and 5.
5. Check that the appropriate rc scripts have been created for each run level. The start number(s) may not match those shown here. # ls /etc/rc3.d/*multi* /etc/rc3.d/S13multipathd # ls /etc/rc5.d/*multi* /etc/rc5.
8 Allocating Storage for Access by the RHEL Host Creating Storage on the HP 3PAR StoreServ Storage This section describes the general steps and commands that are required to create the virtual volumes (VVs) that can then be exported for discovery by the RHEL host. For additional information, see the HP 3PAR Command Line Interface Administrator’s Manual. For a comprehensive description of HP 3PAR OS commands, see the HP 3PAR Command Line Interface Reference.
NOTE: The commands and options available for creating a virtual volume may vary for earlier versions of the HP 3PAR OS.
1 TESTLUNS.1 sqa-dl380g5-05 iqn.1994-05.com.redhat:33853dd5ab2e 1:3:1 host 2 TESTLUNS.2 sqa-dl380g5-05 iqn.1994-05.com.redhat:33853dd5ab2e 1:3:1 host 3 TESTLUNS.3 sqa-dl380g5-05 iqn.1994-05.com.redhat:33853dd5ab2e 1:3:1 host 4 TESTLUNS.4 sqa-dl380g5-05 iqn.1994-05.com.redhat:33853dd5ab2e 1:3:1 host 5 TESTLUNS.5 sqa-dl380g5-05 iqn.1994-05.com.redhat:33853dd5ab2e 1:3:1 host 6 TESTLUNS.6 sqa-dl380g5-05 iqn.1994-05.com.redhat:33853dd5ab2e 1:3:1 host 7 TESTLUNS.7 sqa-dl380g5-05 iqn.1994-05.com.
Method 1 - sysfs Scan After exporting VLUNs to the host using the createvlun command in “Exporting LUNs to the Host” (page 104), use the echo statement on the sysfs file system to scan for devices.
where: • 0 specifies the host • 1 specifies the channel • 2 specifies the ID • 3 specifies the LUN (The SCSI midlayer will re-scan.) # echo "scsi add-single-device 2 0 0 14" > /proc/scsi/scsi You can see the new LUN presented to the OS by the SCSI Mid-Layer in the /var/log/messages file.
The method of echo statement following the QLogic scan scsi-qlascan and the method of echo scsi add statement. . • Use the scsi-qlascan command.
Flash FW version 4.00.
3. Once the driver layer has discovered the device, run the echo statement for the RHEL OS layer to discover the HP 3PAR devices.
1. Issue scsi-qlascan to discover devices: # echo "scsi-qlascan" > /proc/scsi/qla2xxx/ 2. Once the new LUN is visible to the QLogic driver layer, force the SCSI mid-layer to do its own scan and build the device table entry for the new device: # echo "scsi add-single-device 0 1 2 3" >/proc/scsi/scsi The SCSI midlayer will re-scan, where 0 1 2 3 is replaced by your host, channel, ID, and LUN.
NOTE: The example shows other LUNs besides the eight instances of LUN 0.
2. Verify that the iSCSI exported volumes have been discovered. # cat /proc/scsi/scsi Attached devices: Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: 3PARdata Model: VV Type: Direct-Access 3. Rev: 0000 ANSI SCSI revision: 05 To verify device-mapper-multipath, run the multipath -ll command.
4. Check the block device files created in the system: # ls /sys/block/sd* /sys/block/sda: dev device queue range removable sda1 size stat 5. Verify which block device files are HP 3PAR volumes: # cat /sys/block/sd*/device/vendor ATA ATA 3PARdata 6.
9 Modifying HP 3PAR Devices on the Host Creating Device-mapper Devices Complete the following steps to create Device-mapper devices. 1. Run the multipath command to create new Device-mapper nodes under the /dev/mapper directory. # multipath 2. Verify that the Device-mapper devices have been created by issuing multipath -11.
sdc: getprio = /bin/true (config file default) sdc: prio = 0 sdc: getuid = /sbin/scsi_id -g -u -s /block/%n (config file default) sdc: uid = 350002ac0004b0079 (callout) sdd: not found in pathvec sdd: mask = 0x1f sdd: bus = 1 sdd: dev_t = 8:48 sdd: size = 10485760 sdd: vendor = 3PARdata sdd: product = VV sdd: rev = 0000 sdd: h:b:t:l = 3:0:0:0 sdd: serial = 004B0079 sdd: path checker = tur (controller setting) sdd: state = 2 sdd: getprio = /bin/true (config file default) sdd: prio = 0 sdd: getuid = /sbin/scsi
vendor = 3PARdata product = VV rev = 0000 h:b:t:l = 0:0:0:0 tgt_node_name = serial = 01B40031 path checker = tur (controler setting) state = 2 getprio = /bin/true (internal default) prio = 0 uid = 350002ac001b40031 (cache) ===== path info sdb (mask 0x1f) ===== bus = 1 dev_t = 8:16 size = 10485760 vendor = 3PARdata product = VV rev = 0000 h:b:t:l = 1:0:0:0 tgt_node_name = serial = 01B40031 path checker = tur (controler setting) state = 2 getprio = /bin/true (internal default) prio = 0 uid = 350002ac001b40031
NOTE: If you see the device status as [undef] in the output, this is an RHEL defect that has been raised with RHEL to be fixed. Instead, use the multipath -ll command, which shows the correct device status as ready. The dmsetup command can be used with various options to get more information on Device-mapper mappings.
After the fdisk command completes, use the kpartx command to list and create DM devices for the partitions on the device: # kpartx -a -p p /dev/mapper/350002ac001b40031 350002ac001b40031p1 : 0 10477194 /dev/mapper/350002ac001b40031 62 # kpartx -a -p p /dev/mapper/350002ac001b40031 -- will add a partition mapping # ls /dev/mapper 350002ac001b40031 350002ac001b40031p1 where 350002ac001b40031p1 is a partition device of whole disk 350002ac001b40031. fdisk or Parted Usage on RHEL 6.
Device Boot /dev/sdh1 Start 32768 End 10485759 Blocks 5226496 Id 83 System Linux If the -c or -u flag is not used during the creation of the partition, then the start sector is 30876, and a warning "Partition 1 does not start on physical sector boundary" appears after the partition is created. Example without the -c flag or -u flag: # fdisk /dev/sdh WARNING: DOS-compatible mode is deprecated.
File system type? [ext2]? ext4 Start? 0 End? -0 (parted) p Model: 3PARdata VV (scsi) Disk /dev/sdh: 5.37GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number 1 Start 0.02GB End 5.37GB Size 5.
2. Run the showvlun command on the HP 3PAR StoreServ Storage using the output above (minus first digit). # showvlun -lvw -a |grep -i 50002ac001b40031 0 testvlun 50002AC001B40031 redhathost 2100001B321A0C63 0 testvlun 50002AC001B40031 redhathost 2101001B323A0C63 3. 0:4:1 host 1:5:1 host On the iSCSI host, run ls /dev/mapper. # ls /dev/mapper 350002AC0004B0079 4. On the iSCSI host, run showvlun -lvw -a |grep -i .
For example, to remove target 0, LUN 2: # kpartx -d /dev/mapper/350002ac001b40031 # dmsetup remove 350002ac001b40031 # echo "1" > /sys/class/scsi_device/0:0:0:2/device/delete NOTE: When using the echo command, make sure the devices are removed from each of the host HBA instances.
WARNING! While removing the device, make sure the correct underlying device is used. Use the multipath command to identify the underlying device. CAUTION: For iSCSI devices, do not remove the last iSCSI device in / proc/scsi/scsi without first stopping multipathing, and then stopping the iSCSI daemon ( /etc/init.d/iscsi stop). Otherwise, data corruption can occur and the host will hang. Any change to the /etc/multipath configuration file requires running the multipathd command to be effective.
NOTE: Even though the default discard option for creating filesystem is performed on ext2, ext3, or ext4 filesystems, the mount option -o discard is supported only on the ext4 filesystem, so the space reclaim operation is also supported only on the ext4 filesystem. If you are recreating a file system on an existing TPVV, HP recommends that you use the default discard option, as it will free up space on the HP 3PAR StoreServ Storage storage volume for data that was not deleted before recreation.
10 Booting the Host from the HP 3PAR StoreServ Storage HP 3PAR StoreServ Storage Setup Requirements Booting from the HP 3PAR StoreServ Storage is supported in fabric and direct connect modes. During the RHEL installation process, you will specify the correct argument that will take into account multipathing during the installation process. Make sure you have allocated enough space when creating your virtual volumes to be able to install your RHEL 6 or RHEL 5 OS.
1. During the host boot, press Alt-E or Ctrl-E when prompted by the Emulex HBA Utility, a screen appears that will show the Emulex adapters in the system. Select and press Enter. a. After that, if a screen is being displayed that says: The BIOS of the Adapter is Disabled. If the screen says, The BIOS of the Adapter is Enabled, then skip to Step 2. b. Select option 2 Configure This Adapter's Parameters and press Enter. c.
1. For RHEL 5.x, when prompted by the install CDs or DVD after the host comes up, at the boot prompt, type the following command: boot: linux mpath This command communicates that multiple paths are connected from the storage to the host. 2. Respond to all the prompts during the install process by selecting the default settings. When the installation completes, the host is rebooted. Modifying the /etc/multipath.conf File NOTE: RHEL 6 uses the default install for a SAN boot.
NOTE: If the HP 3PAR StoreServ Storage array that the RHEL server is connecting to is running an HP 3PAR OS version earlier than 3.1.1, you must change the no_path_retry setting to 12 rather than 18, and the polling_interval setting to 5 rather than 10. For RHEL 5.6 or later, the contents of /etc/multipath.conf file should be edited as in the following example if the HP 3PAR StoreServ Storage array is running HP 3PAR OS 3.1.1 or later.
For RHEL 6.x, the contents of the /etc/multipath.conf file should be edited as in the following example if the HP 3PAR array is running HP 3PAR OS 3.1.1 or later. NOTE: If the HP 3PAR array that the RHEL server is connecting to is running an HP 3PAR OS version earlier than 3.1.1, you must change the no_path_retry setting to 12 rather than 18, and the polling_interval setting to 5 rather than 10. NOTE: For RHEL 6.1, replace the device keyword rr_min_io_rq in the example below with rr_min_io.
/dev/mapper/VolGroup00-LogVol00 14283576 /dev/mapper/mpath0p1 101086 tmpfs 2023232 3632732 16002 0 9913564 79865 2023232 27% / 17% /boot 0% /dev/shm Changing the Emulex HBA Inbox Driver Parameters See “Modifying the /etc/modprobe.conf File and Building the Ramdisk” (page 33) of this document for changing the Emulex HBA parameters and rebuilding the ramdisk. Installing the New QLogic Driver To install a new QLogic driver to replace the Linux inbox driver, complete the following steps: 1.
To change the qlport_down_retry parameter, issue the following command: # scli After the main menu comes up, select 3: HBA Parameters. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. Then, from the HBA Parameters Menu, select the HBA that you want to change. Then, from the HBA Parameters Menu, select 2: Configure HBA Parameters. From the Configure Parameters Menu, select 13: Port Down Retry Count. Then enter the value 10 for the Down Retry Count: if the HP 3PAR array is running HP 3PAR OS 3.1.1 or later.
11 Using Veritas Cluster Servers HP supports use with Veritas Cluster Server. There are no special setup considerations for the HP 3PAR StoreServ Storage. for installation and setup instructions, see the Veritas Cluster Server Installation Guide and Veritas Cluster Server User's Guide at the following website: Symantec CAUTION: Make sure Device-mapper is disabled if you are using the Veritas DMP as the multipathing solution.
12 Using RHEL Xen Virtualization HP supports the use of RHEL 5 Xen Virtualization. There are no special setup considerations for the HP 3PAR StoreServ Storage.
13 Using RHEL Cluster Services HP supports RHEL Cluster services for RHEL 4, RHEL 5, and RHEL 6. For installation and administration RHEL Cluster services, refer to the RHEL Linux Installation Guide and Configuring and Managing an RHEL Cluster on the following website: Red Hat To manage an RHEL 6.x cluster using the new luci and ricci method you must set a password for the ricci user account created during installation. See the Red Hat Cluster Deployment Guide for further information.
14 Using Red Hat Enterprise Virtualization (KVM/RHEV-H) The Red Hat Enterprise Virtualization Hypervisor (RHEV-H), based on Kernel Virtual Machine (KVM) technology, can be deployed either as a bare metal hypervisor or as an RHEL hypervisor host. The KVM hypervisor requires a processor with the Intel-VT or AMD-V virtualization extensions. The RHEL KVM package is limited to 64-processor cores. A guest OS can be used only on the hypervisor type that they were created on.
15 Using Oracle Linux HP supports Oracle Linux with both the RHEL-compatible kernel and with the UEK. Oracle Linux with RHEL-Compatible Kernel When using Oracle Linux with the RHEL-compatible kernel, follow the procedures in this guide for the corresponding version of RHEL. Using Oracle Linux with UEK Oracle Linux UEK is an optimized package for Oracle software and hardware. The Oracle Linux UEK is built upon the RHEL 6 kernel and is optimized specifically for Oracle software.
Number Start End Size File System Name Flags 1 0.02GB 16.1GB 16.1GB Primary (parted) q The following example uses kpartx to set the device name partition number delimiter: # kpartx -a -p p /dev/mapper/360002ac00000000000000265000185db dev/mapper/360002ac00000000000000265000185dbp1: mknod for 360002ac00000000000000265000185dbp1 failed: File exists In the preceding example, ignore the message failed: File exists.
16 Support for Oracle VM Server Oracle VM Server is supported with HP 3PAR OS 2.3.1 using host persona 6 as documented in HP 3PAR Additional Hardware Support For Inform OS 2.3.1 located in the HP SPOCK website: HP SPOCK To configure Device-mapper multipathing, see “Setting Up Multipathing Software” (page 48), as the procedure is same as that of RHEL. For all Oracle VM support with 3PAR OS 3.1.1 and later, file a Deal Exception Request/Customer Enhancement Request through your HP representative.
17 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 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 components
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 4 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 • System
18 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.
