User’s Manual of
The Global Log Parameters page contains fields for enabling logs globally, and fields for defining log parameters. The Severity log messages are listed from the highest severity to the lowest.
Event messages have a unique format, as per the SYSLOG RFC recommended message format for all error reporting. For example, Syslog+ local device reporting. Messages are assigned a severity code, and include a message mnemonic, which identifies the source application generating the message. Messages are filtered based on their urgency or relevancy. The severity of each message determines the set of event logging devices to which are sent for each event logging device. The following table contains the Log Severity Levels:
Severity Type | Severity | Description | Example |
| Level |
|
|
|
|
|
|
Emergency | 0 | The system is not functioning. | Memories overflow. |
|
|
|
|
Alert | 1 | The system needs immediate | Main system memory |
|
| attention. | pool overflow. |
|
|
|
|
Critical | 2 | The system is in a critical state. | Cannot bind to SNMP. |
|
|
|
|
Error | 3 | A system error has occurred. | Failed to delete entry. |
|
|
|
|
Warning | 4 | A system warning has occurred. | Port down. |
|
|
|
|
Notice | 5 | The system is functioning properly, | Bad route. |
|
| but system notice has occurred. |
|
|
|
|
|
Informational | 6 | Provides device information. | Link up. |
|
|
|
|
Debug | 7 | Provides detailed information about | Method list created. |
|
| the log. If a Debug error occurs, |
|
|
| contact Dell Online Technical Support |
|
|
|
|
|
The Server Logs screen (see figure
- 149 –