We are trying to connect 1142n lightweight APs with the 2504 WLC. We have successfully joined the APs to the WLC by configuring the switchports hostings the APs to be in access mode in the same VLAN as the management interface of the WLC. However, we would like the wireless clients to be assigned to different VLANs based on which SSID they connect to. We have configured a dynamic interface to support the first SSID/VLAN and assigned it the appropriate VLAN id. Clients are able to associate to the AP however they do not receive an address from DHCP. We want the clients to receive addresses from external DHCP servers, which are also providing wired clients addresses within the same network/vlan.
We attempted to configure the APs with the static address of the WLC (10.10.50.5) and statically set the APs address inside the VLAN (172.22.134.101). Routing is functional between the 172.22.134.x network and the WLC, and the APs were able to reconnect to the WLC in this configuration. Unfortunately, clients are no longer able to associate to the APs. So we have returned to the configuration above, but still are unable to address the clients using DHCP.
In answer to your suggestions: Pings between the WLC and the DHCP server are successful.
Primary external DHCP server has been configured on the WLAN.
We have toggled between DHCP proxy and back without success on either setting.
We are able to receive DHCP addresses by creating an internal scope. The addresses we are distributing from the internal scope are on the same network (VLAN 1, 172.22.134.0/24) which we want the external DHCP server to be providing them from. Unfortunately, pings to the DHCP server from the wireless clients still do not work even though they are addressed in the same network as the DHCP server. Therefore, we think that the controller is not assigning the clients to the correct VLAN to allow these pings to succeed.
Thanks for your help, Saravanan. The issue we were having was related to the trunking native VLAN. We wanted to address our clients in VLAN1. After changing the native VLAN on the trunks, the issue has been resolved.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...