HP 12200, User Manual

Page: 173 / 205

A Troubleshooting
This appendix describes some common issues you may encounter while configuring or using the
VLS including automigration/replication and deduplication issues.
VLS Common Issues
Solution Possible causes Symptom
Increase the maximum number of LUNs
per device the operating system is There are more LUNs on the FC host
ports than the operating system is Some of the virtual devices are not
detected by the operating system
configured to see. To change the
maximum LUN per device setting: configured to see. Once the maximum
number of LUNs on a device is
detected, the operating system stops when it scans the SAN for new
hardware.
•
For Microsoft Windows—See
http://support.microsoft.com/
looking for more LUNs. In the case of
the VLS, the operating system
default.aspx?
scid=kb%3ben-us%3b310072
.
considers each FC host port to be one
device. So, if the maximum number of
•
For HP-UX—The value can only be
changed for HP-UX versions 11.31
LUNs an operating system is
configured to see is eight, the
and later. Increase the number of
operating system will only see LUN0,
LUNs per bus on the HP-UX server
LUN1, ..., LUN7 and will not see
by entering
# scsimgr set_attr
LUN8, LUN9, ..., and up on each FC
-a max_lunid=32
. You can view
host port. By default Windows and
the connected IO by entering
#
ioscan -m lun
.
You cannot create legacy DSFs for
LUN IDs above 7; use persistent
device special files instead.
HP-UX hosts can see a maximum of 8
LUNs per FC host port.
See the HP-UX documentation for
more information.
•
For other operating systems—See
the operating system web site.
Use the VLS's LUN masking feature to
restrict the number of virtual devices the
host sees on the VLS FC host ports, so
it only sees the virtual devices it needs
to see. Then, use the VLS's LUN
mapping feature to assign LUNs to the
virtual devices the host can see, such
that the virtual device LUN numbers
include a LUN0 and no gaps in the
LUN numbering. See
LUN Masking and
LUN Mapping for instructions.
Remove the gap in the LUN numbering
by editing the host's LUN mapping (see There is a gap in the LUN numbering
on the FC host port. Most operating
LUN Mapping ), or if a virtual device systems will stop looking for virtual
has been destroyed on the VLS, devices on an FC host port once a
creating a gap in the LUN numbering, gap in the LUN numbering is detected.
restart the VLS device emulations. The For example, if LUN0, LUN1, and
VLS firmware will reassign LUNs to the LUN3 are mapped to an FC host port,
virtual devices as necessary to remove the operating system will see LUN0
any gaps in the LUN numbering. See
Restarting VLS Device Emulations .
and LUN1. When it does not find a
LUN2, it will assume there are no
more LUNs on the port and stop
looking.
Delete the Windows NtmsData
database and put the RSM into the There are two levels of logical device
binding in the Windows OS. At the The virtual tape drive devices either
disappear or move to a different
Disabled state using the following
procedure :
VLS Common Issues 173