HP XP7 Auto LUN User Guide (TK915-96001)

• If you delete an Auto LUN plan, the volume status changes from SMPL(PD) to SMPL. You can
check the status of the volume by viewing the list at the bottom of the window and confirming
the existence of the migration plan.
You can check the status of a volume by using the pairdisplay command, but you cannot
distinguish between the SMPL and SMPL(PD) status.
• When you delete an Auto LUN plan, you should wait until the status of the volume changes
from SMPL(PD) to SMPL (usually about 10 seconds) before executing another Auto LUN
operation through RAID Manager.
• When you attempt to migrate a volume or cancel a migration plan through RAID Manager,
you might encounter an "EX_CMDRJE" exception and the command might be refused depending
on the condition in the DKC.
Troubleshooting when using RAID Manager
When you execute or cancel an Auto LUN plan through RAID Manager, you might identify the
cause of the error by referring to the log displayed on the RAID Manager window or in the RAID
Manager operation log file.
The RAID Manager operation log file is stored in:
/HORCM/log*/curlog/horcmlog_HOST/horcm.log
Where:
• * is the instance number.
• HOST is the host name.
The following figure shows an example of error log message in the RAID Manager window.
Figure 6 Example of a Log Displayed on The RAID Manager Window
Table 20 (page 33) shows the RAID Manager error messages related to executed or canceled
migration plans.
Table 20 RAID Manager errors related to migration plans
Required ActionMessageError Code
(SSB2)
The volume cannot be migrated. Check the
configuration definition file.
The cache mode does not match between the
migration source volume and the migration target
volume.
2027
After the configuration change has finished, try
again.
In the migration source volume, the serial number
and the model of the virtual storage machine or
the virtual LDEV ID has been changed.
203E
After the configuration change has finished, try
again.
In the migration target volume, the serial number
and the model of the virtual storage machine or
the virtual LDEV ID has been changed.
203F
Specify a volume whose capacity is supported.The current microcode version does not support
the capacity of the migration source volume.
204A
Specify a volume whose capacity is supported.The current microcode version does not support
the capacity of the migration target volume.
204B
Release the volume from Volume Retention, and
then migrate the volume.
The migration target volume is being used with
Volume Retention.
2050
Release the volume from Data Retention, and then
migrate the volume.
The migration target volume is being used with
Data Retention.
2051
Troubleshooting when using RAID Manager 33