WS-12-250-DC does not start

[RebusCom]

Apologies, I think I posted to the wrong thread. Please refer to (or move this to) viewtopic.php?f=17&t=3091&p=20995&hilit=reset#p20995

What preceded the lockup was very similar to that thread. There were two VLANs, one tagged and the other not. The tagging was moved from one to the other. Same result. Lockup with no recovery.

[RebusCom]

Another clue. Per syslog it appears the traffic stopped about one minute after the change. That implies the switch perhaps tried to revert back to it's prior config, unsuccessfully.

[jg0007]

Hello the same problem happened with the netonix
Bank batteries of 24 downloaded to 9 volts immediately the panels charged the batteries Netonx did not rise well

It only shows the LED on and the continuous fan on

It has already happened to me in two different places with different netonix the firmware version is v1.4.7
It does not start this seems to me to a fault of the company since the fact that it lowers the voltage after the rank the netonix hibernates but it does not wake up I am losing the confidence in this product



I need to know if it has that defect since its manufacture since

It has caused me many problems this course to work in 9v to 72 without having a problem the truth is that I think the firmware has errors in this regard

I could provide a solution to this problem that has caused me so many customer losses due to this manufacturer's failure

[Dave]

you need to use the latest code, as we have fixes & feature updates since 1.4.7

Click
HERE to download firmware v1.4.8rc12 - Released 10/18/2017

[jg0007]

the problem is that the unit now does not do anything this blocked does not allow me to reset from factory nothing I do not have access to the unit

[sirhc]

the problem is that the unit now does not do anything this blocked does not allow me to reset from factory nothing I do not have access to the unit

Dave is correct, we have warned all users of SMART DC models multiple times they MUST use v1.4.8rcX as there was a nasty big in the code for those models.

You tried a serial console cable?

If the unit is dead (no serial console activity) then the unit failed, was damaged, or flash got totally corrupted.

Step 1 use console cable to see if switch is active, if not active then RMA

If it is active via console the switch may be packet locked in which case removing the offending cable will free it up and then disable Flow Control on that port.

[jg0007]

the problem is that the unit now does not do anything this blocked does not allow me to reset from factory nothing I do not have access to the unit

Dave is correct, we have warned all users of SMART DC models multiple times they MUST use v1.4.8rcX as there was a nasty big in the code for those models.

You tried a serial console cable?

If the unit is dead (no serial console activity) then the unit failed, was damaged, or flash got totally corrupted.

Step 1 use console cable to see if switch is active, if not active then RMA

If it is active via console the switch may be packet locked in which case removing the offending cable will free it up and then disable Flow Control on that port.

Ok I just checked in console I have no answer via console

I will have to send it to you not answered by console the unit

Apparently this recorded firmware error caused the unit to not respond to the flash

[sirhc]

Ok I just checked in console I have no answer via console
I will have to send it to you not answered by console the unit
Apparently this recorded firmware error caused the unit to not respond to the flash

Not sure what this means?

At this point we do not know if the unit failed or is damaged.

When you RMA the unit we will report what we find, rather the unit is failed or damaged.

[jg0007]

I CAN NOT understand that after months without problems just because the battery bank is discharged, this causes the unit to be damaged, but I do not like it.
It has already happened twice this seems to me a problem of the manufacturer

[sirhc]

I CAN NOT understand that after months without problems just because the battery bank is discharged, this causes the unit to be damaged, but I do not like it.
It has already happened twice this seems to me a problem of the manufacturer

Well if you had not upgraded to v1.4.8rcX as directed to which there was a firmware bug where the fans would not kick in if the DC controller chip overheated.

Now think about it, as the batteries dropped in voltage this would cause the DC power supply to run hotter as it is up stepping more amps and would run hotter but if you had not upgraded the firmware to v1.4.8rcX the switch would ignore the DC controller chip temperature and not turn the fans on which is why we had a fix.

Also there was a BUG where the switch was measuring jitter on the input voltages which caused issues in some conditions.

FIXED/CHANGED in v1.4.8rcX
- Fixed input voltage reading on SMART DC models that may cause false ;pw input reading if voltage momentarily drop - RC12
- Fixed Changed temp sensor readings on SMART DC models to effect fan speeds - RC2

It has already happened to me in two different places with different netonix the firmware version is v1.4.7

v1.4.7 - This version has known bugs - USE VERSION v1.4.8rcX
DO NOT USE THIS VERSION WITH SMART DC MODELS USE v1.4.8rcX below.
Click HERE to download firmware v1.4.7 - Released 5/7/2017
Click HERE to go to the thread on v1.4.7 to read other people's comments and questions.

v1.4.8rcX - THIS VERSION HAS ALL KNOWN BUGS FIXED
Click HERE to download firmware v1.4.8rc12 - Released 10/18/2017
Click HERE to go to the thread on v1.4.8rcX to read other people's comments and questions.

NOTE: MSTP is still being tested so use MSTP at your own risk.

FIXED/CHANGED
- Fixed input voltage reading on SMART DC models that may cause false ;pw input reading if voltage momentarily drop - RC12
- Fixed Changed temp sensor readings on SMART DC models to effect fan speeds - RC2
- Fixed SNMP support for Q-SWITCH-MIB, LLDP and CDP - RC7
- Fixed IGMP snooping with multiple VLANs - RC9
- Fixed DC calibration restarting POE - RC10
- Fixed problem with DHCP snooping affecting fragmented UDP packets - RC10
- Fixed problem with ERPS enabling forwarding a failed port - RC10
- Fixed problem with MSTP setting priority and path cost - RC10
- Fixed SSH login with RADIUS when the password contains special characters - RC11
- Fixed scheduled port bounce - RC11
- Fixed VLAN drag/drop being too sensitive - RC12
- Grey out unavailable bulk poe options - RC3
- Upper out of voltage range for IDC is now 54V - RC4

ENHANCEMENTS
- Added ERPS protocol implementation is g.8032v2 - Ring Protection - RC1
- Added BETA note to ERPS - RC3
- Added port name to "show interface status" CLI command - RC3
- Added an input voltage calibration for DC models - RC4
- Improved Q-BRIDGE-MIB support - RC5
- Improved fan control on DC models - RC6
- Improved stability of ERPS- RC6
- Added "Enable Power" action to watchdog - RC8
- Added ifMtu to IF-MIB - RC10
- Added dot3StatsDuplexStatus from EtherLike-MIB - RC10
- Added the time counters were cleared to port detail - RC10
- Added watchdog description to email notification - RC10
- Added terminal length option to CLI - RC10
- Added ability to re-order VLANs using drag and drop - RC10
- Enabled IGMP proxy for IGMP snooping - RC11
- Added "show igmp" CLI command - RC11


KNOWN ISSUES
- Some language templates need help - please private message Eric Stern to help

v1.4.8rc1 Released 5/9/2017
v1.4.8rc2 Released 5/11/2017
v1.4.8rc3 Released 5/15/2017
v1.4.8rc4 Released 5/23/2017
v1.4.8rc5 Released 5/26/2017
v1.4.8rc6 Released 6/7/2017
v1.4.8rc7 Released 6/17/2017
v1.4.8rc10 Released 9/10/2017
v1.4.8rc11 Released 9/22/2017
v1.4.8rc12 Released 10/18/2017

Now it is also possible your units are defective? We can not tell this until you RMA them.
But before you RMA them I would 1st try this.

On bench hold the default button down when you apply power for 20-30 seconds then let up and let the switch sit for a few minutes as it needs to do some work with the FLASH. Make sure power is not removed during this period. I would also have a console cable hooked up to see if anything is going on.

If this does not recover them I would get an RMA # and return them and we can determine what the issue is.