My network is very simple (just a few subnets with a router on a stick in between) , and initially I wanted to place all the wireless clients in the same subnet as the wired clients.
The only way I could get that to work, was by using BVI and sub-interfaces on the 2811 hosting the NM-WLC. (This 2811 is not the default gateway / router-on-a-stick. I have another router that enables routing between subnets.)
While that works, I have a problem with SNMP replies packets that get sent from the NM-WLC to wired/wireless subnet.
Finally, I have come to the conclusion (perhaps incorrectly, and therefore this post), that the best way to set wireless clients is :-
1. To have them in their own separate subnets.
2. Have a separate subnet for the WLC
So for example:-
Data Net :- 10.1.1.0/24 (wired)
Voice Net :- 10.1.2.0/24 (wired)
Wireless Net :- 10.1.3.0/24 (wifi)
Network for WLC Management and AP :- 10.1.10.0/24 (wlan-controller subnet)
Can anyone who uses a NM-WLC please share their thoughts ?
I have the same hardware setup and I'm having issues as well. I'd like to see what you and others have done.
I can't figure out how to get traffic from outside the router to enter the WLC. I've configured my int service-module wlan-controller 1/0 with an IP, and then configured the controller mgmt interface IP on the same subnet.
If I plug my laptop into the router, I cannot browse to the WLC GUI or even ping it.
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...