Logical units and target ports on Hitachi HUS VM systems

The Hitachi HUS VM system has a maximum LUN size of 60 TB and eight Fibre Channel ports.

LUNs

A volume is referenced by the ID or the name of the LDEV.

Hitachi HUS VM can export 4096 LUNs per system to the SAN Volume Controller system. The SAN Volume Controller system supports greater than 2 TB LUNs.

LUN IDs

Hitachi HUS VM systems identify exported logical units through SCSI identification descriptor type 3. The 64-bit IEEE Registered Extended Identifier (NAA=5) for the logical unit is in the form 5-OUI-VSID. The HDS IEEE company ID is 00060E8. The remaining part of the company ID is a vendor-specific ID.

[11:19:00]:~ # lsmdisk 3
id 3
name mdisk2
status online
mode managed
mdisk_grp_id 2
mdisk_grp_name pool1
capacity 256.0GB
quorum_index 1
block_size 512
controller_name controller3
ctrl_type 4
ctrl_WWNN 50060E801329EB30
controller_id 0
path_count 2
max_path_count 2
ctrl_LUN_# 0000000000000003
UID 60060e801329eb00502029eb0000000400000000000000000000000000000000
preferred_WWPN
active_WWPN 50060E801329EB10
fast_write_state empty
raid_status
raid_level
redundancy
strip_size
spare_goal
spare_protection_min
balanced
tier generic_hdd
[11:19:03]:~ #

Configuring Hitachi logical drives, host groups, and paths

The SAN Volume Controller ports can be seen on the Hitachi HUS VM system.

On the Hitachi Storage Navigator, complete the following steps:

Click Ports/Host Groups.
Click Edit Ports to enable port security on each of the port IDs to be used with the SAN Volume Controller system.
From the General Tasks section of the navigator, click Create Host Groups to create a host group for the SAN Volume Controller system.
Continue through the process until you have a host group for the SAN Volume Controller system with the required hosts (host bus adapter WWN) entries.

Volumes and their corresponding logical units (LDEVs) are created, modified, or removed through the web browser. Volumes are formatted to all zeros when created.

Volumes are created as a logical device in a parity group or a dynamic provisioning (DP) pool.

Pools are created from logical devices that have no paths that are configured. For more information, see the Hitachi instructions.

To create managed disks (MDisks), follow these steps:

On the Hitachi Storage Navigator, select General Tasks > Create LDEVs to create a device that is to be presented to the SAN Volume Controller system.
Select a parity group and then select the capacity and number of devices to be created.
Select the paths to be used then click Add.
Click Next, Apply, and Finish. You are shown a task in progress. The devices require a completed format before further progress can be made.
On the SAN Volume Controller system, detect MDisks that were added or rebalance MDisk access across all available controller device ports. You can run the detectmdisk CLI command or use the management GUI.

Resizing or removing a LUN

To modify, resize, or remove a LUN, follow these guidelines:

Note:

Make sure that the MDisk is unmanaged (removed from any storage pool) on the SAN Volume Controller system before you delete the LUN on the Hitachi HUS VM SAN storage system.
Do not expand dynamic arrays on LUNs that are in use by SAN Volume Controller systems. For arrays to be recognized by the SAN Volume Controller system, the MDisk must be first made unmanaged by migrating or deleting the LUN from the storage pool.

LUN presentation

LUNs are exported through the available FC ports of the Hitachi HUS VM storage system. Configure these ports by host group.

Special LUNs

No special considerations are required for logical unit numbering. LUN 0 can be exported where necessary.

Target ports

A Hitachi HUS VM storage system has a total of eight Fibre Channel ports as shown in the following example.

  lscontroller 
id controller_name ctrl_s/n             vendor_id            product_id_low       product_id_high  
0  controller3     502029EB0001 4A      HITACHI              OPEN-V                                
1  controller2     502029EB0001 1A      HITACHI              OPEN-V                                
2  controller1     502029EB0001 2A      HITACHI              OPEN-V                                
3  controller0     502029EB0001 3A      HITACHI              OPEN-V        

 lscontroller 0 
id 0 
controller_name controller3 
WWNN 50060E801329EB30 
mdisk_link_count 15 
max_mdisk_link_count 15 
degraded no 
vendor_id HITACHI 
product_id_low OPEN-V   
product_id_high          
product_revision 7302 
ctrl_s/n 502029EB0001 4A      
allow_quorum yes                  (See section on Manual Quorum)
WWPN 50060E801329EB30 
path_count 8 
max_path_count 26

WWNN and WWPN in default settings appear identically. Hitachi HUS VM WWNNs appear as shown in the following example.

500060E8MMSSSSPP
50          -   NAA format 5, Vendor responsible for address
0060E8      -   ieee unique VSID of Hitachi Computer Products (America), inc.
MM          -   model range
SSSS        -   Hex for serial number
PP          -   Port Number

LU access model

All systems are Active/Active. To avoid an outage from system failure, cross connect the ports across Fibre Channel switches. Because all model Hitachi HUS VM storage systems are equal in priority, no benefit is received by using an exclusive set for a specific LU.

LU grouping

LU grouping does not apply to Hitachi HUS VM systems.

LU preferred access port

The model Hitachi HUS VM has no preferred access ports as all ports are Active/Active across all systems.

LUN security

LUN Security enables LUN masking by the worldwide node name (WWNN) of the initiator port. This function is used for logical units (LUs) that are used by SAN Volume Controller systems.

Detecting Ownership

Detecting ownership does not apply to model Hitachi HUS VM storage arrays.