v1.5.3rcX Bug Reports And Comments

[Stephen]

FIXED/CHANGED
- fixed issue with watchdog poe bounce that was not completely shutting off power depending on the delay time and offset's used

ENHANCEMENTS
- Modified Port Bounce option to read 'Port Bounce POE' and added 'Port Bounce Link' manual option for status and ports tab
- Option in discovery configuration now exists to disable the switch from broadcasting on discovery protocols while the discovery tab is enabled
- link bounce option exists for the watchdog as well as the POE bounce option.

KNOWN ISSUES
- WEB UI issues when not at 100% Zoom on browser especially on VLAN TAB
- Some language templates need help - please private message Eric Stern to help

Released 5/13/2019

[Omniflux]

I think the discovery settings are still not ideal. What would make sense to me would be:

On the configuration page I set which protocols I want the switch to announce itself on.

On the discovery tab, I set which protocols I want to filter by (why do we need to configure which protocols to listen to? does it use too much memory on large networks to listen to all protocols all the time?).

[Stephen]

On the configuration page I set which protocols I want the switch to announce itself on.

I can still do this, I thought you wanted a global switch when I read the feature request last time.

(why do we need to configure which protocols to listen to? does it use too much memory on large networks to listen to all protocols all the time?

That has been debated for some time. It was a precaution done to try and circumvent that as a possibility and also some people where saying that it was counter-intuitive the way it worked before.

[Omniflux]

On the configuration page I set which protocols I want the switch to announce itself on.

I can still do this, I thought you wanted a global switch when I read the feature request last time.

It wasn't my request, so perhaps this actually is what they wanted, but I think a complete separation of the two features makes more sense.

[TheNet]

HI,
recently i did upgrade of WS-12-250-DC and WS-8-150-DC to firmware 1.5.3rc1 and since then it can not pool time from any ntp server even by using ip address or local ntp server. Any idea how to fix that?

[Stephen]

There is a confirmed issue right now that causes NTP to fail when using DHCP, if you are using it try switching to a static IP address. The next release will have this bug dealt with.

[TheNet]

I did tested everything and wrote previously that i did tested and even static address of ntp server does not work.

[lligetfa]

I did tested everything and wrote previously that i did tested and even static address of ntp server does not work.

No, it is the Netonix switch that needs a static IP.

[Stephen]

lligetfa is correct, I meant that if your netonix switch is set to use DHCP then NTP will not work because of this bug. Please try changing it's IP to static until this is resolved.

[dray]

Few issues I am seeing with 3 test bench netonix all running 1.5.3 rc1:

Sometimes when I make vlan config changes, I lose access to netonix, timer runs out, and still it does not revert. A hard reboot will make the switch mgmt accessible and changes are retained.

What is status of MSTP?

I am testing a simple 3 switch ring. I have tried default vlan 1 in CIST and Instance 1. Vlan 1 always fails. When I break (unplug various cables around) the ring, everything will become active, when I plug the cable back in, sometimes it will stay working, sometimes it will break. I am pinging all three switches from outside the ring and with a laptop within.

Tagged vlans on instance 2 appear to be working so far.

The exact same config when switched to RTSP works as expected.

Making changes to MSTP Instances may need a reboot to apply config correctly.


UPDATE: It looks like when I exclude a T on say vlan 2, that is all around the ring also, untagged default vlan 1 starts working. Maybe tagged traffic from other vlans are still counting as default vlan 1 in CIST??