HP StorageWorks P9000 Command View Advanced Edition Suite Software 7.1.1 Administrator Guide (web) (TB581-96065, September 2011)

SolutionProblemNo.
This occurs if there are 100 or more LUs managed by Device
Manager recognized by a single host, and the Device
Manager agent is upgraded from version 6.0.0-00 -
6.2.0-02 to version 6.4 or later via an overwrite installation.
To avoid this, follow the procedure in “Property settings for
hosts that manage 100 or more LUs” on page 215.
When executing the HiScan com-
mand in a Windows Server 2008 or
Windows Server 2008 R2 environ-
ment, the KAIC22009-E, KA-
IC22014-E, KAIC22019-E, or KA-
IC22048-E error message is output,
and host information cannot be re-
gistered on the Device Manager
server.
9
When a host refresh is performed in
a Windows Server 2008 or Win-
dows Server 2008 R2 environment,
an OutOfMemory error occurs on the
host, and there is no response for a
while.
10
To check the correspondence between the file system and
LUN, use VxVM version 4.0 or later. When using a version
of VxVM earlier than 4.0, the Device Manager agent does
not notify the Device Manager server of correspondence
between the file system and LUN if device names are set
based on the enclosure.
When using a version of VxVM
earlier than 4.0 in a Solaris environ-
ment, file system names are not
shown from the Device Manager
GUI.
11
The active node is providing disk reserve normally for the
shared disk, and therefore there is no problem with the
system. Shared disk information is acquired from the Device
Manager agent running on the active node, and therefore
there is no problem with the operation of Device Manager.
This problem is listed because it might occur rarely if the
execution frequency of the HiScan command for the Device
Manager agent is set to the same time in both the active
node and the standby node and if there is a high I/O load
on the shared disk.
In an AIX environment,
SC_DISK_ERR2 (Device Busy) is
output in the error log of the standby
node.
In addition, HSDRV_RSV_CONFLICT
is output to the error log.
12
Acquiring maintenance information
If you cannot identify the cause of a failure or recover from a failure, collect the following information
about the failure, and then contact our support center:
• System status after the failure
• Date and time when the failure occurred
• Situation in which the failure occurred
• Network configurations of the management server and the host
• OSs of the management server and the host
• Maintenance information for the computers where the failure occurred
• Maintenance information for the management server
• Maintenance information for Host Data Collector
• Maintenance information for the host
Troubleshooting258