Epmp devices losing onboarding key

I have had 2 APs and 3 cpes lose their cambium onboarding key and have to be reconnected to the cnMaestro. Firmware 2.6 and latest beta. Any help appreciated.

Don't know if there is any connection, but i was trying to onboard a "Station" in ePTP mode, but without connection to an AP, (it was a GPS-Lite unit being prepared to enter in place of a connectorized CPE). 

The radio had a working connection to the internet (DeviceAgent) reported reaching cnMaestro servers, i could ping and traceroute to external addresses. 

For some reason the credentials were being wiped and lost everytime i applied some config/rebooted the device. 

I had to setup another epmp as the AP that device was looking for, and once connected, the unit authenticated to cnMaestro right away.

Sep  1 00:17:52 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:17:52 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:17:58 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:17:58 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:18:04 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:18:04 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:18:10 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:18:10 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:18:16 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:18:16 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:18:22 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:18:22 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:18:28 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:18:28 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:18:35 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:18:35 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:18:40 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:18:40 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:18:47 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:18:47 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:18:53 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:18:53 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:19:00 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:19:00 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:19:06 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:19:06 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:19:12 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:19:12 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:19:18 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:19:18 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:19:24 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:19:24 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:19:30 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:19:30 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:19:36 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:19:36 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:19:42 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:19:42 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:19:48 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:19:48 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:19:54 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:19:54 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:20:00 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:20:00 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:20:06 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:20:06 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:20:12 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:20:12 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:20:18 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:20:18 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:20:24 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:20:24 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:20:30 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:20:30 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:20:36 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:20:36 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:20:43 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:20:43 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:20:49 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:20:49 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:20:55 ePTP_Station DEVICE-AGENT[1990]: ap_mac [Not Associated]
Sep  1 00:20:55 ePTP_Station DEVICE-AGENT[1990]: pmac unavailable, cannot proceed with registration
Sep  1 00:21:01 ePTP_Station DEVICE-AGENT[1990]:  SMs pmac [00:04:56:C2:E1:3A]
Sep  1 00:21:01 ePTP_Station DEVICE-AGENT[1990]: handle_cns_msg: MSG_REGISTER_SUCCESS received

Another unit acting as ePTP Master had no problems authenticating to cnMaestro. 

For some reason the "Station" unit won't let me select a location in my cnmaestro tree, and appears under the "default" network. 

The units were connected for several days without issue. Over the night 5 units lost connection and showed invalid cookie. Once  the onboarding key was set in the devices again they reconnected to cnMaistro. 

Hi,

 

Just wanted to clarify, if you are noticing this behaviour for first time but it has been there since long time. Once device is successfully onboarded into cnMaestro, device removes the Cambium ID and Onboarding key from UI screen for security reasons. Whenever device is rebooted or loses  connectivity next time, it presents its token obtained during onboarding to cnMaestro and supposed to be successfully re onboarded. 

Could you please email your Cambium ID and MAC address of devices, which showed its status as invalid cookie to ajay.singh@cambiumnetworks.com.

You should be able to see the current status on Home page as shown in below pictures:

  •  Cambium ID and Onboarding Key Removed After Onboarding

Hi Guilherme,

 

There is no relation between below issues and issue where devices showed up with cnMaestro status as Invalid Cookie.

Currently we have a special check on stations to not try registration with cnMaestro, if it is unable to find parent AP. As you described in your case, when station was not connected to an AP, it didn’t appear in cnMaestro but when you connected station to an AP, it appeared in cnMaestro. Hope it explains the current issue. This is a recent fix to address the issue, where some time station used to drop out of its parent AP in tree hierarchy in cnMaestro.

 

The second issue, where you are unable to change SM location in tree is because SM is always supposed to follow its parent AP as far as hierarchy is concerned. Since in this case, AP is not onboarded into cnMaestro, station is appearing under default network and its hierarchy cannot be modified.

 

Thanks,

Ajay

@Ajay
I understand this, for AP-CPE type deployments.

But ePTP mode (and most PTP scenarios), should be treated differently, in my opinion.
What happens if i reverse the master/slave sides? 

 Hi Guilherme,

It is not really about PTP mode, even in PTP mode, one end is going to be configured as AP and other end is going to be still configured as SM. The point I wanted to emphasize that it was always an undersatding that SM is going to have its parent AP. But looking at your use case, we are going to enahnce the existing fix to not wait indefinitely for parent discovery and station should be able to register itself with cnMaestro. We will priortize this fix and let you know once it is available.

Thanks,

Ajay

1 Like

What is the solution to fix devices that are showing "Invalid Cookie" in the connection status? A bunch of mine just went into that stage.

Screen Shot 2016-02-28 at 8.08.27 AM.png

Please re-enter the Cambium ID and Onboarding key on such devices and that should fix the issue.
-Ajay