Dell TL4000 User Guide - Page 259

Appendix D. Enabling LUN support in Linux, H C I L refers to

Page 259 highlights

Appendix D. Enabling LUN support in Linux To verify the detection of a tape drive, administrators check for its entry in /proc/scsi/scsi. Current versions of Linux might not scan the logical storage unit (LUN) ID of every device. This results in some TL2000/TL4000 devices not being identified or listed in the /proc/scsi/scsi output. Administrators can follow these steps to enable support for such devices. 1. Type cat /proc/scsi/scsi. The output looks similar to: Attached devices: Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: IBM Model: ULT3580-HH3 Rev: 88M3 Type: Sequential-Access ANSI SCSI revision: 03 2. Identify the host adapter, channel number, target ID number, and LUN number for the first LUN of the device to be configured. In this example, the IBM Model ULT3580 (a drive in the TL2000/TL4000) is shown at the address, or nexus, 0 0 0 0 - which means host adapter 0, channel number 0, ID 1, and LUN 0. The TL2000/TL4000 always has the tape drive at LUN 0 and the robot at LUN 1. 3. For each LUN that must be discovered by Linux, issue the following command: echo "scsi-add-single-device H C I L">/proc/scsi/scsi H C I L refers to the nexus described in step 2. So, with the TL2000/TL4000 robot configured at LUN 1, type: echo "scsi-add-single-device 0 0 1 0">/proc/scsi/scsi. The echo command forces a scan of each device at the specific nexus. 4. Type cat /proc/scsi/scsi again to verify that all devices are now listed. The output looks similar to: Attached devices: Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: IBM Model: ULT3580-HH3 Rev: 88M3 Type: Sequential-Access ANSI SCSI revision: 03 Attached devices: Host: scsi0 Channel: 00 Id: 02 Lun: 01 Vendor: IBM Model: 3573-TL Rev: 7.10 Type: Medium Changer ANSI SCSI revision: 05 Administrators must add the echo command to the Linux boot scripts because the device information is not persistent and must be created each time that the system boots up. One example file that is used for storing the commands is /etc/rc.local. Configuring more devices on a server or a storage area network (SAN) might cause the devices to be reordered, which requires administrators to modify the commands. If the Fibre Channel adapter supports Persistent Bindings or an equivalent function, it is enabled to reduce the chance of devices that are reordered upon discovery. Note: This procedure must be run each time that the server is booted. Also, if backup application services are running (for example, they automatically start when the OS loads), they must be disabled and re-enabled after the procedure. Another way to enable LUN support is to recompile the kernel and enable LUN scanning in the Adaptec driver, but it requires advanced knowledge of Linux and is not covered here. However, it allows the server to always boot and see the device without any manual procedures. © Copyright IBM Corp. 2007, 2013 D-1

  • 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
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296

Appendix D. Enabling LUN support in Linux
To verify the detection of a tape drive, administrators check for its entry in
/proc/scsi/scsi
. Current versions of Linux might not scan the logical storage unit
(LUN) ID of every device. This results in some TL2000/TL4000 devices not being
identified or listed in the /proc/scsi/scsi output. Administrators can follow these
steps to enable support for such devices.
1.
Type
cat /proc/scsi/scsi
. The output looks similar to:
Attached devices:
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor:
IBM Model: ULT3580-HH3
Rev: 88M3
Type:
Sequential-Access
ANSI SCSI revision: 03
2.
Identify the host adapter, channel number, target ID number, and LUN number
for the first LUN of the device to be configured. In this example, the IBM
Model ULT3580 (a drive in the TL2000/TL4000) is shown at the address, or
nexus, 0 0 0 0 - which means host adapter 0, channel number 0, ID 1, and LUN
0. The TL2000/TL4000 always has the tape drive at LUN 0 and the robot at
LUN 1.
3.
For each LUN that must be discovered by Linux, issue the following command:
echo "scsi-add-single-device H C I L">/proc/scsi/scsi
H C I L refers to the
nexus described in step 2. So, with the TL2000/TL4000 robot configured at
LUN 1, type:
echo "scsi-add-single-device 0 0 1 0">/proc/scsi/scsi
. The
echo command forces a scan of each device at the specific nexus.
4.
Type
cat /proc/scsi/scsi
again to verify that all devices are now listed. The
output looks similar to:
Attached devices:
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor:
IBM Model: ULT3580-HH3
Rev: 88M3
Type:
Sequential-Access
ANSI SCSI revision: 03
Attached devices:
Host: scsi0 Channel: 00 Id: 02 Lun: 01
Vendor:
IBM Model: 3573-TL
Rev: 7.10
Type:
Medium Changer ANSI SCSI revision: 05
Administrators must add the echo command to the Linux boot scripts because
the device information is not persistent and must be created each time that the
system boots up. One example file that is used for storing the commands is
/etc/rc.local. Configuring more devices on a server or a storage area network
(SAN) might cause the devices to be reordered, which requires administrators
to modify the commands. If the Fibre Channel adapter supports Persistent
Bindings or an equivalent function, it is enabled to reduce the chance of devices
that are reordered upon discovery.
Note:
This procedure must be run each time that the server is booted. Also, if
backup application services are running (for example, they automatically
start when the OS loads), they must be disabled and re-enabled after the
procedure.
Another way to enable LUN support is to recompile the kernel and enable
LUN scanning in the Adaptec driver, but it requires advanced knowledge of
Linux and is not covered here. However, it allows the server to always boot
and see the device without any manual procedures.
© Copyright IBM Corp. 2007, 2013
D-1