HP XP7 Command View Advanced Edition Administrator Guide (Web Version) (TK981-96004, May 2014)
Cause
• This problem might occur if a host recognizes 100 or more LUs that are managed by Device
Manager.
• This problem might occur due to high load on the Device Manager server. If so, the following error
message will have been output to the log file specified by the -t option of the HiScan command
or to the HiScan.msg file:
<html><head><title>400 Bad request</title>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
</head><body>
<h1>400 Bad request</h1>
<p><strong>ServiceConnection#0: java.lang.OutOfMemoryError</strong>
</body></html>
The HiScan.msg file is stored in the following locations:
In Windows:
installation-folder-for-the-Device-Manager-agent\bin\logs\
In Solaris, Linux, or HP-UX:
/opt/HDVM/HBaseAgent/bin/logs/
In AIX:
/usr/HDVM/HBaseAgent/bin/logs/
Countermeasure
• If one host recognizes 100 or more LUs that are managed by Device Manager, change the host
settings so that the host can manage 100 or more LUs.
• If the Device Manager server is highly loaded, take action as follows:
• Change the memory heap size on the Device Manager server.
• If multiple hosts concurrently execute the HiScan command, use the hdvmagt_setting
command to adjust the HiScan command execution schedule of those hosts.
Related topics:
• Changing the memory heap size, page 25
• Settings required for a host to manage 100 or more LUs, page 204
• Setting the Device Manager server's information, HiScan command's execution period, and RAID
Manager's information (hdvmagt_setting command), page 213
• Reporting host information to the Device Manager server manually (HiScan command), page 214
The file system name is not displayed in the Device Manager GUI
In a Solaris environment, if the file system name is not displayed in the Device Manager GUI, use
VxVM 4.0 or later.
Cause
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.
Administrator Guide (Web Version) 301