HP Hitachi Dynamic Link Manager Software - Manual (Page 194)

4. HDLM Operation
170
4.1 Notes on Using HDLM
This section contains notes that are important for running HDLM operations.
4.1.1 Using a Storage Management Program
You must not change the vendor ID and product ID of a storage system. If you change
these IDs, HDLM will not be able to recognize the storage system.
4.1.2 Upgrading Windows
Always uninstall HDLM before upgrading Windows, re-installing Windows during a
system recovery, or installing a Windows SP. After upgrading Windows, install the
appropriate HDLM version for the upgraded version of Windows.
4.1.3 Using MSCS
(1) When the Number of Displayed Paths Is Less than the Actual Number of Paths
When displaying path information, the number of paths displayed might be less than
the actual number of paths. This occurs when one host uses an LU exclusively,
preventing other hosts from obtaining information about the devices for that LU. When
this is resolved and the information can be obtained, the host will be able to display all
the paths.
(2) When a System Event Occurs in an MSCS Environment
When you start up a standby node, or when a standby node has recovered from a path
error, the following event is issued and output to the system event log. However, this
will not affect system operations:
Source: mpio
Event ID: 20
Description: A Path Verification request to a device on
\Device\MPIODiskn that is controlled by Hdlm Device-Specific
Module has failed. This may indicate a Path Failure.
This event occurs when the MPIO checks the disk before initializing it and the standby
node cannot use the LU because the active node is using it.
4.1.4 Using the EMC DMX series, EMC CX series, and HP EVA series
• The EMC DMX series, EMC CX series, and HP EVA series can be managed by
using the HDLM versions listed below.
• If the OS is Windows Server 2003:
EMC DMX series and EMC CX series: HDLM 5.7 or later
HP EVA series: HDLM 5.9.1 or later