WLC Management in a VLAN and another VLAN in One Interface. It will probably work a bit easier for that way. You need the switch to be set as a trunk and just set your VLAN 10 as being your native VLAN. Then you can created additional interfaces on the controller and be able to assign those to additional SSIDs. For this lab, I imported the vWLC into my ESXi environment. Before starting the virtual machine, I configured the NICs as trunk ports. This is optional but if you want ISE and the WLC to dynamically change VLANs based on a user getting authorized, it would need to be trunked back to the rest of the network so the WLC has access to those VLANs.
Posted byCompTIA A+
3 years agoHere is the topology.
- SW1 connected to SW2 via a trunk.
- WLC connected to SW1 via a trunk.
- WLC management interface vlan 10 (192.168.10.0/24)
- WLC service interface vlan 200 (192.168.200.0/24)
- switchport to WLC management port = trunk
- switchport to WLC service port = access
- AP 1 = access port vlan 10 SW1 (192.168.10.0/24)
- AP 2 = access port vlan 70 SW2 (192.168.70.0/24)
- SW1 = DHCP server for all vlans
- WLC set up with dynamic interface on vlan 70 (192.168.70.0/24)
- Two WLANs = 1 for vlan 10, one for vlan 70 with different SSID
When my device connects to AP2 on either WLAN, it gets an IP address in the vlan 70 scope, even though when connecting to my management VLAN WLAN, it should have an address in that range.
- If I connect to management VLAN or guest vlan, I get an address in the 192.168.70.0/24 range when connecting to AP2.
- When I roam to AP1, I get an address in the proper subnet depending on which WLAN I am connected to.
The process as I understand it.
The client sends a packet to the ap. AP wraps it in capwap, sends it to the WLC. The WLC dumps it off on the vlan associated with the WLAN. At least this is the unicast process.
What happens with a broadcast / DHCP ?
13 comments