© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 44 of 70
Relevant excerpts from outputs regarding wireless configuration on the Cisco Catalyst 3850 are shown in the
following:
MC1#show wireless mobility summary
Mobility Controller Summary:
Mobility Role : Mobility Controller
Mobility Protocol Port : 16666
Mobility Group Name : default
Controllers configured in the Mobility Domain:
IP Public IP Group Name Multicast IP
Link Status
-----------------------------------------------------------------------------
20.1.3.2 - default - UP : UP
MC1#show wlan summary
Number of WLANs: 1
WLAN Profile Name SSID VLAN Status
----------------------------------------------------------------------------
1 Predator Predator 500 UP
MC1#show capwap summary
CAPWAP Tunnels General Statistics:
Number of Capwap Data Tunnels = 2
Number of Capwap Mobility Tunnels = 0
Number of Capwap Multicast Tunnels = 0
Name APName Type PhyPortIf Mode McastIf
------ -------------------------------- ---- --------- --------- -------
Ca5 3502E_G2/0/25_83A9 data Gi2/0/25 unicast -
Ca4 3602I_G2/0/1_3A04 data Gi2/0/1 unicast -
Name SrcIP SrcPort DestIP DstPort DtlsEn MTU
------ --------------- ------- --------------- ------- ------ -----
Ca5 20.1.3.2 5247 20.1.3.54 63548 No 1657
Ca4 20.1.3.2 5247 20.1.3.53 58274 No 1657
The preceding output shows that two data CAPWAP tunnels are formed with the Cisco access points, 3502E off of
GigabitEthernet 2/0/25 (second switch in the stack) and 3602I off of GigabitEthernet 2/0/1. 20.1.3.2 is the
switch/wireless management IP address of this switch. The last section in the output of "show capwap summary"
displays the source IP address with which the switch forms the data CAPWAP tunnels with the access points with
their IP addresses listed, as 20.1.3.54 on destination port 63584 and 20.1.3.53 on destination port 58274.
Consider the one-switch stack network experiences growth, and now the network administrator needs to add more
Cisco Catalyst 3850 Switches and expand wireless coverage to more endpoints and devices. (See Figure 14.)