Home

Forums

Stories

Knowledge Base

Business Community > All Threads > Management VLAN in Omada SDN Controller > fail

< All Threads

Management VLAN in Omada SDN Controller > fail

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

Management VLAN in Omada SDN Controller > fail

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

mftitalia

2022-09-15 13:02:13 - last edited 2022-09-15 14:06:07

Posts: 7

Helpful: 0

Solutions: 1

Stories: 0

Registered: 2022-09-15

Management VLAN in Omada SDN Controller > fail

2022-09-15 13:02:13 - last edited 2022-09-15 14:06:07

Tags: #Adoption #Controller

Model: ER605 (TL-R605)

Hardware Version: V2

Firmware Version: 2.0.1

If you want to have Controller and Devices on a Management VLAN using ER605 and a controller (i'm using OC200) simply you cannot do it.

Following this guide: https://www.tp-link.com/us/support/faq/2814/ you are going to crash on the fact that the "Omada Discovery Utility" is not able to discover the ER605 router and therefore the whole procedure becomes useless as you find yourself with the controller and the devices on the management VLAN, while the router remains on the DEFAULT LAN and is no longer able to speak with the controller !

1 Accepted Solution

mftitalia

LV1

2022-09-15 14:03:25 - last edited 2022-09-15 14:06:07

Posts: 7

Helpful: 0

Solutions: 1

Stories: 0

Registered: 2022-09-15

Re:Management VLAN in Omada SDN Controller > fail-Solution

2022-09-15 14:03:25 - last edited 2022-09-15 14:06:07

It's INSANE....

I solved the problem but it's totaly insane!!!!

- Discovery utility is able only to discovery devices not adopted!

- Router and controller, connected directly but with different VLAN are unable to discover each other

How to solve the problem?

- To reach the goal you have to configure controller with IP static of the desidered management VLAN

- Using a third party switch you have to tag the port where the controller is connected

- With the er605 on factory default, have to log in and create the management VLAN

- in the er605 you have to go in the controller settings and set enable remote management and set the ip of the controller

- now you have to connect the er605 to a port on the third party switch with native vlan as the default lan, with on same port running the Management VLAN

- Now the controller is able to see the roouter and adopt it.

IT'S INSANE!!!!

Recommended Solution

2 Reply

d0ugmac1

LV5

2022-09-15 13:12:24

Posts: 2149

Helpful: 791

Solutions: 194

Stories: 0

Registered: 2022-03-05

Re:Management VLAN in Omada SDN Controller > fail

2022-09-15 13:12:24

@mftitalia

Agreed, the whole 'use a management VLAN' part of the Omada solution seems pretty clunky and poorly thought out. I found it easier to turn the whole thing on its head and just VLAN and ACL and Route Policy the heck out of the user network(s). Of course you need an all-Omada Omada Router+Switch+Controller+APs to do this, but it does work at least and doesn't fall to bits as soon as you have to replace a device (upgrade or failure).

<< Paying it forward, one juicy problem at a time... >>

mftitalia

LV1

2022-09-15 14:03:25 - last edited 2022-09-15 14:06:07

Posts: 7

Helpful: 0

Solutions: 1

Stories: 0

Registered: 2022-09-15

Re:Management VLAN in Omada SDN Controller > fail-Solution

2022-09-15 14:03:25 - last edited 2022-09-15 14:06:07

It's INSANE....

I solved the problem but it's totaly insane!!!!

- Discovery utility is able only to discovery devices not adopted!

- Router and controller, connected directly but with different VLAN are unable to discover each other

How to solve the problem?

- To reach the goal you have to configure controller with IP static of the desidered management VLAN

- Using a third party switch you have to tag the port where the controller is connected

- With the er605 on factory default, have to log in and create the management VLAN

- in the er605 you have to go in the controller settings and set enable remote management and set the ip of the controller

- now you have to connect the er605 to a port on the third party switch with native vlan as the default lan, with on same port running the Management VLAN

- Now the controller is able to see the roouter and adopt it.

IT'S INSANE!!!!

Information

Helpful: 0

Replies: 2

Management VLAN in Omada SDN Controller > fail

Management VLAN in Omada SDN Controller > fail

Information

Voters 0

Tags