Meru Technical Note - How to block coordinator (Station Association and Dis-association) information in syslog
Description
This article explains how to block station coordinator (Station Association and Dis-association) information in syslog.
Scope
6.x and above.
Solution
Use the following steps to block the coordinator information in syslog.
1) Add syslog information to controller by using the following commands.
2) To check for system information of syslog in the controller.
Navigate to Maintenance > File management > syslog > System > Export. View the file in notepad to see the station coordinator information.
3) Make a copy of the syslog file before making changes.
Make a duplicate of syslog.conf file in the following location:
4) Modify the file.
Replace the parameter where you have local1.* to local1.*;local1.!=notice in the following files:
5) Restart syslog service in root mode and verify if the service is been restarted.
6) Check for the coordinator information in syslog file and the coordinator information should be seen to be blocked.
1) Add syslog information to controller by using the following commands.
Controller#
Controller# configure terminal
Controller(config)# syslog-host 10.32.33.114
Controller(config)# exit
Controller# sh syslog-host
10.32.33.114
2) To check for system information of syslog in the controller.
Navigate to Maintenance > File management > syslog > System > Export. View the file in notepad to see the station coordinator information.
3) Make a copy of the syslog file before making changes.
Make a duplicate of syslog.conf file in the following location:
(a) /etc/
(b) /opt/meru/var/run/running-db/
4) Modify the file.
Replace the parameter where you have local1.* to local1.*;local1.!=notice in the following files:
(a) /etc/syslog.conf
(b) /opt/meru/var/run/running-db/syslog.conf
5) Restart syslog service in root mode and verify if the service is been restarted.
6) Check for the coordinator information in syslog file and the coordinator information should be seen to be blocked.
