Force 200 Frequent Dropouts with Perfect LOS

I have a Force 200 shooting to an ePMP sector a little over three miles out. The shot is picture perfect with only one transmission line resting above our shot. It is shooting to the East sector of a four-sector ePMP 1000 deployment not implementing frequency reuse.

The first ePMP Force 200 would connect to the sector, then drop out almost instantly. After replacing power supply, cable and changing frequencies/sector info, we swapped the SM. The second Force 200 did better, but is still experiencing very frequent dropouts. This is the only customer on this sector - the opposite sector has almost a dozen customers who are perfectly fine.

I have attached the stats and log from the SM. You can see it displays 34 session drops and 14 reboots. I'm kind of at my witts end here, I'm really hoping somebody will have some insight.

Could this be a GPS issue?

Dec  5 08:14:15 Col2 ePMP East DEVICE-AGENT[2621]: rx_config_notify_cb: Send MSG_CONFIG_CHANGE_NOTIFY to cnMaestro
Dec  5 08:14:16 Col2 ePMP East DEVICE-AGENT[2621]: rx_config_notify_cb: Send MSG_CONFIG_CHANGE_NOTIFY to cnMaestro
Dec  5 08:14:16 Col2 ePMP East DEVICE-AGENT[2621]: rx_config_notify_cb: Send MSG_CONFIG_CHANGE_NOTIFY to cnMaestro
Dec  5 08:14:16 Col2 ePMP East kernel: [84910.720000] GPS Sync Lost. (14:14:16:956323)
Dec  5 08:14:18 Col2 ePMP East DEVICE-AGENT[2621]: rx_config_notify_cb: Send MSG_CONFIG_CHANGE_NOTIFY to cnMaestro
Dec  5 08:14:18 Col2 ePMP East DEVICE-AGENT[2621]: rx_config_notify_cb: Send MSG_CONFIG_CHANGE_NOTIFY to cnMaestro
Dec  5 08:14:19 Col2 ePMP East DEVICE-AGENT[2621]: rx_config_notify_cb: Send MSG_CONFIG_CHANGE_NOTIFY to cnMaestro
Dec  5 08:14:19 Col2 ePMP East DEVICE-AGENT[2621]: rx_config_notify_cb: Send MSG_CONFIG_CHANGE_NOTIFY to cnMaestro
Dec  5 08:14:19 Col2 ePMP East DEVICE-AGENT[2621]: rx_config_notify_cb: Send MSG_CONFIG_CHANGE_NOTIFY to cnMaestro
Dec  5 08:14:19 Col2 ePMP East DEVICE-AGENT[2621]: rx_config_notify_cb: Send MSG_CONFIG_CHANGE_NOTIFY to cnMaestro
Dec  5 08:14:19 Col2 ePMP East DEVICE-AGENT[2621]: rx_config_notify_cb: Send MSG_CONFIG_CHANGE_NOTIFY to cnMaestro
Dec  5 08:14:21 Col2 ePMP East kernel: [84914.930000] GPS Sync Lost. (14:14:21:168383)
Dec  5 08:14:26 Col2 ePMP East kernel: [84920.750000] GPS Sync Restored. (14:14:26:986314)

Hello ceander,

Don't think GPS Sync was a factor that specific time, sinceĀ it was restored rather quickly, but both your AP and SM syslogs do show some weird activities... The "Bad LLDP packet" and the frequent "MSG_CONFIG_CHANGE_NOTIFY" from the AP to cnMaestro do not seem normal... You may be better of submitting a ticket with Cambium Support (https://www.cambiumnetworks.com/support/contact-support/) for assistance.

Regards

1 Like

Thanks for the reply Luis. I have submitted a ticket but also wanted to hear from the community.

It appears that the sector that is fuctioning properly has far different GPS stats than the malfunctioning one despite being located ~5ft from each other on the same horizontal plane.(attached PDFs).

Have you figured this out yet or still working on it? You have not posted any confirmation either way.

You say you have a force 200 as an sm on an empty sector that is infront of an oposite sector with 13 subs.
What you havent told us is frequency plan, timing method, frame size and mix, sm target power.
Just because your not using the same frequency back to back does not mean you can gave differing config between those APs on that tower and on any tower that can be heard from there. It is very important to consider all of these metrics when setting up a stable radio network. This is what makes or breaks a radio network.