Limit the type of syslog messages sent from the VAP (APM) to the CPM
Article ID: 168053
Updated On:
Products
XOS
Issue/Introduction
Explains how to limit the type of syslog messages sent from the VAP (APM) to the CPM
N/A
Cause
In order to limit the type of syslog messages sent from VAPs (APMs) to the CPM changes to the syslog config must be made. One example of when limiting is necessary is when NPM debug/verbose messages are enabled as per solution#1115.
Resolution
Before making any changes, the current syslog configuration should be backed up to a location off of the system. Another approach is to copy the file on the VAP, ie. as syslog.conf~ depending on customer's choice.
The changes should be repeated on all the VAPs where you want to limit log messages to the CPM. All paths are expressed as from root folder level on the VAP.
/etc/syslog.conf line as below should be changed from
*.* @primarycpm
to
*.info @primarycpm
This limits the messages sent from the VAP to the CPM to informational level messages only.
After changing the file, restart the syslog daemon.
/etc/init.d/syslog restart
To revert the changes, /etc/syslog.conf must be returned to the old settings and syslog daemon restarted.
The changes should be repeated on all the VAPs where you want to limit log messages to the CPM. All paths are expressed as from root folder level on the VAP.
/etc/syslog.conf line as below should be changed from
*.* @primarycpm
to
*.info @primarycpm
This limits the messages sent from the VAP to the CPM to informational level messages only.
After changing the file, restart the syslog daemon.
/etc/init.d/syslog restart
To revert the changes, /etc/syslog.conf must be returned to the old settings and syslog daemon restarted.
Workaround
N/A
Feedback
Powered by
