Top
ServerView Resource Orchestrator Cloud Edition V3.3.0 Design Guide
FUJITSU Software

D.3.5 When Using EMC CLARiiON Storage or EMC VNX Storage

This section explains how to configure EMC CLARiiON storage or EMC VNX Storage.


EMC CLARiiON Storage or EMC VNX Storage Configuration

Resource Orchestrator controls EMC CLARiiON storage or EMC VNX Storage through EMC Navisphere Manager.

A user ID and a password are required to use EMC Navisphere Manager.

For details on how to add a user ID, refer to the EMC Navisphere Manager manual.

In order to enhance communication security between Resource Orchestrator and EMC Navisphere Manager, security files are used for issuing Navisphere CLIs.

Create security files in the following directories of the server on which Resource Orchestrator is installed, using the command to create security files.

[Windows Manager]
Installation_folder\SVROR\Manager\etc\storage\emc\xxx.xxx.xxx.xxx (*)

[Linux Manager]
/etc/opt/FJSVrcvmr/storage/emc/xxx.xxx.xxx.xxx (*)

* Note: IP address of SP for EMC CLARiiON storage or EMC VNX Storage.
When there are multiple EMC CLARiiON units and EMC VNX units, create multiple directories.

For the user ID to execute commands to create security files, set SYSTEM for Windows, or root for Linux.

Use the following procedure to execute the command for SYSTEM users on Windows.

Information

For details on how to create security files, refer to the explanation of "-AddUserSecurity" switches of Navisphere CLI.

Note

  • The following settings are not configured in Resource Orchestrator. Therefore, configure these settings beforehand.

    • Define Hot Spares

    • Define RAID Groups

    • Create Traditional LUNs

    • Define Storage Pools

    • Create Thin LUNs and Thick LUNs

  • For details on how to create RAID Groups, Traditional LUNs, Storage Pools, Thin LUNs, and Thick LUNs, refer to the manual of EMC CLARiiON storage or EMC VNX Storage.

  • Existing RAID Groups are also recognized as virtual storage, but RAID Groups are not recognized when they are used as hot spares.

  • It is not necessary to create a Storage Group which defines LUN masking (LUN mapping), as one is automatically created when creating an L-Server.

  • When installing an OS and a multipath driver, it is necessary to make only one access path from the server to the storage.

  • It is necessary to install Resource Orchestrator and Navisphere CLI on the same server.

  • Only Fibre channel connections using FC ports (target mode) are supported.

  • The connection form to FC ports only supports fabric connections.

  • For EMC CLARiiON storage or EMC VNX Storage, after installing Resource Orchestrator it is necessary to create definition files combining ports for SAN storage.

  • When there are two or more SPs in EMC CLARiiON storage or EMC VNX Storage, access from the L-Server to the LUN can be performed using multiple paths.

    Even when an SP fails, access from the L-Server to the LUN can be continued using the remaining SPs.

  • To use resources of EMC CLARiiON storage or EMC VNX Storage, it is necessary to register the storage management product with this product using the "rcxadm storagemgr register" command. Even when there are multiple SPs in one EMC CLARiiON storage or EMC VNX Storage device, it is necessary to specify the IP address of one SP of the EMC CLARiiON storage or EMC VNX Storage device for the IP address used to control the storage management product.

    If the selected SP fails, it becomes impossible to create, delete, and attach or detach disks of the physical L-Server that uses the LUN of the EMC CLARiiON storage or EMC VNX Storage device. Request restoration of the SP by the storage manager.

Information

When creation of physical L-Servers or addition of disks to physical L-Servers is performed, storage groups are created for the EMC CLARiiON storage or EMC VNX storage in each L-Server.

The format of storage group names is as follows.

L-Server name (From the 1st character to the 55th character) + "_" + Part of HBA WWPN of Managed Server

Example

L-Server name

HBA WWPN of Managed Server

Storage Group Name

Sample
21:00:00:17:42:50:00:c8
22:00:00:17:42:50:00:c8
Sample_005000c8

When connecting EMC CLARiiON storage or EMC Symmetrix VNX storage to fibre channel switches

In Resource Orchestrator, when connecting EMC CLARiiON storage or EMC VNX Storage, fibre channel switches are not configured.

It is necessary to configure one-to-one WWPN zoning for Fibre Channel switches in advance.

It is necessary to define zoning combining the fibre channel switch combining the HBA Port WWPN value based on the WWN provided by the I/O Virtualization Option and the SP port WWPN value in the EMC CLARiiON storage or EMC VNX Storage used in Resource Orchestrator. For details on the configuration method, refer to the manual of the fibre channel switch.


Fibre Channel Switch Zoning Settings

Set zoning combining the WWPN value of HBA Port1 and the WWPN value of the first SP port defined in the storage_portset.rcxprop definition file, and combining the WWPN value of HBA Port2 and the WWPN value of the second SP port defined in portset.

Examples of command execution for an ETERNUS SN200 are as follows:

In the following examples, 64 patterns of zoning are performed using combination of 16 WWN and 4 SP ports.

Example

Conditions

  • WWN value provided by the I/O Virtualization Option

    "20:00:00:17:42:51:00:0x"

  • WWPN value of HBA Port1

    "9:00:00 PM:17:42:51:00:0x"

  • WWPN value of HBA Port2

    "10:00:00 PM:17:42:51:00:0x"

  • Content of the definition file "storage_portset.rcxprop"

    192.168.1.24,"SPAPort0:SPBPort0","SPAPort1:SPBPort1"

  • WWPN value of SP port "SPAPort0"

    "50:0a:09:81:88:bc:43:dc"

  • WWPN value of SP port "SPBPort0"

    "50:0a:09:82:88:bc:43:dc"

  • WWPN value of SP port "SPAPort1"

    "50:0a:09:83:88:bc:43:dc"

  • WWPN value of SP port "SPBPort1"

    "50:0a:09:84:88:bc:43:dc"

zoneCreate "emc_a_0","50:0a:09:81:88:bc:43:dc;21:00:00:17:42:51:00:00" <RETURN>
zoneCreate "emc_b_0","50:0a:09:82:88:bc:43:dc;22:00:00:17:42:51:00:00" <RETURN>
...
zoneCreate "emc_a_f","50:0a:09:81:88:bc:43:dc;21:01:00:17:42:50:00:0f" <RETURN>
zoneCreate "emc_b_f","50:0a:09:82:88:bc:43:dc;22:01:00:17:42:50:00:0f" <RETURN>
zoneCreate "emc_c_0","50:0a:09:83:88:bc:43:dc;21:00:00:17:42:51:00:00" <RETURN>
zoneCreate "emc_d_0","50:0a:09:84:88:bc:43:dc;22:00:00:17:42:51:00:00" <RETURN>
...
zoneCreate "emc_c_f","50:0a:09:83:88:bc:43:dc;21:01:00:17:42:50:00:0f" <RETURN>
zoneCreate "emc_d_f","50:0a:09:84:88:bc:43:dc;22:01:00:17:42:50:00:0f" <RETURN>
cfgCreate "ror_cfg","emc_a_0;emc_b_0; ... ;emc_a_f;emc_b_f;emc_c_0;emc_d_0; ... ;emc_c_f;emc_d_f" <RETURN>
cfgEnable "ror_cfg" <RETURN>
cfgSave <RETURN>