topic Re: Add LLDP support to Ruckus devices in ZoneDirector

Add LLDP support to Ruckus devices

chris_wooddell — Mon, 30 Sep 2013 23:52:13 GMT

This has been an enhancement request open since Jan 27, 2009 3:14pm on the old website.

Not having LLDP support is a major downside for devices positioned as players in the enterprise space. It's about five years since the standard was finalized, and this is a critical infrastructure management protocol. Please prioritize this.

Re: Add LLDP support to Ruckus devices

dave_burns_5993 — Fri, 04 Oct 2013 17:25:16 GMT

I too have asked my sales rep for this feature. I have over 500 APs deployed, with another ~300 on the way, having lldp would be just about the best thing i could ask for.

Re: Add LLDP support to Ruckus devices

peter_dohm — Mon, 07 Oct 2013 02:58:08 GMT

considering linux is the basis of the device, this seems appropriate:

http://open-lldp.org/

Re: Add LLDP support to Ruckus devices

andrew_larsen_6 — Tue, 08 Oct 2013 16:21:09 GMT

I would also love to see this feature and urge it to be a top priority.

Re: Add LLDP support to Ruckus devices

point_of_presen — Thu, 05 Dec 2013 22:00:23 GMT

Us too!

Re: Add LLDP support to Ruckus devices

bill_burns_6069 — Thu, 09 Jan 2014 01:58:49 GMT

Me too.

Re: Add LLDP support to Ruckus devices

admin_cebuholdi — Fri, 14 Feb 2014 09:02:41 GMT

Re: Add LLDP support to Ruckus devices

bas_sanders — Sat, 22 Feb 2014 10:37:16 GMT

+1..!

Re: Add LLDP support to Ruckus devices

dave_burns_5993 — Wed, 05 Mar 2014 00:19:48 GMT

any updates to this? even my request is now 5 months old, let alone the original request being from ~2009. some kind of network discovery protocol is now almost REQUIRED for these to work in my environment. I need to be able to query my switches and find every Ruckus AP, not have to run macros against an OUI list and hope for the best.

Re: Add LLDP support to Ruckus devices

primoz_marinsek — Wed, 05 Mar 2014 14:15:55 GMT

It's actually quite funny. They have an OPT LED on all APs that seems to be there just to make up the numbers.

Re: Add LLDP support to Ruckus devices

matthew_ausmus — Thu, 06 Mar 2014 18:41:19 GMT

I just posted a question related to this. I'm doing a rollout for a school district and want to use a tool to automate diagraming so I want to find out what the APs support. I guess I can rule this one out for discovery purposes.

Add me to the list requesting LLDP support be added.

Re: Add LLDP support to Ruckus devices

heath_barnhart — Thu, 27 Mar 2014 15:15:57 GMT

I would like LLDP support as well.

Re: Add LLDP support to Ruckus devices

rich_kusak — Sun, 30 Mar 2014 18:30:06 GMT

LLDP - Yes please!

Re: Add LLDP support to Ruckus devices

jeff_roback — Mon, 07 Apr 2014 03:39:11 GMT

Me too!

Re: Add LLDP support to Ruckus devices

scott_sawin — Wed, 09 Apr 2014 23:27:44 GMT

I guess I was a tad surprised this was not already included. Please add

Re: Add LLDP support to Ruckus devices

keith_redfield — Thu, 10 Apr 2014 01:15:50 GMT

This is one of those features that keeps getting bumped in favor of others.

It's important to hit the +1 icon on the original post above (or other features you want to see) if you haven't already.

What would be helpful in the comments is use-cases (why it would be useful) or business-case (deals/installs lost) and that will help our product managers prioritize features better.

Re: Add LLDP support to Ruckus devices

andrew_larsen_6 — Thu, 10 Apr 2014 02:58:21 GMT

As a piece of network equipment, for a network engineer/administrator, LLDP is an indispensible tool for managing and troubleshooting a network. It's almost surprising that I would have to explain how incredibly useful it is, since every other major wifi network equipment manufacturer recognizes this and supports it. Devices which support LLDP will show up on a switch stating what they are (phone, switch, router, WAP, etc), what their IP address is, what their host name is, their firmware revision, manufacturer, etc. This is extremely helpful when you are trying to track down a device that isn't reachable, has failed a firmware update, isn't showing up on an expected port, etc. An incorrect IP address on a WAP means that somehow it got hard coded with a bad IP and may need to be set to factory defaults. A WAP that no longer shows up on the ZoneDirector that shows up on a port that isn't untagged in the native VLAN just needs to have the port reconfigured or be moved to the right port. The list goes on and on. It's a tool that greatly simplifies and speeds up troubleshooting.

Re: Add LLDP support to Ruckus devices

primoz_marinsek — Thu, 10 Apr 2014 08:14:03 GMT

Many times you do a predictive deployment where you specify where each AP should be placed. You document everything. Then when you go to the site to do some troubleshooting or doing a survey you need to check if they have done their job right.

Otherwise you could spend a lot of time solving the wrong problem. It's essential to start with the basics first and work your way up and checking that APs are at their right locations is usually the first step.

Re: Add LLDP support to Ruckus devices

dave_burns_5993 — Thu, 10 Apr 2014 15:23:11 GMT

As i previously posted (and has been repeated by all here) the ability to perform some basic discovery via automated tools that already exist and already read LLDP/CDP/etc is instrumental in problem solving and troubleshooting misbehaving APs.

For me specifically, because of the variety of switches (and levels of switches) I have deployed, frequently APs at a site will mesh, because 1 has determined that either its switch is closer to the default gateway(or spanning tree root bridge) or the port is 100Mb instead of 1Gb. When this happens, no MAC address shows on the port, but POE is being drawn...so then how to determine which AP is connected to which port? LLDP!

Re: Add LLDP support to Ruckus devices

matthew_ausmus — Sat, 26 Apr 2014 13:55:44 GMT

Most of my installations are larger scale: school districts, corporations and the like. At least 200 APs spanning multiple locations.

Business Cases:

From a VAR side: I use automated tools to map the network after a deployment. Without LLDP the APs get discovered (because they support SNMP) but they just hang in the ether. I still have to map connect the APs to the correct switch & port. This adds time and expense to the project both for the VAR and the client.

From the Client side: Clients use network monitoring tools like Solarwinds, WhatUP Gold and the like. These provide mapping functions as well that utilize LLDP. Again, when they run a discovery, the AP is found but just hangs in the ether. The IT team then has to manually create the connections adding more work where they shouldn't have it. When an AP is moved to a new switch port or replaced they have to do it again. IT teams have enough work on their plate without having to do this and it becomes a point against deployment of Ruckus Wireless.