I’m actually relying on George to hound them until they find and fix the problem. Note that I’m on 13.2 which is not the latest latest FW, I don’t think there have been any sync fixes since then however.
Not sure I’ve seen the issue he talks about with sync events during operation, once mine are working they are OK, I just have to remember to check sync status after any reboots. From: Colin Stanners Sent: Saturday, May 09, 2015 10:37 AM To: [email protected] Subject: Re: [AFMUG] Cambium 450 and ePMP with Packet Flux Gear That sounds problematic - what did Cambium tech support say? On Sat, May 9, 2015 at 7:53 AM, Ken Hohhof <[email protected]> wrote: I’ve definitely noticed autosync issues on 450 running 13.2 FW, on both 3.65 and 5 GHz. It will report no sync from internal GPS, or it will report receiving power port sync from a CTM2 or Syncinjector (which is actually present, unlike your case) but nonetheless will freerun. Typically occurs after a power cycle, reboot and the problem clears. From: Zack Deveaux Sent: Saturday, May 09, 2015 5:22 AM To: [email protected] Subject: Re: [AFMUG] Cambium 450 and ePMP with Packet Flux Gear For what it's worth, I've noticed AutoSync weirdness as well on PMP100 900MHz APs and it didn't seem to have anything to do with Packetflux gear. It's occurred with APs timed by Sync Pipes but also when timed by just SM timing ports. Occasionally if the AP were to lose it's timing port sync, the algorithm seemed to get 'confused'. The Event Log would list timing port sync losses. It would also list events stating that it was receiving sync via the power port which was impossible. The GUI would indicate 'receiving sync - power port' when that wasn't even a possibility, and the strange part - when timing port sync did return we were left with an AP with it's SMs dropping session and the AP GUI still showing 'receiving sync - power port' incorrectly. An AP reboot would resolve both the intermittent SM and the AP GUI display symptom completely for us until whatever triggered this state occurred again. There is no source of power port sync at these type of sites. As a workaround, I've set APs exhibiting this symptom to 'Remote AP' instead of 'Standard AP' to remove the power port as a possible sync source. If I remember correctly, that makes me not able to retrieve GPS stats when we're using a sync pipe, but should prevent the AP from freaking out if the timing pulse gets interrupted. ------------------------------------------------------------------------------ Date: Sat, 9 May 2015 04:18:19 +0000 From: [email protected] To: [email protected] Subject: Re: [AFMUG] Cambium 450 and ePMP with Packet Flux Gear Yes, the 110 PTP does have a built in GPS. On Fri, May 8, 2015 at 10:32 PM, Jon Langeler <[email protected]> wrote: Does the 110PTP have a GPS built in? Sent from my iPhone On May 8, 2015, at 7:16 PM, George Skorup (Cyber Broadcasting) <[email protected]> wrote: If it has anything to do with the issue I brought up about the 3GHz 450 going nuts and the APs saying they're losing sync briefly while the SyncInjector shows ZERO events for 1PPS active for months... It's NOT the damn SyncInjectors! It's not even surge suppressors in the path. I have observed exactly the same problems on APs with SyncPipes. There's something busted with AutoSync and/or LBT on 3GHz. And when AutoSync changes sources (on all bands), I get dropped sessions for every SM that's moving traffic, which is not supposed to happen. So I have no reason to suspect any PacketFlux gear is at fault here. That said, they are working hard on 13.4 for Canopy and they will being looking into this soon after. And I'm told the 2.4.3 release for ePMP will be a fairly big step forward for features and fixes. It was really cool that we got the 110PTP radio as a 10 SM Lite AP with 2.4.2 as well. On 5/8/2015 4:48 PM, Forrest Christian (List Account) wrote: I'll let others speak to the stability (as a couple already have). A few months ago there was an issue with a mutual customer of mine and cambium's which was having sync problems with an epmp radio. To date, I don't know if the problem was with the epmp, or with the injector, or with a gps lock, or whatever. I can't say that sync is a perfect thing - from time to time, gps modules act weird, injectors don't inject, and AP's don't work right - no matter which product you have. When sync does bad things, it behaves badly. For all I know, in this case my product *might* have been at fault. Or not. It's not important for the rest of the story.... In any case, somehow this problem morphed into a statement that somehow the SyncInjectors had some sort of systemic issue which lots of wisps were experiencing. I was not particularly amused by this, particularly since I had no communication from cambium at all in relation to this.... After some back and forth with my internal contact at cambium I was informed that a) that they were tracking some *potential* issue with external sync (usually with a syncinjector) on the ePMP and b) that they hadn't had the time to figure out if it was packetflux-specific or a general issue yet, and that if they determined it was related to my product they'd contact me back. So far, no call back, and I haven't heard any more similar complaints - and I've had interactions with a lot of people who use this regularly with ePMP with no known issues. I also haven't seen anything sync-related in the release notes since that time. -forrest On Fri, May 8, 2015 at 6:45 AM, Tyson Burris @ Internet Communications Inc <[email protected]> wrote: General question here. I saw something in the Cambium forum questioning the reliability of Packet flux Sync Injectors. If you use them, are your GPS syncs stable and is power output reliable on the 450 and ePMP gear? Tyson Burris, President Internet Communications Inc. 739 Commerce Dr. Franklin, IN 46131 317-738-0320 Daytime # 317-412-1540 Cell/Direct # Online: www.surfici.net <mime-attachment.png> What can ICI do for you? Broadband Wireless - PtP/PtMP Solutions - WiMax - Mesh Wifi/Hotzones - IP Security - Fiber - Tower - Infrastructure. CONFIDENTIALITY NOTICE: This e-mail is intended for the addressee shown. It contains information that is confidential and protected from disclosure. Any review, dissemination or use of this transmission or its contents by unauthorized organizations or individuals is strictly prohibited. -- Forrest Christian CEO, PacketFlux Technologies, Inc. Tel: 406-449-3345 | Address: 3577 Countryside Road, Helena, MT 59602 [email protected] | http://www.packetflux.com
