The hardware conditions described in the table below must be met when using Resource Orchestrator.
Hardware Condition of Storage that can be Connected with Physical L-Server
When connecting storage units to the physical servers of L-Servers, the following storage units can be used:
Hardware | Remarks |
|---|---|
ETERNUS DX8900 S3 | Thin provisioning is available for the following storage units:
For the following apparatuses, when disk resources are created with Resource Orchestrator, set the alias (if possible) based on the disk resource name in the LUN.
On ETERNUS other than the above, the alias name is set as previously, that is the default value set on the ETERNUS. For the following apparatuses, if an alias has been set for the LUN, the alias name is displayed.
Dynamic LUN mirroring can be used with Resource Orchestrator with the following apparatuses.
When using the target units for the following options, Automatic Storage Layering can be used with Resource Orchestrator.
For the following devices, you should register devices to ETERNUS SF Storage Cruiser manager using the IP address in IPv4 form.
|
ETERNUS4000 series | Model 80 and model 100 are not supported. |
ETERNUS2000 series | When an alias name is configured for a LUN, the alias name is displayed. |
NetApp FAS6000 series | Data ONTAP 7.3.3 or later |
EMC CLARiiON CX4-120 | Navisphere Manager and Access Logix must be installed on SP. |
EMC Symmetrix DMX-3 | VolumeLogix must be installed on SP. |
Storage Server on which FalconStor NSS operates | It should be a model on which FalconStor guarantees the operation of FalconStor NSS.
|
Storage unit connected with Storage Server on which FalconStor NSS operates | It should be a model on which FalconStor guarantees the operation of FalconStor NSS. |
Fiber channel switch connected with Storage Server on which FalconStor NSS operates | It should be a model on which FalconStor guarantees the operation of FalconStor NSS. |
When using storage management software, do not change or delete the content set for storage units by Resource Orchestrator.
When connecting storage units to the physical servers of L-Servers, the following Fibre Channel switches can be used:
Hardware | Remarks |
|---|---|
Brocade series | - |
PRIMERGY BX600 Fibre Channel switch blades | Connect fibre channel switch blades to the following connection blades:
|
PRIMERGY BX900 Fibre Channel switch blades | Connect fibre channel switch blades to the following connection blades:
|
PRIMERGY BX400 Fibre Channel switch blades | Connect fibre channel switch blades to the following connection blades:
|
Hardware Conditions of Storage that can be Connected to Virtual L-Servers
When connecting storage units to virtual L-Servers, the following storage units can be used:
[VMware]
Refer to "Supported Storage Configurations" in "E.1.3 Storage Preparations" in the "Design Guide CE".
[Hyper-V]
Refer to "Supported Storage Configurations" in "E.2.3 Storage Preparations" in the "Design Guide CE".
[Xen]
Refer to "Supported Storage Configurations" in "E.3.3 Storage Preparations" in the "Design Guide CE".
[OVM for x86 2.2]
Refer to "Supported Storage Configurations" in "E.4.3 Storage Preparations" in the "Design Guide CE".
[KVM]
Refer to "Supported Storage Configurations" in "E.5.3 Storage Preparations (SAN Configurations)" in the "Design Guide CE".
[Solaris Zones]
Refer to "Supported Storage Configurations" in "E.6.3 Storage Preparations" in the "Design Guide CE".
[OVM for SPARC]
Refer to "Supported Storage Configurations" in "E.7.3 Storage Preparations" in the "Design Guide CE".
[Citrix Xen]
Refer to "Supported Storage Configurations" in "E.8.3 Storage Preparations" in the "Design Guide CE".
[OVM for x86 3.x]
Refer to "Supported Storage Configurations" in "E.8.3 Storage Preparations" in the "Design Guide CE".
Network Hardware Conditions When Using Simplifying of Network Settings
Refer to the following sections for the LAN switch blades that are available when using simplifying of network settings:
Physical L-Server
"7.3.1 Automatic Network Configuration" in the "Setup Guide CE"
Virtual L-Server
"8.2.4 Automatic Network Configuration" in the "Setup Guide CE"
"8.3.4 Automatic Network Configuration" in the "Setup Guide CE"
Hardware | Version | Functions | |||
|---|---|---|---|---|---|
Status Monitoring | Network Device Automatic Configuration | Network Device Configuration File Management | |||
L2 switches (*1) | Fujitsu SR-X 300 series | V01 or later | Yes | Yes | Yes |
Cisco Catalyst 2900 series | IOS 12.2 or later | Yes | Yes | Yes | |
Cisco Nexus 5000 series (*3) | NX-OS V5.2 | Yes | Yes | Yes | |
Brocade VDX 6710 series | NOS 2.0 or later | Yes | Yes (*4) | No | |
Ethernet Fabric | Fujitsu PRIMERGY Converged Fabric Switch Blade (10 Gbps 18/8+2) (*5) | V01.00 or later | Yes | Yes | No |
Fujitsu Converged Fabric Switch (*5) | V01.00 or later | Yes | Yes | No | |
Brocade VDX 6710 series | NOS4.0 or later (*7) | Yes | No | No | |
Firewall (*2) | Fujitsu IPCOM EX IN series | E20L10 or later | Yes | Yes | Yes |
Fujitsu IPCOM VA LS series | E20L21NF0301 or later | Yes | Yes (*8) | Yes | |
Fujitsu NS Appliance (*9) | - | Yes | Yes | Yes | |
Cisco ASA 5500 series (*10) | ASASoftware-8.3 or later | Yes | Yes | Yes | |
Server load balancer (*2) | Fujitsu IPCOM EX IN series | E20L10 or later | Yes | Yes (*11) | Yes |
Fujitsu IPCOM VA LS series | E20L21NF0301 or later | Yes | Yes (*12) | Yes | |
Fujitsu NS Appliance (*9) | - | Yes | Yes | Yes | |
F5 Networks BIG-IP Local Traffic Manager series | BIG-IP V11.2 | Yes | Yes | Yes | |
Management host | Fujitsu IPCOM VX series | E10L11 or later | Yes | No | No |
Yes: Use possible.
No: Use not possible.
*1: L2 switches are essential in the following cases.
When placing an L2 switch between a firewall and rack mount or tower servers
When placing an L2 switch between a firewall and LAN switch blades
When placing an L2 switch between a firewall and server load balancer
When placing an L2 switch between a server load balancer and a rack mount or tower server
*2: Necessary when placing a firewall or a server load balancer on an L-Platform.
*3: Nexus 2000 series (except Nexus B22 Blade Fabric Extender) connected to Nexus 5000 series using a fabric interface are used as part of Nexus5000series (module related).
*4: Sample scripts for automatic configuration and operation are not provided. It is necessary to create the rulesets for configuring definitions.
*5: Network mode and host mode are supported as the operation mode.
*6: 100 GbE ports cannot be displayed.
*7: NOS4.1.2ac is not supported.
*8: Sample scripts are supported by E20L30NF0201 or later. Sample scripts for automatic configuration are not available for the IPCOM VA SC series. It is necessary to create the rulesets for configuring definitions.
*9: This is not a hardware product but a software appliance.
For details on the hardware environment on which this software appliance can operate, refer to "1.4 Hardware Environment" in the "NS Option Instruction".
*10: Cisco ASA5505 is not supported.
*11: Sample scripts for automatic configuration and operation are not provided for the IPCOM EX LB series. It is necessary to create the rulesets for configuring definitions.
*12: Sample scripts are supported by E20L30NF0201 or later. Sample scripts for automatic configuration are not available for the IPCOM VA LB series. It is necessary to create the rulesets for configuring definitions.
In addition, an L3 switch is necessary when using a separate admin LAN network for each tenant.
