Logs
TBD (current GUI not shown up)
Last updated
TBD (current GUI not shown up)
Last updated
The Syslog protocol allows devices to send event notification messages in response to events, faults, or errors occurring on the platform as well as changes in configuration or other occurrences across an IP network to syslog servers. It then collects the event messages, providing powerful support for users to monitor network operations and diagnose malfunctions. A Syslog-enabled device can generate a syslog message and send it to a Syslog server.
Syslog is defined in RFC 3164. The RFC defines the packet format, content, and system log related information of Syslog messages. Each Syslog message has a facility and severity level. The Syslog facility identifies a file in the Syslog server. Refer to the documentation of your Syslog program for details.
From here, you can select "Enabled or "Disabled" for the log settings of the switch.
Click the Apply button to apply the changes or the Reset button to discard them.
The following table describes the Syslog severity levels.
Click the Edit button to apply the changes in RAM or Flash target, respectively.
The internal log of the ECS switch has a fixed capacity; at a certain level, the ECS switch will start deleting the oldest entries to make room for the newest. If you want a permanent record of all logging activities, you can set up your syslog server to receive log content from the ECS switch. Use this page to direct all logging to the syslog server. Click the Add button, define your syslog server, and select the severity level of events you wish to log.
Click the Add button to add the remote server for syslog logging:
This page displays the most recent records in the switch's internal log. Log entries are listed in reverse chronological order (with the latest logs at the top of the list). Click a column header to sort the content by that category.
RAM: The information stored in the system’s RAM log will be lost after the switch is rebooted or powered off.
Flash: The information stored in the system’s Flash will be kept effective even if the switch is rebooted or powered off.
Click the Download button to export the current buffered log to a .txt file.
Click the Clear button to clear the buffered log in the system's memory.
Click the Apply button to accept the changes or the Cancel button to discard them.
Click the Apply button to accept the changes or the Cancel button to discard them.
Code
Severity
Description
General Description
0
EMERG
System is unusable.
A "panic" condition usually affecting multiple apps/servers/sites. At this level, all tech staff on call would be notified.
1
ALERT
Action must be taken immediately.
Should be corrected immediately. Therefore, notify staff who can fix the problem. An example would be the loss of a primary ISP connection.
2
CRIT
Critical conditions.
Should be corrected immediately but indicates failure in a secondary system; an example is a loss of a backup ISP connection.
3
ERROR
Error conditions.
Non-urgent failures, which should be relayed to developers or admins; each item must be resolved within a given time.
4
WARNING
Warning conditions.
Warning messages, not an error, but indication that an error will occur if action is not taken (e.g. file system 85% full). Each item must be resolved within a given time.
5
NOTICE
Normal but significant condition.
Events that are unusual but not error conditions - might be summarized in an email to developers or admins to spot potential problems - no immediate action required.
6
INFO
Informational messages
Normal operational messages - may be harvested for reporting, measuring throughput, etc. - no action required.
7
DEBUG
Debug messages
Messages that contain information for debugging purpose.
