HP XP P9000 Command View Advanced Edition Suite Software 7.5.0-00 Administrator Guide (Web Version) (TB581-96346, July 2013)

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 235.
When executing the HiScan com-
mand in a Windows Server 2008,
Windows Server 2008 R2 or Win-
dows Server 2012 environment, the
KAIC22009-E, KAIC22014-E, KA-
IC22019-E, or KAIC22048-E error
message is output, and host informa-
tion cannot be registered on the
Device Manager server.
9
When a host refresh is performed in
a Windows Server 2008, Windows
Server 2008 R2 or Windows Server
2012 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
Maintenance information that must be collected if a failure
occurs
If you cannot identify the cause of a failure or recover from a failure, collect the maintenance
information, and then contact our support center.
If a failure occurs, you need to collect the following information to determine the cause of the failure:
• 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
Administrator Guide (Web Version) 287