| Prerequisite products (HDvM agent) | |||||||||||||||||||
| return to main contents page | |||||||||||||||||||
| return to "Application
server" contents page |
|||||||||||||||||||
| �ETo acquire the WWN information for an HBA with no storage subsystem connected on a Windows, Solaris, or Linux host, an HBA API library that supports SNIA HBA API needs to be installed. (These libraries are provided by the HBA vendors.) | |||||||||||||||||||
| �EIf you want to use iSCSI, it is necessary to use following HBA or NIC. | |||||||||||||||||||
| OS | iSCSI HBA/NIC | Comment | |||||||||||||||||
| Windows Server 2008 SP2
Enterprise Edition (x86/x64) Windows Server 2008 R2 SP1 Enterprise Edition (x86/x64) Windows Server 2012 Windows Server 2012 R2 |
Qlogic QLA4050c(*1) | The iSCSI software (MS iSCSI Initiator 2.04 or later) and QLogic driver are necessary. | |||||||||||||||||
| Qlogic QLA4052c(*1) | The iSCSI software (MS iSCSI Initiator 2.04 or later) and QLogic driver are necessary. | ||||||||||||||||||
| Qlogic QLA4010c(*1) | The iSCSI software (MS iSCSI Initiator 2.04 or later) and QLogic driver are necessary. | ||||||||||||||||||
| Windows | NIC | The iSCSI software (MS iSCSI Initiator 2.04 or later) is necessary. | |||||||||||||||||
| Solaris | NIC | The iSCSI Initiator bundled with OS is necessary. | |||||||||||||||||
| AIX | NIC | The iSCSI Initiator bundled with OS is necessary. | |||||||||||||||||
| HP-UX | NIC | The iSCSI Initiator bundled with OS is necessary. | |||||||||||||||||
| Linux | NIC | The iSCSI Initiator bundled with OS is necessary. | |||||||||||||||||
| Notes: | |||||||||||||||||||
| (*1) In order to use a QLogic HBA, download and then install Information Tool (fcinfo) version x86 from the Microsoft web site. | |||||||||||||||||||
| Even if the OS of a host where the Device Manager agent is installed is the IPF version or x64 version, the fcinfo x86 version must be used. | |||||||||||||||||||
| 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. | |||||||||||||||||||
| 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. | |||||||||||||||||||
| • The Device Manager agent only supports global addresses. You cannot use link-local addresses or global unique local addresses (site-local addresses). | |||||||||||||||||||