cancel
Showing results for 
Search instead for 
Did you mean: 

VSZ Search By VLAN

simon_brazell
New Contributor

We use Dynamic VLANS very frequently with our RUCKUS builds and it's rather helpful to sort by VLANs when troubleshooting client issues. I think the only way it could be better is if we could also search for devices on a specific VLAN in the clients section of the VSZ. Is this something that could happen in the future?

8 REPLIES 8

I appreciate that you're trying, but this is what I'm referring to:

Image_ images_messages_6181a9fbfb751956f53205fe_6a590121d08a66b8467e04a18ce611f6_example-5356658b-e6ed-4f21-9ee0-ef5b8dc4bbe5-1944000603.png
I know there are several devices in the zone I'm looking at currently that use VLAN 202, but when I query that number, these are the only two that show up.
Image_ images_messages_6181a9fbfb751956f53205fe_3be710abd69a4165444fe5f7cded35ec_Example2-fae94a78-bee2-41b2-998b-3655b0ae6359-31573859.png
Seen here is when I have nothing in search in the same zone but sorted by VLANs so I can see all entries on VLAN 202 grouped together. But I have to filter through all the other VLANs to get here. 

I would instead like to just search 202, or maybe even specify VLAN:202 somehow and then only get results that meet that specific query.

As a matter of fact, it doesn't even show the VLANS that I want that match 202. Below I unchecked every option except VLAN and searched and didn't get anything remotely close to what I wanted. 
Image_ images_messages_6181acb43a5e841cb239f9ae_7475f716c812b00e751b6675b444158d_example3-bde7ff16-f3b1-4236-a10c-b60e5489c1b1-131822908.png

Hello Simon,

That is strange, it worked for me.  You do need to remember to click the Magnifying Glass icon after entering "202" in the search box.  It should then highlight the VLAN # in table below.

If it isn't working, perhaps the version of sz is out of date?  Otherwise, you may want to connect with TAC for further assistance.

Hi Sunny,

Thanks for spending some time looking at this for us. We have several versions of the vsz in production and to my knowledge, the issue my colleague Simon pointed out is present on all of them.

5.1.2.0.302
5.2.2.0.317
6.0.0.0.1331

If you could tell us what version you are using, it may shed some light on the issue for us.