There are several VLAN interfaces defined. Each acts as a DHCP relay for wireless clients associated to WLANs mapped to the interface.
Everything works fine. Wireless clients able to associate to the APs, obtain IP addresses from the enterprise DHCP server, and get connected to the routed network. When I do "ipconfig /all" on the client, I notice the DHCP server is the IP address of the WLC virtual interface, which I set to 1.x.x.1. I understand this is normal behavior because the virtual interface acts as the DHCP server placeholder for wireless clients that obtain their IP address from a DHCP server.
However, it poses problem in my environment where client needs to connect back to the DHCP server to download some Novell options. This causes Novell services to fail on the clients.
Is there any workaround? I tried to remove the DHCP relay from the VLAN interfaces. Instead, I configured "ip helper-address" on the upstream router to do the relay. It doesn't work.
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...