NCOB02107 - AP's unable to join controller

[davariganesh1994]

Hi All,

Facing below error issue while onboarding AP's to DNAC controller 

NCOB02107: Executed Workflow Timed out. AP didn't join the controller. Please check connectivity/configuration to fix the issue.

[Torbjørn]

This indicates that your access point is unable to join your WLC for some reason. Are you 100% certain that there is no connectivity issue between your AP and your WLC(firewall rules, port auth etc)? Can you see anything in the logs of your WLC?

[davariganesh1994]

Hey Torbjon, 

Connectivity from AP to WLC seems fine. From log on DNAC and AP, AP receiving the PNP config and starting CAPWAP discovery, but getting stuck.

On DNAC AP onboarding is getting completed 80% and after around 1 hrs. its giving error.

If we use external power injector its working fine.

Could you please suggest how we can upgrade the AP's before starting joining to DNAC/controller ?

[salvatore-sp]

Hello,

i have the same issue at the moment. Can`t join APs to the DNA Center. After 80% the plug&play process timed out. Do you fixed it already ?

[Torbjørn]

@davariganesh1994 Interesting that an external power injector would make a difference here. Does it make a difference consistently?

Which version of Cat-C are you running? I am experiencing this for one of the installations I manage on 2.3.7.7 and 2.3.7.9 where the PNP onboarding does time out during AP image upgrade. In my case the access points actually do join the controller with the appropriate config and show up in the inventory I give them enough time - so I have just concluded that this is _mostly_ cosmetic.

Does this match what you're seeing? I would create a TAC case for this if it is causing issues and you have sufficient connectivity between your APs, WLC and Cat-C.

[salvatore-sp]

Hi,

our APs take his power from PoE. Cat-C Version 2.3.5.6 but in 2 weeks we will uprade our center. What's really strange is that the PNP stopped after 80%, but the AP appeared on the WLC. Resyncing from the WLC didn't help either.

Maybe I should wait until the update; maybe the problem will resolve itself.

[davariganesh1994]

@Torbjørn, the solution with the external power injector works for some APWs for which PNP was stuck. 

[davariganesh1994]

Here is my topology.

1 - APW will get an IP address from DHCP ( Which consists of option 43 with DNAC enterprise URL)

2 - On DNAC, it will show 40% stuck; we need to claim the AP.

3 - AP will get the controller information and try to contact the primary controller for OS download

4 - It will be stuck on 80 % till OS gets downloaded.

@salvatore-sp, check that there is no blocking on the firewall / ACL applied.