Legal Information |
Error message coding conventionsHow to determine error message typeWhen a diagnostic test encounters an error, the diagnostic tool generates an error message. The type of message that is generated and displayed on your console helps you determine what failed during the diagnostic test. Error messages are composed of four components. The alphabetic portion of the error message code helps you identify the system generating the error, the module generating the error, and the type of error encountered. The numeric portion of the error code uniquely identifies the error for the module reporting the error. The numeric identifier is followed by a colon and the error message text. The following is an example of error message syntax. Example: "SMTnnnn: The XYZ card failed to reset" System codeThe system code identifies the kernel for which the error is generated. The types of system codes are shown in the following table.
Module codeThe module code identifies the software driver, hardware adapter, or firmware for which the error is generated. Typically, the hardware error messages generated by the diagnostic tool are associated with the diagnostic kernel system code. Also generated by the diagnostics are Data ONTAP kernel and firmware error messages. Only the diagnostic kernel messages are documented in this section. The types of diagnostic kernel module codes are shown in the following table.
Type codeThe last letter of the error message code identifies the probable error type; what caused the error to be generated. The types of probable type codes are shown in the following table.
Message variable conventionsIn the online message text, you see values displayed for conditions found on the system. These values change as conditions in the system change. In error messages in this guide, these values are displayed in italics. The following table illustrates this convention.
|