3 – Managing Fabrics Displaying Fabric Information
S
Severity is indicated in the severity column using icons as described in Table
Table 3-2. Severity Levels
Severity | Description | |
Icon | ||
| ||
|
| |
| Alarm – An Alarm is a "serviceable event". This means that attention by | |
| the user or field service is required. Alarms are posted asynchronously | |
| to the screen and cannot be turned off. If the alarm denotes that a sys- | |
| tem error has occurred, the customer and/or field representative will | |
| generally be directed to provide a "show support" capture of the switch. | |
| Critical event – An event that indicates a potential failure. Critical log | |
| messages are events that warrant notice by the user. By default, these | |
| log messages will be posted to the screen. Critical log messages do not | |
| have alarm status as they require no immediate attention from a user or | |
| service representative. | |
| Warning event – An event that indicates errors or other conditions that | |
| may require attention to maintain maximum performance. Warning mes- | |
| sages will not be posted to the screen unless the log is configured to do | |
| so. Warning messages are not disruptive and, therefore, do not meet | |
| the criteria of Critical. The user need not be informed asynchronously. | |
No icon | Informative – An unclassified event that provides supporting informa- | |
| tion. | |
|
|
NOTE: | Events (Alarms, Critical, Warning, and Informative) generated by |
| the application are not saved on the switch. They are permanently |
| discarded when you close a SANsurfer Switch Manager session, |
| but you can save these events to a file on the workstation before |
| you close SANsurfer Switch Manager and read it later with a text |
| editor or browser. |
| Events generated by the switch, are stored on switch, and will be |
| retrieved when the application is restarted. Some alarms are |
| configurable. Refer to “Configuring Port Threshold Alarms” on |
| page |
|
