Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
5 Deployment Guide
Product Overview 2
Cisco WLC 3504 Key Attributes 2
Platform Components 5
Deploying Cisco WLC 3504 10
Deploying WLC 3504 through Service Port 10
Deploying WLC 3504 through CLI 15
High Availability with Cisco WLC 3504 16
Configuring mGig Port on WLC 3504 17
Configuring LAG between WLC and Switch 18
Product Overview
The explosion of mobile clients in enterprise empowered by bring your own device (BYOD), the deployment of wireless in
mission-critical applications, and the adoption of Wi-Fi in service provider networks enabling new business models require wireless
networks to provide larger AP scale, client scale, and higher throughput.
The Cisco 3504 Wireless Controller is a compact, highly scalable, service-rich, resilient, and industry's first Multigigabit Ethernet
platform that enables next-generation wireless networks for small to medium-sized enterprises and branch office deployments.
Optimized for for 802.11ac Wave 2 performance, Cisco 3504 Wireless Controller provides centralized control, management, and
troubleshooting for small to medium-sized enterprises and branch offices. It offers flexibility to support multiple deployment modes
in the same controller-a centralized mode for campus environments, Cisco FlexConnect® mode for lean branches managed over the
WAN, and a mesh (bridge) mode for deployments in which full Ethernet cabling is unavailable.
As a component of the Cisco Unified Wireless Network, the 3504 controller provides real-time communications between Cisco
Aironet® Access Points, Cisco Prime® Infrastructure, and Cisco Mobility Services Engine, and is interoperable with the Cisco 5520
and 8540 Wireless Controllers.
Figure 1: Cisco 3504 Wireless LAN Controller
2
Table 1: Features and Benefit
Features Benefit
Scale and Performance Optimized to enable 802.11ac Wave 2 next-generation networks,
supporting:
• 4-Gbps throughput
• 150 access points
• 3000 clients
• 1x Multigigabit Ethernet interface (1, 2.5 or 5), + 4x 1
Gigabit Ethernet
• 512 VLANs
• 150 AP Groups
• 100 FlexConnect Groups
• 100 APs per FlexConnect Group
• 512 Interface Groups
• PMK Cache Size of 14000
• Support for 1500 RFIDs tracking
• Detection and containment of up to 600 Rogue APs and 1500
Rogue Clients
• 50 APs per RRM Group
• 180000 AVC Flows
• Database Size is 12000
3
Features Benefit
AP Platform Support • 1260, 3500, 600
• 1600, 2600, 3600
• 1700, 2700, 3700
• 1800, 2800, 3800
• 1815T, OEAP 1810, OEAP 600
• 1815l,1815W, 1810W, 702I, 702W
• 1530, 1540, 1550, 1560, 1570
Ease of Deployment • CLI Setup Wizard, WLAN Express Setup using Service Port,
Auto-Install using Service Port and Data Port 1.
Note Cisco WLC 3504 has software feature parity with Cisco WLC 5520 unless otherwise stated.
4
• Identity Services Engine–Recommended ISE Release 2.2 and later
• Connected Mobility Experiences (CMX)–10.2 and later
Platform Components
Understanding Cisco WLC 3504 Front Panel View
Cisco WLC 3504 supports several interfaces and status LED indicators on the front panel.
Figure 2: WLC 3504 Front Panel Interfaces
5
Interfaces on WLC 3504 Port as noted in figure above Description
GiGE Ports There are four Gigabit Ethernet Ports on
the WLC 3504 for Data Connectivity. Port
3 and Port 4 also have PoE out and can
provide 802.3at power.
Reset 7 Reset button can be used to Reset the WLC
3504 to factory defaults.
Status LED 8 There are three LEDs on the front panel of
WLC3504. There is a System LED, Alarm
LED and High Availability LED. For
description of LED states, please refer to
the section LED Indicators.
Redundancy Port 9 WLC 3504 supports High Availability
similar to WLC 5520 and WLC 8540. The
Redundancy ports can be connected back
to back or via an L2 switch.
6
Figure 3: LED Indicators
7
Temperature Error OFF OFF
8
Figure 4: WLC 3504 Back Panel Interfaces
9
Deploying Cisco WLC 3504
Cisco WLC 3504 supports deploying WLC 3504 using the Service Port as well as CLI. In this guide, both of the methods are
documented below.
10
To deploy WLC 3504 using the Service Port, follow the procedure below:
Procedure
Step 1 Connect a PC laptop's wired Ethernet port directly to Service Port of the WLC 3504.
Step 2 Power up WLC 3504.
Step 3 The Laptop should get an IP address in 192.168.0.x network.
Step 4 Open the browser and browse to http://192.168.0.1 . The Setup Wizard will start.
Step 5 Create the WLC admin account as shown below.
Step 6 Under the Set Up Your Controller section, please enter the following:
• System Name–Enter the System Name
• Country–Select the country
• Date & Time–Select Date & Time manually
• Tiemzone–Select the Timezone
• NTP Server–If you do not want to select the Date & Time manually, you can also enter the IP address of an NTP
server
• Management IP Address–Enter the Management IP address of the controller
• Subnet Mask–Enter the Subnet Mask of the controller
• Default Gateway–Enter the Default Gateway for the controller
• Management VLAN–For tagged, enter the Management VLAN else leave is blank
11
Step 7 Under the Create Your Wireless Network, enter the following:
• Network Name–Enter the Network Name. This will be the SSID.
• Security–Enter the Security for this WLAN. I am selecting WPA2 Personal.
• Passphrase–Enter the passphrase for the SSID.
• VLAN–If WLAN is on the same network as Management, select ‘Management VLAN’ else enter the VLAN ID
for the WLAN.
• DHCP Server–This is optional but one can enter the DHCP server for the WLAN clients.
12
Step 8 Enable RF Parameter Optimization and select the Client Density and Traffic Type.
Step 9 Enter the following as well:
• Virtual IP address: Enter the Virtual IP address.
• Local Mobility Group–Enter the Local Mobility Group name.
• Service Port Interface–Leave this as DHCP if you want the Service Port to obtain an IP address from the DHCP
server. Service Port is typically used out-of-band management and should be on a different network than the
controller management network.
13
Step 10 Confirm the Settings below. The WLC will go through the reboot.
Step 11 After the reboot, open a Web Browser and navigate to the WLC 3540 Management WebUI.
14
Deploying WLC 3504 through CLI
Deploying WLC 3504 is similar to how the 5508 and 5520 WLC are deployed.
To deploy WLC 3504, follow the procedure below:
Procedure
Enable HA [yes][NO]: NO
Enter Country Code list (enter 'help' for a list of countries) [US]:
15
Enter a polling interval between 3600 and 604800 secs: 3600
Configuration correct? If yes, system will save it and reset. [yes][NO]: yes
Cleaning up DHCP Server
Cleaning up Provisioning SSID
Cleaning up Provisioning SSID
Updating HBL license statistics file
Done.
Configuration saved!
Resetting system with new configuration...
To connect a pair of WLC 3504 in HA Setup to the wired network, one can use the following deployment examples. Please note that
only two links are shown from WLC3504 to the switch(s) but one can connect all four of the GE links + mGig link for LAG.
16
WLC supports the same HA configuration as other WLC. To configure High Availability, refer to the HA deployment guide at the
link below: http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-1/HA_SSO_DG/High_Availability_DG.html
To change the speed on the mGig port, follow the procedure below:
Procedure
Step 1 Navigate the WLC WebUI and browse to Controller > Ports. Click on Port 5.
17
Step 2 Set the Max Speed to either 1000, 2550 or 5000. Please note that If the speed is set to 2500 or 5000 on mGIg port, it will
negotiate with the corresponding switch port for the max speed it can support.
Note Cisco WLC does not send CDP advertisements on a LAG interface.
18
• When you include mGig port on the WLC 3504 in LAG, it must be configured to 1Ggig.
• LAG requires the EtherChannel to be configured for 'mode on' on both the controller and the Catalyst switch.
• Terminating on two different modules within a single Catalyst 6500 series switch provides redundancy and ensures that connectivity
between the switch and the controller is maintained when one module fails. The controller’s port 1 is connected to Gigabit
interface 3/1, and the controller’s port 2 is connected to Gigabit interface 2/1 on the Catalyst 6500 series switch. Both switch
ports are assigned to the same channel group.
• Once the EtherChannel is configured as on at both ends of the link, the Catalyst switch should not be configured for either Link
Aggregation Control Protocol (LACP) or Cisco proprietary Port Aggregation Protocol (PAgP) but be set unconditionally to
LAG. Because no channel negotiation is done between the controller and the switch, the controller does not answer to negotiation
frames and the LAG is not formed if a dynamic form of LAG is set on the switch. Additionally, LACP and PAgP are not supported
on the controller.
• If the recommended load-balancing method cannot be configured on the Catalyst switch, then configure the LAG connection
as a single member link or disable LAG on the controller.
• You cannot configure the controller’s ports into separate LAG groups. Only one LAG group is supported per controller. Therefore,
you can connect a controller in LAG mode to only one neighbor device.
• When you enable LAG or make any changes to the LAG configuration, you must immediately reboot the controller.
• When you enable LAG, you can configure only one AP-manager interface because only one logical port is needed. LAG removes
the requirement for supporting multiple AP-manager interfaces.
• When you enable LAG, all dynamic AP-manager interfaces and untagged interfaces are deleted, and all WLANs are disabled
and mapped to the management interface. Also, the management, static AP-manager, and VLAN-tagged dynamic interfaces are
moved to the LAG port.
• Multiple untagged interfaces to the same port are not allowed.
19
• When you enable LAG, you cannot create interfaces with a primary port other than 29.
• When you enable LAG, access points remain connected to the controller until you reboot the controller, which is needed to
activate the LAG mode change, and data service for users continues uninterrupted.
• When you enable LAG, the controller sends packets out on the same port on which it received them. If a CAPWAP packet from
an access point enters the controller on physical port 1, the controller removes the CAPWAP wrapper, processes the packet, and
forwards it to the network on physical port 1. This may not be the case if you disable LAG.
• When you disable LAG, the management, static AP-manager, and dynamic interfaces are moved to port 1.
• When you disable LAG, you must assign an AP-manager interface to each port on the controller. Otherwise, access points are
unable to join.
Procedure
20
Upgrading WLC 3504 using USB
Upgrading via USB is a new Transfer Mode which is available on Cisco WLC 3504. To upgrade via USB, follow the procedure
below:
Procedure
Step 1 Download the WLC3504 Software Image on the USB and insert the USB interface on the front panel of WLC 3504.
Step 2 Login to the WLC CLI and execute the following command:
(Cisco Controller) >config usb enable
Step 3 Login to the WLC WebUi and navigate to the COMMANDS menu as shown below.
• Select File Type as Code
• For Transfer Mode, select USB form the drop-down list
• Enter the USB Path to the file
• Enter the File Name on the USB
Step 4 Click on the Download button to initiate the software download and click on OK when you see the confirmation window.
Step 5 After the Software Download is complete, please reboot the WLC to run the new software.
Shown below is the debug messages in the WLC CLI while performing Software Download from USB.
21
(Cisco Controller) >debug transfer all enable
*TransferTask: Jun 05 14:13:31.989: RESULT_STRING: Writing new AP Image Bundle to flash disk.
22
Americas Headquarters Asia Pacific Headquarters Europe Headquarters
Cisco Systems, Inc. CiscoSystems(USA)Pte.Ltd. CiscoSystemsInternationalBV
San Jose, CA 95134-1706 Singapore Amsterdam,TheNetherlands
USA
Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the
Cisco Website at www.cisco.com/go/offices.