HP StorageWorks 300 HP StorageWorks 300 Virtual Library System user guide (AH1 - Page 69

Default LUN numbering, Operating system LUN requirements and restrictions, LUN masking

Get HP StorageWorks 300 - Virtual Library System EVA Gateway PDF manuals and user guides View all HP StorageWorks 300 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 69 highlights

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 FC host port (LUN1, LUN2 and so on). The first virtual device port mapped to any of the FC host ports is assigned the LUN number LUN0. The second virtual device port mapped to an FC host port is assigned the LUN number LUN1, and so on. The default LUN numbers are changed by the VLS software 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 FC 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 FC host port when it is scanning for new hardware on the SAN, it will stop looking for LUNs on that port and erroneously report that there are no LUNs (virtual devices) on that port. If the operating system sees a LUN0, LUN1, and LUN2 but not a LUN3 on the port, it will stop looking for LUNs on that port when the gap in the LUN numbering is encountered. Even though there may be more LUNs (such as LUN4), the operating system will erroneously report that there are only three LUNs on the port. In addition, operating systems are configured to only look for a maximum number of LUNs per device and no more. Once the maximum number of LUNs is detected, the operating system stops looking. In the case of the VLS, the operating system considers each FC host port to be one device with its own set of LUNs. So, if the maximum number of LUNs an operating system is configured to see is eight, the operating system will only see LUN0, LUN1, ..., LUN7 and will not see LUN8, LUN9, ..., and up on each FC host port. To get around the maximum LUNs per device restriction, you can either: • Increase the maximum LUNs per device setting for the operating system. See Troubleshooting for more information. • Use the VLS's LUN masking feature to restrict the number of virtual devices the host's operating system sees on the VLS FC host port(s). Then, use the VLS's LUN mapping feature to assign LUNs to the virtual devices the host can see, such that the LUN numbers on each FC host port include a LUN0 and no gaps in the LUN numbering. See LUN masking and LUN mapping for instructions. LUN masking By default all hosts on the SAN can access all the virtual libraries on the VLS. You can restrict a host's access to the virtual libraries and/or tape drives (virtual devices) on the VLS by performing LUN masking. LUN masking should also be used when there are more virtual devices (LUNs) port mapped to a FC host port than the operating system LUN restrictions support. This prevents the host's operating system from seeing the virtual devices it needs to see on the port. For example, if a host's operating system is configured to only see up to eight LUNs per FC host port, the host will not be able to see the virtual HP StorageWorks 69

  • 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
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 FC host port (LUN1, LUN2 and so on).
The
fi
rst virtual device port mapped to any of the FC host ports is assigned the LUN number LUN0. The
second virtual device port mapped to an FC host port is assigned the LUN number LUN1, and so on.
The default LUN numbers are changed by the VLS software 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 uncon
fi
gured 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 FC 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 FC host port when it is scanning for new hardware
on the SAN, it will stop looking for LUNs on that port and erroneously report that there are no LUNs
(virtual devices) on that port. If the operating system sees a LUN0, LUN1, and LUN2 but not a LUN3 on
the port, it will stop looking for LUNs on that port when the gap in the LUN numbering is encountered.
Even though there may be more LUNs (such as LUN4), the operating system will erroneously report that
there are only three LUNs on the port.
In addition, operating systems are con
fi
gured to only look for a maximum number of LUNs per device and
no more. Once the maximum number of LUNs is detected, the operating system stops looking. In the case
of the VLS, the operating system considers each FC host port to be one device with its own set of LUNs.
So, if the maximum number of LUNs an operating system is con
fi
gured to see is eight, the operating system
will only see LUN0, LUN1, ..., LUN7 and will not see LUN8, LUN9, ..., and up on each FC host port.
To get around the maximum LUNs per device restriction, you can either:
•
Increase the maximum LUNs per device setting for the operating system. See
Troubleshooting
for more information.
•
Use the VLS’s LUN masking feature to restrict the number of virtual devices the host’s operating
system sees on the VLS FC host port(s). Then, use the VLS’s LUN mapping feature to assign LUNs
to the virtual devices the host can see, such that the LUN numbers on each FC host port include a
LUN0 and no gaps in the LUN numbering. See
LUN masking
and
LUN mapping
for instructions.
LUN masking
By default all hosts on the SAN can access all the virtual libraries on the VLS. You can restrict a host’s
access to the virtual libraries and/or tape drives (virtual devices) on the VLS by performing LUN masking.
LUN masking should also be used when there are more virtual devices (LUNs) port mapped to a FC
host port than the operating system LUN restrictions support. This prevents the host’s operating system
from seeing the virtual devices it needs to see on the port. For example, if a host’s operating system is
con
fi
gured to only see up to eight LUNs per FC host port, the host will not be able to see the virtual
HP StorageWorks
69