WLC 5508 without https web passthrough

Is there a way to not require a certificate and https for web passthrough this way when customers are redirected they do not get the certificate error?

Just disable HTTPS and SSH on the WLC and reload the WLC.

in this way, you should get the web passthrought as http only.

Tags: Cisco Wireless

Similar Questions

  • 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... :-)

  • 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 w / 1042-initial Setup Question

    I have to do an installation from scratch and was looking for some suggestions as a basis for the configuration. I have a 5508 I have to belay 6509.

    I have to get up 16-1042 model APs.  I will support many customers - scanners of bar codes, phones, iphones and laptops with WPA2.  I have to create 2 local networks without wire - one for DATA and for a hotspot.

    Does anyone have a basic configuration that they can share for both the WLC and 6509 configuration?  Someone at - it a 'from' scratch version doc process they could share?  Someone at - it a version of code recommended?

    I downloaded the 7.0 Configuration Guide but was hoping to get some guideance real world also.

    TIA,

    Amir

    Hello

    Well, from version 7.0, is the last it is good to start from it.

    First implementation of 5508:

    http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70mint.html.

    I advise you to read carefully this section which explains the details and best practices to configure WLCs ports and interfaces.

    Regarding the config guides, I advise you to go through the design guide:

    http://www.cisco.com/application/pdf/en/us/guest/netsol/ns279/c649/ccmigration_09186a00808d9330.pdf.

    And examples of configuration:

    http://www.cisco.com/en/US/products/ps6366/prod_configuration_examples_list.html.

    They are valid for all WLC models.

    They are based on the configuration and very good examples.

    HTH,

    Tiago

    --

    If this helps you or answers to your question if it you please mark it as 'responded' or write it down, if other users can easily find it.

  • 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.

  • ISE 1.4 compatible with WLC 5508 version 7.6.130.0 and 8.0.115.0

    Hi Expert,

    We check in on Cisco ISE 1.4 online document below we found this case WLC 5508 version 7.6.130 support
    http://www.Cisco.com/c/en/us/TD/docs/security/ISE/1-4/compatibility/ISE _...

    But as control with Cisco WLC5508 version 7.6.130.0 version found takes in charge only ISE 1.2
    http://www.Cisco.com/c/en/us/TD/docs/wireless/controller/release/notes/c...

    And for WLC 8.0.115.0 show support ISE1.3
    http://www.Cisco.com/c/en/us/TD/docs/wireless/controller/release/notes/c...

    But on the compatibility matrix Wireless show that the version ISE1.3
    http://www.Cisco.com/c/en/us/TD/docs/wireless/compatibility/matrix/Compa...

    We want to know what the WLC version 7.6.130.0 and 8.0.115.0 can support ISE 1.4 or not?

    See you soon,.

    FN

    Yes, they both work with ISE 1.2, 1.3 and 1.4, it's probably just the case of this version specific WLC has been tested with the ISE version that was going out at the time.

  • Cisco WLC 5508 & HP printer

    Hello

    I have some problems with cisco and hp airprint wlan systems.

    I use two cisco wlc 5508, a master and an anchor.

    the APs ar connectet to master wlc, DHCP and the point of diversion to the internet are on anchor wlc.

    so far, with my android phone, I can connect and hepatitis has access to the internet.

    now, I use an HP Multifunction (MFP M276nw) printer with Airprint. I connect to the WLAN even the hp printer on the same IP range.

    I can ping the printer from my android tablet, but I can never find the printer with a hp soft.

    If I connect the printer even with the same compressed to a point of user access to home normal is all ok thing.

    I think I have to configure something on my wlcs.

    any ideas?

    Thank you

    It seems that v7.5 supports Hello on anchor. You might want to look at this thread

    https://supportforums.Cisco.com/thread/2200019

    Sent by Cisco Support technique iPhone App

  • 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

  • How to retrieve the RADIUS shared secret key on the WLC 5508

    Hi all

    The wirelss privious admin left our company and did not let the other know the shared secret key on the WLC 5508 Radius.

    The 5508 WLC runs on the 7.0.98.0 code. I can access the viao WLC CLI and GUI. I can also access the Win2003 Radius Server, but the button displays an asterisk for me. I have listed partial RADIUS config of the WLC below. How can I get the RADIUS shared secret key? Thanks in advance.

    (Cisco Controller) > show RADIUS summary

    Vendor Id backward compatibility... People with disabilities
    Call Station Id... lower case
    Dial the Station Id Type... IP address
    Aggressive failover... Activated
    Keywrap.......................................... People with disabilities
    Rescue test:
    Test Mode.................................... Off
    Probe of username... cisco-probe
    Interval (in seconds)... 300
    MAC for authentication Messages... hyphen delimiter
    MAC for Accounting Messages... hyphen delimiter

    Authentication servers

    The State of the Port Address Type server all RFC3576 IPSec - AuthMode idx / phase 1/group/life/Auth/BA
    ---  ----  ----------------  ------  --------  ----  -------  ------------------------------------------------
    1 NM 10.xx.18.48 1645 on 2 off off - no/unknown/group-0/0 None/None

    Accounting servers

    The State of the Port Address Type server all RFC3576 IPSec - AuthMode idx / phase 1/group/life/Auth/BA

    -Other - or ITU (q)
    ---  ----  ----------------  ------  --------  ----  -------  ------------------------------------------------
    1 N 10.xx.18.48 1646 enabled 2 N/A disabled - no/unknown/group-0/0 None/None

    Kind regards

    Robert

    You can retrieve the RADIUS shared secret key as other passwords that are stored on the WLC by using the procedure at the following link:

    https://supportforums.Cisco.com/community/NetPro/wireless-mobility/begin-wireless/blog/2011/11/04/recover-wepadminguest-account-password-from-WLC

    NOTE: WPA keys are not available through these methods.

    Basically, you can enable password in clear text on the wlc with 'config passwd-cleartext enable' and then issue a "view orders of the running-config' - your RADIUS configuration command should now display the shared secret.

    -Pat

  • Essbase 11.1.2.1 without http server

    Hello

    Ive tried to install the stand-alone Essbase 11.1.2.1. And my question is, is it mandatory to go with the http server. Cause under normal circumstances, from the OHS opmn instance starts apache.exe process in my server which we do not want to be running. I came across a few docs and one of Jean post where I found the workaround below.

    "To configure the registry of SSP without having to install applications Web Services Foundation:

    1.demarrez EPM System Configurator of the command-line, including the option - forceRegistry
    Starting from a console window, change to EPM_ORACLE_HOME/common/config/version_number and enter configtool.bat - forceRegistry.
    On UNIX, change to EPM_ORACLE_HOME/common/config/version_number and then tapez./configtool.sh - forceRegistry. »

    This method will ensure that we can run without http server, thus eliminating the process apache.exe to the server?

    Thank you

    OPMN is part of the installation of OSH in 11.1.2.1 but this does not mean THAT OHS will run for essbase deployment.
    If you deploy OSH then another service OPMN will be created running OSH.

    Essbase can be started from the command line or Windows OPMN for example service opmn_EPM_

    See you soon

    John
    http://John-goodw

  • I can only access https / /: Web sites

    can someone help me with this problem, I did things like. Clear the cache, history, uncheck the proxy etc. settings. I restar my Mac in safe mode and I am able to access http / /: and https / /: web sites, this problem happened on my administrator account and not on other accounts, but just happens in all accounts. I don't remember doing something weird on my mac. I see that I am connected to WiFi, but I can't access http / / sites. any help is appreciated and thanks in advance... A better way to reach me is to *.

    < personal information under the direction of the host >

    FYI, personal information (e-mail) are not recommended to post on public forums, it is an invitation for spam.

    For your problem, try disabling IPv6.

    Goto system preferences > network > advanced > TCP/IP > Local link only

  • All https: Web sites know the untrusted certificate errors and appears as the provider cert Digitalmarketresearchapps Pty Ltd. No virus found on my system.

    I started all of a sudden the problem "untrusted connection" on earlier work https: Web sites with the "not provided any transmitter channel" as a reason. I tried all the proposed solutions and nothing works. I ran several programs antivirus and no viruses or malware detected. I don't have any such installed ESET suggested in the previous solutions. Display of certificates for the default sites shows that the provider in all cases is 'Digitalmarketresearchapps Pty Ltd'. Certificates are always a start date and an expiration of 2039. I think I picked up something that causes the problem, but as I said, none of my antivirus/malware programs are detecting anything.

    I had this problem as well, and he ended up caused by the installation of the E-Rewards application notify. I had to uninstall and then restore my computer to an earlier time to fix the signer of the certificate again to "Thawte Consulting (Pty) Ltd". I contacted E-Rewards to let them know and ask why this is happening.

  • Display the pages Web HTTPS but HTTP Web pages are not

    Hello

    All of a sudden, http Web pages not loading for me in Explorer, Chrome or Firefox.  One minute, they are involved, but the next minute, they were not.
    I don't get an error message in the browser.  Rather, the address of the site remains in the address bar and a screen totally Virgin appears in the box.
    Strangely - in a computer numpty like me! -https Web pages still work, so I can get secure Web pages as email, banking, etc.  To me, this proves that my internet connection works fine.
    Of course, I use a fairly old computer with Windows XP on it.  Maybe this isn't a good thing, but I fear it is where I am right now.
    Anyone happen to know how I could get the http pages working again?  Your help is appreciated.
    Thank you.

    A difference between http https of ASD is that http uses Port 80 and https Port 443.

    It could be that you have a firewall that blocks port 80.  Check your firewall (and maybe disable them temporarily) of the see, it's the source of your problem.

    As a final attempt, sometimes among the following freewares will solve the problems like this:

    LSPFix <> http://www.cexx.org/lspfix.htm >

    WinsockXPFix <> http://www.snapfiles.com/get/winsockxpfix.html >

    HTH,

    JW

Maybe you are looking for

  • Skin wireless keyboard

    HI people, Does anyone found a cover/skin for the new (iMac 21.5 "Oct 2015) wireless keyboard? The 'old' have smaller left and right arrows. Thank you Adam

  • Dynamically adjust the size of table control panel

    Hello I have a combo box control that I drag within a table. Since my request depends on the size of the initialized array, I'm having a problem with the car, adjust the number of items to display on the control panel. Say for example, I wanted to ha

  • POS FAZE TODAS AS OBTAINED, AN IMP VERICACOES E NAO MENSAGEM POPE CONGESTINAMENTO CONTINUED.

    HP DESKJET3050A CH376-64001 {removed privacy} EXIBE MENSAGEM CONGESTIONAMENTO OF PAPEL, AS VERIFICACOES OBTAINED VIA SUPORTE WERE MADE VERY O PROBLEMA a a. CRUISER ESTA NO PRASO DA GARANTIA. O THAT DEVO FAZER?

  • How can I activate my wireless phone?

    wireless connection problems HelloMy without wire was recently turned off due to an internet connection slow and done nothing and I want to turn it back on, but I'm not sure how to turn on my wireless.I have windows vista and a d-link wireless router

  • SSD 1 TB upgrade in Latitude E7470

    Stopped on this laptop choice list a M.2 SSD 512 MB as the best choice.  The tech specs list also 512GB like the max, but I wonder if it shows just what Dell offers.  There are now versions 1 to the market of the m2, it would be this work as an upgra