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

Tags: Cisco Wireless

Similar Questions

  • Hello, I would like to know if it is possible or there is the possibility to choose the path in the preferences to save backups of ios through itunes for windows pc devices. Thank all participants in advance of the availability, I offer cordi

    Hello

    I would like to know if it is possible or there is the possibility to choose the path in the preferences to save backups of ios through itunes for windows pc devices.

    Thank all participants in advance of the availability, I offer cordial greetings.

    Post edited by: andreava

    No preference, but there is a solution. See moving backup iOS device. See the rest of the tip of the user to do a split cell library if the library files and the media folder are on different drives.

    TT2

  • Are the Photos and videos uploaded (iCloud Photo Sharing) equal to the (ios iphoto reviewed)? If not, what is the new equal to that? If so, can I organize the layout as I wish? can I convert (iphoto ios log backup) to the file (iCloud Photo Sharing)?

    I always use the ios 7 because I like my reviews of iphoto, ios 8 and after don't support is not iphoto, I intend to upgrade to the latest version of ios. so my question is:

    Are the Photos and videos uploaded (iCloud Photo Sharing) equal to the (ios iphoto reviewed)?

    -If so, I can arrange the provision in the way I want? What happens if you want to convert my old (iphoto ios log backup) to import (iCloud Photo Sharing) that it is?

    -If not, what is the new equal to that with the possibility of transferring these journals?

    Thank you

    No they are not really the same thing and you can't convert one to the other. When / if you update, you will simply lose your logs. You cannot influence other available photos of the order appear in

  • I backed up my iPhone 3GS on iTunes. Back up seemed to go OK. iTunes then prompted me to update the iOS that I did. The phone then crashed. I did a factory restore. The backup that I did was not there. Can I recover the loss upward in anyway?

    I backed up my iPhone 3GS on iTunes. Back up seemed to go OK. ITunes then prompted me to update the iOS that I did. The update failed. My phone broke. The only option available was to restore to factory settings I've done. The back up I had made was not available for restore. It contains precious family photos and videos. Is anyway to recover the lost or any part of it from my PC Backup? Any help would be appreciated. Best wishes Giles

    If you go to iTunes and watch your backups, you don't see one that was made today? Did you see an indication of the backup was not successful? What version of iOS is the device that you have been asked to update? It was not an iOS for the iPhone 3GS update in a while. Regarding the photos and videos, you had never taken the time to import them on the computer?

  • I am backing up my new iphone more than 6 s. It won't let me select any backup, indicating there is no backup that is compatible with the IOS 9.0.2 version. The backup is the IOS 9.2 (which is the latest version on my iphone 4S).

    I'm trying to set up my new iPhone more than 6 s. When I get to the backup process, he does allow you to choose a backup. He says, there is no backup that is compatible with the version of IOS 9.0.2. The last backup is my iPhone 4S (IOS 9.2).

    If the backup of the iPhone 4S has been with iOS 9.2, then you will need to update the new 6sPlus iPhone is iOS 9.0.2. You can use an old backup iOS on a recent iOS phone, but not the reverse. Set up the 6sPlus of the iPhone as a new device, and then update the iOS to the 9.2. After that, go to settings > general > reset > erase all content and settings. That will bring the Wizard Setup again and you will be able to restore your backup iOS iPhone 4S 9.2.

  • 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

  • authenticate the cisco WLC 5508 with cisco ACS 1120 (version 5.0) using GANYMEDE +.

    My installation has cisco WLC 5508 and ACS 1120 ver 5.0. How to authenticate users who access to the WLC via the ACS 1120 users GANYMEDE +. I am able to authenticate users for routers and cisco switches, but when I try the same for the CMT, it fails.

    Can someone explain please the config/basic steps that must be configured on both services ACS & WLC.

    You use plain vanilla 5.0 or have installed patches?

    the ACS 5.1 has new GANYMEDE related functionaity, including support for custom services and attributes. If they are necessary for the WLC yo need support it would improve.

    He could also relevant corrective patch from calendar 5.0 but I can't find any relevant specific at this stage CDETS

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

  • Discovery of a new WLC 5508 AP

    Hi all

    I have a WLC EXISTING with the APs 5508 located in static 192.168.1.0/24 with 7.5 Cisco IOS.

    I intend to add a NEW 5508 WLC as a PDC with CISCO IOS 8.0 and 5508 WLC existing as a secondary controller.

    How can I move all the AP for the new 5508 and what will happen during the update of the firmware.

    Kind regards

    Hi Rasika, all the answer are helpful.
    If our answers are useful, pls use the (Star) rating system to rate :)
    the wireless controller is now configured, but we have an issue with WLAN that is using radius server authentication. Should we enroll the NEW WLC to the Radius server?
    Yes, you must add your WLC in your RADIUS server with the same credentials that you to define the RADIUS on your WLC server. Link below may provide some guidance on required WLC configs. http://www.Cisco.com/c/en/us/support/docs/wireless-mobility/WLAN-security/69730-EAP-auth-WLC.html HTH Rasika * Pls note all useful responses *.

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

  • Two WLC 5508 anchor high availability

    Hello.

    It is possible use 2 WLC 5508 EN HOW to ANCHOR in an active scenario?.

    For example, if a WLC down the service, another Dungeon provide service to customers of anchor?

    At the moment we have just a WLC 5508 anchor mode. What do I have to configure high availability of the ANCHOR.

    Thank you very much!!!

    You have redundant WLC as anchor points, but if an anchor fails, the user must reconnect.

    There is a feature on the WLC HA, but it is mainly for foreigners redundancy WLC anchor no redundancy. With guest several anchors overseas WLC balance the load between the two. You will not be able to put a primary or backup.

    Sent by Cisco Support technique iPhone App

  • Previous backups of IOS

    So the small questions is, is it possible to display the IOS for my previous backups Icloud? I have tried IOS10 and it please, but I need to return to 9.3.2,and of course I made a return

    The iOS itself is not included in the backup. What follows has instructions on how to reinstall the iOS before restoring your backup. https://beta.Apple.com/SP/betaprogram/FAQ

  • If the iOS 9.3 with older phones problem has been resolved?

    The iOS 9.3 update screwed to the top of my iPhone 5, but good. After downgrading to iOS 9.2.1 and spent several hours chatting with Apple Support and recover my apps, settings and some more time, I'm wary about retry iOS 9.3. My phone invites me to once again 'upgrade' to 9.3.

    Has there been a change?

    Yes, they fixed with an update last night, you should spend.

    ads-affected-by-activation-lock-issue/ http://9to5mac.com/2016/03/28/Apple-re-releases-iOS-9-3-for-Older-iPhones-and-IP

    But backup your iPhone before, just in case it is not resolved.

  • When the iOS 9.3 is again released for iPhone 5 s?

    iOS 9.3 was interrupted due to a failure for older iPhones.

    I have a backup of my iPhone with iOS 9.3 5.

    My new iPhone 5 runs on 9.2.1 and he tells me that this version is the most recent. I am not able to upgrade and can not restore my backup.

    When the iOS 9.3 is again released for iPhone 5 s?

    y at - it another option to the update level or restore the backup with new version of iOS?

    Unfortunately, Apple has not yet released a bug fix, but if you consider the number of iOS users have been touched by the update in 9.3, it should be available soon.

Maybe you are looking for

  • iPhone if disconnette dalla rete wifi quando e in stand by e no arrivano notifiche di messaggi, whastapp e mail

    Salve a tutti, Ho da poco labor-intensive UN iPhone 5s nuovo da 16 GB e da pochi giorni ho noticed he following problema: dopo a periodo di some UNAMET da quando block the screen, it wifi if disconnette e quando paper the screen, the linea wifi TR ri

  • My Satellite P100 (PSPA3E) waste of time

    Hello! For example: if I turn off Monday 17:00 and put it on the next day 12:00 time is still between 17:00 and the date is also incorrect.Sometimes the time is set automatically 2 hours in the past. So with this machine, it is only a year and a half

  • CLIQ XT - lost the weather widget

    I just bought this phone a couple of days, and while I was trying to figure out how to change the city default on the weather widget, I lost the whole widget. Anyway I can get it back?

  • IMAP for Windows Live Mail / Hotmail

    I find it really hard to believe that Microsoft cannot implement IMAP on their Windows Live Mail / accounts Hotmail. Does anyone (who really knows) know what IMAP can be implemented? There must be millions of people who are waiting for this! Microsof

  • Laptop stops shortly after the start.

    I have a slight puzzle on my hands. I was working on a DV5-1012EA which had a damaged palm rest/touchpad. I found a replacement and very well equipped. I had the laptop works well and decided to run windows update. Everything seemed fine, but after a