HP StorageWorks 4/64 Brocade Fabric OS Message Reference v6.3.0 (53-1001338-01 - Page 81
Message Severity Levels, Responding to a System Message
View all HP StorageWorks 4/64 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 81 highlights
Responding to a System Message 1 TABLE 4 Example Audit Message Field Description (Continued) Variable Name Description switchname , , Slot 7 ejector not closed Switch name or chassis name, depending on the action; for example, HA messages typically show the chassis name and login failures show the logical switch name. The defined switch name or the chassis name of the switch. This value is truncated if it is over 16 characters in length. Run either the chassisName command to name the chassis or the switchName command to rename the logical switch. Null Reserved for future use. Error Description A text string explaining the error encountered and providing parameters supplied by the software at runtime. Message Severity Levels There are four levels of severity for messages, ranging from Critical (1) to Info (4). In general, the definitions are wide ranging and are to be used as general guidelines for troubleshooting. For all cases, you should look at each specific error message description thoroughly before taking action. System messages have the following severity levels. 1 = CRITICAL 2 = ERROR 3 = WARNING 4 = INFO Critical-level messages indicate that the software has detected serious problems that will cause a partial or complete failure of a subsystem if not corrected immediately; for example, a power supply failure or rise in temperature must receive immediate attention. Error-level messages represent an error condition that does not impact overall system functionality significantly. For example, error-level messages might indicate time-outs on certain operations, failures of certain operations after retries, invalid parameters, or failure to perform a requested operation. Warning-level messages highlight a current operating condition that should be checked or it might lead to a failure in the future. For example, a power supply failure in a redundant system relays a warning that the system is no longer operating in redundant mode unless the failed power supply is replaced or fixed. Info-level messages report the current non-error status of the system components: for example, detecting online and offline status of a fabric port. Responding to a System Message This section provides procedures on gathering information on system messages, including: • Looking Up a System Message • Gathering Information About the Problem • Support • Panic Dump and Core Dump Files • Trace Dumps • supportSave Command Fabric OS Message Reference 11 53-1001338-01