Configuring The Management, Ap-Manager, Virtual, And Service-Port Interfaces - Cisco 2100 Series Configuration Manual

Configuring the Management, AP-Manager, Virtual, and Service-Port Interfaces

A zero value for the VLAN identifier (on the Controller > Interfaces page) means that the interface is
Note
untagged.
The default (untagged) native VLAN on Cisco switches is VLAN 1. When controller interfaces are
configured as tagged (meaning that the VLAN identifier is set to a non-zero value), the VLAN must be
allowed on the 802.1Q trunk configuration on the neighbor switch and not be the native untagged VLAN.
Cisco recommends that tagged VLANs be used on the controller. You should also allow only relevant
VLANs on the neighbor switch's 802.1Q trunk connections to controller ports. All other VLANs should
be disallowed or pruned in the switch port trunk configuration. This practice is extremely important for
optimal performance of the controller.
Cisco recommends that you assign one set of VLANs for WLANs and a different set of VLANs for
Note
management interfaces to ensure that controllers properly route VLAN traffic.
Follow the instructions on the pages indicated to configure your controller's interfaces and ports:
•
•
•
•
•
Configuring the Management, AP-Manager, Virtual, and
Service-Port Interfaces
Typically, you define the management, AP-manager, virtual, and service-port interface parameters using
the Startup Wizard. However, you can display and configure interface parameters through either the GUI
or CLI after the controller is running.
When assigning a WLAN to a DHCP server, both should be on the same subnet. Otherwise, you need to
Note
use a router to route traffic between the WLAN and the DHCP server.
Cisco Wireless LAN Controller Configuration Guide
3-10
Configuring the Management, AP-Manager, Virtual, and Service-Port Interfaces, page 3-10
Configuring Dynamic Interfaces, page 3-16
Configuring Ports, page 3-19
Enabling Link Aggregation, page 3-29
Configuring a 4400 Series Controller to Support More Than 48 Access Points, page 3-34
Chapter 3 Configuring Ports and Interfaces
OL-17037-01