Manualshelf

Users Guide

ManualsBrandsDell ManualsAccess PlatformsW-Series Controller AOS
851852853854855856857858859860
Table Of Contents
Logging Level Description
Emergency Panic conditions that occur when the system becomes unusable.
Alert Any condition requiring immediate attention and correction.
Critical Any critical conditions such as a hard drive error.
Errors Error conditions.
Warning Warning messages.
Notice Significant events of a non-critical and normal nature.
Informational Messages of general interest to system users.
Debug Messages containing information useful for debugging.
Table 193: Logging Levels
The default logging level for all categories is Warning. You can also configure IP address of a syslog server to
which the controller can direct these logs.
In the WebUI
1. Navigate to the Configuration > Management > Logging > Servers page.
2. To add a logging server, click New in the Logging Servers section.
3. Click Add to add the logging server to the list of logging servers. Ensure that the syslog server is enabled and
configured on this host. Click Apply.
4. To select the types of messages you want to log, select the Levels tab.
5. Select the category or subcategory to be logged.
6. To select the severity level for the category or subcategory, scroll to the bottom of the page. Select the level
from the Logging Level drop-down menu. Click Done.
7. Click Apply to apply the configuration.
In the CLI
logging <ipaddr>
logging level <level> <category> [subcat <subcategory>]
Syslog operates over UDP and is connectionless. Therefore, it is not possible for the controller to recognize a
failure of the syslog server or the network path to the syslog server. By establishing an IPsec tunnel between
the controller and the syslog server, (see
Planning a VPN Configuration) it is possible to indirectly track the
status of the syslog server link.
After a failure occurs, the network administrator has to manually re-synchronize log files by copying them from
the controller to the syslog server. Use the tar logs CLI command to create an archive of all local logs, then use
the copy CLI command to copy this archive to an external server. Log space is limited on the controller, and
depending on how long the outage lasted some local logs may be overwritten.
Dell Networking W-Series ArubaOS 6.5.x | User Guide Management Access |
856