In your scenario - the requirements are - dhcp server ip will be WLC's management interface ip on management vlan, scope is going to be the local site's vlan-x range, the default gateway/router going to be the site's vlan-x gateway.
The challenges are:
#Guess you're having dhcp proxy enabled on WLC to use wlc's internal dhcp
#For wireless client to get an dhcp ip from WLC you need to configure vlan-x dynamic interface ip on WLC as well. This will make the hreap look central.
#From the Remote site, are you routing back to data centre to reach WLC's management interface ip from its site wired interface vlan-x gateway.
#Does WLC know how to reach vlan-x gateway which is actually at the remote site.
#WLC can't decide vlan/interface for remote hreap wireless client, that's why AAA over-ride is not supported with hreap.
Do not use WLC's internal dhcp server for Remote hreap wireless clients. It may be treated as wired client and WLC doesn't respond to the dhcp request.
#WLC Management interface can be reached over wireless and wired side. Any dhcp request that comes on wired side to management interface will be ignored, unless it is AP. All dhcp request that comes via capwap (centrally switched WLAN) will be honored by WLC.
Solution: Use external dhcp server just like Pat said or Use central switching.
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
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 ...
I have created a Powershell script to automatically add a Wireless Guest User on Cisco WLCs. (tested on 2500 Series)
The script should be completely self explanatory.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...