Switchport configuration for Omada Controller

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

Switchport configuration for Omada Controller

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Switchport configuration for Omada Controller
Switchport configuration for Omada Controller
2020-04-30 19:30:36 - last edited 2020-04-30 20:48:12
Model: OC200  
Hardware Version: V1
Firmware Version: 3.2.5

Sorry for the newbie question. I have set up the switch port as a trunk port on my switch, is this correct? Or should it be a access port

  0      
  0      
#1
Options
1 Accepted Solution
Re:Switchport configuration for Omada Controller-Solution
2020-04-30 19:53:35 - last edited 2020-04-30 20:48:12

@JD792, the port to OC200 must be an access port. The port to an EAP must be a trunk if you use either VLAN-mapped SSIDs or Management VLAN or both. See the following diagram for a typical topology. P1, P2 and P4 are access ports, P3 is a trunk. P2 and P4 are members of the Management VLAN 200 (if any), while P3 is a member of Management VLAN 200, VLAN 10, VLAN 20 and VLAN 30:

 

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
Recommended Solution
  1  
  1  
#2
Options
3 Reply
Re:Switchport configuration for Omada Controller-Solution
2020-04-30 19:53:35 - last edited 2020-04-30 20:48:12

@JD792, the port to OC200 must be an access port. The port to an EAP must be a trunk if you use either VLAN-mapped SSIDs or Management VLAN or both. See the following diagram for a typical topology. P1, P2 and P4 are access ports, P3 is a trunk. P2 and P4 are members of the Management VLAN 200 (if any), while P3 is a member of Management VLAN 200, VLAN 10, VLAN 20 and VLAN 30:

 

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
Recommended Solution
  1  
  1  
#2
Options
Re:Switchport configuration for Omada Controller
2020-04-30 20:48:05

@R1D2  Thank you! 

  0  
  0  
#3
Options
Re:Switchport configuration for Omada Controller
2020-04-30 20:58:27 - last edited 2020-04-30 21:02:03

@JD792, you're welcome.

 

Just for the record: If you use a Management VLAN, you need to temporarily untag traffic on VLAN 200 (or whatever ID your Mgmt VLAN has) to any new EAP you want to adopt in the OC200. The procedure is:

 

  • Connect a new (or a factory-reset) EAP to the switch, say on port 8.
  • Set port 8 as an untagged member of VLAN 200, PVID=200.
  • Adopt the EAP in OC200, it will change the state to »Provisioning«.
  • Now change switch port 8 from untagged to tagged and add it as a tagged member of the SSID-VLANs if not done already.
  • Adoption will be completed then.

 

The reason for this procedure is that during adoption the EAP's Mgmt VLAN setting will be set up, so adoption can be successfully completed only if the port is first an untagged, then a tagged member of the Mgmt VLAN.

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

Information

Helpful: 0

Views: 5104

Replies: 3

Related Articles