The hardware conditions described in the table below must be met when using Resource Orchestrator.
Required Hardware Conditions for Managers
Hardware | Remarks |
|---|---|
PRIMERGY BX series servers | The CPU must be a multi-core CPU. |
Required Hardware Conditions for Agents
Product Name | Model | VE | CE | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Physical L-Server | Virtual L-Server types [1] | ||||||||||||
vSphere 4.x/5.x/6 | Hyper-V | OVM x86 V2.2 | OVM x86 V3.x | OVM SPARC | SPARC Solaris Zones | Citrix XenServer | RHEL-Xen | RHEL-KVM | x86 Solaris Zones | ||||
PRIMERGY BX900 PRIMERGY BX900 S2 | BX920 S1 | Y | Y | Y | Y | -- | Y | / | / | Y | -- | Y | -- |
BX2560 M1 [5] [42] | Y | Y | Y | Y | -- | Y | / | / | Y | -- | Y | -- | |
BX2580 M1 [5] [44] | Y | Y | Y | Y | -- | Y | / | / | Y | -- | Y | -- | |
PRIMERGY BX400 | BX920 S2 | Y | Y | Y | Y | -- | Y | / | / | Y | -- | Y | -- |
BX2560 M1 [5] [42] | Y | Y | Y | Y | -- | Y | / | / | Y | -- | Y | -- | |
BX2580 M1 [5] [44] | Y | Y | Y[15] | Y | -- | Y | / | / | Y | -- | Y | -- | |
PRIMERGY BX600 | BX620 S4 | Y | -- | Y | Y | -- | Y | / | / | Y | -- | Y | -- |
PRIMERGY RX | RX100 S5 [29] | Y | -- | Y | Y | -- | Y | / | / | Y | -- | Y | -- |
RX100 S7 [29] | -- | -- | -- | -- | -- | -- | / | / | -- | -- | -- | -- | |
RX900 S1 | -- | -- | -- | -- | -- | -- | / | / | -- | -- | -- | -- | |
RX200 S4 | Y | Y | Y | Y | -- | Y | / | / | Y | -- | Y | -- | |
RX200 S7 | Y | Y | Y | Y | -- | Y | / | / | Y | -- | Y | -- | |
RX350 S7 | -- | -- | -- | -- | -- | -- | / | / | -- | -- | -- | -- | |
RX200 S8 | Y | Y | Y | Y | -- | Y | / | / | Y | -- | Y | -- | |
RX2520 M1 | Y | Y | Y | Y | -- | -- | / | / | Y | -- | Y | -- | |
RX2530 M1 | Y | Y | Y | Y | -- | -- | / | / | -- | -- | Y | -- | |
RX2530 M2 [51] | Y | Y | Y | Y | -- | -- | / | / | -- | -- | -- | -- | |
RX4770 M1 [35] | Y | -- | Y | Y | -- | Y | / | / | -- | -- | -- | -- | |
RX4770 M2 [51] | Y | Y | Y | Y | -- | -- | / | / | -- | -- | -- | -- | |
RX1330 M1 | -- | -- | -- | -- | -- | -- | / | / | -- | -- | -- | -- | |
PRIMERGY TX | TX150 S6 [29] | Y | -- | -- | -- | -- | -- | / | / | -- | -- | -- | -- |
TX150 S8 [29] | -- | -- | -- | -- | -- | -- | / | / | -- | -- | -- | -- | |
TX1310 M1 | -- | -- | -- | -- | -- | -- | / | / | -- | -- | -- | -- | |
PRIMERGY CX1000 | CX122 S1 | Y | -- | -- | -- | -- | -- | / | / | -- | -- | -- | -- |
PRIMERGY CX400 | CX210 S1 | -- | -- | -- | -- | -- | -- | / | / | -- | -- | Y | -- |
CX2550M1 | Y | -- | Y | Y | -- | -- | / | / | -- | -- | -- | -- | |
x86 3rd party servers | IPMI2.0 compatible server [2] | -- | -- | -- | -- | -- | -- | / | / | -- | -- | -- | -- |
x86 3rd party servers - operations on physical servers (i.e. power on/off/status monitoring) are not supported | any VMware compatible server | / | / | -- | / | / | / | / | / | / | / | / | / |
PRIMEQUEST 1000series | 1400S | Y | -- | Y | Y | -- | -- | / | / | -- | Y | Y | -- |
PRIMEQUEST 2000series | 2400S Lite | Y | -- | Y | Y | -- | -- | / | / | -- | -- | Y | -- |
2400S2 Lite | Y | -- | Y | Y | -- | -- | / | / | -- | -- | Y | -- | |
SPARC Enterprise | M3000 | Y | -- | / | / | / | / | / | Y | / | / | / | / |
T5120 | Y | -- | / | / | / | / | -- | -- | / | / | / | / | |
SPARC | M10-1 | Y | -- | / | / | / | / | Y | Y | / | / | / | / |
T4-1 | Y | -- | / | / | / | / | -- | Y | / | / | / | / | |
T5-2 | -- | -- | / | / | / | / | -- | -- | / | / | / | / | |
Y : Supported
-- : Not supported.
/: Strike means the combination is not available
[1] For hardware compatibility with each VM software, please confirm the following sites:
VMware:http://www.vmware.com/resources/compatibility/search.php?action=base&deviceCategory=san
Hyper-V:http://www.windowsservercatalog.com/results.aspx?&chtext=&cstext=&csttext=&chbtext=&bCatID=1333&cpID=14135&avc=10&ava=0&avq=0&OR=1&PGS=25&ready=0
OVM:http://linux.oracle.com/pls/apex/f?p=117:1:8516554786821630::NO:RP::
RHEL KVM:https://hardware.redhat.com/
[2] For 3rd party blade server, individual server management unit is necessary for each blade. ROR doesn't manage blade chassis. Each blade server is managed as an individual server.
The verified server modes are as follows:
IBM:System x3550
Dell PowerEdge 1950 III
HP: ProLiant DL 320/360/380, ProLiant BL685c G7"
Non-IPMI2.0 compatible server is not supported.
[4] To use physical L-Platform on a rack server, two-ports HBA daughter card is required.
[5] Note for BX920 S3/BX920 S4/BX924 S3/BX924 S4/BX2560 M1/BX2560 M2/BX2580 M1/BX2580 M2 blade
CNA LoM and mezzanine cards are supported, but UMC is supported only with the CNA LoM.
When the managed server OS is Windows, the following conditions are required
1) Install the required Microsoft patch file described below
https://partners.ts.fujitsu.com/sites/dmsp/Publications/Service-partner/SB-PRI-12043.pdf
[7] This note is effective only in Japan. http://jp.fujitsu.com/platform/server/primergy/software/vmware/pdf/esx-s.pdf
[8] This note is effective only in Japan. http://jp.fujitsu.com/platform/server/primequest/os/vmware/
[9] This note is effective only in Japan. http://jp.fujitsu.com/platform/server/primequest/os/windows/
[10] This note is effective only in Japan. http://jp.fujitsu.com/platform/server/primergy/software/windows/support/
[11] This note is effective only in Japan. http://pr.fujitsu.com/jp/news/2012/10/29.html
[13] This note is effective only in Japan. http://jp.fujitsu.com/platform/server/primequest/os/linux/
[14] L-Server/L-Platform functions are not supported.
[15] This note is effective only in Japan. http://jp.fujitsu.com/platform/server/primergy/software/primergy-os/pdf/primergy-os.pdf
[16] V6.00.09 is required when using ROR3.1.0. For ROR3.1.1, all versions described in the support matrix are supported.
[22] The following editions are supported.
vSphere 4: Advanced, Enterprise, Enterprise+.
vSphere 5: Standard, Enterprise, Enterprise Plus, Essentials Kit, Essentials Plus Kit.
vSphere 6: Standard, Enterprise, Enterprise Plus, Essentials Kit, Essentials Plus Kit."
[28] SVOM7.01.03 or later and VIOM3.5.2 or later are required for RX2530 M1 and RX2540M1.
[29] HBA address rename is not supported.
[30] HBA address rename is not supported.
[31] HBA address rename is not supported.
[33] Windows Server 2008 R2 Hyper-V, Windows Server 2012 Hyper-V, Windows Server 2012 R2 Hyper-V
[35] VIOM and HBA address rename cannot be used. It is scheduled to be corrected after April , 2016.
[41] SVOM6.31.04 or later and VIOM3.3.08 or later are required for server switch over of ESXi hosts on RX2520 M1.
[42] SVOM7.00.05 or later and VIOM3.4.06 or later are required for BX2560 M1.
[43] Everything from V6.30.05 of SVOM to V6.31.05 cannot be used for an ESXI hosts.
[44] SVOM7.01.01 or later and VIOM3.4.06 or later are required for BX2580 M1.
[45] EP function is not supported.
[46] VIOM cannot be used.
[47] The following image operations are not supported for physical server.
Backup and Restore
Cloning Image Operations
[51] Linux ROR manager is not supported.
[52] In system configurations where port expansion options or CNA cards with Universal Multi-Channel (UMC) functions are mounted, it is not possible to create physical L-Servers (including physical L-Server creation in L-Platform deployment).
Note
When using servers other than PRIMERGY BX servers
It is necessary to mount an IPMI-compatible (*1) server management unit (*2).
*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).
When using HBA address rename [Virtual Edition]
The "I/O virtualization option" is required.
FT model servers are not supported. [Virtual Edition]
For Physical L-Servers [Cloud Edition]
The following servers cannot be used:
PRIMERGY TX series servers
PRIMERGY RX100 series servers
PRIMEQUEST 1000 series servers
PRIMEQUEST 2000 series servers
Other PC Servers
When using physical L-Servers for iSCSI boot [Cloud Edition]
VIOM is required.
iSCSI boot using CNA cannot be used. Use a NIC that is not a CNA.
When configuring the UMC function (expansion of function numbers) for the onboard Converged Network Adapter on a physical L-Server, it is necessary to connect with the following LAN switch blade. No other switches are supported. [Cloud Edition]
LAN switch blade PY CB Eth Switch/IBP 10Gb 18/8
When using the CNA UMC (Universal Multi-Channel) function
Resource Orchestrator can only use Function 0 of each port on CNA.
The UMC functions can only be used for the onboard CNA of the following hardware.
PRIMERGY BX920 S3
PRIMERGY BX920 S4
PRIMERGY BX924 S3
PRIMERGY BX924 S4
PRIMERGY BX2560 M1
PRIMERGY BX2560 M2
PRIMERGY BX2580 M1
PRIMERGY BX2580 M2
iSCSI and FCoE cannot be used as the Type of a Function.
Registration of the physical servers and physical L-Servers which use the UMC function as a VM host is not supported.
The MMB must be one of the following versions:
When using BX400 chassis, the version must be 6.73 or later.
When using BX900 chassis, the version must be 5.41 or later.
DR switchover and failback are not supported. [Cloud Edition]
The NS Option cannot be used. [Cloud Edition]
When the destination of a physical L-Server is a PRIMERGY BX920 series or BX922 series server and LAN switch blades (PY-SWB104(PG-SW109) or PY-SWB101(PG-SW201)) are mounted in CB1 and CB2, only NIC1 and NIC2 can be used. [Cloud Edition]
Rack mount servers supported by VIOM are the following:
PRIMERGY RX200 S7 or later
PRIMERGY RX300 S7 or later
PRIMERGY RX2520 M1 or later
PRIMERGY RX2530 M1 or later
PRIMERGY RX2540 M1 or later
PRIMERGY RX4770 M2 or later
When using the PRIMEQUEST 2000 series, the following server virtualization software are not supported.
VMware vSphere 4.1 or earlier
RHEL5-Xen [Virtual Edition]
Citrix XenServer
OVM for x86 2.2 [Cloud Edition]
When using the PRIMEQUEST series, RHEL7 is not supported.
When using RHEL5-Xen as the server virtualization software [Cloud Edition]
Only PRIMEQUEST 1000 series servers are supported for managed servers.
To use power consumption monitoring, the XCP version should be 1090 or later.
Virtual L-Servers can be deployed. [Cloud Edition]
For details, refer to "E.6 Solaris Zones" in the "Design Guide CE" and "8.7 Solaris Zones" in the "Setup Guide CE".
Configured virtual machines can be used by associating them with virtual L-Servers. [Cloud Edition]
Configured physical servers can be used by associating them with physical L-Servers. [Cloud Edition]
For details, refer to "Chapter 18 Linking L-Servers with Configured Physical Servers or Virtual Machines" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Servers can be managed. [Cloud Edition]
For details, refer to the "Design Guide VE".
The ILOM version should be 3.0 or later.
Configured physical servers can be used by associating them with physical L-Servers. [Cloud Edition]
For details, refer to "Chapter 18 Linking L-Servers with Configured Physical Servers or Virtual Machines" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Servers can be managed. [Cloud Edition]
For details, refer to the "Design Guide VE".
The XSCF version should be version XCP2010 or later. [Virtual Edition]
Virtual L-Servers can be deployed. [Cloud Edition]
For details, refer to the following:
"E.6 Solaris Zones" in the "Design Guide CE"
"E.7 OVM for SPARC" in the "Design Guide CE"
"8.7 Solaris Zones" in the "Setup Guide CE"
"8.8 OVM for SPARC" in the "Setup Guide CE"
Configured virtual machines can be used by associating them with L-Servers. [Cloud Edition]
Configured physical servers can be used by associating them with L-Servers. [Cloud Edition]
For details, refer to "Chapter 18 Linking L-Servers with Configured Physical Servers or Virtual Machines" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Servers can be managed. [Cloud Edition]
For details, refer to the "Design Guide VE".
Functions Available for Agents
The functions that agents can use differ depending on the hardware being used.
Functions | PRIMERGY Series Servers | PRIMEQUEST | Fujitsu M10/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, *3) | Yes | Yes | Yes (*14) | No | Yes (*15) | |
Hardware maintenance | Yes | Yes (*4) | Yes (*4) | No | Yes (*15) | |
Maintenance LED | Yes | No | No | No | No | |
External management software | Yes | Yes | Yes | Yes | No | |
Server switchover | Backup and restore method (*3) | Yes | Yes | No | No | Yes (*15) |
HBA address rename method (*3, *5) | Yes | Yes | No | No | No | |
VIOM server profile exchange method (*6) | Yes | Yes (*7) | No | No | No | |
Storage affinity switchover method | No | No | No | Yes (*8) | No | |
Cloning (*2, *3, *9) | Yes | Yes | Yes (*10) | No | Yes (*15) | |
HBA address rename (*3, *5) | Yes | Yes | No | No | No | |
VIOM coordination (*6) | Yes | Yes (*7) | No | No | No | |
VLAN settings | Yes | No | No | No | No | |
Pre-configuration | Yes | Yes | Yes | Yes | Yes | |
Power consumption monitoring | Yes (*11) | Yes (*12) | No | Yes (*13) | 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: When using backup and restore, cloning, or HBA address rename, the NIC (or LAN expansion board) must support PXE boot.
*4: Maintenance LEDs cannot be operated.
*5: When using HBA address rename, the mounted HBA must be compatible with HBA address rename. Only configurations in which up to two HBA ports are mounted on a single managed server are supported.
*6: ServerView Virtual-IO Manager is required.
*7: VIOM coordination is available only when using rack mount servers that are supported by VIOM.
*8: In the following cases, only configurations in which up to eight HBA ports are mounted on a single managed server are supported.
SPARC Enterprise M3000
SPARC Enterprise Partition Models without divided areas
Fujitsu M10-1/M10-4
Fujitsu M10-4S not in Building Block configurations
SPARC Enterprise T5120/T5140/T5220/T5240/T5440
For the list of functions by OS, refer to "Table: Functions Available for Each Target Operating System" in "2.2 Function Overview" in the "Design Guide VE".
*9: Cloning of Linux agents operating on iSCSI disks is not possible.
*10: Only PRIMEQUEST 1000 series servers are supported. Cloning is only available when Legacy boot is specified for the boot option. When UEFI is specified, cloning is unavailable.
*11: BX900 S1 chassis and BX920 S1, BX920 S2, BX920 S3, BX920 S4, BX2560 M1, BX2560 M2, BX922 S2, BX924 S2, BX924 S3, BX924 S4, BX2580 M1, BX2580 M2, and BX960 S1 servers are supported.
*12: Only rack mount models (RX200/300/600/2520/2530/2540/4770) are supported.
*13: Only SPARC Enterprise M3000 and Fujitsu M10-1/M10-4/M10-4S are supported.
*14: For the PRIMEQUEST 2000 series, backup and restore is only possible when using Windows managers. PXE boot is only supported by on-board LAN NICs.
*15: When using this function, contact Fujitsu technical staff.
Required Hardware for Admin Clients
The following hardware is required for admin clients:
Software | Hardware | Remarks |
|---|---|---|
Client | Personal computers | - |
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 | - |
