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

Managing Virtual Device LUNs, Default LUN Numbering

Page 90 highlights

of the additional storage you make available by erasing cartridges. First erase cartridges from your backup application, then follow the procedure below. From Command View VLS: 1. On the System tab, select Chassis from the navigation screen to open the Chassis status screen. 2. Select Reclaim Space in the task bar. The VLS system initiates space reclamation and the Notifications screen displays a notification of the scheduled reclamation. Managing Virtual Device LUNs The VLS has a LUN masking, a LUN mapping, and a port mapping feature that allows you to restrict host access to the LUNs (virtual libraries and tape drives) configured on the VLS and assign each virtual device to a specific Fibre Channel host port. These features allow you to allocate the virtual devices to individual hosts and distribute the virtual tape drives across the Fibre Channel host ports to achieve maximum bandwidth. See "Managing high availability" (page 103) for more information. You can set a global default so that either the VLS allows all hosts connected to the VLS through the SAN to access all virtual devices configured on the VLS, or the VLS prevents all hosts from viewing any virtual devices until they are explicitly mapped to the host. Each time you add a new host to the VLS, it takes the global default you have set. The VLS firmware also manages the LUN numbering so that the virtual device LUN assignments always meet operating system requirements and restrictions. See "Default LUN Numbering" (page 90) and "Operating System LUN Requirements and Restrictions" (page 90). Port mapping is required and allows you to assign each virtual device to one of the Fibre Channel host ports or a pair of Fibre Channel host ports (if your backup solution supports this). Default LUN Numbering The VLS automatically assigns a logical unit number (LUN) to each virtual library and tape drive created on the VLS in the order in which they are created by you, starting with LUN0 and increasing incrementally by one as each new virtual library or tape drive is created on an Fibre Channel host port (LUN1, LUN2, and so on). The first virtual device port mapped to any of the Fibre Channel host ports is assigned the LUN number LUN0. The second virtual device port mapped to an Fibre Channel host port is assigned the LUN number LUN1, and so on. The default LUN numbers are changed by the VLS firmware when the VLS device emulations are restarted if: • A virtual device has been deleted since the last restart, creating a gap in the LUN numbering, or • A virtual tape drive has been added to a library since the last restart and the default LUN number it was assigned is not consecutive with the other virtual tape drives in the same library. Restarting VLS device emulations changes the default LUN numbers as necessary to remove the gap or to make the virtual tape drive LUN numbers consecutive in each library. This is done so that the virtual device LUN numbering meets the operating system LUN requirements. NOTE: When a LUN has been unconfigured or otherwise deleted, it may still show up in the VLS user interface. Use the VLS discovery utility to refresh the list of LUNs that are present. Operating System LUN Requirements and Restrictions Most operating systems require that each VLS Fibre Channel host port connected to the SAN has a virtual device with the LUN number LUN0 and no gaps in the LUN numbering (LUN0, LUN1, LUN2, and so on). If the operating system does not see a LUN0 on a VLS Fibre Channel host port when it is scanning for new hardware on the SAN, it will stop looking for LUNs on that port and 90 Configuration

  • 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

of the additional storage you make available by erasing cartridges. First erase cartridges from
your backup application, then follow the procedure below.
From Command View VLS:
1.
On the
System
tab, select
Chassis
from the navigation screen to open the Chassis status screen.
2.
Select
Reclaim Space
in the task bar.
The VLS system initiates space reclamation and the Notifications screen displays a notification
of the scheduled reclamation.
Managing Virtual Device LUNs
The VLS has a LUN masking, a LUN mapping, and a port mapping feature that allows you to
restrict host access to the LUNs (virtual libraries and tape drives) configured on the VLS and assign
each virtual device to a specific Fibre Channel host port. These features allow you to allocate the
virtual devices to individual hosts and distribute the virtual tape drives across the Fibre Channel
host ports to achieve maximum bandwidth. See
“Managing high availability” (page 103)
for more
information.
You can set a global default so that either the VLS allows all hosts connected to the VLS through
the SAN to access all virtual devices configured on the VLS, or the VLS prevents all hosts from
viewing any virtual devices until they are explicitly mapped to the host. Each time you add a new
host to the VLS, it takes the global default you have set. The VLS firmware also manages the LUN
numbering so that the virtual device LUN assignments always meet operating system requirements
and restrictions. See
“Default LUN Numbering” (page 90)
and
“Operating System LUN Requirements
and Restrictions” (page 90)
.
Port mapping is required and allows you to assign each virtual device to one of the Fibre Channel
host ports or a pair of Fibre Channel host ports (if your backup solution supports this).
Default LUN Numbering
The VLS automatically assigns a logical unit number (LUN) to each virtual library and tape drive
created on the VLS in the order in which they are created by you, starting with LUN0 and increasing
incrementally by one as each new virtual library or tape drive is created on an Fibre Channel host
port (LUN1, LUN2, and so on). The first virtual device port mapped to any of the Fibre Channel
host ports is assigned the LUN number LUN0. The second virtual device port mapped to an Fibre
Channel host port is assigned the LUN number LUN1, and so on.
The default LUN numbers are changed by the VLS firmware when the VLS device emulations are
restarted if:
A virtual device has been deleted since the last restart, creating a gap in the LUN numbering,
or
A virtual tape drive has been added to a library since the last restart and the default LUN
number it was assigned is not consecutive with the other virtual tape drives in the same library.
Restarting VLS device emulations changes the default LUN numbers as necessary to remove the
gap or to make the virtual tape drive LUN numbers consecutive in each library. This is done so
that the virtual device LUN numbering meets the operating system LUN requirements.
NOTE:
When a LUN has been unconfigured or otherwise deleted, it may still show up in the VLS
user interface. Use the VLS discovery utility to refresh the list of LUNs that are present.
Operating System LUN Requirements and Restrictions
Most operating systems require that each VLS Fibre Channel host port connected to the SAN has
a virtual device with the LUN number LUN0 and no gaps in the LUN numbering (LUN0, LUN1,
LUN2, and so on). If the operating system does not see a LUN0 on a VLS Fibre Channel host port
when it is scanning for new hardware on the SAN, it will stop looking for LUNs on that port and
90
Configuration