HP XP P9000 Command View Advanced Edition Suite Software 7.6.1-00 Administrator Guide (Web Version)

Countermeasure
To check the correspondence between the file system and LUN, use VxVM version 4.0 or later.
Changes to the storage system configuration are not applied to the Device Manager server
If changes to the storage system configuration are not applied to the Device Manager server, use the
hldutil command or the HiScan command to apply the latest information to the Device Manager
server.
Cause
The OS might not recognize the modified contents immediately after the storage system configuration
is changed (for example, when an LU is registered or deleted). In this case, the Device Manager agent
reports the old information to the Device Manager server.
Countermeasure
1. Execute the hldutil command to check the latest information.
2. Restart the host OS.
3. Execute the HiScan command.
Related topics:
• Reporting host information to the Device Manager server manually (HiScan command), page 242
• Acquiring device information (hldutil command), page 244
Errors requiring no action
For errors listed below, no action is required.
• The following messages are output to the event log or system log when multiple instances of the
HiScan command are executed simultaneously:
• [HORCM_005] Could not create endpoint for remote connection.
• [HORCM_007] Illegal parameter values in HORCM configuration file.
• When a S-VOL in the pair status is being mounted, one of the following messages for event ID 51
or 57 is output to the Windows event log:
• Event ID: 51
An error was detected on device \Device\Harddisknn\DRn during a paging
operation.
• Event ID: 57
The system failed to flush data to the transaction log. Corruption
may occur.
• If the same HiScan command execution interval is set on the active and standby nodes of the
Device Manager agent, SC_DISK_ERR2 (Device Busy) or HSDRV_RSV_CONFLICT is output to
the AIX error log for the secondary node.
This problem sometimes occurs if the I/O load on the shared disk is high.
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 Man-
ager.
Troubleshooting284