Information About System Message Logging
You can use system message logging to control the destination and to filter the severity level of messages that system processes generate. You can configure logging to terminal sessions, a log file, and syslog servers on remote systems. System message logging supports IPv4 and IPv6 addresses.
System message logging is based on RFC 3164. For more information about the system message format and the messages that the device generates, see the Cisco NX-OS System Messages Reference.
By default, the device outputs messages to terminal sessions.
The following table describes the severity levels used in system messages. When you configure the severity level, the system outputs messages at that level and lower.
Level | Description |
---|---|
0 – emergency |
System unusable |
1 – alert |
Immediate action needed |
2 – critical |
Critical condition |
3 – error |
Error condition |
4 – warning |
Warning condition |
5 – notification |
Normal but significant condition |
6 – informational |
Informational message only |
7 – debugging |
Appears during debugging only |
The device logs the most recent 100 messages of severity 0, 1, or 2.
You can configure which system messages should be logged based on the facility that generated the message and its severity level.
Syslog servers run on remote systems that are configured to log system messages based on the syslog protocol. You can configure up to three syslog servers.
Note |
When the device first initializes, messages are sent to syslog servers only after the network is initialized. |