How to change the vlan for LAN1 and LAN2 ports on H320

  • 1
  • Question
  • Updated 3 months ago
  • Answered
I am deploying H320 APs connected to Ruckus Cloud and can not find a way to change the VLAN used by the LAN1 and LAN2 ports.
Traffic from devices connected to these ports simply goes to the untagged / native VLAN of the AP, which is the management VLAN.
Photo of Michael Jorgenson-Price

Michael Jorgenson-Price

  • 2 Posts
  • 0 Reply Likes

Posted 10 months ago

  • 1
Photo of Sandeep Gupta

Sandeep Gupta, Employee

  • 25 Posts
  • 10 Reply Likes
Hi Michael,
I do believe that VLAN tagging on those ports is not currently a supported feature in the Ruckus Cloud offering.  Keep watching for updates.

It is supported with other control options such as Unleashed and Smartzone and is also supported on the H510 in Cloud as of the next scheduled release (Jun-2018).
(Edited)
Photo of Michael Brado

Michael Brado, Official Rep

  • 2702 Posts
  • 376 Reply Likes
Yes, this feature is coming in Cloud 18.01 with screen like this:



The release is still a couple weeks away, and should be completely updated by End of June.
Photo of Michael Jorgenson-Price

Michael Jorgenson-Price

  • 2 Posts
  • 0 Reply Likes
Thanks very much, Michael
Photo of Supriya

Supriya, Employee

  • 24 Posts
  • 12 Reply Likes

Configurable options:

·      LAN port

·      Port Type

·      VLAN untag ID/Management VLAN – 1 (mgmt. VLAN always 1)

 

Port Types:

·      Access – End users and VLAN-unaware workstations commonly reside on access links. All ports are in ACCESS mode assigned to the default VLAN (VLAN 1). Ports set to Access mode belong to one VLAN only.

·      Trunk – On VLAN trunk links, all frames must be tagged with the respective VLAN ID’s. The native VLAN must match on all switches in the segment. (VLAN 1 is default Native VLAN). The native VLAN is NOT tagged.

·      General – similar function as Trunk ports but passes only the VLAN traffic that is defined by the user.