SCSI Primary Commands - 2.pdf

More documents

Recommendations

Info

T10/1236-D Revision 20 18 July 20018.3.8 Informational exceptions control pageThe informational exceptions control page (see table 161) defines the methods used by the target to control thereporting and the operations of specific informational exception conditions. This page shall only apply to informationalexceptions that report an additional sense code of FAILURE PREDICTION THRESHOLD EXCEEDED orWARNING to the application client.Informational exception conditions occur as the result of vendor specific events within a target. An informationalexception condition may occur asynchronous to any commands issued by an application client.Table 161 — Informational exceptions control pageBitByte7 6 5 4 3 2 1 00 PS Reserved PAGE CODE (1Ch)1 PAGE LENGTH (0Ah)2 PERF Reserved EBF EWASC DEXCPT TEST Reserved LOGERR3 Reserved MRIE4 (MSB)INTERVAL TIMER7 (LSB)8 (MSB)REPORT COUNT11 (LSB)The log errors bit (LOGERR) of zero indicates that the logging of informational exception conditions by a deviceserver is vendor specific. A LOGERR bit of one indicates the device server shall log informational exception conditions.A TEST bit of one shall create a test device failure at the next interval time, as specified by the INTERVAL TIMER field,if the DEXCPT bit is set to zero. When the TEST bit is one, the MRIE and REPORT COUNT fields shall apply as if theTEST bit were zero. The test device failure shall be reported with an additional sense code of FAILUREPREDICTION THRESHOLD EXCEEDED (FALSE). If both the TEST and the DEXCPT bits are one, the deviceserver shall terminate the MODE SELECT command with CHECK CONDITION status. The sense key shall be setto ILLEGAL REQUEST with the additional sense code set to INVALID FIELD IN PARAMETER LIST. A TEST bit ofzero shall instruct the device server not to generate any test device failure notifications.A disable exception control (DEXCPT) bit of zero indicates the failure prediction threshold exceeded reporting shallbe enabled. The method for reporting the failure prediction threshold exceeded when the DEXCPT bit is set to zerois determined from the MRIE field. A DEXCPT bit of one indicates the target shall disable reporting of the failureprediction threshold exceeded. The MRIE field is ignored when DEXCPT is set to one and EWASC is set to zero.An enable warning (EWASC) bit of zero indicates the target shall disable reporting of the warning. The MRIE field isignored when DEXCPT is set to one and EWASC is set to zero. An EWASC bit of one indicates warning reportingshall be enabled. The method for reporting the warning when the EWASC bit is set to one is determined from theMRIE field.If background functions are supported, an Enable Background Function (EBF) bit of one indicates the target shallenable background functions. An EBF bit of zero indicates the target shall disable the functions.202 dpANS SCSI Primary Commands - 2 (SPC-2)
18 July 2001 T10/1236-D Revision 20For the purposes of the EBF bit, background functions are defined as idle time functions that may impact performancethat are performed by a target operating without errors but do not impact the reliability of the target (e.g.,read scan).A performance (PERF) bit of zero indicates that informational exception operations that are the cause of delays areacceptable. A PERF bit of one indicates the device server shall not cause delays while doing informational exceptionoperations. A PERF bit set to one may cause the device server to disable some or all of the informational exceptionsoperations, thereby limiting the reporting of informational exception conditions.The method of reporting informational exceptions field (MRIE) indicates the methods that shall be used by thedevice server to report informational exception conditions (see table 162). The priority of reporting multiple informationexceptions is vendor specific.Table 162 — Method of reporting informational exceptions (MRIE) field (part 1 of 2)MRIE0h1h2h3hDescriptionNo reporting of informational exception condition: This method instructs the device serverto not report information exception conditions.Asynchronous event reporting: This method instructs the device server to report informationalexception conditions by using the rules for asynchronous event reporting as describedin SAM-2 and the relevant protocol standard.The sense key shall be set to RECOVERED ERROR and the additional sense code shall indicatethe cause of the informational exception condition.Generate unit attention: This method instructs the device server to report informational exceptionconditions by returning a CHECK CONDITION status. The sense key shall be set to UNITATTENTION and the additional sense code shall indicate the cause of the informational exceptioncondition.The command that has the CHECK CONDITION shall not be executed before the informationalexception condition is reported.Conditionally generate recovered error: This method instructs the device server to reportinformational exception conditions, if the reporting of recovered errors is allowed, by returning aCHECK CONDITION status. If the TEST bit equals zero, the status may be returned on any commandafter the informational exception condition occurs. If the TEST bit equals one, the statusshall be returned on the next command that is normally capable of returning an informationalexception condition when the TEST bit equals zero. The sense key shall be set to RECOVEREDERROR and the additional sense code shall indicate the cause of the informational exceptioncondition.A command that has the CHECK CONDITION shall complete without error before any informationalexception condition may be reported.dpANS SCSI Primary Commands - 2 (SPC-2) 203
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:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
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: T10/1236-D Revision 20 18 July 2001
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?