Netonix Forums

I am not sure if this is a WISP switch issue or a UBNT issue but since the outdoor temps here are now -14F I am having periodic issues where the all but one AP on a WS-12-250AC are rebooting.

The only one not rebooting is a Rocket M2. The other 8 APs are Rocket5AC Gen2. Is there any known issues with older wisp switches and sub zero temps? The switch is not rebooting and I am not loosing connectivity to the switch.

Well if the switch is not booting this is not a switch issue with temperature.

But "possibly" could be this issue if the switch is close to 2 years old or older and you added more 24V radios to the switch recently: viewtopic.php?f=17&t=3934#p24989

Please post up a screen grab of the Status and Device/Status TAB.

Here are the screens. I have not added anything to the switch for around 1 year. If it is the power issue could the cold be exposing the problem (the switch components are working harder)?

Also this switch and my one spare were mfg in 2015.

Yea this unit definitely has the original design of 108 watts of 24V POE budget.

You can RMA them for the upgrade.

We would install 24V MOD, GROUND MOD, and do a full checkup for $50.00.

I am guessing that the extreme cold is either a coincidence or your radios are simply transmitting more which requires more power which makes sense since it is so cold kids are inside as well as adults so you have increased traffic.

Also that firmware v1.4.6 is really really old, not your problem, just complaining.

We're seeing issues with a WS-24-400A with the first 12 ports acting up last night in -25 temps.

Ports 3-12 were not rebooting POE but the ethernet was flapping up and down with these temps. Going from down, to 100 Meg, to down, back up to 1G. They would keep doing this until I turned off POE on all the ports 3-12 then turned them on one-by-one until they were all back at 1G. It started happening again so I turned off Port 11 and left it off which helped stabilize the port flapping but it still happened 3 times overnight again, which is much better than every few minutes though.

Any ideas?

The WS-24-400A/B and WS-12-250A/B never had this issue and the 24V power supply is rated at 160 watts.

The WS-26-XXX-XX and WS-24-400A/B have (2) 24V power supplies 1 for ports 1-12 and 1 for ports 13-24 each rated at 160 watts.

My guess is this is more of temperature contraction of parts like Ethernet connectors.

Several times a year we have to dispatch tower guys to simply unplug and replug Ethernet connector. Normally happens in extreme temp ranges cold or hot.

viewtopic.php?f=14&t=4933#p28000

How would I go about paying for the RMA service? Being a public utility we do all purchases usually by Purchase Order/Invoice.

sbyrd wrote:How would I go about paying for the RMA service? Being a public utility we do all purchases usually by Purchase Order/Invoice.

RMA's are paid for via credit card or PayPal. You could also mail a check I guess.
When an RMA is complete we send you a detailed report of what we found and what we did along with a link on our web store to pay for each RMA.

You then go to checkout and use CC or PayPal.

Now you could pay with PO# then mail a check or ACH but your RMA would not ship until we receive the check/ACH and it clears.

This is not one port going down, it's ports 3-12 going down at the same time so it's not a matter of a loose cable not plugged in right. It only has happened during this cold and only on the 1-12 port bank of the 24 port. Logs show this bank having trouble together at the same time.



Jan 30 01:22:01 Port: link state changed to 'down' on port 4

Jan 30 01:22:01 Port: link state changed to 'down' on port 5

Jan 30 01:22:01 Port: link state changed to 'down' on port 6

Jan 30 01:22:01 Port: link state changed to 'down' on port 7

Jan 30 01:22:01 Port: link state changed to 'down' on port 9

Jan 30 01:22:01 Port: link state changed to 'down' on port 10

Jan 30 01:22:01 Port: link state changed to 'down' on port 12

Jan 30 01:22:01 Port: link state changed to 'down' on port 3

Jan 30 01:22:04 Port: link state changed to 'up' (100M-F) on port 9

Jan 30 01:22:04 Port: link state changed to 'up' (100M-F) on port 7

Jan 30 01:22:04 Port: link state changed to 'up' (100M-F) on port 10

Jan 30 01:22:04 Port: link state changed to 'up' (100M-F) on port 12

Jan 30 01:22:04 Port: link state changed to 'up' (100M-F) on port 4

Jan 30 01:22:04 Port: link state changed to 'up' (100M-F) on port 5

Jan 30 01:22:04 Port: link state changed to 'up' (100M-F) on port 8

Jan 30 01:22:04 Port: link state changed to 'up' (100M-F) on port 3

Jan 30 01:22:04 Port: link state changed to 'up' (100M-F) on port 6

Jan 30 01:22:04 switch[3175]: unexpected link change on port 9 (5G 150) from 1G to 100M-F

Jan 30 01:22:04 switch[3177]: unexpected link change on port 7 (5G 090) from 1G to 100M-F

Jan 30 01:22:05 switch[3179]: unexpected link change on port 10 (5G 180) from 1G to 100M-F

Jan 30 01:22:05 switch[3195]: unexpected link change on port 12 (5G 240) from 1G to 100M-F

Jan 30 01:22:05 switch[3197]: unexpected link change on port 4 (5G 000) from 1G to 100M-F

Jan 30 01:22:06 switch[3205]: unexpected link change on port 5 (5G 030) from 1G to 100M-F

Jan 30 01:22:06 switch[3207]: unexpected link change on port 8 (5G 120) from 1G to 100M-F

Jan 30 01:22:07 switch[3209]: unexpected link change on port 3 (Cordes Ubnt BH) from 1G to 100M-F

Jan 30 01:22:07 switch[3211]: unexpected link change on port 6 (5G 060) from 1G to 100M-F

Jan 30 01:22:23 Port: link state changed to 'down' on port 3

Jan 30 01:22:23 Port: link state changed to 'down' on port 4

Jan 30 01:22:23 Port: link state changed to 'down' on port 12

Jan 30 01:22:23 Port: link state changed to 'down' on port 7

Jan 30 01:22:23 Port: link state changed to 'down' on port 5

Jan 30 01:22:23 Port: link state changed to 'down' on port 10

Jan 30 01:22:23 Port: link state changed to 'down' on port 9

Jan 30 01:22:23 Port: link state changed to 'down' on port 6

Jan 30 01:22:24 Port: link state changed to 'down' on port 8

Jan 30 01:22:27 Port: link state changed to 'up' (1G) on port 3

Jan 30 01:22:27 Port: link state changed to 'up' (1G) on port 12

Jan 30 01:22:27 Port: link state changed to 'up' (1G) on port 8

Jan 30 01:22:27 Port: link state changed to 'up' (1G) on port 4

Jan 30 01:22:27 Port: link state changed to 'up' (1G) on port 9

Jan 30 01:22:27 Port: link state changed to 'up' (1G) on port 7

Jan 30 01:22:27 Port: link state changed to 'up' (1G) on port 10

Jan 30 01:22:27 Port: link state changed to 'up' (1G) on port 5

Jan 30 01:22:27 Port: link state changed to 'up' (1G) on port 6