Business Community > All Threads > EAP 225 connect to trunk port on switch
< All Threads

EAP 225 connect to trunk port on switch

EAP 225 connect to trunk port on switch

EAP 225 connect to trunk port on switch
EAP 225 connect to trunk port on switch
Tuesday - last edited 16 hours ago
Model: EAP225  
Hardware Version: V3
Firmware Version: 5.1.6

Hi everyone.

 

I'm having difficulty getting the following situation to work:

 

I have a TL SG2428P switch, that is configured trough the webinterface, because when I adopted it in the Omada configuration, I found it a bit too difficult to get all my WLAN settings configured. When I did this with the built-in web interface, it worked easier for me.

 

On the switch I have configured port 21 as a untagged trunk port with Vlans 1(management), 20 (Lan), 60 (IOT) and 99 (Guest). I also have tried to set the port to tagged, but this also didn't work.

 

When I connect the EAP225 to this trunk port, the omada controller doesn't find the AP, when I connect it to a lan port directly it does. When I then, after configuring the AP WLAN SSID's, try to connect it to the trunk port, It just doesn't seem to work, I get the SSID's in my wireless device, but I don't get a IP from the DHCP server in that selected WLAN range

(10.10.10.x - 10.10.20.x - 10.10.60.x - 10.10.99.x)

 

Do I actually have to have the switches adopted in the omada controller for this to work? Am I missing something else?

 

If anyone needs more information, happy to oblige.

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:EAP 225 connect to trunk port on switch-Solution
Tuesday - last edited 16 hours ago

Hi  @Houseofdreams_ 

 

You're not required to use the controller for everything, but once you get past a little learning curve I think you'll like it.  Regarding your specific issues...

 

Adopting the AP: Put the Controller and AP on the same VLAN. If it finds the AP when connected to a "lan" (vlan 20) port, then your controller is likely also on vlan 20.  Both the controller and AP should be untagged members of the same vlan and also have the same PVID (native vlan) value.

 

WLAN-VLAN Mapping: All SSID's mapped to a VLAN would need to have those vlans as tagged members on the AP's port.

 

Assuming you want to put the controller and AP in the management vlan 1...

  • Port 21 should have vlan 1 untagged, with PVID set to 1; vlan 20, 60 and 99 are tagged.
  • Port X (where controller is installed) should have vlan 1 untagged, with PVID set to 1

 

 

Recommended Solution
  0  
  0  
#2
Options
3 Reply
Re:EAP 225 connect to trunk port on switch-Solution
Tuesday - last edited 16 hours ago

Hi  @Houseofdreams_ 

 

You're not required to use the controller for everything, but once you get past a little learning curve I think you'll like it.  Regarding your specific issues...

 

Adopting the AP: Put the Controller and AP on the same VLAN. If it finds the AP when connected to a "lan" (vlan 20) port, then your controller is likely also on vlan 20.  Both the controller and AP should be untagged members of the same vlan and also have the same PVID (native vlan) value.

 

WLAN-VLAN Mapping: All SSID's mapped to a VLAN would need to have those vlans as tagged members on the AP's port.

 

Assuming you want to put the controller and AP in the management vlan 1...

  • Port 21 should have vlan 1 untagged, with PVID set to 1; vlan 20, 60 and 99 are tagged.
  • Port X (where controller is installed) should have vlan 1 untagged, with PVID set to 1

 

 

Recommended Solution
  0  
  0  
#2
Options
Re:EAP 225 connect to trunk port on switch
8 hours ago

  @D-C 

 

I made some small changes in the switch configuration like you mentioned. I have 3 AP's, located on the switch on ports 21, 22 and 23. These ports have the MGMT network (10.10.10.x as VLAN 1 untagged, with PVID set to 1) and the other 3 networks, LAN(20), IOT(60) and GUEST(99) are set as tagged. So far so good.

 

A little bit more detailed info: 

 

- The omada controller is located virtually (I know, to make it even more difficult to get setup correctly :/) and is connected to the MGMT (management) network (10.10.10.x) 

- The AP was first connected to the LAN network (10.10.20.x) 

 

At this stage, even though they aren't both in the same network, they could "see" each other in the omada controller(green - CONNECTED) and I can configure the AP.

 

When I then make the changes in the omada wireless settings and then connect one of the AP's to port 21, the omada controller first gives an error "heartbeat missed", followed bu "disconnected" a little while later. 

 

To make things even more strange, when I swapped the AP's cable to port 21, It actually worked for a few minutes, I got a IP address in the 10.10.99.x range, I even could browse the web, but after a few minutes, all wireless SSID's are gone. I assume at the same time that the omada controller changes the state of the AP to "disconnected".

 

I think I am still missing something?

 

If you need some screenshots, or any more info, please let me know.

  0  
  0  
#3
Options
Re:EAP 225 connect to trunk port on switch
5 hours ago

  @Houseofdreams_, assuming that you're using DHCP, if you can plug a computer into port 21, do you get a 10.10.10.x address?

  0  
  0  
#4
Options

Information

Helpful: 0

Views: 79

Replies: 3

Related Articles
Can i connect a repeater on an EAP 225 with voucher?
1623 0
Trunk Port
2027 0
EAP 225 - Backdored by the update ?
597 0
Slow speed on EAP 225
188 0
can i connect eap 225 acess point to TP-LINK TL-SG1016PE switch (without poe injector)
471 0
EAP 225 Outdoor LAN port down
1480 1
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.