Log Levels and syslog Level Severities
There is a direct correlation between log levels and syslog level severities. This correlation can be used for syslog MIB reference purposes.
Log Levels
The following table defines the log levels by name and number, and provides a description of each level.
| Numerical Code | Log Level | Description |
|---|---|---|
| 1 | EMERGENCY | The most severe condition within the system which requires immediate attention. If you do not attend to it immediately, there could be physical, irreparable damage to your system. |
| 2 | CRITICAL | A serious condition within the system which requires attention as soon as it is noted. If you do not attend to these conditions immediately, there may be physical damage to your system. |
| 3 | MAJOR | Functionality has been seriously compromised. As a result, there may be loss of functionality, hanging applications, and dropped packets. If you do not attend to this situation, your system will suffer no physical harm, but it will cease to function. |
| 4 | MINOR | Functionality has been impaired to a certain degree and, as a result, you may experience compromised functionality. There will be no physical harm to your system. However, you should attend to it as soon as possible in order to keep your system operating properly. |
| 5 | WARNING | The system has noted some irregularities in its performance. This condition is used to describe situations that are noteworthy. Nonetheless, you should attend to it in order to keep your system operating properly. |
| 6
7 8 9 |
NOTICE
INFO TRACE DEBUG |
All used for Oracle customer support purposes. |
syslog Level Severities
The following table defines the syslog levels by severity and number against the University of California Berkeley Software Distribution (BSD) syslog severities (by level and number).
Refer to the Example Log Message column to view example syslog-related content/messages.
| syslog Level (Numerical Code) | BSD syslog Severity Level (Number) |
|---|---|
| EMERGENCY (1) | Emergency - system is unusable (0) |
| CRITICAL (2) | Alert - action must be taken immediately (1) |
| MAJOR (3) | Critical - critical conditions (2) |
| MINOR (4) | Error - error conditions (3) |
| WARNING (5) | Warning - warning conditions (4) |
| NOTICE (6) | Notice - normal, but significant condition (5) |
| INFO (7) | Informational - informational messages (6) |
| TRACE (8)
DEBUG (9) |
Debug - debug level messages (7) |
Mapping Trap Filter Levels to syslog and Alarm Severities
Although there is no direct correlation between system alarms and the generation of SNMP traps, traps can be mapped to syslog and alarm severities through trap filters that are configured in the filter-level field of the trap-receiver configuration element of the ACLI. The following table shows this mapping.
| filter-level Field Value | Filter Level Description | syslog Level (Numerical Code) | Alarm Severity Levels |
|---|---|---|---|
| CRITICAL | The SNMP agent sends a trap for all alarms and syslogs with a severity level that is greater than or equal to CRITICAL (with a lesser log level numerical code). The corresponding NMS receives only error events. | EMERGENCY (1)
CRITICAL (2) |
EMERGENCY
CRITICAL |
| MAJOR | The SNMP agent sends a trap for all alarms and syslogs with a severity level that is greater than or equal to MAJOR (with a lesser log level numerical code). The corresponding NMS receives warning and error events. | EMERGENCY (1)
CRITICAL (2) MAJOR (3) |
EMERGENCY
CRITICAL MAJOR |
| MINOR | The SNMP agent sends a trap for all alarms and syslogs with a severity level that is greater than or equal to MINOR (i.e., with a lesser log level numerical code) a generate a trap. The corresponding NMS receives informational, warning, and error events. | EMERGENCY (1)
CRITICAL (2) MAJOR (3) MINOR (4) |
EMERGENCY
CRITICAL MAJOR MINOR |
| ALL | The SNMP agent sends a trap for all alarms, syslogs, and other traps. The corresponding NMS receives informational, warning, and error events. | EMERGENCY (1)
CRITICAL (2) MAJOR (3) MINOR (4) WARNING (5) NOTICE (6) INFO (7) TRACE (8) DEBUG (9) |
EMERGENCY
CRITICAL MAJOR MINOR WARNING |
The following table describes the types of events that an NMS can receive.
| Event Category | Description |
|---|---|
| Error | Indicates a catastrophic condition has occurred (e.g., an internal temperature reading exceeds the recommendation). |
| Warning | Indicates pending failures or unexpected events (e.g., at the console, you typed the wrong password three consecutive times) |
| Informational | Represents non-critical conditions (e.g., an event can indicate to an administrator that a configuration element has changed). |
For more information about the filter-level field specifically or the trap-receiver element in general, refer to the Configuration via the ACLI chapter of the Administration and Configuration Guide for the ACLI.