Upgrade OC200 to SDN, upgraded EAPs, both disconnected now!

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

Upgrade OC200 to SDN, upgraded EAPs, both disconnected now!

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Upgrade OC200 to SDN, upgraded EAPs, both disconnected now!
Upgrade OC200 to SDN, upgraded EAPs, both disconnected now!
2020-07-20 12:32:54 - last edited 2020-07-20 13:14:25
Model: Adapter  
Hardware Version: V3
Firmware Version:

Ok, so upgraded my OC200 to SDN compatibility, followed instructions, upgraded 225/245 V3 with a manual firmware SDN version, configured and upgraded but now both EAPs are disconnented and cant get them back. This was a disaster! 

 

Also under settings-wired network it says you can change the default LAN to a different none default IP range from192.168.0.1/24 how, where is the edit button to change that IP range?

Further, cannot update the OC200 now WITHOUT a cloud account, dont want a cloud account, why has this changed?

  0      
  0      
#1
Options
6 Reply
Re:Upgrade OC200 to SDN, upgraded EAPs, both disconnected now!
2020-07-20 13:13:48

@Pugs UPDATE: They are now connected, issue was that the edgerouter had to have a PVID 1added instead of  previoulsy being tagged (VLAN 1). What has happened with the new software that has changed VLAN tagging

 

EAP Port config on router

Before SDN upgrade:

pvid 200 (dummy)

vid 1, 10

 

Now

pvid 1

vid 10

 

OC200 Port config on router

Before\After 

pvid 1

vid NONE

 

Anything that is required to be changed in the new software for OC200?

  0  
  0  
#2
Options
Re:Upgrade OC200 to SDN, upgraded EAPs, both disconnected now!
2020-07-21 00:11:20 - last edited 2020-07-21 00:14:26

Hi Pugs,

 

on EdgeRouter a virtual interface is an access port if you set only the PVID, but no other VLAN.

It becomes a trunk port if you add more VLAN IDs.

 

Thus,

EAP Port config on router

Now

pvid 1

vid 10

 

assigns the port a tagged membership in VLAN 10, while untagged frames get tagged with VID 1 on ingress and tag removed (IIRC) on egress. That's the correct setting if you want to define an additional SSID mapped to VLAN 10. If you add VLAN 1 to the list of VIDs and remove it from PVID, the port will become a tagged member of both VLANs 1 and 10 on ingress and egress. You probably had set the Management VLAN to 1 in OC200 before the upgrade, then frames need to be tagged for the EAP and the port needs to be a trunk port.

 

Likewise,

OC200 Port config on router

pvid 1

vid NONE

 

assigns the port an untagged membership in VLAN 1 only. That's the correct setting for an OC200, which processes only untagged frames (even if the Management VLAN is set in OC200).

 

Anything that is required to be changed in the new software for OC200?

 

 

Yes. There are some settings which can't be restored from a backup and which will require manual intervention. See the Omada Controller Upgrade Guide for more information.

 

Rgearding your question about changing the network IP for the LAN in Wired Network settings: you don't need to change the default LAN profile unless you manage an Omada Security Gateway with the controller (which isn't yet available at this time). The default LAN profile does neither affect your network settings nor the EAP's IP addresses.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#5
Options
Re:Upgrade OC200 to SDN, upgraded EAPs, both disconnected now!
2020-07-21 10:02:31

@R1D2 Thanks bud, TP-LINK should be paying you for supporting here!

 

Anyway another silly? question, where do you change the 802.11 settings to restrict what type of compliant device connects on 2.4/5Ghz channels i.e.

 

802.11b/g/n mixed

802.11a/n/ac mixed

 

I dont want a or n devices connecting to 5Ghz and similarly dont want 'b' devices on 2.4 (no need, i dont have any older devices)

 

 

  0  
  0  
#6
Options
Re:Upgrade OC200 to SDN, upgraded EAPs, both disconnected now!
2020-07-21 11:05:28

 

Pugs wrote

Thanks bud, TP-LINK should be paying you for supporting here!

 

Gladly! Would buy certain JetStream switches then to play with them. :-)

 

Anyway another silly? question, where do you change the 802.11 settings to restrict what type of compliant device connects on 2.4/5Ghz channels i.e.

 

 

There is now a fine-grained control in the Wireless Network → 802.11 Rate Control settings. However, I still wait for the User's Guide, but you might want to try some settings to see what happens when changing those parameters if you have some spare time:

 

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#7
Options
Re:Upgrade OC200 to SDN, upgraded EAPs, both disconnected now!
2020-10-14 11:05:22 - last edited 2020-10-14 11:11:40

@Fae 

 

Back to this topic. I want to use a management vlan1 on my EAPS, I cant because i cannot use VLAN 1 because its locked down to a 192.168 IP address under Wired Networks! So, how do I use my own VLAN1 IP address range?

 

Surely TP-LINK doesn't expect us to use their own specified 192.168 range for VLAN1? If so, thats crazy and a complete deal breaker

  0  
  0  
#8
Options
Re:Upgrade OC200 to SDN, upgraded EAPs, both disconnected now!
2020-10-14 11:16:43

@Pugs, »Wired Network« settings will only take effect if you have an Omada switch and an Omada gateway which are managed by the controller.

 

As long as you use non-SDN switches and an EdgeRouter you can use any network IP and any VLAN setup. Just turn on Mgmt VLAN to have EAPs process tagged frames, everything else (»Wired Network« settings) can be safely ignored.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#9
Options

Information

Helpful: 0

Views: 1402

Replies: 6