Ruckus-Switch VLAN configuration

  • 2
  • Question
  • Updated 6 years ago

I have configured a stand-alone static switch (Cisco 3550) with three DHCP pools associated to different VLANS. Clients connected to vlan 1 would get IP addresses in range of 192.168.0.X, vlan 10 would be in the range of 192.168.1.X & vlan 20 in the range of 192.168.2.X ... Three different interfaces were configured with all three vlans (For Eg: Port 1 with vlan 1, port 2 with vlan 10 & port 3 with vlan 20). The same were tested by connecting a computer to all three ports and was successfully able to obtain a DHCP ip address in the respective range.

However, when i configure my Ruckus access point with the above mentioned vlan for different profiles, it doesn't seem to work. Three different wireless profiles are created viz. [email protected](Vlan 1), [email protected](Vlan 10) & Ruckus @3(Vlan 20).. [email protected] was enabled & was connected to port no 3 of the switch, yet failed to obtain an IP address for my wireless client.. Can anyone let me know in case if i am doing anything wrong at the Access point end as i am sure the switch configuration is correct?

Thanks in advance!
Photo of Mayur Javali

Mayur Javali

  • 8 Posts
  • 0 Reply Likes

Posted 7 years ago

  • 2
Photo of Rahul Koul

Rahul Koul, Employee

  • 79 Posts
  • 16 Reply Likes
Hi Mayur,

I believe what you are trying is to have your Access Points broadcast 3 different WLANs viz [email protected], [email protected] & Ruckus @3 for VLANs 1, 10 and 20 respectively.

In order for the clients to get valid Ip address the Access Points need to be connected to Trunk Ports "tagging"(or allowing) the VLANs 1, 10 and 20 and VLAN info has to be added for respective WLANs in ZD WebUI under Configure :: WLANs :: Advanced Options :: Access VLAN. After having done the above mentioned configuration if the clients still do not get valid Ip addresses then please try the below steps:

SSH into the ZD using a terminal client like "Putty" and execute the following commands:



ruckus(debug)# remote_ap_cli -A set qos directedDHCP disable

ruckus(debug)# remote_ap_cli -A get qos

Please let us know if this helps.

Note: I assume you have a Zone Director managing the Access Points.
Photo of Mayur Javali

Mayur Javali

  • 8 Posts
  • 0 Reply Likes
Hi Rahul,

Thanks for your reply. Yes, i tried the steps suggested by you but still failing in getting connected. Let me explain in detail as to what has been done from my end.

A cisco switch has been configured with DHCP settings for three different VLANS and all three works when connected to a PC. I also tried with a plug and play access point which i got it from my home where the AP was broadcasting the respective DHCP IP addresses as when connected to the switch port with respective vlans.

Now, I have connected the ruckus AP to a certain port which is a trunk port and configured with 1,10 & 20 VLAN ids. ZD has been configured and connected to a default access port. Three profiles/SSIDs created in a similar manner as attached ([email protected], [email protected] & [email protected]) As per your suggestion, the mentioned commands were also executed. Please let me know in case i am going wrong at some point. Attached screen shot of putty and ZD configuration is FYR.

Kindly let me know in case of any clarifications needed from my end.
Photo of Keith - Pack Leader

Keith - Pack Leader

  • 860 Posts
  • 52 Reply Likes
Does the fact the Cisco uses vlan 1 (IRRC..) for default come into play here?
Photo of Mayur Javali

Mayur Javali

  • 8 Posts
  • 0 Reply Likes
By default, cisco switches treat VLAN 1 as the default VLAN. The switch, ZD,AP and the end computer are connected to VLAN 1 IP addresses. However, this should not have any impact on the other vlans.

Kindly let me know if your question is still unanswered!
Photo of Mayur Javali

Mayur Javali

  • 8 Posts
  • 0 Reply Likes

Adding to that, the manual of ZD 1100 says that a radius server along with WPA/WPA2 encryption needs to be set. Is the radius server mandatory as i have setup a stand-alone network (Consisting a Switch, access point, ZD and a PC) which is isolated from the main network ??
Photo of Mayur Javali

Mayur Javali

  • 8 Posts
  • 0 Reply Likes

Any response on the same ?
Photo of Othmane Douiri

Othmane Douiri

  • 2 Posts
  • 0 Reply Likes
hi all,

i have the same issue regarding Vlans on ZoneFlex AP. i have an access point managed by a ZD. the AP is connected to a cisco trunk switch port with only the vlan 200 allowed. i have a dhcp server connected to this switch also and with a dhcp pool on vlan 200. I configured the access vlan on ZD as vlan 200. however, the end user can't get an ip address.

i think that this is due to the fact that the AP Ethernet interface is on Access mode not on Trunk as it should be.

i would like to know what heppen exactly when we configure access vlan id on ZD??? does the AP begins to tag client frames?? what about the AP ethernet port??
Photo of Bill Burns

Bill Burns, AlphaDog

  • 203 Posts
  • 42 Reply Likes

In this case, having your ZD controller connected to an access port in VLAN 200 is fine.
The most common/likely way to get your APs to work with the ZD is to connect the APs to trunk ports with their native VLAN set to 200.

This way, the AP and the ZD should get IP addresses in the same subnet and be able to discover each other.

If it's done this way, the AP sees it's management packets as untagged (a.k.a. VLAN 1) and the ZD sees all packets as untagged.
As a result, the AP does not need to be aware that it's management packets will arrive on VLAN 200 and the ZD does not need to be aware of any VLAN tagging.

note: you should not attempt to place any wireless clients (laptops, phones, SSIDs) in your VLAN 200.
You should create additional VLANs to carry client/SSID traffic.