v1.5.5 Bug Reports and Comments

[picasso]

WS-8-150 DC firmware 1.5.5

24v based system low voltage cut off set to 23v. Switch part never wakes backup. only have 3 devices connected to switch 24v .5amp, all powered on fine but show LAN (wired) unplugged. WS-8-150 never re-awoke so radios cant talk to one another via LAN (wired). batt is +26v and everything was set to wakeup again at 24v.

[RebusCom]

Updated switches to v1.5.5 some weeks ago and for the first time since had a Rocket radio lock up and become unresponsive. Normally ping watchdog would cycle POE and restore service, however, hours passed with repeated watchdog activations to no avail. I performed a manual POE bounce on the port and everything came back. Watchdog is set to Bounce Power but it doesn't appear the power is getting bounced, just the link. Here is the tail end of the log. Switch is a WS-12-250-AC


Dec 31 03:52:24 switch[1763]: Watchdog 'AP8' failure checking 192.168.5.208, watchdog triggered on port 8 (AP8), action is Bounce
Dec 31 03:52:24 Port: link state changed to 'down' on port 8
Dec 31 03:52:24 switch[1763]: Port 8 Link: re-negotiating
Dec 31 03:52:24 sSMTP[1877]: Creating SSL connection to host
Dec 31 03:52:25 sSMTP[1877]: SSL connection using AES128-SHA
Dec 31 03:52:27 sSMTP[1877]: Sent mail for rebuscom@gmail.com (221 2.0.0 closing connection t9sm3254973pjq.11 - gsmtp) uid=0 username=admin outbytes=631
Dec 31 03:52:34 switch[1763]: Port 8 Link: up
Dec 31 03:52:37 Port: link state changed to 'up' (1G) on port 8
Dec 31 04:13:41 switch[1763]: Watchdog 'AP8' failure checking 192.168.5.208, watchdog triggered on port 8 (AP8), action is Bounce
Dec 31 04:13:41 Port: link state changed to 'down' on port 8
Dec 31 04:13:42 switch[1763]: Port 8 Link: re-negotiating
Dec 31 04:13:42 sSMTP[768]: Creating SSL connection to host
Dec 31 04:13:42 sSMTP[768]: SSL connection using AES128-SHA
Dec 31 04:13:44 sSMTP[768]: Sent mail for rebuscom@gmail.com (221 2.0.0 closing connection j9sm43515833pff.6 - gsmtp) uid=0 username=admin outbytes=631
Dec 31 04:13:52 switch[1763]: Port 8 Link: up
Dec 31 04:13:54 Port: link state changed to 'up' (1G) on port 8
Dec 31 04:23:41 UI: Port 8 bounced by admin (::ffff:192.168.5.100)
Dec 31 04:23:41 switch[1768]: Port 8 Link: changed from poe override
Dec 31 04:23:42 Port: link state changed to 'down' on port 8
Dec 31 04:23:54 Port: link state changed to 'up' (100M-F) on port 8
Dec 31 04:24:15 Port: link state changed to 'down' on port 8
Dec 31 04:24:19 Port: link state changed to 'up' (1G) on port 8

[jschalle]

Hi all, I am new to Netonix and not overly technical. I purchased a WS-8-150-AC and I want to download the latest stable firmware which I see is v1.5.5. My question: Is there only one version of firmware for all your models? Hence is this v1.5.5 what I need to update the firmware on my WS-8-150-AC. Thanks for your time.

[Dave]

we have a common software base that is meant for all of our WS models....yes, you just need 1.5.5

[mrmarria]

Like to Bump this again-
Not urgent, but important......

re:ws-12-250-dc ver 1.5.5

Tried using Tool > Watchdog>ping enable power on port that shuts down daily 1-7 am to conserve batteries (AF 11Fx)

When I added the tool, the radio apparently never came up all the way, weirdly. It showed power on but no connection.
After up grading and disabling the tool, all seemed normal, shutdown + startup etc.

This morning, I tried re-enabling the tool, and watched what happened at the 7 am power up.

Every thing acted normal, though the connection seemed to take a minute longer than expected, it ran for 2-3 minutes then the connection stopped, though power indicated still on, there is no tcp traffic.

After disabling the watchdog tool and bouncing the port, the radio came up and stayed up.

????

I have tested this several times. it is consistent.

It is unclear to me where is the problem lay, possible soft glitch??

Thanks,

Michael

[RebusCom]

I've not received a response to this firmware bug. It's happened again, with two AP's locking up becoming unresponsive to ping and ping watchdog failing to cycle the POE. Set to POE it instead just cycles the link, not power. This needs to be fixed ASAP. It's a serious problem.

Updated switches to v1.5.5 some weeks ago and for the first time since had a Rocket radio lock up and become unresponsive. Normally ping watchdog would cycle POE and restore service, however, hours passed with repeated watchdog activations to no avail. I performed a manual POE bounce on the port and everything came back. Watchdog is set to Bounce Power but it doesn't appear the power is getting bounced, just the link. Here is the tail end of the log. Switch is a WS-12-250-AC


Dec 31 03:52:24 switch[1763]: Watchdog 'AP8' failure checking 192.168.5.208, watchdog triggered on port 8 (AP8), action is Bounce
Dec 31 03:52:24 Port: link state changed to 'down' on port 8
Dec 31 03:52:24 switch[1763]: Port 8 Link: re-negotiating
Dec 31 03:52:24 sSMTP[1877]: Creating SSL connection to host
Dec 31 03:52:25 sSMTP[1877]: SSL connection using AES128-SHA
Dec 31 03:52:27 sSMTP[1877]: Sent mail for rebuscom@gmail.com (221 2.0.0 closing connection t9sm3254973pjq.11 - gsmtp) uid=0 username=admin outbytes=631
Dec 31 03:52:34 switch[1763]: Port 8 Link: up
Dec 31 03:52:37 Port: link state changed to 'up' (1G) on port 8
Dec 31 04:13:41 switch[1763]: Watchdog 'AP8' failure checking 192.168.5.208, watchdog triggered on port 8 (AP8), action is Bounce
Dec 31 04:13:41 Port: link state changed to 'down' on port 8
Dec 31 04:13:42 switch[1763]: Port 8 Link: re-negotiating
Dec 31 04:13:42 sSMTP[768]: Creating SSL connection to host
Dec 31 04:13:42 sSMTP[768]: SSL connection using AES128-SHA
Dec 31 04:13:44 sSMTP[768]: Sent mail for rebuscom@gmail.com (221 2.0.0 closing connection j9sm43515833pff.6 - gsmtp) uid=0 username=admin outbytes=631
Dec 31 04:13:52 switch[1763]: Port 8 Link: up
Dec 31 04:13:54 Port: link state changed to 'up' (1G) on port 8
Dec 31 04:23:41 UI: Port 8 bounced by admin (::ffff:192.168.5.100)
Dec 31 04:23:41 switch[1768]: Port 8 Link: changed from poe override
Dec 31 04:23:42 Port: link state changed to 'down' on port 8
Dec 31 04:23:54 Port: link state changed to 'up' (100M-F) on port 8
Dec 31 04:24:15 Port: link state changed to 'down' on port 8
Dec 31 04:24:19 Port: link state changed to 'up' (1G) on port 8

[Dave]

I will have Stephen look at this for you.

[Stephen]

RebusCom,

I believe I see what's happening here.
Here are the logs from my test's:

Jan 12 11:07:52 UI: Log cleared by Netonix Manager (::ffff:192.168.1.66)

Jan 12 11:09:11 UI: Configuration changed by Netonix Manager (::ffff:192.168.1.66)

Jan 12 11:09:11 UI: PingWatchdog 1 PingInterval: changed from '300' to '60'

Jan 12 11:09:11 UI: PingWatchdog 1 FailureThreshold: changed from '3' to '1'

Jan 12 11:14:17 switch[771]: Watchdog 'Port 1' failure checking 12.12.12.12, watchdog triggered on port 1 (Port 1), action is Bounce Power

Jan 12 11:16:27 UI: Configuration changed by Netonix Manager (::ffff:192.168.1.66)

Jan 12 11:16:27 UI: PingWatchdog 1 Action: changed from 'Bounce Power' to 'Bounce Link'

Jan 12 11:21:34 switch[771]: Watchdog 'Port 1' failure checking 12.12.12.12, watchdog triggered on port 1 (Port 1), action is Bounce Link

Jan 12 11:21:34 switch[771]: Port 1 Link: re-negotiating

Jan 12 11:21:44 switch[771]: Port 1 Link: up

Jan 12 11:27:47 switch[771]: Watchdog 'Port 1' failure checking 12.12.12.12, watchdog triggered on port 1 (Port 1), action is Bounce Link

Jan 12 11:27:47 switch[771]: Port 1 Link: re-negotiating

Jan 12 11:27:57 switch[771]: Port 1 Link: up

As you can see, on your log's it just say's action is "Bounce" not "Bounce Power" or "Bounce Link". I believe what has happened is that maybe the firmware you upgraded from may have only had the option to "Bounce" as I recall we separated this into Bounce Link and Bounce Power later on. If in the internal storage of the switch it still shows the action is "Bounce" then it will no longer recognize that option and nothing will happen.

To correct this, try deleting that watchdog, saving your configuration, and then re-create the watchdog and save again. This should correctly update the conditions on the switch. Then monitor the logs, if you don't see it look similar to the bolded statements in mine, aka, "Bounce Power" or "Bounce Link" then let us know here.

[socraticmethod]

Can anyone advise on what exactly "Broadcast On Protocols" is doing under the Discovery section of the configuration page? A quick search of the forums doesn't have any information regarding what's going on there.

[lligetfa]

Normally I would advise you hover the mouse over it and read the tooltip but they didn't populate it.