[Solution] Mesh EAP doesn’t send Client Detail Logs with Omada’s Remote Logging feature

[Solution] Mesh EAP doesn’t send Client Detail Logs with Omada’s Remote Logging feature
[Solution] Mesh EAP doesn’t send Client Detail Logs with Omada’s Remote Logging feature
2021-08-17 12:36:33 - last edited 2 weeks ago

This Article Applies to:

 

EAP225(EU/US) V3, EAP225-Outdoor(EU/US) v1

 

Background:

 

With the Remote Logging feature properly configured, the Omada Controller will be able to send the generated site logs to the expected external syslog server. If the Client Detail Logs feature is enabled during the configuration, the logs of connected clients will be sent to the syslog server as well.

 

Problem Description/Phenomenon:

 

If you have an EAP mesh network, and you have configured the "Remote Logging" feature with the "Client Detail Logs" option enabled on the Omada Controller, you may find that you cannot get detailed logs of the clients connected to the Mesh EAP on the syslog server, comparing to the logs of the clients connected to the Root EAP.

 

To be specific, you may just find basic logs of the clients connected to the Mesh EAP like the following:

But you can get more detailed logs of the clients connected to the Root EAP, which includes the source , destination , ports used , MAC of devices like the following:

 

Available Solution:

 

The root issue is that the Mesh EAP won’t send the detailed logs of clients to the Controller while the Root EAP will.

 

If you have the demand to receive detailed client logs from the Mesh EAP, you can install the following beta firmware to make it.

 

EAP225_V3_5.0.3 Build 20210803 (Beta)

EAP225-Outdoor_V1_5.0.3 Build 20210803 (Beta)

 

 

---------------------------------------------------------------------------------------------

Keywords: Remote Logging, Client Detail Log, syslog server, Mesh EAP

New to the TP-Link Community? Getting Started from this thread: https://community.tp-link.com/en/business/forum/topic/551684
0
0
#1
Options