For WLC ports and interfaces refer to different concepts. Controller ports are physical connections made to an external switched network, whereas interfaces are logical connections made internally within the controller.
- Service port – OOBM, system recovery, initial boot. Connects using Access port only.
- Distribution system port – For AP and management traffic, Client data. Usually a 802.1Q trunk port. For resiliency, configure as LAG port (etherchannel)
- Console port – OOBM, system recovery, initial boot
- Redundancy port — connect to peer controller for redundancy.
- Management interface – For management traffic
- AP-manager interface (Optional) – Used to terminate CAPWAP tunnels between the controller and its APs. Should be on same vlan as the management but it can be created separately if we want to seperate the management and CAPWAP traffic.
- Virtual interface – Used to relay client DHCP requests, client web authentication,
and to support client mobility (all WLCs in same mobility group should have the same IP)
- Service port interface – Connects to the SP port for OOBM
- Dynamic interface – connects WLAN to VLAN
Initial setup via WEB and CLI
- Configure system access.
- Configure SNMP access. v3 is recommended
- Configure the service port.
- Enable or disable LAG
- Configure the management interface.
- Configure the RF mobility domain and country code. Default is US.
- Configure the virtual interface. Should add this to the DNS because it is used for client web authentication
- Configure a WLAN. The WLAN ID is an internal index used when configuration templates are applied to a controller from an Cisco Prime Network Control System (NCS) or Cisco Prime Infrastructure (PI) management station.
- Configure a RADIUS server for client authentication
- Configure 802.11 support.
- Configure the system clock.
- Save and Reboot.