This manual briefly explains the operations that need to be performed by the user in order to connect an
ETERNUS DX Disk storage system or an ETERNUS DX200F All Flash Array to a server running HP-UX via an
iSCSI interface.
This manual should be used in conjunction with any other applicable user manuals, such as those for the
ETERNUS DX Disk storage system, ETERNUS DX200F All Flash Array, server, OS, LAN cards, and drivers.
Refer to "FUJITSU Storage ETERNUS DX Configuration Guide -Server Connection- Notations" for the notations
used in this manual such as product trademarks and product names.
2.2 OS (Operating System)................................................................................................................... 8
2.3 LAN Cards ....................................................................................................................................... 8
Chapter 6 Installing the iSCSI Software Initiator and Setting Up the Server15
6.1 Downloading and Installing the iSCSI Software Initiator............................................................... 15
6.2 Setting Up the Server.................................................................................................................... 16
6.2.1 Setting Up the Command Queue Depth ..............................................................................................................16
6.2.2 Maximum Number of Volume Group Settings.....................................................................................................17
Note the following issues when connecting the ETERNUS DX to a server.
3.1ETERNUS DX Setup Notes
Be sure to set the sub system parameters.
3.2Notes Regarding the Number of LUNs
When using PV-Links, no more than 128 LUNs should be visible on any given path. If more than 128 LUNs
are found in one path, assignment of unique Target IDs and Disk IDs will not be possible and desired behavior will not be observed in this environment. This is because the PV-Links function assumes that if devices on
different paths have the same Target ID and Disk ID, then they must connect to the same LUN.
The maximum number of unique Target IDs and Disk IDs for the device is 128.
3.3LAN Environment Notes
The ETERNUS DX can be connected to a server via an existing LAN. However, a decrease in LAN perform-
•
ance may be observed by prior users of said LAN.
Since an iSCSI LAN handles large amounts of data (traffic volumes) like an FC-SAN, the iSCSI LAN must have
•
its own switch and be a dedicated LAN that is separate from the business LANs.
iSCSI LAN redundancy is achieved by the use of multipaths.
•
For IP network security, separate the iSCSI LAN from the management LAN (for administration).
•
The iSCSI LAN must be configured as a dedicated LAN for each path from a server to the ETERNUS DX.
A separate LAN segment is used for each
Server/Storage grouping (*2).
Here, LAN ports 1, 2 and 10 comprise VLAN1,
while LAN ports 3 and 11 comprise VLAN2.
The iSCSI LAN and management LAN
segments are kept separate in the iSCSI
LAN switches, helping maintain the security
of each.
Similarly to FC-SAN,
a dedicated LAN is used for iSCSI,
not the business LAN.
Business LAN
iSCSI LAN
Management LAN
LAN switch #1
[iSCSI LAN]
LAN switch #2
[iSCSI LAN]
Chapter 3 Notes
3.3 LAN Environment Notes
Example of a LAN switch connection configuration
*1: In this system configuration, multipaths provide redundant connections between the servers and stor-
age system. LAN switches #1 and #2 provide physical separation of the network paths.
*2: A separate LAN segment is provided in the LAN switch (using the switch VLAN function) for each group-
ing of business servers and storage systems (equivalent to the FC zones).
A mirrored LVM configuration using ETERNUS DX storage systems' LUNs is not recommended.
•
[Bad Block Relocation] attribute must be disabled on LVM Logical volume which resides on ETERNUS DX
•
storage systems.
Example:
# lvchange -r N /dev/vg01/lvol_name
Execute this command for all logical volumes created on ETERNUS DX storage systems' LUNs to disable
[Bad Block Relocation]. If [Bad Block Relocation] is not disabled, file system may be damaged.
Raw device access to an LVM logical volume must use an I/O block size that is a multiple of 1024bytes.
•
3.5Server Startup and Power Supply Control Notes
Before turning the server on, check that the ETERNUS DX storage systems and LAN switches are all "Ready". If
the server is turned on and they are not "Ready", the server will not be able to recognize the ETERNUS DX
storage systems.
Also, when the ETERNUS DX power supply is being controlled by a connected server, make sure that the
ETERNUS DX does not shut down before the connected servers. Similarly, the LAN switches must also be
turned off after the connected servers have been shut down. Similarly, the LAN switches must also be turned
off after the connected servers have been shut down. If turned off, data writes from the running server cannot be saved to the ETERNUS DX storage systems, and already saved data may also be affected.
3.6Jumbo Frame Setting Notes
To enable Jumbo Frame, all the connected devices must support Jumbo Frame. Set the appropriate values
•
for various parameters (such as the MTU size) on each connected device.
For details about how to set Jumbo Frame for a LAN card and LAN switch, refer to the OS and each device's
•
manuals. Rebooting the server may be required to apply the new settings.
The MTU size that is supported by the ETERNUS DX is 9,000 bytes.
Installing the iSCSI Software Initiator and Setting Up the Server
6.2Setting Up the Server
iSCSI connection settings depend on the CHAP authentication method. Perform the settings to match the
CHAP authentication to be used.
CHAP authentication methodRequired settings
None
Unidirectional CHAP authentication
Bidirectional CHAP authentication
"6.2.1 Setting Up the Command Queue Depth" (page 16)
•
"6.2.2 Maximum Number of Volume Group Settings" (page 17)
•
"6.2.3 iSCSI Basic Settings" (page 17)
•
"6.2.1 Setting Up the Command Queue Depth" (page 16)
•
"6.2.2 Maximum Number of Volume Group Settings" (page 17)
•
"6.2.3 iSCSI Basic Settings" (page 17)
•
"6.2.4 Server Settings when CHAP Authentication is Used" (page 19)
•
"6.2.1 Setting Up the Command Queue Depth" (page 16)
•
"6.2.2 Maximum Number of Volume Group Settings" (page 17)
•
"6.2.3 iSCSI Basic Settings" (page 17)
•
"6.2.4 Server Settings when CHAP Authentication is Used" (page 19)
•
"6.2.5 Server Settings when Bidirectional CHAP Authentication is Used" (page
•
20)
6.2.1Setting Up the Command Queue Depth
Set the number of commands allowed to be queued (command queue depth) on each LUN in the ETERNUS
DX storage systems from the LAN card. This setting optimizes the connection between the ETERNUS DX storage systems and the server.
Model
ETERNUS DXArbitrary (*1)
*1: Recommended value = 512 ¸ (number of iSCSI ports that are connected to a single CA port) ¸ number of
LUNs
(Round the result down)
Use the value of "8" if the actual result is lower.
For HP-UX11iv3
•
Set the command queue depth using the disk device attribute "max_q_depth". The "max_q_depth" is set
using the "scsimgr" command.
Example:
-
Setting the command queue depth of disk20 to 8
Setting value
Command queue depth
(Up to 512 for each iSCSI port of the ETERNUS DX)
# scsimgr save_attr -D /dev/rdisk/disk20 -a max_q_depth=8
Refer to the HP-UX manuals for details of the "scsimgr" command.
Installing the iSCSI Software Initiator and Setting Up the Server
For HP-UX11iv2
•
Set the command queue depth using the kernel parameter "scsi_max_qdepth".
The "scsi_max_qdepth" is set using System Administration Manager (SAM). When the command queue
depth is set using SAM, all SCSI devices are affected.
When changing the command queue depth of a particular SCSI device, the "scsictl" command is used. However, because the information set by the "scsictl" command becomes invalid when the server is shut down,
it is necessary to carry out setting every time the server is activated. For details about the "scsictl" command, refer to the HP-UX manual.
6.2.2Maximum Number of Volume Group Settings
For HP-UX11iv3, this setting is not required.
Set the kernel parameter maxvgs that limits the number of volume groups. Default value is 10.
If 11 or more volume groups are to be created, maxvgs will need to be changed. Kernel parameter maxvgs is
set using System Administration Manager (SAM).
One volume group is created for OS installation area.
If 10 (default) is set for maxvgs, up to 9 new volume groups can be created.
6.2.3iSCSI Basic Settings
The following items are required for the iSCSI connection and must be set:
iSCSI Initiator name
•
iSCSI connection target information
•
Authentication Method
•
1Set the shell environment variable PATH.
Add the location of the iSCSI Software Initiator executable files to the PATH environment variable.
# PATH=$PATH:/opt/iscsi/bin
2Set the iSCSI Initiator name.
This setting is not required if the default iSCSI Initiator name is to be used. Either the iSCSI Qualified
Name (iqn) or IEEE EUI-64 (eui) format may be used.
To set the iSCSI Initiator name, execute the "iscsiutil" command as follows:
Installing the iSCSI Software Initiator and Setting Up the Server
3Confirm the iSCSI Initiator name.
Use the "iscsiutil" command to check the iSCSI Initiator name.
The iSCSI Initiator name shown here is used for the ETERNUS DX settings.
# iscsiutil -l
4Save the statically-recognized iSCSI target information in the kernel registry.
Use the "iscsiutil" command to save the iSCSI target information.
# iscsiutil [iscsi-device-file] -a -I <ip-address>
[-P <tcp-port>][-M <portal-grp-tag>]
Example:
For an ETERNUS DX with a connection target iSCSI port IP address of 192.1.1.120:
# iscsiutil -a -I 192.1.1.120
5Confirm the iSCSI target information is now in the kernel registry.
# iscsiutil -p -D
6Set whether CHAP authentication is to be used or not.
If CHAP authentication is to be performed, set "CHAP". If CHAP authentication is not required, set
"None".
Example:
When CHAP authentication is not used:
# iscsiutil -t authmethod None
Note:
# iscsiutil -t authmethod CHAP None
The above command sets CHAP authentication to operate according to the ETERNUS DX setting. The
CHAP authentication method is selected if the ETERNUS DX uses CHAP for its responses, otherwise CHAP
authentication is not performed.
Installing the iSCSI Software Initiator and Setting Up the Server
6.2.4Server Settings when CHAP Authentication is Used
To use CHAP authentication, the following items must be set for the iSCSI ports of the ETERNUS DX and for
the iSCSI Initiators.
When setting the iSCSI port parameters for the ETERNUS DX, specify the "-I" option and input the IP address.
When setting the iSCSI Initiator parameters, do not specify the "-I" option.
CHAP Method
•
Initiator CHAP Name
•
CHAP Secret
•
1Set the CHAP Method.
The CHAP authentication method (unidirectional or bidirectional) must be set.
Set the CHAP Method value indicated in the following table:
CHAP authentication method
Unidirectional CHAP authenticationCHAP_UNI
Bidirectional CHAP authenticationCHAP_BI
CHAP Method setting
Use the "iscsiutil" command to set the CHAP Method.
Installing the iSCSI Software Initiator and Setting Up the Server
3Set CHAP Secret.
A CHAP Secret must be set for each target set in Step 4 of "6.2.3 iSCSI Basic Settings" (page 17). The
CHAP Secret set here must match the CHAP Secret that is to be set for Target.
Use the "iscsiutil" command to set the CHAP Secret.
<nas-hostname >Specify the IP address or hostname of the Network Access Server (NAS). This
<nas-secret >Set the NAS secret already set in the RADIUS server.
<radius-server-hostname >Specify the IP address or hostname of the RADIUS server.
Description
is the server that is to connect to the ETERNUS DX via the iSCSI interface. The
specified IP address or hostname must be for a LAN card that is able to communicate with the RADIUS server.
2Activate the daemon (iradd) that communicates with the RADIUS server.
Two types of multipath configurations are available for the connection between the ETERNUS DX and an HPUX server: "PV-Links" and "Native Multipaths".
This chapter explains how to set up the "PV-Links" or "Native Multipaths".
8.1Multipath Configuration using PV-Links
PV-Links" is a Logical Volume Manager (LVM) function, available for all HP-UX versions.
LVM for HP-UX supplies PV-Links as a standard function for configuring paths in a redundant configuration
(path failover function).
PV-Links is set by including multiple paths connected to one physical volume in one volume group.
Only one of the paths will be set as the Active path, with the other paths being made Standby paths.
However, load on the system may be better balanced by spreading the server accesses over multiple Active
paths.
When using PV-Links, note the following:
Confirm that the PV-Links paths have identical target IDs.
•
When set correctly, the device files for all paths that connect to a given ETERNUS DX LUN should all be the
same after the "t" part of the name (e.g. "/dev/dsk/c4t0d0" g"0d0").
For HP-UX11iv3, set the "leg_mpath_enable" parameter to "false" and use LegacyDSF to specify the
•
"pv_path" parameter to create VolumeGroup.
Reference
-
Device special file type
Legacy DSF/dev/dsk/c4t0d0
Persistent DSF/dev/disk/disk25
Example:
-
Setting "leg_mpath_enable" to "false"
# scsimgr save_attr -D /dev/rdisk/disk25 -a leg_mpath_enable=false
Using LegacyDSF to specify the "pv_path" parameter to create VolumeGroup
8.2 Multipath Configuration using Native Multipath
Setting the Multipaths
8.2Multipath Configuration using Native Multipath
"Native Multipaths" is an OS function available for HP-UX11iv3 onwards.
Native Multipaths can be used to set the I/O load balance policy (load_bal_policy) and enable ALUA
(alua_enabled).
Perform these settings to match the ETERNUS DX model and depending on whether the OS supports ALUA.
8.2.1Setting the I/O Load Balance Policy (load_bal_policy)
Set the I/O load balance policy to match the ETERNUS DX model being used as shown below. The policy setting is required for all LUNs in the ETERNUS DX.
I/O load balance policy setting vs ETERNUS DX model
Example procedure of I/O load balance policy setting
•
Setting the I/O load balance policy to "round_robin"
-
# scsimgr save_attr -D /dev/rdisk/disk25 -a load_bal_policy=round_robin
I/O load balance policy setting
round_robin
Execute this "load_bal_policy" setting command for all LUNs in the ETERNUS DX.
If the I/O load balance policy is "preferred_path", a priority path must be set. Set the path that is used
when the I/O load is balanced as the priority path.
Example procedure priority path setting
•
Specify the hardware path of the "Lunpath" that is to be the priority path.
-
# scsimgr save_attr -D /dev/rdisk/disk25 -a preferred_path=64000/0x0/0x0.0x0.0x4
000000000000000
Lunpath hardware paths can be checked using the "ioscan -m lun" and "scsimgr lun_map" commands.