cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
265
Views
0
Helpful
1
Replies

350 AP & WPA - Cisco clients can't get DHCP address

psmith
Level 1
Level 1

I've configured FSR w/WLSM as the WDS device and LEAP authentication against an ACS server:

ssid <SSIDName>

vlan 300

authentication network-eap eap_methods

authentication key-management wpa cckm

mobility network-id 300

With the 1200-series AP's everything is working fine - clients authenticate, get a DHCP address, they're roaming with FSR, etc. But clients trying to connect to an identically configured 350-series AP authenticate but can't get a DHCP address.

When the 350's are configured for LEAP authentication without key management, everything works fine:

ssid <SSIDName>

vlan 2

authentication open

authentication network-eap eap_methods

Although the 350's are running 12.3(2)JA, I don't think this is related to the DHCP bug (CSCsa44872) as non-WPA clients do get DHCP addresses. I've also tried installing 12.3(2)JA2, 12.3(4)JA and 12.2(15)XR2, but the results are the same - WPA clients can't get an address with any of them.

Anyone run into anything similar? Is there something documented with WPA and the 350-series that I've overlooked?

Thanks,

Paul

1 Reply 1
Review Cisco Networking for a $25 gift card