SCSI Primary Commands - 2.pdf

More documents

Recommendations

Info

T10/1236-D Revision 20 18 July 2001abTable 48 — Peripheral device type (part 2 of 2)Code Doc. a Description12h - 1EhReserved1FhUnknown or no device typeAll standards are subject to revision, and parties to agreements based on thisstandard are encouraged to investigate the possibility of applying the most recenteditions of the listed standards.Type code 10h is reserved for use by Bridging Expanders.A removable medium (RMB) bit of zero indicates that the medium is not removable. A RMB bit of one indicates thatthe medium is removable.The VERSION field indicates the implemented version of this standard and is defined in table 49.Table 49 — VersionCode Description00h The device does not claim conformance to any standard.02h The device complies to ANSI X3.131:1994.03h The device complies to ANSI X3.301:1997.04h The device complies to this standard.80h The device complies to ISO/IEC 9316:1995.82h The device complies to ISO/IEC 9316:1995 and to ANSI X3.131:1994.83h The device complies to ISO/IEC 9316:1995 and to ANSI X3.301:1997.84h The device complies to ISO/IEC 9316:1995 and to this standard.Code Description Code Description1h Obsolete (SCSI=001b) 5h - 7h Reserved08h - 0Ch Obsolete (ECMA=001b) 0Dh - 3Fh Reserved40h - 44h Obsolete (ISO=01b) 45h - 47h Reserved48h - 4Ch Obsolete (ISO=01b & ECMA=001b) 4Dh - 7Fh Reserved81h Obsolete (SCSI=001b) 85h - 87h Reserved88h - 8Ch Obsolete (ECMA=001b) 8Dh - FFh ReservedANSI X3.131:1994 is SCSI-2ISO/IEC 9316:1995 is SCSI-2ANSI X3.301:1997 is SPCThe asynchronous event reporting capability (AERC) bit indicates that the target supports the asynchronous eventreporting capability as defined in SAM-2. The AERC bit is qualified by the PERIPHERAL DEVICE TYPE field as follows:a) Processor device-type definition: An AERC bit of one indicates that the processor device is capable ofaccepting asynchronous event reports. An AERC bit of zero indicates that the processor device does notsupport asynchronous event reports; orb) All other device-types: This bit is reserved.Details of the asynchronous event reporting support are protocol specific.84 dpANS SCSI Primary Commands - 2 (SPC-2)
18 July 2001 T10/1236-D Revision 20The Normal ACA Supported bit (NORMACA) of one indicates that the device server supports setting the NACA bit toone in the CONTROL byte of the CDB (see SAM-2). A NORMACA bit of zero indicates that the device server does notsupport setting the NACA bit to one.A hierarchical support (HISUP) bit of zero indicates the target does not use the hierarchical addressing model toassign LUNs to logical units. A HISUP bit of one indicates the target uses the hierarchical addressing model toassign LUNs to logical units. When the HISUP bit is one, the device server shall support the REPORT LUNScommand (see 7.19). When the HISUP bit is zero, the device server may support the REPORT LUNS command.A RESPONSE DATA FORMAT field value of two indicates that the data shall be in the format specified in this standard.Response data format values less than two are obsolete. Response data format values greater than two arereserved.The ADDITIONAL LENGTH field shall specify the length in bytes of the parameters. If the ALLOCATION LENGTH of theCDB is too small to transfer all of the parameters, the ADDITIONAL LENGTH shall not be adjusted to reflect thetruncation.An SCC Supported (SCCS) bit of one indicates that the device contains an embedded storage array controllercomponent. See SCC-2 for details about storage array controller devices. An SCCS bit of zero indicates that thedevice does not contain an embedded storage array controller component.The basic queuing (BQUE) bit shall be zero if the CMDQUE bit is one.When the CMDQUE bit is zero, the BQUE bit shall have the following meaning. A BQUE bit of zero indicates that thedevice does not support tagged tasks (command queuing) for this logical unit. A value of one indicates that thedevice supports, for this logical unit, the basic task management model defined by SAM-2.An Enclosure Services (ENCSERV) bit of one indicates that the device contains an embedded enclosure servicescomponent. See SES for details about enclosure services, including a device model for an embedded enclosureservices device. An ENCSERV bit of zero indicates that the device does not contain an embedded enclosureservices component.A Multi Port (MULTIP) bit of one indicates that this is a multi-port (two or more ports) device and conforms to theSCSI multi-port device requirements found in the applicable standards (e.g., SAM-2, a protocol standard andpossibly provisions of a command set standard). A value of zero indicates that this device has a single port anddoes not implement the multi-port requirements.A medium changer (MCHNGR) bit of one indicates that the device is associated with or attached to a mediumtransport element. See SMC for details about medium changers, including a device model for an attached mediumchanger device. The MCHNGR bit is valid only when the RMB bit is equal to one. A MCHNGR bit of zero indicates thatthe device is not embedded within or attached to a medium transport element.A relative addressing (RELADR) bit of one indicates that the device server supports the relative addressing mode. Ifthis bit is set to one, the linked command (LINKED) bit shall also be set to one; since relative addressing is onlyallowed with linked commands. A RELADR bit of zero indicates the device server does not support relativeaddressing.A linked command (LINKED) bit of one indicates that the device server supports linked commands (see SAM-2). Avalue of zero indicates the device server does not support linked commands.dpANS SCSI Primary Commands - 2 (SPC-2) 85
Page 1 and 2:
dpANSProjectT10/1236-DRevision 2018
Page 3:
DraftANSI (r)NCITS.351:200xAmerican
Page 6 and 7:
T10/1236-D Revision 20 18 July 2001
Page 8 and 9:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53: T10/1236-D Revision 20 18 July 2001
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
show all

SCSI Primary Commands - 2.pdf

Create successful ePaper yourself

Delete template?

Save as template?