How to enable and disable various logging levels on the Aruba Controller?

Aruba Employee

This article explains the need for various "logging levels" as well as enabling/disabling them on the Aruba controller.

 

For each of the various software module categories/subcategories, we can enable a logging level of the messages to be logged.Please refer to the User Guide to get a list of the various software modules for which the logging levels can be enabled.

Below is the list of the various logging levels that can be enabled (most to least severe):

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.

NOTE: If a specific logging level is enabled, all the higher logging levels that are more critical gets enabled by itself. Default logging level on the controller is Warning meaning Emergency, Alert, Critical and Errors are enabled automatically.

We can 
also configure IP address of a syslog server to which the controller can direct these logs.

 

Environment : This article applies to all the controller models and AOS version.

 

WebUI
 
1. Navigate to the Configuration > Management > Logging > Servers.
2. To add a logging server to collect the logs, 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.

 

rtaImage.png

 

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.

 

rtaImage (1).png

 

CLI
 
(NS-Aruba-3200) #configure terminal
Enter Configuration commands, one per line. End with CNTL/Z
 
(NS-Aruba-3200) (config) #logging level ?
alerts                  Immediate action needed
critical                Critical Condition
debugging               Debug Messages
emergencies             System is unusable
errors                  Error Conditions in the system
informational           Informational Messages
notifications           Normal but significant condition
warnings                Warning condition
 
To disable the logging level, use the “no” keyword as shown below:
 
(NS-Aruba-3200) #configure terminal
Enter Configuration commands, one per line. End with CNTL/Z
 
(NS-Aruba-3200) (config) #no logging level ?
alerts                  Immediate action needed
critical                Critical Condition
debugging               Debug Messages
emergencies             System is unusable
errors                  Error Conditions in the system
informational           Informational Messages
notifications           Normal but significant condition
warnings                Warning condition

 

(NS-Aruba-3200) #show logging level verbose
 
LOGGING LEVELS
--------------
Facility  Level        Sub Category  Process
--------  -----        ------------  -------
network   warnings     N/A           N/A
network   debugging    dhcp          N/A
security  warnings     N/A           N/A
security  warnings     ids           N/A
security  warnings     ids-ap        N/A
system    emergencies  N/A           N/A
user      warnings     N/A           N/A
wireless  warnings     N/A           N/A

Version history
Revision #:
1 of 1
Last update:
‎07-16-2014 12:30 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: