cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
12900
Views
15
Helpful
12
Replies

9120ax Access Point not joining 3504 wlc

RGilbert
Level 1
Level 1

9120 AX Access point not joining controller (8.9.111.0 code) and the error I am getting at every turn is - Waiting for preferred uplink IP configuration - anyone have anything I can try.  I did try to manually place IP on access point.  Under Security tab - AP Policies - I checked first 3 boxes for certs SSC MIC and LSC.  Also under Controller Tab - Advanced - DHCP - I enabled DHCP proxy - which was unchecked.  I have since taken those configs off as there was no change in AP.  Any idea on how to get this set?  

1 Accepted Solution

Accepted Solutions

1. Fix this first - Do not use 8.9 code. Upgrade 3504 to any/latest 8.10. code. (Cisco doesn't support 8.9 code period.)
2. what's the AP running code - AP#show version. (Brand new AP9120 generally have 8.10.X.X code on it)
3. what's the AP's power-source OR use appropriate suggested power source for 9120.
4. Have only MIC checked on WLC.
5. share the AP connected switch port config. And does this vlan have access to DHCP server -Swap with wired client to confirm.
6. Did the physical/wired0 interface come up- show int wired, show control wired -Are AP connected to 3504 directly or POE switch.
7. share the AP connected switch port config.
8. AP#debug dhcp errors/events/packets
9. obtain full AP boot-up logs to get hints.
10. Check the Eth cable

(Done many deployments/migrations with 9120 and AireoOS 8.10 - Generally, it works very smooth.)

View solution in original post

12 Replies 12

Did you try placing AP on the same vlan as WLC management vlan ?

 

If possible attach AP console output to have a look.

 

HTH

Rasika

it is untagged.  Trying to use as test AP for ax/WiFi 6.  This is main output as it comes up.

*06/27/2019 00:06:47.4880] <=== Deactivate Deep Green Mode
[*06/27/2019 00:06:51.3090] Waiting for preferred uplink IP configuration
[*06/27/2019 00:06:56.3160] Waiting for preferred uplink IP configuration
[*06/27/2019 00:07:01.3230] Waiting for preferred uplink IP configuration
[*06/27/2019 00:07:02.3280] Resetting wired0 and restart DHCP client
[*06/27/2019 00:07:02.5190] wired0 (Ext switch port: 7) (Logical Port: 15) (phyId: 1f) Link DOWN.
[*06/27/2019 00:07:02.5190] ===> Activate Deep Green Mode
[*06/27/2019 00:07:04.5240] wired0 (Ext switch port: 7) (Logical Port: 15) (phyId: 1f) Link UP at 1000 mbps full

Your AP simply has no IP.

You could add a dhcp server on the vlan the ap's reside or you'll have to console in each ap and give them an ip manually. Capwap ap ip x.x.x.x 255.x.x.x x.x.x.x

 

First being ip then mask and then gateway. If the controller is on the same vlan then you wont need to point the aps towards the controller.


 

Configuring a static IP address on the AP via Console port worked for me:

capwap ap ip 10.0.0.2 255.255.255.0 10.0.0.1 208.67.222.222

After a reload of the AP, it happily joined its controller:

reload 

 

Thank you, this worked for me as well. I'm wondering why one out of 10 APs did not get an IP Address from DHCP

You need to troubleshoot that issue separately. You can look at the dhcp logs on the dhcp server, console into the ap or do a wired bar capture to see what was sent or received.
-Scott
*** Please rate helpful posts ***

1. Fix this first - Do not use 8.9 code. Upgrade 3504 to any/latest 8.10. code. (Cisco doesn't support 8.9 code period.)
2. what's the AP running code - AP#show version. (Brand new AP9120 generally have 8.10.X.X code on it)
3. what's the AP's power-source OR use appropriate suggested power source for 9120.
4. Have only MIC checked on WLC.
5. share the AP connected switch port config. And does this vlan have access to DHCP server -Swap with wired client to confirm.
6. Did the physical/wired0 interface come up- show int wired, show control wired -Are AP connected to 3504 directly or POE switch.
7. share the AP connected switch port config.
8. AP#debug dhcp errors/events/packets
9. obtain full AP boot-up logs to get hints.
10. Check the Eth cable

(Done many deployments/migrations with 9120 and AireoOS 8.10 - Generally, it works very smooth.)

Leo Laohoo
Hall of Fame
Hall of Fame

@RGilbert wrote:

Waiting for preferred uplink IP configuration


This error message means the AP is "waiting" (and waiting) for a response from the DHCP server. 

Is DHCP Option 43 configured correctly?

It looks like no dhcp at all never mind option 43 Leo :)
I'm with Joey - check dhcp server configuration or configure static IP.

ammahend
VIP
VIP

AP Policies - I checked first 3 boxes for certs SSC MIC and LSC

 

I know you have lot of good information below, but I am just curious are you using your own CA signed certs or self signed cert on AP, if now why you have SSC and LSC checked ? If Yes then why do you have MIC checked ?

-hope this helps-

Andrés Mora
Level 1
Level 1

Hello,

Im having the same issue with my Catalyst 9115AX. 

 

We have the WLC Cat 9800-40 with the software version 16.12.

 

We have configure the AP with static IP.  The AP is able to have connectivity with the same network and others but in certain momment this log appear :  

 

[*10/28/2019 18:14:48.5730] wired0 (Ext switch port: 7) (Logical Port: 15) (phyId: 1e) Link DOWN.
[*10/28/2019 18:14:48.5730] ===> Activate Deep Green Mode

and then, it lose connectivity even with the Gateway.

 

This makes the Controller to Disjoin the AP.

 

Does anyone know what could happen?

use this config

WLC#wireless ewc-ap ap shell username Cisco
Cisco@192.168.129.1's password: Cisco

AP6C71.0DF2.5B94>en
Password: Cisco

then manually set AP ip

capwap ap ip 10.0.0.2 255.255.255.0 10.0.0.1 208.67.222.222

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card