cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1496
Views
6
Helpful
24
Replies

Ap 9130 can't access to 9800-L-F

sigcerder
Level 1
Level 1

Hi Collegues.
Can you help me solve a problem. There is an issue with connecting a Cisco AP 2802 access point to a Cisco 9800-L wireless controller.
The access point fails during the CAPWAP Discovery stage, and the following logs are observed on the AP console:

[*11/19/2024 18:22:27.7743] CAPWAP State: Discovery
[*11/19/2024 18:22:27.7788] Not Sending the TLV_AP_EWLC_TAGS_PAYLOAD.
[*11/19/2024 18:22:27.7791] Discovery Request sent to 10.1.2.7, discovery type STATIC_CONFIG(1)
[*11/19/2024 18:22:27.7845] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*11/19/2024 18:23:01.9391] Received Capwap watchdog update msg.
[*11/19/2024 18:23:34.6082] !!!!! {watchdogd} Unable to reach gateway for 1200 seconds


Network Diagram

Switch: Cisco CBS350 in L2 mode connects the controller and the AP.
Wireless Controller: Cisco 9800-L-F (physical) is configured with a management VLAN (VLAN 2, IP 10.1.2.7).
Access Point: Cisco AP 2802 connected in VLAN 60 (IP 10.1.60.10) on SW
Router: GW-1111 acting as the gateway and DHCP server for the network:
Router IP: 10.1.2.1.
DHCP server provides IP addresses for VLAN 60.

 

Screenshot_4.png


Error Details
The AP and controller can ping each other successfully.
However, the CAPWAP Discovery process fails, and the AP switches to standalone mode.

I guess there is a possible issues, incorrect trustpoint on the controller — does it need to be reconfigured or reissued?
What mode is recommended for configuring the controller — L2 between the router and the switch or L3?
What additional configurations are required to ensure successful CAPWAP Discovery?

 

GW Configuration:

interface GigabitEthernet0/1/2
description SW-C350
switchport
switchport trunk native vlan 2
switchport mode trunk
switchport nonegotiate
spanning-tree portfast trunk

interface Vlan2
description NETWORK-MGMT
ip address 10.1.2.1 255.255.255.0
ip nat inside
ip virtual-reassembly

interface Vlan60
description LWAP
ip address 10.1.60.254 255.255.255.0
ip nat inside
ip virtual-reassembly

ip default-gateway 10.1.100.254

ip dhcp pool VLAN60
network 10.1.60.0 255.255.255.0
default-router 10.1.60.254
dns-server 8.8.8.8 8.8.4.4
lease 30
!


SW Configuration:

interface vlan 2
name NETWORK_MGMT
ip address 10.1.2.2 255.255.255.0

interface GigabitEthernet7
description AP-9130
spanning-tree link-type point-to-point
switchport mode trunk
switchport access vlan none
macro description "switch "
!next command is internal.
macro auto smartport dynamic_type switch
!
interface GigabitEthernet17
description 9800
switchport mode trunk
switchport access vlan none
switchport trunk native vlan 2
!
ip dhcp snooping
ip dhcp snooping information option allowed-untrusted
ip dhcp snooping vlan 2
ip default-gateway 10.1.2.1


9800 Configuration:

vlan 60
name LWAP

interface TwoGigabitEthernet0/0/0
switchport trunk native vlan 60
switchport mode trunk
negotiation auto
!
interface TwoGigabitEthernet0/0/1
negotiation auto
!
interface TwoGigabitEthernet0/0/2
negotiation auto
!
interface TwoGigabitEthernet0/0/3
no switchport
ip address 192.168.1.1 255.255.255.0
negotiation auto
!
interface TenGigabitEthernet0/1/0
description SW-C350
switchport trunk native vlan 2
switchport mode trunk
switchport nonegotiate
negotiation auto
!
interface TenGigabitEthernet0/1/1
no negotiation auto
no snmp trap link-status
!
interface GigabitEthernet0
vrf forwarding Mgmt-intf
ip address dhcp
negotiation auto
!
interface Vlan1
no ip address
no ip proxy-arp
shutdown
!
interface Vlan2
ip address 10.1.2.7 255.255.255.0
no ip proxy-arp
!
ip default-gateway 10.1.2.1
ip route 0.0.0.0 0.0.0.0 10.1.2.1
!
!

24 Replies 24

WLC-9800#show ap uptime
Number of APs: 0


show wireless stats ap join summary
Number of APs: 0

Base MAC Ethernet MAC AP Name IP Address Status Last Failure Phase Last Disconnect Reason
----------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

show wireless stats ap mac address <mac of AP> join detailed
No APs

debug cap client error - No information the log is empty

Spoiler
debug cap client events:
[*11/19/2024 18:13:53.8397] CAPWAP State: Discovery
[*11/19/2024 18:13:53.8418] Not Sending the TLV_AP_EWLC_TAGS_PAYLOAD.
[*11/19/2024 18:13:53.8419] Discovery Request sent to 10.1.2.7, discovery type STATIC_CONFIG(1)
[*11/19/2024 18:13:53.8420]
[*11/19/2024 18:13:53.8420] Send Discovery requests to dcb capwapCfg.mwarIpAddr[0]=10.1.2.7
[*11/19/2024 18:13:53.8434] Not Sending the TLV_AP_EWLC_TAGS_PAYLOAD.
[*11/19/2024 18:13:53.8434] Discovery Request sent to 10.1.2.7, discovery type STATIC_CONFIG(1)
[*11/19/2024 18:13:53.8435]
[*11/19/2024 18:13:53.8435] SENDING DISCOVERY REQUEST: WLC name 9800, addr 10.1.2.7
[*11/19/2024 18:13:53.8435]
[*11/19/2024 18:13:53.8448] Not Sending the TLV_AP_EWLC_TAGS_PAYLOAD.
[*11/19/2024 18:13:53.8448] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*11/19/2024 18:13:53.8448] AP in local mode switch to standalone
[*11/19/2024 18:14:03.2966] Could not discover any WLC.
[*11/19/2024 18:14:13.2979] Starting Discovery.
[*11/19/2024 18:14:23.2996]
[*11/19/2024 18:14:23.2996] CAPWAP State: Discovery
[*11/19/2024 18:14:23.3019] Not Sending the TLV_AP_EWLC_TAGS_PAYLOAD.
[*11/19/2024 18:14:23.3020] Discovery Request sent to 10.1.2.7, discovery type STATIC_CONFIG(1)
[*11/19/2024 18:14:23.3022]
[*11/19/2024 18:14:23.3022] Send Discovery requests to dcb capwapCfg.mwarIpAddr[0]=10.1.2.7
[*11/19/2024 18:14:23.3065] Not Sending the TLV_AP_EWLC_TAGS_PAYLOAD.
[*11/19/2024 18:14:23.3066] Discovery Request sent to 10.1.2.7, discovery type STATIC_CONFIG(1)
[*11/19/2024 18:14:23.3066]
[*11/19/2024 18:14:23.3066] SENDING DISCOVERY REQUEST: WLC name 9800, addr 10.1.2.7
[*11/19/2024 18:14:23.3066]
[*11/19/2024 18:14:23.3084] Not Sending the TLV_AP_EWLC_TAGS_PAYLOAD.
[*11/19/2024 18:14:23.3085] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*11/19/2024 18:14:23.3085] AP in local mode switch to standalone
[*11/19/2024 18:14:32.7563] Could not discover any WLC.
[*11/19/2024 18:14:42.7575] Starting Discovery.
[*11/19/2024 18:14:52.7592]
[*11/19/2024 18:14:52.7592] CAPWAP State: Discovery
[*11/19/2024 18:14:52.7621] Not Sending the TLV_AP_EWLC_TAGS_PAYLOAD.
[*11/19/2024 18:14:52.7622] Discovery Request sent to 10.1.2.7, discovery type STATIC_CONFIG(1)
[*11/19/2024 18:14:52.7624]
[*11/19/2024 18:14:52.7624] Send Discovery requests to dcb capwapCfg.mwarIpAddr[0]=10.1.2.7
[*11/19/2024 18:14:52.7646] Not Sending the TLV_AP_EWLC_TAGS_PAYLOAD.
[*11/19/2024 18:14:52.7647] Discovery Request sent to 10.1.2.7, discovery type STATIC_CONFIG(1)

..........

MHM

Rich R
VIP
VIP

> interface GigabitEthernet7
> description AP-9130
is missing "switchport trunk native vlan 60"
Otherwise set the port to access mode in vlan 60.

AP management is always untagged.

Yes, I fixed this, I also tried different configurations:

sw mode trunk
sw trunk native vlan 60

sw mode access
sw access vlan 60

But the result is the same. My version of AP

AP Running Image : 17.6.4.56
Primary Boot Image : 17.6.4.56
Backup Boot Image : 8.10.112.0

Rich R
VIP
VIP

Have you checked your controller config with the Config Analyzer (link below) using the output from "show tech wireless"?

Looks like you have defined the native vlan on the WLC but not on the switch port
also recommend defining the native vlan for the AP

Can you ping the WLC from the source interface of the AP VLAN from the router?

can you do a show interfaces trunk on the switch and WLC
and show wireless interface summary on the WLC

Which physical port is connected from the WLC to the switch

 

You may also need this command:
wireless management interface interface-type interface-number

*****Help out other by using the rating system and marking answered questions as "Answered"*****
*** Please rate helpful posts ***

Which is exactly why I was asking whether they'd tried Config Analyzer @Haydn Andrews - that will highlight obvious mistakes like missing wireless management interface.  So far not seen any reply ...

sigcerder
Level 1
Level 1

Dear colleagues, sorry for the silence. Yes, it finally worked for me.
I used the command: wireless management interface vlan2 and my ap was able to connect to the controller.
The Wireless Config Analyser also showed the need. Admittedly, I had overlooked this.
For the sake of understanding, could you explain what this command does and why the point cannot join without it, when there is no reason for it not to join?

I think we all assume that what you sharing is part of config not all 

so we dont ask about WMI 
WMI is mandatory for WLC and it use to join AP

WMI IP is use in discovery and it the IP of CAPWAP tuunel 

you maybe need to check this link 

https://www.wiresandwi.fi/blog/cisco-wlc-9800-base-initial-configuration-cli

MHM

 

tnx for sharing, I'll check it out and use it in my production.

Review Cisco Networking for a $25 gift card