15
Step 5
Enter the IP address, netmask, default router IP address, and optional VLAN identifier (a valid
VLAN identifier or 0 for an untagged VLAN) for the management interface.
Note
The VLAN identifier should be set to match the switch interface configuration.
Step 6
Enter the IP address of the default DHCP server that will supply IP addresses to clients, the
controller’s management interface, and optionally the service-port interface.
Note
The
management interface
is the default interface for in-band management of the
controller and connectivity to enterprise services such as AAA servers.
Step 7
Enter the IP address of the controller’s AP-manager interface.
Note
The
AP-manager interface
is used for Layer 3 communications between the controller
and lightweight access points. It must have a unique IP address and is usually
configured on the same VLAN or IP subnet as the management interface, but this is
not a requirement.
Note
If the AP-manager interface is on the same subnet as the management interface, the
AP-manager interface uses the same DHCP server IP address as the management
interface.
Step 8
Enter the IP address of the controller’s virtual interface, which will be used by all controller
Layer 3 security and mobility managers. You should enter a fictitious, unassigned IP address,
such as 1.1.1.1.
Note
The
virtual interface
is used to support mobility management, DHCP relay, and
embedded Layer 3 security such as guest web authentication and VPN termination.
All controllers within a mobility group must be configured with the same virtual
interface IP address.
Step 9
If desired, enter the name of the mobility group/RF group to which you want the controller
to belong.