Environment -Standalone controller running 6.3.1.13 AOS.
Answer - When there is any config change or debugging is been enabled on the controller, these recent changes should be sent from controller SAPM to AP.
For example, lets say client-match debug log is been enabled, the AP will start sending the client match related debug messages to the controller.
# logging level debugging user subcat client-match
Jan 22 14:21:24 :507013: <DBUG> |AP TestAP@10.98.11.38 sapd| |client-match| Client Match: Detected client 8c:2d:aa:7d:76:ce Assoc BSSID 24:de:c6:c6:9c:11 channel 11 with low RSSI 11 dB
Jan 22 14:21:24 :507004: <DBUG> |AP TestAP@10.98.11.38 sapd| |client-match| Client Match: Other radio 24:de:c6:c6:9b:00 not strong enough: Min Signal 65 Sticky thresh 10, cur signal 87 new signal 86 (-dBm)
Jan 22 14:21:24 :507007: <DBUG> |AP TestAP@10.98.11.38 sapd| |client-match| Client Match: For client 8c:2d:aa:7d:76:ce Trigger Sticky No better candidate AP
When this logging been disabled, the AP will stop sending the client match related debug messages to the controller.
# no logging level debugging user subcat client-match
To check the recent message sent from the controller to the AP, execute the below command with name of AP which triggers the debug messages:
"show ap details advanced ap-name <ap-name>"
It will show the most recent message sent from controller SAPM to AP, and there should be a "LOG_CONFIG".
Sample Output:
============
.......
Rebootstraps and Control Messages Log
-------------------------------------
Recent Messages Time now: Wed Feb 25 03:20:57 2015
--------------- ----------------------------------
Time Offset Message details
----------- ---------------
-3 SENT: LOG_CONFIG len=252 peer=10.3.43.243 seq_num=8 tries=1 rtt=0 result=OK
-443 RCVD: KEEPALIVE len=20 peer=10.3.43.243 seq_num=573 rtt=0 result=OK
Then execute "show ap debug config-msg-history ap-name <ap-name>", It will show the recent message received by AP:
Sample Output:
============
......
Wed Feb 25 03:20:54 2015(382 secs ago): RCVD REQ type=LOG_CONFIG len=176 peer=10.3.90.100 seq_num=8 resps_sent=1
AnswerLT- When there is any config change or debugging is been enabled on the controller, these recent changes should be sent from controller SAPM to AP.
For example, lets say client-match debug log is been enabled, the AP will start sending the client match related debug messages to the controller.
# logging level debugging user subcat client-match
Jan 22 14:21:24 :507013: <DBUG> |AP TestAP@10.98.11.38 sapd| |client-match| Client Match: Detected client 8c:2d:aa:7d:76:ce Assoc BSSID 24:de:c6:c6:9c:11 channel 11 with low RSSI 11 dB
Jan 22 14:21:24 :507004: <DBUG> |AP TestAP@10.98.11.38 sapd| |client-match| Client Match: Other radio 24:de:c6:c6:9b:00 not strong enough: Min Signal 65 Sticky thresh 10, cur signal 87 new signal 86 (-dBm)
Jan 22 14:21:24 :507007: <DBUG> |AP TestAP@10.98.11.38 sapd| |client-match| Client Match: For client 8c:2d:aa:7d:76:ce Trigger Sticky No better candidate AP
When this logging been disabled, the AP will stop sending the client match related debug messages to the controller.
# no logging level debugging user subcat client-match
To check the recent message sent from the controller to the AP, execute the below command with name of AP which triggers the debug messages:
"show ap details advanced ap-name <ap-name>"
It will show the most recent message sent from controller SAPM to AP, and there should be a "LOG_CONFIG".
Sample Output:
============
.......
Rebootstraps and Control Messages Log
-------------------------------------
Recent Messages Time now: Wed Feb 25 03:20:57 2015
--------------- ----------------------------------
Time Offset Message details
----------- ---------------
-3 SENT: LOG_CONFIG len=252 peer=10.3.43.243 seq_num=8 tries=1 rtt=0 result=OK
-443 RCVD: KEEPALIVE len=20 peer=10.3.43.243 seq_num=573 rtt=0 result=OK
Then execute "show ap debug config-msg-history ap-name <ap-name>", It will show the recent message received by AP:
Sample Output:
============
......
Wed Feb 25 03:20:54 2015(382 secs ago): RCVD REQ type=LOG_CONFIG len=176 peer=10.3.90.100 seq_num=8 resps_sent=1