WS-26-500-DC intermittent power issues??

[sirhc]

Would be nice if you could swap out the WS-26-500-DC with a WS-12-250-DC for the PSO warehouse switch and see if the reboots stop.

You could achieve this if you used a copper SFP module to gain an extra port and move what is in port 1 to the SFP port as it does not require POE.

If the WS-12-250-DC also reboots or does not reboot would help to know.

[ALXMADRID]

We too have an issue with a WS-26-500-DC. It too reboots about every 3-5 days. I have a replacement on order. When I can switch those out, I will be sending the unit back for inspection. After it reboots I get this in the log:


Dec 31 17:00:06 netonix: 1.4.9 on WS-26-500-DC
Dec 31 17:00:11 system: Setting MAC address from flash configuration: EC:13:B2:06:0C:16
Dec 31 17:00:13 system: starting ntpclient
Dec 31 17:00:14 admin: adding lan (eth0) to firewall zone lan
Dec 31 17:00:15 admin: Unable to query power supply
Dec 31 17:00:25 STP: set port 1 to discarding
Dec 31 17:00:25 STP: set port 22 to discarding
Dec 31 17:00:26 STP: MSTI0: New root on port 1, root path cost is 20012
Dec 31 17:00:26 STP: set port 1 to learning
Dec 31 17:00:26 STP: set port 1 to forwarding
Mar 14 20:40:25 UI: i2c error setting 0x47 12 110
Mar 14 20:40:46 UI: i2c error setting 0x47 14 122
Mar 14 20:40:49 dropbear[949]: Running in background
Mar 14 20:40:52 switch[991]: Detected cold boot

[sirhc]

We have been testing the WS-26-500-DC sent back from Intellipop and so far no reboots up time 1 day 19+ hours.

We have changed the input voltages from 24V to 52V during this test with no reboots but the CPU Utilization is way too HIGH.

We are "suspecting" that this may be the cause. Eric has optimized the code to reduce CPU to 30% +/- which we think will greatly help.

A theory of what might be happening is the CPU is getting bogged down and possibly not responding to the watchdog which forces a reboot or other adverse issues resulting in a reboot.

The fact that it is not rebooting in our LAB even with HIGH CPU is probably that there is nothing else going on so the high CPU is not an issue.

Anyway below you can see Intellipops switch with HIGH CPU usage and under similar POE load as he had deployed it and also another unit with the new optimized code with LOW CPU utilization.

So anyway will be hopefully releasing v1.5.0rcX today or tomorrow.

v1.4.9

v1.5.0rcX

[intellipop]

Well we hope it's that simple. We will keep you posted on our office switch, we are testing the new firmware as of about 11 hours ago.

[intellipop]

Current uptime is 2 Days and 2 Hours. Not holding my breath yet, but this so far this is a good sign.

Mat

[intellipop]

The switch has crashed again, the current uptime is now only 8 hours. What can we do to help your team find this issue?

Mat

[intellipop]

You asked for some details on our other switches in the network.

We have 4x 8 port switches deployed in our network other then the current 26 port switches and those are as follows for uptime.
137 Days
238 Days
265 Days
273 Days

Here is the uptime rundown of our 26 port switches:
6 Days
23 Minutes
8 Days
2 Days
61 Days
8 Hours

We have one 12 port switch still deployed and it's uptime is...
153 Days


I'm seeing a pretty clear uptime trend... we would love to work with your team in a more real time capacity to address these issues please let us know what we can do, please call me. We are supportive of your products but will soon need to remove them from our network if we can't come to a resolution.

Mat

[sirhc]

The switch has crashed again, the current uptime is now only 8 hours. What can we do to help your team find this issue?

Mat

Well first off I have asked several times to please use more descriptive words of the issue.

"Crash" would indicate to me and probably most other people reading your posts the switch locks up and you need to manually reboot it.

"Reboot" would indicate the switch rebooted on its own and came back up.

Which better describes your issue?

Several people have indicated this fixed their issue?

How many switches have you tried this on, you indicated you had several WS-26-500-DC units that I think are "rebooting".

It would be helpful if you installed v1.5.0rc1 on all your WS-26-500-DC units and reported the out come of each unit.

I am confused as you reported Monday night that your switch was up 11 hours and that was 48 hours ago yet now your saying the switch is rebooting after 8 hours?

Well we hope it's that simple. We will keep you posted on our office switch, we are testing the new firmware as of about 11 hours ago

[intellipop]

Yes Chris, the switch is crashing resulting in a system reboot. So you want me to install the new 1.5x firmware across all our switches when a switch in our office powering 5 POE cameras and 4 POE phones isn't able to remain stable on this code base?

[sirhc]

You asked for some details on our other switches in the network.

Yes accurate information helps

We have 4x 8 port switches deployed in our network other then the current 26 port switches and those are as follows for uptime.
137 Days
238 Days
265 Days
273 Days

Other than your running old firmware I see no issues with these units?

Here is the uptime rundown of our 26 port switches:
6 Days - What mode WS-26-400-AC or WS-26-500-DC - Obviously you have not loaded v1.5.0rc1
23 Minutes - What mode WS-26-400-AC or WS-26-500-DC - Did you load v1.5.0rc1?
8 Days - What mode WS-26-400-AC or WS-26-500-DC - Obviously you have not loaded v1.5.0rc1
2 Days - What mode WS-26-400-AC or WS-26-500-DC - Did you load v1.5.0rc1?
61 Days - What mode WS-26-400-AC or WS-26-500-DC - Obviously you have not loaded v1.5.0rc1
8 Hours- What mode WS-26-400-AC or WS-26-500-DC - Did you load v1.5.0rc1?

Please load v1.5.0rc1 on all WS-26-500-DC units your having issues with.

We have one 12 port switch still deployed and it's uptime is...
153 Days

I see no problem with this model?

I'm seeing a pretty clear uptime trend... we would love to work with your team in a more real time capacity to address these issues please let us know what we can do, please call me. We are supportive of your products but will soon need to remove them from our network if we can't come to a resolution.

So you are having an issue with 1 model of our switches (WS-26-500-DC) which we have only been working on since last week. We just released our first attempt to clean up the matter 3 days ago and you "just" got back to us with this information. Julian spoke with your office today and your unit had been up far more than 8 hours????

But you want to rip out all out all our switches because we are having an issue with one model that we are actively working on as best we can?

As I said I would appreciate if you installed v1.5.0rc1 on all WS-26-500-DC and see what the results are.

If it solves the issue with all but 1 or 2 units then maybe there is something additionally wrong with those units.

As I said I am confused by your description crash or reboot and I know you installed this on 1 switch Monday yet you just said your switch is crashing which I think you mean rebooted after 8 hours?