Netonix Forums

I have a couple of the WS-6-MINI switched entering into a reboot cycle until they are power cycled. They are in a Tyco box on tower using the UBNT POE-54V-80W poe to power them. They are powering 5 UBNT Prism AC AP's. Showing to be drawing about 50 Watts from the switch. I have ran new CAT5 cable to the switches already and still seems to happen. If i turn off the a couple of the ports it seems that the issue stays away. Seems to be an overloading issue but according to the switch info the Prism radio are only pulling around 50 Watts with all five powered on. Thoughts

Please RMA.

We had a percentage of a batch of 6-minis exhibit this symptom; as it takes an appreciable amount of time to occur, it escaped our testing at that point in time. We have since redesigned the affected circuit, and revised our testing procedure, but in order to effect a repair, I need to modify the actual hardware.

I just ordered and received these unit within the last three weeks and two of the three that i have deployed on tower are experiencing this issue. Is there a way to tell which batch need repaired as i have more and dont want to replace them only to have to climb again to find out that they too are bad. Or better yet i dont want to order more and get more from the bad batch??

I stand corrected these unit were ordered in October of 2016 from Streakwave. I have 6 units that i need to RMA for the repair they were all filled on same order i have ordered 6 more to replace the ones on the towers and will pull them and send in for RMA.
Thanks

Really sorry about this.

Will make sure we repair and send them back to you ASAP.

I'm not sure if my problem is related to this or not. I have a WS-6-mini powering 2 rockets and 1 AF5X that has worked fine since November until the last month or so when the weather warms up over 80 outside in the afternoons. The switch would just stop passing traffic, then will soon reboot itself. It will do this 2-3 time until sundown. I replaced the unit with a differnet switch, same model and works great at site. While testing first unit in the shop i can power up to five rockets without any issue but only when i add an AF5X it starts rebooting again after a few days, starting the cycle all over again.

prbennett wrote:I'm not sure if my problem is related to this or not. I have a WS-6-mini powering 2 rockets and 1 AF5X that has worked fine since November until the last month or so when the weather warms up over 80 outside in the afternoons. The switch would just stop passing traffic, then will soon reboot itself. It will do this 2-3 time until sundown. I replaced the unit with a differnet switch, same model and works great at site. While testing first unit in the shop i can power up to five rockets without any issue but only when i add an AF5X it starts rebooting again after a few days, starting the cycle all over again.

It should be RMA'd with a detailed explanation of issue.

The defective 3.3V CAP issue "could possibly" be exasperated by higher temperatures.

I have a WS-6-MINI (out of curiosity, why does it say WS-6-POE on the label if that's not the actual model number?) that works just fine until POE is turned on, then it enters a boot loop. It has MAC EC:13:B2:91:DC:BC. I don't know when it was made, but it seems to have been bought in January of 2019. Could this be due to the same hardware issue?

My goal with this unit is to get a refund for it (as we have already replaced the unit), however it was bought through Streakwave. How would I go about accomplishing this? I only ask here because Streakwave redirected me here for the RMA.

patricrowenetworks wrote:I have a WS-6-MINI (out of curiosity, why does it say WS-6-POE on the label if that's not the actual model number?) that works just fine until POE is turned on, then it enters a boot loop. It has MAC EC:13:B2:91:DC:BC. I don't know when it was made, but it seems to have been bought in January of 2019. Could this be due to the same hardware issue?

My goal with this unit is to get a refund for it (as we have already replaced the unit), however it was bought through Streakwave. How would I go about accomplishing this? I only ask here because Streakwave redirected me here for the RMA.

"US","858827005087","08/25/2017","EC13B291DCBC","N/A

That unit was built on 08/25/2017, can not see how it was bought in January 2019?
I can investigate further when Streakwave purchased that particular unit and then check to see how many orders they purchased between then and January 2019 as they often run out between orders.

But as far as RMA you can click on a link in our web site footer for instruction to RMA it for repair.

If the unit is faulty and within warranty period we will repair and return free, if it is damaged we will provide a report with pictures of damage and cost for repair as well as what we think occurred.

sirhc wrote:

patricrowenetworks wrote:I have a WS-6-MINI (out of curiosity, why does it say WS-6-POE on the label if that's not the actual model number?) that works just fine until POE is turned on, then it enters a boot loop. It has MAC EC:13:B2:91:DC:BC. I don't know when it was made, but it seems to have been bought in January of 2019. Could this be due to the same hardware issue?

My goal with this unit is to get a refund for it (as we have already replaced the unit), however it was bought through Streakwave. How would I go about accomplishing this? I only ask here because Streakwave redirected me here for the RMA.

"US","858827005087","08/25/2017","EC13B291DCBC","N/A

That unit was built on 08/25/2017, can not see how it was bought in January 2019?
I can investigate further when Streakwave purchased that particular unit and then check to see how many orders they purchased between then and January 2019 as they often run out between orders.

But as far as RMA you can click on a link in our web site footer for instruction to RMA it for repair.

If the unit is faulty and within warranty period we will repair and return free, if it is damaged we will provide a report with pictures of damage and cost for repair as well as what we think occurred.

I don't know too much about the order, and the only reason I haven't already followed the procedure is that the post that states the procedure reeks of user error frustration, and I didn't want to do anything to add to it. I've sent in the RMA, thanks for your help.