The hardware conditions described in the table below must be met when using Resource Orchestrator.
Required Hardware Conditions for Managers and Agents
Software | Hardware | Remarks |
|---|---|---|
Manager | PRIMERGY BX series servers | The CPU must be a multi-core CPU. |
Agent | PRIMERGY BX620 S4 |
|
SPARC Enterprise M series |
| |
SPARC Enterprise T5120 |
| |
HBA address rename setup service | Personal computers (*3) | - |
*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).
Note
The functions that agents can use differ depending on the hardware being used.
Function | PRIMERGY Series Servers | PRIMEQUEST | SPARC Enterprise | Other PC servers | ||
|---|---|---|---|---|---|---|
Blade Models | Rack Mount/Tower Models | |||||
Status monitoring | Yes | Yes | Yes | Yes | Yes (*1) | |
Power operations | Yes | Yes | Yes | Yes | Yes | |
Backup and restore (*2) | Yes | Yes | Yes | No | Yes | |
Hardware maintenance | Yes | Yes (*3) | Yes (*3) | No | Yes (*3) | |
Maintenance LED | Yes | No | No | No | No | |
External management software | Yes | Yes | Yes | Yes | No | |
Server switchover | Backup and restore method | Yes | Yes | No | No | Yes |
HBA address rename method (*4) | Yes | Yes | No | No | No | |
VIOM server profile exchange method | Yes (*5) | No | No | No | No | |
Storage affinity switchover method | No | No | No | Yes (*6) | No | |
Cloning (*2, *7) | Yes | Yes | Yes (*11) | No | Yes | |
HBA address rename (*4) | Yes | Yes | No | No | No | |
VIOM coordination | Yes (*5) | No | No | No | No | |
VLAN settings | Yes | No | No | No | No | |
Pre-configuration | Yes | Yes | Yes | Yes | Yes | |
Power consumption monitoring | Yes (*8) | Yes (*9) | No | Yes (*10) | No | |
Yes: Use possible.
No: Use not possible.
*1: Server monitoring in coordination with server management software is not possible.
*2: When agents are operating on iSCSI disks, image operations are not possible for the following disk configurations.
Perform operation using a single iSCSI disk configuration.
iSCSI disk + internal disk
iSCSI disk + SAN disk
*3: Maintenance LEDs cannot be operated.
*4: When using HBA address rename, the mounted HBA must be compatible with HBA address rename.
*5: ServerView Virtual-IO Manager is required.
*6: Only M3000 servers, SPARC Enterprise Partition Models and T5120/T5140/T5220/T5240/T5440 servers with undivided areas are supported. SPARC Enterprise Partition Models with divided areas are not supported.
*7: Cloning of Linux agents operating on iSCSI disks is not possible.
*8: Only BX900 S1 chassis and BX920 S1, BX920 S2, BX922 S2, BX924 S2, and BX960 S1 servers are supported.
*9: Only rack mount models (RX200/300/600) are supported.
*10: Only M3000 servers are supported.
*11: Cloning is available only when Legacy boot is specified for the boot option. When UEFI is specified, cloning is unavailable.
Required Hardware for Admin Clients
The following hardware is required for admin clients:
Software | Hardware | Remarks |
|---|---|---|
Client | Personal computers | - |
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 DX8000 series | 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.
|
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. |
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".
[Hyper-V]
Refer to "Supported Storage Configurations" in "E.2.3 Storage Preparations".
[Xen]
Refer to "Supported Storage Configurations" in "E.3.3 Storage Preparations".
[Oracle VM]
Refer to "Supported Storage Configurations" in "E.4.3 Storage Preparations".
[KVM]
Refer to "Supported Storage Configurations" in "E.5.3 Storage Preparations".
[Solaris Containers]
Refer to "Supported Storage Configurations" in "E.6.3 Storage Preparations".
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
"B.3.1 Automatic Network Configuration" in the "Setup Guide CE"
Virtual L-Server
"C.2.4 Automatic Network Configuration" in the "Setup Guide CE"
"C.3.4 Automatic Network Configuration" in the "Setup Guide CE"
Hardware | Version | |
|---|---|---|
L2 switches (*) | Fujitsu SR-X 300 series | V01 or later |
Cisco Catalyst 2900 series | IOS 12.2 or later | |
Cisco Nexus 2000 series (*3) | NX-OS V4.1 or later | |
Brocade VDX 6710 series (*3) | NOS 2.0 or later | |
Firewall (*2) | Fujitsu IPCOM EX IN series | E20L10 or later |
Fujitsu NS Appliance (*4) | - | |
Cisco ASA 5500 series (*5) | ASASoftware-8.3 or later | |
Server load balancer (*2) | Fujitsu IPCOM EX IN series | E20L10 or later |
F5 Networks BIG-IP Local Traffic Manager series | BIG-IP V11.2 | |
* Note: 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: Network device monitoring is supported but sample scripts for automatic configuration are not offered.
*4: This is not a hardware product but a virtual appliance.
*5: Cisco ASA5505 is not supported.
In addition, an L3 switch is necessary when using a separate admin LAN network for each tenant.
Hardware Conditions of Power Monitoring Devices
Hardware | Remarks |
|---|---|
Symmetra RM 4000VA | The firmware version of the network management card is v2.5.4 or v3.0 or higher |
Smart-UPS RT 10000 | - |
Smart-UPS RT 5000 | - |
