Sending you an email David. I'd like to arrange remote access to have a look.
Anyone else seeing similar issues, please feel free to reach out directly [email protected] On Thu, Nov 17, 2016 at 12:45 PM, David Hulsebus <[email protected]> wrote: > Long read, but wanted get out what we have found. Still don't have a > workable solution other than replacing links with Mimosa which we are doing > now to all the P to P links. > > Here's a snipit of what a log shows. > > Nov 15 13:42:12 wireless: ath0 Received disassoc from > 80:2a:a8:a8:56:81. Reason: Unspecified reason (1). > Nov 15 13:42:13 wireless: ath0 New Access Point/Cell > address:Not-Associated > Nov 15 13:42:14 wireless: ath0 New Access Point/Cell > address:80:2A:A8:A8:56:81 > > All these have Airmax quality and capacity numbers above 90% - SNR's above > 30 some near 50 > > Point to Point PBE-M5-400 V 5.6.2 firmware - 20M Channel - DFS 5500 - 2.3 > m link. No DFS issues. The link will stop passing traffic. Logging into the > AP shows station at 144/6.5 rate. If I kick the station it will > re-associate and work again - never more than a week sometimes less than a > day. Looking at the station on the AP side the TX combined signal goes away > and comes back a couple seconds later. A reboot of the AP looks to fix it > as well as a kick of the station. > > Point to Point NB-13's V5.6.3 firmware - 10M channel - 1.2m link - power > turned down - quality and capacity well above 95%. No interference issues. > Ran for a few months with no problems. Started having the same issue as > above radios. I noticed the latency number would jump to 100-200-500ms. > Tried updating from 5.6.3 to 5.6.5 eventually to worked up to 5.6.9 - same > issue persists. > > Point to Point NB25 to PBE-M5-400 V5.6.3 on both - 30M channel - 5.6 mile > - non DFS. This is the first link I started having issues with. Thought it > was related to XM to XW hardware. Replaced one side with a PBE-400 and the > issue continued although it took a few weeks to show up. I did change the > frequency a weeks ago from 5755 to 5760 it seemed to lasted longer without > dropping but still drops off . I've tried from 5.6.3 through 5.6.9 with no > success. > > Point to Point NB25 to PBE-M5-400 V5.6.2 on both - 20M channel - 2.8 mile > DFS link. No issues at all until I replaced the NB25 with a NBE-400. Now I > see 144.444/6.5 on it multiple times per day. The AP was the NB25. > > I had an NSM2 feeding 7 clients 10M channel - mixed NS2, M2, M2L, NB13's > and NB18's - Replaced the AP with a PBE-M2400 to focus the energy down a > road and started having issues with it a couple weeks later. Replaced all > the clients that weren't XW hardware and the issue continues. > > PBE-M2-400 AP feeding 2 NB13 and 1 PBE-M2-400 client. All clients have the > same issue, not always at the same time. I usually kick all three clients > so as not to deal with the issue multiple times per day. Again, have > updated firmware from 5.6.2 to 5.6.9 over the last month to no avail. > > I've tried all versions of firmware between 5.6.2 and 5.6.9 No beta yet > but in reading the beta forum I don't expect it would help. Others > reporting similar problems all the way through rc15 beta. > > I see in the Ubiquiti forums folks with similar issues being reported but > no fix or what seems an acknowledgement of the issue. Any ideas ? > > > On Tue, Nov 15, 2016 at 3:47 PM, Troy Gibson, Byhalia.net < > [email protected]> wrote: > >> Clay that is exactly what is happening. Issue is weather is incredible >> for October and November as well as these are long standing connections and >> not new crimps. >> >> Simple reboot remotely through Air Control or directly connected to >> station side restores connection. >> >> I was reviewing beta firmware, but unsure if it would fix this issue. >> >> Thanks, >> >> Troy >> >> >> >> Sent from my Verizon, Samsung Galaxy smartphone >> >> -------- Original message -------- >> From: Clay Stewart <[email protected]> >> Date: 11/8/16 12:29 PM (GMT-05:00) >> To: Ubiquiti Users Group <[email protected]> >> Subject: Re: [Ubnt_users] Backhaul Radios freeze on Station side >> >> If you saying stopped passing traffic on Lan side, but remained powered >> and connected to AP, I would suspect a bad crimper and cold weather. >> >> On Nov 7, 2016 1:04 PM, <[email protected]> wrote: >> >>> I have had 3 towers in the past week have the Station side of the >>> Backhaul >>> link lock up and not transfer service to the tower until rebooted, but >>> each stayed connected to the AP side of the Backhaul connection. In all >>> 3 >>> cases, I was able to log into both the AP and Station side of the >>> backhaul >>> link to reboot the station remotely. Once rebooted every CPE came back >>> online. >>> >>> These radios have been in operation for months and zero issues. The >>> details are below for the setup and firmware. >>> >>> The radio's are M series Rocket radios. >>> >>> Tower 1: M5 5.6.4 XW to M5 5.6.4 XW >>> >>> Tower 2: M365 5.6.4 XM to M365 5.6.4 XM >>> >>> Tower 3: PBE M5 5.6.6 XW to M5 5.6.6 XM >>> >>> I have not seen this occur previously and wondered if it was a firmware >>> issue. Also, I am not using any DFS channels for either tower. Any >>> ideas >>> or areas to monitor is appreciated. >>> >>> Troy >>> >>> _______________________________________________ >>> Ubnt_users mailing list >>> [email protected] >>> http://lists.wispa.org/mailman/listinfo/ubnt_users >>> >> >> _______________________________________________ >> Ubnt_users mailing list >> [email protected] >> http://lists.wispa.org/mailman/listinfo/ubnt_users >> >> > > > -- > David Hulsebus > Portative Technologies, LLC > www.portative.com > 812-738-7007 > > _______________________________________________ > Ubnt_users mailing list > [email protected] > http://lists.wispa.org/mailman/listinfo/ubnt_users > >
_______________________________________________ Ubnt_users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/ubnt_users
