(QoS) for mobility services such as voice and video, and OEAP support for the teleworker solution. Cisco 2500 Series Wireless Controller support a maximum of 50 lightweight APs in increments of 5 APs with a minimum of 5 APs, making it a cost−effective solution for retail and small and medium−sized businesses.
The Cisco 2500 Series Wireless Controller physically has the same form factor as the Cisco 2106 controller. The CPU on a Cisco 2500 Series Wireless Controller is a multi−core CPU and can handle both data plane and wireless data traffic. The CPU can handle control plane application, which handles all the management traffic...
The Cisco 2500 Series Wireless Controller has 1 GB system memory. Two types of memory devices are supported in order to store software images. The boot flash contains the boot code, and the compact flash contains the application code that can store multiple images. The front panel houses four Gigabit Ethernet ports.
In the case of the Cisco 2500 Series Wireless Controller, a single dynamic AP manager can support any number of APs. However, as a best practice, it is suggested to have 4 separate dynamic AP manager interfaces and associate them to the 4 Gigabit interfaces.
Configure the Neighbor Switch By default, all four ports on the Cisco 2500 Series Wireless Controller are 802.1Q trunk ports. The controller is always connected to a Gigabit Ethernet port on the neighboring switch. The neighbor switch port is configured as an 802.1Q trunk and only the appropriate VLANs are allowed on the trunk. All other VLANs are pruned.
APs will not be able to join the controller. It is recommended to install appropriate licenses on the Cisco 2500 Series Wireless Controller in order to work with the controller going forward. The Cisco 2500 Series Wireless Controller is shipped with an evaluation license for a period of 60 days (that is, 8 weeks 4 days).
License Priority: None (Cisco Controller) > Enable DTLS in the Cisco 2500 Series Controller In order to enable DTLS on an AP or particularly on a group of APs, make sure that you have Data Encryption License installed in the controller. DTLS (Data Encryption) can be enabled on a per AP basis from the Advanced tab once you select the AP details.
WCS uses SNMP to manage wireless controllers, access points, client devices. The Cisco 2500 Series Wireless Controller devices need to have SNMP configured correctly. Cisco 2500 Series Wireless Controller can be managed with WCS version 18.104.22.168 and later.
The controller is added successfully, and the Cisco 2500 Series Wireless Controller is ready to be provisioned by the WCS. In order to verify the Cisco 2500 Series Wireless Controller after it is added in WCS, go to Monitor > Controllers to see the controller details.
Cisco 2500 Series Wireless Controller also support multiple AP−managers (for AP Load Balancing) where multiple AP−managers can be configured in addition to an AP−manager which is bounded with a management interface.
Note: Internal DHCP server will only work (for wireless clients) with DHCP proxy enabled. Some of the scenarios supported by the Cisco 2500 Series Wireless Controller are described here with sample configurations.
Switch# The management interface configuration on the Cisco 2500 Series Wireless Controller is straight forward, and has dynamic AP management enabled. Two WLANs are configured. WLAN1 and WLAN2 are mapped to the management interface and are servicing clients.
DNS Domain........ DNS........0.0.0.0 0.0.0.0 0.0.0.0 Netbios Name Servers...... 0.0.0.0 0.0.0.0 0.0.0.0 <CISCO2504> > This is the DHCP configuration capture using the GUI from the Cisco 2500 Series Wireless Controller: The DHCP Proxy is enabled on all Cisco controllers by default.
In the all of the above configuration, VLAN10 is not tagged on the switch. All traffic from the switch is sourced to Port 1 on the controller. APs and client traffic is forwarded to the controller untagged. APs are connected to the Catalyst switch with these switchport configurations. The switchport can either be trunked or configured to be an access port.
External DHCP Server with DHCP Proxy Disabled This is a general setup that has been in practice for all Cisco controllers for some deployments. The configurations are almost the same as noted in the previous, but will have the DHCP Proxy disabled.
10.10.11.1 External DHCP Server with DHCP Proxy Enabled This is a general setup that is one of the best practices for all Cisco controllers. The configurations are almost the same as noted in the previous with DHCP Proxy enabled.
One more DHCP scope is configured on the controller. This configured DHCP Scope TestVlan11 is mapped to the dynamic−interface configured on the controller. <CISCO2504> >show dhcp summary Scope Name Enabled Address Range TestVlan10 10.10.10.100 −> 10.10.10.200 TestVlan11 10.10.11.100 −> 10.10.11.200 <CISCO2504>...
One of the configured WLANs is mapped to the management interface and the second WLAN is mapped to the configured dynamic interface dynamic11. The primary DHCP server is a necessity for configuration in this scenario, but should be pointed to the management interface. External DHCP Server with DHCP Proxy Disabled...
Clients will successfully get IP addresses from the configured external DHCP server. Verify the status of the internal DHCP server and make sure that the internal DHCP server is disabled. External DHCP Server with DHCP Proxy Enabled Clients will successfully get IP addresses from the configured external DHCP server. Scenario 3 The management interface with AP−manager enabled is mapped to port 1.
In this scenario the management and dynamic interfaces are configured on Port 1 with either the internal DHCP server or the external DHCP server. Ports 1 and 2 are connected to 2 different switches. This provides redundancy to the Layer 2 and Layer 3 switch network as shown in this topology and interface captures.
Guidelines for Deploying the Cisco 2500 Wireless Controller Ethernet ports on Cisco 2500 Series Wireless Controllers do not work as Switch ports (that is, 2 machines directly connected to these ports will not be able to communicate with each other). You should not connect servers like DHCP, TFTP etc.