Server (Compute Systems Manager (HCSM) Target OS)
return to main contents page
return to "Management and monitoring target" contents page
Hardware Requirements
The following table lists the supported firmware versions for Hitachi Compute Blades and Hitachi Compute Rack servers.
Firmware versions - Hitachi Compute Blade and Rack-mounted Servers
Hardware name Management module version Management module version
Hitachi Compute Blade 500 SVP-FW
A0280 or later (*18)
(A0290 or later)(*21)
LP-FW 01-80 or later(*13)
(02-25 or later)(*15)
(02-27 or later)(*17)
Hitachi Compute Blade 2000 SVP-FW
A0365 or later(*13)
(A0375 or later)(*7)(*11)
LP-FW 59-60 or later(*13)
(59-70 or later)(*7)(*11)
Hitachi Compute Blade 2000 MP SVP-FW
A0365 or later(*13)
(A0375 or later)(*7)(*11)
LP-FW 79-60 or later(*13)
(79-70 or later)(*7)(*11)
Hitachi Compute Blade 2500 SVP-FW
A0145 or later  (*18)
(A0150 or later)(*21)
LP-FW 02-00 or later
(02-25 or later)(*15)
(02-27 or later)(*17)
Hitachi Compute Rack CR220HM
CR220SM
CR210HM
09.48 or later(*13)
(*7) If you display SR-IOV, use this firmware.
(*8) Server Name change function is not available for the following servers. 
      CB520Ax1, CB540Ax1, CB520Hx1(Server firmware less than 01-92), and CB520Hx2(Server firmware less than 04-22)
(*11) If you change SR-IOV settings, use this firmware.
(*12) If you manage chassis via IPv6 protocol, use this firmware.
(*13) HCSM V8.1.1 or later versions do not use SSLv3 in communications with managed Hitachi servers by default because of security vulnerabilities in the SSLv3 protocol.
        As a result, if communication with a management target by using SSLv3 is performed in a version of HCSM earlier than version 8.1.1, the communication will fail.
        Update to this firmware version so that HCSM can communicate with the hardware using TLS.
(*14) If you use Guest NUMA function, use this firmware.
(*15) If you use HBA Core Dedicated Mode, use this firmware.
(*16) If you use IOEU, use this firmware.
(*17)If you use LPAR Manager Enterprise licence, use this firmware.
(*18)The support firmware version changed for security vulnerabilities. Update to this firmware version so that HCSM can communicate with hardware.
(*21)Use the version of firmware within the described range for using LPAR Manager-FW version 02-45 or later.
Software requirements
This section provides system requirements for Management targets.
Note: You cannot use Blade servers with Hitachi Compute Blade logical partitioning or Blade servers running virtual machines with the N+M Cold Standby feature.
 If you configure N+M Cold Standby pairs with Blade servers using either of these features, the guest OSs are not shut down during N+M Failover and Failback tasks.
Operating system requirements
The following table lists the supported operating systems for management targets.
Supported management target OSs (Windows)
OS Name OS Version SP Architecture
Windows Server 2008(*4)(*5)(*11) Standard 32 bit Edition
Enterprise 32 bit Edition
Datacenter 32 bit Edition
Standard without Hyper-V 32 bit Edition
Enterprise without Hyper-V 32 bit Edition
Datacenter without Hyper-V 32 bit Edition
No SP x86
SP1 x86
SP2 x86
Standard Edition
Enterprise Edition
Datacenter Edition
Standard without Hyper-V Edition
Enterprise without Hyper-V Edition
Datacenter without Hyper-V Edition
No SP x64
SP1 x64
SP2 x64
Windows Server 2008 R2(*4)(*11)(*12) Standard
Enterprise
Datacenter
No SP x64
SP1 x64
Windows Server 2012(*9)(*11)(*12) Standard
Datacenter
No SP x64
R2 Standard or
R2 Datacenter
No SP x64
(*4) Server core isn't supported.
(*5) HCSM doesn't discover Hyper-V as Hypervisor.
(*9) Server core and Minimal Server Interface is not supported.
(*11) Master image deploy and snapshot is not supported in Hyper-V environments.
(*12) Deployment Manager's functions are not supported in native VHD boot environment.
Supported management target OSs (Linux)
OS Name OS Version SP Architecture
Red Hat Enterprise Linux
Red Hat Enterprise Linux Advanced Platform(*18)
5 - x86
x64
5.1 - x86
x64
5.2 - x86
x64
5.3 - x86
x64
5.4 - x86
x64
5.5 - x86
x64
5.6 - x86
x64
5.7 - x86
x64
5.8 - x86
x64
5.9 - x86
x64
5.10 - x86
x64
5.11 - x86
x64
Red Hat Enterprise Linux(*18) 6.0 - x86
x64
6.1 - x86
x64
6.2 - x86
x64
6.3 - x86
x64
6.4 - x86
x64
6.5 - x86
x64
6.6 - x86
x64
6.7 - x86
x64
6.8(*25) - x86
x64
7(*20) - x64
7.1(*20) - x64
7.2(*20) - x64
SUSE Linux Enterprise Server (*7)(*18) 11(*3) No SP x86
x64
SP1 x86
x64
SP2 x86
x64
SP3 x86
x64
SP4 x86
x64
12 No SP x64
SP1 x64
Oracle Enterprise Linux (*8)(*18) 5.5 - x86
x64
Oracle Linux (*8)(*18) 6 - x86
x64
6.1 - x86
x64
6.2 - x86
x64
6.3 - x86
x64
6.4 - x86
x64
6.5 - x86
x64
6.6 - x86
x64
6.7 - x86
x64
6.8(*26) - x86
x64
7(*20) - x64
7.1(*20) - x64
7.2(*20) - x64
(*3) HCSM recognizes only the first nine characters of the network interface name of SUSE Linux.
     A name that consists of 10 characters more is not correctly displayed.
     This phenomenon is mostly observed when VLAN IP alias is configured.
(*7) Only Full Sector is supported in System-level Backup and Snapshot of Deployment Manager.
(*8) Deployment Manager is not supported.
(*13) Only Full Sector is supported in System-level Backup.
(*18)You cannot select the Minimum package option when installing Linux. If you select this option, HCSM cannot function properly because there is a lack of required functionality. 
       Note that HCSM is tested using the default OS installation packages.
(*20)After default installation of that OS, the following packages are required:
   net-tools-*.el7.x86_64
   iscsi-initiator-utils-*.el7.x86_64
   pciutils-*.el7.x86_64
   device-mapper-multipath-*.el7.x86_64
   bzip2-*.el7.x86_64
   sysstat-*.el7.x86_64
   samba-common-*.el7.x86_64
   nfs-utils-*.el7.x86_64
   smartmontools-*.el7.x86_64 
(*25)After default installation of RHEL6.8, the following packages are required:
      iscsi-initiator-utils
      device-mapper-multipath
      sysstat
      samba-common
      nfs-utils
      smartmontools
(*26)After default installation of Oralce Linux 6.8, the following packages are required:
      iscsi-initiator-utils
      device-mapper-multipath
      sysstat
      samba-common
      dmidecode
      nfs-utils
      smartmontools
Supported management target OSs (Unix)
OS Name OS Version OS Service Pack Architecture
Solaris(*10)(*13)(*15)(*16)(*19) 10 1/13 x64
11.1 - x64
(*10) Master image deploy and snapshot is not supported.
(*13) Only Full Sector is supported in System-level Backup.
(*15) Deployment Manager's functions are supported only LPAR or VM environment.
(*16) If there is a multipath configuration in Solaris, the Disk Load value cannot be obtained from the performance information.
(*19)Note that HCSM is tested using the default OS installation packages.
Supported management target OSs (VMware ESXi)
OS Name OS Version Update Architecture
VMware ESXi (*6)(*22) 5.0 no update
update1
update2
update3
-
5.1 no update
update1
update2
update3
-
5.5 no update
update1
update2
update3
-
6.0 no update
update1
update2
-
(*6) VMware vSphere Hypervisor (free edition) is not supported.
(*22)There are known problmes when you manage VMware.
・ When a VMware High Availability (VMware HA) hypervisor is managed, the information of the virtual machine on which VMware FT is enabled is not displayed correctly. 
  Therefore, do not use VMware FT.
・ Do not run tasks other than refresh for ESX/ESXi and any virtual machine that uses vCloud, vApp. If you run other tasks, unexpected issues might occur in vCloud, vApp, and HCSM.
・ When ESX/ESXi information is updated from HCSM when the VM configuration is changing, HCSM deletes the VM management information and the VM tasks fails. 
  In this case, wait until the VM configuration information changes are complete, refresh the information, and then register the VM tasks again.
・ An HCSM operation for a virtual machine may fail with the KASV00275-E or KASV10205-E message, indicating that the virtual machine has been unmanaged or deleted,
   even though the virtual machine exists.Reregister the task, and then run it again.
・ ESXi, which uses Virtual Volumes, cannnot be managed in HCSM.
・ Do not use vMotion across vCenter Server.
・ ESXi, which uses VMware vCenter Site Recovery Manager or vSphere Replication, cannnot be managed in HCSM.