Controller Provisioining of ES210X-M2 Fails

Controller Provisioining of ES210X-M2 Fails

Controller Provisioining of ES210X-M2 Fails
Controller Provisioining of ES210X-M2 Fails
a week ago - last edited Monday
Model: ES210X-M2  
Hardware Version: V1
Firmware Version: 1.0.1 Build 20251128 Rel.41332

I am trying to adopt an ES210X-M2 switch to an Omada SDN controller.  I can get the controller to adopt on VLAN1 but as soon as I try to configure any other VLANs or switch port configuration, the switch goes offline and must be hard reset to recover.  Standalone mode appears to work fine.

 

The issue presents similarly to:  https://community.tp-link.com/en/business/forum/topic/863690?moduleId=3

 

Thanks

0
0
#1
1 Accepted Solution
Re:Controller Provisioining of ES210X-M2 Fails-Solution
Friday - last edited Monday

  @Vincent-TP 

 

Thank you very much.  I found my issue.  In my previous configuration with assorted non-Omada switches I had set my trunk port to carry only tagged traffic.  My (non-Omada) Router /DHCP server was configured to serve DHCP only on tagged ports.  A port carrying no untagged vlan is a configuration only possible via the switch UI since the controller combines PVID and untagged VLAN as "Native VLAN".  When the switch was adopted into the controller, the management vlan went from tagged to untagged causing the DHCP server to be unavailable.  I resolved the issue by reconfiguring the DHCP to serve DHCP on the management VLAN as untagged.

 

Thanks again!

Recommended Solution
1
1
#5
5 Reply
Re:Controller Provisioining of ES210X-M2 Fails
a week ago

  @LnxRocks 

 

Are you configuring the switch ports from inside its device management page directly when it has been adopted, or during the vlan wizard ?

 

I do have many SG and ES class switches and have never seen this, but i always configure my ports manually and not during the wizard.  My only though is if you are changing the native vlan on the switch uplink port without realising it?

0
0
#2
Re:Controller Provisioining of ES210X-M2 Fails
a week ago

  @GRL 

 

I'm not sure what you mean by the wiizard.  Here is the process I was using:

 

From factory reset state:

 

1) Enter the switch management page and configure DHCP and 802.1q vlan.

2) Once the switch receives an IP address from VLAN1, it appears in the controller as pending

3) Adopt the switch 

4) Switch adopts in and is shown as connected

5) Under Network Config -> Switch Ports make a change to any port and apply

 

In a few seconds, all devices connected to the switch willl lose connection.  The switch reverts to it's default IP of 192.168.0.1.  Going to the switch page it says the switch has been adopted.

 

It's possible I accidentally changed the Native VLAN (I ran so many tries they all blur together), but I thought I was being careful in later attempts.

 

 

Some other notes in case they are relevant:

  • My router / dhcp is running OpenWRT and is not Omada
  • The controller is directly connected to the ES210X-M2
  • I bought an ES208G as a downstream switch.  Once I properly configured VLAN1 as a management VLAN it adopted into the controller and configured without issues (Even using DHCP option 138)

 

Thanks

0
0
#3
Re:Controller Provisioining of ES210X-M2 Fails
Friday

Hi  @LnxRocks 

 

Thanks for your posting.

Actually, our team had already tested the issue you provided feedback on in the other post, and everything works perfectly.

We may test again with ES210X-M2. Before that, please let us know:

 

5) Under Network Config -> Switch Ports make a change to any port and apply

>>>What exact change did you do on this step? Or do you mean any change will cause the switch to turn offline?

 

If possible, could you record a video showing this process? This will help us better understand the situation. Thanks.

0
0
#4
Re:Controller Provisioining of ES210X-M2 Fails-Solution
Friday - last edited Monday

  @Vincent-TP 

 

Thank you very much.  I found my issue.  In my previous configuration with assorted non-Omada switches I had set my trunk port to carry only tagged traffic.  My (non-Omada) Router /DHCP server was configured to serve DHCP only on tagged ports.  A port carrying no untagged vlan is a configuration only possible via the switch UI since the controller combines PVID and untagged VLAN as "Native VLAN".  When the switch was adopted into the controller, the management vlan went from tagged to untagged causing the DHCP server to be unavailable.  I resolved the issue by reconfiguring the DHCP to serve DHCP on the management VLAN as untagged.

 

Thanks again!

Recommended Solution
1
1
#5
Re:Controller Provisioining of ES210X-M2 Fails
Monday

Hi  @LnxRocks 

 

Great to hear that the issue has been resolved!

If you encounter any further problems or have additional questions, feel free to reach out.

0
0
#6