v1.5.25 Bug Reports and Comments

[Stephen]

The netonix manager version 1.0.21 is now out.

It fix's all the issue's we where able to replicate with the latest 1.5.25 switch firmware, this includes:
- opening web interface for selected switch from the manager in a new tab.
- opening web console for selected switch from the manager in a new tab.
- fix several formatting problems that occur when running switch's with latest firmware
- restructured device table to prevent formatting problems when switch's toggle online state (this is not related to 1.5.25 but rather another inconvenience we found while testing)


PLEASE NOTE:

Due to the nature of one of the incompatibilities in the netonix manager 1.0.20 or below with the latest 1.5.25 switch firmware.
You will probably not be able to upgrade the manager with the built-in update system because one of the running process's created to do this will crash if monitoring a 1.5.25 switch.
Instead you'll have to upgrade it manually:

Netonix Manager Software


If you do not have any switch's with firmware >1.5.17 then the normal upgrade process available in the manager should work fine.

[mnitech]

I have been using a old tool called RANCID to back up the configuration of Netonix units in text format. I have some simple scripts to analyze the configurations and prepare reports.

Switching from 5.16 to 5.25 causes some of the reports to break. The configuration file is slightly different. Maybe a space is gone or a comma is now there.

its not a problem to fix things but it was upexpected.

[RebusCom]

The 1.0.21 version still needs only node.js version 8.x or later to run? (Current is 23.x)

[Stephen]

The 1.0.21 version still needs only node.js version 8.x or later to run? (Current is 23.x)

I actually didn't have any problems running this on v20.15.1, officially however it is still on 8.x but it's worth trying on a later version if you don't want to deal with 8.x

[RebusCom]

I actually didn't have any problems running this on v20.15.1, officially however it is still on 8.x but it's worth trying on a later version if you don't want to deal with 8.x

The reason I ask is I'm actually presently running 1.0.20 on v16.13.0 of node.js. I'm hesitant to replace it with v2x.x because I have another critical js app that's shall we say, delicate, critical, and sadly no longer supported or tested with newer versions. Consequently I'm reluctant to risk an upgrade of node.js if I don't have to. I'm going to assume in-place upgrade of the manager will be fine with the existing v16.13.0 node.

[sirhc]

We did a quick fix on manager to properly deal with v1.5.2X

We need to get back on WS3-14E line.

Trust me Stephen has been chomping at the bit to completely rewrite manager for a long time and it will be discussed at some point in future.

We need to sell 5M in inventory of WS line then get WS3-14E line in production.

This will allow hiring more people and getting more done.

The last 4 years recked havoc on us and many small businesses I'm just glad we survived many did not.

[Viv]

Thanks for updating the netonix manager and looking forward to the complete rewrite version soon.

Apparently, we are encountering a very strange issue with 1.0.20 as well as 1.0.21 @Yahel have asked to post it here. We did manual upgrade of netonix manager from 1.0.20 to 1.0.21 there was a UI issue which only show 5 Netonix in the list (see screenshots) we have close to 80 of them and that seems to be persistent even after upgrade. After restart of service we see the full list but as it start getting update from netonix it again reduce to 5 only. Is this a known issue? Do you have fix?
If this is new, then We are going to a fresh install of the netonix manager on a new VM and then add all netionix again.

Thanks,

[sirhc]

Can anyone else confirm the above issue or state they do not see the issue.

If multiple people see this issue i will move it up on list.

Please report info such as windows or Linux flavor, OS version, number of switches in manager, all updated to v1.5 25 or mixed (why as v 1.5.25 is best vetsion) and so on.

[mfwbooks]

We did an inplace upgrade of Netonix Manager on Ubuntu Linux from 1.0.20 to 1.0.21.
The new version resolved the issues were were having. Formatting looks good. All of our switches show up (firmware at 1.5.22, 15.24, or 1.5.25). We can use the Web UI and Console buttons again.

Thanks for getting this fixed.

[sirhc]

Thanks for updating the netonix manager and looking forward to the complete rewrite version soon.

Apparently, we are encountering a very strange issue with 1.0.20 as well as 1.0.21 @Yahel have asked to post it here. We did manual upgrade of netonix manager from 1.0.20 to 1.0.21 there was a UI issue which only show 5 Netonix in the list (see screenshots) we have close to 80 of them and that seems to be persistent even after upgrade. After restart of service we see the full list but as it start getting update from netonix it again reduce to 5 only. Is this a known issue? Do you have fix?
If this is new, then We are going to a fresh install of the netonix manager on a new VM and then add all netionix again.

Thanks,

Screenshot 2025-01-16 at 7.24.46 PM.png

What ranges of firmware are you using?
If a wild mix possibly try upgrading all to v1.5.25 (best firmware we have)

If all are v1.5.22 or higher then possibly you have corrupted install or config which may require removing all files and re-install from scratch?