v1.3.7 FINAL bug reports and comments

[Dave]

designweb

is it possible to vary the speed on the new timer that reverts to previous config, perfect idea, very useful, but sometimes need longer to make other changes around it before it comes back up and reverts. thanks again for a great product

We will consider this request...

Dave

[lligetfa]

...finally are you going to compete with Edgepoint with a waterproof switch for the tower?

Have you looked at the towerswitch discussions here?

[designweb]

Hi Dave

This was a new switch with 1.3.2. I always upgrade to the latest firmware before bringing into service, I have not seen this before either and when you are 200 miles from the tower not a nice experience :-(

Probably not required by everyone but an option to extend the timer to two minutes would be useful because I have some techies who are brave enough to climb towers in all weathers but not always good with IT, so I talk them through installing an IP, saving that and connecting online, I then untag the incoming radio add more config with some vlans, save and then retag the vlan on the incoming radio, to continue remaining config, however by the time DFS has delayed reconnection the switch has not found its way to home and restores previous config and the process has to start over.

[Travis_WVN]

Experienced what may be a bug today - latest 1.3.7 firmware on a variety of Netonix across our network. Switches wouldn't pass a tagged VLAN unless multicast was checked. Is this by design or ???


Additionally, 1.3.7 results in the 8-port units pegging their CPUs and dumping packets all over the ground

Rolled the 8-ports back to 1.3.3 and they're fine.

Thanks

[Dave]

designweb

Hi Dave

This was a new switch with 1.3.2. I always upgrade to the latest firmware before bringing into service, I have not seen this before either and when you are 200 miles from the tower not a nice experience :-(

Probably not required by everyone but an option to extend the timer to two minutes would be useful because I have some techies who are brave enough to climb towers in all weathers but not always good with IT, so I talk them through installing an IP, saving that and connecting online, I then untag the incoming radio add more config with some vlans, save and then retag the vlan on the incoming radio, to continue remaining config, however by the time DFS has delayed reconnection the switch has not found its way to home and restores previous config and the process has to start over.

ok, we discussed internally & agree we can add this option to extend timer.

Dave

[designweb]

It is that response of listening to clients (not accountants) that other manufacturers ignore, which sets Netonix apart, many thanks Dave

[vive]

After setting the NTP server the switch hung and rebooted, then finally came back. Then went into the web admin of it and it lost IP connectivity. All traffic was ok through it, the switch just locked up it's admin interface and would not ping. Then came back afterwards.

[gunther_01]

Any thoughts on going from a FW 1.1.1 Board Rev a. To this firmware directly?

[sirhc]

Any thoughts on going from a FW 1.1.1 Board Rev a. To this firmware directly?

Should be fine but always prepare for the worst and hope for the best.

Ne prepared since this is an EXTREMELY old firmware. I had sent many PMs when we came out with v1.1.8 that older firmware had SEVER issues.

I would read all the release notes from v1.1.1 until present and take notes to any concerns.

You should really try and stay a little more current on your firmware.

[cbl]

I have a WS-12-250-AC (board revD) that was on 1.3.7rc2 that exhibited some problems tonight randomly. Around 12:30am, it started rebooting. I would be able to get into it for a minute, then it'd reboot again. I have an AF5x using 24VH on port 1 and a SAF Lumina on port 2 with 48VH. Both appeared to be off when it finally was stable. I upgraded to 1.3.7 final, and disabled PoE Smart for both port 1 and 2. Enabling the 5X with 24VH everything became stable until I enabled 48VH for the SAF Lumina. Then the reboots started again. I was finally able to login with SSH and script the "poe off" for the Lumina interface before it'd reboot again.

I was able to login to the SAF lumina from the far side of the path and it was still powered during these "cold" reboots.. it was just reporting its interface bouncing, similar to what I was seeing on the Cisco plugging into the WS-12-250-AC.

I moved the Lumina to this WS-12-250-AC earlier last week and both have been fine until tonight. Looks like we'll be heading to move it back to it's SAF power supply later today. I don't have any other Luminas powered by a switching running 1.3.7 currently.