Switch Manager
2
1
1 Severity column | 2 Column sorting buttons |
Figure 13: Event Browser
Note:
■Events that are generated by the application are not saved on the switch. They are permanently discarded when you close a Switch Manager session, but you can save these events to a file on the workstation before closing Switch Manager and can read it later with a text editor or browser.
■Events that are generated by the switch are stored on the switch, and retrieved when the application is restarted. Some alarms are configurable. See “Configuring port threshold alarms” on page 66.
Table 7: Event severity levels
Severity Icon | Description |
| |
| attention by the user or field service is required. Alarms are events that get |
| posted asynchronously to the screen. Alarms cannot be turned off. If the alarm |
| denotes that a system error has occurred, the customer or field representative |
| will be directed to provide a “show support” capture of the switch. |
|
|
| Critical |
| indicates a potential failure. Critical log messages are events that warrant |
| notice by the user. By default, these log messages are posted to the screen. |
| Critical log messages do not have alarm status because they require no |
| immediate attention from a user or service representative. |
|
|
| Warning |
| indicates errors or other conditions that may require attention to maintain |
| maximum performance. Warning messages are not 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 | application that provides supporting information. |
| |
|
|