Strange mac in logging omada oc200 controller

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Strange mac in logging omada oc200 controller

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Strange mac in logging omada oc200 controller
Strange mac in logging omada oc200 controller
2025-04-18 14:12:36 - last edited 2025-04-23 03:06:53
Model: OC200  
Hardware Version: V1
Firmware Version: 1.34.2 Build 20250110 Rel.75707

Hi all,

One of my oc200 controllers is sending on a regular base a log to my mailbox with the message of a discovered device that is unknown in my network. 
the mac adress in the logging is not a device in my network..... strange.....

the message is:

###################################################################################################
#                        Xxxxxxxxxxxx. Log - 2025-04-18
# Time: 2025-04-18
# Controller version: 5.15.8.12
# Controller Name: xxxxxxxxxxxxxx
###################################################################################################

2025-04-18 06:08:46 AM  DEVICE          INFO            Pending ap [ap:50-C7-BF-76-20-74:50-C7-BF-76-20-74] was discovered.

 

when i click in de logging on that mac i get "ap does not exist"

 

best regards

guy

  0      
  0      
#1
Options
1 Accepted Solution
Re:Strange mac in logging omada oc200 controller-Solution
2025-04-23 02:55:36 - last edited 2025-04-23 03:06:53

Hi  @Guyan 

 

It's possible that the controller has detected other mesh APs. When additional EAPs power on within the coverage range of the controller-connected EAP, they may be identified and enter a wireless pending state.

 

Are you still seeing this log in the controller recently? If it no longer appears, we recommend ignore it

Recommended Solution
  0  
  0  
#2
Options
1 Reply
Re:Strange mac in logging omada oc200 controller-Solution
2025-04-23 02:55:36 - last edited 2025-04-23 03:06:53

Hi  @Guyan 

 

It's possible that the controller has detected other mesh APs. When additional EAPs power on within the coverage range of the controller-connected EAP, they may be identified and enter a wireless pending state.

 

Are you still seeing this log in the controller recently? If it no longer appears, we recommend ignore it

Recommended Solution
  0  
  0  
#2
Options