Documente Academic
Documente Profesional
Documente Cultură
Project Title:
Wireless LAN Controller Based Architecture
Controller Installation Guide
Location:
IGA
Last Revision Date:
15 September 2011
Cisco Controller Release 6.0.202.0
Cisco Controller Release 7.0.98.218 (for 3502 and 1262 WAPs)
Revision History
Date
15 Sep 2011
Who
Andrew Potter
Purpose
11.1 Template release
1.3
Load current Wireless LAN controller code .............................................................................................. 8
1.3.1
Config TACACS and Radius Servers ........................................................................................................ 9
1.3.2
Create AL_CPU_ACCESS access control list ......................................................................................... 10
1.3.3
Apply the ACL (note different syntax for V6 and V7 code) .................................................................... 13
1.3.4
Test TACACS (Americas, AP) ................................................................................................................ 13
1.3.5
Generate Webadmin/SSH self signed certificate and disable controller handling of DHCP helper for
client users .............................................................................................................................................................. 13
2.6
IBM-WPA1 Profile ..................................................................................................................................... 33
2.6.1
IBM-WPA1 profile WLANs Edit ............................................................................................................ 33
2.6.2 ........................................................................................................................................................................ 33
2.6.3
IBM-WPA1 profile WLAN Edit Security Layer 2 tab ............................................................................ 34
2.6.4
WLANs Edit Create IBMVISITOR Profile (SSID IBMVISITOR) ...................................................... 35
2.7
IBMVISITOR WLAN Edit General ......................................................................................................... 36
2.7.1
IBMVISITOR WLAN Edit Security Layer 2 .......................................................................................... 36
2.7.2
IBMVISITOR WLAN Edit Advanced ..................................................................................................... 37
2.7.3
Wireless Access Points Global configuration .................................................................................... 38
2.7.4
Wireless 802.11a/n Network .............................................................................................................. 38
2.7.5
Wireless 802.11a/n RRM DCA ......................................................................................................... 39
2.7.6
Wireless 802.11b/g/n Network ........................................................................................................... 40
2.7.7
Wireless 802.11b/g/n RRM DCA ..................................................................................................... 41
2.8
WISM controllers can also use standard Cisco blue console rollover serial cable. (Note 2
consoles per WISM blade)
HINT. If you skip a question by mistake or answer wrong, you can back up to the
previous question by typing the minus key -and pressing <Enter>
Boot up the controller. Wait until it boots and prompts.
Resetting to Default Settings Using the CLI (WISM session or 440x/5508 serial
console only)
If the controller has an undesired old configuration, follow these steps to reset the configuration
to factory default settings using the CLI.
Step 1 If logged in, enter reset system. At the prompt that asks whether you need to save
changes to the configuration, enter N. The unit reboots.
Step 2 Reconnect to the console. When you are prompted for a username, enter recover-config
to restore the factory default configuration. The controller reboots and displays this message:
Welcome to the Cisco WLAN Solution Wizard Configuration Tool
9.<x.x.x>
<netmask>
<gateway>
4001
IP address of DHCP server that will supply IP addresses to clients: <dhcp #1>
(Others added later)
LWAPP transport mode (layer 2 or layer 3): layer 3 (not asked on WISM)
AP manager interface IP address: <ap manager IP address>
(this question will not be asked on 5508 controllers)
Controller>
If the ports show up and the management interface responds to ping, then the initial install is
complete.
Delete the WLAN created during the dialog script. Correct WLAN profiles configured later.
Controller> Config wlan delete 1
Controller> save config
Important: Refer to Cisco Release notes to ensure that code is upgraded properly. Very old
code versions require upgrading to an intermediate version of code prior to version 6
https://www.cisco.com/en/US/products/ps6366/prod_release_notes_list.html
Log into the controller management IP address using failsafe via ssh 9.<x.x.x>
Controller> show sysinfo
Verify code level
Code is on Controller WCS server via TFTP at 9.41.5.184
Hint: due to TFTP speeds across WAN a LOCAL TFTP server is strongly recommended.
Version 5.2 and later code support much faster transfers using FTP
Set TFTP download parameters:
transfer
transfer
transfer
transfer
download
download
download
download
filename <tftp-code-image>.aes
serve rip <ip address of tftp server>
datatype code
path <file path> (If using WCS path is /)
config
config
config
config
config
config
config
radius
radius
radius
radius
radius
radius
radius
auth
auth
auth
auth
auth
auth
auth
retransmit-timeout
retransmit-timeout
retransmit-timeout
retransmit-timeout
retransmit-timeout
retransmit-timeout
retransmit-timeout
config
config
config
config
config
config
config
radius
radius
radius
radius
radius
radius
radius
auth
auth
auth
auth
auth
auth
auth
management
management
management
management
management
management
management
config
config
config
config
config
config
config
radius
radius
radius
radius
radius
radius
radius
auth
auth
auth
auth
auth
auth
auth
add
add
add
add
add
add
add
1
2
3
4
5
6
7
1
2
3
4
5
6
7
49
49
49
49
ascii
ascii
ascii
ascii
1
2
3
4
5
6
7
<TACACS-shared-secret>
<TACACS-shared-secret>
<TACACS-shared-secret>
<TACACS-shared-secret>
4
4
4
4
4
4
4
disable
disable
disable
disable
disable
disable
disable
9.41.5.108
9.17.182.81
9.61.5.108
9.56.5.173
9.27.5.108
9.45.5.108
9.43.5.108
1812
1812
1812
1812
1812
1812
1812
ascii
ascii
ascii
ascii
ascii
ascii
ascii
<wireless-shared-secret>
<wireless-shared-secret>
<wireless-shared-secret>
<wireless-shared-secret>
<wireless-shared-secret>
<wireless-shared-secret>
<wireless-shared-secret>
save config
If you make a mistake, you must delete any definitions before re-applying them
Config radius auth delete 1 (repeat for servers 2 7)
Config tacacs auth delete 1 (repeat for server 2)
Config tacacs athr delete 1 (repeat for server 2)
acl
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 2
destination port range AL_CPU_ACCESS 2 161 161
protocol AL_CPU_ACCESS 2 17
action AL_CPU_ACCESS 2 permit
direction AL_CPU_ACCESS 2 in
source address AL_CPU_ACCESS 2 9.0.1.0 255.255.255.0
add AL_CPU_ACCESS 3
config
config
config
config
config
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 4
destination port range AL_CPU_ACCESS 4 161 161
protocol AL_CPU_ACCESS 4 17
action AL_CPU_ACCESS 4 permit
direction AL_CPU_ACCESS 4 in
source address AL_CPU_ACCESS 4 9.0.3.0 255.255.255.0
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 5
destination port range AL_CPU_ACCESS 5 161 161
protocol AL_CPU_ACCESS 5 17
action AL_CPU_ACCESS 5 permit
direction AL_CPU_ACCESS 5 in
source address AL_CPU_ACCESS 5 9.0.4.0 255.255.255.0
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 6
destination port range AL_CPU_ACCESS 6 161 161
protocol AL_CPU_ACCESS 6 17
action AL_CPU_ACCESS 6 permit
direction AL_CPU_ACCESS 6 in
source address AL_CPU_ACCESS 6 9.0.5.0 255.255.255.0
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 7
destination port range AL_CPU_ACCESS 7 161 161
protocol AL_CPU_ACCESS 7 17
action AL_CPU_ACCESS 7 permit
direction AL_CPU_ACCESS 7 in
source address AL_CPU_ACCESS 7 9.0.6.0 255.255.255.0
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 8
destination port range AL_CPU_ACCESS 8 161 161
protocol AL_CPU_ACCESS 8 17
action AL_CPU_ACCESS 8 permit
direction AL_CPU_ACCESS 8 in
source address AL_CPU_ACCESS 8 9.0.7.0 255.255.255.0
10
config
config
config
config
config
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 10
destination port range AL_CPU_ACCESS 10 161 161
protocol AL_CPU_ACCESS 10 17
action AL_CPU_ACCESS 10 permit
direction AL_CPU_ACCESS 10 in
source address AL_CPU_ACCESS 10 9.0.9.0 255.255.255.0
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 11
destination port range AL_CPU_ACCESS 11 161 161
protocol AL_CPU_ACCESS 11 17
action AL_CPU_ACCESS 11 permit
direction AL_CPU_ACCESS 11 in
source address AL_CPU_ACCESS 11 9.17.5.0 255.255.255.0
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 12
destination port range AL_CPU_ACCESS 12 161 161
protocol AL_CPU_ACCESS 12 17
action AL_CPU_ACCESS 12 permit
direction AL_CPU_ACCESS 12 in
source address AL_CPU_ACCESS 12 9.27.5.0 255.255.255.0
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 13
destination port range AL_CPU_ACCESS 13 161 161
protocol AL_CPU_ACCESS 13 17
action AL_CPU_ACCESS 13 permit
direction AL_CPU_ACCESS 13 in
source address AL_CPU_ACCESS 13 9.0.33.0 255.255.255.0
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 14
destination port range AL_CPU_ACCESS 14 161 161
protocol AL_CPU_ACCESS 14 17
action AL_CPU_ACCESS 14 permit
direction AL_CPU_ACCESS 14 in
source address AL_CPU_ACCESS 14 9.41.5.0 255.255.255.0
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 15
destination port range AL_CPU_ACCESS 15 161 161
protocol AL_CPU_ACCESS 15 17
action AL_CPU_ACCESS 15 permit
direction AL_CPU_ACCESS 15 in
source address AL_CPU_ACCESS 15 9.43.5.0 255.255.255.0
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 16
destination port range AL_CPU_ACCESS 16 161 161
protocol AL_CPU_ACCESS 16 17
action AL_CPU_ACCESS 16 permit
direction AL_CPU_ACCESS 16 in
source address AL_CPU_ACCESS 16 9.45.5.0 255.255.255.0
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 17
destination port range AL_CPU_ACCESS 17 161 161
protocol AL_CPU_ACCESS 17 17
action AL_CPU_ACCESS 17 permit
direction AL_CPU_ACCESS 17 in
source address AL_CPU_ACCESS 17 9.56.5.0 255.255.255.0
11
config
config
config
config
config
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 19
destination port range AL_CPU_ACCESS 19 161 161
protocol AL_CPU_ACCESS 19 17
action AL_CPU_ACCESS 19 permit
direction AL_CPU_ACCESS 19 in
source address AL_CPU_ACCESS 19 135.89.176.0 255.255.255.0
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 20
destination port range AL_CPU_ACCESS 20 161 161
protocol AL_CPU_ACCESS 20 17
action AL_CPU_ACCESS 20 permit
direction AL_CPU_ACCESS 20 in
source address AL_CPU_ACCESS 20 135.89.45.0 255.255.255.0
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 21
destination port range AL_CPU_ACCESS 21 443 443
protocol AL_CPU_ACCESS 21 6
action AL_CPU_ACCESS 21 permit
direction AL_CPU_ACCESS 21 in
source address AL_CPU_ACCESS 21 9.0.0.0 255.0.0.0
config
config
config
config
config
config
acl
acl
acl
acl
acl
acl
rule
rule
rule
rule
rule
rule
add AL_CPU_ACCESS 22
destination port range AL_CPU_ACCESS 22 22 22
protocol AL_CPU_ACCESS 22 6
action AL_CPU_ACCESS 22 permit
direction AL_CPU_ACCESS 22 in
source address AL_CPU_ACCESS 22 9.0.0.0 255.0.0.0
config
config
config
config
acl
acl
acl
acl
rule
rule
rule
rule
add AL_CPU_ACCESS 23
destination port range AL_CPU_ACCESS 23 443 443
protocol AL_CPU_ACCESS 23 6
direction AL_CPU_ACCESS 23 in
config
config
config
config
acl
acl
acl
acl
rule
rule
rule
rule
add AL_CPU_ACCESS 24
destination port range AL_CPU_ACCESS 24 22 22
protocol AL_CPU_ACCESS 24 6
direction AL_CPU_ACCESS 24 in
config
config
config
config
acl
acl
acl
acl
rule
rule
rule
rule
add AL_CPU_ACCESS 25
destination port range AL_CPU_ACCESS 25 161 161
protocol AL_CPU_ACCESS 25 17
direction AL_CPU_ACCESS 25 in
12
1.3.3 Apply the ACL (note different syntax for V6 and V7 code)
config acl apply AL_CPU_ACCESS
config acl cpu AL_CPU_ACCESS both
save config
13
14
15
1.
2.
3.
4.
5.
Click NEW
Enter in NTP server 1
Click apply
Enter in NTP server 2
Click Apply and Save Configuration
Verify that Management, AP-Manager exist in VLAN 4001 and that the Virtual interface is set to
1.1.1.1
16
Click new
Create default-non-usable VLAN ID 4093 . Do NOT put this VLAN on WD /CD/UD or any
switch port to any controller. This VLAN is a default non functioning subnet used to park new
Access Points (APs) prior to their being configured on the controller. This reduces the risk of the
IBMVISITOR SSID of mistakenly mapping to an IBM 9.x.x.x subnet.
Netmask
17
Fill in VLAN ip address, netmask (/23 or /24) from controller address spreadsheet default
gateway. Start the IP addressing at the .5 address in the user subnet (same addressing as a
User Access switch)
Fill in primary and secondary DHCP servers.
Click Apply
Repeat for each IBM VLAN needed
18
Enter VLAN name VLAN-<vlan #>-GUEST and VLAN id: <vlan #>
19
MAC address and Management IP address for this controller should display
Click new
Enter in MAC address and Management IP address of all controllers in the same Layer 2
domain. (MAC address visible on Controller Inventory screen)
Hint: do this on one controller, then click editall and copy the information for
pasting into the other controllers serving the same site access points.
Click Apply
Note: Verify Mobility configuration by using SSH console level commands:
Controller> mping <ip-address-of-mobility-member-controllers>
Controller> eping <ip-address-of-mobility-member-controllers>
The Mping command is a special controller only command that validates the LWAPP/CAPWAP
connection between the controller members of the same mobility group. This is important to manage
shared radio management, AP discovery, and client roam decisions
The Eping command is a special command that validates the ability of the controller to establish an
Ethernet-over-IP layer 2 link between different controllers in the same mobility group. This feature is
critical to allow client users to maintain their original IP address as they roam between different
controllers in the same Mobility group.
20
1.
2.
3.
4.
5.
6.
Click Communities
Click New
4. Click Apply.
5. Repeat for RW community string.
6. RW is address and netmask is 0.0.0.0
Click New
Enter community name and IP address for WCS server (Currently In US 9.41.5.184)
Status enable
For US and Canada only: Add two SNMP trap destinations for iGEMS servers. Call these
community names IGEMS1 and IGEMS2 per the following rule.
a. If the Controller hostname begins with letters a though f or digits 0 though 9,
enter 135.89.176.120 and 135.89.45.120 as SNMP trap destinations
b. If the Controller hostname begins with letters g though z, enter 135.89.45.121
and 135.89.176.121 as SNMP trap destinations
c. For all controllers installed in Canada, enter 135.89.176.122 and 135.89.45.122 as
SNMP trap destinations.
5. For other global regions, enter the appropriate IGEMS or NetView trap destinations.
6. Click Apply and Save Configuration
1.
2.
3.
4.
22
1.
2.
3.
4.
Enter IP address of Syslog server (US Wireless LAN syslog server is 9.0.6.151)
Click Add,
Click Apply
Save Configuration
23
Security Radius
Expand Radius on left
Click New
IP
9.41.5.108
9.17.182.81
9.61.5.108
9.56.5.173
9.27.5.108
9.45.5.108
24
snjk-cs-lc01-en0.sanjose.ibm.com
9.43.5.108
25
Verify the two TACACS servers 9.0.4.33 and 9.0.2.33 are defined and Enabled
on Index 1 and 2 to edit if necessary. Server timeout is 5 seconds.
Click
Repeat step for TACACS Authorization servers 9.0.4.33 and 9.0.2.33 should be
defined and enabled.
26
2.3.4
2.3.5 Security - Priority Order > Management User
Verify this: (US, AP only) Expand Priority Order, Select Management User
1. Use > and < buttons to send TACACS+ and LOCAL to order used for
Authentication.
2. Use Up and Down to make TACACS+ the first service attempted.
27
(Set Timezone)
28
IBM-WPA2 Profile
1.
2.
3.
4.
5.
29
1. Status Enabled Not checked (do not enable until controller config is complete)
2. Radio Policy All
3. Interface default-non-usable (actual VLAN is assigned later using AP Group feature
when Access points are installed and configured on the controller)
4. Broadcast SSID check Enabled
30
1. Select from Authentication Servers three previously defined ACS servers for this
WLAN based on Load Balance design and those that are closest. Choose for server 1,
Server 2 and Server 3
2. Click Apply and Save Configuration
31
32
1.
2.
3.
4.
5.
2.6.2
1.
2.
3.
4.
Status Enabled Not checked (do not enable until controller config is complete)
Radio Policy All
Interface default-non-usable
Broadcast SSID check Enabled
33
Complete configuration of the WLAN IBM-WPA1 profile following the same steps as the IBMWPA2 WLAN profile continuing from step WLANs Edit Security AAA Servers above.
34
35
1. Status Enabled NOT checked (this will be enabled later when the APs are fully
configured)
2. Radio policy all
3. Interface default-non-usable
4. Broadcast SSID enabled
36
37
38
1.
2.
3.
4.
39
1.
2.
3.
4.
40
1.
2.
3.
4.
5.
41
1.
2.
3.
4.
5.
6.
7.
This completes the base configuration of the controller. Access points are configured in Section
3 below.
You can also view the configuration commands by logging in via SSH to the controller and
issuing the following command
Controller> show run-config commands
Screen paging can be disabled with the command:
Controller> config paging disable
42
43
44
45
46
group, it will use the default-non-usable VLAN defined on the SSIDs and wireless LAN
connectivity will be disabled.
47
1. Select the first IBM SSID profile (note the IBM-WPA2 profile name will not show up)
2. Select the correct IBM VLAN for the interface name.
3. Click Add
4. Click Add New
5. Click the 2nd IBM SSID Profile (note the IBM-WPA1 profile name will not show up)
6. Select the same IBM VLAN profile as in step 2 above to select the correct IBM VLAN
7. Click Add
8. Click Add New
9. Select the IBMVISITOR SSID profile
10. Select the correct VLAN-202x-GUEST VLAN for the IBMVISITOR
11. Click Add, Click Save Configuration
The completed AP group will look like :
48
Before attempting to join access points to a controller, verify the discovery controller for the
site by doing an NSLOOKUP command to verify these DNS aliases.
c:\nslookup cisco-lwapp-controller.pok.ibm.com
Server: POKDNS01.srv.ibm.com
Address: 9.0.2.1
Name:
pok-wc-w3c1a.pok.ibm.com
Address: 9.57.120.139
Aliases: cisco-lwapp-controller.pok.ibm.com
c:\
Secondly, each access point must be defined after discovery to operate with a primary and backup
controller. The backup controller will only be used by the access point if the primary controller fails.
The location of the backup controller will be within the same layer 2 distribution block for medium
and large wireless site types. For small site types with a single onsite controller, the backup
controller will be at a large site and will offer layer 3 failover.
49
50
General tab.
High Availability tab: Fill in primary and backup controller name and IP.
Click Apply. APs will reboot one last time with their new VLAN group.
Click save configuration
51
52
53
54
55
Verify that the Both WLAN profiles IBM-WPA2 and IBM-WPA2 are enabled for
HREAP (WLANs, Click on each profile and select Advanced, HREAP checked at
the bottom)
56
Fill in the VLAN information: (Interface IP, Netmask, Gateway Default route. DHCP is the
Gateway, Click Apply, Click Save Configuration
57
Add the new AP group for this site: WLANs, Advanced, AP Groups Click Add
Group
Enter Group name (Format: <Central-Site-RESO>-<City>-HREAP) Click Add
HREAP ADD APGROUP WLAN: Click on the new AP group. Click the WLANs tab
within the AP group
Select WLAN IBM(20), Select Interface name default-non-usable, Click Add
58
59
Note that the DNS Discovery controller may not be the same intended to permanently support
these WAPs. For this situation, simply allow the discovery to occur and then re-assign the APs
primary and backup controllers to their correct operational controllers.
60
5.1.4 Connect the HREAP APs and enable the Ethernet ports.
Follow the steps in Chapter 5 (AP Join) to discover and configure each of the access points
with the following two exceptions.
1. In the Wireless tab, click <ap-name>, general tab, select AP Mode: HREAP
2. Check Static IP and assign the AP Static IP address, netmask, gateway, domain
name and DNS server for the wireless VLAN on the site UA switch. (it is important to
fill in all 5 fields)
3. When you click apply the AP will reboot and join in HREAP mode.
61
Browse to and select the floor area where these new APs are being installed OR where
old IOS APs have been migrated and converted to controller based wireless..
Note: If the floor area is not present in WCS, then it must be loaded in by the AT&T
network server support team. A JPEG (.jpg) or portable network graphics (.png) floor
plan file must be supplied. These files can be sent to the IBM Lotus Notes ID
ACSADMIN asking that they be placed in to WCS. Please identify the site, building
floor and floor area of each floor plan map supplied.
62
Select one or more APs from the list of un-assigned APs for placement on this floor area
The APs you selected will show up at the upper right of the floor plan.
Drag and drop the AP to the proper location on the map.
Click save
63
The WAP will show up with its RF heat map (802.11a or 802.11b/g) . Select heat map, client
and configuration viewing options from the list on the left.
64
If the service IP shows 0.0.0.0, then the session command will not work. Verify the 6509 configuration
template the correct private DHCP scope configured to the WISM service VLAN. If the controller does NOT
have a service IP address, then the WISM module must be power cycled using the config level command
power cycle . NOTE: this will power cycle BOTH controllers on this module.
Verify that the controller has gotten a DHCP address from for the Service IP
ft0-wd-4a#sh wism module 4 controller 2 status
WiSM Controller 2 in Slot 4 configured with auto-lag
Operational Status of the Controller : Oper-Up
Service VLAN
: 4081
Service Port
: 10
Service Port Mac Address
: 001f.cac0.a382
Service IP Address
: 192.168.253.129
Management IP Address
: 169.254.1.1
Software Version
: 6.0.188.0
Port Channel Number
: 408
Allowed-vlan list
: 2001-2003,2021-2022,4001
WCP Keep Alive Missed
: 0
Connect to controller and run console dialog
ft0-wd-4a# session slot 4 processor 2
The default escape character is Ctrl-^, then x.
You can also type 'exit' at the remote prompt to end the session
Trying 192.168.253.129 ... Open
(WiSM-slot4-2)
Welcome to the Cisco Wizard Configuration Tool
Use the '-' character to backup
Would you like to terminate autoinstall? [yes]: yes
System Name [Cisco_c0:a3:8b] (31 characters max): <hostname>
Enter Administrative User Name (24 characters max): failsafe
ft0-wc-w1c2a
65
Interface
Interface
Interface
Interface
Interface
Interface
Configuration correct? If yes, system will save it and reset. [yes][NO]: yes
Configuration saved!
Resetting system with new configuration...
[Connection to 192.168.253.129 closed by foreign host]
ft0-wd-4a#
66
ft0-wd-4a#
67
Type
------Normal
Normal
Normal
Normal
STP
Stat
---Forw
Forw
Forw
Forw
Admin
Mode
------Enable
Enable
Enable
Enable
Physical
Mode
---------Auto
Auto
Auto
Auto
Physical
Status
---------1000 Full
1000 Full
1000 Full
1000 Full
Link
Status
-----Up
Up
Up
Up
Link
Trap
------Enable
Enable
Enable
Enable
Mcast
Appliance
POE
--------- ------Enable
N/A
Enable
N/A
Enable
N/A
Enable
N/A
Port
---LAG
LAG
N/A
N/A
Vlan Id
-------4001
4001
N/A
N/A
IP Address
--------------9.32.112.16
9.32.112.15
192.168.253.129
1.1.1.1
Type
------Static
Static
Static
Static
Ap Mgr
-----Yes
No
No
No
Guest
----No
No
No
No
68