v1.5.2 Bug Reports and Comments

[IntL-Daniel]

In current way of Discovery tab it is impossible to scan network without visibility of the switch itself (unitl 1.5.1 it was)

[Stephen]

Could you elaborate on this a bit?

I'm afraid I don't completely understand what you mean.

[IntL-Daniel]

Unitl 1.5.1 - I was able to enable Discovery tab without any selected protocols and monitor our network for discovery enabled devices while the switch itself was invisible. Currently I cannot, I have to enable some protocol what I want to scan and that protocol is also enabled on switch itself for discovery.

[Stephen]

Ah I see,

This was actually a feature request, to allow people to select which protocol was being searched for instead of all of them being searched for regardless of which protocols where enabled.

I can add an option on the next release to allow you to disable whether or not the switch is broadcasting on the enabled discovery protocol if you want.

[IntL-Daniel]

yes that would be the best way of the solution, thanks

[tonym]

Any chance we could get a longer port description field?

It seems to be limited to 26 right now. 64 would help a lot and 128 would be more than enough :)

[IntL-Daniel]

Any chance we could get a longer port description field?

It seems to be limited to 40 right now. 64 would help a lot and 128 would be more than enough :)

I had asked for that years ago but they told me it would be a problem...too many dependecies probably...

[sirhc]

No the issue is it does not fit in the field of view so it would be displayed chopped.

[noc@ethoplex.com]

We had a strange situation with a WS-12-250-AC & 1.5.2 this week.

We upgraded the switch to 1.5.2. overnight. The next morning, we got complaints from customers connected through the wireless link powered by the Netonix.

We have been troubleshooting the last few days. Speed were so poor that I couldnt upgrade the netonix on the other side of the link to 1.5.2 (as part of the troubleshooting).

We upgraded the far switch, made no difference. What corrected the issue? Downgrading to 1.5.0. The link is now performing as it was prior to the upgrade to 1.5.2. (The other netonix (WS-12-250-AC, as well) on the far side is still at 1.5.2 btw).

We have upgraded a few switches to 1.5.2, with no negative effects.

The wireless link is a UBNT AF5XHD on 1.1.2 fw.

Any thoughts as to what might have happened?

[Stephen]

If you see it again drop into the bash shell and run top, check to see if multiple 'switch' processes are running.

There is a bug we have been working on for awhile hunting down that has apparently been there for a long time that sometimes causes the switch to boot up with two instance's of the 'switch' process to run. It happens extremely rarely but it does happen. It has been known to cause strange side-effects.

If you see that, just killing one of the extra switch processes will fix it. (It doesn't matter which one)