Configuration choices for a cisco switch syslog
View PDF | Print View
by: Admin
Total views: 229
Word Count: 315
A cisco switch syslog works in a similar manner to any of a variety of other logging systems. As the switch operates, the cisco switch syslog is populated with entries based on the logging level configured by default, unless you have reconfigured the switch to log data differently. The log service can be reconfigured in such a way to specify which events are written to the cisco switch syslog. There are different severity levels to all loggable events, and you can specify the severity level by which a log event is generated.
This configuration might be modified in cases where you wanted to look for certain types of log events. Or, you might wish to log only the more critical events and ignore non critical, informational log entries to keep the log size either smaller or easier to review. In a setup where you do not use a syslog server and have to examine the cisco switch syslog yourself, you might want to keep it cleaner unless you are looking for something specific from a less important event.
A cisco switch syslog is stored internally on the switch device using volatile memory. This memory space for the cisco switch syslog is limited, and due to the volatility, would be lost if you were to power cycle the switch or lose power. Either way, once the switch is offline, the cisco switch syslog is lost. Which is why it may be a good idea to look into using a syslog server. That way, the cisco switch syslog is exported to a remote computer that can store it in a more permanent manner. However, cisco switch syslog data may not be considered critical to keep long term and is often only used to troubleshoot acute problem. In that case, the internal cisco switch syslog storage will probably suffice.
About the Author
Information on juniper syslog, try sysloganalyzer.com.
Rating: Not yet rated