HP 12000 HP 12200 Gateway Virtual Library System User Guide (BW403-10001, June - Page 173

A Troubleshooting, VLS Common Issues

Get HP 12000 PDF manuals and user guides View all HP 12000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 173 highlights

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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 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
h
t
tp://su
ppo
r
t
.mi
c
r
o
s
o
f
t
.co
m/
looking for more LUNs. In the case of
the VLS, the operating system
de
f
a
ult
.a
s
p
x?
s
c
i
d=kb%3be
n
-u
s%3b3
1
00
7
2
.
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