Managing Data Retention; Table 35 Sylog Priority Levels - Aruba Networks PowerConnect W Clearpass 100 Software Deployment Manual

For high-traffic sites that are maintaining many weeks of log files, enter a non-zero value for Disk Space to
ensure that the log files cannot fill up the system's disk. If the disk space check is enabled, the server's free
disk space is checked daily at midnight, and if it is below the specified threshold, old log files are deleted to
free up space.
The syslog protocol is used to send log messages from one system to a syslog server (also known as a
'collector'). The syslog protocol uses UDP port 514. Log messages are grouped according to both facility
and priority.
System log messages can be sent to multiple syslog collectors. In the Syslog Server row of the System Log
Configuration page, you may enter multiple syslog collectors as a comma-separated list of hostnames or IP
addresses.
When a syslog server has been defined, messages that match the rules defined in this form will be sent to
the specified syslog server.
The following priority levels are defined in the syslog protocol, which is fully specified in

Table 35 Sylog Priority Levels

Level
0
1
2
3
4
5
6
7
Click the
immediately.

Managing Data Retention

The Data Retention Policy page (Administrator > System Control > Data Retention) lets you manage
historical data by archiving or deleting it. For a data retention policy to take effect, you must schedule and
enable database maintenance. To do this, go to Administrator > System Control > Database Config.
404 | Administrator Tasks
Name Meaning
Emergency System is unusable
Alert Action must be taken immediately
Critical Critical conditions that warrant urgent attention
Error Error conditions that should be investigated more closely
Warning Warning conditions that may need to be investigated more
closely
Notice Normal but significant condition
Informational Informational messages
Debug Debugging messages
Save Changes button to apply the new system log parameters. The changes will take effect
RFC 3164:
ClearPass Guest 3.9 | Deployment Guide