We have noticed on some 450i APs that go into Free Run stay stuck in this mode even after sync has been restored on the power port. It will not switch back from Free Riun without a reboot. This seem to be new unwanted bahaviour that was not present in V14.2.1 which we had previously been running on these APs. Possibly this is a known issue, so can someone from Cambium please confirm if this is a known issue with V15.1.1 and when it will be fixed? Thanks.
What are you using for sync?
I've had this issue too, but I've only noticed it on the original PMP450 AP's (we haven't seen this with the newer 450i AP's) and only once I started using more recent firmware versions like 15.X... I've tried a number of things to fix this including:
- Moving from a LastMile CTM1 to Packetflux sync injector (didn't solve the issue)
- Moving from the older style 600 series ethernet lightning surge protection to new Cambium gig-e surge protection (didn't solve the issue)
- Moving from a normal packetfluc to a gig-e version of the packetflux (didn't solve the issue)
Thankfully I haven't had too many issues because the vast majority of the legacy PMP450 AP's can still get their sync via iGPS... there's only a couple times where I've noticed a sector freaking out because of lack of sync, and I login and it's in freerun mode, and then I reboot it, and it typically picks up it's sync pulse from the ethernet port.
At this point we're not sure what to do, other then maybe try a CMM5, or a LastMile CTM2.
1 Like
We are using the Packet Flux sync injector on the power port. I am hoping someone from Cambium will pick up on this as it was not an issue on 14.2.1 firmware so something in the firmeware must have changed to cause this. At the moment this is stopping us from upograding the rest of our network to 15.1.1.
We also had many problems with 450/450i and packetflux... I think Cambium changed many things on sync...
Right now I am waiting for some uGPS and CMM5 to try.
We are looking into this issue... stay tuned. I don't have any answers as yet.
Ive had a few issues on one tower like this using packetflux on 450i. What worked for me was to set the access points to "Auto Sync" instead of "AutoSync+Free Run". No problem since making that change.
1 Like
@Kevin Simms wrote:Ive had a few issues on one tower like this using packetflux on 450i. What worked for me was to set the access points to "Auto Sync" instead of "AutoSync+Free Run". No problem since making that change.
Have you noticed in the AP's logs that the pulse from the ethernet port is flapping... we're seeing this on multiple older 2.4/3.65 450 AP's using PacketFlux gig sync injects with Cambium gig LPU's. Sometimes it will just fall into free run mode and not come back. It will take a power cycle to get it to listen to ethernet pulse again.
| 09/18/2017 : 05:13:45 PST : Lost sync pulse from Power Port |
| 09/18/2017 : 05:13:45 PST : Acquired sync pulse from On-board GPS |
| 09/18/2017 : 06:45:47 PST : Lost sync pulse from On-board GPS |
| 09/18/2017 : 06:45:47 PST : Acquired sync pulse from Power Port |
| 09/20/2017 : 06:14:41 PST : Lost sync pulse from Power Port |
| 09/20/2017 : 06:14:41 PST : Acquired sync pulse from On-board GPS |
| 09/20/2017 : 06:15:11 PST : Lost sync pulse from On-board GPS |
| 09/20/2017 : 06:15:11 PST : Acquired sync pulse from Power Port |
| 09/20/2017 : 06:27:00 PST : Lost sync pulse from Power Port |
| 09/20/2017 : 06:27:00 PST : Acquired sync pulse from On-board GPS |
| 09/20/2017 : 06:32:58 PST : Lost sync pulse from On-board GPS |
| 09/20/2017 : 06:32:58 PST : Acquired sync pulse from Power Port |
| 09/20/2017 : 06:48:18 PST : Lost sync pulse from Power Port |
| 09/20/2017 : 06:48:18 PST : Acquired sync pulse from On-board GPS |
| 09/20/2017 : 07:41:07 PST : Lost sync pulse from On-board GPS |
| 09/20/2017 : 07:41:07 PST : Acquired sync pulse from Power Port |
| 09/20/2017 : 08:05:17 PST : Lost sync pulse from Power Port |
| 09/20/2017 : 08:05:17 PST : Acquired sync pulse from On-board GPS |
| 09/20/2017 : 09:29:54 PST : Lost sync pulse from On-board GPS |
| 09/20/2017 : 09:29:54 PST : Acquired sync pulse from Power Port |
| 09/20/2017 : 09:50:22 PST : Lost sync pulse from Power Port |
| 09/20/2017 : 09:50:22 PST : Acquired sync pulse from On-board GPS |
| 09/20/2017 : 11:06:31 PST : Lost sync pulse from On-board GPS |
| 09/20/2017 : 11:06:31 PST : Acquired sync pulse from Power Port |
| 10/10/2017 : 18:42:54 PST : Lost sync pulse from Power Port |
| 10/10/2017 : 18:42:54 PST : Acquired sync pulse from On-board GPS |
| 10/10/2017 : 18:44:10 PST : Lost sync pulse from On-board GPS |
| 10/10/2017 : 18:44:10 PST : Acquired sync pulse from Power Port |
| 10/10/2017 : 18:47:38 PST : Lost sync pulse from Power Port |
| 10/10/2017 : 18:47:38 PST : Acquired sync pulse from On-board GPS |
| 10/10/2017 : 19:06:55 PST : Lost sync pulse from On-board GPS |
| 10/10/2017 : 19:06:55 PST : Acquired sync pulse from Power Port |
| 10/19/2017 : 18:39:56 PST : Lost sync pulse from Power Port |
| 10/19/2017 : 18:39:56 PST : Acquired sync pulse from On-board GPS |
| 10/19/2017 : 18:42:37 PST : Lost sync pulse from On-board GPS |
| 10/19/2017 : 18:42:37 PST : Acquired sync pulse from Power Port |
| 10/19/2017 : 19:13:39 PST : Lost sync pulse from Power Port |
| 10/19/2017 : 19:13:39 PST : Generating Sync - Free Run |
| 10/19/2017 : 19:13:49 PST : Acquired sync pulse from Power Port |
It would be really cool if you could specify the priority and time-out in which the AP seeks for a GPS pulse... iGPS (for legacy 450 AP's), uGPS/AUX port, or ethernet port pulse... it checks all these, and if all of them fail, it can be configured to go into free run mode or just shutdown all together (while continuing to look for a pulse from any available sources).
Bonus points for allowing legacy 450 AP's to extrapolate iGPS data for GPS coordinates in the GUI (and cnMaestro), while still using uGPS/AUX or ethernet pulse.
We are having the same issue. For us it happens on PMP450i 3.65 radios but NOT on PMP450i 900 MHz radios.
So setting it to just 'autosync' with no free run has somewhat helped... we still have radios that are periodically losing their sync pulse off the ethernet port, but now they're just flapping between iGPS and ethernet pulse, instead of failing completely and staying in free run mode.
1 Like
Try to power the PacketFlux with only one AP instead both.
We had the same problem with PacketFlux and we solved that with power though only an AP
Hi all,
The issue appears to be with the addition of a new 'Cambium Sync' alonside the original 'Canopy Sync' on 15.1.1
In order to resolve the issue, no reboot needed, telnet into the radio and run
`syncpowerport off camb`
This disables the new 'Cambium Sync' and allows the radio to sync on the original received 'Canopy Sync'
Hopefully this will get resolved soon...
@Lightnet_Barry wrote:Hi all,
The issue appears to be with the addition of a new 'Cambium Sync' alonside the original 'Canopy Sync' on 15.1.1
In order to resolve the issue, no reboot needed, telnet into the radio and run
`syncpowerport off camb`
This disables the new 'Cambium Sync' and allows the radio to sync on the original received 'Canopy Sync'
Hopefully this will get resolved soon...
Very interesting... I've gone ahead and made this change to some of our most problematic AP's... we'll know if this fixes the issue in a few days.
Does 15.1.2 do anything to fix this?
I have realised that I did not include the full actions necessary.
On the unit which first experienced this issue I have also run
`synctimingport off`
It appears to be necessary to turn off both timing port sync and powerport cambium sync for the sync to be stable.
My inital unit has remained stable for >3 weeks with both turned off.
Barry
I updated my most problemic pmp450i 5.x cluster to 15.1.2 bit over 2 weeks ago and it has not acted up since but that could be coincidence.
We are seeing it on PMP450i 900Mhz. Also seeing it on PMP450i and PTP450i in 5Ghz. I was hoping 15.1.2 would resolve it but apparently not. All our PxP450i gear is powered by one form or another of PacketFlux sync injection.
Is Cambium getting anywhere on this?
So after trying the `syncpowerport off camb` on our AP's for awhile, we're still seeing lots of GPS sync drops still. Can we get PLEASE get an official word or at least 'we're working on a fix' from Cambium here... I think enough people are having an issue and seeing a pattern here.