@Jackace 

 

There is one PoE out port on the 235-Wall. Check the product pics: https://www.tp-link.com/en/business-networking/omada-sdn-access-point/eap235-wall/

And, what you say here is when you plug a device into the EAP235-W, it will just pass through this device? Not connected to the EAP but to the switch? I don't really understand.. Not sure if I understand you correctly. Can you paste some pictures for this?

 

The Omada Map(topology) only shows Omada compatible devices. If that PoE switch is not Omada compatible or other brands, won't show up at all.

@Yannie 

 

 

This EAP WAP is connected to the MAIN_POE_SWITCH but it doesn't show up that way unless I unplug both physical devices plugged into the EAP WAP switchports.

 

 

These Clients are physically connected to the EAP WAP switch ports not the MAIN_POE_SWITCH Port 1. The EAP WAP is physically connected to the MAIN_POE_SWITCH Port 1.

 

 

The EAP WAP in the Uplink section reports (corrctly) that is is connected to the MAIN_POE_SWITCH, but back to the first picture posted it doesn't show up that way on the MAP.

 

 

You can see the MAIN_POE_SWITCH doesn't report the EAP WAP connected to Port 1 how it should be. If I physically unplug the 2 clients from the EAP WAP it will change and show up on the switch down links and the MAP correctly.

 

It's almost like the EAP WAP switch ports are acting like a HUB and not a switch and confusing the MAIN_POE_SWITCH on what is physically connected to it's port.

@Jackace 

 

Yeah. I see. So, this one is acting weird. I saw you have multiple EAPs that are the same models like this one. Do they have similar issues like this "troublesome" one?

Seems to be a visual bug. I don't know. But, it does not act what it's supposed to be. 

 

Add some thoughts.

1. Make sure that #1 port is working okay with other devices. The device plugged in, shows the device.

2. Reset? Re-adopt this one? Re-config it? Will this solve your issue?

@Yannie 

 

As soon as I unplug the wired clients from the EAP WAP the MAP updates and everything shows up correctly in the various uplinks and downlinks on the devices. If I plug wired clients into the other EAP WAPs they do the same thing as this one. Like I said it seems something is confusing the switch on what is connected to it's ports and the EAP WAP isn't reporting wired clients at all and instead is passing them through to the switch.

 

It seems part of the problem is my PC (which also has the controller installed) is one of the the wired clients on the EAP WAP. That is what is causing the EAP WAP to not show up as connected to the switch. It instead show my PC, the controller, connected to the switch. Again this all seems to be caused because the EAP WAPs don't report wired clients and instead pass them through to the connected switch.

@Jackace 

 

Don't know why's that. What's the Omada version? 4.4.3? Software or hardware OC?

4.4.3 and software running on my PC. Waiting for the OC200 to get 4.4.3 then I will migrate my controller to it.

@Fae 

 

I tried that firmware. It had the same issue. Once I moved the controller off the EAP the map updated showing the EAP connected to the switch as it should. My guess is there is some weird interaction between the EAP, wired clients and the discovery mechanism for the MAP.