Top
ServerView Resource Orchestrator Cloud Edition V3.1.1 Design Guide
ServerView

D.3.7 When Using Storage Server that operates FalconStor NSS

This section explains how to configure Storage Server that operates FalconStor NSS.


Configuration of Storage Server that operates FalconStor NSS

Resource Orchestrator controls FalconStor NSS through SAN Client CLI installed in management server.

FalconStor NSS controls Storage Server and the storage unit connected with Storage Server.

Therefore, user ID and the password to use FalconStor NSS are necessary.

Type of user ID is "IPstor Admin" or "IPStor User" (User that manages storage device to be used with this product) should.

For details on how to add a user ID, refer to the FalconStor NSS manual.

Note

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

    • Define Physical Devices(for Virtual Device)

    • Define Storage Pools(for Virtual Device)

    • Create Virtual Devices

    For details on how to perform configuration, refer to the FalconStor NSS manual.

  • The following are recognized as virtual storage in this product.

    • Physical Device(for Virtual Device) not registered in Storage Pool

    • Storage Pool(for Virtual Device)

  • The following are recognized as disk in this product.

    • Virtual Device made from one PhysicalDevice (for Virtual Device)

  • Physical Device(for Service Enabled Device) is not recognized.

  • Storage Pool(for Service Enabled Device) is not recognized.

  • Physical Device (for Virtual Device) registered in Storage Pool is not recognized.

  • Virtual Device made from two or more Physical Device (for Virtual Device) is not recognized.

  • Service Enabled Device is not recognized.

  • Please do not execute the following configuration changes thereafter at the time of began the management of Storage Server that FalconStor NSS operates by this product.

    • Registration or deregistration to StoragePool of Physical Device for which Virutal Device is made

  • It is not necessary to define LUN masking (LUN mapping), as one is automatically defined 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 SAN Client CLI on the same server.

  • As for Storage Server and the storage device, it is iscsi connection or should be the FC connections (FC-AL or Fabric).

  • The connection of Storage Server and managed server supports only the fiber channel attached using FC port (target mode).

  • Connection type of Storage Server and managed server supports only the fabric connection.

  • It should be additionally within two of NSS target port and NSS dual port of Storage Server.

    When the disk is connected, it becomes an error in case of 3 pieces or more.

  • Storage Server supports two or more NIC. It is recommended to make it tediously by using bonding.

When Connecting Storage Server that operates FalconStor NSS to Fibre Channel Switches

In Resource Orchestrator, when connecting Storage Server that operates FalconStor NSS, Fibre Channel switches are not configured.

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

You should execute the zoning (WWN value provided by the I/O Virtualization Option(Up to two) and combination of WWPN value of NSS target port(or NSS dual port)(Up to two)) to the fiber channel switch.

For details on the configuration method, refer to the manual of the fibre channel switch.


Fibre Channel Switch Zoning Settings

When Storage Server that operates FalconStor NSS is connected with the fiber channel switch, it is necessary to set the following zonings.

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

Example

Conditions

  • WWN value provided by the I/O Virtualization Option

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

  • WWPN value of HBA Port1

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

  • WWPN value of HBA Port2

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

  • WWPN value of the first NSS target port(or NSS dual port)

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

  • WWPN value of the second NSS target port(or NSS dual port)

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

Command Example

zoneCreate "nss_1_1_0","50:0a:09:81:88:bc:43:dc;21:00:00:17:42:51:00:00"
zoneCreate "nss_2_1_0","50:0a:09:82:88:bc:43:dc;21:00:00:17:42:51:00:00"
zoneCreate "nss_1_2_0","50:0a:09:81:88:bc:43:dc;22:00:00:17:42:51:00:00"
zoneCreate "nss_2_2_0","50:0a:09:82:88:bc:43:dc;22:00:00:17:42:51:00:00"

...
zoneCreate "nss_1_1_f","50:0a:09:81:88:bc:43:dc;21:00:00:17:42:51:00:0f"
zoneCreate "nss_2_1_f","50:0a:09:82:88:bc:43:dc;21:00:00:17:42:51:00:0f"
zoneCreate "nss_1_2_f","50:0a:09:81:88:bc:43:dc;22:00:00:17:42:51:00:0f"
zoneCreate "nss_2_2_f","50:0a:09:82:88:bc:43:dc;22:00:00:17:42:51:00:0f"
cfgCreate "ror_cfg","nss_1_1_0;nss_2_1_0; nss_1_2_0;nss_2_2_0; ... ; nss_1_1_f;nss_2_1_f; nss_1_2_f;nss_2_2_f"
cfgEnable "ror_cfg"
cfgSave