Netonix Forums

Please post comments and questions on this firmware version here.

With 1.1.x considered "final", is there any work going into a user manual that aligns with the features and GUI? What is currently posted on the forum from last October is rather obsolete.

RebusCom wrote:With 1.1.x considered "final", is there any work going into a user manual that aligns with the features and GUI? What is currently posted on the forum from last October is rather obsolete.

I need to find some time to set down and work on the manual for the WISP Switch or find someone that would like to write the manual and cut a deal with them to write it.

Power readings don't seem to be right on 1.1.3:

Code: Select all

 Sand Hollow Netonix# sho status
System
------
Current Time: 12/31/1969 17:26:02
Uptime: 1562.430054 seconds
CPU Usage: 24%
Memory Usage: 28.43 MB
Firmware Version: 1.1.3
MAC Address: ec:13:b3:21:08:a4
IP Address: 10.250.73.2
IPv6 Address: fe80::ee13:b3ff:fe21:8a4
IPv6 Address: fe80::ee13:b3ff:fe21:8a4
Model: WS-12-250A

Power
-----
Board 48V: 12.9 Vdc
Board 24V (Ports 1 - 12): 6.6 Vdc
Board 3V: 0.3 Vdc

Thermal
-------
Board Temp: 40 C
CPU Temp: 54 C

Cooling
-------
Fan 1 Speed: 0 RPM
Fan 2 Speed: 0 RPM

 

I have just one device plugged in right now - A Solectec CM licensed backhaul. It's working fine, but again power reporting is low (I've seen similar with an airfiber24):

Code: Select all

 Sand Hollow Netonix# show interface status
Port Link PoE Watts
---- -------- ---- -----
1 1G-F 48VH 2.3
2 Disabled Off 0.0
3 Disabled Off 0.0
4 Down Off 0.0
5 Down Off 0.0
6 Down Off 0.0
7 Down Off 0.0
8 Disabled Off 0.0
9 Down Off 0.0
10 1G-F Off 0.0
11 Down Off 0.0
12 Disabled Off 0.0
13 Disabled
14 Down

 

There a bug on CLI for vlan management. If you use lowercase for tagged / untagged setting, it's accepted but vlan setting for this port won't work anymore.

Exemple, connected to port 11 on a switch with default config.

Code: Select all

Netonix Switch# configure
Netonix Switch(config)# vlan 1
Netonix Switch(vlan 1)# port 11 u
Netonix Switch(vlan 1)# exit

192.168.1.20 don't ping anymore

Code: Select all

Netonix Switch# configure
Netonix Switch(config)# vlan 1
Netonix Switch(vlan 1)# port 11 U
Netonix Switch(vlan 1)# exit

192.168.1.20 ping again

Edit: Firmware 1.1.3
CLI won't accept something else like "port 11 a" so I think it was desired to accept lowercase but forget to translate to uppercase in config.

Also, while tagging on a port range, all port after the first will be untagged.

exemple :

Code: Select all

(vlan 105)# port 1-12 T
(vlan 105)# exit
(config)# exit
#show config
...
 "ID": 105,
 "Name": "VLAN 105",
 "Enable": true,
 "Ports": [
 {
 "Status": "T"
 },
 {
 "Status": "U"
 },
 {
 "Status": "U"
 },
 {
 "Status": "U"
 },
 {
 "Status": "U"
 },
 {
 "Status": "U"
 },
 {
 "Status": "U"
 },
 {
 "Status": "U"
 },
 {
 "Status": "U"
 },
 {
 "Status": "U"
 },
 {
 "Status": "U"
 },
 {
 "Status": "U"
 },
 {
 "Status": "U"
 },
 {
 "Status": "U"
 }
...


Firmware 1.1.3

Hello

Now we have tested firmware 1.1.3 and we are still experiencing the switch is unstable and can not capture it on our management Network after it has been rebooting ,we have also found out that when the switch can not be capture on manigenment Network, then the netonix switch and make som kind of loop on the 8 port TSP it is plugged in to , because when netonix switch tried to negotiate or self up right It self, i lose ping on TSP 8 but only from management network and only until the green light lights up Again (Port light) in netonix switch ,tried to switch on / off loop protection and have also tried to switch off / on RSTP and without succes.
But we can still just move the lan cabel from one port to another, and then after that the netonix switch can becapture on our management Network Again .

Mola9850 wrote:Hello

Now we have tested firmware 1.1.3 and we are still experiencing the switch is unstable and can not capture it on our management Network after it has been rebooting ,we have also found out that when the switch can not be capture on manigenment Network, then the netonix switch and make som kind of loop on the 8 port TSP it is plugged in to , because when netonix switch tried to negotiate or self up right It self, i lose ping on TSP 8 but only from management network and only until the green light lights up Again (Port light) in netonix switch ,tried to switch on / off loop protection and have also tried to switch off / on RSTP and without succes.
But we can still just move the lan cabel from one port to another, and then after that the netonix switch can be captured on our management Network Again .

Did you default the switch after upgrading (Downgrading) and - re enter the config manually as we requested?

If you are installing this version on a switch that has or had v1.2.0rcX, especially a WS-8-250-AC, and it acts weird still try power cycling it but if that does not help you may need to default the switch and re-set it up if after installing this version. (DO NOT BACKUP THE CONFIG, DEFAULT AND THEN RESTORE AS THIS DEFEATS THE PURPOSE)

Mola9850 wrote:Hello

Now we have tested firmware 1.1.3 and we are still experiencing the switch is unstable and can not capture it on our management Network after it has been rebooting ,we have also found out that when the switch can not be capture on management Network, then the netonix switch and make some kind of loop on the 8 port TSP it is plugged in to , because when netonix switch tried to negotiate or self up right It self, i lose ping on TSP 8 but only from management network and only until the green light lights up Again (Port light) in netonix switch ,tried to switch on / off loop protection and have also tried to switch off / on RSTP and without succes.
But we can still just move the lan cable from one port to another, and then after that the netonix switch can becapture on our management Network Again .

Try turning off Flow Control on any port of the WISP Switch connecting to a Tough Switch 5 or 8 port.

We have found for some reason that Tough Switch 5 and 8 port sometimes randomly freak out with our switch if Flow Control is turned on for the port connecting to the Tough Switch? When this happens it is sort of like a loop as there are MILLIONS of Pause Frames being sent out. This happens randomly and not all the time but we have found that if Flow Control is on a port of the WISP Switch that connects to a Ubiquiti Tough Switch this can happen without ant reason. It is on Eric's list to investigate what is going on here.

We do not think it is our switch core but for some reason Flow Control does not agree with the Tough Switch.
We have tried many other switches and this does not happen, just the Tough Switch 5 and 8 port as it does not happen with a Ubiquiti Edge Switch either?

sirhc wrote:

Mola9850 wrote:Hello

Now we have tested firmware 1.1.3 and we are still experiencing the switch is unstable and can not capture it on our management Network after it has been rebooting ,we have also found out that when the switch can not be capture on manigenment Network, then the netonix switch and make som kind of loop on the 8 port TSP it is plugged in to , because when netonix switch tried to negotiate or self up right It self, i lose ping on TSP 8 but only from management network and only until the green light lights up Again (Port light) in netonix switch ,tried to switch on / off loop protection and have also tried to switch off / on RSTP and without succes.
But we can still just move the lan cabel from one port to another, and then after that the netonix switch can be captured on our management Network Again .

Did you default the switch after upgrading (Downgrading) and - re enter the config manually as we requested?

If you are installing this version on a switch that has or had v1.2.0rcX, especially a WS-8-250-AC, and it acts weird still try power cycling it but if that does not help you may need to default the switch and re-set it up if after installing this version. (DO NOT BACKUP THE CONFIG, DEFAULT AND THEN RESTORE AS THIS DEFEATS THE PURPOSE)

Yes we updated firmware to 1.1.3 dit "hold reset for 10 sec when power up switch, and the updated firmware again to 1.1.3, then mamuel typing configuration.