Let's face it, Ubiquiti always has a way of "accidentally" breaking any other vendor from being compatible with one of their features. I am sure it takes a lot of Netonix time to out-guess them.
But I like good old Ubiquiti Discovery tool. It's easy and informative to use. At least the PC version that doesn't try to screw with the WS-xx-www-xx device type still plays nice.
What I am reporting here is that with Ubiquiti Discovery enabled on each WS, (let's say v1.5.6) I can run the tool against the WS and it will display it and all of the UI devices attached to it.
If the first switch then has a second WS directly attached on the same VLAN, again both WSs and all their attached UI radios are listed.
BUT if the two WSs are connected via a T trunk port ... the closest one to the PC shows up, all the UI devices across on the common VLAN on both WSs show up the way they should...
But alas, the second WS itself does not show up on the PC list over the trunk. :(
WS no UI Discovery reply over VLAN trunk
-
Stephen - Employee
- Posts: 1030
- Joined: Sun Dec 24, 2017 8:56 pm
- Has thanked: 85 times
- Been thanked: 181 times
Re: WS no UI Discovery reply over VLAN trunk
Hello JustJoe,
To make sure I understand what you're saying:
|PC | <===> | port 2 (vlan1, U) WS-A port 1 (vlan 1, U) | <=====> | port 1 (vlan1, U) WS-B |
With the above setup, the PC discovery tool is able to see the discovery broadcasts of both WS-A and WS-B but:
|PC | <===> | port 2 (vlan1, U) WS-A port 1 (vlan 1, T) | <=====> | port 1 (vlan1, T) WS-B |
Now the Discovery Tool on the PC is only able to see WS-A.
Is that correct?
To make sure I understand what you're saying:
|PC | <===> | port 2 (vlan1, U) WS-A port 1 (vlan 1, U) | <=====> | port 1 (vlan1, U) WS-B |
With the above setup, the PC discovery tool is able to see the discovery broadcasts of both WS-A and WS-B but:
|PC | <===> | port 2 (vlan1, U) WS-A port 1 (vlan 1, T) | <=====> | port 1 (vlan1, T) WS-B |
Now the Discovery Tool on the PC is only able to see WS-A.
Is that correct?
-
JustJoe - Experienced Member
- Posts: 266
- Joined: Sat Aug 02, 2014 11:33 pm
- Has thanked: 94 times
- Been thanked: 59 times
Re: WS no UI Discovery reply over VLAN trunk
Stephen wrote:Hello JustJoe,
To make sure I understand what you're saying:
|PC | <===> | port 2 (vlan1, U) WS-A port 1 (vlan 1, U) | <=====> | port 1 (vlan1, U) WS-B |
With the above setup, the PC discovery tool is able to see the discovery broadcasts of both WS-A and WS-B but:
|PC | <===> | port 2 (vlan1, U) WS-A port 1 (vlan 1, T) | <=====> | port 1 (vlan1, T) WS-B |
Now the Discovery Tool on the PC is only able to see WS-A.
Is that correct?
Hi Stephen, yes, that is exactly correct. :)
And it is not only the "infamous" VLAN1 , but any VLAN ID.
Also, in either of your examples, the all actual ubiquiti devices on any of the other ports of WS-B in VLAN1 are visible to the PC.
-
Stephen - Employee
- Posts: 1030
- Joined: Sun Dec 24, 2017 8:56 pm
- Has thanked: 85 times
- Been thanked: 181 times
Re: WS no UI Discovery reply over VLAN trunk
Understood, thanks for the additional details.
I've added it to my list of things to look into.
I've added it to my list of things to look into.
-
JustJoe - Experienced Member
- Posts: 266
- Joined: Sat Aug 02, 2014 11:33 pm
- Has thanked: 94 times
- Been thanked: 59 times
Re: WS no UI Discovery reply over VLAN trunk
BTW I chuckle when sometimes running UI Discovery from one of their radios GUIs ...
I have seen some of their model-firmware versions will insult the WS by displaying it as a frickin' "ToughSwitch"
... that should be grounds for a defamation of character lawsuit ! ;)
I have seen some of their model-firmware versions will insult the WS by displaying it as a frickin' "ToughSwitch"
... that should be grounds for a defamation of character lawsuit ! ;)
-
Stephen - Employee
- Posts: 1030
- Joined: Sun Dec 24, 2017 8:56 pm
- Has thanked: 85 times
- Been thanked: 181 times
Re: WS no UI Discovery reply over VLAN trunk
JustJoe wrote: have seen some of their model-firmware versions will insult the WS by displaying it as a frickin' "ToughSwitch"
Now I've gotta see that for myself
8 posts
Page 1 of 1
Who is online
Users browsing this forum: Google [Bot] and 23 guests