This example shows Syslog informational messages, displayed with the show logging buffer command. It indicates that messages were generated by facility code 16 (local4) at severity level 5 from the CLI application on IP address 10.42.71.13.
System(rw)->show logging buffer <165>Sep 4 07:43:09 10.42.71.13 CLI[5]User:rw logged in from 10.2.1.122 (telnet) <165>Sep 4 07:43:24 10.42.71.13 CLI[5]User: debug failed login from 10.4.1.100 (telnet)
Syslog Message Components describes the components of these messages.
Syslog Message Components
| Component | Description | Example Code |
|---|---|---|
| Facility/Severity | Combined code indicating the facility generating the message and the severity level used to determine message priority. Facility codes 16 - 23 are Syslog designations for local0 - local7, the Extreme Networks supported designations for local use. For a complete list of facility codes, refer to RFC 3164. | <165> = Numerical code indicating a message from facility local4 at severity 5. |
| Time stamp | Month, date, and time the Syslog message appeared. | Sep 4 07:43:09 |
| Address | IP address of the client originating the Syslog message. | 10.42.71.13 |
| Application | Client process generating the Syslog message. | CLI |
| Slot/Module | Slot location of the device module generating the Syslog message. | (5) = Slot 5 in the chassis. |
| Message text | Brief description of error condition. | User: debug failed login from 10.4.1.100 (telnet) |
Print
this page
Email this topic
Feedback
View PDF
Download EPUB