03-17-2021 11:59 AM - edited 07-05-2021 01:24 PM
Hi We have WLC 5520 and several APs joined. The SSID is ABC associated with interface DEF of its controller. It can work well. Now we created second SSID ABC2, also associated with the interface DEF. and all other configuration is same as ABC. The issue is the user cannot get ip address after users connect to ABC2. Any solutions? Thank you
03-17-2021 12:28 PM
Do you have any AP Group configurations? if so pls check which interface map for hyour 2nd SSID under AP group configs.
Also cross-check "show wlan <wlan_id>" output for both of these SSID
HTH
Rasika
03-17-2021 12:37 PM - edited 03-17-2021 12:59 PM
Thank you Rasika for your fast reply. Yes we have ap group and already added the second ssid to the group and has the same associated interface with the first SSID., but still cannot see ip add
show wlan wlan_id command cannot work,
03-17-2021 01:18 PM
"show wlan summary" should give you the WLAN_ID numbers correspond to those 2 SSID. Then replace <wlan_id> with those numbers and get the output
HTH
Rasika
03-18-2021 06:55 PM - edited 03-19-2021 08:39 PM
by comparing two outputs, there are some differences. Its helpful to this issue
03-19-2021 06:38 AM
You said "all other configuration is same as ABC" but that compare shows it is definitely NOT the same.
You need to check *all* config parameters on *all* tabs and sub-tabs of the WLANs to make sure they are the same.
03-19-2021 07:52 AM - edited 03-19-2021 07:53 AM
As you already identified there are configuration mismatches. My guest is WLAN_ID 8 is the one not working.
If this is FlexConnect local switch deployment, then I would correct that first on that SSID and the below 2 settings should fix it.
1. Enable FlexConnect Local Switching
2. Enable DHCP Address Assignment Required
HTH
Rasika
*** Pls rate all useful responses ***
03-19-2021 12:51 PM - edited 03-19-2021 12:52 PM
i know the idea is make it exactly same. I just checked wlan to make sure all configuration is same between two except AAA, but it still cannot work. and also tried to associated with another interface/another ssid, it still cannot work. strange
03-19-2021 08:13 PM
have you did a debug on your WLC? just try with one device to connect and debug with its mac.
03-19-2021 08:45 PM - edited 03-19-2021 08:47 PM
Yes, Thank you Seckerfers.
debug ip dhcp server ... on the dhcp server(located at switch)
Please see the below. It looks like dhcp option issue. but the question is why the first ssid can work? actually the speed is very slow
*Mar 19 22:47:23.288: Option 82 not present
*Mar 19 22:47:23.288: DHCPD: Reload workspace interface Vlan40 tableid 0.
*Mar 19 22:47:23.288: DHCPD: tableid for 10.1.218.1 on Vlan40 is 0
*Mar 19 22:47:23.288: DHCPD: client's VPN is .
*Mar 19 22:47:23.288: DHCPD: No option 125
*Mar 19 22:47:23.288: DHCPD: DHCPREQUEST received from client 0140.665c.7116.9e.
*Mar 19 22:47:23.288: DHCPD: DHCPREQUEST received on interface Vlan40.
*Mar 19 22:47:23.288: DHCPD: FSM state change INVALID
*Mar 19 22:47:23.288: DHCPD: Workspace state changed from INIT to INVALID
*Mar 19 22:47:23.288: DHCPD: Client either rebooted or rebinding we are seeing the client for first time
*Mar 19 22:47:23.288: DHCPD: excluded address: 10.1.218.126
*Mar 19 22:47:23.288: DHCPD: Finding a relay for client 0140.665c.7116.9e on interface Vlan40.
*Mar 19 22:47:23.288: DHCPD : Locating relay for Subnet 10.1.218.1
*Mar 19 22:47:23.289: DHCPD: Looking up binding using address 10.1.218.1
*Mar 19 22:47:23.289: DHCPD: setting giaddr to 10.1.218.1.
*Mar 19 22:47:23.289: DHCPD: BOOTREQUEST from 0140.665c.7116.9e forwarded to 10.1.218.6.
*Mar 19 22:47:23.289: DHCPD: BOOTREQUEST from 0140.665c.7116.9e forwarded to 10.1.218.5.
*Mar 19 22:47:23.290: Option 82 not present
*Mar 19 22:47:23.290: DHCPD: Reload workspace interface Vlan40 tableid 0.
*Mar 19 22:47:23.290: DHCPD: tableid for 10.1.218.1 on Vlan40 is 0
*Mar 19 22:47:23.290: DHCPD: client's VPN is .
*Mar 19 22:47:23.291: DHCPD: No option 125
*Mar 19 22:47:23.291: DHCPD: forwarding BOOTREPLY to client 408d.6671.169e.
*Mar 19 22:47:23.291: DHCPD: Forwarding reply on numbered intf
*Mar 19 22:47:23.291: DHCPD: Option 125 not present in the msg.
*Mar 19 22:47:23.291: DHCPD: Clearing unwanted ARP entries for multiple helpers
*Mar 19 22:47:23.291: DHCPD: src nbma addr as zero
*Mar 19 22:47:23.291: DHCPD: ARP entry exists (10.1.218.126, 408d.6611.169e).
*Mar 19 22:47:23.291: DHCPD: egress Interfce Vlan40
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide