PDF(19.9 KB) View with Adobe Reader on a variety of devices
ePub(58.4 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(94.4 KB) View on Kindle device or Kindle app on multiple devices
Updated:December 11, 2018
System Log Settings on ESW2-550X Switch
A system log is a set of messages that describes system events. Each system event has different severity levels. The logs can be saved locally on the RAM, flash memory of the device.
Note: Refer the article Remote Log Server Configuration to save the logs remotely.
This article explains how to save the logs locally on the ESW2-550X stackable managed switch.
• ESW2-550X • ESW2-550X-DC
System Log Settings
Step 1. Log in to the switch configuration utility and choose Administration > System Log > Log Settings. The Log Settings page opens:
Step 2. Check the Enable check box in the Logging field to enable message logging.
Step 3. The Syslog Aggregator option is used if identical and contiguous syslog messages and the trap messages are to be aggregated over a period of time and to be sent as a single message. Check the Enable check box in the Syslog Aggregator field to enable the feature.
Note: If Syslog Aggregator is enabled, proceed with Step 4, else skip Step 5.
Step 4. Enter the time interval that the syslog messages and traps are aggregated in the Max Aggregation Time field.
Logs can be saved in the following memory location on the system.
• RAM — It is a volatile memory and is very fast.
• Flash — It is a non-volatile memory and is slow when compared to RAM.
Step 5. Check the desired severity level event check boxes under the RAM and Flash Memory Logging area. A log is created on the RAM and Flash that contains messages from the checked events. The following are the event severity levels which are listed from the highest severity to the lowest severity.
• Emergency — System is not usable. Example: At a panic situation where the multiple servers are down, a log with emergency severity level helps to notify the technical person immediately.
• Alert — Action is needed. Example: Loss of primary ISP connection.
• Critical — System is in a critical condition. Example: Loss of backup ISP connection.
• Error — System is in error condition. Example: Non - urgent failures where the failures need to be addressed by the developer or administrators.
• Warning — A system warning has occurred. Example: File system is 95% full.
• Notice — System is functioning properly, but a system notice has occurred. Example: Events that occur unusually.
• Informational — Device Information. Example: Information for measuring throughput.
• Debug — Provides detailed information about an event. Example: Information for the events where the issue occurred at.