IBM IC35L036UWDY10 Hard Drive Specifications - Page 210

Invalid LUN in Identify Message, 1.3 Incorrect Initiator Connection

Get IBM IC35L036UWDY10 - Ultrastar 36.7 GB Hard Drive PDF manuals and user guides
UPC - 000004119524
View all IBM IC35L036UWDY10 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 210 highlights

11.1.2 Invalid LUN in Identify Message There are three different circumstances defined within the SCSI protocol when the response to an invalid LUN will occur. Each of these result in a different response. 1.1.1 .1 Case 1 - Selection message sequence with Inquiry command The INQUIRY command is a special case in SCSI. It is used to configure the bus when the drive ID's and LUN's are not known. The proper response is to return the inquiry data with a peripheral drive type of 1Fh which indicates that the specified LUN is not supported. 1.1.1 .1 Case 2 - Selection message sequence with any other command Any other commands except REQUEST SENSE return CHECK CONDITION status when an invalid LUN is specified in the message sequence following selection. In response to a REQUEST SENSE command the drive shall return sense data. The sense key shall be set to ILLEGAL REQUEST and the additional sense code shall be set to LOGICAL UNIT NOT SUPPORTED. 11.1.2 .1 Case 3 - After selection message sequence It is permissible for the initiator to issue multiple IDENTIFY messages during a single command sequence provided the LUN remains the same. If the LUN is altered, the drive goes to a BUS FREE Phase. 11.1.3 Incorrect Initiator Connection Incorrect Initiator Connection error is reported if any of the following conditions occur: ! an Initiator attempts to establish an I_T_L nexus when an I/O process (either queued or active) with an I_T_L nexus already exists from a previous connection with the same initiator. ! an Initiator attempts to establish an I_T_L_Q nexus when an I/O process (either queued or active) with an I_T_L_Q nexus already exists from a previous connection with the same initiator. Note: It is not an Incorrect Initiator Connection to attempt to establish an I_T_L nexus when an I_T_L_Q nexus already exists or establish an I_T_L_Q nexus when an I_T_L nexus already exists. But when sense is pending on the logical unit for the initiator and send command is not REQUEST SENSE, INQUIRY or REPORT LUNS, sense data is cleared upon receipt of the command. If any of the above errors occur, all queued I/O processes and active I/O processes associated with the issuing Initiator on the specified logical unit are terminated. The current I/O process is ended with a CHECK CONDITION status, the sense key is set to ABORTED COMMAND, and the additional sense code is set to OVERLAPPED COMMANDS ATTEMPTED. Status is only returned for the current I/O process. 11.1.4 Command Processing during execution of active I/O process When the Target is not executing any active I/O processes, a new I/O process is permitted to execute unless execution is prevented by another internal Target condition listed in Section 11.1.1 , "Priority of SCSI Status Byte Reporting" on page 193. If an active I/O process does exist when the Target receives a new command, the Target determines how the new command should be handled based on the following rules: ! CHECK CONDITION Status is returned with Sense Key set to ABORTED COMMAND for an Incorrect Initiator Connector Condition error. See 11.1.3, "Incorrect Initiator Connection." ! the command is permitted to execute if the command is an INQUIRY, REQUEST SENSE, or REPORT LUNS command ! CHECK CONDITION Status is returned with Sense Key set to Logical Unit Not Ready if the bringup operation or format operation is an active process. Ultrastar 146Z10 hard disk drive specifications 194

  • 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
11.1.2 Invalid LUN in Identify Message
There are three different circumstances defined within the SCSI protocol when the response to an invalid
LUN will occur. Each of these result in a different response.
1.1.1 .1
Case 1 - Selection message sequence with Inquiry command
The INQUIRY command is a special case in SCSI. It is used to configure the bus when the drive ID's and
LUN's are not known. The proper response is to return the inquiry data with a peripheral drive type of 1Fh
which indicates that the specified LUN is not supported.
1.1.1 .1
Case 2 - Selection message sequence with any other command
Any other commands except REQUEST SENSE return CHECK CONDITION status when an invalid LUN
is specified in the message sequence following selection. In response to a REQUEST SENSE command
the drive shall return sense data. The sense key shall be set to ILLEGAL REQUEST and the additional
sense code shall be set to LOGICAL UNIT NOT SUPPORTED.
11.1.2 .1 Case 3 - After selection message sequence
It is permissible for the initiator to issue multiple IDENTIFY messages during a single command sequence
provided the LUN remains the same. If the LUN is altered, the drive goes to a BUS FREE Phase.
11.1.3 Incorrect Initiator Connection
Incorrect Initiator Connection error is reported if any of the following conditions occur:
!
an Initiator attempts to establish an I_T_L nexus when an I/O process (either queued or active) with
an I_T_L nexus already exists from a previous connection with the same initiator.
!
an Initiator attempts to establish an I_T_L_Q nexus when an I/O process (either queued or active)
with an I_T_L_Q nexus already exists from a previous connection with the same initiator.
Note:
It is not an Incorrect Initiator Connection to attempt to establish an I_T_L nexus when an I_T_L_Q
nexus already exists or establish an I_T_L_Q nexus when an I_T_L nexus already exists.
But when sense is pending on the logical unit for the initiator and send command is not REQUEST
SENSE, INQUIRY or REPORT LUNS, sense data is cleared upon receipt of the command
.
If any of the above errors occur, all queued I/O processes and active I/O processes associated with the
issuing Initiator on the specified logical unit are terminated. The current I/O process is ended with a
CHECK CONDITION status, the sense key is set to ABORTED COMMAND, and the additional sense
code is set to OVERLAPPED COMMANDS ATTEMPTED. Status is only returned for the current I/O
process.
11.1.4 Command Processing during execution of active I/O process
When the Target is not executing any active I/O processes, a new I/O process is permitted to execute
unless execution is prevented by another internal Target condition listed in Section 11.1.1 , “Priority of
SCSI Status Byte Reporting" on page 193.
If an active I/O process does exist when the Target receives a new command, the Target determines how
the new command should be handled based on the following rules:
!
CHECK CONDITION Status is returned with Sense Key set to ABORTED COMMAND for an Incorrect
Initiator Connector Condition error.
See 11.1.3, “Incorrect Initiator Connection.”
!
the command is permitted to execute if the command is an INQUIRY, REQUEST SENSE, or
REPORT LUNS command
!
CHECK CONDITION Status is returned with Sense Key set to Logical Unit Not Ready if the bringup
operation or format operation is an active process.
Ultrastar 146Z10 hard disk drive specifications
194