Sure, if you're having to power cycle APs then you have a problem you
should fix, but I'd still prefer to know that I could if I had to. It's
also useful during a migration to be able to power up the new AP and
power down the old one. And if your vendor introduces a bug requiring a
power cycle then at least you have a short term solution while you wait
for the patch.
The thing I'd watch out for is tech support leaning on rebooting as a
crutch rather than solving underlying problems. In 2015 I witnessed
first hand a company where low level people were rebooting Wimax APs
every single day. It turned out the biggest reason for it was they had
a bunch of power supplies which were factory set to 220V but plugged
into 110V outlets. They would run normally for awhile, but an internal
breaker would trip at the drop of a hat. Cycling the outlet would reset
that breaker. All they had to do was put a jumper on the PSU to switch
it to 110V, but they got themsel ves into a loop of saying "oh an AP is
down, reboot it."
The AP's also had bugs that made them crash so they still needed the
stupid reboot switches, but it became more of a monthly thing than a
daily thing.
On the one hand, that situation was super dumb. On the other hand these
dummies were diligently monitoring the AP's and resolving the immediate
issue, so if they didn't have their reboot switches I imagine they would
have had somebody running around pulling power cords every day. I saw
this T-shirt at Walmart and thought of them. I wore it around them
frequently, but I don't know if they ever realized it was about them.
PubliciTeeZ Big and Tall King No You're Right Let's Do image 0
On 9/24/2020 1:56 PM, Ken Hohhof wrote:
I can’t remember last time I power cycled an AP, it’s been years.
Only time would be if I did something stupid and needed to do the
quick power cycle to get into the Recovery Console. Usually that
wouldn’t be an AP that’s in service, but one from the used pile that
I’m planning to redeploy but I didn’t label where it came from.
Sometimes after a year or two uptime some of the Ubiquiti stuff will
go off to Lalaland and need a reboot, I had to do an old Powerbridge
the other day, but I could still reboot it from the GUI. I had an old
Karlnet/YDI/Terabeam/Proxim backhaul radio that needed to be power
cycled regularly but that was 15 years ago and it got replaced with a
PTP500 which has now been replaced with a PTP820.
*From:* AF <af-boun...@af.afmug.com> *On Behalf Of *Sean Heskett
*Sent:* Thursday, September 24, 2020 12:30 PM
*To:* AnimalFarm Microwave Users Group <af@af.afmug.com>
*Subject:* Re: [AFMUG] Power for 450M via PacketFlux or Rectifier?
Either way is fine, we’ve chosen to do it in the PacketFlux RI so that
everything is standardized across our towers. Support staff and field
techs know that ALL APs get power from a rack injector...so when
problems happen look there and try a reboot.
-Sean
On Thu, Sep 24, 2020 at 9:18 AM Josh Baird <joshba...@gmail.com
<mailto:joshba...@gmail.com>> wrote:
We're deploying our first 450M gear soon. This site will have
a +48VDC ICT rectifier solution and DC distribution (managed).
We're going to be using a PacketFlux RackInkjector w/ Cambium Sync
modules to provide sync to the 450M 3ghz radios. We could load a
PDU module in the RackInjector as well to provide power to them.
Alternatively, we could power them directly off of the ICT managed
distribution.
Both solutions are managed (can turn them on/off via IP). Is
there any reason to use the PacketFlux PDU module over the DC
distribution panel in this scenario?
Cheers,
Josh
--
AF mailing list
AF@af.afmug.com <mailto:AF@af.afmug.com>
http://af.afmug.com/mailman/listinfo/af_af.afmug.com
<http://af.afmug.com/mailman/listinfo/af_af.afmug.com>
--
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com
