v1.3.9 FINAL bug reports and comments

[RebusCom]

Ok, I got it set to 5s. It seems to work ok. What kind of errors/problems are you seeing?

BTW, I did notice a note in PRTG that says anything less than 10 seconds may not work and is not officially supported.

The symptom which started with v1.3.9 (PRTG settings unchanged) is that the reported port throughput alternates between actual and zero.

[RebusCom]

The symptom which started with v1.3.9 (PRTG settings unchanged) is that the reported port throughput alternates between actual and zero.

To avoid this issue entirely the polling interval can be no shorter than 15 sec. This is with an aggregate traffic level around 150-200Mbps.

[Eric Stern]

To avoid this issue entirely the polling interval can be no shorter than 15 sec. This is with an aggregate traffic level around 150-200Mbps.

Whats the average CPU usage on the switch?

[Uintadave]

I am still having watchdog fail after about 3 days. I have some problems with some sectors that keep losing connection on their Ethernet side. after the 2 day and 22 hour mark of uptime on the switch the watchdog stops functioning.

To get watchdog back I have to ether start the service back up with the CLI or reboot the switch.

Does the watchdog service need a watch dog on it?

[lligetfa]

Does the watchdog service need a watch dog on it?

Too funny!

[nasked]

At the moment only problem with mac table. Web interface is empty...and buttom is running...only after enter by CLI and make a show mac table...show me mac information in CLI and web interface, but only a few host has ip....many host are unknow ip address..

[sirhc]

At the moment only problem with mac table. Web interface is empty...and buttom is running...only after enter by CLI and make a show mac table...show me mac information in CLI and web interface, but only a few host has ip....many host are unknow ip address..

Try v1.4.0rc3

FIXED
- Fixed SNMP reported uptime - rc2
- Fixed rare problem with mac table not loading - rc3
- Fixed small UI issues with Firefox and IE - rc3

ENHANCEMENTS
- Increased MAX allowed DC input voltage for WS-8-250-DC and WS-12-250-DC to 61.5V for off grid solar sites - rc2

KNOWN ISSUES
- None

rc3 Released 2/11/2016
rc2 Released 2/06/2016

[RebusCom]

To avoid this issue entirely the polling interval can be no shorter than 15 sec. This is with an aggregate traffic level around 150-200Mbps.

Whats the average CPU usage on the switch?

<25%

[cwachs]

Potential issue with SNMP. Have been monitoring our WS-10-250-AC running 1.3.9 with PRTG. I have 5 SNMP Traffic monitors set up - on 5 different ports. Working great for 2 weeks. Today, without provocation, the SNMP traffic monitoring off all 5 ports stopped at the same time. PRTG reported those as unreachable. I was getting SNMP traffic from a bunch of devices on the other side of the switch. Pings to the switch were fine. No other issues with the switch other than SNMP stopped.

No log entries at all for today on the Netonix (not unusual but nothing about SNMP stopping). The only way to get them back was to turn off SNMP on the switch and then turn it back on again. Everything has been fine since.

Error in PRTG: "No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003)"

[ehsab]

I just noted that the switch reports "vlan 1" to syslog when infact the Management vlan has been changed to another number.
That might have been fixed in earlierar versions though, i don't have the possibility to upgrade the switch at the moment and thought i would mention it.

Kind Regards
M