Interface WLC 5508 AP-Manager

Hi, I own a WLC 5508 and (probably), I do not understand the AP Manager interfaces. I have a laboratory with 2 x 1242AG and 1 x 1252AG connected to c2960. APs in vlan 10 (192.168.10.0/24, configured via DHCP), APs are connected to interface 'switchport access mode. C2960 is connected via a trunk to c4506 and WLC is plugged into article gi1/3 and article gi1/4 (both through twingig). The two ports are configured as 'switchport mode trunk ". WLC management interface is IDE oucederomsurlesecondport WLC 8 (linked to article gi1/4), and AP-Manager is on port 1 (connected to article gi1/3) WLC. WLC management interface has 'Management dynamic AP' set to off, and AP-Manager defined activated. The two are interfaces to management and AP-Manager tag, vlan id 12 and 13 (subnets 192.168.12.0/24, 192.168.13.0/24) respectively. APs receive their IP through DHCP configuration (server located in vlan 20, 192.168.20.0, in use ip helper-address) and try to discover DNS resolution WLC (CISCO-CAPWAP - CONTROLLER.some.domain resolves to AP-Manager IP correctly). But AP has the status "not connected" in monitor/statistics/AP join APs do not join to the controller, said WLC "Discovery request Ignoring received on the management interface".

But if I put management interface as "Dynamic AP activated" and change the DNS to resolve CISCO-CAPWAP... it's IP everything works well - AP is associated with the time. Please help, how to reach the KNEES a AP-Manager interface? Sign up for the Manager of WLC is simple, but my design requires at least 2 interfaces AP Manager.

If you have a 5508, why you have the AP Manager?

Tags: Cisco Wireless

Similar Questions

WLC 5508 management interface

Hi, I have a design requiring a WLC 5508 be connected to two separate swithces specific wireless. WLC 1 port is connected to the switch A trunk and WLC Port 2 is connected to the switch B. Each switch has its own local VLANS. When I connect the years 1130 towers they need find the interface of management initially then only use management. AP interfaces since there is only a single management interface, if the assignment of management interface on a VLAN that is configured on the switch then APs on spend a fine join but those switch B continue to ask for the management interface and the version debug capwap on WLC he says that this query Join were received on the bad ineterface...

the only work around that was to do the routing between switch A and switch B for both VLAN residing APs... but for security reasons - customer would like to avoid this

any help is appreciated...

Unfortunately, the initial discovery must arrive in the management interface. Once this has happened the AP expected the second AP manager who is on the subnet of comments, therefore, they are able to stand. But if the AP is restarted, it would need to discover once again and would fail.

What is the concern of customers to have all routable network mgmt AP? guest users can not see anything there.

IMO, let the AP able to connect to the subnet of mgmt, but then put an ACL L3 upward, to block the subnet of comments to achieve anything in the internal network.

WLC 5508 internal DHCP server issues

Hello

I'm hoping to get your comments around the issues of dhcp, I faced with two centrally switched Wireless LAN. I have attempted to explain the installation and the problems below and would be grateful if anyone can suggest a solution for the problems I am facing:

The configuration is the following:

-J' have a WLC 5508, which has been configured with 4 SSID, of which 2 are the Central authentication and commissioning.
-J' have a LWAP connected to the WLC in HREAP mode.
-WLC is configured as a DHCP server for clients that connect to the SSID "Guest." For the rest, I'm on external dhcp server.
-Only one scope of comments Interface is configured on the WLC.

Problems:

1. as far as I know, to WLC serve internal dhcp server, it is mandatory to have the proxy enabled, but the Clients connecting to 'Internet' SSID are

Unable to get an external dhcp server ip address, if the proxy dhcp is enabled on the WLC. If I disable the proxy, everything works fine.

2 DHCP does not release the ip addresses assigned to clients, even after that that they are connected.

3. If a machine that has previously been connected to "Guest" SSID connects to the 'Internet' SSID, he asks the same ip address, he was charged by the WLC assigned under "Guest", it gets the tag with the Vlan configured on the management interface.

The controller output *.

(Cisco Controller) > show sysinfo

Name of the manufacturer... Cisco Systems Inc..
Product name... Cisco controller
Version of the product... 7.0.116.0
Bootloader Version... 1.0.1
Retrieving Image Version field... 6.0.182.0
Firmware version... Console USB 1.3, 1.6 Env FPGA, 1.27
Build Type....................................... DATA + WPS, LDPE

(Cisco Controller) > show interface summary

Name interface Vlan Id IP port address Type Ap Mgr. Gu

EST
-------------------------------- ---- -------- --------------- ------- ------ --
1 301 10.255.255.30 dynamic guest no no
Management 1 100 172.17.1.30 static yes no

service-port s/o s/o 192.168.0.1 static no no
n/a n/a 10.0.0.1 no nonstatic virtual

(Cisco Controller) > show wlan summary

Number of wireless LANs... 4

Profile WIFI WLAN ID name / name of the SSID status Interface
------- ------------------------------------- -------- --------------------
1 active LAN management
2 active Internet management
3 active active management management
4 comments comments enabled

(Cisco Controller) > show dhcp detailed comments

Scope: comments

Enabled.......................................... Yes
Lease Time....................................... 86400 (1 day)
Pool Start....................................... 10.255.255.31
Pool End......................................... 10.255.255.254
Network.......................................... 10.255.255.0
Netmask.......................................... 255.255.255.0
Default routers... 10.255.255.1 0.0.0.0 0.0.0.0
DNS Domain.......................................
DNS.............................................. 8.8.8.8 8.8.4.4 0.0.0.0
NetBIOS name servers... 0.0.0.0 0.0.0.0 0.0.0.0

(Cisco Controller) > show detailed interface management

... Management interface
MAC address... e8:b7:48:9 b: 84:20
IP Address....................................... 172.17.1.30
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 172.17.1.1
State IP NAT outside... People with disabilities
External IP NAT... 0.0.0.0
VLAN............................................. 100
Quarantine-vlan... 0
Active physical Port... 1
The primary physical Port... 1
Port of physical backup... Not configured
Primary DHCP server... 172.30.50.1
Secondary DHCP server... Not configured
Option DHCP 82... People with disabilities
ACL.............................................. Not configured
AP Manager....................................... Yes
Comments interface... NO.
L2 multicast... Activated

(Cisco Controller) > show detailed comments from interface

Interface name... Comments
MAC address... e8:b7:48:9 b: 84:24
IP Address....................................... 10.255.255.30
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 10.255.255.1
State IP NAT outside... People with disabilities
External IP NAT... 0.0.0.0
VLAN............................................. 301
Quarantine-vlan... 0
Active physical Port... 1
The primary physical Port... 1
Port of physical backup... Not configured
Primary DHCP server... Not configured
Secondary DHCP server... Not configured
Option DHCP 82... People with disabilities
ACL.............................................. Not configured
AP Manager....................................... NO.
Comments interface... NO.
L2 multicast... Activated

(Cisco Controller) > show dhcp leases

IP MAC remaining rental period
00:21: 6a: 9 c: 03:04 10.255.255.46 23 hours, 52 minutes, 42 seconds< lease="" remains="" even="" when="" the="" client="" is="">

Example of customer connected to the Vlan right with an ip address from the incorrect interface. *************

(Cisco Controller) > show customer detail 00:21: 6a: 9 c: 03:04
MAC address of the client... 00:21: 6a: 9 c: 03:04
User name of the client... N/A
AP MAC address... a0:cf:5 b: 00:49:c0
AP Name.......................................... mel
Status of the client... Associates
Customer of the NAC OOB State... Access
Wireless LAN Id... 2< 'internet'="">
BSSID... a0:cf:5 b: 00:49: this
Connected to... dry 319
Channel.......................................... 36
IP Address....................................... 10.255.255.46< ip="" address="" assigned="" from="" the="" 'guest'="" interface="" or="" dhcp="" scope="" on="" the="">
Association ID... 1
Authentication algorithm... Open System
Reason code... 1
Status code... 0
Session timeout... 1800
Client CCX version... 4
Version of E2E customer... 1
QoS Level........................................ Silver
Beacon priority P 802,1... disabled
Support WMM... Activated
Power Save....................................... OFF
State of mobility... Local
County of movement mobility... 0
Complete security policy... Yes
State Policy Manager... RUN
Policy Manager rule created... Yes
ACL name... no
Status to apply ACL... Not available
Type of strategy... N/A
Encryption Cipher... None
Protection management framework... NO.
EAP Type......................................... Unknown
Data HARVEST-H switching... Central
H - HARVEST authentication... Central
Management of the interface...
VLAN............................................. 100< right="">
Quarantine VLAN... 0
Access VIRTUAL LAN... 100

Well it's good news. At least you have to operate.

Thank you

Scott Fella

Sent from my iPhone

1602i-e-k9 AP and WLC 5508 issue of Cisco

Dear forum participants,

I experience a problem connection Access Point 1602i-e-k9 to WLC 5508

I upack and taken an AP on the network, it appears on the WLC (monitor > all APs), I can see it using the link details for several time.

Then he desappears, restart does not help.

I searched the forum for solutions, made AP reset via command "cli rommon-like" + button "MODE" and "reset" . After that, the same thing happens again: he appears on WLC and disappears.

What I am doing wrong?

Brief info on devices and newspapers partial

Please see the full changelog of the AP attached (contains info after the reset command has been entered).

The AP Info

looking at the picture...

extracting information (283 bytes)

Image info:

Version suffix: k9w8-. 152 - 2.JB

Image name: ap1g2-k9w8 - mx.152 - 2.JB

The release directory: ap1g2-k9w8 - mx.152 - 2.JB

The iOS Image size: 9400832

Total image size: 9769472

Image device: Wireless LAN | LWAPP

Family pictures: AP1G2

Wireless switch management Version: 7.4.100.0

WLC Info

Name of the manufacturer... Cisco Systems Inc..

Product name... Cisco controller

Version of the product... 7.4.100.0

Bootloader Version... 1.0.1

Retrieving Image Version field... 6.0.182.0

Firmware version... Console USB 1.3, 1.6 Env FPGA, 1.27

Build Type....................................... DATA + WPS, LDPE

Journal of the AP

reset

[BEGIN] 20.03.2013 14:09:31

Are you sure you want to reset the system (y/n)? There

System reset...

Boot from flash

>>>>>>>>>>>>>>>>>>

"Loading Flash:/ap1g2-rcvk9w8-mx/ap1g2-rcvk9w8-mx"...### ".

File "flash: / ap1g2-rcvk9w8-mx/ap1g2-rcvk9w8-mx" unzipped and installed, point of entry: 0x100000

execution of...

>>>>>>>>>>>>>>>>>>

Software Cisco IOS, C1600 Software (AP1G2-RCVK9W8-M), Version 15.2 (2) JB, RELEASE SOFTWARE (fc1)

>>>>>>>>>>>>>>>>>>

^

Invalid entry % detected at ' ^' marker.

no ip address of the http server

^

Invalid entry % detected at ' ^' marker.

use. Delivery of Cisco cryptographic products does not imply

third party approval to import, export, distribute or use encryption.

Importers, exporters, distributors and users are responsible for

by default the authentication of connection

^

Invalid entry % detected at ' ^' marker.

compliance with U.S. laws and local countries. By using this product you

agree to comply with the regulations and laws in force. If you are unable

to satisfy the United States and local laws, return the product.

A summary of U.S. laws governing Cisco cryptographic products to:

http://www.Cisco.com/WWL/export/crypto/tool/stqrg.html

If you need assistance please contact us by mail at

[email protected] / * /.

>>>>>>>>>>>>>>>>>>

% Please first set a domain name.

Kern of logging mechanism

^

Invalid entry % detected at ' ^' marker.

emergency logging trap

^

Invalid entry % detected at ' ^' marker.

Press RETURN to get started!

* 00:00:12.787 Mar 1: % LWAPP-3-CLIENTERRORLOG: Config flash load failed. Initialization of Cfg

* 00:00:14.047 Mar 1: % LINK-6-UPDOWN: Interface GigabitEthernet0, changed State to

* 00:00:15.059 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed State to

* 00:00:15.507 Mar 1: % SYS-5-RESTART: System restarted.

Software Cisco IOS, C1600 Software (AP1G2-RCVK9W8-M), Version 15.2 (2) JB, RELEASE SOFTWARE (fc1)

Technical support: http://www.cisco.com/techsupport

Copyright (c) 1986-2012 by Cisco Systems, Inc.

Updated Wednesday, December 11, 12 04:52 by prod_rel_team

* 00:00:15.627 Mar 1: % LWAPP-3-CLIENTERRORLOG: Config flash load failed. Initialization of Cfg

* 00:00:15.631 Mar 1: % CAPWAP-3-Journal of ERROR: could not load the configuration of flash. Reset to the default configuration

* 00:00:16.671 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed to uplwapp_crypto_init: MIC present and analyzed successfully

No source of bridge-Group 1-learning

^

Invalid entry % detected at ' ^' marker.

% Without Gateway default route, if not an interface point, may affect performance

* 00:00:46.131 Mar 1: % CDP_PD-4-POWER_OK: all disabled radio - power INJECTOR_CONFIGURED_ON_SOURCE online source

* 00:00:49.411 Mar 1: DHCP-6-ADDRESS_ASSIGN %: BVI1 Interface assigned address DHCP 172.17.254.6, mask 255.255.255.0, hostname AP0006.f618.1d3b

Translate "CISCO-CAPWAP-CONTROLLER"... the domain server (172.17.254.1)

* 00:01:00.347 Mar 1: % CAPWAP-5-DHCP_OPTION_43: the 172.17.254.203 drive address obtained by DHCP

* 00:01:00.347 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.

* 00:01:09.347 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-CAPWAP-CONTROLLER

* 00:01:19.347 Mar 1: % 3-CAPWAP-ERRORLOG: go join a capwap controller

looking at the picture...

extracting information (283 bytes)

Image info:

Version suffix: k9w8-. 152 - 2.JB

Image name: ap1g2-k9w8 - mx.152 - 2.JB

The release directory: ap1g2-k9w8 - mx.152 - 2.JB

The iOS Image size: 9400832

Total image size: 9769472

Image device: Wireless LAN | LWAPP

Family pictures: AP1G2

Wireless switch management Version: 7.4.100.0

Extraction of the files...

AP1G2-k9w8-MX.152-2.JB/ (directory) 0 (bytes)

extraction of ap1g2-k9w8-mx.152-2.JB/K5.bin (75790 bytes)

* 14:10:57.000 20 Mar: % CA

extraction ap1g2-k9w8-mx.152-2.JB/S2.bin (9328 bytes)

extraction of ap1g2-k9w8-mx.152-2.JB/S5.bin (106106 byte) PWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246

* 14:10:57.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246

* 14:10:57.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203

* 14:10:57.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.

* 14:10:57.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.

* 14:10:57.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller

* 14:10:57.543 Mar 20: % CAPWAP-3-Journal of ERROR: could not process the encrypted package capwap 172.17.254.203perform archive download capwap: / ap1g2 tar file

* 14:10:57.547 Mar 20: % CAPWAP-6-AP_IMG_DWNLD: not found required image on AP. image controller download.

extraction ap1g2-k9w8-mx.152-2.JB/info (283 bytes)

AP1G2-k9w8-MX.152-2.JB/HTML/ (directory) 0 (bytes)

AP1G2-k9w8-MX.152-2.JB/HTML/level/ (directory) 0 (bytes)

AP1G2-k9w8-MX.152-2.JB/HTML/level/1/ (directory) 0 (bytes)

extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/forms.js (17492 bytes)

extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/appsui.js (563 bytes)

extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/ap_home.shtml.gz (1297 bytes)

AP1G2-k9w8-MX.152-2.JB/HTML/level/1/images/ (directory) 0 (bytes)

extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/images/info.gif (399 bytes)

extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/images/cisco-logo-2007.gif (1648 bytes)

extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/images/background_web41.jpg (732 bytes)

extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/images/login_homeap.gif (19671 bytes)

extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/config.js (25507 bytes)

extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/sitewide.js (16554 bytes)

extraction of ap1g2-k9w8-mx.152-2.JB/html/level/1/officeExtendap.css (41801 bytes)

extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/back.shtml (512 bytes)

AP1G2-k9w8-MX.152-2.JB/HTML/level/15/ (directory) 0 (bytes)

extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapBanner.htm (7114 bytes)

extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapConfig.shtml.gz (2864 bytes)

extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapSummary.htm (718 bytes)

extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapHelp.htm (5013 bytes)

extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapMain.shtml.gz (3350 bytes)

extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapEvent.shtml.gz (988 bytes)

extraction ap1g2-k9w8-mx.152-2.JB/K2.bin (5830 bytes)

extraction of ap1g2-k9w8-mx.152-2.JB/8005.img (200872 bytes)

extraction of ap1g2-k9w8-mx.152-2.JB/ap1g2-k9w8-mx.152-2.JB (9196955 bytes)

* 14:12:57.694 Mar 20: % 3-CAPWAP-ERRORLOG: white event 48 & combination State 10.

* 14:12:57.694 Mar 20: % 3-CAPWAP-ERRORLOG: SM Manager: failed to process the message of the timer. Event 48, State 10

* 14:12:57.694 Mar 20: % CAPWAP-3-Journal of ERRORS: do not handle the message from the timer.

* 14:12:57.694 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the message of the timer.

extraction info.ver (283 bytes)

Removal of target version: flash:/ap1g2-k9w8-mx.152-2.JB...done.

New image of the software installed in flash:/ap1g2-k9w8-mx.152-2.JB

System to use new IMA configuration

Flash event log entry: / event.log...

GE... done.

Download of archive: 212 seconds

* 14:14:28.389 Mar 20: upgrade successfully, the system image is now reloading

* 14:14:28.425 Mar 20: % SYS-5-RELOAD: reload requested by capwap image download proc. reload reason: NEW IMAGE DOWNLOAD.

* 14:14:28.425 Mar 20: % LWAPP-5-CHANGED: CAPWAP changed State to DOWN

Event.log written

Boot from flash

>>>>>>>>>>>>>>>>>>>>

WARNING: the checksum of compiling code doesn't seem to be present.

Radio0 presents 8764B 8000 0 A8000000 A8010000 0

Rate table has 180 entries (48 variations of BF IMS/72)

Radio1 present 8764B 8000 0 88000000 88010000 4

This product contains cryptographic features and is under the United States

memory checksum validate 30

^

Invalid entry % detected at ' ^' marker.

by default the authentication of connection

^

Invalid entry % detected at ' ^' marker.

>>>>>>>>>>>>>>>>>>>>

Press RETURN to get started!

* 00:00:11.995 Mar 1: % SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: crypto IOS FIPS self-test passed

* 00:00:14.451 Mar 1: % SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: crypto RADIO FIPS self-test passed on Dot11Radio interface 0

* 00:00:14.575 Mar 1: % LINK-6-UPDOWN: Interface GigabitEthernet0, changed State to

* 00:00:15.563 Mar 1: % SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: crypto RADIO FIPS self-test passed on 1 Dot11Radio interface

* 00:00:15.619 Mar 1: % LWAPP-3-CLIENTERRORLOG: Config flash load failed. Initialization of Cfg

* 00:00:18.283 Mar 1: % SYS-5-RESTART: System restarted.

Software Cisco IOS, C1600 Software (AP1G2-K9W8-M), Version 15.2 (2) JB, RELEASE SOFTWARE (fc1)

Technical support: http://www.cisco.com/techsupport

Copyright (c) 1986-2012 by Cisco Systems, Inc.

Updated Wednesday, December 11, 12 04:45 by prod_rel_team

* 00:00:18.283 Mar 1: % SNMP-5-start COLD: SNMP agent on host ap knows a cold start

* 00:00:18.339 Mar 1: % LWAPP-3-CLIENTERRORLOG: Config flash load failed. Initialization of Cfg

* 00:00:18.339 Mar 1: % CAPWAP-3-Journal of ERROR: could not load the configuration of flash. Reset to the default configuration

* 00:00:18.355 Mar 1: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

* 00:00:18.355 Mar 1: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset

* 00:00:18.819 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed State to

* 00:00:19.439 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed State to

* 00:00:21.699 Mar 1: % SSH-5-ACTIVATED: SSH 2.0 has been enabledlwapp_crypto_init: MIC present and analyzed successfully

% Without Gateway default route, if not an interface point, may affect performance

* 00:00:47.127 Mar 1: message logging LWAPP to 255.255.255.255.

* 00:00:52.059 Mar 1: % CDP_PD-4-POWER_OK: full power - supply line INJECTOR_CONFIGURED_ON_SOURCE

* 00:00:53.107 Mar 1: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 00:00:54.031 Mar 1: DHCP-6-ADDRESS_ASSIGN %: BVI1 Interface assigned address DHCP 172.17.254.7, mask 255.255.255.0, hostname AP0006.f618.1d3b

* 00:00:54.107 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 00:00:54.163 Mar 1: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 00:00:55.163 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to

Translate "CISCO-CAPWAP-CONTROLLER"... the domain server (172.17.254.1)

* 00:01:04.927 Mar 1: % CAPWAP-5-DHCP_OPTION_43: the 172.17.254.203 drive address obtained by DHCP

* 00:01:04.927 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.

* 00:01:13.927 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-CAPWAP-CONTROLLER

* 00:01:23.927 Mar 1: % 3-CAPWAP-ERRORLOG: go join a capwap controller

* 14:16:30.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246

* 14:16:30.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246

* 14:16:30.539 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203

* 14:16:30.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.

* 14:16:30.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.

* 14:16:30.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller

* 14:16:30.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap

* 14:16:49.211 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))

., 1)

* 14:16:49.211 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION

* 14:16:49.211 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246

* 14:16:49.267 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255

* 14:16:49.287 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

* 14:16:49.287 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively

* 14:16:49.303 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:16:49.343 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:16:50.287 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:16:50.335 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down

* 14:16:50.343 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset

* 14:16:51.327 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:16:51.335 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down

* 14:16:51.379 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:16:51.387 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down

* 14:16:51.395 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

* 14:16:52.379 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to

* 14:16:52.387 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:16:52.423 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:16:53.423 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:16:59.343 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller

* 14:16:59.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246

* 14:16:59.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246

* 14:16:59.539 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203

* 14:16:59.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.

* 14:16:59.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.

* 14:16:59.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller

* 14:16:59.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap

* 14:17:17.699 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))

., 1)

* 14:17:17.699 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION

* 14:17:17.699 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246

* 14:17:17.755 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255

* 14:17:17.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

* 14:17:17.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively

* 14:17:17.783 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:17:17.819 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:17:18.771 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:17:18.819 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down

* 14:17:18.827 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset

* 14:17:19.811 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:17:19.819 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down

* 14:17:19.863 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:17:19.871 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down

* 14:17:19.879 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

* 14:17:20.863 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to

* 14:17:20.871 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:17:20.907 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:17:21.907 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:17:27.819 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller

* 14:17:28.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246

* 14:17:28.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246

* 14:17:28.539 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203

* 14:17:28.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.

* 14:17:28.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.

* 14:17:28.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller

* 14:17:28.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap

* 14:17:47.203 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))

., 1)

* 14:17:47.203 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION

* 14:17:47.203 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246

* 14:17:47.259 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255

* 14:17:47.275 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

* 14:17:47.275 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively

* 14:17:47.287 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:17:47.323 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:17:48.275 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:17:48.323 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down

* 14:17:48.331 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset

* 14:17:49.315 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:17:49.323 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down

* 14:17:49.367 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:17:49.375 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down

* 14:17:49.383 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

* 14:17:50.367 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to

* 14:17:50.375 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:17:50.411 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:17:51.411 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:17:57.323 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller

* 14:17:57.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246

* 14:17:57.543 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246

* 14:17:57.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203

* 14:17:57.547 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.

* 14:17:57.547 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.

* 14:17:57.547 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller

* 14:17:57.547 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap

* 14:18:15.699 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))

., 1)

* 14:18:15.699 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION

* 14:18:15.699 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246

* 14:18:15.755 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255

* 14:18:15.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

* 14:18:15.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively

* 14:18:15.799 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:18:15.831 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:18:16.771 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:18:16.835 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down

* 14:18:16.843 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset

* 14:18:17.827 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:18:17.835 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down

* 14:18:17.879 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:18:17.887 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down

* 14:18:17.895 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

* 14:18:18.879 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to

* 14:18:18.887 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:18:18.923 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:18:19.923 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:18:25.831 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller

* 14:18:26.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246

* 14:18:26.543 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246

* 14:18:26.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203

* 14:18:26.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.

* 14:18:26.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.

* 14:18:26.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller

* 14:18:26.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap

* 14:18:44.699 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))

., 1)

* 14:18:44.699 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION

* 14:18:44.699 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246

* 14:18:45.163 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255

* 14:18:45.183 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

* 14:18:45.183 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively

* 14:18:45.195 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:18:45.227 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:18:46.183 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:18:46.231 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down

* 14:18:46.239 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset

* 14:18:47.223 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:18:47.231 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down

* 14:18:47.275 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:18:47.283 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down

* 14:18:47.291 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

* 14:18:48.275 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to

* 14:18:48.283 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:18:48.319 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:18:49.319 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:18:55.227 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller

* 14:18:55.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246

* 14:18:55.543 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246

* 14:18:55.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203

* 14:18:55.547 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.

* 14:18:55.547 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.

* 14:18:55.547 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller

* 14:18:55.547 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap

* 14:19:13.695 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))

., 1)

* 14:19:13.695 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION

* 14:19:13.695 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246

* 14:19:13.751 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255

* 14:19:13.767 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

* 14:19:13.767 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively

* 14:19:13.783 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:19:13.815 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:19:14.767 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:19:14.827 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down

* 14:19:14.835 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset

* 14:19:15.819 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:19:15.827 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down

* 14:19:15.871 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:19:15.879 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down

* 14:19:15.887 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

* 14:19:16.871 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to

* 14:19:16.879 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:19:16.915 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:19:17.915 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:19:23.815 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller

* 14:19:24.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246

* 14:19:24.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246

* 14:19:24.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203

* 14:19:24.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.

* 14:19:24.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.

* 14:19:24.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller

* 14:19:24.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap

* 14:19:42.695 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))

., 1)

* 14:19:42.695 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION

* 14:19:42.695 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246

* 14:19:42.751 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255

* 14:19:42.767 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

* 14:19:42.767 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively

* 14:19:42.783 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:19:42.815 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:19:43.767 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:19:43.815 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down

* 14:19:43.823 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset

* 14:19:44.807 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:19:44.815 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down

* 14:19:44.859 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:19:44.867 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down

* 14:19:44.875 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

* 14:19:45.859 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to

* 14:19:45.867 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:19:45.903 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:19:46.903 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:19:52.815 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller

* 14:19:53.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246

* 14:19:53.543 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246

* 14:19:53.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203

* 14:19:53.547 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.

* 14:19:53.547 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.

* 14:19:53.547 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller

* 14:19:53.547 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap

* 14:20:12.111 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))

., 1)

* 14:20:12.111 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION

* 14:20:12.111 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246

* 14:20:12.167 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255

* 14:20:12.183 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

* 14:20:12.183 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively

* 14:20:12.199 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:20:12.231 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:20:13.183 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:20:13.235 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down

* 14:20:13.243 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset

* 14:20:14.227 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:20:14.235 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down

* 14:20:14.279 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:20:14.287 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down

* 14:20:14.295 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

* 14:20:15.279 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to

* 14:20:15.287 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:20:15.323 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:20:16.323 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:20:22.231 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller

* 14:20:22.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246

* 14:20:22.543 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246

* 14:20:22.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203

* 14:20:22.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.

* 14:20:22.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.

* 14:20:22.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller

* 14:20:22.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap

* 14:20:40.699 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))

., 1)

* 14:20:40.699 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION

* 14:20:40.699 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246

* 14:20:40.755 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255

* 14:20:40.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

* 14:20:40.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively

* 14:20:40.787 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:20:40.819 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:20:41.771 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:20:41.819 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down

* 14:20:41.827 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset

* 14:20:42.811 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:20:42.819 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down

* 14:20:42.863 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:20:42.871 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down

* 14:20:42.879 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

* 14:20:43.863 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to

* 14:20:43.871 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:20:43.907 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:20:44.907 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:20:50.819 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller

* 14:20:51.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246

* 14:20:51.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246

* 14:20:51.539 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203

* 14:20:51.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.

* 14:20:51.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.

* 14:20:51.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller

* 14:20:51.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap

* 14:21:10.107 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))

., 1)

* 14:21:10.107 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION

* 14:21:10.107 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246

* 14:21:10.163 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255

* 14:21:10.179 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

* 14:21:10.179 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively

* 14:21:10.191 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:21:10.227 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:21:11.179 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:21:11.227 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down

* 14:21:11.235 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset

* 14:21:12.219 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:21:12.227 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down

* 14:21:12.271 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to

* 14:21:12.279 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down

* 14:21:12.287 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

* 14:21:13.271 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to

* 14:21:13.279 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

* 14:21:13.315 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to

* 14:21:14.315 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

* 14:21:20.227 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller

* 14:21:20.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246

* 14:21:20.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246

* 14:21:20.539 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203

* 14:21:20.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.

* 14:21:20.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.

* 14:21:20.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller

* 14:21:20.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap

[END] 20.03.2013 14:21:55

Azim,

I wonder if the regulatory domain of the AP is correct.

Please provide the result following (authorization according to Leo)

1 WLC: sh sysinfo

2 PA: sh version

3 PA: HS inventory

Thank you.

Amjad

Rating of useful answers is more useful to say "thank you".

WLC 5508 high availability

Hello

Today I have two WLC 5508 (with license for 100 AP each of them), on a single site.

The WLC work availability (active-standby).

However, we have a new scenario, with 02 sites: A and B (attachment).

I would like to know if it is possible to work as follows:

The WLC - A as the main controller of site A. WLC - B as a backup (BDC) of WLC.-a.

The WLC - B that has the PDC site B. WLC - as a backup (BDC) to WLC - B.

For example:

If WLC - a falls, site access Points are managed by B WLC site - B and vice versa.

Is this possible?

How can I configure the new scenario? Don't forget, there is a site-to-site between Site A and Site b.

Another point:

If I add more than 50 APs on Site A. How does the license number?

Should I buy a license for the two WLC?

TKS,

>....

>.. .is it possible?

No. , high availability in terms of controller is supposed to be what is said, the backup controller is not 'full' - stby and cannot play other roles.

M.

How to connect wlc 5508 on 2 switches for redundancy

Hi, I'm planning implementation of WLC5508, but in the documentation is not clear how to connect WLC5508 to two chassis for redundancy. I do it with WLC4404, where I have the opportunity to choose the primary and secondary port for the management interface. I understand that in 5508 management interface is not mapped to any port.

You can always set the primary/secondary ports as long as you have not enabled lag. If you try to use two different switches so you should not LAG have enabled anyway (unless it is a battery 3750 or vss)

You can always set several AP-managers as well. By default, the management interface is an ap - manager, but he will not be an ap-Manager on the port of relief if you have a defined ap-Manager for the port... Make sense?

Just think of the 5508 ports defined as a 4400, except that you don't have to have a Manager AP for each port, unless you want a...

WLC 5508 Active Directory / LDAP integration to authenticate

Hello

I am redundant deployment WLC 5508 with 4 VLANS and 4 SSID matches it, everything works fine, now I have to do the below, then please put your valuable comments and advice.

1. I need all users authenticated with existing Active Directory/LDAP wireless

2. I create accounts invited in my ad and go to the guests, so comments should only Internet access except the company's resources

2. How can I get my VoIP VLAN for wireless phones. I want to only wireless phones to connect to VLANS voice. No internet access on VLan VoIP

Concerning

Dinesh

Hello

1. I need all users authenticated with existing Active Directory/LDAP wireless

2. I create accounts invited in my ad and go to the guests, so comments should only Internet access except the company's resources

YEARS 1 & 2 - the link below provides the example config and also the memorandum of understanding on the conditions depth, please go through the link atleast once...

http://www.Cisco.com/en/us/products/ps6366/products_configuration_example09186a0080a03e09.shtml

2. How can I get my VoIP VLAN for wireless phones. I want to only wireless phones to connect to VLANS voice. No internet access on VLan VoIP

YEARS - you can configure the auth required for WLAN voice and then NAT this interface VLAN so that he won't get out of the internet!

Let me know if that answers your question and please do not forget to rate traore useful messages!

Concerning

Surendra

WLC 5508

Hi all

who knows how many users can manage with WLC 5508?

Can the finally user change his or her password at the first loging or later?

Thank you

Hello

change of password is a feature that you need to search on the authentication server (radius). The radius server that resides on the WLC is all the features that ACS can have for example.

The 5508 supports up to 500 access points. The customer table is limited, I think, about 7,000 customers (it's 4000 for the 4404).

Nicolas

Trouble getting a Cisco 2600 series AP to stay connected to WLC 5508

Hello

I recently loaded the independent our old APs upgrade to LWAPs. We have a WLC 5508 to our Virtual Co - Lo and I use Flexconnect to accommodate local switch and dhcp on our sites. I have updated more than 50 APs and joined them to the controller. These include only the 1130AG and 1240AG models. However they work perfectly and stay connected to the controller. I'm having is with a new batch of 2600 series APs stay connected to the controller. I tried to do research in what may cause disconnect it but have yet to find a solution. I use DNS to resolve queries for CAPWAP & LWAPP APs to the controller on our EXTENSIVE network. Read other messages I thought that this is perhaps a problem with packages to drop but have had our provider that manages Sonicwalls at both ends of the WAN confirm for me that there is no packet loss. Here are the logs that I collected through the puttty of the WLC & AP. Any help would be greatly appreciated.

AP, I do the test on:

NAME: "AP2600', DESCR: 'Cisco Aironet 2600 Series (IEEE 802.11n) Access Point.

PID: AIR-CAP2602I-A-K9, VID: V01, SN: FTX1740J8V1

WLC in question:

Name of the manufacturer... Cisco Systems Inc..

Product name... Cisco controller

Version of the product... 7.3.112.0

Bootloader Version... 1.0.1

Retrieving Image Version field... 6.0.182.0

Firmware version... Console USB 1.3, 1.6 Env FPGA, 1.27

Build Type....................................... DATA + WPS

System name... wificontroller

Location of the system... Corp

Contact System... Net engineer

ObjectID of system... 1.3.6.1.4.1.9.1.1069

Redundancy mode... People with disabilities

IP Address....................................... 10.250.32.8

Last Reset....................................... Software reset

Time system... 190 days 3 hours 34 minutes 24 seconds

Location of the time zone of the system... (GMT - 5:00) Eastern (USA and Canada)

The country is set... USA - United States

Operating environment... Utilities (0 to 40 ° C)

Limits the internal temperature alarm... 0 to 65 ° C

-Other - or ITU (q)

... Internal temperature 38 C

Outdoor temperature... + 20 C

Fan Status....................................... Ok

State of 802. 11 b network... Activated

State of 802. 11A network... Activated

Number of wireless LANs... 14

Number of Active Clients... 71

Built-in MAC address... C8:9 C: D: 8 1: 52:E0

Power supply 1... Currently, OK

Power supply 2... Absent

Maximum number of taken access points supported... 100

Here is the result which leaves on concluded that the AP joins the WLC for a short period and then goes offline

WT-4thFlr-AP3 #.

* 15:42:04.419 Dec 14: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (CAPWAP_WTP_EVENT_REQUEST

., 3)

* 15:42:11.443 Dec 14: EVT-4-AVT %: write flash: / done event.capwap

* 15:42:11.483 Dec 14: LWAPP-3-CLIENTERRORLOG %: switch to standalone mode

* 15:42:11.487 Dec 14: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION

* 15:42:11.487 Dec 14: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 10.250.32.8:5246

* 15:42:11.571 Dec 14: % FEDS-6-persons with DISABILITIES: Signature of IDS is removed and disabled.

* 15:42:21.575 Dec 14: % 3-CAPWAP-ERRORLOG: MWAR selected ' wificontroller'(index 0).

* 15:42:21.575 Dec 14: % 3-CAPWAP-ERRORLOG: go join a capwap controller

* 15:42:12.000 Dec 14: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.250.32.8 peer_port: 5246

* 15:42:14.303 Dec 14: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.250.32.8 peer_port: 5246

* 15:42:14.303 Dec 14: % CAPWAP-5-SENDJOIN: send request to join 10.250.32.8

* 15:42:15.127 Dec 14: "Promiscuous" from Ethernet mode

* 15:42:15.535 Dec 14: LWAPP-4-CLIENTEVENTLOG %: OfficeExtend Localssid recorded Flash AP

* 15:42:15.667 Dec 14: ac_first_hop_mac - IP:10.1.2.250 Hop IP:10.1.2.250 IDB:BVI1

* 15:42:15.667 Dec 14: AC setting hop first MAC: 0017.c575.a23c

* 15:42:15.855 Dec 14: % CAPWAP-5-JOINEDCONTROLLER: AP joined controller wificontroller

* 15:42:15.911 Dec 14: LWAPP-4-CLIENTEVENTLOG %: No. Flex ACL to load map configuration file. To connect to the controller to get the configuration file

* 15:42:15.911 Dec 14: LWAPP-4-CLIENTEVENTLOG %: No. Flex ACL to load map configuration file. To connect to the controller to get the configuration file

* 15:42:15.911 Dec 14: LWAPP-4-CLIENTEVENTLOG %: map No. LS Flex to load ACL configuration file. To connect to the controller to get the configuration file

* 15:42:15.915 Dec 14: LWAPP-4-CLIENTEVENTLOG %: no central Dhcp configuration file map to load. To connect to the controller to get the configuration file

* 15:42:15.915 Dec 14: % LWAPP-3-CLIENTERRORLOG: connected mode

* 15:42:23.639 Dec 14: FEDS-6-ACTIVATED %: Signature of IDS is loaded and enabled

* 15:42:34.615 Dec 14: CLEANAIR-6-State: Slot 0 disabled

* 15:42:34.615 Dec 14: CLEANAIR-6-State: Slot 1 disabled

* 15:45:43.783 Dec 14: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (CAPWAP_WTP_EVENT_REQUEST

(. 11).

* 15:45:43.787 Dec 14: LWAPP-3-CLIENTERRORLOG %: switch to standalone mode

* 15:45:43.787 Dec 14: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION

* 15:45:43.787 Dec 14: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 10.250.32.8:5246

* 15:45:43.867 Dec 14: % FEDS-6-persons with DISABILITIES: Signature of IDS is removed and disabled.

* 15:45:53.867 Dec 14: % 3-CAPWAP-ERRORLOG: MWAR selected ' wificontroller'(index 0).

* 15:45:53.867 Dec 14: % 3-CAPWAP-ERRORLOG: go join a capwap controller

* 15:45:44.000 Dec 14: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.250.32.8 peer_port: 5246

* 15:45:46.315 Dec 14: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.250.32.8 peer_port: 5246

* 15:45:46.315 Dec 14: % CAPWAP-5-SENDJOIN: send request to join 10.250.32.8

* 15:45:46.487 Dec 14: "Promiscuous" from Ethernet mode

* 15:45:49.903 Dec 14: LWAPP-4-CLIENTEVENTLOG %: OfficeExtend Localssid recorded Flash AP

* 15:45:50.031 Dec 14: ac_first_hop_mac - IP:10.1.2.250 Hop IP:10.1.2.250 IDB:BVI1

* 15:45:50.031 Dec 14: AC setting hop first MAC: 0017.c575.a23c

Here are the results of the client debugging capwap event about to access:

WT-4thFlr-AP3 #debug capwap customer event

Display debugging EVENT customer CAPWAP is on

WT-4thFlr-AP3 #.

* 15:54:58.335 Dec 14: % 3-CAPWAP-EVENTLOG: Echo interval has expired.

* 15:54:58.335 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

* 15:54:58.335 Dec 14: % 3-CAPWAP-EVENTLOG: echo sent to 10.250.32.8 request

* 15:54:58.343 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

* 15:54:58.343 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

* 15:54:58.343 Dec 14: % 3-CAPWAP-EVENTLOG: echo response from 10.250.32.8

* 15:55:08.000 Dec 14: % 3-CAPWAP-EVENTLOG: setting the time at 15:55:08 UTC 14 December 2013

* 15:55:25.579 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

* 15:55:25.587 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

* 15:55:25.587 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

* 15:55:25.587 Dec 14: % CAPWAP-3-Journal of EVENTS: event Wtp 10.250.32.8 response

* 15:55:25.827 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

* 15:55:25.835 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

* 15:55:25.835 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

* 15:55:25.835 Dec 14: % CAPWAP-3-Journal of EVENTS: event Wtp 10.250.32.8 response

* 15:55:55.835 Dec 14: % 3-CAPWAP-EVENTLOG: Echo interval has expired.

* 15:55:55.835 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

* 15:55:55.835 Dec 14: % 3-CAPWAP-EVENTLOG: echo sent to 10.250.32.8 request

* 15:55:55.843 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

* 15:55:55.843 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

* 15:55:55.843 Dec 14: % 3-CAPWAP-EVENTLOG: echo response from 10.250.32.8

* 15:55:56.000 Dec 14: % 3-CAPWAP-EVENTLOG: setting the time at 15:55:56 UTC 14 December 2013

* 15:56:25.735 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

* 15:56:25.743 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

* 15:56:25.743 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

* 15:56:25.743 Dec 14: % CAPWAP-3-Journal of EVENTS: event Wtp 10.250.32.8 response

* 15:56:25.983 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

* 15:56:25.991 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

* 15:56:25.991 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

* 15:56:25.991 Dec 14: % CAPWAP-3-Journal of EVENTS: event Wtp 10.250.32.8 response

* 15:56:55.991 Dec 14: % 3-CAPWAP-EVENTLOG: Echo interval has expired.

* 15:56:55.991 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

* 15:56:55.991 Dec 14: % 3-CAPWAP-EVENTLOG: echo sent to 10.250.32.8 request

* 15:56:55.999 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

* 15:56:55.999 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

* 15:56:55.999 Dec 14: % 3-CAPWAP-EVENTLOG: echo response from 10.250.32.8

* 15:56:56.000 Dec 14: % 3-CAPWAP-EVENTLOG: setting the time at 15:56:56 UTC 14 December 2013

Here are the results of debug capwap client package in detail:

WT-4thFlr-AP3 #.

* 14 Dec 15:59:01.823: <   start="" of="" capwap="" packet ="">>

* 15:59:01.823 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

* 15:59:01.823 Dec 14: Type Msg: CAPWAP_ECHO_REQUEST

* 15:59:01.823 Dec 14: Msg length: 0

* 15:59:01.823 Dec 14: Msg SeqNum: 44

* 14 Dec 15:59:01.823: < end="" of="" capwap="" packet ="">>

* 14 Dec 15:59:01.831: <   start="" of="" capwap="" packet ="">>

* 15:59:01.831 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

* 15:59:01.831 Dec 14: HLEN 2, Radio ID 0, WBID 1

* 15:59:01.831 Dec 14: Type Msg: CAPWAP_ECHO_RESPONSE

* 15:59:01.831 Dec 14: Msg length: 15

* 15:59:01.831 Dec 14: Msg SeqNum: 44

* 15:59:01.831 Dec 14:

* 15:59:01.831 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 11

* 15:59:01.831 Dec 14: the vendor identifier: 0 x 00409600

* 15:59:01.831 Dec 14:

* 15:59:01.831 Dec 14:

IE: UNKNOWN IT IS ABOUT 151

* 15:59:01.831 Dec 14: IE length: 5

* 15:59:01.831 Dec 14: decode the routine unavailable, Hex Dump printing

* 15:59:01.831 Dec 14:

52 80 46 00 AC

* 14 Dec 15:59:01.831: < end="" of="" capwap="" packet ="">>

* 14 Dec 15:59:20.931: <   start="" of="" capwap="" packet ="">>

* 15:59:20.931 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

* 15:59:20.931 Dec 14: HLEN 2, Radio ID 0, WBID 1

* 15:59:20.931 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_REQUEST

* 15:59:20.931 Dec 14: Msg length: 93

* 15:59:20.931 Dec 14: Msg SeqNum: 38

* 15:59:20.931 Dec 14:

* 15:59:20.931 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 89

* 15:59:20.931 Dec 14: the vendor identifier: 0 x 00409600

* 15:59:20.931 Dec 14:

* 15:59:20.931 Dec 14:

IE: RRM_NEIGHBOR_CTRL_PAYLOAD

* 15:59:20.931 Dec 14: IE length: 83

* 15:59:20.931 Dec 14: decode the routine unavailable, Hex Dump printing

* 15:59:20.931 Dec 14:

00 0 HAS FA 20 08 01 00 07 0A 20 08 03 00 01 FA F4

01 00 00 3 B4 2ND 2ND 06 94 51 79 25 C7 B2 B4 E7

22 FD BE F6 04 00 00 00 00 00 00 00 00 50 52 4F

53 2D 57 69 46 69 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 01 06 0B

01 01 01

* 14 Dec 15:59:20.931: < end="" of="" capwap="" packet ="">>

* 14 Dec 15:59:20.931: <   start="" of="" capwap="" packet ="">>

* 15:59:20.931 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

* 15:59:20.931 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_RESPONSE

* 15:59:20.931 Dec 14: Msg length: 8

* 15:59:20.931 Dec 14: Msg SeqNum: 38

* 15:59:20.931 Dec 14:

* 15:59:20.931 Dec 14: Type: CAPWAP_MSGELE_RESULT_CODE, length 4

* 15:59:20.931 Dec 14: result of Code: CAPWAP_SUCCESS

* 14 Dec 15:59:20.931: < end="" of="" capwap="" packet ="">>

* 14 Dec 15:59:21.139: <   start="" of="" capwap="" packet ="">>

* 15:59:21.139 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

* 15:59:21.139 Dec 14: HLEN 2, Radio ID 0, WBID 1

* 15:59:21.139 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_REQUEST

* 15:59:21.139 Dec 14: Msg length: 111

* 15:59:21.139 Dec 14: Msg SeqNum: 39

* 15:59:21.139 Dec 14:

* 15:59:21.139 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 107

* 15:59:21.139 Dec 14: the vendor identifier: 0 x 00409600

* 15:59:21.139 Dec 14:

* 15:59:21.139 Dec 14:

IE: RRM_NEIGHBOR_CTRL_PAYLOAD

* 15:59:21.139 Dec 14: IE length: 101

* 15:59:21.139 Dec 14: decode the routine unavailable, Hex Dump printing

* 15:59:21.143 Dec 14:

01 0 TO FA 20 08 01 F4 00 07 0A 20 08 00 01 0C FA

01 00 00 3 B4 2ND 2ND 06 94 51 79 25 C7 B2 B4 E7

22 FD BE F6 04 00 00 00 00 00 00 00 00 50 52 4F

53 2D 57 69 46 69 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 24 28 2

30 34 38 3 40 95 99 9 01 01 01 01 01 01 01 A1

01 01 01 01 01

* 14 Dec 15:59:21.143: < end="" of="" capwap="" packet ="">>

* 14 Dec 15:59:21.143: <   start="" of="" capwap="" packet ="">>

* 15:59:21.143 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

* 15:59:21.143 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_RESPONSE

* 15:59:21.143 Dec 14: Msg length: 8

* 15:59:21.143 Dec 14: Msg SeqNum: 39

* 15:59:21.143 Dec 14:

* 15:59:21.143 Dec 14: Type: CAPWAP_MSGELE_RESULT_CODE, length 4

* 15:59:21.143 Dec 14: result of Code: CAPWAP_SUCCESS

* 14 Dec 15:59:21.143: < end="" of="" capwap="" packet ="">>

* 14 Dec 15:59:25.547: <   start="" of="" capwap="" packet ="">>

* 15:59:25.547 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

* 15:59:25.547 Dec 14: Type Msg: CAPWAP_WTP_EVENT_REQUEST

* 15:59:25.547 Dec 14: Msg length: 14

* 15:59:25.547 Dec 14: Msg SeqNum: 45

* 15:59:25.547 Dec 14:

* 15:59:25.547 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 10

* 15:59:25.547 Dec 14: the vendor identifier: 0 x 00409600

* 15:59:25.547 Dec 14:

* 15:59:25.547 Dec 14:

IE: RRM_LOAD_DATA_PAYLOAD

* 15:59:25.547 Dec 14: IE length: 4

* 14 Dec 15:59:25.547: slot ccaLoad 0 rxLoad 0 txLoad 0 33

* 14 Dec 15:59:25.547: < end="" of="" capwap="" packet ="">>

* 14 Dec 15:59:25.555: <   start="" of="" capwap="" packet ="">>

* 15:59:25.555 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

* 15:59:25.555 Dec 14: HLEN 2, Radio ID 0, WBID 1

* 15:59:25.555 Dec 14: Type Msg: CAPWAP_WTP_EVENT_RESPONSE

* 15:59:25.555 Dec 14: Msg length: 0

* 15:59:25.555 Dec 14: Msg SeqNum: 45

* 14 Dec 15:59:25.555: < end="" of="" capwap="" packet ="">>

* 14 Dec 15:59:25.795: <   start="" of="" capwap="" packet ="">>

* 15:59:25.795 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

* 15:59:25.795 Dec 14: Type Msg: CAPWAP_WTP_EVENT_REQUEST

* 15:59:25.795 Dec 14: Msg length: 14

* 15:59:25.795 Dec 14: Msg SeqNum: 46

* 15:59:25.795 Dec 14:

* 15:59:25.795 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 10

* 15:59:25.795 Dec 14: the vendor identifier: 0 x 00409600

* 15:59:25.795 Dec 14:

* 15:59:25.795 Dec 14:

IE: RRM_LOAD_DATA_PAYLOAD

* 15:59:25.795 Dec 14: IE length: 4

* 14 Dec 15:59:25.795: slot ccaLoad 1 rxLoad 0 txLoad 0 0

* 14 Dec 15:59:25.795: < end="" of="" capwap="" packet ="">>

* 14 Dec 15:59:25.803: <   start="" of="" capwap="" packet ="">>

* 15:59:25.803 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

* 15:59:25.803 Dec 14: HLEN 2, Radio ID 0, WBID 1

* 15:59:25.803 Dec 14: Type Msg: CAPWAP_WTP_EVENT_RESPONSE

* 15:59:25.803 Dec 14: Msg length: 0

* 15:59:25.803 Dec 14: Msg SeqNum: 46

* 14 Dec 15:59:25.803: < end="" of="" capwap="" packet ="">>

* 14 Dec 15:59:30.375: <   start="" of="" capwap="" packet ="">>

* 15:59:30.375 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

* 15:59:30.375 Dec 14: HLEN 2, Radio ID 0, WBID 1

* 15:59:30.375 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_REQUEST

* 15:59:30.375 Dec 14: Msg length: 17

* 15:59:30.375 Dec 14: Msg SeqNum: 40

* 15:59:30.375 Dec 14:

* 15:59:30.375 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 13

* 15:59:30.375 Dec 14: the vendor identifier: 0 x 00409600

SlotId: 0

Mobile Mac Addr: BC:52:B7:E3:17:CB

* 14 Dec 15:59:30.375: < end="" of="" capwap="" packet ="">>

* 14 Dec 15:59:30.375: <   start="" of="" capwap="" packet ="">>

* 15:59:30.375 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

* 15:59:30.375 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_RESPONSE

* 15:59:30.379 Dec 14: Msg length: 8

* 15:59:30.379 Dec 14: Msg SeqNum: 40

* 15:59:30.379 Dec 14:

* 15:59:30.379 Dec 14: Type: CAPWAP_MSGELE_RESULT_CODE, length 4

* 15:59:30.379 Dec 14: result of Code: CAPWAP_SUCCESS

* 14 Dec 15:59:30.379: < end="" of="" capwap="" packet ="">>

* 14 Dec 15:59:30.387: <   start="" of="" capwap="" packet ="">>

* 15:59:30.387 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

* 15:59:30.387 Dec 14: HLEN 2, Radio ID 0, WBID 1

* 15:59:30.387 Dec 14: Type Msg: CAPWAP_WTP_EVENT_RESPONSE

* 15:59:30.387 Dec 14: Msg length: 0

* 15:59:30.387 Dec 14: Msg SeqNum: 47

* 14 Dec 15:59:30.387: < end="" of="" capwap="" packet ="">>

* 14 Dec 16:00:00.387: <   start="" of="" capwap="" packet ="">>

* 16:00:00.387 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

* 16:00:00.387 Dec 14: Type Msg: CAPWAP_ECHO_REQUEST

* 16:00:00.387 Dec 14: Msg length: 0

* 16:00:00.387 Dec 14: Msg SeqNum: 48

* 14 Dec 16:00:00.387: < end="" of="" capwap="" packet ="">>

* 14 Dec 16:00:00.395: <   start="" of="" capwap="" packet ="">>

* 16:00:00.395 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

* 16:00:00.395 Dec 14: HLEN 2, Radio ID 0, WBID 1

* 16:00:00.395 Dec 14: Type Msg: CAPWAP_ECHO_RESPONSE

* 16:00:00.395 Dec 14: Msg length: 15

* 16:00:00.395 Dec 14: Msg SeqNum: 48

* 16:00:00.395 Dec 14:

* 16:00:00.395 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 11

* 16:00:00.395 Dec 14: the vendor identifier: 0 x 00409600

* 16:00:00.395 Dec 14:

* 16:00:00.395 Dec 14:

IE: UNKNOWN IT IS ABOUT 151

* 16:00:00.395 Dec 14: IE length: 5

* 16:00:00.395 Dec 14: decode the routine unavailable, Hex Dump printing

* 16:00:00.395 Dec 14:

52 80 81 00 AC

* 14 Dec 16:00:00.395: < end="" of="" capwap="" packet ="">>

Try reducing the mtu on ap 2600.

WLC 5508 joined connected vs status

Hello

What is the difference between the status of 'Joint' and 'Connected' AP on the controller of Cisco 5508 wireless in HA configuration?

I have two WLC 5508 in HA configuration. October 3 the controller switchovered with reason "Active controller failed" (attached file 1). I tried to understand why the controller has failed, but I did not find the reason.

Now, there are a lot of AP (not all) in the 'connected' State, not 'Supported in status' (attached file 2).

What is the meaning? and why in the details ' AP join stats ' (attachment 3 and 4) tha AP are well attached status? It's a licensing issue? I can solve this problem with a manual failover to main controller?

Thank you for the help

You have a license for 250 AP on your primary controller and the secondary is a SKU or has at least 50 AP license to act like a HA.

As long as the main unit is available for the secondary unit (active) it will not perform the countdown. 90 days don't apply if the main unit is unavailable for more than 90 days in a row. If the secondary image (active) loses power and the principal is unavailable when it starts again, it will go into maintenance mode.

Please rate helpful messages... :-)

Wireless converged access (new) Mobiliity between WLC 5508

Hello

I have 3 WLC 5508 which is upgraded to version 8.x and I can see this feature when searching on the web I find that this new feature is necessary when we have new models of WLC 5760 or 3850 in the network and must contact 5508.

So my question is in my current scenario, I only 5508

1. can I activate this function and use this function between 5508 - If Yes, in the configuration, I just create mobility than in the old configuration groups and it should work right or is there additional configuration is required?

Also in my network current fflexconnect is activated and allow this will affect my flexconnect?

Please notify.

Kind regards

Anjaz

If you want to, you can migrate to the new mobility without any problem, but must be allowed to all of your WLC at the same time. This will have no impact for your flex-connect communication or configuration and influence the way in which the tunnels between of WLC are under construction. No changes are necessary in this configuration either.

Please rate helpful messages... :-)

SHIFT of Mode on Cisco WLC 5508

Hello

I have two WLC 5508 working in ACTIVE / standby. They are connected to my local network by linking to each WLC.

I would like to implement the LAG Mode to have two WLC link but when I activate LAG Mode (Mode CONTROLLER/general/LAG at the next reboot active), I have this newspaper:

"Error in the setting of the Mode of LAG. Please see the log file.

I see nothing in the log file.

The version of my WLC is 8.0.100.0

Thank you

First, you will need to disable HA if you want to enable the LAG.

http://www.Cisco.com/c/en/us/TD/docs/wireless/controller/8-0/Configuration-Guide/b_cg80/b_cg80_chapter_010100001.html

A time LAG configured on both controllers, you can then enable HA between two WLCs

HTH

Rasika

Pls note all useful responses *.

STROKE (Application Visibilty Control) on WLC 5508 7.5 do not display data

Dear all

My WLC has problem...

the STROKE is not display data (graphic or otherwise)

I have already set up two Wlan id with the visibility control, but two of them do not display data...

Here is my setup place WLC 5508...

My WLC running on OS 7.5

pack 1.0 protocol version

NBAR engine 13.0

AUS 6.0.182.0

Cisco controller) > see the version of the Protocol-pack stroke

Protocol STROKE Pack name: Protocol Advanced Pack

Protocol STROKE Pack Version: 1.0

(Cisco Controller) > show stroke engine version

Version of the engine STROKE: 13

(Cisco Controller) > show sysinfo

Name of the manufacturer... Cisco Systems Inc..

Product name... Cisco controller

Version of the product... 7.5.102.0

Bootloader Version... 1.0.1

Retrieving Image Version field... 6.0.182.0

Firmware version... Console USB 1.3, 1.6 Env FPGA, 1.27

even from CLI still do not display data

(Cisco Controller) >Show stroke statistics upstream applications top

Perspective of the STROKE is 0 for all applications.

MISTLETOE on attachment configuration capture

Need your advice is there any configuration that I miss... ??

As long as you go to the STROKE centre should work in Flexconnect. You can check the AP mode under wireless > click on any access point.

http://www.Cisco.com/c/en/us/support/docs/wireless/5500-Series-Wireless-...

Cisco ISE 2.0 and WLC 5508 with 7.6.130.0

I have looked on the release notes and compatibility n for ISE 2.0 and have not seen the answer to that. For the WLC 5508, the minimum AirOS is 7.0.116.0 but he limited the AAA authentication and support for comments. The recommended version of AirOS is 8.0.121.0.

http://www.Cisco.com/c/en/us/TD/docs/security/ISE/2-0/compatibility/ISE _...

What airos 7.6.130.0? I know that AirOS release works with 1.3 and 1.4, even if they show the same support for version 2.0. I'm just afraid that something may have changed with 2.0. I am concerned only about the AAA authentication and guest access. No BYOD, posture or MDM is necessary.

No change. Works well.

Backup the IOS on a WLC 5508

Hello

Hope someone can help me, I have a Cisco 5508 WLC and wanted to backup the IOS.

Is there an easy way to do it? or a Cisco restrict this function with the new IOS licensing model?

Second question, with WLC 5508 IOS version 7.0.98 I see that there is no field recovery Image, is that correct?

See you soon,.

Ron

I guess that you Q #1 has been addressed above.

For your Q n ° 2 'the second question, with WLC 5508 IOS version 7.0.98 I see that there is no field recovery Image, is this correct?"

Yes that is correct

-->

(w-5508-1) > show sysinfo

Name of the manufacturer... Cisco Systems Inc..
Product name... Cisco controller
Version of the product... 7.0.98.0
Bootloader Version... 1.0.1
Retrieving Image Version field... N/A

And it's a CSCth43373 bug

5508 7.0 running shows the version of field recovery images by n/a
```
Symptom:

5508 shows Field Recovery Image version as N/A.
Conditions:
Upgrade 5508 to version 7.0.98.0
Workaround:
None
```
--

You will have to wait for the new 7.0 code to appear on Cisco.com

Be sure to mark the thread as solved if you feel that your issue has been addressed.

Thank you

Serge

Interface WLC 5508 AP-Manager

Similar Questions

Maybe you are looking for