Omada OC200 not reachable after MGMT VLAN config

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

Omada OC200 not reachable after MGMT VLAN config

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Omada OC200 not reachable after MGMT VLAN config
Omada OC200 not reachable after MGMT VLAN config
2023-10-26 09:22:46 - last edited 2023-10-27 11:25:56

Hi everyone,

I started to configure my network with the OMADA OC200 and now I got a problem:

I followed this instruction https://www.tp-link.com/de/support/faq/2814/ and after that my controller is not reachable anymore.

- I created a VLAN 4090 (management) as a Interface with DHCP (net 10.10.10.0/28  range: 10.10.10.1 - 10.10.10.14)
- I linked Port1 from the 2218P Switch to the related rofile (management)

- I updated the switches and the AP with the management profile

- I plugged the OC200 to the Port 1 of the switch

 

How do I know access the Controller now? It seems that it don't get an IP from the 10.10.10.0 Range.
If I plug my PC to this port I also don't get an IP. Manual config doesn't help.

 

If I plug the controller back to a non changed Port it it reachable again via 192.168.0.* network. 
I can see that the devices were manageable for the controller (show "connected" shortly and then changing to "heartbeat missing")
 

I do not have access to my switches anymore. Please help.

 

my equipment:

OC200

ER7206

SG2218P

SG3428

3x EAP615

 

 

Thank you and best regard

Sebastian

  0      
  0      
#1
Options
1 Accepted Solution
Re:Omada OC200 not reachable after MGMT VLAN config-Solution
2023-10-27 11:25:54 - last edited 2023-10-27 11:25:56

  @SebastianH 

Now everything is working like expected. It took ages until the controller got the new IP address.

 

Summary:
I configured everything like in the wiki article and it works. 
Some hints that it can take several minuten up to hours for some change to be applied would be good.

 

Why it didn't work in the first place, I don't know.

Recommended Solution
  0  
  0  
#5
Options
4 Reply
Re:Omada OC200 not reachable after MGMT VLAN config
2023-10-27 06:53:24

  @SebastianH 

 

How did you tagged the ports? Did you put the controller into the management VLAN either?

Just striving to develop myself while helping others.
  0  
  0  
#2
Options
Re:Omada OC200 not reachable after MGMT VLAN config
2023-10-27 07:26:46

  @Virgo 
Thank you for you reply.
I made it working again by resetting everything to factory default.
My 3428 switch I was able to access by putting my PC ethernet adapter to VLAN 4090 and connect it directy.

Afterwards I configured everything else exact the same way like before with one difference:
The first time I forgot to enable the DHCP setting when creating the 4090 VLAN Interface. I modified it directly afterwards.
This time I ticked it during creation.

Now it works.


 

  0  
  0  
#3
Options
Re:Omada OC200 not reachable after MGMT VLAN config
2023-10-27 09:39:01

Now I have made it to put every Switch and AP in the new Management VLAN. 
All the devices received a new IP from the correct range.

 

But I can't make it working when I plug the controller in the preconfigured port. 
It will not change its IP address. Not even after a reboot.

 

When I plug my PC to the port it receives the correct IP. when I plug the controller to the port, nothing happens.

 

 

 

  0  
  0  
#4
Options
Re:Omada OC200 not reachable after MGMT VLAN config-Solution
2023-10-27 11:25:54 - last edited 2023-10-27 11:25:56

  @SebastianH 

Now everything is working like expected. It took ages until the controller got the new IP address.

 

Summary:
I configured everything like in the wiki article and it works. 
Some hints that it can take several minuten up to hours for some change to be applied would be good.

 

Why it didn't work in the first place, I don't know.

Recommended Solution
  0  
  0  
#5
Options

Information

Helpful: 0

Views: 343

Replies: 4

Related Articles