I think you have enable the Management VLAN for EAP225. With the Management VLAN enabled, only the Controller/OC200 belongs to this VLAN can adopt and manage the EAP225. So we suggest you checking the VLAN setting of your network first.

I use EAP 225 V3 and OC200

They are both in same VLAN and  same subnet (10.0.8.0/22) from DHCP server, check ping success to EAP and OC225

I reset EAP password many time and tried default password, both don't working

I use EAP 225 V3 and OC200

They are both in same VLAN and  same subnet (10.0.8.0/22) from DHCP server, check ping success to EAP and OC225

I reset EAP password many time and tried default password, both don't working

That's weird thing. Maybe you can send a email to support.tp-link.com for help.

Hi Kay
It can. 

I am also quite good at setting management VLAN on the EAPs. 

It seems you are using pure L2 VLAN structure, as the OC200 is in same subnet as EAPs.
Let me give my example.

My goal:

EAP225 in management VLAN100. but ssid bind to VLAN1 for guests.

OC200 in management VLAN100.

I am using a L2 VLAN switch.

Steps:

1. Ensure the EAP are in default status, to reduce misunderstanding.

2. Put the OC200 and EAPs in VLAN1 (untag on the switch ports), so now you can adopt the EAPs in OC200.

3. On OC200 --> enable management VLAN = 100. Wait till all EAP finish provisioning and you will see all the EAPs disconnect because EAP now "tag its own management traffic with VID100 and accepts only incoming management traffic with Vid100".

4. Then on the switch:

    create VLAN100,

    configure the EAP ports as "allow VLAN1(for guest), allow VLAN100 (for EAPs), outgoing tag" ,

    configure the OC200 port as "allow VLAN100 (for EAPs), outgoing untag, incoming tag VID100". (This is because OC200 itself cannot generate or accept any tagged traffic, so what I am actually doing is to configure the switch port as ACCESS PORT, allowing VLAN100).

Now, EAP sends its management traffic with VID100, switch accepts this traffic and then untagged and forward to OC200. OC200 accepts the untagged traffic from EAPs and then talk back to them by sending untagged traffic, then switch accept OC200's untagged traffic and tag them with VID100 and then forward to EAPs.

So it works.

My network have 2 segment with 2 subnet and alot device in producing. I plan to upgrade some old AP to EAP 225 and using one OC200 for all the AP in 2 subnet.

You should look my network diagram, I know how to setup VLAN. Mikrotik have more feature to do with subnet, VLAN, routing... than TPLink switch.

But the protocol TP Link using connect from controller to access point make me confuse.

Their VLAN managed on access point work well with web access, not for cloud control.

Hello, I have the following query, because it is confusing all this vlan with the EAP.

I have 3 different networks in my network. for example:

LAN Offices 10.10.10.1/24 + (vlan20; vlan30)
LAN Students 10.10.20.1/24 + (vlan10; vlan30)
LAN Rooms10.10.30.1 / 24 + (vlan10; vlan20)

Each network is for different uses, for example offices, students and rooms.

The need arises to have EAP in all ranges, because not all cables reach everywhere.

2 EAP + omada controller on 10.10.10.1/24
2 EAP on 10.10.20.1/24
2 EAP at 10.10.30.1/24

create 3 wifi signals and their respective ssid

SSID: Offices
SSID: Students
SSID: Rooms

but what I need is more complete, I need to be able to place a VLAN to each EAP particularly
EAP that are DHCP 10.10.20.1, configure VLAN10, to see omada controller.

Summary, I need to use EAP nodes in all wired IP ranges and that emit all ranges over Wi-Fi, I need that each EAP node has the option of choosing which VLAN to connect regardless of which VLAN emits over Wi-Fi.

am I clear?
ideas?