because they all randomly reboot On Tue, Jun 13, 2017 at 9:42 AM, Andreas Wiatowski <[email protected] > wrote:
> There is so much surplus gear in the market, why not just replace the AP > and call it a day? > > > > Cheers, > > > > Andreas Wiatowski, CEO > > Silo Wireless Inc. > > 1-866-727-4138 x-600 <(866)%20727-4138> > > http://www.silowireless.com > > Wireless | Fibre | VoIP | PBX | IPTV > > > > _________________________________ > > The contents of this email message and any attachments are intended solely > for the addressee(s) and may contain confidential and/or privileged > information and may be legally protected from disclosure. If you are not > the intended recipient of this message or their agent, or if this message > has been addressed to you in error, please immediately alert the sender by > reply email and then delete this message and any attachments. If you are > not the intended recipient, you are hereby notified that any use, > dissemination, copying, or storage of this message or its attachments is > strictly prohibited. > > > > > > *From: *Af <[email protected]> on behalf of Eric Muehleisen < > [email protected]> > *Reply-To: *"[email protected]" <[email protected]> > *Date: *Tuesday, June 13, 2017 at 9:04 AM > *To: *"[email protected]" <[email protected]> > *Subject: *Re: [AFMUG] reading 320 crash reports - cambium guys input > appreciated > > > > The only time I've ever seen a 320 AP crash/lock/reboot is when you leave > any of the performance monitor stats open for an extended period of time. > Our help desk routinely leaves these stats open on the AP and we will > occasionally cause reboots. > > > > The only other instance of reboots come when static/heavy wind or > lightning is in the area. The AP's surge suppression is super sensitive and > clamps any time a mouse farts. Maybe take a look at your grounding or surge > suppression as a possible cause. > > > > On Mon, Jun 12, 2017 at 7:10 PM, Steve Jones <[email protected]> > wrote: > > These are dead ducks, I know this. > > I would bet however cambium has a nifty tool they used to use that took > all the data and spit out a wtf report. > > I'm pretty sure I'm seeing random AP reboots from interference, looking > through the archive a thread from me indicated cambium told me at some > point in the past if I'm configured upper 3.65 with no failover channel it > will just crash reboot. I don't have the email chain from them because we > dumped an exchange server a few years ago. > > This particular AP was doing the thing where CSM would stay connected, > show connected, but become unresponsive, Ive dicked all I can with the sm > isolation and aging time workarounds, finally took it to a lower 3.65 > channel, but left upper enabled, as I understand, this keeps the unit > abiding by upper 3.65 rules in todays FCC new world order. > > not all that concerned right now about troubleshooting the issue, I just > really want to get a tool to read the crash reports. > > Cambium, I was a good guy and stole your AP telnet login but never > released it to the wild, Can you toss a brother a bone here? > > >
