System Log
Last updated
Last updated
From here, you can Enable or Disable the Log settings for the EWS switch.
The System Log is designed to monitor the operation of the EWS switch by recording the event messages it generates during normal operation. These events may provide vital information about system activity that can assist in the identification and solutions of system problems.
The EWS switch supports log output to two repositories: Flash and RAM. The information stored in the system’s RAM log will be lost after the switch is rebooted or powered off, whereas the information stored in the system’s Flash will be kept even after the switch is rebooted or powered off. The flash repository has a fixed capacity; at a certain level, the EWS switch will start deleting the oldest entries to make room for the newest.
Severity Level
RFC 5424 defines eight severity levels:
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 | This should be corrected immediately; please notify staff who can fix the problem. |
2 | CRIT | Critical conditions | This should be corrected immediately; please notify staff who can fix the problem. |
3 | ERROR | Error conditions | Non-urgent failures, these 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. |
The internal log of the EWS switch has a fixed capacity; at a certain level, the EWS 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 contents from the EWS 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.
Items | Descriptions |
IP/Hostname | Specify the IP address or host name of syslog server |
Server Port | Specify the port of the syslog server. The default port is 514. |
Severity Level | RFC 5424 defines eight severity levels: |
Facility | The log facility is used to separate out log messages by application or by function, allowing you to send logs to different files in the syslog server. Use the drop-down menu to select local0, local1, local2, local3, local4, local5, local6, or local7. |
This page displays the most recent records in the EWS 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 contents 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 even after the switch is rebooted or powered off. |
Controller | Display controller related logs. |
Switch | Display switch related logs. |
Wireless Client | Display wireless client activities from managed APs. |
All | Display logs from both controller and switch |
Export Click Export button to export the current buffered log to a .txt file.
Clear Click Clear button to clear the buffered log in the system's memory.
