- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2025 07:53 AM - edited 06-16-2025 07:58 AM
Hello Professionals,
I'm wondering my curiosity can be resolved from Wireless topic or Switch topic.
For the beginning, I would like to share that I'm having WLC9800-L-K9 with 17.13 version and C9300L switch(17.06) as a DHCP server.
- Client PC connects to WiFi (SSID-A): Success, getting IP address from Core switch. (10.100.100.30/24)
- I manually provide IP address to Client PC which is in SSID-A's IP subnet(10.100.100.31/24) : Seems wifi connected, but can't talk with my IP address. (Can't ping to gateway, can't reach to internet/server) - IP address is not duplicated with other devices
Static binding from Core switch is working, but manual IP binding to client PC can't.
Is this happened due to WLC's configure or Core switch config?
I believe Clients should have all IP address from centrally, not by themselves so this result is good to me in management terms but still want to know why.
Thank you for giving your precious time.
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2025 09:51 AM
well I would expect endpoint to get an ip from dhcp server while ip-mac binding is enabled. I would suggest you to have a look into the config of 9800 and if possible share 'show tech wireless' from WLC, so that we can have a look too. Here are couple of docs you can refer for passive client and IP-MAC binding -
https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-12/config-guide/b_wl_17_12_cg/m_passive_client.html
https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-12/config-guide/b_wl_17_12_cg/m_ip-mac-binding.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2025 08:01 AM
Try disable option
Dhcp assignments in wlan advance.
If this op. Is enable wlc not allow client to finish auth.
MHM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2025 08:18 AM
If you are giving static IP address to the PC, you need to enable Passive Client inside the Policy Profile and try to test by disabling IP-MAC binding.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2025 09:25 AM
Hello @Saikat Nandy
I appreciate your response.
SSID-A has enabled 'IP-MAC binding' unlike other SSIDs I made.
When I disable this feature, I was able to manually provide IP address.
However, I remember enabling IP-MAC binding caused issue to get IP address from DHCP server. I couldn't get IP address from the DHCP server until I disable this feature.
Could you teach me on how this feature works? I would like to keep this enabled, but still worried that client can't get IP address correctly like before.
Thank you very much.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2025 09:51 AM
well I would expect endpoint to get an ip from dhcp server while ip-mac binding is enabled. I would suggest you to have a look into the config of 9800 and if possible share 'show tech wireless' from WLC, so that we can have a look too. Here are couple of docs you can refer for passive client and IP-MAC binding -
https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-12/config-guide/b_wl_17_12_cg/m_passive_client.html
https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-12/config-guide/b_wl_17_12_cg/m_ip-mac-binding.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2025 11:08 AM
Thank you for sharing documents. I will check and test followed instructions.
Have a wonderful day!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2025 03:14 PM
> WLC9800-L-K9 with 17.13 version
You should not be using 17.13 because it's a limited support, feature only, release which will never get any bug fixes!
Refer to the TAC Recommended link below - you should either be using 17.12 or 17.15 - which are the recommended Extended Support releases with regular bug fix maintenance releases for up to 2 years.
Please click Helpful if this post helped you and Select as Solution (drop down menu at top right of this reply) if this answered your query.
------------------------------
TAC recommended codes for AireOS WLC's and TAC recommended codes for 9800 WLC's
Best Practices for AireOS WLC's, Best Practices for 9800 WLC's and Cisco Wireless compatibility matrix
Check your 9800 WLC config with Wireless Config Analyzer using "show tech wireless" output or "config paging disable" then "show run-config" output on AireOS and use Wireless Debug Analyzer to analyze your WLC client debugs
Field Notice: FN63942 APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
Field Notice: FN72424 Later Versions of WiFi 6 APs Fail to Join WLC - Software Upgrade Required
Field Notice: FN72524 IOS APs stuck in downloading state after 4 Dec 2022 due to Certificate Expired
- Fixed in 8.10.196.0, latest 9800 releases, 8.5.182.12 (8.5.182.13 for 3504) and 8.5.182.109 (IRCM, 8.5.182.111 for 3504)
Field Notice: FN70479 AP Fails to Join or Joins with 1 Radio due to Country Mismatch, RMA needed
How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points (CSCvx32806)
Field Notice: FN74035 - Wave2 APs DFS May Not Detect Radar After Channel Availability Check Time
Leo's list of bugs affecting 2800/3800/4800/1560 APs
Default AP console baud rate from 17.12.x is 115200 - introduced by CSCwe88390
