v1.3.7 FINAL bug reports and comments

[sirhc]

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.

If removing the SAF from being powered by the switch fixes the issue I would investigate the SAF cabling and adapter maybe the cable is damage and has water in it?

Are you using an adapter to allow you to power the Lumina with the switch?

[cbl]

If removing the SAF from being powered by the switch fixes the issue I would investigate the SAF cabling and adapter maybe the cable is damage and has water in it?

Are you using an adapter to allow you to power the Lumina with the switch?

Yes, we do have the outdoor SAF splitter box that takes the PoE and splits it into their funky DC adapter. Will check cabling when we can get onsite.

[sirhc]

If the adapter or wire has water in it then it could cause the port to draw too much power and cause the switch reboot.

Water itself is not a conductor but as the copper corrodes it will infuse conductive minerals into the water and will draw more and more power.

If it is drawing to much power eventually it will damage the Ethernet transformer in the switch.

[mike99]

Port 1 on WS-24-400A and WS-12-250A port is enabled at boot even if disabled in config. Probably introduced with the PoE bug on port 1 at boot (if I remeber well). Enabling and disabling it again will disable the port but once you reboot, the port is enable again.

Had a broadcast storm because of this bug (SAF connected via fiber port 24 and powered via disabled port 1). Be careful whit this bug while upgrading.

[sirhc]

Port 1 on WS-24-400A and WS-12-250A port is enabled at boot even if disabled in config.

Mike we were unaware that such a bug existed?

Bug confirmed and fixing!

So sorry Mike!

[Perfectsim9]

Hello, i have a WS-12-250-DC that is currently running on firmware 1.3.7 and it is powering off automatically with out warning or error log entry approx every 15min when i have it plugged connected to a Power Max PM3-50-24. The Power Max charger / inverter works great with our current Packetflux deployment. The WS-12-250-DC works exactly how it should when connected directly to a variable voltage inverter (Mean Well S-150-24) which does have an integrated rectifier. When the WS-12-250-Dc powers off when connected to the Power Max charger the Voltage stays well above the Hibernate Switch Voltage level (29.52 volts and when the POE Switch shuts off it jumps down to 27.66 Volts) . For testing purposes i have the POE switch set to 27 Volts for Warning Voltage, 25 Voltsfor Hibernate Voltage, 26 Volts for Wakeup Switch Voltage. I have also tried firmware 1.3.6 with the same results. Any ideas as to what might be happening?

[highlands]

I would get out a Oscilloscope and look to see how dirty the power is. Those charges are great! I have one in my RV and I had issues with the AM/FM radio that is in it. I had to use a healthy sized inductor and some caps to clean it up enough to be able to use it.

Remember that charger is intended to charge batteries in your RV, not to run sensitive electronics!

John

[sirhc]

PLEASE UPGRADE TO v1.3.8

1.3.8 was primarily al lot of fixes for DC units.

[sileng]

Hello,
I have a Netonix 250W 12 Port POE WISP Switch that I am unable to access via Google Chrome/ Firefox/ IE. I have been able to gain access via SSH and I thought it might have been a configuration issue so I factory reset the switch. This did not fix it.

The switch has been fine for the past 6 weeks. Any Ideas?

Code: Select all

Netonix Switch# show log
Dec 31 19:00:28 syslogd started: BusyBox v1.19.4
Dec 31 19:00:28 STP: set port 5 to learning
Dec 31 19:00:28 STP: set port 5 to forwarding
Dec 31 19:00:29 dropbear[1103]: Running in background
Dec 31 19:00:30 sysinit: 1070
Dec 31 19:00:33 switch[1125]: Detected cold boot
Dec 31 19:01:50 dropbear[1273]: Child connection from ::ffff:192.168.1.29:55717
Dec 31 19:01:52 dropbear[1273]: password auth succeeded for 'admin' from ::ffff:192.168.1 .29:55717
Dec 31 19:24:43 dropbear[1273]: exit after auth (admin): Exited normally
Dec 31 19:25:03 dropbear[3605]: Child connection from ::ffff:192.168.1.29:56431
Dec 31 19:25:03 dropbear[3605]: password auth succeeded for 'admin' from ::ffff:192.168.1 .29:56431
Netonix Switch# show status
System
------
Current Time: 12/31/1969 19:25:47
Uptime: 1547.709961 seconds
CPU Usage: 12%
Memory Usage: 37.91 MB
MAC Address: ec:13:b3:61:0d:2e
IP Address: 192.168.1.20
IPv6 Address: fe80::ee13:b3ff:fe61:d2e
Firmware Version: 1.3.7
Model: WS-12-250-AC
Board Rev: D
Power
-----
Board 48V: 50.2 V
Board 24V: 24.7 V
Board 3V: 3.3 V
Thermal
-------
Board Temp: 44 C
CPU Temp: 61 C
PHY Temp: 62 C
Cooling
-------
Fan 1 Speed: 2370 RPM
 


[sirhc]

I would do the factory reset where you hold in the reset button for 20 seconds as you apply power.

viewtopic.php?f=17&t=409

Also since we have 3 different models of 12 port 250W switches it is best to state the model number, not that in this situation it matters but still wise to do.

My guess is that you either turned off the HTTPS access by un-checking the box or changed the port

Read this post on how to Enable HTTPS again from the CLI viewtopic.php?f=17&t=641#p4584

Also in the future tell us current firmware version, I hope you are keeping your units up to date?

Current stable is v1.3.8 but v1.3.9rc6 has been stable and fixes SNMP and a few other little things.