HP Surestore Tape Library Model 10/180 HP Surestore Bridge FC 2/1 LV and FC 4/ - Page 230

SCC Addressing Option, The host can perform discovery by either walking through the bus:target:LUN

Page 230 highlights

SCC Addressing Option When a bridge is configured to use SCC addressing, the unit is capable of responding as a controller device to the FCP initiator or routing the FCP request to a specified bus:target:LUN. When a request using the peripheral device addressing method is received (an FCP command with the LUN field with bits 7 and 6 of byte 9 are set to 0), the unit routes the request to the internal processor, which acts on the command directly. When a request using the logical unit addressing method is received (bits 7 and 6 set to 10b), the request is routed to the bus:target:LUN as specified in the defined field. Host systems using SCC addressing will typically do initial device discovery using the peripheral device addressing method. On issuing an INQUIRY command to the bridge, the host will receive the bridge inquiry data, indicating the device type as a controller device (inquiry data indicated device type is 0xC). The host will then know that subsequent commands to the bridge attached devices will use the logical unit addressing method. The host can perform discovery by either walking through the bus:target:LUN values as would a standard SCSI driver, or by issuing a report LUNS command. This command is sent to the bridge (using the peripheral device addressing method), and the bridge returns a table indicating attached devices. The host can then perform actions on these bridge attached devices directly without having to perform discovery by issuing commands through all possible combinations. 232 SCC Addressing Option Appendix C

  • 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

232
SCC Addressing Option
Appendix C
SCC Addressing Option
When a bridge is configured to use SCC addressing, the unit is capable of
responding as a controller device to the FCP initiator or routing the FCP
request to a specified bus:target:LUN. When a request using the peripheral
device addressing method is received (an FCP command with the LUN field
with bits 7 and 6 of byte 9 are set to 0), the unit routes the request to the
internal processor, which acts on the command directly. When a request using
the logical unit addressing method is received (bits 7 and 6 set to 10b), the
request is routed to the bus:target:LUN as specified in the defined field.
Host systems using SCC addressing will typically do initial device discovery
using the peripheral device addressing method. On issuing an
INQUIRY
command to the bridge, the host will receive the bridge inquiry data,
indicating the device type as a controller device (inquiry data indicated device
type is 0xC). The host will then know that subsequent commands to the bridge
attached devices will use the logical unit addressing method.
The host can perform discovery by either walking through the bus:target:LUN
values as would a standard SCSI driver, or by issuing a report LUNS
command. This command is sent to the bridge (using the peripheral device
addressing method), and the bridge returns a table indicating attached
devices. The host can then perform actions on these bridge attached devices
directly without having to perform discovery by issuing commands through all
possible combinations.