Hitachi Device Manager Software System Requirements

Transcription

1 Hitachi Device Manager Software -00 System Requirements Table of Contents Table of Contents... 1 Management server requirements... 1 Host Data Collector requirements Device Manager GUI requirements Device Manager CLI requirements Tiered Storage Manager CLI requirements Requirements for the Plug-in for Virtualization Server Provisioning setup tool Storage systems requirements Copyrights and Licenses Management server requirements This chapter describes the management server requirements. Hardware requirements Installation of the Hitachi Command Suite requires a computer that satisfies the following hardware requirements. Computer requirements The following table describes the computer requirements for the management server. Table 1 Management server computer requirements Item Windows Solaris or Linux Processor Minimum: Dual-Core Processor Recommended: At least Quad-Core Processor In Solaris10 (x64) or Linux: Minimum: Dual-Core Processor Recommended:At least Quad-Core Processor In Solaris (SPARC)* 1 : Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 1

2 Management server requirements Item Windows Solaris or Linux Minimum: 1.0 GHz Recommended: 1.2 GHz or faster Physical memory Disk space Monitor Minimum: 3 GB Recommended: At least 6GB* 2 Minimum: 5 GB Recommended: At least 20 GB XGA (1024 x 768 resolution) or higher. Minimum: 3 GB Recommended: At least 6 GB* 2 Minimum: 5 GB Recommended: At least 20 GB LAN card DVD drive 10/100 Ethernet LAN card If the computer and the LAN cable are compatible with Gigabit Ethernet, you can use a Gigabit-class card. Required. #1: #2: Device Manager can be usable in server machines that have UltraSPARC T1/T2 processor. But the server machines are not recommended because Device Manager does not make use of the merit of UltraSPARC T1/T2 processor. If the Device Manager server and software products other than the Device Manager server and the Tiered Storage Manager server are used simultaneously, the amount of the physical memory must be equal to the total memory size of all the software products. Virtual memory requirements If adequate virtual memory is not allocated on the management server, the Hitachi Command Suite products and any other installed programs might become unstable or might not start. To ensure stable operation of the management server, in addition to the virtual memory required for the OS and other programs, the management server also requires the amount of virtual memory required for both the products shown in Table 2 and Common Component. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 2

3 Management server requirements In addition to the virtual memory required for all the products installed on a management server, be sure to secure enough virtual memory (750MB) for Common Component. The following table shows the virtual memory requirements for each product in this version. Table 2 Virtual memory requirements for each product Product name Device Manager #1 + Tiered Storage Manager + Replication Manager #3 Virtual memory requirement (MB) 2,600 Tuning Manager #2 1,500 Global Link Manager 300 Compute Systems Manager 1,500 Hitachi NAS Manager #4 512 Hitachi File Services Manager 1024 Storage Navigator Modular 2 #4 200 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 3

4 Management server requirements Note: Device Manager, Tiered Storage Manager, and Replication Manager will always be installed at the same time. If you plan to install these products, and if 1,000 MB of virtual memory is already used by the OS and other programs, you must secure more than 4,350 MB of virtual memory. 2,600 (for Device Manager, Tiered Storage Manager, and Replication Manager (for Common Component) + 1,000 (already used virtual memory) = 4,350 #1: #2: #3: #4: If the Device Manager agent is installed on the management server, you need to allocate additional virtual memory for it. Specify a value for the virtual memory of the Device Manager agent in the server.agent.maxmemorysize property. If the Tuning Manager agent is installed on the management server, you need to allocate additional virtual memory for it. For details on virtual memory requirements, see the description of memory requirements in the Hitachi Command Suite Tuning Manager Software Installation Guide. If Replication Manager Application Agent is installed on the management server, you need to allocate additional virtual memory for it. For details on virtual memory requirements, see the Hitachi Command Suite Replication Manager Configuration Guide. The virtual memory requirements listed in the table are for Hitachi NAS Manager version 6.4, Hitachi File Services Manager version and Storage Navigator Modular 2 version For details on the latest virtual memory requirements, see the documentation for each product. Required disk space Installation of the Hitachi Command Suite requires the disk space described in Table 3 and Table 4. Table 3 Required disk space (in Windows) Item Default installation Folder Required disk space Installation folder for Common Component Installation folder for the Device Manager server Installation folder for the Tiered Storage Manager server program-filesfolder\hicommand\base #1 program-filesfolder\hicommand\devicemanager program-filesfolder\hicommand\tieredstoragem anager 2.5 GB Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 4

5 Management server requirements Item Default installation Folder Required disk space Installation folder for the Replication Manager server Installation folder for the setup support utility Installation folder for the Host Data Collector Storage folder of the database for Common Component #2 Storage folder of the database for the Device Manager server Storage folder of the database for the Tiered Storage Manager server Storage folder of the database for the Replication Manager server Installation folder for the common library #2 Output folder for common trace log files #2#3 Output folder for installation log files A temporary folder #4 program-filesfolder\hicommand\replicationsto ragemanager program-filesfolder\hicommand\utility program-filesfolder\hicommand\hostdatacollec tor program-filesfolder\hicommand\database program-filesfolder\hicommand\database\base program-filesfolder\hicommand\database\devic emanager program-filesfolder\hicommand\database\htsm program-filesfolder\hicommand\database\hrpm program-filesfolder\hitachi\hntrlib2 common-program-filesfolder\hitachi program-filesfolder\hitachi\hntrlib2\spool program-files-folder\ HiCommand\HInst A folder specified by the environment variable TMP 650 MB 800 MB 150 MB 250 MB 1 MB 1 MB 10 MB 300 MB Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 5

6 Management server requirements Note: #1: #2: #3: #4: Note that the program-files-folder\hicommand portion can be changed. Read it as the folder specified during installation. If the architecture is, program-files-folder and common-program-filesfolder are the folders specified in the Windows environment variables %ProgramFiles% and %CommonProgramFiles%. If the architecture is x64, program-files-folder and common-program-filesfolder are the folders specified in the Windows environment variable %ProgramFiles()% and %CommonProgramFiles()%. If you are installing the Hitachi Command Suite in an environment where Common Component has already been installed, install it on the same drive. This is not required if version 4.0 or later of a Hitachi Command Suite product has already been installed. ou can change the size and number of generations of common trace log files. This is required only during installation, and is unnecessary after installation. Table 4 Required disk space (Solaris or Linux) Item Default installation directory Required disk space Installation directory for Common Component Installation directory for the Device Manager server Installation directory for the Tiered Storage Manager server Installation directory for the Replication Manager server Installation directory for the setup support utility Installation directory for the Host Data Collector /opt/hicommand/base /opt/hicommand /opt/hicommand/tieredstoragemanager /opt/hicommand/replicationmanager /opt/hicommand/utility /opt/hicommand/hostdatacollector /opt/hicommand/winexe 2.7 GB Storage directory of the database /var/opt/hicommand/database 750 MB for Common Component #1 /var/opt/hicommand/database/base Storage directory of the database for the Device Manager server Storage directory of the database for the Tiered Storage Manager /var/opt/hicommand/database/deviceman ager /var/opt/hicommand/database/htsm 800 MB 150 MB Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 6

7 Management server requirements Item Default installation directory Required disk space server Storage directory of the database for the Replication Manager server /var/opt/hicommand/database/hrpm 250 MB Installation directory for the /opt/hitachi 1 MB common library #1 Output directory for common trace /var/opt/hitachi/hntrlib2/spool 1 MB log files #1#2 Output directory for installation log files /opt/hicommand/hinst 10 MB A temporary directory #3 /var/tmp 1.7 GB Note: In Solaris (x64) or Linux, the /opt/hicommand portion shown in the above table can be changed. Read it as the directory specified during installation. #1: #2: #3: This is not required if version 4.0 or later of a Hitachi Command Suite product has already been installed. ou can change the size and number of generations of common trace log files. This is required only during installation, and is unnecessary after installation. Software requirements Installation of the Hitachi Command Suite requires a computer that satisfies the following software requirements. Prerequisite OS Table 5 to Table 7 describe the prerequisite OSs for the Hitachi Command Suite. Table 5 Usable management server OSs (Windows) OS Edition Service pack Hitachi Command Suite HDvM HDC HTSM HRpM IPv6 Windows XP () Professional SP2 N SP3 N Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 7

8 Management server requirements OS Edition Service pack Hitachi Command Suite HDvM HDC HTSM HRpM IPv6 Windows Server 2003 R2 () #2 Windows Server 2003 R2 (x64) #2 Windows Vista () Windows 7 () Windows 7 (x64) Windows Server 2008 #1 #2 () Windows Server 2008 #1 #2 (x64) Windows Server 2008 R2 #1 #2 (x64) Datacenter Edition Enterprise Edition Standard Edition Datacenter x64 Edition Enterprise x64 Edition Standard x64 Edition Business Enterprise Ultimate Enterprise Edition Professional Edition Ultimate Edition Enterprise Edition Professional Edition Ultimate Edition Datacenter 32-bit Edition Datacenter without Hyper-V 32-bit Edition Enterprise 32-bit Edition Enterprise without Hyper-V 32-bit Edition Standard 32-bit Edition Standard without Hyper-V 32-bit Edition Datacenter Edition Datacenter without Hyper-V Edition Enterprise Edition Enterprise without Hyper-V Edition Standard Edition Standard without Hyper-V Edition Datacenter Edition Enterprise Edition Standard Edition SP2 SP2 No SP N SP1 N SP2 N No SP N SP1 N No SP N SP1 N No SP SP1 N SP2 No SP SP1 N SP2 No SP SP1 Legend : Supported. --: Not supported. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 8

9 Management server requirements #1: #2: Operation on Server Core is not supported. By linking with Tuning Manager, storage system performance information can be viewed in the Mobility tab and the Analytics tab. Table 6 Usable management server OSs (Solaris) OS Architecture Required patches Hitachi Command Suite IPv6 HDvM HTSM HRpM HDC Solaris 9 SPARC (32 and 64 bit) #4 Solaris SPARC (32 and #1 bit) x64 Edition #3#4 Apply the following patch: Apply the following patch: or later #2 Do not apply the following patch: xx (xx is 02 or later) Apply the following patch: #4 Do not apply the following patch: xx (xx is 02 or later) Legend #1: #2: : Supported. --: Not supported. The Hitachi Command Suite only run in a normal global environment (global zone). If a non-global zone has been created, be sure to install the Hitachi Command Suite in the global zone. Apply this patch if you use Solaris 10 11/06 (update 3), Solaris 10 8/07 (update 4), or Solaris 10 5/08 (update 5). Check the /etc/release file for the update number. The following shows an example of the /etc/release file for Solaris 10 11/06: Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 9

10 Management server requirements #3: #4: Solaris 10 11/06 s10s_u3wos_10 SPARC Copyright 2006 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 14 November 2006 The Device Manager server runs only in the 64-bit kernel mode on the Sun Fire x64 Servers hardware. Do not change the kernel mode to a mode other than 64-bit kernel mode after installing Hitachi Command Suite. By linking with Tuning Manager, storage system performance information can be viewed in the Mobility tab and the Analytics tab. Table 7 Usable management server OSs (Linux) OS Version Architecture Hitachi Command Suite IPv6 HDvM HTSM HRpM HDC Red Hat Enterprise Linux 5 Red Hat Enterprise Linux 5 Advanced Platform Red Hat Enterprise Linux 5 Red Hat Enterprise Linux 5 Advanced Platform Red Hat Enterprise Linux 5 Red Hat Enterprise Linux 5 Advanced Platform SUSE Linux Enterprise Server #1 -- x #1 x #1 -- x64 -- SP2 -- x64 -- SP3 -- x64 -- SUSE Linux Enterprise Server 11 No SP #1 -- x64 -- SP1 #1 x64 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 10

11 Management server requirements Legend #1: : Supported. --: Not supported. By linking with Tuning Manager, storage system performance information can be viewed in the Mobility tab and the Analytics tab. Prerequisite JDK For Window Solaris (SPARC) or Linux In Hitachi Command Suite products, the following Oracle Sun JDK versions are available besides the bundled JDK 5 Update 03 (1.5.0_03) or later except in Windows XP or Windows Server 2003 R2 environment: Oracle Sun JDK 5 (1.5.0) An Update 17 or later version is required for SSL communication between the external authentication server (LDAP directory server) and the management server. Oracle Sun JDK 6 (1.6.0) If the OS of the management server is Windows, the file system of the management server must be NTFS in order to use Oracle Sun JDK. Use Oracle Sun JDK for 32 bit because Hitachi Command Suite products are 32 bit applications. After new installation, the bundled JDK in the product will be set to use. Exchange the JDK for Hitachi Command Suite products to use Oracle Sun JDK after the installation. For Solaris (x64) The JDK provided by the Oracle is also available besides the bundled JDK in OS. An Update 17 or later version is required for SSL communication between the external authentication server (LDAP directory server) and the management server. Other Prerequisite software The following software is required for the management server: For Windows Microsoft Windows Installer 3.1 This software is required for decompressing the installer. J2SE Java Runtime Environment 5.0.xx (xx is 03 or later) This software is automatically installed when you install Hitachi Command Suite. For Solaris (SPARC) Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 11

12 Management server requirements SUNWgzip This software is required for decompressing the installer. J2SE Java Runtime Environment 5.0.xx (xx is 03 or later) This software is automatically installed when you install Hitachi Command Suite. For Solaris 10 (x64) SUNWgzip This software is required for decompressing the installer. J2SE Java Runtime Environment Install JDK 1.5.0, provided by Oracle Corporation. For Linux gzip This software is required for decompressing the installer. J2SE Java Runtime Environment 5.0.xx (xx is 03 or later) This software is automatically installed when you install Hitachi Command Suite. The following package is required for the listed OS: Red Hat Enterprise Linux 4.x() : compat-libstdc Red Hat Enterprise Linux 5.2(),5.3(/x64) or later : compat-libstdc SUSE Linux Enterprise Server 10 SP2(/x64) : compatlibstdc SUSE Linux Enterprise Server 10 SP3(): libstdc SUSE Linux Enterprise Server 10 SP3(x64) : libstdc bit SUSE Linux Enterprise Server 11() : libstdc SUSE Linux Enterprise Server 11(x64) : libstdc bit Virtualization software Table 8 and Table 9 describe the virtual machine OSs on which the Hitachi Command Suite can run. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 12

13 Management server requirements Table 8 Virtualization software (Windows) Virtual machine OS Edition Service pack Virtualization software VMware ESX #1 Hyper-V #2 Windows XP Professional SP2 -- SP3 -- Windows Server 2003 R2 () Windows Server 2003 R2 (x64) Windows Vista () Datacenter Edition Enterprise Edition Standard Edition Datacenter x64 Edition Enterprise x64 Edition Standard x64 Edition Business Enterprise Ultimate SP2 SP2 No SP -- SP1 -- SP2 -- Windows 7 Enterprise Edition No SP -- () Professional Edition SP1 Ultimate Edition Windows 7 Enterprise Edition No SP -- (x64) Professional Edition SP1 Ultimate Edition Windows Server 2008 () Windows Server 2008 (x64) Windows Server 2008 R2 (x64) Datacenter 32-bit Edition Datacenter without Hyper-V 32-bit Edition Enterprise 32-bit Edition Enterprise without Hyper- V 32-bit Edition Standard 32-bit Edition Standard without Hyper-V 32-bit Edition Datacenter Edition Datacenter without Hyper-V Edition Enterprise Edition Enterprise without Hyper- V Edition Standard Edition Standard without Hyper-V Edition Datacenter Edition Enterprise Edition Standard Edition No SP SP1 SP2 No SP SP1 SP2 No SP SP1 N N Legend Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 13

14 Management server requirements : Supported. --: Not supported. Note: To run the Hitachi Command Suite on a virtual machine, configure the virtual machine to satisfy the requirements in Computer requirements. #1: The following versions can be used. Virtual machine Prerequisite version Prerequisite software products 1 ESX3.5 update2 or later -- 2 ESXi vma 3 ESX vma 4 ESXi vma 5 ESX vma 6 ESXi vma 7 ESX4.1u1 -- vma 8 ESXi4.1u1 -- vma 9 ESXi vma Legend --: Not supported. #2: Version 1.0 or 2.0 can be used. Table 9 Virtualization software (Solaris) Virtual machine Architecture Logical domains # Solaris 10 SPARC Legend : Supported. Note: To run the Hitachi Command Suite on a virtual machine, configure the virtual machine to satisfy the requirements in Computer requirements. #1: Version 1.2 or 1.3 can be used. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 14

15 Management server requirements Supported cluster software If you use the cluster management software described in the following table, you can manage two management servers in an active-standby clustering configuration. Table 10 Supported cluster environments OS Architecture Service pack Cluster software Windows Server 2003 R2 SP2 Microsoft Cluster Service Windows Server 2008 No SP SP1 Microsoft Failover Cluster SP2 x64 No SP SP1 SP2 Windows Server 2008 R2 x64 No SP SP1 Microsoft Failover Cluster Solaris 9 SPARC -- VERITAS Cluster Server 4.0 or Sun Cluster 3.1 Solaris 10 SPARC -- VERITAS Cluster Server 4.1 MP2 x64 -- or Veritas Cluster Server 5.0 MP1 Legend: --: Not applicable 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 11 Tuning Manager versions required for viewing storage system performance information Condition Software Version Displaying from the Analytics Tuning Manager server or later Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 15

16 tab Condition Software Version Tuning Manager - Agent for RAID 5.9 or later Displaying performance information from the Mobility tab Launching historical report dialog boxes from the legacy Tiered Storage Manager GUI Viewing parity group usage rates from the legacy Tiered Storage Manager GUI or the Tiered Storage Manager CLI Tuning Manager server Tuning Manager - Agent for RAID Tuning Manager server Tuning Manager - Agent for RAID or later 5.0 or later 7.0 or later 7.0 or later File Services Manager By linking with File Services Manager, from Device Manager, the usage status of Hitachi Data Ingestor volumes can be checked, and File Services Manager can be launched from the GUI. The File Services Manager versions required for managing file servers are shown in the following table. Table 12 File Services Manager versions required for managing file servers Condition Version Allocating volumes to Hitachi Data Ingestor Launching Hitachi File Services Manager (Login screen) Receiving Hitachi Data Ingestor SNMP traps 3.0 or later 3.1 or later Device Manager Mainframe Agent By using Tiered Storage Manager, you can migrate and shred mainframe volumes on OS/390 or z/os. The following table describes the software required for using Tiered Storage Manager to manage mainframe volumes. Table 13 Software required to manage mainframe volumes Software Version Device Manager Mainframe Agent 6.0 or later Host Data Collector requirements This section gives the Host Data Collector support matrix for the network elements. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 16

17 Server support matrix The following table provides the support matrix for the servers supported by the Host Data Collector. Table 14 Host Data Collector server support matrix OS name Server version Service pack Architecture Windows Server 2003 Standard Edition Enterprise Edition SP2 Datacenter Edition Standard x64 Edition SP2 x64 Enterprise x64 Edition Datacenter x64 Edition R2 Standard Edition SP2 R2 Enterprise Edition R2 Datacenter Edition R2 Standard x64 Edition SP 2 x64 R2 Enterprise x64 Edition R2 Datacenter x64 Edition Windows Server 2008 Standard 32-bit Edition Enterprise 32-bit Edition SP2 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 Standard Edition SP2 x64 Enterprise Edition Datacenter Edition Standard without Hyper-V Edition Enterprise without Hyper-V Edition Datacenter without Hyper-V Edition R2 Standard Edition No SP x64 R2 Enterprise Edition R2 Datacenter Edition R2 Standard Edition SP1 x64 R2 Enterprise Edition R2 Datacenter Edition Solaris 9 None SPARC 32 bit, 64 bit 10 None SPARC 32 bit, 64 bit Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 17

18 OS name Server version Service pack Architecture x64 64 bit Red Hat ELAS or Red Hat ELES 5.5 No SP x64 X86 SUSELES 11 SP1 x64 X86 Table 15 Host Data Collector prerequisite libraries matrix OS Package Name Solaris 9 (SPARC) SUNWcsl SUNWlibpopt SUNWsmbau SUNWgss SUNWcsl SUNWlibsasl SUNWpr SUNWtls SUNWkrbu Solaris 10 (SPARC) SUNWcslr SUNWcsl SUNWlibpopt SUNWlibmsr SUNWsmbau SUNWgss SUNWcsl SUNWlibsasl SUNWpr SUNWtls SUNWkrbu Note: It is required that SMBClient ( or later) is installed and running correctly. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 18

19 Target Host support matrix The following table provides the target host matrix for the servers supported by the Host Data Collector. Table 16 Host Data Collector target host matrix OS name Server version Service pack Architecture Windows Server 2003 Standard Edition Enterprise Edition Datacenter Edition SP2 Web Edition Standard x64 Edition SP2 x64 Enterprise x64 Edition Datacenter x64 Edition R2 Standard Edition SP2(*2) R2 Enterprise Edition R2 Datacenter Edition R2 Standard x64 Edition SP2(*2) x64 R2 Enterprise x64 Edition R2 Datacenter x64 Edition Windows Server 2008 Standard 32-bit Edition Enterprise 32-bit Edition SP2(*2) 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 for Itanium-based Systems SP2 Standard Edition Enterprise Edition Datacenter Edition Standard without Hyper-V Edition Enterprise without Hyper-V Edition Datacenter without Hyper-V Edition R2 Standard R2 Enterprise R2 Datacenter SP2(*2) No SP SP1(*2) x64 x64 x64 R2 for Itanium-Based Systems No SP SP1 Solaris 9 (*1) None SPARC 32 bit, 64 bit 10 None SPARC Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 19

20 OS name Server version Service pack Architecture 32 bit, 64 bit x64 64 bit AIX HP-UX iv2 None None None None POWER 32 bit 64 bit POWER 64 bit POWER 64 bit PA-RISC 64 bit 11iv3 None PA-RISC 64 bit Red Hat ELAS or Red Hat ELES 4.7 None 4.8 None x64 x64 Red Hat EL or Red Hat ELAP 5.3 None x64 None 5.4 x64 None 5.5 SUSELES SP3 No SP x64 x64 x64 SP1 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 20

21 OS name Server version Service pack Architecture x64 #:(*1) In case that target operation system is Solaris 9 4/04 s9s_u6wos_08a SPARC, registering hosts fail because of SCP (Secure Copy) command failure. Please use later release of Solaris 9. #:(*2) ESX/ESXi4.1u1, ESX/ESXi4.1, and ESX/ESXi4.0 are supported. Supported Storage Systems and HBAs The following storage system models are supported by Host Data Collector: Virtual Storage Platform (*1) Universal Storage Platform V/VM (*1) Hitachi USP (*1) Lightning 9900V Hitachi AMS 2000 (*2) Hitachi SMS (*2) Hitachi AMS/WMS (*2) Thunder 9500V (*1) (*1) Fibre Channel is supported. (*2) Fibre Channel and iscsi are supported. Note: If you gather the information from host that connects to a storage system shown above, use an HBA described in the manual of the storage system. Note: To obtain host WWN information, an HBA API library that supports SNIA HBA API provided by the HBA vendors is required. Note: If you gather the information from the host that uses iscsi, there are following requirements. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 21

22 OS Windows Server 2003 SP2 Windows Server 2003 R2 SP2 Windows Server 2008 SP2 Windows Server 2008 R2 Windows Server 2008 R2 SP1 HP-UX Other OSs which are supported as a target host of Host Data Collector Description The iscsi software (MS iscsi Initiator 2.08 or later) is required. iscsi is not supported. Only NIC is supported. File System support matrix Table 17 to Table 23 provide the File System support matrix for the Host Data Collector. Table 17 Host Data Collector File System support matrix for Windows 2003 OS version Service pack Architecture File System Standard Edition Enterprise Edition Datacenter Edition Web Edition Standard x64 Edition Enterprise x64 Edition Datacenter x64 Edition R2 Standard Edition R2 Enterprise Edition R2 Datacenter Edition R2 Standard x64 Edition R2 Enterprise x64 Edition R2 Datacenter x64 Edition SP2 NTFS FAT FAT32 NTFS FAT FAT32 SP2 x64 NTFS FAT FAT32 SP2 NTFS FAT FAT32 SP2 x64 NTFS FAT FAT32 Table 18 Host Data Collector File System support matrix for Windows 2008 OS version Service pack Architecture File System Standard 32-bit Edition Enterprise 32-bit Edition Datacenter 32-bit Edition Standard without Hyper-V 32- bit Edition Enterprise without Hyper-V SP2 NTFS FAT FAT32 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 22

23 32-bit Edition OS version Service pack Architecture File System Datacenter without Hyper-V 32-bit Edition for Itanium-based Systems SP2 NTFS FAT FAT32 Standard Edition Enterprise Edition Datacenter Edition Standard without Hyper-V Edition Enterprise without Hyper-V Edition Datacenter without Hyper-V Edition R2 Standard R2 Enterprise R2 Datacenter R2 for Itanium-Based Systems SP2 x64 NTFS FAT FAT32 No SP x64 NTFS FAT SP1 FAT32 No SP NTFS FAT SP1 FAT32 Table 19 Host Data Collector File System support matrix for Solaris OS version Service pack Architecture File System 9 None SPARC Kernel mode: 32-bit or 64-bit 10 None SPARC Kernel mode: 32-bit or 64-bit x64 Kernel mode: 64-bit VxFS UFS VxFS UFS VxFS UFS Table 20 Host Data Collector File System support matrix for AIX OS version Service pack Architecture File System 5.3 None POWER Kernel mode: 32-bit or 64-bit JFS Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 23

24 OS version Service pack Architecture File System 6.1 None POWER Kernel mode: 64-bit JFS 7.1 None POWER Kernel mode: 64-bit JFS Table 21 Host Data Collector File System support matrix for HP-UX OS version Service pack Architecture File System 11iv2 None VxFS (*1)HFS PA-RISC Kernel mode: 64-bit 11iv3 None PA-RISC Kernel mode: 64-bit VxFS (*1)HFS VxFS (*1)HFS VxFS HFS #:(*1) Online JFS is not supported. Table 22 Host Data Collector File System support matrix for RedHatELAS or RedHatELES OS version Service pack Architecture File System 5.3 None x64 ext2 ext3 5.4 None ext2 ext3 ext2 ext3 x64 ext2 ext3 5.5 None ext2 ext3 ext2 ext3 x64 ext2 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 24

25 OS version Service pack Architecture File System ext3 Table 23 Host Data Collector File System support matrix for SUSELES OS version Service pack Architecture File System 10 SP3 ext2 ext3 ext2 ext3 x64 ext2 ext3 11 No SP ext2 ext3 ext2 ext3 x64 ext2 ext3 SP1 ext2 ext3 ext2 ext3 x64 ext2 ext3 Volume Manager support matrix Table 24 to Table 30 provide the Volume Manager support matrix for the Host Data Collector. Table 24 Host Data Collector Volume Manager support matrix for Windows 2003 OS version Service pack Architecture Volume manager Volume manager version Standard Edition Enterprise Edition Datacenter Edition Web Edition SP2 Basic Dynamic Basic Dynamic None None Standard x64 Edition SP2 x64 Basic None Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 25

26 OS version Service pack Architecture Enterprise x64 Edition Datacenter x64 Edition Volume manager Dynamic Volume manager version R2 Standard Edition R2 Enterprise Edition R2 Datacenter Edition R2 Standard x64 Edition R2 Enterprise x64 Edition R2 Datacenter x64 Edition SP2 x64 Basic Dynamic SP2 x64 Basic Dynamic None None Table 25 Host Data Collector Volume Manager support matrix for Windows 2008 OS version Service pack Architecture Volume manager Volume manager version 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 SP2 Basic Dynamic None Itanium-based systems SP2 Basic Dynamic None Standard Edition Enterprise Edition Datacenter Edition Standard without Hyper-V Edition Enterprise without Hyper-V Edition Datacenter without Hyper-V Edition R2 Standard R2 Enterprise R2 Datacenter R2 for Itanium-Based Systems SP2 x64 Basic Dynamic No SP x64 Basic SP1 Dynamic No SP Basic SP1 Dynamic None None None Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 26

27 Table 26 Host Data Collector Volume Manager support matrix for Solaris OS version Service pack Architecture Volume manager Volume manager version 9 None SPARC Kernel mode: 32-bit or 64-bit 10 None SPARC Kernel mode: 32-bit or 64-bit x64 Kernel mode: 64-bit None None SVM 1.0 VxVM 5 None None SVM 1.0 VxVM 5 5.0MP1 None SVM 1.0 Table 27 Host Data Collector Volume Manager support matrix for HP- UX OS version Service pack Architecture Volume manager Volume manager version 11iv2 None None None PA-RISC Kernel mode: 64-bit LVM None LVM Independent None Independent 11iv3 None None None PA-RISC Kernel mode: 64-bit LVM2.1 None LVM2.1 Independent None Independent Table 28 Host Data Collector Volume Manager support matrix for AIX OS version Service pack Architecture 5.3 None POWER Kernel mode: 32-bit or 64-bit 6.1 None POWER Kernel mode: 64-bit Volume manager LVM LVM Volume manager version Independent Independent Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 27

28 7.1 None POWER Kernel mode: 64-bit LVM Independent Table 29 Host Data Collector Volume Manager support matrix for Linux RedHatEL or RedHatELAP OS version Service pack Architecture Volume manager Volume manager version 5.4 None None None LVM2 Independent None None LVM2 Independent x64 None None LVM2 Independent 5.5 None None None LVM2 Independent None None LVM2 Independent x64 None None LVM2 Independent Table 30 Host Data Collector Volume Manager support matrix for Linux SUSELES OS version Service pack Architecture 10 SP3 Kernel ver: independent Kernel ver: independent x64 11 No SP Kernel ver: independent Kernel ver: independent Kernel ver: independent Volume manager None LVM2 None LVM2 None LVM2 None LVM2 None LVM2 Volume manager version None Independent None Independent None Independent None Independent None Independent Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 28

29 x64 Kernel ver: independent None LVM2 None Independent SP1 None None Kernel ver: independent LVM2 Independent None None Kernel ver: independent LVM2 Independent x64 None None Kernel ver: independent LVM2 Independent Path Manager support matrix Table 31 to Table 37 provide the Path Manager support matrix for the Host Data Collector. Table 31 Host Data Collector Path Manager support matrix for Windows 2003 OS version Service pack Architecture Path Manager Path Manager version Standard Edition Enterprise Edition Datacenter Edition Web Edition Standard x64 Edition Enterprise x64 Edition Datacenter x64 Edition R2 Standard Edition R2 Enterprise Edition R2 Datacenter Edition R2 Standard x64 Edition R2 Enterprise x64 Edition R2 Datacenter x64 Edition SP2 HDLM to HDLM to SP2 x64 HDLM to SP2 HDLM to SP2 x64 HDLM to Table 32 Host Data Collector Path Manager support matrix for Windows 2008 OS version Service pack Architecture Path Manager Path Manager version Standard 32-bit Edition SP2 HDLM to Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 29

30 OS version Service pack Architecture Path Manager Enterprise 32-bit Edition Datacenter 32-bit Edition or Standard without Hyper-V 32-bit Edition Enterprise without Hyper-V 32-bit Edition Datacenter without Hyper- V 32-bit Edition Path Manager version for Itanium-based Systems SP2 HDLM to Standard Edition Enterprise Edition Datacenter Edition Standard without Hyper-V Edition Enterprise without Hyper-V Edition Datacenter without Hyper- V Edition R2 Standard R2 Enterprise R2 Datacenter R2 for Itanium-Based Systems SP2 x64 HDLM to No SP x64 HDLM to No SP HDLM to Table 33 Host Data Collector Path Manager support matrix for Solaris OS version Service pack Architecture Path Manager Path Manager version 9 None SPARC Kernel mode: 32-bit or 64- bit HDLM to 10 None SPARC Kernel mode: 32-bit or 64- bit x64 Kernel mode: 64-bit VxVM-DMP 5.0 HDLM VxVM-DMP to Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 30

31 Table 34 Host Data Collector Path Manager support matrix for AIX OS version Service pack Architecture Path Manager Path Manager version 5.3 None POWER Kernel mode: 32-bit or 64- bit 6.1 None POWER Kernel mode: 64-bit 7.1 None POWER Kernel mode: 64-bit HDLM HDLM HDLM to to to Table 35 Host Data Collector Path Manager support matrix for HP-UX OS version Service pack Architecture Path Manager Path Manager version 11iv2 None PA-RISC Kernel mode: 64-bit HDLM to HDLM to Table 36 Host Data Collector Path Manager support matrix for RedHatEL or RedHatELAP OS version Service pack Architecture Path Manager Path Manager version 5.4 None HDLM to HDLM to x64 HDLM to 5.5 None HDLM to HDLM to x64 HDLM to Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 31

32 Table 37 Host Data Collector Path Manager support matrix for SUSELES OS version Service pack Architecture Path Manager Path Manager version 10 SP3 HDLM to 11 No SP HDLM to SP1 HDLM to Device Manager agent requirements This chapter gives the system requirements of the Device Manager agent. Hardware requirements This section explains the system requirements for SAN environments that are supported by Device Manager agents. Caution: Before you connect the host with storage systems via FC-HUB (or FC-SWITCH), confirm whether FC-HUB (or FC-SWITCH) and its firmware are appropriate for the storage system: Check the corresponding HBA model. For details, seesupported Host Bus Adapter models. Check the FC-HUB (and firmware) supported by the target storage systems. Refer to the appropriate documentation for your storage system. Computer requirements The following table describes the computer requirements for Device Manager agent. Table 38 Computer requirements for Device Manager agent. OS Installation destination Required disk space Remarks Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 32

33 OS Installation destination Required disk space Remarks Windows For 32-bit () architecture system-drive\program Files\HITACHI\HDVM\HBaseAgent 180MB An additional 100 MB of temporary free space is required for the system drive during installation. For 64-bit ( or x64) architecture system-drive\program Files ()\HITACHI\HDVM\HBaseAgent For 32-bit () architecture 25MB system-drive\program Files\HITACHI\HGLMAgent system-drive\program Files\HDVM\HBaseAgent\mod\hglm For 64-bit ( or x64) architecture system-drive\program Files()\HITACHI\HGLMAgent systemdrive\program Files ()\HDVM\HBaseAgent\mod\hglm Solaris /opt/hdvm/hbaseagent 25MB The temporary free space during installations in /opt/hglmagent 25MB /var/tmp directory are /opt/hdvm/hbaseagent/mod/hglm also required. /var/opt 5MB New installation 30MB Overwrite installation 80MB AIX /usr/hdvm/hbaseagent 40MB The temporary free space /var 5MB during installations in /var/tmp directory are also required. New installation 30MB Overwrite installation 80MB Linux( or x64) /opt/hdvm/hbaseagent /var/opt 145MB 5MB The following temporary free space is required in the directory /var/tmp during installation: New installation 155 MB Overwrite installation 205 MB Linux /opt/hdvm/hbaseagent 145MB The following Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 33

34 OS Installation destination Required disk space () /var/opt 5MB Remarks temporary free space is required in the directory /var/tmp during installation: New installation 155 MB Overwrite installation 205 MB HP-UX /opt/hdvm/hbaseagent 25MB The temporary free space during installations in /opt/hglmagent 25MB /var/tmp directory are /opt/hdvm/hbaseagent/mod/hglm also required. /var/opt 5MB New installation 30MB Overwrite installation 80MB # The installation folder can be modified during new installation. Supported storage systems The following storage system models are supported by the Device Manager agent: Virtual Storage Platform Universal Storage Platform V/VM Hitachi USP Lightning 9900V Hitachi AMS 2000 Hitachi SMS Hitachi AMS/WMS Thunder 9500V If a host in which the Device Manager agent is installed is connected to a storage system, all HBA models supported by that storage system are available. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 34

35 Caution: When using Hitachi AMS 2000, Hitachi SMS, Hitachi AMS/WMS or Thunder 9500V, do not change the default settings of the following: Vendor ID Do not change the default setting (HITACHI). Product ID For Hitachi AMS 2000, Hitachi SMS, Hitachi AMS/WMS and Thunder 9500V, do not change the default setting (DF600F). Supported Host Bus Adapter models To obtain host WWN information, the HBA models shown in the following table and the HBA API library provided by the HBA vendor are required. Table 39 HBA models required to obtain host WWN information OS Model name Hitachi type name Windows Emulex LP8000 Not applicable Emulex LP9002DC Emulex LP9002L Emulex LP9802 QLogic QLA23xx #1 QLogic QLA24xx #1 Hitachi GV-CC62G1 Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable Solaris (SPARC edition) JNI FCI-1063 A-6516-FCPN Solaris (x64 Edition (AMD64)) JNI FC JNI FCE-6410 JNI FCE-6460 QLogic QLA2200 Sun HBA #2 QLogic QLA2310 Sun HBA A-6716-FCSN Not applicable Not applicable Not applicable Not applicable Not applicable Not applicable AIX IBM6227 Not applicable IBM6228 Not applicable Linux QLogic QLA2200F Not applicable QLogic QLA23xx QLogic QLA24xx Hitachi GV-CC62G1 Not applicable Not applicable Not applicable HP-UX HP A3404A HT-F3360-FC2 HP A3591B HT-F3360-FC3 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 35

36 OS Model name Hitachi type name HP A3636A HP A3740A HP A5158A HP A6684A HP A6685A HP A6795A HP A6826A HP A9784A HT-F3360-FC1 HT-F3360-PC5 HT-F3360-PC5A Not applicable Not applicable HT-F3360-PCFC Not applicable Not applicable #1: #2: In order to use a QLogic HBA, download and then install Fibre Channel Information Tool (fcinfo) version from the Microsoft web site. Even if the OS of a host where the Device Manager agent is installed is the version or x64 version, the fcinfo version must be used. When using an HBA by Oracle on Solaris 9, install Sun StorEdge SAN Foundation Software 4.2 or later. Note that if either of the following conditions is satisfied, obtaining host WWN information, alternate path WWN information, and LU information (such as file systems, usage, copy types, copy roles, and copy statuses) might not be possible: The host on which the Device Manager agent is running does not recognize the LU for the storage system. A multi-path configuration is set up in one of the following host environments, where the host OS is: Windows, and Dynamic Link Manager or Windows MPIO is used. Solaris, and Dynamic Link Manager or Sun StorEdge Traffic Manager is used. AIX, and MPIO is used. Supported iscsi connection configurations The Device Manager agent supports the iscsi connection configurations listed below in IPv4 environments only. Note that an instance of Device Manager connected by using iscsi can only manage storage systems that belong to Hitachi AMS 2000, Hitachi SMS and Hitachi AMS/WMS. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 36

37 Table 40 Supported iscsi connection configurations OS NIC or HBA Necessary drivers Windows NIC Microsoft iscsi Software Initiator (2.04 or later) Windows Server 2003 R2 Enterprise Edition ( or x64) Windows Server 2008 Enterprise Edition ( or x64) Windows Server 2008 R2 Enterprise Edition ( or x64) QLogic QLA4050c QLogic QLA4052c QLogic QLA4010c Microsoft iscsi Software Initiator (2.04 or later) and QLogic Driver Solaris NIC Included with the OS AIX NIC Included with the OS Linux NIC Included with the OS (Drivers are not installed by default.) HP-UX NIC Included with the OS Software requirements The following explains the system requirements for the Device Manager agent. Caution: The name of each host on which the Device Manager agent runs must be unique within the notification destination Device Manager server. Device Manager agent can connect to Device Manager server of the same version or later. However, if the version of the Device Manager server is later than that of the Device Manager agent, the Device Manager functionality that can be used is limited to that of the Device Manager agent. Supported operating systems The following table lists the supported operating systems for Device Manager agents. Table 41 Supported operating systems OS Version Architecture IPv6 environment support Remarks Windows Server No SP -- Not applicable 2003 R2 #1 x64 Edition -- Runs under WOW64. (EM64T and Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 37

38 OS Version Architecture IPv6 environment support AMD64) Remarks SP2 Not applicable x64 Edition (EM64T and AMD64) Runs under WOW64. Windows Server No SP 2008 #1 SP1 Not applicable -- Runs under WOW64. x64 Edition (EM64T and AMD64) SP2 Not applicable -- Runs under WOW64. x64 Edition (EM64T and AMD64) Windows Server No SP -- Runs under WOW R2 #1 x64 Edition (EM64T and AMD64) SP1 -- Runs under WOW64. x64 Edition (EM64T and AMD64) Solaris 8 SPARC (32 and 64 bit) 9 SPARC (32 and 64 bit) 10 #2 SPARC (32 and 64 bit) x64 Edition (AMD64) #3 AIX bit 64 bit -- We recommend that Solaris Patch Cluster be installed. Not applicable bit The Device Manager agent does not support environments where the Secure by Default function is enabled bit Not applicable HP-UX 11i v1 PA-RISC (32 and 64 bit) Workstation is not supported. 11i v2 PA-RISC (64bit) Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 38

39 OS Version Architecture IPv6 environment support Remarks 11i v3 PA-RISC (64bit) Red Hat Enterprise Linux Linux AS/ES 4 Update 1 -- Not applicable x64 Edition (EM64T) Linux AS/ES 4 Update 3 -- x64 Edition (EM64T) Linux AS/ES 4 Update 4 -- x64 Edition (EM64T) Linux AS/ES x64 Edition (EM64T) Linux AS/ES x64 Edition (EM64T) Linux AS/ES x64 Edition (EM64T) Linux AS/ES x64 Edition (EM64T) Linux AS/ES x64 Edition (EM64T) Linux x64 Edition (EM64T) Linux 5.1 #4 -- Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 39

40 OS Version Architecture IPv6 environment support Remarks x64 Edition (EM64T) Linux x64 Edition (EM64T) Linux x64 Edition (EM64T) Linux x64 Edition (EM64T) Linux x64 Edition (EM64T) Linux x64 Edition (EM64T) Linux 6.0 x64 Edition (EM64T) Linux 6.1 #6 x64 Edition (EM64T) SUSE Linux Enterprise Server 9 SP1 SP2 SP3 SP4 -- Only the default kernel is supported. SUSE Linux Enterprise Server 10 #5 No SP SP1 SP2 SP3 x64 Edition (EM64T) -- SP4 x64 Edition (EM64T) SUSE Linux No SP -- Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 40

41 OS Version Architecture IPv6 environment support Remarks Enterprise Server 11 SP1 x64 Edition (EM64T) Legend : Supported. --: Not supported. Note: Third-party agents are available for other servers. For the latest information about these agents, please contact your Hitachi Data System representative or refer to documentation about a specific agent. #1: #2: #3: #4: #5: #6: If Windows Firewall has been enabled, the Device Manager agent must be registered as an exception with Windows Firewall when a new installation of the Device Manager agent is performed. The Device Manager agent runs in the usual global environment (global zone) only. If a non-global zone has been created, install the Device Manager agent in the global zone. The Device Manager agent supports only the Sun Fire x64 server family hardware. In addition, only the 64-bit kernel mode is supported. The following library is required: glibc el5_1.1 or later. The module of gdb or later is necessary. The package of glibc-<rpm-package-version>.i686.rpm is necessary. Caution: The Device Manager agent only supports global addresses. ou cannot use link-local addresses or global unique local addresses (sitelocal addresses). Required patches for operating systems When using the Device Manager agent, it is assumed that the OS patches or succeeding patches listed in Table 43 Required patches and succeeding patches for Solaris 8 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 41

42 Required patches SunOS 5.8: 32-Bit Shared library patch for C SunOS 5.8: 64-Bit Shared library patch for C SunOS 5.8: kernel update and Apache patch SunOS 5.8: IIIM and X Input & Output Method patch Succeeding patches , , , , None CDE 1.4: dtwm patch , Motif and 2.1.1: Runtime library patch for Solaris SunOS 5.8: Patch for patchadd and patchrm SunOS 5.8: /usr/kernel/sys/acctctl and /usr/kernel/sys/exacctsys patch None None SunOS 5.8: linker patch None SunOS 5.8: libresolv.so.2 and in.named patch , , , , , , SunOS 5.8: RBAC Feature Patch None SunOS 5.8: /usr/lib/fs/ufs utilities patch SunOS 5.8: /kernel/fs/mntfs and /kernel/fs/sparcv9/mntfs patch None SunOS 5.8: /usr/bin/nawk patch None SunOS 5.8: /usr/lib/libmtmalloc.so.1 patch SunOS 5.8: /usr/lib/libdhcpagent.so.1 patch SunOS 5.8: /sbin/init and /usr/sbin/init patch SunOS 5.8: Unable to load fontset in 64-bit Solaris 8 iso-1 or iso-15 None. None. None. None SunOS 5.8: /usr/bin/fgrep patch None SunOS 5.8: /kernel/drv/random patch SunOS 5.8: Font2DTest2 abort when Lucida Sans Thai Typewriter selected None. None SunOS 5.8: mount patch OpenGL 1.3: OpenGL Patch for Solaris (32-bit) OpenGL 1.3: OpenGL Patch for Solaris (64-bit) SunOS 5.8: /sbin/sulogin and /sbin/netstrategy patch None. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 42

43 Required patches Succeeding patches SunOS 5.8: /sbin/uadmin and /sbin/hostconfig patch None SunOS 5.8: Kernel Patch None SunOS 5.8: kernel patch , , , , , , , , X : Xsun patch , SunOS 5.8: fsck patch None SunOS 5.8: LDAP2 client, libc, libthread and libnsl libraries patch , , , , , , , , , , , Note: The architecture is SPARC (32 or 64 bit). ou can also install the required patches by applying J2SE Solaris 8 Recommended Patch Cluster. For details on the latest information, see the Oracle web site. Table 44 Required patches and succeeding patches for Solaris 9 Required patches SunOS 5.9: 32-bit Shared library patch for C SunOS 5.9: 64-Bit Shared library patch for C++ Succeeding patches , , , , , , , , , , , , , , , , , , , , , , , , X : Xsun patch , SunOS 5.9: linker Patch , , , X : OWconfig patch None OpenGL 1.3: OpenGL Patch for Solaris (32-bit) OpenGL 1.3: OpenGL Patch for Solaris (64-bit) Note: The architecture is SPARC (32 or 64 bit). ou can also install the required patches by applying J2SE Solaris 9 Recommended Patch Cluster. For details on the latest information, see the Oracle web site. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 43

44 Table 45 Required patches and succeeding patches for Solaris 10 Architecture Required patches Succeeding patches SPARC (32 and 64 bit) SunOS 5.10: kernel patch None SunOS 5.10: Solaris Crypto Framework patch None SunOS 5.10: svccfg & svcprop patch SunOS 5.10: Sun iscsi Device Driver and Utilities SunOS 5.10: Install and Patch Utilities Patch , None , , , , , , , , , , , , , , , , , , , , , , , , , , , , SunOS 5.10: FMA Patch None SunOS 5.10: libzonecfg Patch None SunOS 5.10: zones library and zones utility patch None SunOS 5.10: pkcs11_softtoken patch # x64 Edition (AMD64) (Version of the Java execution environment) SunOS 5.10_: Sun iscsi Device Driver and Utilities None SunOS 5.10_: pkcs11_softtoken patch # x64 Edition (AMD64) (Version 5.0 of the Java execution environment) SunOS 5.10_: SUNWgrub patch SunOS 5.10_: biosdev patch SunOS 5.10_: Fault Manager Patch SunOS 5.10_: Sun iscsi Device Driver and Utilities None. None. None. None. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 44

45 Architecture Required patches Succeeding patches SunOS 5.10_: Install and Patch Utilities Patch SunOS 5.10_: Shared library patch for C++_ SunOS 5.10_: libzonecfg patch SunOS 5.10_: cadp160 driver patch SunOS 5.10_: zoneadmd, zlogin and zoneadm patch SunOS 5.10_: umountall patch , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , None. None. None , SunOS 5.10_: pkcs11_softtoken patch # Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 45

46 Note: ou can also install the required patches by applying J2SE Solaris 10 Recommended Patch Cluster. For details on the latest information, see the Oracle web site. #: Apply this patch if you use Solaris 10 11/06 (update 3), Solaris 10 8/07 (update 4), Solaris 10 5/08 (update 5), or Solaris 10 10/08 (update 6). Check the update numbers by referencing the /etc/release file. The following shows an example of the /etc/release file for Solaris 10 11/06. Assembled 14 November 2006 Solaris 10 11/06 s10s_u3wos_10 SPARC Copyright 2006 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 14 November 2006 Table 46 Required patches and succeeding patches for AIX 5.3 Java execution environment Version Version 5.0 Version 6.0 Required patches (APAR I69190) (APAR I71011) (APAR IZ07976) Succeeding patches , , , , , , , , , , , , , , , , , , , , , Note: The architecture is 32 or 64 bit. For details on the latest information, see the IBM web site. Table 47 Required patches and succeeding patches for AIX 6.1 Java execution environment Required patches Succeeding patches Version , , , , , Version , , , , , Version , , , , , Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 46

47 Note: The architecture is 64 bit. For details on the latest information, see the IBM web site. Table 48 Required patches and succeeding patches for AIX 7.1 Java execution environment Required patches Succeeding patches Version Version Version Note: The architecture is 64 bit. For details on the latest information, see the IBM web site. Table 49 Required patches for Linux OS Architecture Patches Red Hat Enterprise Linux 5.1 SUSE Linux Enterprise Server 10 x64 Edition (EM64T) x64 Edition (EM64T) glibc el5_1.1 or later nscd el5_1.1 or later gdb or later Table 50 Required patches and succeeding patches for HP-UX 11i v1 Required patches PHCO_25226 s700_ Initialised TLS, Psets, Mutex performance PHCO_25452 s700_ libc cumulative patch Java execution environment Version Version 5.0 Version 6.0 Succeeding patches PHCO_26466, PHCO_27632, PHCO_29109, PHCO_29960, PHCO_30544, PHCO_33282, PHCO_36229, PHCO_38307 PHCO_26124, PHCO_27434, PHCO_27740, PHCO_27910, PHCO_28427, PHCO_29029, PHCO_29287, PHCO_29495, PHCO_29955, PHCO_30030, PHCO_30530, PHCO_31061, PHCO_31903, PHCO_32761, PHCO_33360, PHCO_33533, PHCO_33711, PHCO_34275, Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 47

48 Required patches PHCO_29960 s700_ Pthread enhancement and fixes PHKL_24253 s700_ thread nostop patch supporting NFS PHKL_24254 s700_ thread nostop patch supporting NFS PHKL_24255 s700_ thread nostop patch supporting NFS PHKL_24256 s700_ signal race condition patch/threads enh PHKL_24257 s700_ thread nostop patch supporting NFS PHKL_24751 s700_ preserve IPSW W-bit and GR31 lower bits PHKL_25227 s700_ VM/JFS deadlock; mmap performance/defect PHKL_25367 s700_ Priority inversion and thread hang PHKL_25468 s700_ eventport (/dev/poll) pseudo driver PHKL_25614 s700_ VM-JFS deadlock, mmap, perf thread creation PHKL_25728 s700_ Psets Enablement, thread cumulative Java execution environment Succeeding patches PHCO_35743, PHCO_36184, PHCO_37369, PHCO_38279, PHCO_40310 PHCO_30544, PHCO_33282, PHCO_36229, PHCO_38307 PHKL_24569, PHKL_25994, PHKL_30216, PHKL_32061, PHKL_34309, PHKL_35879, PHKL_36035, PHKL_40455 PHKL_24568, PHKL_25728, PHKL_25840, PHKL_27092, PHKL_27294, PHKL_27317, PHKL_29707, PHKL_30032, PHKL_30216, PHKL_32061, PHKL_34309, PHKL_35879, PHKL_36035, PHKL_40455 PHKL_25652, PHKL_25993 PHKL_24567, PHKL_25729, PHKL_28122 PHKL_23665, PHKL_24551, PHKL_25389, PHKL_27091, PHKL_29706, PHKL_30033, PHKL_30587, PHKL_31993, PHKL_33328, PHKL_33336, PHKL_34310, PHKL_35281, PHKL_36948 None. PHKL_25614, PHKL_26233, PHKL_27278, PHKL_28267, PHKL_28428, PHKL_28990, PHKL_30158, PHKL_30616, PHKL_31003, PHKL_32578, PHKL_32806, PHKL_33261, PHKL_33270, PHKL_33988, PHKL_35464, PHKL_35564, PHKL_41910 PHKL_26468, PHKL_27316, PHKL_30837, PHKL_34534, PHKL_38299, PHKL_38430 PHKL_30542, PHKL_40704 PHKL_26233, PHKL_27278, PHKL_28267, PHKL_28428, PHKL_28990, PHKL_30158, PHKL_30616, PHKL_31003, PHKL_32578, PHKL_32806, PHKL_33261, PHKL_33270, PHKL_33988, PHKL_35464, PHKL_35564, PHKL_41910 PHKL_25840, PHKL_27092, PHKL_27294, PHKL_27317, PHKL_29707, PHKL_30032, Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 48

49 Required patches PHKL_25729 s700_ signals, threads enhancement, Psets Enablement PHKL_25840 s700_ Thread NOSTOP, Psets, Thread Abort PHKL_25842 s700_ Thread Abort PHKL_25871 s700_ eventport syscalls;socket close(2) hang fix PHKL_27091 s700_ Core PM, vpar, Psets Cumulative, slpq1 perf PHKL_27092 s700_ Thread NOSTOP, Abort; Psets PHKL_28489 s700_ copyin EFAULT, LDCD access type PHKL_32927 s700_ PA-8800 Fix Java (64-bit JVM) process hang PHKL_34534 s700_ vpar,callout, abstime, sync perf, wakeup PHNE_23502 s700_ ONC/NFS General Release/Performance Patch PHNE_25084 s700_ Java execution environment Succeeding patches PHKL_30216, PHKL_32061, PHKL_34309, PHKL_35879, PHKL_36035, PHKL_40455 PHKL_28122 PHKL_27092, PHKL_27294, PHKL_27317, PHKL_29707, PHKL_30032, PHKL_30216, PHKL_32061, PHKL_34309, PHKL_35879, PHKL_36035, PHKL_40455 PHKL_30288, PHKL_34311, PHKL_35145 PHKL_25995, PHKL_29826, PHKL_30317, PHKL_30541, PHKL_30557, PHKL_32374, PHKL_32457, PHKL_34024, PHKL_35091, PHKL_37753, PHKL_39133 PHKL_29706, PHKL_30033, PHKL_30587, PHKL_31993, PHKL_33328, PHKL_33336, PHKL_34310, PHKL_35281, PHKL_36948 PHKL_27294, PHKL_27317, PHKL_29707, PHKL_30032, PHKL_30216, PHKL_32061, PHKL_34309, PHKL_35879, PHKL_36035, PHKL_40455 None. PHKL_36763 PHKL_38299, PHKL_38430 PHNE_24035, PHNE_24910, PHNE_25625, PHNE_25627, PHNE_26388, PHNE_27218, PHNE_28103, PHNE_28568, PHNE_28983, PHNE_29211, PHNE_29303, PHNE_29783, PHNE_29883, PHNE_30378, PHNE_30380, PHNE_30661, PHNE_31097, PHNE_31929, PHNE_32477, PHNE_32811, PHNE_33315, PHNE_33498, PHNE_33971, PHNE_34293, PHNE_34662, PHNE_34938, PHNE_35418, PHNE_35871, PHNE_36168, PHNE_37110, PHNE_37568, PHNE_39167, PHNE_41023 PHNE_26728, PHNE_27703, Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 49

50 Required patches Cumulative STREAMS Patch PHNE_29887 s700_ cumulative ARPA Transport patch PHSS_24932 s700_ Japanese TrueType font patch PHSS_24934 s700_ Korean TrueType font patch PHSS_24936 s700_ Chinese- S TrueType font patch for PHSS_25449 s700_ X/Motif Runtime OCT2001 Periodic Patch PHSS_25881 s700_ X/Motif Runtime JAN2002 Periodic Patch PHSS_30049 s700_ ld(1) and linker tools cumulative patch PHSS_35385 s700_ ld(1) and linker tools cumulative patch Java execution environment Version 6.0 Succeeding patches PHNE_28476, PHNE_29825, PHNE_30367, PHNE_31091, PHNE_33313, PHNE_33729, PHNE_34131, PHNE_34777, PHNE_35453, PHNE_36576, PHNE_37259 PHNE_31247, PHNE_33159, PHNE_33628, PHNE_34135, PHNE_34672, PHNE_35183, PHNE_35351, PHNE_36125, PHNE_37671, PHNE_37898, PHNE_38678, PHNE_39386, PHNE_42029 PHSS_26971 PHSS_26973 PHSS_26975 PHSS_25881, PHSS_27234, PHSS_27425, PHSS_28370, PHSS_28875, PHSS_29371, PHSS_30262, PHSS_30787, PHSS_31000, PHSS_33130, PHSS_35711, PHSS_37028 PHSS_27234, PHSS_27425, PHSS_28370, PHSS_28875, PHSS_29371, PHSS_30262, PHSS_30787, PHSS_31000, PHSS_33130, PHSS_35711, PHSS_37028 PHSS_30966, PHSS_30968, PHSS_30970, PHSS_32864, PHSS_33033, PHSS_33035, PHSS_33037, PHSS_35379, PHSS_35381, PHSS_35383, PHSS_35385, PHSS_37516, PHSS_37517, PHSS_38154, PHSS_39077, PHSS_39749, PHSS_40549, PHSS_41214, PHSS_41713, PHSS_42253 PHSS_37516, PHSS_37517, PHSS_38154, PHSS_39077, PHSS_39749, PHSS_40549, PHSS_41214, PHSS_41713, PHSS_42253 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 50

51 Note: The architecture is PA-RISC (32 or 64 bit). Depending on the OS release date, required patches might have been applied at the time of delivery. For details on the latest information, see the HP web site. Table 51 Required patches and succeeding patches for HP-UX 11i v2 Architecture Required patches Succeeding patches PA-RISC (64bit) (Version 5.0 of the Java execution environment) PA-RISC (64bit) (Version 6.0 of the Java execution environment) (Version of the Java execution environment) PHSS_33349 s700_ linker + fdp cumulative patch PHSS_37201s700_ linker + fdp cumulative patch PHSS_33349 s700_ linker + fdp cumulative patch PHCO_30476 s700_ Pthread library patch PHKL_30192 s700_ Eliminate race at MxN kernel thread creation PHSS_30015 s700_ Aries cumulative patch PHSS_34040, PHSS_34353, PHSS_34440, PHSS_34858, PHSS_34860, PHSS_35979, PHSS_36336, PHSS_36342, PHSS_37201, PHSS_37492, PHSS_37947, PHSS_39093, PHSS_38134, PHSS_39821, PHSS_40537, PHSS_41178, PHSS_41491, PHSS_42043 PHSS_37492, PHSS_37947, PHSS_38134, PHSS_39093, PHSS_39821, PHSS_40537, PHSS_41178, PHSS_41491, PHSS_42043 PHSS_34040, PHSS_34353, PHSS_34440, PHSS_34858, PHSS_34860, PHSS_35979, PHSS_36336, PHSS_36342, PHSS_37201, PHSS_37492, PHSS_37947, PHSS_38134, PHSS_39093, PHSS_40537, PHSS_41178, PHSS_41491, PHSS_42043 PHCO_30543, PHCO_31553, PHCO_32489, PHCO_33675, PHCO_34718, PHCO_34944, PHCO_35997, PHCO_36323, PHCO_37543, PHCO_37940, PHCO_38955, PHCO_39699, PHCO_41946 PHKL_31500 PHSS_30237, PHSS_30674, PHSS_30779, PHSS_31816, PHSS_32213, PHSS_32502, PHSS_34201, PHSS_35045, PHSS_35528, PHSS_36519, PHSS_37552, PHSS_38526, PHSS_39293, PHSS_39897, PHSS_41098, PHSS_41422 (Version 5.0 of the Java execution environment) PHCO_30476 s700_ Pthread library patch PHCO_30543, PHCO_31553, PHCO_32489, PHCO_33675, PHCO_34718, PHCO_34944, PHCO_35997, PHCO_36323, PHCO_37543, PHCO_37940, PHCO_38955, PHCO_39699, PHCO_41946 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 51

52 Architecture Required patches Succeeding patches (Version 6.0 of the Java execution environment) PHKL_30192 s700_ Eliminate race at MxN kernel thread creation PHKL_35029 s700_ ksleep cumulative patch PHSS_30015 s700_ Aries cumulative patch PHSS_33349 s700_ linker + fdp cumulative patch PHSS_33350 s700_ ac++ Runtime PHSS_34043 s700_ Integrity Unwind Library PHSS_25045 s700_ solves problem emulating floating point patch PHKL_36667 s700_ mmap patch PHSS_30015 s700_ Aries cumulative patch PHKL_30192 s700_ Eliminate race at MxN kernel thread creation PHCO_30476 s700_ Pthread library patch PHKL_31500 PHKL_36826, PHKL_37121, PHKL_41057 PHSS_30237, PHSS_30674, PHSS_30779, PHSS_31816, PHSS_32213, PHSS_32502, PHSS_34201, PHSS_35045, PHSS_35528, PHSS_36519, PHSS_37552, PHSS_38526, PHSS_39293, PHSS_39897, PHSS_41098, PHSS_41422 PHSS_34040, PHSS_34353, PHSS_34440, PHSS_34858, PHSS_34860, PHSS_35979, PHSS_36336, PHSS_36342, PHSS_37201, PHSS_37492, PHSS_37947, PHSS_38134, PHSS_39093, PHSS_40537, PHSS_41178, PHSS_41491, PHSS_42043 PHSS_34041, PHSS_34441, PHSS_35055, PHSS_35978, PHSS_36343, PHSS_37500, PHSS_38140, PHSS_40543, PHSS_41184 PHSS_34854, PHSS_34859, PHSS_36345, PHSS_37039, PHSS_37498, PHSS_37953, PHSS_38138, PHSS_39101, PHSS_40541, PHSS_41182, PHSS_41495 PHSS_35528, PHSS_36519, PHSS_37552, PHSS_38526, PHSS_39293, PHSS_39897, PHSS_41098, PHSS_41422 PHKL_37653, PHKL_39436, PHKL_39901, PHKL_40094, PHKL_41002, PHKL_41807 PHSS_30237, PHSS_30674, PHSS_30779, PHSS_31816, PHSS_32213, PHSS_32502, PHSS_34201, PHSS_35045, PHSS_35528, PHSS_36519, PHSS_37552, PHSS_38526, PHSS_39293, PHSS_39897, PHSS_41098, PHSS_41422 PHKL_31500 PHCO_30543, PHCO_31553, PHCO_32489, PHCO_33675, PHCO_34718, PHCO_34944, PHCO_35997, PHCO_36323, PHCO_37543, PHCO_37940, PHCO_38955, PHCO_39699, PHCO_41946 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 52

53 Architecture Required patches Succeeding patches PHSS_33349 s700_ linker + fdp cumulative patch PHSS_33350 s700_ ac++ Runtime PHSS_34043 s700_ Integrity Unwind Library PHKL_35029 s700_ ksleep cumulative patch PHSS_35045 s700_ Aries cumulative patch PHKL_36667 s700_ mmap(2),mlock[all](2),madvise(2),msync(2) PHSS_34040, PHSS_34353, PHSS_34440, PHSS_34858, PHSS_34860, PHSS_35979, PHSS_36336, PHSS_36342, PHSS_37201, PHSS_37492, PHSS_37947, PHSS_38134, PHSS_39093, PHSS_40537, PHSS_41178, PHSS_41491, PHSS_42043 PHSS_34041, PHSS_34441, PHSS_35055, PHSS_35978, PHSS_36343, PHSS_37500, PHSS_38140, PHSS_40543, PHSS_41184 PHSS_34854, PHSS_34859, PHSS_36345, PHSS_37039, PHSS_37498, PHSS_37953, PHSS_38138, PHSS_39101, PHSS_40541, PHSS_41182, PHSS_41495 PHKL_36826, PHKL_37121, PHKL_41057 PHSS_35528, PHSS_36519, PHSS_37552, PHSS_38526, PHSS_39293, PHSS_39897, PHSS_41098, PHSS_41422 PHKL_37653, PHKL_39436, PHKL_39901, PHKL_40094, PHKL_41002, PHKL_41807 Note: Depending on the OS release date, required patches might have been applied at the time of delivery. For details on the latest information, see the HP web site. Table 52 Required patches and succeeding patches for HP-UX 11i v3 Architecture Required patches Succeeding patches PA-RISC (64bit) (Version of the Java execution environment) PA-RISC (64bit) (Version 5.0 of the Java execution environment) PHKL_ scheduler cumulative patch PHKL_ scheduler cumulative patch PHKL_40207, PHKL_40941, PHKL_40963, PHKL_41481, PHKL_41981 PHKL_40207, PHKL_40941, PHKL_40963, PHKL_41481, PHKL_41981 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 53

54 Architecture Required patches Succeeding patches PA-RISC (64bit) (Version 6.0 of the Java execution environment) (Version of the Java execution environment) (Version 5.0 of the Java execution environment) (Version 6.0 of the Java execution environment) PHSS_ linker + fdp cumulative patch PHKL_ scheduler cumulative patch PHKL_ scheduler cumulative patch PHCO_ pthread library cumulative patch PHKL_ scheduler cumulative patch PHSS_ ac++ Runtime (IA: A.06.16, PA: A.03.76) PHCO_ pthread library cumulative patch PHSS_ Integrity Unwind Library PHSS_ ac++ Runtime (IA: A.06.16, PA: A.03.76) PHCO_ pthread library cumulative patch PHSS_ Integrity Unwind Library PHKL_ scheduler cumulative patch PHSS_37493, PHSS_37948, PHSS_37955, PHSS_38135, PHSS_39094, PHSS_39822, PHSS_40538, PHSS_41179, PHSS_41492, PHSS_42040 PHKL_40207, PHKL_40941, PHKL_40963, PHKL_41481, PHKL_41981 PHKL_40207, PHKL_40941, PHKL_40963, PHKL_41481, PHKL_41981 PHCO_38837, PHCO_39604, PHCO_40211, PHCO_41092, PHCO_41291, PHCO_41407, PHCO_42165, PHCO_42326 PHKL_40207, PHKL_40941, PHKL_40963, PHKL_41481, PHKL_41981 PHSS_38141, PHSS_40544, PHSS_41185 PHCO_38837, PHCO_39604, PHCO_40211, PHCO_41092, PHCO_41291, PHCO_41407, PHCO_42165, PHCO_42326 PHSS_39102, PHSS_40542, PHSS_41183, PHSS_41496 PHSS_38141, PHSS_40544, PHSS_41185 PHCO_38837, PHCO_39604, PHCO_40211, PHCO_41092, PHCO_41291, PHCO_41407, PHCO_42165, PHCO_42326 PHSS_39102, PHSS_40542, PHSS_41183, PHSS_41496 PHKL_40207, PHKL_40941, PHKL_40963, PHKL_41481, PHKL_41981 to Error! Reference source not found. have been applied. The following tables only list the OSs to which patches must be applied. Table 42 Required patches for Windows OS Architecture Patches Windows Server 2003 R2 (No SP) x64 (EM64T and AMD64) KB KB Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 54

55 Table 43 Required patches and succeeding patches for Solaris 8 Required patches SunOS 5.8: 32-Bit Shared library patch for C SunOS 5.8: 64-Bit Shared library patch for C SunOS 5.8: kernel update and Apache patch SunOS 5.8: IIIM and X Input & Output Method patch Succeeding patches , , , , None CDE 1.4: dtwm patch , Motif and 2.1.1: Runtime library patch for Solaris SunOS 5.8: Patch for patchadd and patchrm SunOS 5.8: /usr/kernel/sys/acctctl and /usr/kernel/sys/exacctsys patch None None SunOS 5.8: linker patch None SunOS 5.8: libresolv.so.2 and in.named patch , , , , , , SunOS 5.8: RBAC Feature Patch None SunOS 5.8: /usr/lib/fs/ufs utilities patch SunOS 5.8: /kernel/fs/mntfs and /kernel/fs/sparcv9/mntfs patch None SunOS 5.8: /usr/bin/nawk patch None SunOS 5.8: /usr/lib/libmtmalloc.so.1 patch SunOS 5.8: /usr/lib/libdhcpagent.so.1 patch SunOS 5.8: /sbin/init and /usr/sbin/init patch SunOS 5.8: Unable to load fontset in 64-bit Solaris 8 iso-1 or iso-15 None. None. None. None SunOS 5.8: /usr/bin/fgrep patch None SunOS 5.8: /kernel/drv/random patch SunOS 5.8: Font2DTest2 abort when Lucida Sans Thai Typewriter selected None. None SunOS 5.8: mount patch OpenGL 1.3: OpenGL Patch for Solaris (32-bit) OpenGL 1.3: OpenGL Patch for Solaris (64-bit) Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 55

56 Required patches Succeeding patches SunOS 5.8: /sbin/sulogin and /sbin/netstrategy patch SunOS 5.8: /sbin/uadmin and /sbin/hostconfig patch None. None SunOS 5.8: Kernel Patch None SunOS 5.8: kernel patch , , , , , , , , X : Xsun patch , SunOS 5.8: fsck patch None SunOS 5.8: LDAP2 client, libc, libthread and libnsl libraries patch , , , , , , , , , , , Note: The architecture is SPARC (32 or 64 bit). ou can also install the required patches by applying J2SE Solaris 8 Recommended Patch Cluster. For details on the latest information, see the Oracle web site. Table 44 Required patches and succeeding patches for Solaris 9 Required patches SunOS 5.9: 32-bit Shared library patch for C SunOS 5.9: 64-Bit Shared library patch for C++ Succeeding patches , , , , , , , , , , , , , , , , , , , , , , , , X : Xsun patch , SunOS 5.9: linker Patch , , , X : OWconfig patch None OpenGL 1.3: OpenGL Patch for Solaris (32-bit) OpenGL 1.3: OpenGL Patch for Solaris (64-bit) Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 56

57 Note: The architecture is SPARC (32 or 64 bit). ou can also install the required patches by applying J2SE Solaris 9 Recommended Patch Cluster. For details on the latest information, see the Oracle web site. Table 45 Required patches and succeeding patches for Solaris 10 Architecture Required patches Succeeding patches SPARC (32 and 64 bit) SunOS 5.10: kernel patch None SunOS 5.10: Solaris Crypto Framework patch None SunOS 5.10: svccfg & svcprop patch SunOS 5.10: Sun iscsi Device Driver and Utilities SunOS 5.10: Install and Patch Utilities Patch , None , , , , , , , , , , , , , , , , , , , , , , , , , , , , SunOS 5.10: FMA Patch None SunOS 5.10: libzonecfg Patch None SunOS 5.10: zones library and zones utility patch None SunOS 5.10: pkcs11_softtoken patch # x64 Edition (AMD64) (Version of the Java execution environment) SunOS 5.10_: Sun iscsi Device Driver and Utilities None SunOS 5.10_: pkcs11_softtoken patch # x64 Edition (AMD64) (Version 5.0 of the Java execution environment) SunOS 5.10_: SUNWgrub patch SunOS 5.10_: biosdev patch SunOS 5.10_: Fault Manager Patch None. None. None. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 57

58 Architecture Required patches Succeeding patches SunOS 5.10_: Sun iscsi Device Driver and Utilities SunOS 5.10_: Install and Patch Utilities Patch SunOS 5.10_: Shared library patch for C++_ SunOS 5.10_: libzonecfg patch SunOS 5.10_: cadp160 driver patch SunOS 5.10_: zoneadmd, zlogin and zoneadm patch SunOS 5.10_: umountall patch None , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , None. None. None , SunOS 5.10_: pkcs11_softtoken patch # Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 58

59 Note: ou can also install the required patches by applying J2SE Solaris 10 Recommended Patch Cluster. For details on the latest information, see the Oracle web site. #: Apply this patch if you use Solaris 10 11/06 (update 3), Solaris 10 8/07 (update 4), Solaris 10 5/08 (update 5), or Solaris 10 10/08 (update 6). Check the update numbers by referencing the /etc/release file. The following shows an example of the /etc/release file for Solaris 10 11/06. Assembled 14 November 2006 Solaris 10 11/06 s10s_u3wos_10 SPARC Copyright 2006 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 14 November 2006 Table 46 Required patches and succeeding patches for AIX 5.3 Java execution environment Version Version 5.0 Version 6.0 Required patches (APAR I69190) (APAR I71011) (APAR IZ07976) Succeeding patches , , , , , , , , , , , , , , , , , , , , , Note: The architecture is 32 or 64 bit. For details on the latest information, see the IBM web site. Table 47 Required patches and succeeding patches for AIX 6.1 Java execution environment Required patches Succeeding patches Version , , , , , Version , , , , , Version , , , , , Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 59

60 Note: The architecture is 64 bit. For details on the latest information, see the IBM web site. Table 48 Required patches and succeeding patches for AIX 7.1 Java execution environment Required patches Succeeding patches Version Version Version Note: The architecture is 64 bit. For details on the latest information, see the IBM web site. Table 49 Required patches for Linux OS Architecture Patches Red Hat Enterprise Linux 5.1 SUSE Linux Enterprise Server 10 x64 Edition (EM64T) x64 Edition (EM64T) glibc el5_1.1 or later nscd el5_1.1 or later gdb or later Table 50 Required patches and succeeding patches for HP-UX 11i v1 Required patches PHCO_25226 s700_ Initialised TLS, Psets, Mutex performance PHCO_25452 s700_ libc cumulative patch Java execution environment Version Version 5.0 Version 6.0 Succeeding patches PHCO_26466, PHCO_27632, PHCO_29109, PHCO_29960, PHCO_30544, PHCO_33282, PHCO_36229, PHCO_38307 PHCO_26124, PHCO_27434, PHCO_27740, PHCO_27910, PHCO_28427, PHCO_29029, PHCO_29287, PHCO_29495, PHCO_29955, PHCO_30030, PHCO_30530, PHCO_31061, PHCO_31903, PHCO_32761, PHCO_33360, PHCO_33533, PHCO_33711, PHCO_34275, Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 60

61 Required patches PHCO_29960 s700_ Pthread enhancement and fixes PHKL_24253 s700_ thread nostop patch supporting NFS PHKL_24254 s700_ thread nostop patch supporting NFS PHKL_24255 s700_ thread nostop patch supporting NFS PHKL_24256 s700_ signal race condition patch/threads enh PHKL_24257 s700_ thread nostop patch supporting NFS PHKL_24751 s700_ preserve IPSW W-bit and GR31 lower bits PHKL_25227 s700_ VM/JFS deadlock; mmap performance/defect PHKL_25367 s700_ Priority inversion and thread hang PHKL_25468 s700_ eventport (/dev/poll) pseudo driver PHKL_25614 s700_ VM-JFS deadlock, mmap, perf thread creation PHKL_25728 s700_ Psets Enablement, thread cumulative Java execution environment Succeeding patches PHCO_35743, PHCO_36184, PHCO_37369, PHCO_38279, PHCO_40310 PHCO_30544, PHCO_33282, PHCO_36229, PHCO_38307 PHKL_24569, PHKL_25994, PHKL_30216, PHKL_32061, PHKL_34309, PHKL_35879, PHKL_36035, PHKL_40455 PHKL_24568, PHKL_25728, PHKL_25840, PHKL_27092, PHKL_27294, PHKL_27317, PHKL_29707, PHKL_30032, PHKL_30216, PHKL_32061, PHKL_34309, PHKL_35879, PHKL_36035, PHKL_40455 PHKL_25652, PHKL_25993 PHKL_24567, PHKL_25729, PHKL_28122 PHKL_23665, PHKL_24551, PHKL_25389, PHKL_27091, PHKL_29706, PHKL_30033, PHKL_30587, PHKL_31993, PHKL_33328, PHKL_33336, PHKL_34310, PHKL_35281, PHKL_36948 None. PHKL_25614, PHKL_26233, PHKL_27278, PHKL_28267, PHKL_28428, PHKL_28990, PHKL_30158, PHKL_30616, PHKL_31003, PHKL_32578, PHKL_32806, PHKL_33261, PHKL_33270, PHKL_33988, PHKL_35464, PHKL_35564, PHKL_41910 PHKL_26468, PHKL_27316, PHKL_30837, PHKL_34534, PHKL_38299, PHKL_38430 PHKL_30542, PHKL_40704 PHKL_26233, PHKL_27278, PHKL_28267, PHKL_28428, PHKL_28990, PHKL_30158, PHKL_30616, PHKL_31003, PHKL_32578, PHKL_32806, PHKL_33261, PHKL_33270, PHKL_33988, PHKL_35464, PHKL_35564, PHKL_41910 PHKL_25840, PHKL_27092, PHKL_27294, PHKL_27317, PHKL_29707, PHKL_30032, Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 61

62 Required patches PHKL_25729 s700_ signals, threads enhancement, Psets Enablement PHKL_25840 s700_ Thread NOSTOP, Psets, Thread Abort PHKL_25842 s700_ Thread Abort PHKL_25871 s700_ eventport syscalls;socket close(2) hang fix PHKL_27091 s700_ Core PM, vpar, Psets Cumulative, slpq1 perf PHKL_27092 s700_ Thread NOSTOP, Abort; Psets PHKL_28489 s700_ copyin EFAULT, LDCD access type PHKL_32927 s700_ PA-8800 Fix Java (64-bit JVM) process hang PHKL_34534 s700_ vpar,callout, abstime, sync perf, wakeup PHNE_23502 s700_ ONC/NFS General Release/Performance Patch PHNE_25084 s700_ Java execution environment Succeeding patches PHKL_30216, PHKL_32061, PHKL_34309, PHKL_35879, PHKL_36035, PHKL_40455 PHKL_28122 PHKL_27092, PHKL_27294, PHKL_27317, PHKL_29707, PHKL_30032, PHKL_30216, PHKL_32061, PHKL_34309, PHKL_35879, PHKL_36035, PHKL_40455 PHKL_30288, PHKL_34311, PHKL_35145 PHKL_25995, PHKL_29826, PHKL_30317, PHKL_30541, PHKL_30557, PHKL_32374, PHKL_32457, PHKL_34024, PHKL_35091, PHKL_37753, PHKL_39133 PHKL_29706, PHKL_30033, PHKL_30587, PHKL_31993, PHKL_33328, PHKL_33336, PHKL_34310, PHKL_35281, PHKL_36948 PHKL_27294, PHKL_27317, PHKL_29707, PHKL_30032, PHKL_30216, PHKL_32061, PHKL_34309, PHKL_35879, PHKL_36035, PHKL_40455 None. PHKL_36763 PHKL_38299, PHKL_38430 PHNE_24035, PHNE_24910, PHNE_25625, PHNE_25627, PHNE_26388, PHNE_27218, PHNE_28103, PHNE_28568, PHNE_28983, PHNE_29211, PHNE_29303, PHNE_29783, PHNE_29883, PHNE_30378, PHNE_30380, PHNE_30661, PHNE_31097, PHNE_31929, PHNE_32477, PHNE_32811, PHNE_33315, PHNE_33498, PHNE_33971, PHNE_34293, PHNE_34662, PHNE_34938, PHNE_35418, PHNE_35871, PHNE_36168, PHNE_37110, PHNE_37568, PHNE_39167, PHNE_41023 PHNE_26728, PHNE_27703, Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 62

63 Required patches Cumulative STREAMS Patch PHNE_29887 s700_ cumulative ARPA Transport patch PHSS_24932 s700_ Japanese TrueType font patch PHSS_24934 s700_ Korean TrueType font patch PHSS_24936 s700_ Chinese- S TrueType font patch for PHSS_25449 s700_ X/Motif Runtime OCT2001 Periodic Patch PHSS_25881 s700_ X/Motif Runtime JAN2002 Periodic Patch PHSS_30049 s700_ ld(1) and linker tools cumulative patch PHSS_35385 s700_ ld(1) and linker tools cumulative patch Java execution environment Version 6.0 Succeeding patches PHNE_28476, PHNE_29825, PHNE_30367, PHNE_31091, PHNE_33313, PHNE_33729, PHNE_34131, PHNE_34777, PHNE_35453, PHNE_36576, PHNE_37259 PHNE_31247, PHNE_33159, PHNE_33628, PHNE_34135, PHNE_34672, PHNE_35183, PHNE_35351, PHNE_36125, PHNE_37671, PHNE_37898, PHNE_38678, PHNE_39386, PHNE_42029 PHSS_26971 PHSS_26973 PHSS_26975 PHSS_25881, PHSS_27234, PHSS_27425, PHSS_28370, PHSS_28875, PHSS_29371, PHSS_30262, PHSS_30787, PHSS_31000, PHSS_33130, PHSS_35711, PHSS_37028 PHSS_27234, PHSS_27425, PHSS_28370, PHSS_28875, PHSS_29371, PHSS_30262, PHSS_30787, PHSS_31000, PHSS_33130, PHSS_35711, PHSS_37028 PHSS_30966, PHSS_30968, PHSS_30970, PHSS_32864, PHSS_33033, PHSS_33035, PHSS_33037, PHSS_35379, PHSS_35381, PHSS_35383, PHSS_35385, PHSS_37516, PHSS_37517, PHSS_38154, PHSS_39077, PHSS_39749, PHSS_40549, PHSS_41214, PHSS_41713, PHSS_42253 PHSS_37516, PHSS_37517, PHSS_38154, PHSS_39077, PHSS_39749, PHSS_40549, PHSS_41214, PHSS_41713, PHSS_42253 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 63

64 Note: The architecture is PA-RISC (32 or 64 bit). Depending on the OS release date, required patches might have been applied at the time of delivery. For details on the latest information, see the HP web site. Table 51 Required patches and succeeding patches for HP-UX 11i v2 Architecture Required patches Succeeding patches PA-RISC (64bit) (Version 5.0 of the Java execution environment) PA-RISC (64bit) (Version 6.0 of the Java execution environment) (Version of the Java execution environment) PHSS_33349 s700_ linker + fdp cumulative patch PHSS_37201s700_ linker + fdp cumulative patch PHSS_33349 s700_ linker + fdp cumulative patch PHCO_30476 s700_ Pthread library patch PHKL_30192 s700_ Eliminate race at MxN kernel thread creation PHSS_30015 s700_ Aries cumulative patch PHSS_34040, PHSS_34353, PHSS_34440, PHSS_34858, PHSS_34860, PHSS_35979, PHSS_36336, PHSS_36342, PHSS_37201, PHSS_37492, PHSS_37947, PHSS_39093, PHSS_38134, PHSS_39821, PHSS_40537, PHSS_41178, PHSS_41491, PHSS_42043 PHSS_37492, PHSS_37947, PHSS_38134, PHSS_39093, PHSS_39821, PHSS_40537, PHSS_41178, PHSS_41491, PHSS_42043 PHSS_34040, PHSS_34353, PHSS_34440, PHSS_34858, PHSS_34860, PHSS_35979, PHSS_36336, PHSS_36342, PHSS_37201, PHSS_37492, PHSS_37947, PHSS_38134, PHSS_39093, PHSS_40537, PHSS_41178, PHSS_41491, PHSS_42043 PHCO_30543, PHCO_31553, PHCO_32489, PHCO_33675, PHCO_34718, PHCO_34944, PHCO_35997, PHCO_36323, PHCO_37543, PHCO_37940, PHCO_38955, PHCO_39699, PHCO_41946 PHKL_31500 PHSS_30237, PHSS_30674, PHSS_30779, PHSS_31816, PHSS_32213, PHSS_32502, PHSS_34201, PHSS_35045, PHSS_35528, PHSS_36519, PHSS_37552, PHSS_38526, PHSS_39293, PHSS_39897, PHSS_41098, PHSS_41422 (Version 5.0 of the Java execution environment) PHCO_30476 s700_ Pthread library patch PHCO_30543, PHCO_31553, PHCO_32489, PHCO_33675, PHCO_34718, PHCO_34944, PHCO_35997, PHCO_36323, PHCO_37543, PHCO_37940, PHCO_38955, PHCO_39699, PHCO_41946 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 64

65 Architecture Required patches Succeeding patches (Version 6.0 of the Java execution environment) PHKL_30192 s700_ Eliminate race at MxN kernel thread creation PHKL_35029 s700_ ksleep cumulative patch PHSS_30015 s700_ Aries cumulative patch PHSS_33349 s700_ linker + fdp cumulative patch PHSS_33350 s700_ ac++ Runtime PHSS_34043 s700_ Integrity Unwind Library PHSS_25045 s700_ solves problem emulating floating point patch PHKL_36667 s700_ mmap patch PHSS_30015 s700_ Aries cumulative patch PHKL_30192 s700_ Eliminate race at MxN kernel thread creation PHCO_30476 s700_ Pthread library patch PHKL_31500 PHKL_36826, PHKL_37121, PHKL_41057 PHSS_30237, PHSS_30674, PHSS_30779, PHSS_31816, PHSS_32213, PHSS_32502, PHSS_34201, PHSS_35045, PHSS_35528, PHSS_36519, PHSS_37552, PHSS_38526, PHSS_39293, PHSS_39897, PHSS_41098, PHSS_41422 PHSS_34040, PHSS_34353, PHSS_34440, PHSS_34858, PHSS_34860, PHSS_35979, PHSS_36336, PHSS_36342, PHSS_37201, PHSS_37492, PHSS_37947, PHSS_38134, PHSS_39093, PHSS_40537, PHSS_41178, PHSS_41491, PHSS_42043 PHSS_34041, PHSS_34441, PHSS_35055, PHSS_35978, PHSS_36343, PHSS_37500, PHSS_38140, PHSS_40543, PHSS_41184 PHSS_34854, PHSS_34859, PHSS_36345, PHSS_37039, PHSS_37498, PHSS_37953, PHSS_38138, PHSS_39101, PHSS_40541, PHSS_41182, PHSS_41495 PHSS_35528, PHSS_36519, PHSS_37552, PHSS_38526, PHSS_39293, PHSS_39897, PHSS_41098, PHSS_41422 PHKL_37653, PHKL_39436, PHKL_39901, PHKL_40094, PHKL_41002, PHKL_41807 PHSS_30237, PHSS_30674, PHSS_30779, PHSS_31816, PHSS_32213, PHSS_32502, PHSS_34201, PHSS_35045, PHSS_35528, PHSS_36519, PHSS_37552, PHSS_38526, PHSS_39293, PHSS_39897, PHSS_41098, PHSS_41422 PHKL_31500 PHCO_30543, PHCO_31553, PHCO_32489, PHCO_33675, PHCO_34718, PHCO_34944, PHCO_35997, PHCO_36323, PHCO_37543, PHCO_37940, PHCO_38955, PHCO_39699, PHCO_41946 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 65

66 Architecture Required patches Succeeding patches PHSS_33349 s700_ linker + fdp cumulative patch PHSS_33350 s700_ ac++ Runtime PHSS_34043 s700_ Integrity Unwind Library PHKL_35029 s700_ ksleep cumulative patch PHSS_35045 s700_ Aries cumulative patch PHKL_36667 s700_ mmap(2),mlock[all](2),madvise(2),msync(2) PHSS_34040, PHSS_34353, PHSS_34440, PHSS_34858, PHSS_34860, PHSS_35979, PHSS_36336, PHSS_36342, PHSS_37201, PHSS_37492, PHSS_37947, PHSS_38134, PHSS_39093, PHSS_40537, PHSS_41178, PHSS_41491, PHSS_42043 PHSS_34041, PHSS_34441, PHSS_35055, PHSS_35978, PHSS_36343, PHSS_37500, PHSS_38140, PHSS_40543, PHSS_41184 PHSS_34854, PHSS_34859, PHSS_36345, PHSS_37039, PHSS_37498, PHSS_37953, PHSS_38138, PHSS_39101, PHSS_40541, PHSS_41182, PHSS_41495 PHKL_36826, PHKL_37121, PHKL_41057 PHSS_35528, PHSS_36519, PHSS_37552, PHSS_38526, PHSS_39293, PHSS_39897, PHSS_41098, PHSS_41422 PHKL_37653, PHKL_39436, PHKL_39901, PHKL_40094, PHKL_41002, PHKL_41807 Note: Depending on the OS release date, required patches might have been applied at the time of delivery. For details on the latest information, see the HP web site. Table 52 Required patches and succeeding patches for HP-UX 11i v3 Architecture Required patches Succeeding patches PA-RISC (64bit) (Version of the Java execution environment) PA-RISC (64bit) (Version 5.0 of the Java execution environment) PHKL_ scheduler cumulative patch PHKL_ scheduler cumulative patch PHKL_40207, PHKL_40941, PHKL_40963, PHKL_41481, PHKL_41981 PHKL_40207, PHKL_40941, PHKL_40963, PHKL_41481, PHKL_41981 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 66

67 Architecture Required patches Succeeding patches PA-RISC (64bit) (Version 6.0 of the Java execution environment) (Version of the Java execution environment) (Version 5.0 of the Java execution environment) (Version 6.0 of the Java execution environment) PHSS_ linker + fdp cumulative patch PHKL_ scheduler cumulative patch PHKL_ scheduler cumulative patch PHCO_ pthread library cumulative patch PHKL_ scheduler cumulative patch PHSS_ ac++ Runtime (IA: A.06.16, PA: A.03.76) PHCO_ pthread library cumulative patch PHSS_ Integrity Unwind Library PHSS_ ac++ Runtime (IA: A.06.16, PA: A.03.76) PHCO_ pthread library cumulative patch PHSS_ Integrity Unwind Library PHKL_ scheduler cumulative patch PHSS_37493, PHSS_37948, PHSS_37955, PHSS_38135, PHSS_39094, PHSS_39822, PHSS_40538, PHSS_41179, PHSS_41492, PHSS_42040 PHKL_40207, PHKL_40941, PHKL_40963, PHKL_41481, PHKL_41981 PHKL_40207, PHKL_40941, PHKL_40963, PHKL_41481, PHKL_41981 PHCO_38837, PHCO_39604, PHCO_40211, PHCO_41092, PHCO_41291, PHCO_41407, PHCO_42165, PHCO_42326 PHKL_40207, PHKL_40941, PHKL_40963, PHKL_41481, PHKL_41981 PHSS_38141, PHSS_40544, PHSS_41185 PHCO_38837, PHCO_39604, PHCO_40211, PHCO_41092, PHCO_41291, PHCO_41407, PHCO_42165, PHCO_42326 PHSS_39102, PHSS_40542, PHSS_41183, PHSS_41496 PHSS_38141, PHSS_40544, PHSS_41185 PHCO_38837, PHCO_39604, PHCO_40211, PHCO_41092, PHCO_41291, PHCO_41407, PHCO_42165, PHCO_42326 PHSS_39102, PHSS_40542, PHSS_41183, PHSS_41496 PHKL_40207, PHKL_40941, PHKL_40963, PHKL_41481, PHKL_41981 Note: Depending on the OS release date, required patches might have been applied at the time of delivery. For details on the latest information, see the HP web site. Prerequisite Java execution environments Conditions depend on the OSs where Device Manager agent is installed. For Windows or Linux Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 67

68 If the host OS is Windows or Linux, the bundled JRE in the product will be set to use after new installation. To use Oracle Sun JDK or Oracle Sun JRE, change the Java execution environment for Device Manager agent after the installation. The following is the prerequisite of Java execution environment for Device Manager agent. Table 53 Prerequisite Java execution environment for Device Manager agent (Windows or Linux) OS Bundled JRE 5.0 (1.5.0) Oracle Sun JDK 6.0 Update 22 (1.6.0_22) or later # 1 Oracle Sun JRE 6.0 Update 22 (1.6.0_22) or later # 1 Windows Server 2003 R2 () Windows Server 2003 R2 (x64) Windows Server 2008 () Windows Server 2008 (x64) Windows Server 2008() Windows Server 2008 R2 (x64) Windows Server 2008 R2 () Red Hat Enterprise Linux () Red Hat Enterprise Linux (x64) Red Hat Enterprise Linux () SUSE Linux Enterprise Server () SUSE Linux Enterprise Server (x64) SUSE Linux Enterprise Server () # 2 # 2 # 2 # 2 N N # 2 # 2 N N Legend: : Supported. N: Not supported. --: None Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 68

69 #1: #2: Use the program of installer type for Windows, or package type for Linux but not self-extract file. Use Java execution environment for 32 bit because Device Manager agent is 32 bit application. Note: If Dynamic Link Manager is installed in the host, use an execution environment of Java for 32 bit. For Solaris, AIX or HP-UX If the host OS is Solaris, AIX, or HP-UX, you need software that provides a Java execution environment on the host before installing the Device Manager agent. Download the software from your OS vendor site, and then install it. The following table shows the prerequisite Java execution environments for Device Manager agents. Table 54 Required Java execution environments (Solaris, AIX or HP- UX) OS Architecture Java Execution Environment Solaris SPARC (32 and 64 bit) For IPv4 environment operation: JDK 1.4.2_xx (xx is 15 or later) JDK 5.0 (Update 11 or later) JDK 6.0 (Update 17 or later) For IPv6 environment operation: JDK 5.0 (Update 11 or later) JDK 6.0 (Update 17 or later) AIX AMD64 32 bit 64 bit JDK 5.0 (Update 11 or later) JDK 6.0 (Update 17 or later) For IPv4 environment operation: JDK (Update 8 or later) JDK 5.0 (Update 5 or later) JDK 6.0 (Update 17 or later) For IPv6 environment operation: JDK 5.0 (Update 5 or later) JDK 6.0 (Update 17 or later) HP-UX PA-RISC (32 and 64 For IPv4 environment operation: Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 69

70 OS Architecture Java Execution Environment bit) JDK 1.4.2_xx (xx is 17 or later) RTE 1.4.2_xx (xx is 17 or later) JDK 5.0 (Update 11 or later) JRE 5.0 (Update 11 or later) JDK 6.0 (Update 17 or later) JRE 6.0 (Update 17 or later) For IPv6 environment operation: JDK 5.0 (Update 11 or later) JRE 5.0 (Update 11 or later) JDK 6.0 (Update 17 or later) Note: Use a package program instead of a self-expanding program. If multiple versions are installed, the Device Manager agent uses the latest version of the Java execution environment. Use the following commands to check the versions of the listed software products, which provide a Java execution environment. Table 55 Commands for checking the version of the software that provides a Java execution environment OS Software that provides a Java execution environment Command Solaris JDK pkginfo -li SUNWj3rt JDK 5.0 pkginfo -li SUNWj5rt JDK 6.0 pkginfo -li SUNWj6rt AIX JDK (32 bit) lslpp -l Java14.sdk JDK (64 bit) lslpp -l Java14_64.sdk JDK 5.0 (32 bit) lslpp -l Java5.sdk JDK 5.0 (64 bit) lslpp -l Java5_64.sdk JDK 6.0 (32 bit) lslpp -l Java6.sdk JDK 6.0 (64 bit) lslpp -l Java6_64.sdk HP-UX JDK swlist T1456AA RTE swlist T1457AA JDK 5.0 swlist Java15JDK JRE 5.0 swlist Java15JRE JDK 6.0 swlist Java60JDK JRE 6.0 swlist Java60JRE Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 70

71 Caution: When updating the software that provides a Java execution environment (after installing the Device Manager agent), temporarily stop the Device Manager agent service before proceeding with any updates. Also, when changing the installation path of the software that provides a Java execution environment, you must modify the server.agent.jre.location setting in the server.properties file. Supported virtualization software The Device Manager agent can also run on the guest OSs or the VIO clients of the virtualization software in the following table. Note that the Device Manager agent should be installed on either a virtualization server (host OS) or the virtual machines (guest OS or VIO client). Table 56 Supported Virtualization Software Guest OS or VIO client Version Architecture Virtualization software Windows Server 2003 R2 No SP x64 Edition (EM64T and AMD64) VMware ESX 3.x VMware ESX 4.x VMware ESXi 3.x VMware ESXi 4.x VMware ESXi 5.0 SP2 VMware ESX 3.x x64 Edition (EM64T and AMD64) VMware ESX 4.x VMware ESXi 3.x VMware ESXi 4.x VMware ESXi 5.0 Windows Server 2008 (Hyper-V) Windows Server 2008 R2 (Hyper-V2) Windows Server 2008 No SP SP1 SP2 x64 Edition (EM64T and AMD64) VMware ESX 3.x VMware ESX 4.x VMware ESXi 3.x VMware ESXi 4.x VMware ESXi 5.0 Windows Server 2008 (Hyper-V) Windows Server 2008 R2 (Hyper-V2) Windows Server 2008 R2 No SP SP1 x64 Edition (EM64T and AMD64) VMware ESX 3.x VMware ESX 4.x VMware ESXi 3.x Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 71

72 Guest OS or VIO client Version Architecture Virtualization software VMware ESXi 4.x VMware ESXi 5.0 Windows Server 2008 (Hyper-V) Windows Server 2008 R2 (Hyper-V2) Solaris 10 SPARC (32 and 64 bit) Solaris 10 (SPARC) (Logical Domains 1.2 or 1.3) AIX bit 64 bit VIO # bit bit Not applicable #: HBAs that support NPIV are required. Use HBAs that support NPIV to assign LUs to the VIO client. When running the Device Manager agent on a guest OS or a VIO client, be sure to take into account the number of LUs managed by the virtual machines in order to allocate a sufficient amount of memory to the guest OS or the VIO client. As for the Device Manager agent configuration, follow the configuration recommendations. Caution: When you use Logical Domains, if you export a physical disk of the service domain as a virtual disk of the guest domain, specify the full disk. If you specify a single slice disk instead, information about the virtual disk cannot be acquired correctly. Supported file systems The following table lists the file systems supported by the Device Manager agent. Table 57 Supported file systems OS File system Windows NTFS FAT FAT32 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 72

73 OS File system Solaris UFS Veritas File System AIX Red Hat Enterprise Linux SUSE Linux Enterprise Server HP-UX JFS ext2 ext3 ext2 ext3 ext4 Veritas File System (JFS # ) HFS #: This includes HP OnlineJFS and HP JFS, which are recognized as Veritas File System on a host. Supported volume managers The following table lists volume managers supported by the Device Manager agent. Note that the table only lists OSs that support volume managers. Table 58 Supported volume managers OS Version Architecture Volume manager Windows Server 2003 No SP Basic Dynamic x64 Edition (EM64T and AMD64) SP1 Basic Dynamic VERITAS Volume Manager 4.3 Basic Dynamic SP2 Basic Dynamic x64 Edition (EM64T and AMD64) Windows Server 2003 R2 No SP SP2 x64 Edition (EM64T and AMD64) Basic Dynamic Windows Server 2008 No SP SP1 Basic Dynamic Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 73

74 OS Version Architecture Volume manager SP2 x64 Edition (EM64T and AMD64) Windows Server 2008 R2 No SP x64 Edition (EM64T and AMD64) Basic Dynamic SP1 x64 Edition (EM64T and AMD64) Basic Dynamic Solaris 8 SPARC (32 or 64 bit) SDS SPARC (32 or 64 bit) SVM SPARC (32 or 64 bit) SVM 1.0 x64 Edition (AMD64) SVM 1.0 VERITAS Volume Manager 3.2 VERITAS Volume Manager 3.5 VERITAS Volume Manager 4.0 VERITAS Volume Manager 3.5 VERITAS Volume Manager 4.0 VERITAS Volume Manager 4.1 Veritas Volume Manager 5.0 VERITAS Volume Manager 4.1 MP2 #1 Veritas Volume Manager 5.0 #1 Veritas Volume Manager 5.0 MP1 #1 VERITAS Volume Manager 4.1 VERITAS Volume Manager 4.1 MP2 Veritas Volume Manager 5.0 MP1 AIX bit 64 bit LVM bit LVM bit LVM Red Hat Enterprise Linux Linux AS/ES 4 LVM2 x64 Edition (EM64T) Linux 5 LVM2 x64 Edition (EM64T) Linux 6 LVM2 x64 Edition (EM64T) SUSE Linux 9 LVM2 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 74

75 Enterprise Server OS Version Architecture Volume manager 10 x64 Edition (EM64T) LVM2 11 x64 Edition (EM64T) LVM2 HP-UX 11i v1 PA-RISC (32 or 64 bit) LVM VERITAS Volume Manager i v2 (for versions earlier than 12/2005) 11i v2 (for versions later than or equal to 12/2005) 11i v3 PA-RISC (64 bit) PA-RISC (64 bit) PA-RISC (64 bit) LVM VERITAS Volume Manager 3.5 VERITAS Volume Manager 4.1 LVM VERITAS Volume Manager 3.5 VERITAS Volume Manager 4.1 LVM LVM2 #2 LVM2.1 #2 VERITAS Volume Manager 4.1 #1: #2: Logical domains cannot be used. This version of Device Manager agent supports volume groups whose version is up to 2.1. Therefore, even if an LVM that supports volume groups whose version is higher than 2.1 is installed on a host, the file systems and device files will be created as volume groups of version 2.1. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 75

76 Caution: Even if the Device Manager agent is installed on the host, the GUI LU usage rate will not be displayed in the following cases: Windows is the OS on the host using the LUs, and LUs or LU partitions are subject to dynamic disk management. Solaris is the OS on the host using the LUs, and LUs are managed by SDS, SVM, or Veritas Volume Manager. The OS on the host using the LUs is AIX. Linux is the OS on the host using the LUs, and LUs satisfy one of the following conditions: The LUs are managed by LVM2. The LUs are partitioned, and some of the LU partitions are managed by a volume manager. The OS on the host using the LUs is HP-UX, and the LUs are managed by LVM. Supported path management software Path management software is required when path redundancy is used between host ports and storage system ports to increase system reliability and availability. The following table lists the path management software supported by the Device Manager agent. Note that the table only lists OSs that support path management software. Table 59 Supported path management software OS Version Architecture Path management software Windows Server 2003 No SP Dynamic Link Manager to x64 Edition (EM64T and AMD64) Dynamic Link Manager 5.7 to SP1 Dynamic Link Manager 5.4 to SP2 Dynamic Link Manager 5.9 to x64 Edition (EM64T and AMD64) Windows Server 2003 R2 No SP x64 Edition (EM64T and AMD64) Dynamic Link Manager 5.8 to SP2 Dynamic Link Manager 5.9 to x64 Edition (EM64T and AMD64) Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 76

77 OS Version Architecture Path management software Windows Server 2008 No SP SP1 Dynamic Link Manager to x64 Edition (EM64T and AMD64) SP2 Dynamic Link Manager to x64 Edition (EM64T and AMD64) Windows Server 2008 R2 No SP x64 Edition (EM64T and AMD64) Dynamic Link Manager to SP1 x64 Edition (EM64T and AMD64) Dynamic Link Manager to Solaris 8 SPARC (32 and 64 bit) Dynamic Link Manager Dynamic Link Manager Dynamic Link Manager to 9 SPARC (32 and 64 bit) VERITAS Volume Manager 4.0 (Dynamic Multi-Pathing) VERITAS Volume Manager 4.1 (Dynamic Multi-Pathing) Dynamic Link Manager to Sun StorEdge Traffic Manager SPARC (32 and 64 bit) Dynamic Link Manager to Sun StorEdge Traffic Manager AIX bit x64 Edition (AMD64) 64 bit Sun StorEdge Traffic Manager Dynamic Link Manager to MPIO bit Dynamic Link Manager to bit Dynamic Link Manager HP-UX 11i v1 PA-RISC (32bit) PV-link PA-RISC (64bit) PV-link Dynamic Link Manager to i v2 PA-RISC (64bit) PV-link Dynamic Link Manager to i v3 PA-RISC (64bit) PV-link Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 77

78 OS Version Architecture Path management software MPIO Red Hat Enterprise Linux Linux AS/ES 4 Update 1 Dynamic Link Manager to x64 Edition (EM64T) Dynamic Link Manager to Linux AS/ES 4 Update 3 x64 Edition (EM64T) Dynamic Link Manager to Linux AS/ES 4 Update 4 x64 Edition (EM64T) Dynamic Link Manager to Linux AS/ES 4.5 Dynamic Link Manager to x64 Edition (EM64T) Linux AS/ES 4.6 Dynamic Link Manager to x64 Edition (EM64T) Linux AS/ES 4.7 Dynamic Link Manager to x64 Edition (EM64T) Linux AS/ES 4.8 Dynamic Link Manager to x64 Edition (EM64T) Linux AS/ES 4.9 Dynamic Link Manager to x64 Edition (EM64T) Linux 5.0 Dynamic Link Manager to x64 Edition (EM64T) Linux 5.1 Dynamic Link Manager to x64 Edition (EM64T) Linux 5.2 Dynamic Link Manager to x64 Edition (EM64T) Linux 5.3 Dynamic Link Manager to x64 Edition (EM64T) Linux 5.4 Dynamic Link Manager to Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 78

79 OS Version Architecture Path management software x64 Edition (EM64T) Linux 5.5 Linux 5.6 Linux 6.0 Linux 6.1 x64 Edition (EM64T) x64 Edition (EM64T) x64 Edition (EM64T) x64 Edition (EM64T) Dynamic Link Manager to Dynamic Link Manager to Dynamic Link Manager to Dynamic Link Manager to SUSE Linux Enterprise Server 9 (SP1, SP2) Dynamic Link Manager to (SP3) Dynamic Link Manager to (SP4) Dynamic Link Manager to 10 (No SP) Dynamic Link Manager to 10 (SP1) Dynamic Link Manager to 10 (SP2) Dynamic Link Manager to 10 (SP3) Dynamic Link Manager to 10 (SP4) Dynamic Link Manager to 11 (No SP) Dynamic Link Manager to 11 (SP1) x64 Edition (EM64T and AMD64) Dynamic Link Manager to Supported cluster software When cluster software is installed, hosts on which Device Manager agent is also installed can be clustered in an Active-Standby configuration or Active-Active configuration. The Device Manager agent runs in cluster environments configured with the cluster software listed in the table below. Note that the table only lists OSs that support cluster software. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 79

80 Note: Because the Device Manager agent is not compatible with the logical host, the Device Manager agent cannot be registered in cluster resources. The Device Manager agent is activated on the physical hosts that make up the cluster, and collects the data for those hosts. For details about setting up the cluster software, see the manual for each cluster software product. Table 60 Supported cluster software OS Version Architecture Cluster software Windows Server 2003 No SP Microsoft Cluster Service VERITAS Cluster Server 4.1 x64 Edition (EM64T and AMD64) Microsoft Cluster Service Microsoft Cluster Service SP1 Microsoft Cluster Service VERITAS Cluster Server 4.1 VERITAS Cluster Server 4.3 Microsoft Cluster Service SP2 Microsoft Cluster Service Microsoft Cluster Service x64 Edition (EM64T and AMD64) Microsoft Cluster Service Windows Server 2003 R2 No SP SP2 x64 Edition (EM64T and AMD64) Microsoft Cluster Service Microsoft Cluster Service Windows Server 2008 No SP SP1 SP2 x64 Edition (EM64T and AMD64) Microsoft Failover Cluster Microsoft Failover Cluster Microsoft Failover Cluster Windows Server 2008 R2 No SP SP1 x64 Edition (EM64T and AMD64) Microsoft Failover Cluster Solaris 8 SPARC (32 and 64 bit) Sun Cluster 3.0 Sun Cluster 3.1 VERITAS Cluster Server 1.3 VERITAS Cluster Server 2.0 VERITAS Cluster Server 3.5 #1, #2 PRIMECLUSTER SPARC (32 and 64 bit) Sun Cluster 3.1 VERITAS Cluster Server 3.5 VERITAS Cluster Server 4.0 VERITAS Cluster Server 4.1 Cluster Perfect 4.5 R2 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 80

81 OS Version Architecture Cluster software #1, #2 PRIMECLUSTER SPARC (32 and 64 bit) Sun Cluster 3.1 VERITAS Cluster Server 4.1 VERITAS Cluster Server 4.1 MP2 Veritas Cluster Server 5.0 Veritas Cluster Server 5.0 MP1 #1, #2 PRIMECLUSTER #1, #2 PRIMECLUSTER 4.2 x64 Edition (AMD64) VERITAS Cluster Server 4.1 MP2 AIX bit HACMP 5.2 Veritas Cluster Server 5.0 MP1 PowerHA 5.5 PowerHA bit HACMP 5.2 HACMP 5.3 PowerHA 5.5 PowerHA bit HACMP PowerHA 5.5 PowerHA bit Not applicable Red Hat Enterprise Linux Linux AS/ES 4 Update 1 Linux AS/ES 4 Update 3 Linux AS/ES 4 Update 4 Linux AS/ES 4.5 VERITAS Cluster Server 4.1 HA Monitor /D HA Monitor /A PRIMECLUSTER 4.2 #1 PRIMECLUSTER 4.2 #1 Linux AS/ES 5.4 x64 Edition (EM64T and AMD64) HA Monitor or later Linux AS/ES 5.5 ClusterPro 2.1 HP-UX 11i v1 PA-RISC (32 bit) Serviceguard PA-RISC (64 bit) MC/Service Guard Serviceguard i v2 PA-RISC (64 bit) Serviceguard Serviceguard i v3 PA-RISC (64 bit) Serviceguard Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 81

82 Device Manager GUI requirements OS Version Architecture Cluster software Serviceguard Serviceguard #1: File systems created with GDS are not supported. #2: Dynamic Link Manager must be already installed. Device Manager GUI requirements Device Manager requirements for GUI operations Table 61 lists the supported OSs, Web browsers, and Java Runtime Environment (JRE) versions for using this version of Device Manager GUI. Table 61 also indicates whether linkages with management tools are supported, and whether IPv6 connections to the Device Manager server using GUI are supported. Adobe Flash Player 10.1 to 10.3 is required for all browsers. Table 61 Environment for using GUI OS Web browser JRE version #1#2 Linkage with management tools IPv6 connections SN SNM2 SNM DAMP VSP USP V/VM USP 9900V Windows XP ( version) SP2 Internet Explorer 7.0 # _xx (xx is 04 or later) 5.0 N N N N N N N N (Update 7 or later) 6.0 N N N N Internet Explorer _xx (xx is 04 or later) 5.0 (Update 7 or later) N N N N N N N N 6.0 N N N N Windows XP Internet 1.4.2_xx N N N N N N N Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 82

83 Device Manager GUI requirements OS Web browser JRE version #1#2 Linkage with management tools IPv6 connections SN SNM2 SNM DAMP VSP USP V/VM USP 9900V ( version) SP3 Explorer 7.0 (xx is 04 or later) 5.0 N N N N N N (Update 7 or later) 6.0 N N N N N Internet Explorer _xx (xx is 04 or later) 5.0 (Update 7 or later) N N N N N N N N N N N N N N N 6.0 N N N N N N Windows Server 2003 R2 ( version) SP2 Internet Explorer 6.0 # _xx (xx is 12 or later) 5.0 N N N N N N N N N N N (Update 7 or later) 6.0 N N N N N Internet Explorer 7.0 # _xx (xx is 12 or later) 5.0 (Update 7 or later) N N N N N N N N N N Windows Vista ( version) no SP Windows Vista (x64 version) no SP Windows Vista ( version) SP1 Windows Vista (x64 version) Internet Explorer 7.0 Internet Explorer 8.0 Internet Explorer 7.0 Internet Explorer 8.0 Internet Explorer 7.0 Internet Explorer 8.0 Internet Explorer 7.0 # N N N N N N 6.0 N N N 6.0 N N N N N N N 6.0 N N N N 6.0 N N N N N N N 6.0 N N N N N N 6.0 N N N N N N N 6.0 N N N N N N N Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 83

84 Device Manager GUI requirements OS Web browser JRE version #1#2 Linkage with management tools IPv6 connections SN SNM2 SNM DAMP VSP USP V/VM USP 9900V SP1 Windows Vista ( version) SP2 Internet Explorer 8.0 #10 Internet Explorer 7.0 Internet Explorer N N N N N N N 6.0 N N N N N N N 6.0 N N N N N N N Internet Explorer 9.0 #9 6.0(Update 25 or later) N N N N N N N Windows Vista (x64 version) SP2 Internet Explorer 7.0 #10 Internet Explorer 8.0 # N N N N N N N 6.0 N N N N N N N Internet Explorer 9.0 #9#10 6.0(Update 25 or later) N N N N N N N Windows 7 ( version or x64 version) No SP SP1 Windows Server 2008 #3 ( version) No SP SP1 Windows Server 2008 #3 (x64 version) No SP SP1 Windows Server 2008 #3 ( Internet Explorer 8.0 Internet Explorer 9.0 #9 Internet Explorer 7.0 Internet Explorer 8.0 Internet Explorer 7.0 #10 Internet Explorer 8.0 #10 Internet Explorer 7.0 Internet Explorer N N N N N N 6.0(Update 25 or later) N N N N N N N 6.0 N N N N N N 6.0 N N N N N N N 6.0 N N N N N N N 6.0 N N N N N N N 6.0 N N N N N N 6.0 N N N N N N N Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 84

85 Device Manager GUI requirements OS Web browser JRE version #1#2 Linkage with management tools IPv6 connections SN SNM2 SNM DAMP VSP USP V/VM USP 9900V version) SP2 Internet Explorer 9.0 #9 6.0(Update 25 or later) N N N N N N N Windows Server 2008 #3 (x64 version) SP2 Windows Server 2008 R2 #3 (x64 version) no SP SP1 Internet Explorer 7.0 #10 Internet Explorer 8.0 #10 Internet Explorer 9.0 #9#10 Internet Explorer 8.0 #10 Internet Explorer 9.0 #9# N N N N N 6.0 N N N N N N N 6.0(Update 25 or later) N N N N N N N 6.0 N N N N 6.0(Update 25 or later) N N N N N N N Solaris 10 SPARC (32bit version or 64bit version) Firefox 3.6.x # _xx (xx is 12 or later) 5.0 (Update 7 or later) N N N N N N N N N N N N N N N N 6.0 N N N N N N N Red Hat Enterprise Linux 5.2 ( version) Firefox 3.6.x 6.0 (1.6.0_10- b33 or later) N N N N N N N Red Hat Enterprise Linux AP 5.2 ( version) Firefox 3.6.x 6.0 (1.6.0_10- b33 or later) N N N N N N N Red Hat Enterprise Linux 5.3 ( version) Firefox 3.6.x 6.0 (1.6.0_10- b33 or later) N N N N N N N Red Hat Enterprise Linux AP 5.3 ( version) Firefox 3.6.x 6.0 (1.6.0_10- b33 or later) N N N N N N N Red Hat Firefox 6.0 N N N N N N N Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 85

86 Device Manager GUI requirements OS Web browser JRE version #1#2 Linkage with management tools IPv6 connections SN SNM2 SNM DAMP VSP USP V/VM USP 9900V Enterprise Linux 5.4 ( version) 3.6.x (1.6.0_10- b33 or later) Red Hat Enterprise Linux AP 5.4 ( version) Firefox 3.6.x 6.0 (1.6.0_10- b33 or later) N N N N N N N Red Hat Enterprise Linux 5.5 ( version) Firefox 3.6.x 6.0 (1.6.0_10- b33 or later) N N N N N N N Red Hat Enterprise Linux AP 5.5 ( version) Firefox 3.6.x 6.0 (1.6.0_10- b33 or later) N N N N N N N Red Hat Enterprise Linux 5.6 ( version) Firefox 3.6.x 6.0 (1.6.0_10- b33 or later) N N N N N N N Red Hat Enterprise Linux AP 5.6 ( version) Firefox 3.6.x 6.0 (1.6.0_10- b33 or later) N N N N N N N SUSE Linux Enterprise Server 11 ( version) no SP SP1 Firefox 3.6.x Firefox 4.0.x 6.0 N N N N N N N 6.0(Update 25 or later) N N N N N N N Legend: SN: Storage Navigator SNM: Storage Navigator Modular SNM2: Storage Navigator Modular 2 USP: Hitachi USP 9900V: Lightning 9900V : Linkage with the management tool is supported. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 86

87 Device Manager GUI requirements N: Linkage with the management tool is not supported. #1: When Java Runtime Environment (JRE) is installed, Java Web Start (JWS) of the same version as JRE is automatically installed. For xx, we recommend that you use the latest version. #2: To link Device Manager with a management tool, you need to use a JRE that is supported by the management tool. For details on the JRE versions required to launch management tools, see the manual for the management tools. For details on how to install JRE, see section 3.3. For details on how to set up JWS when different JRE versions have been installed, see section #3: Server Core is not supported. #4: This management tool is supported in 32-bit OSs only. #5: Solaris 10 (x64 edition) is supported only when the Sun Fire x64 Servers hardware is used. #6: The following is the restrictions when Device Manager server security is enabled: - If the default signature algorithm, SHA256withRSA, is specified when a keypair is created, this browser cannot be used. - To use this browser, apply Windows XP Service Pack 3. #7: The following is the restrictions when Device Manager server security is enabled: - If the default signature algorithm, SHA256withRSA, is specified when a keypair is created, this browser cannot be used. - To use this browser, apply Microsoft Knowledge Base article #8: Supported in 32-bit Browser only. #9: Launching Protection Manager is not supported in Internet Explorer 9.0. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 87

88 Device Manager CLI requirements #10: To launch Element Manager other than VSP by using a 32-bit browser, install 32-bit java plug-in, and then set the value in the storage system manual to 32-bit java plug-in. If an error message such as an out-of-memory error is displayed and Element Manager cannot be launched, check the settings of the 32-bit java plug-in. This applies to the following storage systems: - USP V - AMS SMS - AMS/WMS V Note: For best results, when using the Hitachi Command Suite GUI, make sure that the size of the page display area of the Web browser is at least 800 pixels wide and 600 pixels tall. The minimum supported monitor resolution is XGA (1024 x 768). Device Manager CLI requirements Platforms for Device Manager CLI and the Java Runtime Environment Table 62 lists platforms on which Device Manager CLI runs and the requisite Java runtime environments. In addition, this table also lists the support status of Device Manager CLI in IPv6 environments. The following symbols are used in the table: : Device Manager CLI is supported in IPv6 environments. N: Device Manager CLI is not supported in IPv6 environments. Table 62 Platform, Java Runtime Environment, and IPv6 Environment support for Device Manager CLI OS OS version Java Runtime Environment IPv6 Environmen t support Windows XP () Windows XP Professional SP2 JRE version 1.4.1_xx (xx is 07 or later) #1 JRE version 1.4.2_xx (xx is 04 or later) #1 JRE version 5.0_xx (xx is 03 or later) #4 JRE version 5.0 (Update 7 or later) JRE version 6.0 N N Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 88

89 Device Manager CLI requirements OS OS version Java Runtime Environment IPv6 Environmen t support Windows XP Professional SP3 JRE version 1.4.2_xx (xx is 04 or later) #1 JRE version 5.0 (Update 7 or later) JRE version 6.0 N Windows Server 2003 R2 () Windows Server 2003 R2, Standard Edition SP2 JRE version 1.4.2_xx (xx is 04 or later) #1 N Windows Server 2003 R2, Enterprise Edition SP2 Windows Server 2003 R2, Datacenter Edition SP2 JRE version 5.0_xx (xx is 03 or later) #4 JRE version 5.0 (Update 7 or later) JRE version 6.0 Windows Server 2003 R2 (x64) Windows Server 2003 R2, Standard x64 Edition SP2 JRE version 1.4.2_xx (xx is 12 or later) #1 N Windows Server 2003 R2, Enterprise x64 Edition SP2 Windows Server 2003 R2, Datacenter x64 Edition SP2 JRE version 5.0_xx (xx is 03 or later) #4 JRE version 5.0 (Update 7 or later) JRE version 6.0 Windows Vista (, x64) Windows Vista Business Windows Vista Business SP1 JRE version 6.0 Windows Vista Business SP2 Windows Vista Enterprise Windows Vista Enterprise SP1 Windows Vista Enterprise SP2 Windows Vista Ultimate Windows Vista Ultimate SP1 Windows Vista Ultimate SP2 Windows 7 (, x64) Windows 7 Enterprise Edition Windows 7 Enterprise Edition SP1 JRE version 6.0 Windows 7 Professional Edition Windows 7 Professional Edition SP1 Windows 7 Ultimate Edition Windows 7 Ultimate Edition SP1 Windows Server Windows Server 2008 Standard 2008 (, x64) #2 Windows Server 2008 Standard SP1 Windows Server 2008 Standard SP2 Windows Server 2008 Standard 32-bit Windows Server 2008 Standard 32-bit SP1 Windows Server 2008 Standard 32-bit SP2 Windows Server 2008 Standard without JRE version 6.0 Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 89

90 Device Manager CLI requirements OS OS version Java Runtime Environment IPv6 Environmen t support Hyper-V Windows Server 2008 Standard without Hyper-V SP1 Windows Server 2008 Standard without Hyper-V SP2 Windows Server 2008 Standard without Hyper-V 32-bit Windows Server 2008 Standard without Hyper-V 32-bit SP1 Windows Server 2008 Standard without Hyper-V 32-bit SP2 Windows Server 2008 Enterprise Windows Server 2008 Enterprise SP1 Windows Server 2008 Enterprise SP2 Windows Server 2008 Enterprise 32-bit Windows Server 2008 Enterprise 32-bit SP1 Windows Server 2008 Enterprise 32-bit SP2 Windows Server 2008 Enterprise without Hyper-V Windows Server 2008 Enterprise without Hyper-V SP1 Windows Server 2008 Enterprise without Hyper-V SP2 Windows Server 2008 Enterprise without Hyper-V 32-bit Windows Server 2008 Enterprise without Hyper-V 32-bit SP1 Windows Server 2008 Enterprise without Hyper-V 32-bit SP2 Windows Server 2008 Datacenter Windows Server 2008 Datacenter SP1 Windows Server 2008 Datacenter SP2 Windows Server 2008 Datacenter 32- bit Windows Server 2008 Datacenter 32- bit SP1 Windows Server 2008 Datacenter 32- bit SP2 Windows Server 2008 Datacenter without Hyper-V Windows Server 2008 Datacenter without Hyper-V SP1 Windows Server 2008 Datacenter without Hyper-V SP2 Windows Server 2008 Datacenter without Hyper-V 32-bit Windows Server 2008 Datacenter Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 90

91 Device Manager CLI requirements OS OS version Java Runtime Environment IPv6 Environmen t support without Hyper-V 32-bit SP1 Windows Server 2008 Datacenter without Hyper-V 32-bit SP2 Windows Server Windows Server 2008 R2 Standard 2008 R2 (x64) #2 Windows Server 2008 R2 Standard SP1 Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Enterprise SP1 Windows Server 2008 R2 Datacenter Windows Server 2008 R2 Datacenter SP1 JRE version 6.0 Solaris Solaris 9 (SPARC edition) JRE version 1.4.1_xx (xx is 07 or later) #1 JRE version 1.4.2_xx (xx is 04 or later) #1 JRE version 5.0_xx (xx is 03 or later) #4 JRE version 5.0 (Update 7 or later) JRE version 6.0 Solaris 10 (SPARC edition) JRE version 1.4.2_xx (xx is 12 or later) #1 JRE version 5.0_xx (xx is 03 or later) #4 JRE version 5.0 (Update 7 or later) JRE version 6.0 N N N Solaris 10 (x64 edition) #3 JRE version 5.0 (Update 7 or later) AIX AIX 5L Version 5.3 (POWER) JRE version N JRE version 5.0 (Update 7 or later) HP-UX HP-UX 11i v1 (PA-RISC) JRE version 1.4.2_xx (xx is 05 or later) #1 JRE version 5.0.xx (xx is 03 or later) #1 N N HP-UX 11i v2 () HP-UX 11i v2 (PA-RISC) HP-UX 11i v3 () HP-UX 11i v3 (PA-RISC) Linux () Red Hat Enterprise Linux 5.4 Red Hat Enterprise Linux 5.4 Advanced JRE version 1.4.2_xx (xx is 05 or later) #1 JRE version 5.0.xx (xx is 03 or later) #1 JRE version 5.0.xx (xx is 03 or later) #1 JRE version 6.0 (Update 4 or later) N Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 91

92 Device Manager CLI requirements OS OS version Java Runtime Environment IPv6 Environmen t support Platform Red Hat Enterprise Linux 5.5 Red Hat Enterprise Linux 5.5 Advanced Platform Red Hat Enterprise Linux 5.6 Red Hat Enterprise Linux 5.6 Advanced Platform SUSE Linux Enterprise Server 10 SP2 SUSE Linux Enterprise Server 10 SP3 SUSE Linux Enterprise Server 11 SUSE Linux Enterprise Server 11 SP1 Linux (x64) Red Hat Enterprise Linux 5.4 Red Hat Enterprise Linux 5.4 Advanced Platform Red Hat Enterprise Linux 5.5 Red Hat Enterprise Linux 5.5 Advanced Platform Red Hat Enterprise Linux 5.6 Red Hat Enterprise Linux 5.6 Advanced Platform SUSE Linux Enterprise Server 10 SP2 SUSE Linux Enterprise Server 10 SP3 SUSE Linux Enterprise Server 11 SUSE Linux Enterprise Server 11 SP1 JRE version 6.0 (Update 4 or later) JRE version 6.0 (Update 4 or later) JRE version 5.0 (Update 10 or later) JRE version 6.0 JRE version 6.0 (Update 4 or later) JRE version 6.0 (Update 4 or later) JRE version 6.0 (Update 4 or later) JRE version 5.0 (Update 10 or later) JRE version 6.0 N N #1 For xx, we recommend that the latest version be used. #2 Device Manager CLI does not support Hyper-V. #3 Solaris 10 (x64 edition) is supported only when the Sun Fire x64 Servers hardware is used. #4 JRE bundled in each product Note: When you use Windows Vista, execute Device Manager CLI from a command prompt initiated as an administrator. If you attempt to execute Device Manager CLI from a command prompt not initiated as an administrator, the log file and execution results may not be output to the specified output location. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 92

93 Tiered Storage Manager CLI requirements Note: If the system on which HP-UX operates uses a Dual-Core Intel Itanium 2 Processor for the CPU, use JRE version 1.4.2_xx (xx is 10 or later) or JRE version or later, which comes with HP-UX (released in June 2006 or September 2006) that supports the processor. Note: If you run Device Manager CLI using a time zone for the U.S. and Canada, set up the OS so that the OS will support the new Daylight Saving Time (DST) rules introduced in Set up the OS, according to the information provided by the OS vendor. Note: If you run Device Manager CLI using a time zone for the U.S. and Canada, use the JRE that supports the new Daylight Saving Time (DST) rules introduced in The JRE used in the Device Manager server version 5.7 or later supports the new DST. If you run Device Manager CLI by using the JRE used in the Device Manager server version 5.7 or later, you do not have to prepare another JRE. Note: To use this function, we recommend that you install JRE version 6.0. We do not recommend that you use JRE version 1.4.1, 1.4.2, or 5.0 because entered passwords are displayed on the screen in those versions. Note: To use Device Manager CLI with the encoded password, install JRE version or later on the management client. Tiered Storage Manager CLI requirements The following table lists the programs that are required to set up the CLI on a management client. Table 63 OS, JRE version, and IPv6 Environment support for CLI client OS OS product JRE version IPv6 #1 Environment support Windows XP #2 Microsoft Windows XP Professional Edition Operating System (SP2, SP3) (Build 06 or later) or 5.0 (Build 07 or later) #5 or 5.0 (Build 07 or later) or Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 93

94 Tiered Storage Manager CLI requirements OS OS product JRE version IPv6 #1 Environment support Windows Server 2003 R2 () #2 Microsoft Windows Server 2003 R2, Datacenter Edition (SP2) Microsoft Windows Server 2003 R2, Enterprise Edition (SP2) Microsoft Windows Server 2003 R2, Standard Edition (SP2) 5.0 (Build 07 or later) #5 or 5.0 (Build 07 or later) or 6.0 Windows Server 2003 R2 (x64) #2 Microsoft Windows Server 2003 R2, Datacenter Edition (SP2) Microsoft Windows Server 2003 R2, Enterprise Edition (SP2) Microsoft Windows Server 2003 R2, Standard Edition (SP2) 5.0 (Build 07 or later) #5 or 5.0 (Build 07 or later) or 6.0 Windows Vista () #2 Windows Vista (x64) #2 Windows 7 () Windows 7 (x64) Windows Server 2008 #2, #3, () #4 Microsoft Windows Vista Business Edition (No SP, SP1, SP2) Microsoft Windows Vista Enterprise Edition (No SP, SP1, SP2) Microsoft Windows Vista Ultimate Edition (No SP, SP1, SP2) Microsoft Windows Vista Business Edition (No SP, SP1, SP2) Microsoft Windows Vista Enterprise Edition (No SP, SP1, SP2) Microsoft Windows Vista Ultimate Edition (No SP, SP1, SP2) Microsoft Windows 7 Enterprise Edition (No SP, SP1) Microsoft Windows 7 Professional Edition (No SP, SP1) Microsoft Windows 7 Ultimate Edition (No SP, SP1) Microsoft Windows 7 Enterprise Edition (No SP, SP1) Microsoft Windows 7 Professional Edition (No SP, SP1) Microsoft Windows 7 Ultimate Edition (No SP, SP1) Microsoft Windows Server 2008 Datacenter 32-bit (No SP, SP1, SP2) Microsoft Windows Server 2008 Enterprise 32-bit (No SP, SP1, SP2) Microsoft Windows Server 2008 Standard 32-bit (No SP, SP1, SP2) Microsoft Windows Server 2008 Datacenter without Hyper-V 32-bit (No SP, SP1, SP2) Microsoft Windows Server 2008 Enterprise without Hyper-V 32-bit (No SP, SP1, SP2) Microsoft Windows Server 2008 Standard without Hyper-V 32-bit (No SP, SP1, SP2) Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 94

95 Tiered Storage Manager CLI requirements OS OS product JRE version IPv6 #1 Environment support Windows Server 2008 #2, #3, (x64) #4 Windows Server 2008 R2 (x64) #3, #4 Microsoft Windows Server 2008 Datacenter (No SP, SP1, SP2) Microsoft Windows Server 2008 Enterprise (No SP, SP1, SP2) Microsoft Windows Server 2008 Standard (No SP, SP1, SP2) Microsoft Windows Server 2008 Datacenter without Hyper-V (No SP, SP1, SP2) Microsoft Windows Server 2008 Enterprise without Hyper-V (No SP, SP1, SP2) Microsoft Windows Server 2008 Standard without Hyper-V (No SP, SP1, SP2) Microsoft Windows Server 2008 R2, Datacenter (No SP, SP1) Microsoft Windows Server 2008 R2, Enterprise (No SP, SP1) Microsoft Windows Server 2008 R2, Standard (No SP, SP1) Solaris Solaris 9 (SPARC) (Build 06 or later) 5.0 (Build 07 or later) #5 or 5.0 (Build 07 or later) or Solaris 10 (SPARC) (Build 06 or later) 5.0 (Build 07 or later) #5 5.0 (Build 07 or later) or Solaris 10 (x64) 5.0 (Build 07 or later) HP-UX HP-UX 11i v1 (PA-RISC) (Build 08 or later) 5.0 (Build 03 or later) HP-UX 11i v2 (PA-RISC) HP-UX 11i v2 () HP-UX 11i v3 (PA-RISC) HP-UX 11i v3 () (Build 08 or later) 5.0 (Build 03 or later) -- Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 95

96 Tiered Storage Manager CLI requirements OS OS product JRE version IPv6 #1 Environment support Linux Red Hat Enterprise Linux 5.4 () Red Hat Enterprise Linux 5.4 (x64) 6.0 (Build 4 or later) Red Hat Enterprise Linux 5.4 Advanced Platform () Red Hat Enterprise Linux 5.4 Advanced Platform (x64) Red Hat Enterprise Linux 5.5 () Red Hat Enterprise Linux 5.6 () 6.0 (Build 4 or later) -- Red Hat Enterprise Linux 5.5 (x64) Red Hat Enterprise Linux 5.6 (x64) Red Hat Enterprise Linux 5.5 Advanced Platform () Red Hat Enterprise Linux 5.6 Advanced Platform () Red Hat Enterprise Linux 5.5 Advanced Platform (x64) Red Hat Enterprise Linux 5.6 Advanced Platform (x64) SUSE Linux Enterprise Server 10 () (SP2, SP3) 5.0 (Build 10 or later) SUSE Linux Enterprise Server 10 (x64) (SP2, SP3) SUSE Linux Enterprise Server 11 () (No SP, SP1) SUSE Linux Enterprise Server 11 (x64) (No SP, SP1) 6.0 Legend: #1 #2 #3 #4 : An IPv6 environment is supported. --: An IPv6 environment is not supported. Both an IPv4 environment and IPv6 environment are required to run Tiered Storage Manager. The CLI also runs on guest OSs on VMware ESX version 3.x. The CLI does not support operations on Windows Server 2008 (Hyper-V) guest OSs. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 96

97 Requirements for the Plug-in for Virtualization Server Provisioning setup tool #5 Operation on Server Core is not supported. JRE bundled in each product Note: To use this function, we recommend that you install JRE version 6.0. We do not recommend that you use JRE version 1.4.1, 1.4.2, or 5.0 because entered passwords are displayed on the screen in those versions. Note: To use Device Manager CLI with the encoded password, install JRE version or later on the management client. Requirements for the Plug-in for Virtualization Server Provisioning setup tool The following table describes the supported OSs for the Plug-in for Virtualization Server Provisioning setup tool. The supported versions of VMWare vsphere are 4.1 and 4.1 Update 1..NET Framework 2.0 or later is required. Table 64 Supported OSs for the Plug-in for Virtualization Server Provisioning setup tool OS Edition Service pack Architecture Windows XP Professional Edition SP3 x64 Windows Server 2003 Standard Edition Enterprise Edition SP2 Datacenter Edition Standard x64 Edition SP2 x64 Enterprise x64 Edition Datacenter x64 Edition R2 Standard Edition SP2 R2 Enterprise Edition R2 Datacenter Edition R2 Standard x64 Edition SP2 x64 R2 Enterprise x64 Edition R2 Datacenter x64 Edition Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 97

98 Storage systems requirements OS Edition Service pack Architecture Windows Server 2008 # Standard 32-bit Edition Enterprise 32-bit Edition Datacenter 32-bit Edition SP2 Standard without Hyper-V 32-bit Edition SP2 Enterprise without Hyper-V 32-bit Edition Datacenter without Hyper-V 32-bit Edition Standard Edition SP2 x64 Enterprise Edition Datacenter Edition Standard without Hyper-V Edition SP2 x64 Enterprise without Hyper-V Edition Datacenter without Hyper-V Edition R2 Standard SP1 x64 R2 Enterprise R2 Datacenter Windows Vista Business Edition Enterprise Edition SP2 x64 Ultimate Edition Windows 7 Professional SP1 Enterprise x64 Ultimate #1 Operation on Server Core is not supported. Storage systems requirements To use Device Manager or Tiered Storage Manager to manage storage systems, you need storage system management tools and software in addition to Device Manager and Tiered Storage Manager. Updating the microcode or firmware If you want to update the microcode or firmware of a storage system, follow the procedure below. While the microcode or firmware is being updated, do not change the configuration by, for example, refreshing the storage system or performing path operations. To update the microcode or firmware: 1. Make sure that no Device Manager refresh or setup operations are being executed on the target storage system. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 98

99 Storage systems requirements ou need to ensure that operations such as adding or removing storage, creating or deleting LDEVs, and setting the host mode have finished. Note: ou do not need to stop the Device Manager server. 2. Temporarily change the settings in the property file so that the Device Manager database is not updated while the microcode or firmware is being updated. Change the property settings in the server.properties file as follows: Change the setting for the server.dispatcher.daemon.configupdate.detection.interval property to 0. Change the setting for the server.dispatcher.daemon.autosynchro.dorefresh property to false. 3. Update the microcode or firmware. During the update, an error might be output to the trace log or error log because of storage system polling. This error will not be output after the microcode is changed successfully. 4. Set the SVP tuning parameters, and then restart the SVP. 5. For Virtual Storage Platform or Universal Storage Platform V/VM, restart the Device Manager server. 6. Manually refresh the storage system. 7. Restore the property settings that you changed in step 2. Virtual Storage Platform The following table lists the prerequisite firmware versions and software products. Table 65 Prerequisite firmware versions and software products (for Virtual Storage Platform) Prerequisite firmware versions Controller microcode: x-xx/xx or later Controller microcode to manage copy groups defined by device groups: xx/xx or later Prerequisite software products Required software to manage storage systems: Java API SNMP API To add LUN and delete LUN LUN Manager Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 99

100 Storage systems requirements Prerequisite firmware versions Prerequisite software products To use the Volume Migration functionality: Volume Migration V2 Volume Shredder (Required to destroy the data on migration-source volumes.) Open Volume Management (Required to destroy data when there are multiple migration-source DP volumes.) Data Retention (Required to lock volumes.) To use functions for creating a LUSE or LDEV (CVS): OPEN Volume Management To use the copy pair functionality: ShadowImage ShadowImage for Mainframe *1 TrueCopy TrueCopy for Mainframe *1 Copy-on-Write Snapshot Universal Replicator Universal Replicator for Mainframe *1 To use Element Manager: Storage Navigator To use Universal Volume Manager: Universal Volume Manager To use cache logical partitioning (CLPR): Virtual Partition Manager To use 3DC functionality: Disaster Recovery Extended To use the Dynamic Provisioning functionality: Dynamic Provisioning To use the Dynamic Tiering functionality: Dynamic Tiering #1: In Device Manager, confirm of the configuration information of a copy pair is possible. Change of a configuration is impossible. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 100

101 Storage systems requirements Universal Storage Platform V/VM The following table lists the prerequisite firmware versions and software products. Table 66 Prerequisite firmware versions and software products (for Universal Storage Platform V/VM) Prerequisite firmware versions Controller microcode: xx/xx or later Java API SNMP API Prerequisite software products Controller microcode to use a Universal Replicator function or a Hitachi Universal Replication for Mainframe function: xx/xx or later Controller microcode to use a LUSE: xx/xx or later Controller microcode to use the function that allows LU creation and LU formatting to be performed separately: xx/xx or later Controller microcode to use when a copy pair of Hitachi ShadowImage for Mainframe or of Hitachi TrueCopy for Mainframe exists on a managed Universal Storage Platform V/VM: xx/xx or later Controller microcode to use the setup function of the Dynamic Provisioning functionality: xx-xx/xx or later To add LUN and delete LUN LUN Manager To use the Volume Migration functionality: Volume Migration V2 Volume Shredder (Required to destroy the data on migration-source volumes.) Open Volume Management (Required to destroy data when there are multiple migration-source DP volumes.) Data Retention (Required to lock volumes.) To use functions for creating a LUSE or LDEV (CVS): OPEN Volume Management To use the copy pair functionality: ShadowImage Hitachi ShadowImage for Mainframe # TrueCopy Hitachi TrueCopy for Mainframe # TrueCopy Asynchronous Hitachi TrueCopy Asynchronous for Mainframe # Universal Replicator Hitachi Universal Replicator for Mainframe # Copy-on-Write Snapshot # To use Element Manager: Storage Navigator To use Universal Volume Manager: Universal Volume Manager Controller microcode to perform a quick format: To use storage logical partitioning (SLPR) or cache logical partitioning (CLPR): Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 101

102 Storage systems requirements Prerequisite firmware versions x-xx/xx or later Prerequisite software products Virtual Partition Manager Controller microcode to use the performance information acquisition feature: xx/xx or later To use 3DC functionality: Disaster Recovery Extended Controller microcode to use the function that links Dynamic Provisioning and TrueCopy, and the function that links Dynamic Provisioning and Universal Replicator: x-xx/xx or later To use the Dynamic Provisioning functionality: Dynamic Provisioning Controller microcode to use Universal Volume Manager for mapping external volumes to internal volumes: x-xx/xx or later Controller microcode to use Universal Volume Manager for removing the mapping between external and internal volumes: xx/xx or later Controller microcode to manage storage systems by using IPv6 addresses: x-xx/xx or later Controller microcode to use 23 REC Command Support as the host mode option xx/xx or later Controller microcode to use 48 HAM Svol Read Option as the host mode option xx/xx or later Controller microcode to use 49 BB Credit Set Up Option1, 50 BB Credit Set Up Option2 or 51 Round Trip Set Up Option as the host mode option x-xx/xx or later Controller microcode to use when the Device Manager server Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 102

103 Storage systems requirements Prerequisite firmware versions periodically checks changes in the Universal Storage Platform V/VM configuration: xx/xx or later Prerequisite software products #: From Device Manager, you can only check configuration information of copy pairs. ou cannot change the copy pair configuration. Note: Do not use DHCP if you use Device Manager to manage the storage system. Hitachi USP The following table describes the prerequisite firmware versions and software products. Table 67 Prerequisite firmware versions and software products (for Hitachi USP) Prerequisite firmware versions Controller microcode: xx/xx or later Java API SNMP API Prerequisite software products Controller microcode to use the Virtual Partition Manager view function: xx-xx/xx or later Controller microcode to use Universal Replicator functions: xx/xx or later Controller microcode to use Universal Volume Manager to view the setting status of a remote command device: xx/xx or later To add LUN and delete LUN LUN Manager To use the Volume Migration functionality: Volume Migration V2 Volume Shredder (Required to destroy the data on migration-source volumes.) Open Volume Management (Required to destroy data when there are multiple migration-source DP volumes.) Data Retention (Required to lock volumes.) To use functions for creating a LUSE or LDEV (CVS): OPEN Volume Management To use the copy pair functionality: Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 103

104 Storage systems requirements Prerequisite firmware versions Prerequisite software products ShadowImage Hitachi ShadowImage for Mainframe #1 TrueCopy Hitachi TrueCopy for Mainframe #1 TrueCopy Asynchronous Hitachi TrueCopy Asynchronous for Mainframe #1 Universal Replicator Hitachi Universal Replicator for Mainframe #1 Copy-on-Write Snapshot #1 To use Element Manager: Storage Navigator To use Universal Volume Manager: Universal Volume Manager #2 Controller microcode to use 3DC functionality: xx/xx or later To use storage logical partitioning (SLPR) or cache logical partitioning (CLPR): Virtual Partition Manager Controller microcode to use the function that allows LU creation and LU formatting to be performed separately: xx/xx or later Controller microcode to use the function for acquiring the status of an LDEV: xx/xx or later Controller microcode to use the performance information acquisition feature: xx/xx or later Controller microcode to use 19 VMware as the host mode option: xx/xx or later Controller microcode to use 27 iscsi Delayed ACK improvement as the host mode option: xx/xx or later Controller microcode to use 23 REC Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 104

105 Storage systems requirements Prerequisite firmware versions Command Support as the host mode option: x-xx/xx or later Prerequisite software products #1: #2: From Device Manager, you can only check configuration information of copy pairs. ou cannot change the copy pair configuration. Even if Universal Volume Manager is used, cannot an external volume maps to an internal volume and remove of a mapping. Note: Do not use DHCP if you use Device Manager to manage the storage system. Lightning 9900V The following table describes the prerequisite firmware versions and software products. Table 68 Prerequisite firmware versions and software products (for Lightning 9900V) Prerequisite firmware versions Controller microcode: xx/xx or later Java API SNMP API Prerequisite software products Controller microcode to perform incontext launching of the Storage Navigator: xx/xx or later Controller microcode to launch NAS Manager: xx/xx or later Controller microcode to use Open LDEV Guard function: xx/xx To add LUN and delete LUN LUN Manager To use functions for creating a LUSE or LDEV (CVS): Open Volume Management To use the copy pair functionality: Hitachi ShadowImage Hitachi TrueCopy Hitachi TrueCopy Asynchronous To use Element Manager: Storage Navigator To link with NAS Manager: Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 105

106 Storage systems requirements Prerequisite firmware versions Prerequisite software products NAS/Management Note: Do not use DHCP if you use Device Manager to manage the storage system. Lightning 9900 Device Manager and Tiered Storage Manager versions 7.0 and later do not support Lightning If Lightning 9900 remains under management after upgrading Device Manager and Tiered Storage Manager, use GUI or CLI to remove Lightning 9900 from Device Manager management. Hitachi AMS 2000 The Device Manager server supports Hitachi AMS 2000 only in Windows and Solaris. The following table lists the prerequisite firmware versions and software products. Table 69 Prerequisite firmware versions and software products (for Hitachi AMS 2000) Prerequisite firmware versions Hitachi AMS 2000 firmware version: Any Firmware version required to use TrueCopy: Any Prerequisite software products To set for LUN security, or using an iscsi function #2 LUN Manager To use LUSE: LUN Expansion Firmware version required to use TrueCopy Modular Distributed: 2/x-x Firmware version required to use iscsi: Any Firmware version required to use SSL communication: x84x/x-x To use a lock system for devices accessed from Device Manager: Password Protection Account Authentication To use the copy pair functionality: ShadowImage in-system replication TrueCopy remote replication TrueCopy Extended Distance TrueCopy Modular Distributed Copy-on-write SnapShot Firmware version required to manage Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 106

107 Storage systems requirements Prerequisite firmware versions storage systems by using IPv6 addresses: x/x-x Firmware version required to use the Dynamic Provisioning functionality: x87x/x-x Firmware version required to use Discovery CHAP as the host mode 2 (host connection mode 2): 0/A-x Firmware version required to use Unique Extended COP Mode or Unique Write Same Mode as the host mode 2 (host connection mode 2): x890/a-x Prerequisite software products To use Element Manager: Storage Navigator Modular 2 #1 To use the Dynamic Provisioning functionality: Dynamic Provisioning To use SMI-S to acquire performance information: Performance Monitor To use or cache logical partitioning : Cache Partition Manager #1: #2: Configure a management server in a non-cluster configuration. Use version or later when Element Manager is used to replace a micro program. Necessary, only when an iscsi function is used from GUI. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 107

108 Storage systems requirements Caution: If you use both Storage Navigator Modular 2 and Device Manager that are installed on the same computer to manage a storage system, the setting for the following items must be the same in Storage Navigator Modular 2 and Device Manager: IP address of the storage system (or the resolved IP address if a host name is specified) Communication protocol Do not use DHCP if you use Device Manager to manage the storage system. Use Storage Navigator Modular 2 to make sure that DHCP is not selected. If you upgrade the model of a storage system, device information such as the serial number and model name might be changed. For this reason, if you perform a refresh operation by using Device Manager after the upgrade, an error (KAIC07299-E) might occur. If an error occurs, delete the storage system in which an error occurred from Device Manager, re-register it, and then set the following Device Manager information again: Information about storage that has been added to logical groups Information about LDEVs that have been allocated to the resource group Information of links to URLs (URLLink) set up by using the CLI Labels that have been set for LDEVs Storage system names (if the names have been changed from the default) Storage system device information written in CLI batch and script files Note that, if you are using Hitachi Command Suite products other than Device Manager, also check, and if necessary, revise the settings for those products. AMS2010 FC (8GB) is not supported. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 108

109 Storage systems requirements Note: If the following OSs are used on the management server, you can use IPv6 for communication between Hitachi AMS 2000 and the management server: Windows Server 2003 SP2 () Windows Server 2003 SP2 (x64) Windows Server 2003 R2 SP2 () Windows Server 2003 R2 SP2 (x64) Windows Vista SP1 () Solaris 10 (SPARC) Hitachi SMS The Device Manager server supports Hitachi SMS only in Windows and Solaris. The following table lists the prerequisite firmware versions and software products. Table 70 Prerequisite firmware versions and software products (for Hitachi SMS) Prerequisite firmware versions Hitachi SMS firmware version: Any Firmware version required to use SSL communication: x84x/x-x Prerequisite software products To set for LUN security, or using an iscsi function #3 LUN Manager To use LUSE: LUN Expansion Firmware version required to manage storage systems by using IPv6 addresses: x/x-x To use a lock system for devices accessed from Device Manager: Password Protection Account Authentication Firmware version required to use Discovery CHAP as the host mode 2 (host connection mode 2): 0/A-x To use the copy pair functionality: ShadowImage in-system replication TrueCopy remote replication #1 Copy-on-write SnapShot Simple Data Recovery #1 To use Element Manager: Storage Navigator Modular 2 #2 To use SMI-S to acquire performance information: Performance Monitor Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 109

110 Storage systems requirements #1: #2: #3: From Device Manager, you can only check configuration information of copy pairs. ou cannot change the copy pair configuration. Configure a management server in a non-cluster configuration. Use version or later when Element Manager is used to replace a micro program. Necessary, only when an iscsi function is used from GUI. Caution: If you use both Storage Navigator Modular 2 and Device Manager that are installed on the same computer to manage a storage system, the setting for the following items must be the same in Storage Navigator Modular 2 and Device Manager: IP address of the storage system (or the resolved IP address if a host name is specified) Communication protocol Do not use DHCP if you use Device Manager to manage the storage system. Use Storage Navigator Modular 2 to make sure that DHCP is not selected. Note: For IP-SAN configurations, if the following OSs are used on the management server, you can use IPv6 for communication between Hitachi SMS and the management server: Windows Server 2003 SP2 () Windows Server 2003 SP2 (x64) Windows Server 2003 R2 SP2 () Windows Server 2003 R2 SP2 (x64) Windows Vista SP1 () Solaris 10 (SPARC) Hitachi AMS/WMS The Device Manager server supports Hitachi AMS/WMS only when the Windows or Solaris version is being used. The following table describes the prerequisite firmware versions and software products. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 110

111 Storage systems requirements Table 71 Prerequisite firmware versions and software products (for Hitachi AMS/WMS) Prerequisite firmware versions Hitachi AMS/WMS firmware version: Any Firmware version required to use TrueCopy: For Hitachi AMS 500 or Hitachi AMS 1000: Any For Hitachi AMS 200 or Hitachi WMS 100: 0760/A or later Firmware version required to use iscsi: For Hitachi AMS 200, Hitachi AMS 500, or Hitachi WMS 100: 0730/B or later For Hitachi AMS 1000: 0732/A or later Prerequisite software products To set for LUN security, or using an iscsi function #4 LUN Manager To use LUSE: LUN Expansion To use a lock system for devices accessed from Device Manager: Password Protection Account Authentication #1 To use the copy pair functionality: #2 ShadowImage in-system replication TrueCopy remote replication TrueCopy Extended Distance Copy-on-write SnapShot To use Element Manager: Storage Navigator Modular 2 #3 To use SMI-S to acquire performance information: Performance Monitor To use or cache logical partitioning : Cache Partition Manager #1: #2: #3: #4: If you want to use Account Authentication, the firmware version of the storage system must be 0760/A or later and the firmware version of Storage Navigator Modular (for Web) must be 6.0 or later. To expand the mirror configuration, the firmware version of the storage system must be 0750/A or later. Configure a management server in a non-cluster configuration. Use version or later when Element Manager is used to replace a micro program. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 111

112 Storage systems requirements Necessary, only when an iscsi function is used from GUI. Caution: If you use both Storage Navigator Modular 2 and Device Manager that are installed on the same computer to manage a storage system, the setting for the IP address of the storage system (or the resolved IP address if a host name is specified) must be the same in Storage Navigator Modular 2 and Device Manager. Do not use DHCP if you are using Device Manager to manage the storage systems. Use Storage Navigator Modular (for Web) or Storage Navigator Modular 2 to make sure that DHCP is not selected. Note: IPv6 is not supported for IP-SAN configurations. For a NAS Modular system of Hitachi AMS/WMS, Device Manager only allows you to add storage systems and to launch Storage Navigator Modular or Storage Navigator Modular 2. To operate a NAS Modular system of Hitachi AMS/WMS, perform the operations from Storage Navigator Modular. Thunder 9500V The Device Manager server supports Thunder 9500V only when the Windows or Solaris version is being used. The following table describes the prerequisite firmware versions and software products. Table 72 Prerequisite firmware versions and software products (for Thunder 9500V) Prerequisite firmware versions Thunder 9580V firmware version: 1655/B or later Prerequisite software products To set for LUN security LUN Management Thunder 9585V firmware version: 1657/A or later To use LUSE: LUN Expansion Thunder 9520V firmware version: 0659/M or later Firmware version required to use QuickShadow: To use a lock system for devices accessed from Device Manager: Password Protection To use the copy pair functionality: Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 112

113 Storage systems requirements Prerequisite firmware versions For Thunder 9580V: 1655/D or later For Thunder 9585V: 1657/A or later For Thunder 9520V: 0659/M or later Prerequisite software products Hitachi ShadowImage Hitachi TrueCopy Basic Hitachi QuickShadow Firmware version required to use SATA expansion enclosure: For Thunder 9580V or Thunder 9585V: 1658 or later For Thunder 9520V: 0659/M or later Firmware version required to use LUN Management: For Thunder 9580V: 1655/D or later For Thunder 9585V: 1657/A or later For Thunder 9520V: 0659/M or later To use SMI-S to acquire performance information: Performance Management - Base Monitor To use Element Manager: Storage Navigator Modular 2 #: Configure a management server in a non-cluster configuration. Use version or later when Element Manager is used to replace a micro program. Caution: Before installation, use Storage Navigator Modular (for Web) or DAMP (for Web) to verify that there are no ports with a WWN node name consisting only of zeros. If there is, you must change the name or delete the WWN, or a node-name error message will be output. If the Password Protection option is installed and usable, any addition of a storage system to Device Manager requires a Password Protection user ID and password. Do not use DHCP if you use Device Manager to manage the storage system. Use Storage Navigator Modular (for Web), DAMP (for Web), or Storage Navigator Modular 2 to make sure that DHCP is not selected. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 113

114 Storage systems requirements SMI-S Enabled storage systems The following table lists the SMI-S Enabled storage systems supported in Device Manager and Tiered Storage Manager. Table 73 Supported SMI-S Enabled storage system for Device Manager and Tiered Storage Manager Vendor name Model no. Provider HP EVA 3000 #1#4 EVA 4100 #2#4 EVA 4400 #2#4 EVA 5000 #1#4 EVA 6100 #2#4 EVA 6400 #2#3#4 EVA 8100 #2#4 EVA 8400 #2#3#4 EMC CLARiiON CX200 #4 CLARiiON CX300 #4 CLARiiON CX400 #4 CLARiiON CX500 #4 CLARiiON CX600 #4 CLARiiON CX700 #4 CLARiiON CX3 series #4 CLARiiON CX4 series #4 HP StorageWorks Command View EVA or later (SMI-S Version 1.2 or later) EMC Solutions Enabler (EMC SMI-S Provider) 6.5 or later (4.2 or later) (SMI-S Version 1.2 or later) IBM DS8000 series #4 IBM CIM Agent for DS Open API 5.3 or later (SMI-S Version 1.2 or later) #1: Firmware version is or later. #2: Firmware version is or later. #3: When this subsystem is used for an external storage of USP V/VM, the microcode version of the USP V/VM should be xx/xx or later. #4: When this subsystem is used for an external storage of VSP, the microcode version of the VSP should be /00 or later. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 114

115 Copyrights and Licenses Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED Notice: No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi Data Systems Corporation (hereinafter referred to as Hitachi Data Systems ). Hitachi Data Systems reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. Hitachi Data Systems products and services can only be ordered under the terms and conditions of Hitachi Data Systems applicable agreements. All of the features described in this document may not be currently available. Refer to the most recent product announcement or contact your local Hitachi Data Systems sales office for information on feature and product availability. This document contains the most current information available at the time of publication. When new and/or revised information becomes available, this entire document will be updated and distributed to all registered users. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., and the Hitachi Data Systems design mark is a trademark and service mark of Hitachi, Ltd. All other brand or product names are or may be trademarks or service marks of and are used to identify products or services of their respective owners. Adobe and Flash are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. AIX is a registered trademark of the International Business Machines Corp. in the U.S. All Borland brand names and product names are trademarks or registered trademarks of Borland Software Corporation in the United States and other countries. Brocade is a trademark or a registered trademark of Brocade Communications Systems, Inc. in the United States and/or in other countries. BSAFE is a registered trademark or trademark of RSA Security Inc. in the United States and/or other countries. ESCON is a registered trademark of the International Business Machines Corp. in the U.S. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 115

116 Copyrights and Licenses HP is a trademark of the Hewlett-Packard Company. HP Tru64 UNIX is a trademark of Hewlett-Packard Company. HP-UX is a product name of Hewlett-Packard Company. HP StorageWorks is a trademark of Hewlett-Packard Company. IBM is a registered trademark of the International Business Machines Corp. in the U.S. OS/390 is a registered trademark of the International Business Machines Corp. in the U.S. z/os is a registered trademark of the International Business Machines Corp. in the U.S. Java TM and JDK are registered trademarks of Oracle and/or its affiliates. Linux is a registered trademark or trademark of Linus Torvalds in the U.S. and other countries. Microsoft is a registered trademark of Microsoft Corp. in the U.S. and other countries. Microsoft.NET is software for connecting people, information, systems, and devices. Internet Explorer is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries. Microsoft and Windows Server are registered trademarks of Microsoft Corp. in the U.S. and other countries. Mozilla is a trademark of the Mozilla Foundation in the U.S and other countries. NetWare is a registered trademark of Novell, Inc. RC2 is a registered trademark or trademark of RSA Security Inc. in the United States and/or other countries. RC4 is a registered trademark or trademark of RSA Security Inc. in the United States and/or other countries. Red Hat is a registered trademark or trademark of Red Hat, Inc. in the United States and/or other countries. RSA is a registered trademark or trademark of RSA Security Inc. in the United States and/or other countries. Hitachi Device Manager Software includes RSA BSAFE Cryptographic software from RSA Security Inc. RSA is a registered trademark of RSA Security Inc. Solstice is either a registered trademark or a trademark of Oracle and/or its affiliates. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc., in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 116

117 Copyrights and Licenses Solaris is a registered trademark of Oracle and/or its affiliates. Sun and Sun Microsystems are registered trademarks of Oracle and/or its affiliates. ORACLE is either a registered trademark or a trademark of Oracle Corporation and/or its affiliates in the United States and/or other countries. Sun and StorEdge are registered trademarks of Oracle and/or its affiliates. Sun Fire is a registered trademark of Oracle and/or its affiliates. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. VERITAS is a trademark or registered trademark of Symantec Corporation in the U.S. and other countries. VMware and ESX are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Windows NT is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Windows Server is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Windows Vista is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Windows 7 is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. This product includes software developed by the Apache Software Foundation ( This product includes software developed by Ben Laurie for use in the Apache- SSL HTTP server project. This product includes software developed by Borland Software Corp. This product includes software developed by Ralf S. Engelschall [email protected] for use in the mod_ssl project ( The file of interclient.jar was extracted from the InterClient Solaris version 2.0 as of November 15th, 2002, which "Original Code" was created by InterBase Software Corp and its successors, and which portions created by Borland/Inprise are Copyright (C) Borland/Inprise. All Rights Reserved. EMC and CLARiiON are registered trademarks of EMC Corporation. Hitachi Device Manager and Hitachi Tiered Storage Manager include some parts whose copyrights are reserved by Oracle and/or its affiliates. Hitachi Device Manager Software includes some parts whose copyrights are reserved by UNIX System Laboratories, Inc. SUSE is a registered trademark of Novell, Inc. in the United States and other countries. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 117

118 Copyrights and Licenses Kerberos is a name of network authentication protocol created by Massachusetts Institute of Technology. Other product and company names mentioned in this document may be the trademarks of their respective owners. Throughout this document Hitachi has attempted to distinguish trademarks from descriptive terms by writing the name with the capitalization used by the manufacturer, or by writing the name with initial capital letters. Hitachi cannot attest to the accuracy of this information. Use of a trademark in this document should not be regarded as affecting the validity of the trademark. Copyright 2011 Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 118