cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1774
Views
10
Helpful
6
Replies

New 9115AP won't connect to a New C9800-L-F

Smorgan
Level 1
Level 1

I am trying to setup a new WLC 9800-L-F (version 17.3) in conjunction with a 9115AP (version 8.10)  but am having issues getting the AP to connect to the controller. 

 

This is the error that I am seeing on the AP when attempting to connect. 

 

[*01/29/2022 14:07:16.7850] CAPWAP State: Discovery
[*01/29/2022 14:07:16.7860] IP DNS query for CISCO-CAPWAP-CONTROLLER.X.COM
[*01/29/2022 14:07:36.8070] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*01/29/2022 14:07:36.8090] Discovery Response from 172.X,X.10
[*01/29/2022 14:07:47.0000]
[*01/29/2022 14:07:47.0000] CAPWAP State: DTLS Setup
[*01/29/2022 14:08:44.0310]
[*01/29/2022 14:08:44.0310] CAPWAP State: DTLS Teardown
[*01/29/2022 14:08:44.1210] upgrade.sh: Script called with args:[ABORT]
[*01/29/2022 14:08:44.1620] do ABORT, part1 is active part
[*01/29/2022 14:08:44.1790] upgrade.sh: Cleanup tmp files ...
[*01/29/2022 14:08:44.1980] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*01/29/2022 14:08:44.1980] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*01/29/2022 14:08:48.7810] No more AP manager addresses remain..
[*01/29/2022 14:08:48.7810] No valid AP manager found for controller 'oc-ncwwlc01' (ip: 172.X.X.10)
[*01/29/2022 14:08:48.7810] Failed to join controller oc-wlc01.
[*01/29/2022 14:08:48.7810] Failed to join controller.

 

The WLC Tw0/0/0 is configured for my primary vlan 10.X.X.10 and Gig0/0/0 is configured for my Wireless Management Vlan 172.X.X.10 

I can ping the AP and BOTH WLC interfaces from the Switch. 

 

Any thoughts or suggestions? 

1 Accepted Solution

Accepted Solutions

Hi Flavio,

There is another thread by the same user, I can see the same configuration file there as well. I think this is a copy of the same question.

Re: 9115 AP not connecting to WLC 9800-L-F - Cisco Community

9800's doesn't work like a router. VRF is there only to segregate OOB interface. It doesn't officially support VRF's in data interfaces. 

View solution in original post

6 Replies 6

Hi

Why you G0 is inside a vrf?

 

interface GigabitEthernet0
vrf forwarding Mgmt-intf
ip address 172.X.X.10 255.255.0.0
negotiation auto
no mop enabled

 

Can you ping AP from WLC or vice-versa?

 

 

Hi Flavio,

In 9800's GigabitEthernet0 interface is equal to Service port. So to maintain a total OOB experience Cisco has designed it this way. I can confirm that this is normal.

 

Hi

 If that interface is equivalent to service port, he shouldn´t expect to connect AP on it. Service port is for mgmt only.  That´s why I asked  for ping validation between WLC and AP as ping between SW and AP and SW and WLC is not valid.

 If one interface is inside a vrf, everything else  must be inside this vrf is they intend to communicate, otherwise, it is necessary to leak traffic in an out.

Hi Flavio,

There is another thread by the same user, I can see the same configuration file there as well. I think this is a copy of the same question.

Re: 9115 AP not connecting to WLC 9800-L-F - Cisco Community

9800's doesn't work like a router. VRF is there only to segregate OOB interface. It doesn't officially support VRF's in data interfaces. 

 

Thank you for all the help and direction! 

While I was able to ping across both networks and bidirectional from each device the APs wouldn't join. The resolution seemingly was nothing to do with the WLC configuration. I changed my upstream switch port connecting to the service port on the WLc from a Trunk (native vlan WM vlan) back to an access port and restarted everything and the AP nearly instantly began communicating with the controller. 

 

Thank you for all the help and direction! 

Review Cisco Networking for a $25 gift card