Cisco 4402 - Wireless LAN Controller Using Manual page 15

Note: As mentioned above, the AP Manager Interface must not be configured in the 5500
controller. Here the Management Interface acts as an AP Manager Interface.
The following is an explanation of the individual configuration parameters:
System Name: Choose a suitable name using your own name convention, for example "uninett-4402-
50-wlc".
Enter Administrative User Name: e.g. "admin"
Enter Administrative Password: use something appropriate
Service Interface IP Address Configuration [none][DHCP]: none
The "service interface" is an "out-of-band" address which can be used to manage the control by way of
IP. This is all it is used for and often it is not used at all. Since a gateway cannot be specified for this
address, it cannot be routed out of the subnet (out-of-band address). It is a good backup address in
case the Management address cannot be reached. It is also useful during the initial configuration after
the CLI configuration has been completed. One can connect this port to the administration network or
provide an RFC1918 address and connect directly to the port using a PC.
If "none" is selected, the address is set to 10.0.0.1/255.255.255.0. It may be changed later via the web
interface.
Enable Link Aggregation (LAG) [yes][NO]: No
In the case of small installations, there is no need to use more than one SFP port. In that case, enter
"no". For larger installations you should bundle several SFP ports using link aggregation. In that case,
enter "yes".
Management Interface IP Address:
This is the address which will later be used to administer the controller via HTTP, HTTPS, Telnet, SSH
and/or SNMP. WCS uses SNMP to communicate with the controller at this address. The address will
also be used by the access points to discover their controller. The address should therefore be
registered in the DNS as "CISCO-CAPWAP-CONTROLLER.yourdomain.no" and "CISCO-LWAPP-
CONTROLLER.yourdomain.no".
15