Cisco Wireless Controller Online Help, Release 8.5

Buttons

• New : Adds a new interface.

Interfaces > New

Choose CONTROLLER > Interfaces and then New to navigate to this page.

Add a new Cisco WLC operator-defined interface by entering the following parameters:

• Interface Name—Enter the name of the new operator-defined interface without any spaces. The interface name can be up to 32 characters and can include special characters.
• VLAN Id—Enter the VLAN identifier for this new interface, or enter 0 for an untagged VLAN.

Note IPv6 is not supported on Dynamic Interface.

Buttons

• Back: Returns to the previous page.
• Apply: Displays the Interfaces > Edit page and continues configuring the new operator-defined interface.

Interfaces > Edit

Choose CONTROLLER > Interfaces and then click on an interface name to navigate to this page.

The top of this page displays the operator-defined Interface Name, and may include the interface MAC address.

Edit Management, VLAN, Operator-Defined, Service Port, Virtual, and AP-Manager interfaces as described in the following tables.

Management Interface Parameters

Note If you made any changes to the management interface, reboot the controller so that your changes take effect.

Note The IPv4 and IPv6 configurations cannot be changed in redundancy mode.

Table 4-5 Management Interface Parameters

Parameter	Description
General Information
Interface Name	Name of the interface.
MAC Address	MAC address of the interface.
Configuration
Quarantine	Quarantine status. Check the check box to indicate that this VLAN is a quarantine VLAN. When a client is assigned to a quarantine VLAN, its data switching is always central.
Quarantine VLAN ID	Quarantine VLAN ID. Enter a nonzero value for the quarantine VLAN ID. Note We recommend that you configure unique quarantine VLANs throughout your network. If multiple controllers are configured in the same mobility group and access interfaces on all controllers are in the same subnet, you must have the same quarantine VLAN if there is only one NAC appliance in the network. If multiple controllers are configured in the same mobility group and access interfaces on all controllers are in different subnets, you must have different quarantine VLANs if there is only one NAC appliance in the network.
NAS-ID	ID that is sent to the RADIUS server by the controller through an authentication request to classify users to different groups so that the RADIUS server can send a customized authentication response.
NAT Address Note This option is available only for Cisco WLCs that are configured for dynamic AP management.
Enable NAT Address	NAT addresses that you can enable. Check the check box to deploy the Cisco WLC behind a router or other gateway device that is using a one-to-one mapping network address translation (NAT). NAT allows a device, such as a router, to act as an agent between the Internet (public) and a local network (private). In this case, it maps the controller’s Intranet IP addresses to a corresponding external address. The controller’s dynamic AP-manager interface must be configured with the external NAT IP address so that the controller can send the correct IP address in the Discovery Response.
NAT IP Address	External NAT IP address.
Interface Address
VLAN Identifier	Virtual LAN assigned to the interface. Enter 0 for an untagged VLAN or a nonzero value for a tagged VLAN. We recommend using tagged VLANs for the management interface. Note For Cisco 5500 Series Controllers in a nonlink-aggregation (non-LAG) configuration, the management interface must be on a different VLAN than any dynamic AP-manager interface. Otherwise, the management interface cannot fail over to the port that the AP-manager is on.
IP Address	IPv4 address of the interface.
Netmask	Interface subnet mask (IPv4).
Gateway	Interface gateway router IP address.
IPv6 Address	IPv6 address of the interface.
Prefix Length	Interface subnet mask (IPv6).
IPv6 Gateway	Link local address of the interface gateway router. Note An error is thrown when the IPv6 gateway is not a link local IPv6 address.
Link Local IPv6 Address	IPv6 unicast address that is configured on the interface. Link local IPv6 address is used for addressing a single link for automatic address configuration or neighbor discovery protocol.
Physical Information
Port Number	Primary port for the interface.
Backup Port	Backup port. If the primary port for an interface fails, the interface moves to the backup port.
Active Port	Active port for the interface.
Enable Dynamic AP Management	AP-manager interface. Note Only one AP-manager interface is allowed per physical port. A dynamic interface that is marked as an AP-manager interface cannot be used as a WLAN interface. Caution Do not define a backup port for an AP-manager interface. Port redundancy is not supported for AP-manager interfaces. If the AP-manager interface fails, all of the access points connected to the controller through that interface are evenly distributed among the other configured AP-manager interfaces.
DHCP Information
Primary DHCP Server	Interface that uses this DHCP server first to obtain an IPv4 address. Note IPv6 is not supported for DHCP.
Secondary DHCP Server	Interface that uses this DHCP server as a backup to obtain an IP address. Note IPv6 is not supported for DHCP.
DHCP Proxy Mode	Drop-down list from which you can choose the DHCP Proxy Mode that can be one of the following: Global—Uses the global DHCP proxy mode on the controller. Enabled—Enables the DHCP proxy mode on the interface. When you enable DHCP proxy on the controller, the controller unicasts the DHCP requests from the client to the configured servers. You must configure at least one DHCP server on either the interface associated with the WLAN or on the WLAN. Disabled—Disables the DHCP proxy mode on the interface. When you disable the DHCP proxy on the controller, the DHCP packets transmitted to and from the clients are bridged by the controller without any modification to the IP portion of the packet. Packets received from the client are removed from the CAPWAP tunnel and transmitted on the upstream VLAN. DHCP packets directed to the client are received on the upstream VLAN, converted to 802.11, and transmitted through a CAPWAP tunnel toward the client. As a result, the internal DHCP server cannot be used when DHCP proxy is disabled. Note The DHCP Proxy mode is disabled by default when the interface uses IPv6 address. DHCP does not support IPv6.
Enable DHCP Option 82	Check box that allows you to enable the DHCP Option 82 on the dynamic interface. DHCP option 82 provides additional security when DHCP is used to allocate network addresses.
Enable DHCP Option 82-Link Select	Option 82-Link Select pads the extra information to get the IP address in the required subnet.
Link Select relay source	Allows to specify the required interface/subnet on which the DHCP client require an IP address.
Enable DHCP Option 82 - VPN Select	Enables the VPN select. This is used in conjunction with the link select relay source.
VPN select - VRF Name	VPN Select-VRF Name is a string that is used to select a DHCP pool based on the VRF name.
VPN select - VPN ID	VPN Select-VPN ID is an ASCII value that is used to select a DHCP pool based on the identifier.
Access Control List
ACL Name	Drop-down list from which you can choose an IPv4 ACL. Note Applying an ACL to the management interface does not affect wired devices. To block access to wired devices, you must configure an ACL on the upstream device port.
IPv6 ACL Name	Drop-down list from which you can choose an IPv6 ACL. Note Guest LAN does not support IPv6 ACL.
URL ACL	Drop-down list from which you can choose the URL ACL profile for the interface. Interface URL ACL profiles have higher priority than WLAN URL ACL profiles.
mDNS
mDNS Profile	Drop-down list from which you can choose the mDNS profile for the interface. Interface mDNS profiles have higher priority than WLAN mDNS profiles. Clients receive service advertisements only for the services associated with the profile.

Redundancy-Management Interface Parameters

Service Port Interface Parameters

Virtual Interface Parameters

Note If you made any changes to the virtual interface, reboot the controller so that your changes take effect.

AP-Manager Interface Parameter

Note For Cisco 5508 WLCs, you do not have to configure an AP-manager interface because the management interface acts like an AP-manager interface by default.

Buttons

• Back: Returns to the previous page.
• Apply: Sends data to the Cisco WLC, but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

Note Applying interface changes may cause WLANs to temporarily drop client connections. You are prompted to confirm the changes if this is the case.

Buttons

Add Group : Adds a new interface group.

Interface Groups > Add Group

Choose CONTROLLER > Interface Groups and then click Add Group to navigate to this page.

Add a new Cisco WLC operator-defined interface group by entering the following parameters:

• Interface Group Name—Enter the name of the new operator-defined interface group. The interface group name can be up to 32 characters and can include special characters.
• Description—Enter the description for this new interface group.

Buttons

• Add: Adds a new interface group.
• Cancel: Disregards any settings or changes.

Interface Groups > Edit

Choose CONTROLLER > Interface Groups and then click on an interface group name to navigate to this page.

Buttons

• Back: Returns to the previous page.
• Apply: Sends data to the controller, but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

Buttons

• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

Network Routes > IPv4 Routes

This page provides a summary of existing IPv4 based service port network routes to network or element management systems on a different subnet. You can choose IP Address , IP Netmask , or Gateway IP Address .

• To remove a network route, hover your cursor over the blue drop-down arrow for the route and choose Remove. You are prompted to confirm the Network Route removal.

Buttons

New: Adds a new IPv4 based network route.

IPv4 Routes > New

Choose CONTROLLER > Network Routes > IPv4 Routes and then click New to navigate to this page.

To add a new network route for the service port.

• Route Type—Select IPv4 as the route type.

Enter the following information in the text boxes:

• IP Address—Destination network IP address range
• IP Netmask—Destination subnet mask
• Gateway IP Address—IP address of the service port gateway router

Buttons

• Back: Returns to the previous page.

Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

Network Routes > IPv6 Routes

Choose CONTROLLER > Network Routes > IPv6 Routes to navigate to this page.

This page provides a summary of existing IPv6 based service port network routes to network or element management systems on a different subnet. You can choose IP Address , IP Netmask , or Gateway IP Address .

• To remove a network route, hover your cursor over the blue drop-down arrow for the route and choose Remove. You are prompted to confirm the Network Route removal.

Buttons

New: Adds a new IPv6 based network route.

IPv6 Routes > New

Choose CONTROLLER > Network Routes > IPv6 Routes and then click New to navigate to this page.

To add a new network route for the service port.

Route Type—Select IPv6 as the route type.

Enter the following information in the text boxes:

• IP Address—Destination network IP address range
• IP Netmask/Prefix Length—The prefix length assigned to the destination IPv6 address.
• Gateway IP Address—IP address of the service port gateway router

Buttons

• Back: Returns to the previous page.

Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

Fabric Configuration > Control Plane

Choose CONTROLLER > Fabric Configuration > Control Plane to navigate to this page.

You can enable fabric and configure parameters on the enterprise and guest controllers, using the Fabric Enable/Disable button at the top of the screen.

Table 4-13 Fabric Control Plane Configuration Details

Fabric Configuration > Interface

Choose CONTROLLER > Fabric Configuration > Interface to navigate to this page.

This page provides a summary of existing fabric networks. You can view the Fabric Interface Name, L2 Instance ID, Network IP address, IP subnet mask, and L3 Instance ID. To remove a fabric interface, hover your cursor over the blue drop-down arrow for the interface and choose Remove. You are prompted to confirm the Fabric Interface removal.

Buttons

New: Adds a new fabric interface.

Table 4-14 Fabric Interface Configuration Details

Buttons

Apply: Commits your changes.

Fabric Configuration > Templates

Choose CONTROLLER > Fabric Configuration > Templates to navigate to this page.

This page provides a summary of existing fabric configuration templates. You can view the Fabric ACL templates and its Status. To remove a fabric template, hover your cursor over the blue drop-down arrow for the interface and choose Remove. You are prompted to confirm the Fabric Template removal.

Buttons

New: Adds a new fabric template.

Copy: Copies parameters from an existing template.

Table 4-15 Fabric Template Copy Details

Buttons

Apply: Commits your changes.

Redundancy > Global Configuration

Choose CONTROLLER > Redundancy > Global Configuration to navigate to this page.

You can enable redundancy and configure redundancy parameters on the primary and secondary controllers.

The controllers reboot to negotiate the HA role based on the configuration. The standby controller downloads the configuration from the active controller and reboots. In the next bootup process, after the role of the controller is determined, the standby controller tries to validate the configuration again to establish itself as the controller in the Standby state.

After the controllers are rebooted and the XML configuration is synchronized, the active controller transitions to the Active state, and the standby controller transitions to the Standby HOT state. From this point, GUI, Telnet, and SSH for the standby controller on the management interface do not work because all the configurations and management have to be done through the active controller. The standby controller can only be managed through the console or the service port. Also, when a controller transitions to the Standby HOT state, the Standby keyword is automatically appended to the prompt of the controller.

To see the redundancy status of the active controller, choose Monitor > Redundancy > Summary to navigate the Redundancy Summary page.

Buttons

• Apply: Commits your changes.
• Save Configuration: Saves the changes

Redundancy > Peer Network Route

Choose CONTROLLER > Redundancy > Peer Network Route to navigate to this page.

This page provides a summary of existing service port network routes of the peer controller to network or element management systems on a different subnet. You can view the IP address, IP netmask, and gateway IP address. To remove a peer network route, hover your cursor over the blue drop-down arrow for the route and choose Remove. You are prompted to confirm the Network Route removal.

Buttons

• New: Adds a new peer network route.

Internal DHCP Server > DHCP Scope

Choose CONTROLLER > Internal DHCP Server > DHCP Scope to navigate to this page.

The controllers have built-in DHCP relay agents. However, when you want network segments that do not have a separate DHCP server, the controllers can have built-in DHCP scopes (Dynamic Host Configuration Protocol servers) that assign IP addresses and subnet masks to wireless clients, direct-connect access points, appliance-mode access points on the management interface, and DHCP requests that are relayed from access points. (Only lightweight access points are supported.)

Typically, one Cisco WLC can have one or more DHCP scopes that each provide a range of IP addresses. This page shows the existing DHCP server scope names.

Each DHCP Scope displays the following entries, which are a subset of those set on the DHCP Scope > Edit page:

• Scope Name
• Address Pool—IP address range. This pool must be unique for each DHCP scope and must not include the static IP addresses of routers and other servers
• Lease Time—Number of seconds that an IP address is granted to a client or access point
• Status—Scope is Enabled or Disabled

Click the scope name to go to the DHCP Scope > Edit page to change the DHCP scope settings.

Remove a DHCP Scope by hovering your cursor over the blue drop-down arrow and choosing Remove . You are prompted to confirm the DHCP Scope removal.

Buttons

• New : Creates a new DHCP Scope.

DHCP Scope > New

Choose CONTROLLER > Internal DHCP Server > DHCP Scope and then click New to navigate to this page.

The controllers have built-in DHCP relay agents. However, if you want network segments that do not have a separate DHCP server, the controllers also have built-in DHCP scopes (servers) that assign IP addresses and subnet masks to wireless clients, direct-connect access points, appliance-mode access points on the management interface, and DHCP requests that are relayed from access points. (Only lightweight access points are supported.)

Typically, one Cisco WLC can have one or more DHCP scopes that each provide a range of IP addresses. This page enables you to add a DHCP server scope name.

Add a new DHCP scope by entering the DHCP scope name and then clicking Apply . The Cisco WLAN Solution saves the DHCP scope name and returns you to the Internal DHCP Server > DHCP Scope page. On the Internal DHCP Server > DHCP Scope page, click the scope name to set the DHCP scope parameters on the DHCP Scope > Edit page.

Buttons

• Back: Returns to the previous page.
• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

DHCP Scope > Edit

Choose CONTROLLER > Internal DHCP Server > DHCP Scope and then click the scope name to navigate to this page.

The controllers have built-in DHCP relay agents. However, when you want network segments that do not have a separate DHCP server, the controllers also have built-in DHCP scopes (servers) that assign IP addresses and subnet masks to wireless clients, direct-connect access points, appliance-mode access points on the management interface, and DHCP requests that are relayed from access points. (Only lightweight access points are supported.)

Typically, one Cisco WLC can have one or more DHCP scopes that each provide a range of IP addresses. This page enables you to edit a DHCP server scope.

This page shows the name of the DHCP Scope you are editing.

Buttons

• Back: Returns to the previous page.
• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

Internal DHCP Server > DHCP Allocated Lease

Choose CONTROLLER > Internal DHCP Server > DHCP Allocated Leases to navigate to this page.

This page displays the MAC address, the IP address, and the remaining lease time for wireless clients.

Mobility Management > Mobility Configuration

Choose CONTROLLER > Mobility Management > Mobility Configuration to navigate to this page.

This page allows you to enable New Mobility and configure its parameters.

Buttons

• Apply : Sends data to the controller but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

Mobility Management > Mobility Groups

Choose CONTROLLER > Mobility Management > Mobility Groups to navigate to this page.

This page lists existing mobility group members by their MAC address and IP address and also indicates whether the mobility group member is local (this Cisco WLC) or remote (any other mobility group member). The first entry is the local Cisco WLC, which cannot be deleted. The following entries are other controllers in the mobility group that can be deleted at any time by choosing Remove . You can also view the hash key of the virtual controller in your domain.

Note You can ping any of the static mobility group members by choosing Ping.

You set the Mobility Group Name that is set on the General page.

Buttons

• New : Adds a new mobility group member.
• Edit All: Displays the Mobility Group Member > Edit All page.

Mobility Group Member > New

Choose CONTROLLER > Mobility Management > Mobility Groups and then click New to navigate to this page.

This page enables you to add mobility group members.

• Member IP Address—Enables you to enter the management interface IP address of the controller to be added. Both, IPv4 and IPv6 are supported.

Note If you are configuring the mobility group in a network where network address translation (NAT) is enabled, enter the IP address sent to the controller from the NAT device rather than the controller’s management interface IP address. Otherwise, mobility will fail among controllers in the mobility group.

Also, client mobility among controllers works only if you enable auto-anchor mobility or symmetric mobility tunneling. Asymmetric tunneling is not supported when mobility controllers are behind a NAT device.

• Public IP Address(IPv4/IPv6)—IP address of the Cisco WLC if there is no NAT.
• Member MAC Address—Enables you to enter the MAC address of the controller to be added. Both, IPv4 and IPv6 are supported.
• Group Name—Enables you to enter the name of the mobility group.

Note The mobility group name is case sensitive.

• Hash—Enables you to configure hash key of the peer mobility controller. This is not supported for IPv6 members.

Note You must configure the hash only if the peer mobility controller is a virtual controller.

Buttons

• Back: Returns to the previous page.
• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

Mobility Group Member > Edit All

Choose CONTROLLER > Mobility Management > Mobility Groups and then click Edit All to navigate to this page.

This page enables you to edit all the existing Mobility Group members’ MAC addresses, IPv4 and IPv6 addresses in a text box and then to cut and paste all the entries from one Cisco WLC to the other controllers in the mobility group.

You can edit existing entries in the box and/or paste new entries into the box. In all cases, leave one space between the MAC address and IP address on each line.

The text box on this page makes it easy to avoid data-entry errors while copying the mobility group members list to all the controllers in the same mobility group. Some guidelines are as follows:

• Notice that the text box starts with the local Cisco WLC MAC address and IPv4/IPv6 address.
• In the text box, add the MAC addresses, IPv4/IPv6 addresses, and the mobility group name for the rest of the controllers in the same geographical location (such as a campus or building) that you want to add to the static mobility group.
• When you have added all the Cisco WLC MAC addresses and IP v4/IPv6 addresses to the static mobility group, you can cut and paste the complete list into the corresponding boxes in the Mobility Group Member > Edit All pages in other mobility group member Web User Interface pages.

Note The mobility Group supports a maximum of 72 mobility peers.

Buttons

• Back: Returns to the previous page.
• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

Mobility Management > Mobility Anchor Configuration

Choose CONTROLLER > Mobility Management > Mobility Anchor Config to navigate to this page. This page enables you to configure the symmetric mobility tunneling for mobile client features.

Guest N+1 Redundancy

The guest N+1 redundancy feature enables the foreign controller to periodically send ping requests to each anchor controller in the mobility group and enables you to configure the number and interval of requests sent to each anchor controller. Once a failed anchor controller is detected, all of the clients anchored to this controller are deauthenticated so that they can quickly become anchored to another controller.

When using the guest N+1 redundancy and mobility failover features with a firewall, ensure that the following ports are open:

• UDP 16666 for tunnel control traffic
• UDP 16667 for encrypted traffic
• IP Protocol 97 for user data traffic
• TCP 161 and 162 for SNMP

To view the current state of the data and control paths of controllers that have already been configured as mobility anchors, use the Mobility Anchors page.

Symmetric Mobility Tunneling

Note When controllers in the mobility list are running different software releases (such as 5.2, 6.0, and 7.0), Layer 2 or Layer 3 client roaming is not supported between them. It is supported only between controllers running the same release.

The controller provides inter-subnet mobility for clients roaming from one access point to another within a wireless LAN. This mobility is asymmetric so that the client traffic to the wired network is routed directly through the foreign controller.

This mechanism breaks when an upstream router has reverse path filtering (RPF) enabled. In this case, the client traffic is dropped at the router because the RPF check ensures that the path back to the source address matches the path from which the packet is coming.

When symmetric mobility tunneling is enabled, all client traffic is sent to the anchor controller and can then successfully pass the RPF check.

You should also enable symmetric mobility tunneling if a firewall installation in the client packet path may drop the packets whose source IP address does not match the subnet on which the packets are received.

Note Although a Cisco 2000 Series Controller cannot be designated as an anchor for a WLAN when using auto-anchor mobility, it can serve as an anchor in symmetric mobility tunneling to process and forward the upstream client data traffic tunneled from the foreign controller.

Mobility Anchor Config Parameters

Buttons

• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

Mobility Management > Mobility Multicast Messaging

Choose CONTROLLER > Mobility Management > Multicast Messaging to navigate to this page.

The controller provides inter-subnet mobility for clients by sending mobility messages to other member controllers. There can be up to 72 members in the list with up to 24 in the same mobility group. The controller sends a Mobile Announce message to members in the mobility list each time a new client associates to it.

You can configure the controller to use multicast to send the Mobile Announce messages. This behavior enables the controller to send only one copy of the message to the network, which designates it to the multicast group that contains all the mobility members. To derive the maximum benefit from multicast messaging, we recommend that it be enabled or disabled on all group members.

• Enable Multicast Messaging—Enables the controller to use multicast to send the Mobile Announce messages. If you leave it unselected, the controller uses unicast mode to send the Mobile Announce messages. The default value is unselected.
• Local Group Multicast IPv4 Address—Enables you to enter the multicast group IPv4 address for the local mobility group. This address is used for multicast mobility messaging.

Note To use multicast messaging, you must configure the IPv4 address for the local mobility group.

• Mobility Group—Lists the names of all the currently configured mobility groups.

Note IPv6 is not supported for mobility multicast.

Buttons

• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

Mobility Multicast Messaging > Edit

Choose CONTROLLER > Mobility Management > Multicast Messaging and then click the name of the local mobility group to navigate to this page.

• Mobility Group—Lists the name of all the mobility group.
• Local Group Multicast IP Address—Enables you to enter the multicast group IP address for the nonlocal mobility group. This address is used for multicast mobility messaging.

Note If you do not configure the multicast IP address for nonlocal groups, the controller uses unicast mode to send mobility messages to those members.

Buttons

• Back: Returns to the previous page.
• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

Mobility Management > Switch Peer Group

Choose CONTROLLER > Mobility Management > Switch Peer Group to navigate to this page.

This page lists all the switch peer groups and their details like bridge domain ID, multicast IP address, and status of the multicast mode. Click the name of the switch peer group to navigate to the Edit page and update the parameters if required.

Mobility Management > Switch Peer Group Member

Choose CONTROLLER > Mobility Management > Switch Peer Member to navigate to this page.

This page lists all the members of the switch peer group along with their group name, IP address, and public IP address.

Buttons

• New: Adds a new member to the switch peer group.

Mobility Management > Mobility Controllers

Choose CONTROLLER > Mobility Management > Mobility Controllers to navigate to this page.

This page lists all the mobility controllers. Mobility Controllers are controllers that provide mobility management services for an inter proximity group.

You can see the total number of mobility controllers and details like IP address, MAC address, client count, and link status.

Buttons

• New: Adds a new member to the switch peer group.

Mobility Management > Mobility Clients

Choose CONTROLLER > Mobility Management > Mobility Clients to navigate to this page.

This page lists the total number of mobility clients and their parameters.

Buttons

• Configure All : Opens the Global Port configuration data page.

Ports > Configure

Choose CONTROLLER > Ports and then click ConfigureAll to navigate to this page.

This page enables you to change the parameters of all front-panel physical ports on the Cisco WLC simultaneously.

Buttons

• Back: Returns to the previous page.
• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

Ports > Configure

Choose CONTROLLER > Ports and then click on a Port No to navigate to this page.

This page enables you to change the parameters of a single physical port on the Cisco WLC.

General Port Configuration

NTP > NTP Servers

Choose CONTROLLER > NTP > Server to navigate to this page. Use this page to set the Network Time Protocol parameters.

Click a server index number to go to the NTP Server > Edit page to change the NTP server IP address.

Remove an NTP server entry by hovering your cursor over the blue drop-down arrow and choosing Remove . You are prompted for confirmation of the NTP server removal.

Ping the NTP server by hovering your cursor over the blue drop-down arrow and choosing Ping .

Buttons

• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.
• New: Adds a new item to a list. To set up a new NTP server, click to open the NTP Server > New page.

NTP Server > New

Choose CONTROLLER > NTP > Server and click New to navigate to this page. This page enables you to add a new NTP server.

Buttons

• Back: Returns to the previous page.
• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

NTP Server > Edit

Choose CONTROLLER > NTP and then click the server index number to navigate to this page. This page enables you to change the NTP server.

Buttons

• Back: Returns to the previous page.
• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

NTP > NTP Keys

Choose CONTROLLER > NTP > Keys to navigate to this page. This page enables you to set the Network Time Protocol keys.

Click a index number to go to the NTP Keys > Edit page to change the NTP key details.

Remove an NTP key entry by hovering your cursor over the blue drop-down arrow and choosing Remove . You are prompted for confirmation of the NTP key removal.

Buttons

New: Adds a new item to a list. To add a new NTP key, click to open the NTP Keys > New page.

NTP Keys > New

Choose CONTROLLER > NTP > Keys and then click New to navigate to this page. This page enables you to associate a new NTP key to a Server index.

Buttons

• Back: Returns to the previous page.
• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

NTP Keys > Edit

Choose CONTROLLER > NTP > Keys and then click the index number to navigate to this page. This page enables you to change the NTP key.

Buttons

• Back: Returns to the previous page.
• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

Controller Configuration

Choose CONTROLLER > CDP > Controller Configuration to navigate to this page. This page enables you to configure the Cisco Discovery Protocol (CDP).

Cisco Discovery Protocol Overview

The Cisco Discovery Protocol (CDP) is a device discovery protocol that runs on all Cisco-manufactured equipment. A device enabled with CDP sends out periodic interface updates to a multicast address in order to make itself known to neighboring devices.

The default value for the frequency of periodic transmissions is 60 seconds, and the default advertised time-to-live value is 180 seconds. The second and latest version of the protocol, CDPv2, introduces new time-length-values (TLVs) and provides a reporting mechanism that allows for more rapid error tracking, reducing down time.

CDPv1 and CDPv2 are supported on the following devices:

• Cisco Flex 7500 and 5500 Series Controllers
• Lightweight access points
• An access point connected directly to a Cisco Flex 7500 and 5500 Series Controller

This support enables network management applications to discover Cisco devices.

The following TLVs are supported by both the controller and the access point:

• Device-ID TLV: 0x0001—The hostname of the controller, the access point, or the CDP neighbor.
• Address TLV: 0x0002—The IP address of the controller, the access point, or the CDP neighbor.
• Port-ID TLV: 0x0003—The name of the interface on which CDP packets are sent out.
• Capabilities TLV: 0x0004—The capabilities of the device. The controller sends out this TLV with a value of Host: 0x10, and the access point sends out this TLV with a value of Transparent Bridge: 0x02.
• Version TLV: 0x0005—The software version of the controller, the access point, or the CDP neighbor.
• Platform TLV: 0x0006—The hardware platform of the controller, the access point, or the CDP neighbor.
• Power Available TLV: 0x001a—The amount of power available to be transmitted by Power Sourcing Equipment to permit a device to negotiate and select an appropriate power setting.

The following TLVs are supported only by the access point:

• Full/Half Duplex TLV: 0x000b—The full- or half-duplex mode of the Ethernet link on which CDP packets are sent out. This TLV is not supported on access points that are connected directly to a Cisco 5500 Series Controller.
• Power Consumption TLV: 0x0010—The maximum amount of power consumed by the access point. This TLV is not supported on access points that are connected directly to a Cisco Flex 7500, 5500, Series Controllers.
• Power Request TLV:0x0019—The amount of power to be transmitted by a powerable device in order to negotiate a suitable power level with the supplier of the network power.

Note Changing the CDP configuration on the controller does not change the CDP configuration on the access points that are connected to the controller. You must enable and disable CDP separately for each access point.

Parameters and Descriptions

For information on displaying CDP neighbor information, see the following topics:

• CDP Neighbors Details
• CDP Neighbors
• CDP AP Neighbors
• CDP Traffic Metrics

Buttons

• Apply : Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

PMIPv6 > General

Choose CONTROLLER > PMIP > General to configure global parameters for PMIPv6.

Note For timer parameters, default values appear in the UI when you reconfigure the domain name.

PMIPv6 > LMA

Choose CONTROLLER > PMIP > LMA to add new and view existing Local Mobility Anchor (LMA) to the controller.

Click New to add a new LMA to the controller.

Buttons

Apply: Adds a new LMA member.

PMIPv6 > Profile

Choose CONTROLLER > PMIPv6 > Profile to navigate to this page. This page lists existing PMIPv6 profiles.

Buttons

• New : Adds a new PMIPv6 profile.

Click a PMIPv6 profile to edit the configurations of the PMIPv6 profile.

PMIPv6 Profile > New

Choose CONTROLLER > PMIPv6 > Profile and then click New to navigate to this page. This page allows you to create a new PMIPv6 profile.

Buttons

• Back: Returns to the previous page.
• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

PMIPv6 Profile > Edit

Choose CONTROLLER > PMIP > Profile and then click on any profile to navigate to this page. This page allows you to add more NAIs and remove any of the existing NAIs.

Button

• Add NAI: Allows you to add more NAIs.

EoGRE

Choose CONTROLLER > Tunneling > EoGRE to navigate to this page.

Profiles

Choose CONTROLLER > Tunneling > Profiles to navigate to this page.

Neighbor Binding Timers

Choose CONTROLLER > IPv6 > Neighbor Binding Timers to navigate to this page. This page enables you to configure the Neighbor Binding timers.

Parameters and Descriptions

Buttons

• Apply : Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

RA Throttle Policy

Choose CONTROLLER > IPv6 > RA Throttle Policy to navigate to this page. This page enables you to configure the RA Throttle Policy.

The purpose of the RA Throttle Policy is to limit the amount of multicast Router Advertisements (RA) circulating on the wireless network.

Parameters and Descriptions

Buttons

• Apply : Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

RA Guard

Choose CONTROLLER > IPv6 > RA Guard to navigate to this page. This page enables you to configure router advertisement (RA) filtering.

RA Guard is a Unified Wireless solution to drop RA from wireless clients. It is configured globally, and by default it is enabled.

Buttons

• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

mDNS > General

Choose CONTROLLER > mDNS > General to navigate to this page. This page enables you to configure the global mDNS parameters and update the Master Services database.

,

To view the details of an mDNS service, hover your cursor over the blue drop-down arrow of a service, and choose Details . The mDNS > Service > Detail page appears, for more information, see mDNS > Service > Detail.

mDNS > Service > Detail

Choose CONTROLLER > mDNS > General , hover your cursor over the blue drop-down arrow for a service, and choose Details to navigate to this page. This page enables you to view the details of each service.

mDNS > Profiles

Choose CONTROLLER > mDNS > Profiles to view the mDNS profiles configured on the controller and create new mDNS profiles.

After creating a new profile, you must map the profile to an interface group, an interface, or a WLAN. Clients receive service advertisements only for the services associated with the profile. The controller gives the highest priority to the profiles associated to interface groups, followed by the interface profiles, and then the WLAN profiles. Each client is mapped to a profile based on the order of priority.

By default, the controller has an mDNS profile, default-mdns-profile. You cannot delete this default profile.

For more information, see the following topics:

• Mapping mDNS Profiles to an Interface Group
• Mapping mDNS Profiles to an Interface
• Mapping mDNS Profiles to a WLAN

Buttons

New: Creates a new mDNS profile.

Mapping mDNS Profiles to an Interface Group

To map a profile to an interface group, follow these steps:

Step 1 Choose CONTROLLER > Interface Groups and click the Interface Group name to navigate to the Interface Groups > Edit page.

Step 2 Choose an mDNS profile from the drop-down list.

Mapping mDNS Profiles to an Interface

To map a profile to an interface, follow these steps:

Step 1 Choose CONTROLLER > Interfaces and then click on an interface name to navigate to the Interfaces > Edit page.

Step 2 Choose an mDNS profile from the drop-down list.

Mapping mDNS Profiles to a WLAN

To map a profile to a WLAN, follow these steps:

Step 1 Choose WLANs and click the Profile name to navigate to the WLANs > Edit page.

Step 2 Select the mDNS check box.

Step 3 Choose an mDNS profile from the drop-down list.

mDNS Profile > Edit

Choose CONTROLLER > mDNS > Profiles and click the profile name to navigate to the mDNS Profile > Edit page. You can view the following details of the profile:

• Profile Name
• Profile ID
• Service Count
• Number of interfaces attached
• Number of interface groups attached
• Interface groups
• Number of WLANs attached
• WLAN IDs
• Number of Guest LANs attached
• Guest LAN IDs
• Number of Local Policies attached
• Local Policy IDs

To add more services to the profile, choose a service from the Service Name drop-down list and click Add . You can choose from a list of services that are configured in the Master service database. To update the Master service database, choose CONTROLLER > mDNS > General .

mDNS > Domain Names

Choose CONTROLLER > mDNS > Domain Names to view the domain names and other details of the service providers.

Each service advertisement contains a record that maps the domain name of the service provider to the IP address. The mapping also contains details such as the client MAC address, the VLAN ID, the TTL, and the IPv4 address.

mDNS Browser

Choose CONTROLLER > mDNS > mDNS Browser to view the total number of services added in the master database.

mDNS Service Groups

Choose CONTROLLER > mDNS > mDNS Policies to view total number of mDNS Service groups.

Creating mDNS Service Group

Step 1 Choose CONTROLLER > mDNS > mDNS Policies and click the Add Group button.

Step 2 Enter a service group name in the mDNS Service Group Name box.

Step 3 Add a description for the service group in the Description box.

Step 4 Click Add to create a new mDNS Service Group.

mDNS Service Group > Edit

Choose CONTROLLER > mDNS > Policies and click the mDNS Service Group Name to navigate to the mDNS Service Groups > Edit page. You can add a MAC Address and a rule to the Service Group.

DHCP

Choose CONTROLLER > Advanced > DHCP to navigate to this page. This page enables you to set the following DHCP parameters:

Buttons

• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.

Master Controller Mode

Choose CONTROLLER > Advanced > Master Controller Mode to navigate to this page.

This page enables the Cisco WLC to be configured as the master Cisco WLC for your access points that are connected in appliance mode. When there is a master Cisco WLC enabled, all newly added access points with no primary, secondary, or tertiary controllers assigned associate with the master Cisco WLC on the same subnet. This feature enables you to verify the access point configuration and assign primary, secondary, and tertiary controllers to the access point using the All AP Details page.

Note The master Cisco WLC is normally used only while adding new access points to the Cisco Wireless LAN Solution (Cisco WLAN Solution). When no more access points are being added to the network, you should disable the master Cisco WLC.

Note Because the master Cisco WLC is normally not used in a deployed network, the master Cisco WLC setting is disabled upon reboot or OS code upgrade.

Buttons

• Apply: Sends data to the Cisco WLC but the data is not preserved across a power cycle; these parameters are stored temporarily in volatile RAM.