F

6 Messages

 • 

132 Points

Wed, May 12, 2021 9:09 PM

Unleashed VLAN on WLAN :)

Hi!

(I'm not sure about policy for reviving old threads, so instead of replying to this old thread, https://forums.ruckuswireless.com/conversations/ruckus-icx-switches/ruckus-unleashed-vlan-setup/5f91c3f3135b77e2478f6cb2, I'm starting a new. Feel free to move it, if that's better.)

I'm new to Ruckus, just got my hands on a ZoneFlex R510.

It's running Unleashed and I'm trying to figure out if I can fit it into existing VLAN structure.

From the above mentioned thread/topic, it seemed it should work if I;

- Connected ethernet (Port 1 or 2) to a switch port configured to delived admin VLAN untagged and the other VLAN's tagged

So I did/tried to do this, and the Ruckus AP gets an admin IP on the network interface, so far so good.

Then configuring the SSID, I enter Advanced, then WLAN Priority and then enter my office VLAN number in the Access VLAN field.

Then it does not seem to work. (I get no DHCP offer through to my client on that WLAN.)

Something I'm missing?

How/where to debug?

My switch is a non-Ruckus switch, configured to deliver admin VLAN as untagged/PVID and three other VLANS as tagged to the Ruckus AP.

(If unleashed is not really up to VLAN'ing, should I use other firmware? What software/hardware/licence is required to manage this in another fasion/way?)

EDIT:

As it seems, just after posting, I realized the switch port (with it's ingress filtering on) was set to admit only untagged and priority tagged. As soon as I switched it to admit all it started working. :-)

Official Solution

Official Rep

 • 

1.2K Messages

 • 

17K Points

5 m ago

Hi Filip,

Configuration looks good to me but I am again sharing the general points for multiVLAN configuration with Unleashed.

1. Switch port should be in trunk mode.

2. Tag any additional VLAN on which you want to configure your WLANs. AP will get IP on default/untagged VLAN and same cannot be changed.

3. Configure correct VLAN under WLAN's advanced settings. Anything other than 1 is tagged. VLAN 1 is Untagged, when configured under WLAN advanced settings.

4. If you are using relay agent/IP helper, check and make sure it is configured correctly on network nodes.

5. DHCP server pool.

If above all looks good an if you are still facing the issue, take packet capture or run Troubleshoot utility on Unleashed, see at what point connection is failing.

If discovery is sent out from the AP, issue is mostly with network or DHCP.

6 Messages

 • 

132 Points

Wow, you guys reply quickly. :-D

As it turned out, as mentioned above, the switch port was filtering too much.

Official Rep

 • 

1.2K Messages

 • 

17K Points

Good to know that you figured it out!

Regards,

Syamantak Omer

Official Rep | Staff TSE | CWNA | CCNA | RASZA | RICXI

Follow me on Linkedin

16 Messages

 • 

210 Points

5 m ago

Is your access point connected to an untagged port on the switch? Unleashed works with vlans, just the management needs to be untagged.

6 Messages

 • 

132 Points

Yes, it has the admin VLAN untagged.

I was about to update my original post just before I realized I already had a reply.

As it seems, just after posting, I realized the switch port (with it's ingress filtering on) was set to admit only untagged and priority tagged. As soon as I switched it to admit all it started working. :-)

Now I only wonder if I need a Management Interface IP defined as well ... As there's no VLAN setting there, the management interface and regular interface would be on the same untagged VLAN ... Or can I define Port 1 and Port 2 to serve different purposes?

(Sorry if this is too basic stuff, I should get around to read more in the User's Guide etc. I just got this AP earlier today.) :)

455 Messages

 • 

5.6K Points

5 m ago

This is typical thing with part of the switches -- it's not enough to add tagged VLANs to the port, you must allow them, otherwise they traffic is dropped.

I don't understand question about additional Management interface -- do you mean on AP? You don't need more than 1 IP on AP for sure...

6 Messages

 • 

132 Points

@eizens_putnins Well, there's a separate setting where you can define a separate Admin IP and netmask (but no VLAN setting). Looks like it's meant for SNMP etc. But as there is no selection there or in the main IP address setting for VLAN, or to choose which ethernet port to use for regular and admin IP, I don't really understand the point of this admin IP setting ... (I'm sure it has it's use, even if I don't see what it is ...) :-)

A slightly different issue I have now:

This is a non-unleashed AP (p/n starts with 901- and not 9U1-), but I figured that I wanted to try Unleashed first, so I downloaded and installed the unleashed firmware.

Then I thought I would go back and install and try out the standalone firmware for this R510. After searching the closest I find is Software Version 114.0.0.0.5585, the title says it's for R550, but the text/tag includes R510. But the issue for me is that I need to be a Premium Support User* to download it. So, seems I'm stuck with Unleashed/won't be able to revert/switch back to standalone AP mode.(?)

(Unleashed version is 200.9.something ...)

* I'll try to check out what premium support user means. Not sure I qualify, as this AP, though new, had been in stock since 2018 before I got it with a nice rebate.

(edited)

455 Messages

 • 

5.6K Points

5 m ago

1. For my understanding you should be able to download standalone firmware without premium status. Probably  syamantak_omer will be interested to look why everyting on portal start to be in unpublic part. I think it shouldn't be so.

  Anyway, standalone  is just a basic software, in practice mainly used as intermediate when converting between SZ, ZD and Unleashed firmwares. You'll have much less featurs in standalone mode.  If Unleashed works for you, stay with it...

By the way, if this AP was never registered, I think you can register it for warranty and get access: https://support.ruckuswireless.com/warranty_registrations/new .

It is possible, that to access firmware you have to register your hardware, it makes sense actually.

2. You definitely  don't want to load different model firmware to your AP, as it will most probably permanently brick it and  even void warranty.Hopefully, AP are supposed to not allow loading wrong firmware file, but I know that it can be done, as I know user who bricked AP this way by mistake.

I don't believe R550 and R510 can share firmware, as R550 has different chipset, it is 802.11ax AP, when R510 is 802.11ac.

Correct link for latest R510 standalone firmware seems to be https://support.ruckuswireless.com/software/2765-ruckus-solo-access-point-114-0-0-0-6565-ga-software-release-r510

Some standalone releases in the past were published as one big zip file, including firmware images for all supported APs, so you needed to download archive, expand it and find proper file, but this is not the case. Link for R550 firmware is https://support.ruckuswireless.com/software/2764-ruckus-solo-access-point-114-0-0-0-5585-ga-refresh2-software-release-r550,  so they are not the same.

6 Messages

 • 

132 Points

Thanks again! :) Great answers!

@eizens_putnins wrote:

Anyway, standalone  is just a basic software, in practice mainly used as intermediate when converting between SZ, ZD and Unleashed firmwares. You'll have much less featurs in standalone mode.  If Unleashed works for you, stay with it...

Being new to the Ruckus universe, trying to read up on the tech, reading this product guide, it looks like ZD/ZoneDirector is meant for 50-150 AP's. And then SZ/SmartZone for even larger deployments? (Not sure if SmartZone and RUCKUS Cloud is the same, or not related.) But I/we would probably be best served sticking with unleashed.

Only reason for testing standalone would be to check VLAN settings, and to see if there is more fine grained control of radio usage, channels etc. (Unleashed is hiding most advanced controls, it seems.)

455 Messages

 • 

5.6K Points

Most advanced RF settings are available mainly from CLI both in unleashed and standalone mode, SZ and ZD provide more detailed control, but still some things need to be done on AP through CLI.

But you really rarely need them (mostly only to fix some specific issue or in a very specific environment).

6 Messages

 • 

132 Points

Ah, there's a CLI, thank you! :-)

Important Announcement