Netonix Forums

Please post comments and report bugs with v1.4.2rcX in this thread

v1.4.2 wrote:FIXED
- Fixed SFP Stats for WS-10-250-AC - rc4
- Fixed Disabling Discovery Tab in the UI so it actually disables the service - rc4

ENHANCEMENTS
- Added option to disable IGMP querier per VLAN if IGMP snooping is enabled - rc4
- Increased the acceptable voltage ranges to prevent false alerts - rc4

KNOWN ISSUES
- Some language templates need help
- Some people still report high CPU usage with Discovery Tab enabled

Released 6/02/2016

Hey Chris, i upgraded to latest v1.4.2rc4 that was smooth.
The only (maybe only visual) issue was the notice about a missing variable that can bee seen in the text during the upgrade process.

Code: Select all

Uploading firmware file ...
Unpacking firmware ...
sh: missing ]
/usr/bin/firmware_upgrade: line 150: WS-12-250-AC: not found
Running preflash script ...
Unlocking /dev/mtd8 ...
Writing from redboot_recovery_config to /dev/mtd8 ...
Unlocking linux ...
Writing from kernel.img to linux ...
Updating FIS entry linux
Unlocking FIS directory ...
Writing from fisdir to FIS directory ...
Unlocking Redundant FIS ...
Writing from redundant_fisdir to Redundant FIS ...
Unlocking rootfs ...
Writing from rootfs.img to rootfs ...
Unlocking /dev/mtd8
The interface will reload when the reboot is complete


Thank you in overall for your F/W work and effort.

We finally figured out what was causing the HIGH CPU utilization with v1.4.X with the Discovery Tab enabled.

v1.4.2rc6 fixes this, we need people to confirm rc6 so we can finalize rc6 for the next production batch.

I'm running 1.4.2rc4 on a switch with no issues (resolved STP and discovery problems), what's changed in rc6?

sporkman wrote:I'm running 1.4.2rc4 on a switch with no issues (resolved STP and discovery problems), what's changed in rc6?

We have release notes where you download it

v1.4.2 wrote:FIXED
- Fixed SFP Stats for WS-10-250-AC - rc4
- Fixed Disabling Discovery Tab in the UI so it actually disables the service - rc4
- Fixed HIGH CPU utilization wen Discovery Tab was enabled - rc6
- Fixed port watt useage on the WS-8-150-DC - rc6

ENHANCEMENTS
- Added option to disable IGMP querier per VLAN if IGMP snooping is enabled - rc4
- Increased the acceptable voltage ranges to prevent false alerts - rc4

KNOWN ISSUES
- Some language templates need help - please contact us to help

Released 6/06/2016

How many people are running 1.4.2rc6 and is it safe to push out to our network?

1.4.1 sounds like there are too many bugs of significance to push this out as a stable release to our network?
(CPU utilisation issues & discovery tab not working in particular - we also use SFPs in some WS-10-250-ACs)

bmv wrote:How many people are running 1.4.2rc6 and is it safe to push out to our network?

1.4.1 sounds like there are too many bugs of significance to push this out as a stable release to our network?
(CPU utilisation issues & discovery tab not working in particular - we also use SFPs in some WS-10-250-ACs)

The only real BUG in v1.4.1 is the Discovery Tab "if" Enabled will cause HIGH CPU utilization for "some" people who have many CDP enable devices on their segment. The bug was with if a corrupted CDP packet could caused our routine to get into an infinite loop and consume CPU which had nothing to do with packet switching. The more CDP devices the higher percentage chance it could affect you and the poorer your wireless links with the ability to corrupt a packet also increased this chance. Now v1.4.0 allowed this bug to impact LACP and STP but that was prevented in v1.4.1 but the HIGH CPU usage remained IF the Discovery Tab was enabled but switching performance was not impacted. Disabling the Discovery Tab made the version run just fine.

The SFP in WS-10-250-AC BUG would only prevent you from seeing the stats on the port not crash your network.

v1.4.2rc6 fixes the Discovery Tab BUG with CDP active devices and HIGH CPU use.

Why not do this:
1) Roll out v1.4.2rc6 to an easy to access switch and let it run for a day then report back.
2) Roll it out to another switch and let it run and then if it is OK finish your roll out if you want.

rc4 fixed my high CPU issue, but of note, I have zero devices with CDP enabled. As a general rule I disable CDP on ubiquiti devices, and the one cisco device does have it enabled, but I'm assuming CDP was not enabled on the Netonix.

Just a datapoint since I was seeing the bug but didn't fit the profile (CDP devices, large, flat network).

sporkman wrote:rc4 fixed my high CPU issue, but of note, I have zero devices with CDP enabled. As a general rule I disable CDP on ubiquiti devices, and the one cisco device does have it enabled, but I'm assuming CDP was not enabled on the Netonix.

Just a datapoint since I was seeing the bug but didn't fit the profile (CDP devices, large, flat network).

To be CLEAR the high CPU useage was fixed in v1.4.2rc6 NOT v1.4.2rc4

The fact that some people never had the CPU useage is probably why you do not see it with v1.4.2rc4, personally I never saw it on my network even with v1.4.0 but the bug was there and could rear its head at anytime.

You should upgrade to v1.4.2rc6