1.5 Hardware Environment

The hardware conditions described in the table below must be met when using Resource Orchestrator.

Table 1.59 Required Hardware
Software	Hardware	Remarks
Manager	PRIMERGY BX series servers PRIMERGY RX series servers PRIMERGY TX series servers	The CPU must be a multi-core CPU. 10 GB or more of memory is necessary.
Agent	PRIMERGY BX620 S4 PRIMERGY BX620 S5 PRIMERGY BX620 S6 PRIMERGY BX920 S1 PRIMERGY BX920 S2 PRIMERGY BX922 S2 PRIMERGY BX924 S2 PRIMERGY BX960 S1 PRIMERGY RX100 S5 PRIMERGY RX100 S6 PRIMERGY RX200 S4 PRIMERGY RX200 S5 PRIMERGY RX200 S6 PRIMERGY RX300 S4 PRIMERGY RX300 S5 PRIMERGY RX300 S6 PRIMERGY RX600 S4 PRIMERGY RX600 S5 PRIMERGY RX900 S1 PRIMERGY TX150 S6 PRIMERGY TX150 S7 PRIMERGY TX200 S5 PRIMERGY TX200 S6 PRIMERGY TX300 S4 PRIMERGY TX300 S5 PRIMERGY TX300 S6 PRIMEQUEST 1000 series servers Other PC servers	When using servers other than PRIMERGY BX servers Only configurations where Fibre Channel cards are mounted in expansion slot 2 are supported. When using servers other than PRIMERGY BX servers It is necessary to mount an IPMI-compatible (1) server management unit (2). For Physical L-Servers The following servers cannot be used: PRIMERGY TX series servers PRIMERGY RX100 series servers PRIMEQUEST 1000 series servers Other PC servers When using RHEL5-Xen as the server virtualization software Only PRIMEQUEST 1000 series servers are supported for managed servers. When using physical L-Servers for iSCSI boot PRIMERGY BX900 and VIOM are required. When the destination of a physical L-Server is a PRIMERGY BX920 series or BX922 series server and LAN switch blades (PG-SW109 or PG-SW201) are mounted in CB1 and CB2, only NIC1 and NIC2 can be used.

*1: Supports IPMI 2.0.
*2: This usually indicates a Baseboard Management Controller (hereinafter BMC). For PRIMERGY, it is called an integrated Remote Management Controller (hereinafter iRMC).

The following hardware is required for admin clients:

Table 1.60 Required Hardware for Admin Clients
Software	Hardware	Remarks
Client	Personal computers PRIMERGY RX series servers PRIMERGY BX series servers PRIMERGY TX series servers Other PC servers	-

When connecting storage units that can be connected to the physical servers of L-Servers, the following storage units can be used:

Table 1.61 Storage Units that can be Connected with L-Servers on Physical Servers
Hardware	Remarks
ETERNUS DX8000 series ETERNUS DX8000 S2 series ETERNUS DX400 series ETERNUS DX400 S2 series ETERNUS DX90 S2 ETERNUS DX90 ETERNUS DX80 S2 ETERNUS DX80 ETERNUS DX60 S2 ETERNUS DX60 ETERNUS8000 series	Thin provisioning is available for the following storage units: ETERNUS DX8000 series ETERNUS DX8000 S2 series ETERNUS DX400 series ETERNUS DX400 S2 series ETERNUS DX90 S2 ETERNUS DX80 S2 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. ETERNUS DX8000 S2 series ETERNUS DX400 S2 series ETERNUS DX90 S2 ETERNUS DX80 S2 ETERNUS DX60 S2 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. ETERNUS DX8000 series ETERNUS DX8000 S2 series ETERNUS DX400 series ETERNUS DX400 S2 series ETERNUS DX90 S2 ETERNUS DX90 ETERNUS DX80 S2 ETERNUS DX80 ETERNUS DX60 S2 ETERNUS DX60 Dynamic LUN mirroring can be used with Resource Orchestrator with the following apparatuses. ETERNUS DX8000 S2 series ETERNUS DX410 S2 ETERNUS DX440 S2 ETERNUS DX90 S2 When using the target units for the following options, Automatic Storage Layering can be used with Resource Orchestrator. ETERNUS SF Storage Cruiser V15 Optimization Option
ETERNUS4000 series	Model 80 and model 100 are not supported. Thin provisioning is not available for this series.
ETERNUS2000 series	When an alias name is configured for a LUN, the alias name is displayed.
NetApp FAS6000 series NetApp FAS3100 series NetApp FAS2000 series NetApp V6000 series NetApp V3100 series	Data ONTAP 7.3.3 or later Data ONTAP 8.0.1 7-Mode
EMC CLARiiON CX4-120 EMC CLARiiON CX4-240 EMC CLARiiON CX4-480 EMC CLARiiON CX4-960 EMC CLARiiON CX3-10 EMC CLARiiON CX3-20 EMC CLARiiON CX3-40 EMC CLARiiON CX3-80	Navisphere Manager and Access Logix must be installed on SP.
EMC Symmetrix DMX-3 EMC Symmetrix DMX-4 EMC Symmetrix VMAX	VolumeLogix must be installed on SP.

When using storage management software, do not change or delete the content set for storage units by Resource Orchestrator. Insufficient disk space does not cause any problems for RAID group or aggregate creation.

When connecting storage units that can be connected to the physical servers of L-Servers, the following Fibre Channel switches can be used:

Table 1.62 Fibre Channel Switches which can be used when Connecting ETERNUS Storage, NetApp Storage, EMC CLARiiON Storage, and EMC Symmetrix DMX Storage with L-Servers on Physical Servers
Hardware	Remarks
Brocade series ETERNUS SN200 series	-
PRIMERGY BX600 Fibre Channel switch blades	Connect fibre channel switch blades to the following connection blades: NET3, NET4
PRIMERGY BX900 Fibre Channel switch blades	Connect fibre channel switch blades to the following connection blades: CB5, CB6
PRIMERGY BX400 Fibre Channel switch blades	Connect fibre channel switch blades to the following connection blades: CB3, CB4

Refer to the following sections for the LAN switch blades that are available when using simplifying of network settings:

Physical L-Server
"D.6.1 Automatic Network Configuration"
Virtual L-Server
- "E.2.5 Setup"
- "E.3.4 Setup"

Table 1.63 Supported Network Devices
Hardware		Version
L2 switches (*1)	Fujitsu SR-X 300 series Fujitsu SR-X 500 series	V01 or later
L2 switches (*1)	Cisco Catalyst 2900 series Cisco Catalyst 2918 series Cisco Catalyst 2928 series Cisco Catalyst 2940 series Cisco Catalyst 2950 series Cisco Catalyst 2955 series Cisco Catalyst 2960 series Cisco Catalyst 2970 series Cisco Catalyst 2975 series Cisco Catalyst 3500 series Cisco Catalyst 3550 series Cisco Catalyst 3560 series Cisco Catalyst 3750 series	IOS 12.2 or later
Firewall (*2)	Fujitsu IPCOM EX IN series Fujitsu IPCOM EX SC series	E20L10 or later
Firewall (*2)	Cisco ASA 5500 series	ASASoftware-8.3 or later

*1: L2 switches are necessary 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

*2: Necessary when placing a firewall on an L-Platform.

In addition, an L3 switch is necessary when using a separate admin LAN network for each tenant.