Two WS-8-150-AC Fail After Defaulting and Applying Volts
Posted: Tue Jun 18, 2019 1:29 pm
I have two switches that have the same behavior after factory defaulting via cli and supplying power to a device.
The first switch (EC13B2D12C58) I was unable to access the web management page, so I used a console cable to view the running config and factory default the unit. My laptop was plugged into eth8. Via the cli I issued "reload defaults" and the switch restarted. I was able to log into the web management page using the default IP, and while I had a phone plugged (Polycom SoundStation Ip 6000) into eth1, I changed PoE to 24V 0.75A while the phone was plugged into the port. I saw the port supply power, but the switch did not show a physical link to the phone. I would expect that as the phone requires 48V to boot. I was then in the process of updating the power to 48V 0.75A, but the switch's fans maxed out, and I could smell something burning. The console cable also was not responsive. I tried to reset using the reset button on the front of the unit, but the switch was nonresponsive. Thinking I had a bad switch. I moved to another WS-8-150-AC switch.
Same process. I factory defaulted the switch (EC13B2D146D0) via the cli. I then plugged my laptop into eth8. I set eth1 to 24V 0.75A before plugging in the phone. I then plugged in the phone, after I saw power supplied to the switch port. There was still not a link light. I then unplugged the phone's ethernet cable to eth1. I then set PoE on that switch port to 48V 0.75A, and after I hit save, the switch then had the same behavior. I smelt something burning. I was unable to ping the default IP, and the console port was also unresponsive. Also using the reset button on the front of the switch did not work.
To try to figure out what happened, I opened one of the switches with a colleague, and we found a component of the board was fried. See the attached image. Before I factory both switches, I did not take note of the current firmware version.
Have these symptoms or behavior been reported before?
Image -> https://drive.google.com/open?id=1fbzUl ... rK5BIVENoV
The first switch (EC13B2D12C58) I was unable to access the web management page, so I used a console cable to view the running config and factory default the unit. My laptop was plugged into eth8. Via the cli I issued "reload defaults" and the switch restarted. I was able to log into the web management page using the default IP, and while I had a phone plugged (Polycom SoundStation Ip 6000) into eth1, I changed PoE to 24V 0.75A while the phone was plugged into the port. I saw the port supply power, but the switch did not show a physical link to the phone. I would expect that as the phone requires 48V to boot. I was then in the process of updating the power to 48V 0.75A, but the switch's fans maxed out, and I could smell something burning. The console cable also was not responsive. I tried to reset using the reset button on the front of the unit, but the switch was nonresponsive. Thinking I had a bad switch. I moved to another WS-8-150-AC switch.
Same process. I factory defaulted the switch (EC13B2D146D0) via the cli. I then plugged my laptop into eth8. I set eth1 to 24V 0.75A before plugging in the phone. I then plugged in the phone, after I saw power supplied to the switch port. There was still not a link light. I then unplugged the phone's ethernet cable to eth1. I then set PoE on that switch port to 48V 0.75A, and after I hit save, the switch then had the same behavior. I smelt something burning. I was unable to ping the default IP, and the console port was also unresponsive. Also using the reset button on the front of the switch did not work.
To try to figure out what happened, I opened one of the switches with a colleague, and we found a component of the board was fried. See the attached image. Before I factory both switches, I did not take note of the current firmware version.
Have these symptoms or behavior been reported before?
Image -> https://drive.google.com/open?id=1fbzUl ... rK5BIVENoV