Related products 
return to main contents page
return to "Management server" contents page
Device Manager (HDvM)/Tiered Storage Manager (HTSM)
Related software
Tuning Manager
By linking Device Manager and Tiered Storage Manager to Tuning Manager, 
storage system performance information (for example, volume IOPS and parity group usage rates) can be viewed from management clients. 
The Tuning Manager versions required for viewing storage system performance information are shown in the following table.
Table Tuning Manager versions required for viewing storage system performance information
OS Condition codes Case Required Product Name Version
Windows or Linux R Analyzing the storage usage from the GUI Analytics tab Hitachi Tuning Manager server 8.5.0 or later
Hitachi Tuning Manager - Agent for RAID 5.9 or later(*4)(*5)
R Displaying performance information from the GUI Mobility tab Hitachi Tuning Manager server 8.5.0 or later
Hitachi Tuning Manager - Agent for RAID 5.0 or later
R Checking the array group usage from the GUI or CLI client Hitachi Tuning Manager server 8.5.0 or later
Hitachi Tuning Manager - Agent for RAID 7.0 or later
R Analyzing Universal Replicator performance from the GUI Replication tab Tuning Manager server 8.5.0 or later
Tuning Manager - Agent for RAID 7.5 or later(*2)(*3)(*4)
Replication Manager server 8.0.0 or later
R Using VMware VVOL VVOL management server Same version with HDvM
Condition codes :
R: The Required Product should be installed for the described optional support Case.
(*2) For analyzing Universal Replicator performance with VSP G1000, G1500, VSP F1500, 8.0.0 or later version is needed.
(*3) For analyzing Universal Replicator performance with newly supported metrics in HDvM v8.0.0, required product version must be 8.0.0 or later. 
(*4) For the Tuning Manager-Agent for RAID version required for monitoring each storage series, see the Tuning Manager server FRS.
(*5) To analyze (in minutes) a period exceeding 72 minutes in the Analytics tab, a Tuning Manager Agent for RAID version of 8.0.0 or later is needed.
In addition, Tuning Manager - Agent for RAID must support the related storage system. 
HDvM
CIM/WBEM
�@�@�@�@The table below lists the versions of SMI-S that can use the CIM/WBEM functionality for Device Manager.
SMI-S Version  Profile/Subprofile Name
(SNIA CTP recognition profile)
SMI-S1.0.2 Array Profile(*1) �@
�@ AccessPoints Subprofile(*1)
�@ Disk Drive Subprofile(*1)
�@ Extent Mapping Subprofile(*1)
�@ Job Control Subprofile(*1)
�@ LUN Creation Subprofile(*1)
�@ LUN Mapping and Masking Subprofile(*1)
�@ Pool Manipulaion Capabilitieis and Settings Subprofile(*1)
�@ Software Subprofile(*1)
Server Profile(*1) �@
SMI-S1.1.0 Array Profile(*1) �@
�@ AccessPoints Subprofile(*1)
�@ Disk Drive Lite Subprofile(*1)
�@ Extent Composition Subprofile(*1)
�@ FC Target Ports Subprofile(*1)
�@ FC Initiator Ports Subprofile(*1)
�@ Location Subprofile(*1)
�@ Masking and Mapping Subprofile(*1)
�@ Multiple Computer System Subprofile(*1)
�@ Software Subprofile(*1)
Server Profile(*1) �@
�@ Indication Subprofile
SMI-S1.2.0 Array Profile �@
�@ AccessPoints Subprofile
�@ Disk Drive Lite Subprofile
�@ Extent Composition Subprofile
�@ FC Target Ports Subprofile
�@ FC Initiator Ports Subprofile
�@ Location Subprofile
�@ Masking and Mapping Subprofile
�@ Multiple Computer System Subprofile
�@ Software Subprofile
�@ Block Server Performance Subprofile
�@ Storage Element Protection Subprofile
�@ Volume Composition Subprofile
�@ Block Storage Views Subprofile
Server Profile �@
�@ Indication Subprofile
�@ Profile Registration Subprofile
SMI-S1.3.0 Array Profile �@
�@ AccessPoints Subprofile
�@ Disk Drive Lite Subprofile
�@ Extent Composition Subprofile
�@ FC Target Ports Subprofile
�@ FC Initiator Ports Subprofile
�@ Location Subprofile
�@ Masking and Mapping Subprofile
�@ Multiple Computer System Subprofile
�@ Software Subprofile
�@ Block Server Performance Subprofile
�@ Storage Element Protection Subprofile
�@ Volume Composition Subprofile
�@ Block Storage Views Subprofile
Server Profile �@
�@ Indication Subprofile
�@ Profile Registration Subprofile
�@ Object Manager Adapter Subprofile
SMI-S1.4.0 Array Profile �@
�@ AccessPoints Subprofile
�@ Disk Drive Lite Subprofile
�@ Extent Composition Subprofile
�@ FC Target Ports Subprofile
�@ FC Initiator Ports Subprofile
�@ Location Subprofile
�@ Masking and Mapping Subprofile
�@ Multiple Computer System Subprofile
�@ Software Subprofile
�@ Block Server Performance Subprofile
�@ Storage Element Protection Subprofile
�@ Volume Composition Subprofile
�@ Block Storage Views Subprofile
�@ Thin Provisioning Subprofile
�@ Pools from Volumes Subprofile
Server Profile �@
�@ Indication Subprofile
�@ Profile Registration Subprofile
�@ Object Manager Adapter Subprofile
SMI-S1.5.0 Array Profile �@
�@ AccessPoints Subprofile
�@ Disk Drive Lite Subprofile
�@ Extent Composition Subprofile
�@ FC Target Ports Subprofile
�@ FC Initiator Ports Subprofile
�@ Location Subprofile
�@ Masking and Mapping Subprofile
�@ Multiple Computer System Subprofile
�@ Software Subprofile
�@ Block Server Performance Subprofile
�@ Storage Element Protection Subprofile
�@ Volume Composition Subprofile
�@ Block Storage Views Subprofile
�@ Thin Provisioning Subprofile
�@ Pools from Volumes Subprofile
Server Profile �@
�@ Indication Subprofile
�@ Profile Registration Subprofile
�@ Object Manager Adapter Subprofile
(*1) HDvM has the function. But it does not acquire recognition.
Replication Manager
By linking Device Manager to Replication Manager, you can use the Replication tab to manage replication configurations, confirm the write delay time of Continuous Access Journal copy groups (C/T delta), and analyze the cause of C/T delta degradation.
For details of copy pair requirements by using Replication Manager, see the "Copy Pair(HRpM)" sheet.
Table Replication Manager versions required for using the Replication tab
Software Version
Hitachi Replication Manager 8.0.1(*1)
(*1)To manage replication configurations in the Replication tab, the Replication Manager server v8.2.0 or later must be installed.
Compute Systems Manager
Information of each hosts managed by Compute Systems Manager or Device Manager is automatically synchronized, if you install Compute Systems Manager on the same server as the one used by Device Manager.
The versions of Compute Systems Manager that can be linked with Device Manager are as shown below.
Table Compute Systems Manager versions required to launch Compute Systems Manager from Device Manager
Software Version
Hitachi Compute Systems Manager 8.0.1
8.1.0
8.1.1
8.1.2
8.1.4
8.2.0
8.2.1
8.4.0
Mainframe Agent
For managing and shredding mainframe host volumes, from Device Manager and Tiered Storage Manager, 
Mainframe Agent needs to be installed to mainframe host. 
The versions of Mainframe Agent to be supported by Device Manager and Tiered Storage Manager are shown in the following table.
Table Mainframe Agent versions required for managing mainframe hosts
Software Version
Referring mainframe volume data (Device Manager) 6.0 or later
Migrating and shredding mainframe volumes (Tiered Storage Manager) 6.0 or later
HTSM
OS Condition codes Case Software Version
Windows N Always Hitachi Device Manager(*1) Same version with HTSM
R When a Volume's Host Name is to be displayed Hitachi Device Manager Agent 6.0.0 or later
R When a Volumes Mainframe host information (VOLSER and DEVN) is to be displayed Hitachi Mainframe Agent 6.0.0 or later
N When a Volumes Mainframe host information (VOLSER and DEVN) is to be displayed Hitachi Device Manager Same version with HTSM
N When HDvM repository updates can be automatically detected and HTSM will perform a refresh Hitachi Device Manager Same version with HTSM
N When a user ID / Password length more than 25 characters long Hitachi Device Manager Same version with HTSM
N When USP V is present Hitachi Device Manager Same version with HTSM
R When the historical report of HTnM is to be displayed Hitachi Tuning Manager 8.5.0 or later
R When USP V contains mainframe volumes  Hitachi Mainframe Agent 6.0.0 or later
Linux N Always Hitachi Device Manager Same version with HTSM
R When a Volume's Host Name is to be displayed Hitachi Device Manager Agent 6.0.0 or later
R When a Volumes Mainframe host information (VOLSER and DEVN) is to be displayed Hitachi Mainframe Agent 6.0.0 or later
N When a Volumes Mainframe host information (VOLSER and DEVN) is to be displayed Hitachi Device Manager Same version with HTSM
N When HDvM repository updates can be automatically detected and HTSM will perform a refresh Hitachi Device Manager Same version with HTSM
N When a user ID / Password length more than 25 characters long Hitachi Device Manager Same version with HTSM
N When USP V is present Hitachi Device Manager Same version with HTSM
R When the historical report of HTnM is to be displayed Hitachi Tuning Manager 8.5.0 or later
R When USP V contains mainframe volumes Hitachi Mainframe Agent 6.0.0 or later
Condition codes :
N: The Required Product must be installed on the same node(host).
R: The Required Product should be installed for the described optional support Case.
(*1) The version of Device Manager required to support the storage hardware must be installed.
Replication Manager(HRpM)
To use the copy pair functionality
-HDvM Agent
-BCM
-CCI
For the supported versions of the above products, see "Pair management server".
Tuning Manager (HTnM)
OS Case Required Product Version VRS
Windows or Linux When monitoring storages HTnM-Agent for RAID 5.0.0 - 6.4.0
Hitachi Tuning Manager (HTnM-Agent for RAID) 7.0.0 - 8.5.0
When monitoring server hosts HTnM-Agent for Server System 5.0.0 - 6.4.0
Hitachi Tuning Manager (HTnM-Agent for Server System) 7.0.0 - 8.5.0
When monitoring Oracle HTnM-Agent for Oracle 5.0.0 - 6.3.0
Hitachi Tuning Manager (HTnM-Agent for Oracle) 7.0.0 - 8.5.0
When monitoring fabric switches HTnM-Agent for SAN Switch 5.0.0 - 6.3.0
Hitachi Tuning Manager (HTnM-Agent for SAN Switch) 7.0.0 - 8.5.0
When monitoring SQL Server HTnM-Agent for SQL Server 5.0.0 - 6.3.0
Hitachi Tuning Manager (HTnM-Agent for Microsoft SQL Server) 7.0.0 - 8.5.0
When monitoring DB2 HTnM-Agent for DB2 5.0.0 - 6.3.0
Hitachi Tuning Manager (HTnM-Agent for DB2) 7.0.0 - 8.5.0
When monitoring NAS HTnM-Agent for Network Attached Storage 5.0.0 - 6.2.0
Hitachi Tuning Manager (HTnM-Agent for Network Attached Storage) 7.0.0 - 8.5.0
(EOT)(SOE)
Global Link Manager (HGLM)
When Using HDLM
If the installed HDLM version is earlier than 5.8, Device Manager agent 3.5 or later must also be installed. To manage a VMware version of HDLM, a remote management client is required. Note that if HDLM is installed on a host on which any of the OSs listed in the following table is running, HDLM cannot be managed by Global Link Manager.
Table 1 OSs That Cannot Be Managed by Global Link Manager
OSs that Are not Supported for Global Link Manager Architecture
Windows Windows NT (SP6a) x86
Windows 2000 (SP2 and SP3) x86
Solaris Solaris 2.6 SPARC
AIX AIX 4.3.3 POWER
Linux Red Hat Enterprise Linux AS 2.1 IPF
SUSE Linux Enterprise Server 8 x86
IPF
Oracle Enterprise Linux 4 x86
AMD64/EM64T
Oracle Enterprise Linux 5 x86
AMD64/EM64T
Note:
If the installed HDLM version is earlier than 6.0, the hosts cannot connect to Global Link Manager via IPv6. If IPv6 is enabled on a host, disable it. If IPv6 remains enabled, you cannot start the Device Manager agent service or the Hitachi Command Suite Common Agent Component service.
When Using DMP
The following table lists the requirements and prerequisite programs for DMP versions supported by Global Link Manager.
Table 2 DMP Requirements and Prerequisite Programs
Applicable OS DMP version Prerequisite program Supported Storage Systems that can be managed by HGLM  (Symantec Volume Manager )
Windows Server 2008 (IPF) (no SP) DMP 5.1 without AP, or with AP1 or SP1, is supported.  - Global Link Manager agent 6.3 or later
 - JRE 5.0
Hitachi Universal Storage Platform, Hitachi Universal Storage Platform V, Hitachi Universal Storage Platform VM, Hitachi Network Storage Controller NSC55, Hitachi Adaptable Modular Storage AMS200, Hitachi Adaptable Modular Storage AMS500, Hitachi Adaptable Modular Storage AMS1000, Hitachi Adaptable Modular Storage AMS2100, Hitachi Adaptable Modular Storage AMS2300, Hitachi Adaptable Modular Storage AMS2500, Hitachi Workgroup Modular Storage WMS100
Windows Server 2008 (x64) (no SP)(Datacenter, Enterprise, Standard)
Windows Server 2008 (x86) (no SP)(Datacenter 32 bit, Enterprise 32 bit, Standard 32 bit)
#
The Global Link Manager agent only runs in the global zone.
For details about DMP environment settings, see the VxVM documentation.
When Using HP-UX Multipathing
The requirement for HP-UX multipathing supported by Global Link Manager is as follows:
• HP-UX 11i v3 (IPF)#
#
HP-UX running on a virtual machine is not supported.
For details about HP-UX multipathing environment settings, see the HP-UX documentation.
The supported storage systems that can be managed by HGLM is as follows:
• VSP G1000
• VSP Gx00 models
• VSP Fx00 models
• VSP
• USP V
• USP VM
• NSC55
• USP
• HUS VM
• HUS150
• HUS130
• HUS100
• SMS100
• TMS
• AMS2500
• AMS2300
• AMS2100
• AMS2010
• BR1600E
• WMS100
Compute Systems Manager (HCSM)
Function Required Product Name Required Product Version
View storage system information Device Manager  8.1.2 or later
Command Director (HCmD)
None.
Automation Director (HAD)
Function Required Product Name Required Product Version
When the HAD contents are used Device Manager  8.1.4 or later
When HAD contents are used with performance information of HTnM Device Manager  8.1.4 or later
Tuning Manager server 8.1.1 or later(*1)
(*1) When HDvM and HTnM are required with a service template to support newly, use HDvM and HTnM same as a version of HAD.
Host Data Collector (HDC)
None.
HTnM - Agent for RAID
None.
HTnM - Agent for NAS
None.
HTnM - Agent for SAN Switch
None.
HCmD Data Collector
None.
Incompatible products
Tuning Manager (HTnM) and HTnM-Agent for RAID
Do not install Tuning Manager and Tuning Manager agents in the host on which the following products are installed:
- Analytics probe of Hitachi Infrastructure Analytics Advisor