Professional Documents
Culture Documents
HP 3PAR HP-UX Implementation Guide PDF
HP 3PAR HP-UX Implementation Guide PDF
Abstract
This implementation guide provides information for configuring an HP 3PAR StoreServ Storage system with HP-UX 11i v2
(11.23) or v3 (11.31). General information is provided with the basic steps required to allocate storage on the HP 3PAR
StoreServ Storage that can be accessed by the HP-UX host.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Links to third-party websites take you outside the HP website. HP has no control over and is not responsible for information outside HP.com.
Acknowledgments
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
Contents 3
10 Support and Other Resources...................................................................48
Contacting HP........................................................................................................................48
HP 3PAR documentation..........................................................................................................48
Typographic conventions.........................................................................................................49
Documentation feedback.........................................................................................................49
Index.........................................................................................................50
4 Contents
1 Introduction
This implementation guide provides information for configuring an HP 3PAR StoreServ Storage
system with HP-UX 11i v2 (11.23) or v3 (11.31). General information and basic steps are provided
for allocating storage on the HP 3PAR StoreServ Storage that is accessed by the HP-UX host.
NOTE:
• For predictable performance and results with the HP 3PAR StoreServ Storage, the information
in this guide must be used in concert with the documentation provided by HP for the HP 3PAR
StoreServ Storage and the documentation provided by the vendor for their respective products.
• In addition to the OS patches mentioned in this guide, there might be additional patches
referenced at the HP Storage Single Point of Connectivity Knowledge website.
For information about supported hardware and software platforms, see HP SPOCK:
http://www.hp.com/storage/spock
(From SPOCK Home under Explore Storage Interoperability With SPOCK, select Explore HP 3PAR
StoreServ Storage interoperability.)
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 HP-UX and the
HP 3PAR OS.
This guide provides basic information for establishing communication between the HP 3PAR
StoreServ Storage and the HP-UX host and allocating the required storage for a given configuration.
See the appropriate HP documentation in conjunction with the HP-UX host and HBA (Host Bus
Adapter) documentation for specific details and procedures.
Supported Configurations
FC connections are supported between the HP 3PAR StoreServ Storage and the HP-UX host in both
a fabric-attached and direct-connect topology.
Audience 5
For complete details about supported host configurations and interoperability, see HP SPOCK:
http://www.hp.com/storage/spock (From SPOCK Home under Explore Storage Interoperability
With SPOCK, select Explore HP 3PAR StoreServ Storage interoperability.)
6 Introduction
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
HP-UX host using Fibre Channel and how to set up the fabric when running HP 3PAR OS 3.1.x.
For information on setting up the physical connection for a particular HP 3PAR StoreServ Storage,
see the appropriate HP 3PAR installation manual.
NOTE: HP Recommends using default values to configure your host unless otherwise specified
in the following procedure.
REQUIRED
If you are setting up a fabric along with your installation of the HP 3PAR StoreServ Storage, see
“Setting Up and Zoning the Fabric” (page 11) before configuring or connecting your HP 3PAR
StoreServ Storage.
NOTE:
• Before connecting the HP 3PAR StoreServ Storage port to the host, complete the following
setup.
• When deploying HP Virtual Connect Direct-Attach Fibre Channel storage for HP 3PAR StoreServ
Storage systems, where the HP 3PAR StoreServ Storage ports are cabled directly to the uplink
ports on the HP Virtual Connect FlexFabric 10 Gb/24-port Module for c-Class BladeSystem,
follow the procedure for configuring the HP 3PAR StoreServ Storage ports for a fabric
connection.
• For more information about HP Virtual Connect, HP Virtual Connect interconnect modules,
and HP Virtual Connect Direct-Attach Fibre Channel feature, see the HP Support Center:
http://h20566.www2.hp.com/portal/site/hpsc/
See the HP SAN Design Reference Guide at HP SPOCK:
http://www.hp.com/storage/spock
(From SPOCK Home under Design Guides, select SAN Design Guide.)
• Download Brocade HBA drivers, firmware, and the BCU utility from the QLogic website at:
http://www.qlogic.com. Specific Brocade drivers are named with a BR prefix, such as BR-xxx
HBA model.
NOTE: Direct connect is not supported by the 16 Gb FC HP 3PAR StoreServ Storage target
interface.
Run the following HP 3PAR CLI (command line interface) commands with the appropriate parameters
for each direct connect port:
Configuring the HP 3PAR StoreServ Storage Port Running HP 3PAR OS 3.2.x or 3.1.x 7
1. Take the port off line using the controlport offline <node:slot:port> command.
For example:
2. Run the controlport config host -ct loop <node:slot:port> command, where
-ct loop specifies a direct connection.
For example:
3. Reset the port by using the controlport rst <node:slot:port> command on the HP
3PAR StoreServ Storage.
For example:
After all the ports are configured, verify that they are configured for a host in a direct connection
by using the showport -par command on the HP 3PAR StoreServ Storage.
NOTE: The HP 3PAR OS 3.2.1 Express Writes feature optimizes the performance for small block
random writes. It is enabled by default with 8 Gb Targets in Host HBA mode with bit Express
Writes. This Express Writes feature is only available on the HP 3PAR StoreServ 7000 and 10000
Storage systems with 8 Gb targets and not supported on HP 3PAR StoreServ 20000, 10000,
8000, or 7000 Storage systems with 16 Gb targets.
In the following example, a ConnType (connection type) of loop would denote a direct connection
and a ConnType of point would denote a fabric connection:
# showport -par
N:S:P Connmode ConnType CfgRate MaxRate Class2 UniqNodeWwn VCN IntCoal
...
1:5:1 host loop auto 4Gbps disabled disabled disabled enabled
...
# showport -par
N:S:P Connmode ConnType CfgRate MaxRate Class2 UniqNodeWwn VCN IntCoal
1:5:1 host point auto 4Gbps disabled disabled disabled enabled
2. If the port has not been configured, take the port offline before configuring it for connection
to a host.
CAUTION: Before taking a port offline in preparation for a fabric connection, verify that it
was not previously defined and that it is not connected to a host, because this would interrupt
the existing host connection. If an HP 3PAR StoreServ Storage port is already configured for
a fabric connection, ignore this step 2.
To take the port offline, run the controlport offline <node:slot:port> command
on the HP 3PAR StoreServ Storage.
For example:
3. To configure the port to the host, run the controlport config host -ct point
<node:slot:port> command on the HP 3PAR StoreServ Storage, where -ct point
indicates that the connection type is a fabric connection.
For example:
4. Reset the port by using the controlport rst <node:slot:port> command on the HP
3PAR StoreServ Storage.
For example:
NOTE: Beginning with HP 3PAR OS 3.2.2, the createhost command has been enhanced
with the -port option, which automatically creates zones on the switch or fabric if the target port
is a 16 Gb FC target and the switch supports enhanced zoning. See “Fibre Channel Smart SAN”
(page 12).
Configuring the HP 3PAR StoreServ Storage Port Running HP 3PAR OS 3.2.x or 3.1.x 9
1. Create host definitions by using the createhost [options] <hostname> [<WWN>...]
command.
For example:
NOTE:
• The WWN, used in the command above to create a host definition, is the host HBA N_Port
Port World Wide Name (PWWN). To obtain the PWWN, run the fcmsutil command
on the HP-UX host. (This fcmsutil command is not an HP 3PAR CLI command.)
For example:
• Specifying the WWN in the createhost command is mandatory if the HBA used in
the HP-UX host is a QLogic HBA claimed by the fcd driver.
• Run fcmsutil <adapter device_file reset> on the host HBA to force it to
populate the WWNs on HP-UX if the zoning is in place.
Reset Done
2. Verify that the host has been created by using the showhost command on the HP 3PAR CLI.
# showhost
Id Name Persona -WWN/iSCSI_Name-
2 hpux-host HPUX 1122334455667799
1122334455667788
NOTE: See the HP 3PAR Command Line Interface Reference or the HP 3PAR StoreServ
Management Console User’s Guide for complete details about using the controlport,
createhost, and showhost commands.
These documents are available at the HP Storage Information Library:
http://www.hp.com/go/storage/docs
Fabric zoning controls which FC end-devices have access to each other on the fabric. Zoning also
isolates the host and HP 3PAR StoreServ Storage ports from Registered State Change Notifications
(RSCNs) that are irrelevant to these ports.
Set up fabric zoning by associating the device World Wide Names (WWNs) or the switch ports
with specified zones in the fabric. Use either the WWN method or the port zoning method with
the HP 3PAR StoreServ Storage. The WWN zoning method is recommended because the zone
survives the changes of switch ports when cables are moved around on a fabric.
Required
Employ fabric zoning, by using the methods provided by the switch vendor, to create relationships
between host HBA/CNA ports and HP 3PAR StoreServ Storage ports before connecting the host
HBA/CNA ports or HP 3PAR StoreServ Storage ports to the fabrics.
FC switch vendors support the zoning of the fabric end-devices in different zoning configurations.
There are advantages and disadvantages with each zoning configuration, so determine what is
needed before choosing a zoning configuration.
The HP 3PAR 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. Zoning by HBA is required for coexistence
with other HP Storage systems.
NOTE:
◦ For high availability and clustered environments that require multiple initiators to access
the same set of target ports, HP recommends creating separate zones for each initiator
with the same set of target ports.
◦ The storage targets in the zone can be from the same HP 3PAR StoreServ Storage, multiple
HP 3PAR StoreServ Storages, or a mixture of HP 3PAR and other HP storage systems.
For more information about using one initiator to multiple targets per zone, see the HP SAN Design
Reference Guide at HP SPOCK:
http://www.hp.com/storage/spock
(From SPOCK Home under Design Guides, select SAN Design Guide.)
When using an unsupported zoning configuration and an issue occurs, HP might require
implementing one of the supported zoning configurations as part of the corrective action.
HP 3PAR Coexistence
The HP 3PAR StoreServ Storage array can coexist with other HP array families.
For supported HP array combinations and rules, see the HP SAN Design Reference Guide at
HP SPOCK:
http://www.hp.com/storage/spock
(From SPOCK Home under Design Guides, select SAN Design Guide.)
brocade2_1:admin> portcfgshow
Ports 0 1 2 3 4 5 6 7
-----------------+--+--+--+--+----+--+--+--
Speed AN AN AN AN AN AN AN AN
Trunk Port ON ON ON ON ON ON ON ON
Locked L_Port .. .. .. .. .. .. .. ..
Locked G_Port .. .. .. .. .. .. .. ..
The following fill-word modes are supported on a Brocade 8 Gb switch running FOS firmware
6.3.1a and later:
admin>portcfgfillword
Usage: portCfgFillWord PortNumber Mode [Passive]
Mode: 0/-idle-idle - IDLE in Link Init, IDLE as fill word (default)
1/-arbff-arbff - ARBFF in Link Init, ARBFF as fill word
2/-idle-arbff - IDLE in Link Init, ARBFF as fill word (SW)
3/-aa-then-ia - If ARBFF/ARBFF failed, then do IDLE/ARBFF
HP recommends setting the fill word to mode 3 (aa-then-ia), which is the preferred mode,
by using the portcfgfillword command. If the fill word is not correctly set, er_bad_os
counters (invalid ordered set) will increase when using the portstatsshow command while
connected to 8 Gb HBA ports, as they need the ARBFF-ARBFF fill word. Mode 3 will also
work correctly for lower-speed HBAs, such as 4 Gb/2 Gb HBAs. For more information, see
the Fabric OS Command Reference Manual and the FOS release notes, at the Brocade website:
https:/www.brocade.com
NOTE: 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.
• Cisco switch ports that connect to HP 3PAR StoreServ Storage ports or host HBA ports should
be set to AdminMode = FX and AdminSpeed = auto port, with the speed set to auto negotiate.
• QLogic switch ports should be set to port type GL-port and port speed auto-detect. QLogic
switch ports that connect to the HP 3PAR StoreServ Storage should be set to I/O Stream Guard
disable or auto, but never enable.
◦ HP 3PAR HBA 8 Gb: 3276 (HP 3PAR StoreServ 10000 and 7000 Storage systems only)
• The I/O queues are shared among the connected host HBA ports on a first-come, first-served
basis.
• When all queues are in use and a host HBA port tries to initiate I/O, it receives a target queue
full response from the HP 3PAR StoreServ Storage port. This condition can result in erratic I/O
performance on each host. If this condition occurs, each host should be throttled so that it
Setting Up and Zoning the Fabric 13
cannot overrun the HP 3PAR StoreServ Storage port's queues when all hosts are delivering
their maximum number of I/O requests.
NOTE:
◦ When host ports can access multiple targets on fabric zones, the target number assigned
by the host driver for each discovered target can change when the host is booted and
some targets are not present in the zone. This situation might change the device node
access point for devices during a host restart. This issue can occur with any
fabric-connected storage, and is not specific to the HP 3PAR StoreServ Storage.
◦ The maximum number of I/O paths supported is 16.
NOTE: Use of HP 3PAR Persistent Ports technology does not negate the need for properly installed,
configured, and maintained host multipathing software.
# rmsf -H <hw_path>
For example:
# rmsf -H 0/0/0/9/0/0/0.50.100.0.2.5.0
To take advantage of the HP 3PAR Persistent Ports feature, disable the following Symantec Storage
Foundation Dynamic Multi-Pathing (DMP) tunables:
HP recommends that PVLinks multipathing be enabled on all HP-UX 11i v2 host servers in order to
avoid I/O disruption when a persistent port fails over to its partner port.
The HP 3PAR Persistent Ports feature is not supported with iSCSI.
# swlist FibrChanl*
#
# swlist Online*
# OnlineDiag B.11.31.04.05 HPUX 11.31 Support Tools Bundle, September 2008
3. HP recommends that the server be at a certain firmware version to detect the fibre channel
cards. Verify the firmware version using the MP interface on the Integrity or HP 9000 Server.
MP:CM> SYSREV
FIRMWARE:
Core IO
Master : A.006.012
Event Dict. : 1.009
Slave : A.006.012
Event Dict. : 1.009
Cell 0
PDHC : A.003.023
Pri SFW : 22.002 (PA)
Sec SFW : 1.025 (IA)
Cell 1
PDHC : A.003.023
Pri SFW : 22.002 (PA)
Sec SFW : 1.025 (IA)
Alternately, if Online Diagnostics are installed, run the cstm tool to find the firmware version.
a. Run the Support Tools Manager (STM) utility cstm.
# /usr/sbin/cstm
b. Use the STM CLI selall and il commands to find all the required system information.
# cstm>SelAll
cstm>il
...
Product ID : ia64 hp server rx7620
Product Number : not set
System Firmware Revision : 001.025
BMC Revision : v06.12
System Serial Number: : not set
System Software ID : 3801066248
c. For Itanium systems, install the supported EFI firmware for all supported HBAs. Download
the firmware from the HP Support Center by searching for your HBA model. Those firmware
versions are essential to enable the boot over SAN feature.
For example:
For complete details on creating volumes for the HP 3PAR OS version that is being used on the
HP 3PAR StoreServ Storage, see the following documents:
• HP 3PAR Management Console User Guide
• HP 3PAR OS Command Line Interface Reference
These documents are available at the HP Storage Information Library:
http://www.hp.com/go/storage/docs
NOTE: The commands and options available for creating a virtual volume might vary for earlier
versions of the HP 3PAR OS.
# showvlun
Active VLUNs
Lun VVName HostName -Host_WWN/iSCSI_Name- Port Type
...
VLUN Templates
Lun VVName HostName -Host_WWN/iSCSI_Name- Port Type
1 TestLUNs.0 hpux-host ---------------- --- host
2 TestLUNs.1 hpux-host ---------------- --- host
3 TestLUNs.2 hpux-host ---------------- --- host
4 TestLUNs.3 hpux-host ---------------- --- host
5 TestLUNs.4 hpux-host ---------------- --- host
...
2. Data VV LUN 254 has been presented to host, SES LUN 254 no longer auto-presented to
host:
5. For the HP-UX host to use the SES LUN 254, a data VV LUN 254, if presented, must be
unpresented and steps 3 and 4 above executed.
For more detail and other variations of using the HP-UX 11.31 scsimgr utility, see the SCSI
Management and Diagnostics utility white paper, available on the HP Support Center:
HP Support Center
# diskinfo /dev/rdisk/disk100
NOTE: Additional information on Agile Addressing Mode is provided in the Next Generation
Mass Storage Stack, HP-UX 11i v3 Native Multipathing for Mass Storage, and other documents
about storage area management for HP-UX 11i v3 are available at the HP SC:
HP Support Center
2. By default, Agile Addressing Mode is enabled. After exporting, new VLUNs exported while
the host is running are not registered on the host until you issue the ioscan command. This
command scans the hardware for new and usable devices. You can check the
/var/adm/syslog/syslog.log file during the discovery process to verify that the new
devices are discovered. Special device files for the new devices (raw and block device paths)
required to access the devices are created as part of the ioscan command by internally
executing the insf -e command.
# ioscan
# tail -f /var/adm/syslog/syslog.log
vmunix: 0/0/4/1/0.0x20420002ac000036.0x400a000000000000 eslpt
vmunix: 0/0/4/1/1.0x21520002ac000036.0x400a000000000000 eslpt
vmunix: 64000/0xfa00/0x243 esdisk
sfd[2330]: started 'insf' to create device special files for newly found devices.
sfd[2330]: execution of 'insf' completed.
Always use the -N option for the ioscan command to see the persistent devices or agile
devices. Without the -N option, legacy devices will be seen.
NOTE: Broken or stale device paths are displayed with S/W State of NO_HW in the output
of the ioscan -kfnNC disk command. The CLAIMED state indicates a valid disk device
path existence.
Example: Without the -N option, legacy devices are shown.
Example: The output of ioscan shows the relationship between the legacy and persistent
devices.
# ioscan -m dsf
Persistent DSF Legacy DSF(s)
========================================
/dev/rdisk/disk0 /dev/rdsk/c11t0d1
/dev/rdsk/c15t0d1
/dev/rdisk/disk1 /dev/rdsk/c11t0d2
/dev/rdsk/c15t0d2
/dev/rdisk/disk2 /dev/rdsk/c8t6d0
3. HP recommends not using the legacy device paths; instead, migrate applications from legacy
to persistent device paths by disabling the legacy device paths. All LVM commands work with
persistent device paths (DSF). Use the rmsf -v -L command to disable the legacy device
paths.
# rmsf -vL
WARNING: This command may be disruptive to the system.
Before running this command, make sure you have first run
iofind(1M) and migrated all applications using legacy device
special files. Please refer to the man page of rmsf(1M) to
verify the possible side effects of the option '-L'.
Do you want to continue ?
(You must respond with 'y' or 'n'.): y
rmsf: Removing special file /dev/dsk/c0t6d0
rmsf: Removing special file /dev/dsk/c0t6d0s1
rmsf: Removing special file /dev/dsk/c0t6d0s2
# insf -L
This command will re-install all legacy I/O nodes and legacy DSFs.
Do you want to continue ?
(You must respond with 'y' or 'n'.): y
insf: Legacy mode has been successfully enabled
Use insf -Lv to display the status as to whether Legacy Mode is enabled or disabled.
# insf -Lv
insf: Legacy mode is disabled
NOTE: The rest of this document assumes that legacy device paths have been disabled.
4. You can use various options for the ioscan command to obtain more details.
Example:
a. To show discovered devices, issue ioscan -kfnNC disk. The description field will
have HP 3PAR VV for all HP 3PAR StoreServ Storage volumes.
CAUTION: All I/O to the devices should use /dev/rdisk/disk for raw disk or
/dev/disk/disk for block I/O. Any partition on the device will be represented as
/dev/disk/diskX_pN number.
b. To determine the connected target ports (0:4:2 and 1:5:2) use the following commands:
1) Issue ioscan -kfnNC tgtpath on the HP-UX host.
# showport -i
N:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type
...
0:4:2 target ready 2FF70002AC000036 20420002AC000036 host
1:5:2 target ready 2FF70002AC000036 21520002AC000036 host
# ioscan -kfnNC fc
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
fc 5 0/0/4/1/0 fcd CLAIMED INTERFACE HP AH401A 8Gb Dual Port PCIe Fibre Channel Adapter
(FC Port 1)
/dev/fcd5
fc 6 0/0/4/1/1 fcd CLAIMED INTERFACE HP AH401A 8Gb Dual Port PCIe Fibre Channel Adapter
(FC Port 2)
/dev/fcd6
4) To determine the number of LUN paths for each DSF, issue ioscan -m hwpath:
# ioscan -m hwpath
Lun H/W Path Lunpath H/W Path Legacy H/W Path
====================================================================
64000/0xfa00/0x0
0/0/0/3/0.0x6.0x0
64000/0xfa00/0x17
0/0/4/1/1.0x21520002ac000036.0x0
64000/0xfa00/0x18
0/0/4/1/0.0x20420002ac000036.0x0
64000/0xfa00/0x23e
0/0/4/1/0.0x20420002ac000036.0x4001000000000000
0/0/4/1/1.0x21520002ac000036.0x4001000000000000
64000/0xfa00/0x23f
0/0/4/1/0.0x20420002ac000036.0x4002000000000000
0/0/4/1/1.0x21520002ac000036.0x4002000000000000
In the LUN path the 16-bit address following the target port ID
(0x20420002ac000036) represents the LUN number where the device is seen and
the addressing mode. For example, for 0x4001 (which translates to
0100000000000001) the first two bits 01 represents Volume Set Addressing mode
and the remaining 14 bits represent the LUN number, which is LUN 1 in this example.
The host uses estp driver for target paths, eslpt for LUN paths and esdisk as
disk driver.
5) You can find the health of a device, target, LUN path and determine whether it is
on or off line using the -P option. The -C option can be used to specify attributes
such as target ports, disks, or individual LUN paths. The status limited means some
paths are taken offline from the available multiple paths.
# showvlun -a
Lun VVname Host -Host_WWN/iSCSI_Name- Port Type
20 hpcheck sqahpit2 50060B00001D1192 1:5:2 host
20 hpcheck sqahpit2 50060B000068D5A4 0:4:2 host
Issue ioscan -kfnNC lunpath to verify that the host recognizes the VV as
/dev/disk/disk20.
Remove the LUN and re-export it as LUN 25 and you can see that /dev/disk/disk20 is
recreated for LUN 25 and the LUN path for LUN number 20 goes stale (NO_HW).
HP 3PAR StoreServ Storage:
# showvlun -a
Lun VVname Host -Host_WWN/iSCSI_Name- Port Type
25 hpcheck sqahpit2 50060B00001D1192 1:5:2 host
25 hpcheck sqahpit2 50060B000068D5A4 0:4:2 host
HP-UX host:
6. HP-UX 11i v3 provides the scsimgr command, which provides generic management and
diagnostic capabilities for the SCSI subsystem of the mass storage stack. Use the scsimgr
command to obtain the SCSI disk status information, statistics, change multipath options, set
attributes, inquiry information and to perform other task management functions such as LUN
and target resets.
Example:
a. Issue the scsimgr command to obtain the relationship between the hardware LUN path,
device special file (DSF), and HP 3PAR VV.
# showvv -d
ID Name Rd Mstr Prnt Roch Rwch PPrnt PBlkRemain -----VV_WWN----- ---------CreationTime--------
584 hpcluster.0 RW 0/1/- --- --- --- - 50002AC002480036 Tue Oct 23 12:53:36 PDT 20
The output above shows that /dev/rdisk/disk0 is a device special file for HP 3PAR
StoreServ Storage VV hpcluster.0 exported as LUN 1 and verified from HP 3PAR
StoreServ Storage CLI showvv and showvlun commands.
c. To find the number of paths for a disk, use either the scsimgr lun_map command or
the scsimgr lun_map -D /dev/rdisk/disk6 command:
e. The default load balancing policy is round robin. HP offers other load balancing options.
The load balancing policy can be changed either globally or for an individual disk.
Example: Issue the following commands to globally change from round_robin to
least_cmd_load:
name = load_bal_policy
current = round_robin
default = round_robin
saved =
Verify it is changed
name = load_bal_policy
current = least_cmd_load
default = round_robin
saved =
name = load_bal_policy
current = least_cmd_load
default = round_robin
saved = least_cmd_load
name = load_bal_policy
current = round_robin
default = least_cmd_load
saved =
name = load_bal_policy
current = round_robin
default = round_robin
saved =
CAUTION: Do not change any other default values such as path failover or I/O retry
values.
...
SCSI ATTRIBUTES FOR LUN : /dev/pt/pt4
Device type = Array_Controller
Serial number = 00000000
Vendor id = 3PARdata
Product id = ARRAY
Product revision = 0000
I/O load balance policy = path_lockdown
LUN Path used when policy is path_lockdown = 0/0/4/1/0.0x20420002ac000036.0x0
h. You can use the get_stat option to obtain the statistics of a given device and for debug
purposes.
Generic Statistics:
...
I/O transfer Statistics:
i. In HP-UX 11i v3, a device WWN (HP 3PAR StoreServ Storage VV) is closely tied to its
exported LUN ID (HP 3PAR StoreServ Storage VLUN). When seeing a different device
WWN (HP 3PAR StoreServ Storage VV) on a previously used LUN ID (VLUN) to prevent
data corruption, the host puts the LUN into an authentication failure state where the LUN
path cannot be used for I/O transfer. This state causes the host to log a message in
/var/adm/syslog/syslog.log and on the console to alert the user. The user should
rely on these messages and should apply the recommended corrective action, which
usually consists of running the scsimgr replace_wwid command.
# showvv -d
590 oracle1 RW 0/1/- --- --- --- --- - 50002AC0024E0036 Tue Oct 30 19:31:59 PDT 2007
591 oracle2 RW 1/0/- --- --- --- --- - 50002AC0024F0036 Tue Oct 30 19:32:01 PDT 2007
# showvlun -a
Lun VVname Host -Host_WWN/iSCSI_Name- Port Type
6 oracle1 sqahpit2 50060B000068D5A4 0:4:2 host
6 oracle1 sqahpit2 50060B00001D1192 1:5:2 host
Remove the VLUN oracle1, and export oracle2 on the same LUN ID 6.
Issuing ioscan on the HP-UX 11i v3 host shows the scsimgr replace_wwid in the
syslog.log file and that the LUN path instances (19, 20) have failed the authentication.
# ioscan
# tail -f /var/adm/syslog/syslog.log
sqahpit2 vmunix: class : lunpath, instance 19
sqahpit2 vmunix: Evpd inquiry page 83h/80h failed or the current page 83h/80h data do not match the previous
known page 83h/80h data on LUN id 0x0 probed beneath the target path (class = tgtpath, instance = 0) The lun
path is (class = lunpath, instance 19).Run 'scsimgr replace_wwid' command to validate the change
sqahpit2 vmunix: An attempt to probe existing LUN id 0x4006000000000000 failed with errno of 14.
sqahpit2 vmunix: class : lunpath, instance 20
sqahpit2 vmunix: class : lunpath, instance 19
sqahpit2 vmunix: Evpd inquiry page 83h/80h failed or the current page 83h/80h data do not match the previous
known page 83h/80h data on LUN id 0x0 probed beneath the target path (class = tgtpath, instance = 1) The lun
path is (class = lunpath, instance 20).Run 'scsimgr replace_wwid' command to validate the change
You can use oracle2 volume with the same device name (/dev/rdisk/disk22), which
was previously allocated to oracle1 and have the same LUN path instance (19, 20). This
feature is useful for cases where applications, volume manager, file system do not need
to be re-configured. Then, use the DSF option as part of the scsimgr replace_wwid
command which will preserve and reuse the existing device name
(/dev/rdisk/disk22).
Not using the DSF option will generate a new DSF names example
(/dev/rdisk/disk23) using the same LUN path instances.
j. In cases where all the LUNs below the target port are put in the authentication state, such
as, when the target port was moved but the LUNs are the same, then the target port must
be authenticated. Use the following command to authenticate a target:
The target instance can be obtained using the “ioscan -kfnNC tgtpath” command
CAUTION: All I/O should be paused and the disk re-configured from Volume Manger
or Application before changing the name. For details, consult the appropriate HP
documentation.
l. You can give alias names for the disk as a way of tracking device names with the HP
3PAR StoreServ Storage volume name using the alias option for set_attr in the
scsimgr command.
7. List and remove all stale devices in the system using the following commands:
8. Use the diskinfo or scsimgr command or SAM tool to display the volume size of the
exported LUN.
# diskinfo /dev/rdisk/disk3
SCSI describe of /dev/rdisk/disk3:
vendor: 3PARdata
product id: VV
type: direct access
size: 5242880 Kbytes
bytes per sector: 512
# scsimgr get_info -D /dev/rdisk/disk3
Driver esdisk Status Information :
9. Some LVM commands, such as vgimport require the-N option to be specified to use the
new DSF device name (/dev/disk/disk). All display commands show the persistent DSF
name.
# vgdisplay -v
VG Name /dev/vgcluster
VG Write Access read/write
VG Status available
...
WARNING! HP-UX defines every path to a device (that is, a single HP 3PAR StoreServ
Storage VLUN) as a different device (for example, cxt0d0 and cyt0d0), the potential to
overwrite data on a LUN exists if I/O is performed directly to the /dev/dsk/ or /dev/rdsk/
special files. The PVLinks feature is part of LVM volume management. See the HP LVM
documentation on the HP SC: HP Support Center for information on using PVLinks. In particular,
see Managing Systems and Workgroups: A Guide for HP-UX System Administrators HP, 9000,
Computers, Edition 9, Manufacturing Part Number: 2355-90950, Chapter 6: “Administering
a System: Managing Disks and Files,” Section: “Setting Up Alternate Links to a Physical
Volume.”
Alternate links (paths) to a volume are defined at the volume group level using the vgcreate
command or by using the SAM GUI.
# sam > Disk and File systems > Volume Groups & Logical Volumes
The order of failover paths specified during volume creation is important, that is failover priority
is considered in the same order as that used when the volume was created. For example:
The failover path for the primary active path is increased by 1 up to path n.
NOTE: The SAM utility for creating volume groups creates all possible alternate links by
default.
After the primary link recovers, LVM automatically switches the active I/O from the alternate
path to the primary path unless instructed otherwise with the pvchange LVM command.
After initial volume-group setup, path management is manipulated at the physical-volume level
using HP—UX pv commands.
• To display the paths to a device, and the status of each path, use the HP—UX pvdisplay
/dev/dsk/... command.
• To display the paths to all devices within a volume-group, use the HP-UX vgdisplay
-v command.
The following example shows partial output from these commands:
# vgdisplay -v
LV Name /dev/testdg/testvol1
LV Status available/syncd
LV Size (Mbytes) 10000
Current LE 2500
Allocated PE 2500
Used PV 1
--- Physical volumes --
PV Name /dev/dsk/c120d1
PV Name /dev/dsk/c14t0d1 Alternate Link
PV Status available
Total PE 2559
NOTE:
• See the : HP Support Center website for information on using the PVLinks feature to
manage device paths.
• LVM and VxVM may coexist on the same system but should not be used to manage the
same devices.
• Remember to create raw and block device paths for the exported VLUNs using the HP-UX
ioscan and insf commands before executing any LVM and VxVM commands for the
new devices.
• The driver for AB379B and AD194A is FCD. The driver for AD299A or AD355A is FCLP.
Replace FCD to FCLP if you are using the AD299A or AD355A driver in the following
examples. The example below is for the AD194A HBA.
2. The fcmsutil utility can be used to display important information about each HBA port using
the port's /dev/fcd<instance> device node. The FCD instance number is shown in the
output of the ioscan -fun command.
# ioscan -fun
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
fc 2 2/0/11/1/0/4/0 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb
FC/2-port 1000B-T Combo Adapter (FC Port 1)
NOTE: Topology will be PRIVATE_LOOP for a direct connection and PTTOPT_FABRIC for
a fabric connection. The example below is for fabric.
Vendor ID is = 0x001077
Device ID is = 0x002422
Topology = PTTOPT_FABRIC
Driver Version = @(#) libfcd.a HP Fibre Channel ISP 23xx & 24xx Driver B.11.23.1205
/ux/core/isu/FCD/kern/src/common/wsio/fcd_init.c:Apr 27 2012,05:18:14
4. Use fcmsutil to find out other command fabric service parameters and connected HP 3PAR
StoreServ Storage port WWNs. Here is an example for a fabric connection:
5. To find the storage serial number for the corresponding disk id on the HP-UX host, use the
STM CLI cstm command. The HP Online diagnostic tool must be installed to access the cstm
command. For example:
# cstm
# selclass type disk
# info
# infolog
. . .
Hardware path: 0/2/0/0.8.0.0.0.0.4
The selected device is not supported by this tool.
Inaccurate information could be displayed by the tool.
Check the ioscan -fun disk for the given hardware path and use the HP 3PAR StoreServ
Storage CLI command showvlun -lvw or showvv -d to get the volume name. The data
which matches is in bold font:
NOTE: For Itanium systems, install the supported EFI firmware for all of the HBAs listed on
HP SPOCK:
http://www.hp.com/storage/spock
Download firmware from the HP SC at: HP Support Center by searching for the HBA model.
Those versions of firmware are essential to enabling the boot over SAN feature.
For the latest supported HBA firmware and driver versions, see the HP SPOCK website:
http://www.hp.com/storage/spock
The following example shows the HBA and EFI versions in bold.
For AH403A
# fcmsutil /dev/fclp1 vpd
V I T A L P R O D U C T D A T A
--------- ------------- -------
Product Description : "HP 8Gb Dual Channel PCI-e 2.0 FC HBA"
Part number : "AJ763-63001"
Part Serial number : "MY19255R61"
Engineering Date Code : "B-4845"
Mfd. Date : "4925"
Misc. Information : "PW=13.3 W; PCIE X8 GEN 2"
ROM Firmware version : "2.00A4 SLI-3 (U3D2.00A4)"
EFI version : "UU5.03A15"
Use the <tab> key to navigate between fields, and the arrow keys
within fields. Use the <return/enter> key to select an item.
Use the <return/enter> or <space-bar> to pop-up a choices list. If the
menus are not clear, select the "Help" item for more information.
[ Reboot ] [ Help ]
2. Select H/W Details to verify that the HP 3PAR StoreServ Storage VV is visible.
[ H/W Details ]
Disk Drives:
Model Capacity(Mb) WWID
HP_36.4GST33675 34732 0x0011c6fffe28ddfc
1/0/0/3/0.0x6.0x0
/opt/ignite/bin/itool () +
¦ ¦
¦ +-------++----------++--------++-------------++----------+ ¦
¦ ¦ Basic ¦¦ Software ¦¦ System ¦¦ File System ¦¦ Advanced ¦ ¦
¦ ¦ \-------------------------------------------------------------------+¦
¦ ¦ ¦¦
¦ ¦ Configurations: [ HP-UX B.11.31 Default ->] [ Description... ] ¦¦
¦ ¦ ¦¦
¦ ¦ Environments: [ HP-UX Data Center Operatin ->] (HP-UX B.11.31) ¦¦
¦ ¦ ¦¦
¦ ¦ [ Root Disk ] HP_36.4GST336753LC, 1/0/0/3/0.0x6.0x0, 3> ¦¦
¦ ¦ ¦¦
¦ ¦ File System: [ Logical Volume Manager (LVM) with VxFS ->] ¦¦
¦ ¦ ¦¦
¦ ¦ [ Root Swap (MB)... ] 2048 Physical Memory (RAM) = 2040 MB ¦¦
¦ ¦ ¦¦
¦ ¦ [ Languages... ] English [ Keyboards... ] [ Additional... ] ¦¦
¦ ¦ ¦¦
¦ +---------------------------------------------------------------------------+¦
¦ [ Show Summary... ] [ Reset Configuration ] ¦
¦------------------------------------------------------------------------------¦
¦ [ Go! ] [ Cancel ] [ Help ] ¦
+------------------------------------------------------------------------------+
[ Root Disk ]
/opt/ignite/bin/itool () +
¦ ¦
¦ +-------++----------++--------++-------------++----------+ ¦
¦ ¦ Basic ¦¦ Software ¦¦ System ¦¦ File System ¦¦ Advanced ¦ ¦
¦ ¦ \-------------------------------------------------------------------+¦
¦ ¦ ¦¦
¦ ¦ Configurations: [ HP-UX B.11.31 Default ->] [ Description... ] ¦¦
¦ ¦ ¦¦
¦ ¦ Environments: [ HP-UX Data Center Operatin ->] (HP-UX B.11.31) ¦¦
¦ ¦ ¦¦
¦ ¦ [ Root Disk ] 3PARdataVV, 1/0/6/1/0.0x21410002ac0000b4> ¦¦
¦ ¦ ¦¦
¦ ¦ File System: [ Logical Volume Manager (LVM) with VxFS ->] ¦¦
¦ ¦ ¦¦
¦ ¦ [ Root Swap (MB)... ] 2048 Physical Memory (RAM) = 2040 MB ¦¦
¦ ¦ ¦¦
¦ ¦ [ Languages... ] English [ Keyboards... ] [ Additional... ] ¦¦
¦ ¦ ¦¦
¦ +---------------------------------------------------------------------------+¦
¦ [ Show Summary... ] [ Reset Configuration ] ¦
¦------------------------------------------------------------------------------¦
¦ [ Go! ] [ Cancel ] [ Help ] ¦
+------------------------------------------------------------------------------+
4. The installation process starts installing files to the boot volume and sets the primary boot path.
HP recommends having a high-availability, redundant boot path.
45
9 HP-UX Software List Command Output
Servers have different patch requirements. HP Itanium Servers booted from SAN running HP-UX
11i v3 September 2012 Data Center OE and HP-UX 11i v2 June 2008 Mission Critical OE installed
with AB379B, AH402A, and AD193A HBA Cards. The following example shows listings of
operating system installations with product and patch components.
HP-UX 11i v3
# swlist
#
# Bundle(s):
#
10GigEthr-02 B.11.31.1209 PCIe 10 Gigabit Ethernet;Supptd HW=467799-B21, HW=AM225A, HW=AM232A, HW=AM233A
10GigEthr-03 B.11.31.1209 PCIe 10 GbE;Supptd HW=580151/610609/613431-B21,NC551/552/553,AT094/111/118A
10GigEthr-04 B.11.31.1209.01 PCIe 10 Gigabit Ethernet;Supptd HW=593715/BS668
B2491BA B.11.31 MirrorDisk/UX (Server)
B3835DA C.03.06 HP Process Resource Manager
B3929GB B.05.01.03 OnlineJFS for Veritas File System 5.0.1 Bundle
B5140BA A.11.31.08 Serviceguard NFS Toolkit
B5736DA A.04.20.31.08 HA Monitors
B8843CA A.03.05 HP-UX Workload Manager
Base-VXFS B.11.31 Base VxFS File System 4.1 Bundle for HP-UX
Base-VxFS-501 B.05.01.03 Veritas File System Bundle 5.0.1 for HP-UX
BaseLVM B.11.31.1209 Logical Volume Manager
CIFS-CLIENT A.02.02.02 HP CIFS Client
CIFS-SERVER A.03.01.05 HP CIFS Server
CommonIO B.11.31.1209 Common IO Drivers
DSAUtilities C.01.00.20 HP-UX Distributed Systems Administration Utilities
DynRootDisk B.1131.A.3.11.328 Dynamic Root Disk
DynamicNPars B.11.31.0709 Dynamic nPartitions enablement
FEATURE11i B.11.31.1209.383a Feature Enablement Patches for HP-UX 11i v3, September 2012
FIREFOX A.2.0.0.19ar.02 Firefox for HP-UX
FibrChanl-00 B.11.31.1003 FibreChannel;HW=A6795A,A5158A
FibrChanl-01 B.11.31.1209 FibrChnl;HW=A6826A,A9782A,A9784A,AB378A/B,AB379A/B,AB465A,AD193A,AD194A,AD300A
FibrChanl-02 B.11.31.1209 FCLP;HW=AD299A,AD355A,AD221A,AD222A,AD393A,AH402A,AH403A,403621-B21,456972-B21
FibrChanl-03 B.11.31.1209 FCOC;HW=580151-B21,613433-001,AT111A
FibrChanl-04 B.11.31.1209.01 FCQ;HW=P3P
GTK 2.6.8.00.01 GTK+ 2.6 The Gnome GUI Runtime Toolkit
GigEther-00 B.11.31.0903 PCI GigEther;Supptd HW=A4926A/A4929A/A6096A;SW=J1642AA
GigEther-01 B.11.31.1112 PCI GigEther;Supptd HW=A6825A/A6794A/A6847A/A8685A/A9782A/A9784A/A7109A/AB465A
HP-ACC-Link C.11.31.03 HP aCC_link Bundle
HP-Caliper-PERF C.11.31.07 HP Caliper Bundle
HP-WDB-DEBUGGER C.11.31.07 HP DEBUGGER Bundle
HPPortableImage B.11.31.1103 HP-UX Portable Image
HPUX-DHCPv4 B.11.31 HPUX DHCPv4 Server
HPUX-DHCPv6 B.11.31 HPUX DHCPv6 Server
HPUX-FTPServer C.2.6.1.7.0 HPUX FTP Server
HPUX-MailServer C.8.13.3.5 HPUX Mail Server
HPUX-NTP B.11.31 HPUX NTP Server
HPUX-NameServer C.9.3.2.12.0 HPUX Name Server
HPUX-RAMD B.11.31 HPUX IPv6 routing Server
HPUX-TCPWRAP B.11.31 HPUX TCPWrapper daemon
HPUX11i-DC-OE B.11.31.1209 HP-UX Data Center Operating Environment
HPUXBastille B.3.3.01 Bastille Security Hardening Tool
HPUXEssential B.11.31.1203 Essential HP-UX Utilities
HPUXExtns-Jpn B.11.31 Japanese font, input methods and printer extensions
HPUXExtns-Kor B.11.31 Korean font, input methods and printer extensions
HPUXExtns-SCh B.11.31 Simplified Chinese font, input methods and printer extensions
HPUXExtns-TCh B.11.31 Traditional Chinese font, input methods and printer extensions
HPUXGatedMrouted B.11.31 HPUX Gated and Mrouted Server
HPUXLocales B.11.31 Internationalization Support
HPUXMan-Eng B.11.31.1203 Minimum and Essential English man pages
HPUXMan-Jpn B.11.31.1203 Minimum and Essential Japanese man pages
HPUXMinRuntime B.11.31 Minimum Runtime Environment
HPUXMsgs-Fre B.11.31 Minimum and Essential HP-UX French Language Message Catalogs
HPUXMsgs-Ger B.11.31 Minimum and Essential HP-UX German Language Message Catalogs
HPUXMsgs-Ita B.11.31 Minimum and Essential HP-UX Italian Language Message Catalogs
HPUXMsgs-Jpn B.11.31 Minimum and Essential HP-UX Japanese Language Message Catalogs
HPUXMsgs-Kor B.11.31 Minimum and Essential HP-UX Korean Language Message Catalogs
HPUXMsgs-SCh B.11.31 Minimum and Essential HP-UX Simplified Chinese Language Message Catalogs
HPUXMsgs-Spa B.11.31 Minimum and Essential HP-UX Spanish Language Message Catalogs
HPUXMsgs-Swe B.11.31 Minimum and Essential HP-UX Swedish Language Message Catalogs
HPUXMsgs-TCh B.11.31 Minimum and Essential HP-UX Traditional Chinese Language Message Catalogs
HWEnable11i B.11.31.12
HP-UX 11i v2 47
10 Support and Other Resources
Contacting HP
For worldwide technical support information, see the HP support website:
http://www.hp.com/support
HP 3PAR documentation
For information about: See:
Supported hardware and software platforms The Single Point of Connectivity Knowledge for HP
Storage Products (SPOCK) website:
SPOCK (http://www.hp.com/storage/spock)
Customer Self Repair procedures (media) The HP Customer Self Repair Services Media Library:
Customer Self Repair Services Media Library
(http://h20464.www2.hp.com/index.html)
Under Product category, select Storage. Under Product
family, select 3PAR StoreServ Storage for HP 3PAR
StoreServ 7000, 8000, 10000, and 20000 Storage
systems.
Bold monospace text • Commands you enter into a command line interface
• System output emphasized for scannability
WARNING! Indicates that failure to follow directions could result in bodily harm or death, or in
irreversible damage to data or to the operating system.
CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.
Required
Indicates that a procedure must be followed as directed in order to achieve a functional and
supported implementation based on testing at HP.
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.
Typographic conventions 49
Index
HP Smart SAN, 12
C Fibre Channel see FC
CLI firmware
command line interface, 7 Brocade, 7
command line interface see CLI
configuring H
direct connection to host , 7 HBA
port, 7 Host Bus Adapter, 5
ports, 8 host
ports for a direct connection, 7 creating definition for FC, 9
connecting HBA considerations, 41
to host, 10 HP 3PAR devices
conventions removing, 40
text symbols, 49 HP 3PAR Persistent Ports
creating connectivity guidelines for FC, 15
storage, 19 for FC, 14
TDVVs, 20 setting up for FC, 15
TPVVs, 20 HP Smart SAN
VLUNs, 19 FC, 12
VVs, 19 HP Storage Single Point of Connectivity Knowledge see
HP SPOCK
D HP Virtual Connect Direct-Attach Fibre Channel
data duplication, 20 storage, 7
deduplication, 20
deploying I
HP Virtual Connect Direct-Attach Fibre Channel storage, installation
7 from HP-UX 11i v2, 42
documentation from HP-UX 11i v3, 42
providing feedback on, 49 Itanium systems
drivers HBA considerations, 41
Brocade, 7
HBA, 7 L
LUN
E exporting to host, 20
EFI firmware, 41 marked as offline after an HP 3PAR OS upgrade, 5
exporting
LUNs to a Windows Server host, 5 M
Microsoft Failover Clustering, 5
F
fabric P
setting up for FC, 11 patch components, 46
zoning for FC, 11 ports
FC configuring, 8
creating host definition, 9 configuring for direct connection , 7
guidelines for FC switch vendors, 12 configuring for direct topology, 7
host connection, 10 FC target port limits, 13
HP 3PAR Persistent Ports, 14 FC target port specifications, 13
HP 3PAR Priority Optimization, 14 HP 3PAR Persistent Ports for FC, 14
persistent port setup, 15
setting up fabric, 11 R
target port limits, 13 removing
target port specifications, 13 devices from the host, 40
zoning fabric, 11 restrictions
features volume size and number, 22
HP 3PAR Persistent Ports for FC, 14
HP 3PAR Priority Optimization for FC, 14
50 Index
S
SPOCK
HP Storage Single Point of Connectivity Knowledge, 5
storage
creating TDVV, 20
creating VVs, 19
storage foundation, 45
swlist output, 46
symbols in text, 49
T
TDVV
creating, 20
thinly deduplicated virtual volumes, 20
text symbols, 49
thinly deduplicated virtual volumes see TDVV
thinly provisioned virtual volume see TPVV
TPVV
creating, 19
thinly provisioned virtual volume, 20
U
upgrading, 5
considerations, 5
V
virtual
LUN, 20
see also VLUN
virtual volume see VV
VLUN, 20
creating, 19
volume
number restrictions, 22
size restrictions, 22
VV, 20
creating, 19
fully provisioned, 19
thinly deduplicated, 20
thinly provisioned, 19
virtual volume, 19
Z
ZFS
using with deduplication, 20
51