Ever wanted/needed to change the DTIM interval on your SSID beacons with Ruckus? Well you can’t – Not from the GUI at least (as of vSZ code rev 3.5). Why would you want to one might ask? And a valid question indeed. Specralink best practices for most WLAN VoIP solutions recommends a DTIM setting of 2. See here and here for more info. Increasing the DTIM can also help improve battery life in some devices as it allows a device to snooze for longer a duration when not needing to transmit/receive traffic. Traditionally a device needs to be awake for every DTIM interval or for every beacon in most default environments. But by adjusting the DTIM interval, traffic is buffered at the AP for users for the duration of the DTIM and the clients can take a nap and wake up just prior to the necessary beacon to be able to receive (or request) their traffic.
Alas, it can be done directly at the CLI of the AP(s). From the vSZ,
From the CLI of the vSZ, you have to the following commands. Sadly, at the moment, I’m not sure how to do this in mass, but will continue to dig for a better solution.
vSZ# remote ap-cli <mac address of AP connected to vSZ> “get wlanlist”
This command will tell you the WLAN that your specified SSID is attached to. From there, you will need to reference that in the next command.
vSZ# remote ap-cli <MAC> “set dtim-period wlan#(from the prior command) <DTIM interval value desired>” – It’ll look something like this.
vSZ# remote ap-cli aa:bb:cc:aa:bb:cc “set dtim-period vlan25 3”
After that, you should see a return from the CLI of “OK”. To verify things, you can just change the “” command to say get “dtim-period wlan25”. The following should be returned.
Wlan25 DTIM Period: 3
As I stated prior, the unfortunate thing is that this option is a 1 by 1 approach. I believe we can use AP-CLi scripts to automate this somewhat (which is under the diagnostics page now on the left) and will try to update or follow up on this once I’ve been able to test the scripting functionality more.
Hope this helps if you ever need to change the DTIM interval with a Ruckus solution.
Here are a few other “get/set” commands that can be ran on the APs to get some useful information returned that may or may not actually show in the GUI.
|get scg||Shows the info of the mgmt platform the device is attempting to connect to|
|set scg ip <ip address>||Sets the IP address of the mgmt platform for the device to attempt to connect to|
|get boarddata||Shows hardware info (MAC, SNs, etc.)|
|get uptime||Shows uptime of device|
|get lldp neighbors||Shows LLDP neighbor info|
|get device-name||Shows hostname of device|
|get macbd ethx (where x is 0 or 1)||Shows learned MAC addresses on specified interface|
|get model-display||Shows AP model information|
|get netstats <interface name>||Gets netstat info for specified interface (all interfaces if left blank)|
|get ntp||Shows currently configured ntp settings|
|get version||Shows version of AP (similar to get model-display command)|
|get ipaddr wan||Shows current IP info of device (IP, Subnet Mask, Default Gateway).|
|get channel wifix (where x is 0 or 1)||Shows currently set channel for selected radio (0 = 2.4 GHz, 1 = 5 GHz)|
|get wlanlist||Shows list of all available WLAN/SSIDs on selected device (wlan0 – wlan47, each are uniquely tied to a single SSID)|
|get station wlanxx list||Shows all available client devices connected to a specified SSID (wlanXX – where XX is the number of the wlan for the particular SSID in question)|
|get radiostats wifix (where x is 0 or 1)||Shows detailed radio statistics for the specified radio|
|set factory||Sets the AP to factory default after next reboot|
|reboot||Reboots the device|