Cannot add WLC 5508 7.2.111.3 to Cisco Prime Infrastructure 2.0

Though the Cisco Prime Infrastructure Compatibility Matrix list out that 7.2.111.3 is supported for PI 2.0
I am not able to add the controller to the PI 2.0.
The Reachability Status always shown "Unknow" and SNMP Status always shown "No response for SNMP Get".
There is no firewall between the WLC and PI.
And ping test shows it is reachable.
If I try to add controller by non-management port (I know it is not work but I want to try the reachability), the Reachability Status shown "Reachable" but the SNMP Status always shown error.
And if I use some SNMP testing software to test the SNMP port. SNMP can be quoted.
I have try to lower down the "Maximum VarBinds per Get PDU" but no luck.
Any thing I can do to troubleshoot the problem?

Yes, I follow the procedure but it does not work.
Another update:
I add another WLC with version 7.0.98.0. It is fine.
And I setup another new PI 2.0 and new temporary WLC5508 with 7.2.111.3 to test. It work fine also......
So, I am wondering the existing 7.2 WLC have problem in responsing the SNMP Get. But I dont have any idea to test....
Do anyone have idea to test the snmp connection between PI and WLC?

Similar Messages

  • Cannot add WLC 5508 v7.6.120.0 into Prime Infrastructure 2.1

    Hi everyone
    Hope you can help us with this issue.
    We already configure the WLC using this guide: http://mrncciew.com/2013/02/14/configuring-snmp-on-wlc/
    snmp v2: enable
    snmp v1: enable
    default port values
    community: incaenic with ip and mask 0.0.0.0 to allow access from any network or ip
    traps receiver:                   community: incaenic                 ip: 10.100.100.15
    when we try to discover the WLC with the PI it gave the error "SNMP Connectivity Fail"
    WLC is on subnet 10.100.102.0/24 and PI in 10.100.100.0/24; there is a Catalyst 3850 between then with no access list on then.
    Did someone can guide us with this?
    Best Regards.
    Alvaro Rugama

    Hi,
    Which version of SNMP are you using?
    If you are using v1/v2 you should be using community string rather than local database credentials?
    Regarding the service port what is the ip address assigned on the service port. From the configuration guide "Prime Infrastructure uses the preferred management IP address from the loop back interface. If the device does not have a loopback interface, Prime Infrastructure uses similar logic to the OSPF algorithm to select the router’s preferred management IP address."
    Hope that helps.
    Regards
    Najaf

  • Cannot add WLC 5508 to Prime Infrastructure 2.1

    Regards,
    I've been migrating / implementing a WCS to PI 2.1. I had several problems at first to add the 11 WLC we have to PI which I could be solving by trying and testing as I have not found many references by Cisco when it comes to troubleshooting when deploying PI.
    I have several queries:
    1. The WCS was added 11 WLC using different SNMP communities are configured on each of them. At first when trying to add the WLC had PI SNMP communication problems. I performed the test to eliminate any of the WLC added to WCS and add it again with some communities already existing R / W without any problem. At the end, I could not add the WLC so I had to create an SNMP community with the IP of Prime in the WLC so that they can be added. Does anyone know what is the cause of this?
    2. I could not add a WLC 5508 IOS 7.3 using this method, even creating an SNMP community and IP mask 0.0.0.0 / 0. No access list or FW in between the WLC These WLC are spread over several countries but i was able to add the other WLC adding a community in each WLC pointing to the IP of Prime. It is similar to this case:
    https://supportforums.cisco.com/discussion/12232506/cannot-add-wlc-5508-v761200-prime-infrastructure-21
    Thanks for the help.

    It turns out that this situation was caused by a bug in 7.6.120.0 (CSCuo73572).
    TAC handed me an escalation image (7.6.120.16) that fixed this. 
    Added the controllers sucessfully on the first try. 
    Phill

  • CANNOT ADD WLC 5508 HA MODE IN PRIME INFRASTRUCTURE 2

    I have two 5508 7.5.102 in HA mode and i am trying to add theme in cisco prime infrastructure 2 but i am taking back unreachable. Controller can ping the prime. I adding the controller using the management ip address of controller. Have anyone meat thise issue ? I also have problem when adding switches in stack mode (WS-C2960S-48TD-L)

    Hello!
    Check, that the service-port of the wlc is not in the same subnet, as Prime ip address

  • Cisco Prime Infrastructure 2.2 Rest API XML does not add LF

    I am using several scripts that dig the data from XML files created through Cisco Prime Infrastructure Rest API. It worked fine until 2.1. Now, with 2.2, seems Cisco stopped adding LF to each line and everything is 'one' line.
    Here is an example with 2.1, there is a LF to the end of each line:
    ?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <queryResponse type="AccessPointDetails" rootUrl="https://server/webacs/api/v1/data" requestUrl="https://server/webacs/api/v1/data/AccessPointDetails?type=contains(UnifiedAp)&amp;.full=true&amp;.maxResults=1000&amp;.firstResult=0" responseType="listEntityInstances" count="715" first="0" last="714">
        <entity url="https://server/webacs/api/v1/data/AccessPointDetails/1505569" type="AccessPointDetails" dtoType="accessPointDetailsDTO">
            <accessPointDetailsDTO id="1505569" displayName="1505569">
                <adminStatus>ENABLE</adminStatus>
                <apType>AP1240</apType>
                <cdpNeighbors>
                    <cdpNeighbor>
                        <capabilities>Switch IGMP </capabilities>
                        <duplex>Half Duplex</duplex>
                        <interfaceSpeed>100Mbps</interfaceSpeed>
                        <localPort>2</localPort>
                        <neighborIpAddress>10.1.1.1</neighborIpAddress>
                        <neighborName>switch</neighborName>
                        <neighborPort>FastEthernet0/1</neighborPort>
                        <platform>cisco WS-C3560-8PC</platform>
                    </cdpNeighbor>
    Now, with 2.2, there is not LF anywhere:
    ?xml version="1.0" encoding="UTF-8" standalone="yes"?><queryResponse type="AccessPointDetails" rootUrl="https://server/webacs/api/v1/data" requestUrl="https://server/webacs/api/v1/data/AccessPointDetails?type=contains(UnifiedAp&amp;.full=true&amp;.maxResults=1000&amp;.firstResult=0" responseType="listEntityInstances" count="715" first="0" last="714">
    <entity url="https://server/webacs/api/v1/data/AccessPointDetails/1505569" type="AccessPointDetails" dtoType="accessPointDetailsDTO">
    <accessPointDetailsDTO id="1505569" displayName="1505569"><adminStatus>ENABLE</adminStatus><apType>AP1240</apType><cdpNeighbors><cdpNeighbor>
    Does anyone know, is this intentional or a mistake? Or is there a way how I control this?
    I am reading on-line CPI Rest API docs, but seems cannot find anything.
    Thanks,
    Vlad

    PI 2.0 is in Beta mode for testing in closed group already. However it may still take some time to get released on CCO for FCS.
    I think it is expected to be released between aug-sep. BU has also started working on CPI 2.1, which you can see test uploads on CCO.
    For what does it have for customers?
    > As Cisco have a vision of one network Management software for both wired and wireless infrastructure, which started getting real partially with Cisco PI.
    As WCS got evolved to NCS and eventually to Cisco Prime Infrastructure, but it doesnt yet have full Management capability for wired infra., which is there with LMS.
    With CPI 2.x Cisco plans to blend entire LMS and WCS features together.
    -Thanks

  • WLC 2504 in Cisco Prime Infrastructure 1.2

    Trying to add Cisco 2504 Wireless Controller, Software Version 7.3.101.0, to Cisco Prime Infrastructure
    1.2 (1.2.0.103), License Evaluation, with no success.
    When using Discovery, Discovery Job show Credential Errors: "Error occured due to invalid SNMP credential"
    When Add Device from Device Work Center I get:
    Reachability is "Unknown", Device Type is empty, Collection Status is "Managed with Warnings", with message "SNMP Failure: No Response for SNMP Get request.", Collection Time is empty.
    I've tried with both snmp v2 and v3.
    I've tried to lower "Maximum VarBinds per Get PDU" to 10 or 20, cause I've read similar problem in NCS.

    I solved the same problem 5min ago.!
    select the device and press syc ..that helped me ...

  • Cisco Prime Infrastructure 1.3 - TFTP backup WLC not working

    I don;t get the the background task "Controller Configuration Backup" working. I want to use default TFTP.
    When i look in the logging i see 2 of three WLC's succesfully backuped there logging. Is their a log file where you can see what is happening?
    With kind regards,
    Martijn.

    Hi Martijn:
    If you go to the controller's GUI to Commands > Upload File and manually trigger the TFTP Configuration backup, does the process complete as expected?  If not, whatever's causing that problem needs to be addressed first.
    When someone wants to do a config backup from the command line, they give a series of commands
    transfer download datatype config
    transfer download mode tftp
    transfer download serverip x.x.x.x
    transfer download path ./
    transfer download filename myBackup.cfg
    transfer download start
    The Controller Config Backup background task is just the SNMP version of "transfer download filename " and "transfer download start".  If these other required settings aren't already there, the task isn't going to set them (the humans have to).  If there's a problem with writing out the file on the server, or packet routing issues to get to the server, the task isn't going to see those things, it just knows that the answer to "transfer download start" wasn't "Okay!"
    As for watching this processing in logs, go to Administration > Logging, and set the logging level to Trace for the modules SNMP and System, and click Save.  Then kick off your backup attempt, allowing it to fail.  When it does, return to Administration > Logging, and click the Download button to retrieve the logs.zip file.  The activity should be in the ncs-x-x.log file. 
    If you don't have the new Update-1 patch for Prime Infrastructure 1.3.0.20 (filename PI_1.3.0.20_Update_1-12.tar.gz) installed, I'd suggest you get it.  While it's not going to specifically address this issue, there are a lot of really good fixes in it.
    Release Notes for Update 1 for Cisco Prime Infrastructure 1.3.0.20

  • Cisco Prime Infrastructure 2.0 add antenna?

    Hi!,   
         I Have installed a cisco infrastructure 2.0 application. during the configuration phase of the heatmaps I notice that my antenna model is not in the list; there is a "generic antenna" option but this antenna is a "directional" antenna but my model is AIR-ANT2430V-R an omni-directional antenna. how can i ADD my exact model of antenna to the Prime Infrastructure app?

    Just to be more specific, i need to know if is possible add more antennas on this option marked on the picture... this is to avoid use the "other" option or other equivalent model (which is what i have configured now based on the dBi value)... thanks in advance for any idea...

  • WCS cannot add WLC over slow link

    I have a WCS running at our main data center. We recently added a WLAN Controller (4402)in a remote office that is located over a VPN tunnel.
    The WCS can PING the WLC (but it is slow at about 250ms), and I can access the controller's web interface from the WCS server. I just cannot add the controller, it gives me the error "No response from device, check SNMP communities, version or network for issues."
    Any thoughts on what I can try?
    I have also verified the SNMP communities and removed and re-added them on both the WCS and WLC, and I've tried both the RO and RW strings. No difference.
    Thanks.

    Here is what appears in the log when I try to connect via SNMP v2c.
    *Oct 13 13:26:19.552: %SIM-3-MACADDR_GET_FAIL: sim.c:1147 Interface 1 source MAC address is not found.
    *Oct 13 13:26:03.546: %SIM-3-MACADDR_GET_FAIL: sim.c:1147 Interface 1 source MAC address is not found.
    *Oct 13 13:25:55.548: %SIM-3-MACADDR_GET_FAIL: sim.c:1147 Interface 1 source MAC address is not found.
    *Oct 13 13:25:51.560: %SIM-3-MACADDR_GET_FAIL: sim.c:1147 Interface 1 source MAC address is not found.
    *Oct 13 13:25:44.483: %USMDB-4-MSGTAG027: usmdb_wcp.c:221 usmDbWcpGetParentRouterName(): Non-Doberman platform.
    *Oct 13 13:25:44.483: %USMDB-4-MSGTAG022: usmdb_wcp.c:95 usmDbWcpGetControllerSlotPort(): Non-Doberman platform.
    *Oct 13 13:25:44.482: %USMDB-4-MSGTAG023: usmdb_wcp.c:119 usmDbWcpGetPeersPortAndIp(): Non-Doberman platform.
    *Oct 13 13:25:44.481: %USMDB-4-MSGTAG022: usmdb_wcp.c:95 usmDbWcpGetControllerSlotPort(): Non-Doberman platform.
    *Oct 13 13:25:44.480: %USMDB-4-MSGTAG023: usmdb_wcp.c:119 usmDbWcpGetPeersPortAndIp(): Non-Doberman platform.
    I tried an extended ping from the WCS's default gateway and if I increase the datagram size to 1500, I get the “M” = could not fragment reply. However a size of 1300 works fine.

  • WLC 5508, DHCP Problem after Update Cisco ASA(DHCP-Server)

    Hello,
    our Problem is, our Apple Devices get no ip adress from our Cisco ASA Cluster(ASA 9.1.2) over Wireless(Cisco WLC 5508). All other devices(Windows, Android,...) work correct, without problems. Our WLC is in HA-Mode.
    Does anybody have an Idea?
    Thank you very much and Best regards,
    Stefan

    Hello again,
    I hope this case is the solution.
    https://supportforums.cisco.com/message/3942112#3942112
    I will let you know after downgrade.
    Best regards,
    Stefan

  • Cisco Prime Infrastructure 2.0 cannot establish connectiont with WLC5508 7.4.110

    I have two wlc 5508 in HA with image version 7.4.110. These two WLC are connected on two 6509 Catalyst Switch VSS system. On the WLC the LAG are enabled for the connection to the VSS. When i am trying to add the WLC to PI 2  once is succsessful. The connection continew working for a wile and after 3 hours or 5 hours or 1 day lost the connection between these two (WLC 5508 & PI.2) . After this trying again to add the WLC to PI.2 with no success . It became unreachable but the ping between the WLC & PI.2 its working fine.
    It realy importand for me to add the WLC to PI.2 becouse it is the eyes for the APs for me.
    Also the image of WLC 7.4.110 is compatible for PI.2 . I check it at cisco matrix files. Cisco also sugest 7.4.110 image for PI.2
    any idea........?

    The subject of the posting shows Prime Infrastructure 2.0 but in the body of the message you've got Prime Infrastructure 1.2
    If it's in fact Prime Infrastructure 1.2 ::: 1.2 and 7.4.110.0 code isn't compatible
    http://www.cisco.com/en/US/partner/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html#wp92761
    1.2.1.12
    7.3.112.0
    7.3.101.0
    7.2.115.2
    7.2.111.3
    7.2.110.0
    7.2.103.0
    7.0.240.0
    7.0.235.3
    7.0.235.0
    7.0.230.0
    7.1.91.0
    7.0.220.0
    7.0.116.0
    7.0.98.218
    7.0.98.0
    7.3.101.0
    7.2.110.0
    7.2.103.0
    7.0.240.0
    7.0.230.0
    7.0.220.0
    7.0.201.204
    7.0.112.0
    7.0.105.0
    ISE 1.0
    ISE 1.1
    IOS12.2(50)SE
    IOS12.2(50)SG
    IOS12.2(33)SXI
    If deploying Prime Infrastructure as a virtual appliance on a customer-supplied server, one of the following versions of VMware ESX or ESXi can be used:
    •VMware ESX or VMware ESXi Version 4.0
    •VMware ESX or VMware ESXi Version 4.1
    •VMware ESXi Version 5.0
    Note VMware Tools Version 4.1 is preinstalled in the Prime Infrastructure virtual appliance.

  • Cisco prime infrastructure 1.3 cannot access to the user interface

    Hello,
    We use prime infrastructure 1.3 , and since 1 week we cannot acces to the Web UI to manage network devices.
    "Health monitor server" service doesn't started correctly
    #ncs status
    Health Monitor is running, with an error.
    failed to start NCS on startup Health Monitor
    Reporting Server is running
    Ftp Server is running
    Database server is running
    Tftp Server is running
    Matlab Server is running
    NMS Server is stopped.
    SAM Daemon is not running ...
    DA Daemon is not running ...
    Syslog Daemon is not running ...
    thanks for your help.

    PI 1.x Health Monitor is running, with an error/NMS Server is stopped
    CSCuf25963
    Description
    Symptom:
    PI cannot start completely after the re-setup with different hostname/IP address from that in the original setup.
    NCS-APL-01-new/admin# ncs status
    Health Monitor is running, with an error.
    failed to start NCS on startup Health Monitor
    Reporting Server is running
    Ftp Server is running
    Database server is running
    Tftp Server is running
    Matlab Server is running
    NMS Server is stopped.
    SAM Daemon is running ...
    DA Daemon is running ...
    Syslog Daemon is running ...
    Conditions:
    1.2.1.12
    Not happen in 1.1.X or earlier
    Workaround:
    from the root shell,
    update the file /opt/CSCOlumos/conf/messaging.properties with the correct ipaddress.
    Known Affected Releases:
    (2)
    1.2(1.12)
    1.3(0.20)

  • AP 360021 cannot join WLC 5508

    Dears,
    I have a cisco 5508 WLC and 40 cisco 360021 APs.
    I configured the WLC and assign the management interface IP and also configured a DHCP pool on my Cisco 4507 core switch wit option 43.
    But the problem that the APs connot join the WLC.
    The below message appears:-
    Nov  7 09:08:28.953: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Nov  7 09:08:28.954: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Nov  7 09:08:38.968: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Nov  7 09:08:39.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: x.x.x.x pe6
    *Nov  7 09:08:39.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
    Please support me to solve this issue.
    Regards,

    Dears,
    Also find the attched debug and the requirements that you asked for.
    AP cisco debug:
    *Oct 13 01:33:32.691: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Oct 13 01:33:34.691: %LINK-3-UPDOWN: Interface BVI1, changed state to up
    *Oct 13 01:33:35.691: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
    *Oct 13 01:33:35.691: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started - CLI initiated
    *Oct 13 01:33:37.815: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
    *Oct 13 01:33:37.903:  status of voice_diag_test from WLC is false
    *Oct 13 01:33:37.907: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!
    *Oct 13 01:33:37.907: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Oct 13 01:33:38.815: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Oct 13 01:33:38.867: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Oct 13 01:33:38.875: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Oct 13 01:33:39.191: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Oct 13 01:33:39.223: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 10.10.107.58, mask 255.255.255.0, hostname APfc99.47a2.2ef7
    *Oct 13 01:33:39.223: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Oct 13 01:33:39.899: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Oct 13 01:33:40.899: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Oct 13 01:33:43.191: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Oct 13 01:33:43.259: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.10.107.58, mask 255.255.255.0, hostname APfc99.47a2.2ef7
    *Oct 13 01:33:43.259: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Oct 13 01:33:47.907: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
    *Oct 13 01:33:47.907: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
    *Oct 13 01:33:47.907: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
    *Oct 13 01:33:47.907: %CAPWAP-3-ERRORLOG: Failed to process timer message.
    *Oct 13 01:33:48.315: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Oct 13 01:33:48.379: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to ad
    Translating "CISCO-CAPWAP-CONTROLLER"...domain server (10.10.18.1) (10.10.18.100)
    ministratively down
    *Oct 13 01:33:48.467:  status of voice_diag_test from WLC is false
    *Oct 13 01:33:48.471: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Oct 13 01:33:49.379: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Oct 13 01:33:49.431: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Oct 13 01:33:49.439: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Oct 13 01:33:49.471: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
    *Oct 13 01:33:49.471: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
    *Oct 13 01:33:50.463: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Oct 13 01:33:51.463: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Oct 13 01:33:52.475: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Oct 13 01:33:52.483: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Oct 13 01:33:53.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Oct 13 01:33:53.507: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Oct 13 01:33:54.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Mar 23 23:47:46.583: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
    *Mar 23 23:47:46.583: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
    *Mar 23 23:47:46.583: %MESH-6-LINK_UPDOWN: Mesh station fc99.47a2.2ef7 link Down
    *Mar 23 23:47:47.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.10.107.5:5246
    *Mar 23 23:47:48.055: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Mar 23 23:47:48.119: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
    *Mar 23 23:47:48.211:  status of voice_diag_test from WLC is false
    *Mar 23 23:47:48.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 23 23:47:49.119: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 23 23:47:49.171: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar 23 23:47:49.179: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 23 23:47:50.207: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 23 23:47:51.207: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Mar 23 23:47:51.215: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar 23 23:47:51.223: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 23 23:47:52.215: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 23 23:47:52.247: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 23 23:47:53.247: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.10.107.5
    *Mar 24 00:25:36.579: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
    *Mar 24 00:25:36.579: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
    *Mar 24 00:25:36.579: %MESH-6-LINK_UPDOWN: Mesh station fc99.47a2.2ef7 link Down
    APfc99.47a2.2ef7#
    %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
    *Mar 24 00:33:27.519: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
    *Mar 24 00:33:28.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 24 00:33:28.035: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 00:33:28.043: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar 24 00:33:28.051: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 24 00:33:29.079: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 00:33:30.079: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Mar 24 00:33:32.519: %CAPWAP-5-SENDJOIN: sending Join Request to 10.10.107.5
    *Mar 24 00:33:32.523: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar 24 00:33:32.531: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 24 00:33:33.523: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 24 00:33:33.555: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 00:33:34.555: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radi
    The Time on AP is not same time on the WLC
    Oct 13 01:34:13.411: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Mar 24 02:02:36.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.107.5 peer_port: 5246
    *Mar 24 02:02:36.003: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    User Access Verification
    Username:
    *Mar 24 02:02:36.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 24 02:02:37.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 24 02:02:37.035: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:02:38.035: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    Username:
    *Mar 24 02:03:05.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached!
    Username: Cisco
    Password:
    APfc99.47a2.2ef7>
    *Oct 13 01:34:13.411: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Mar 24 02:02:36.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.107.5 peer_port: 5246
    *Mar 24 02:02:36.003: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    User Access Verification
    Username:
    *Mar 24 02:02:36.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 24 02:02:37.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 24 02:02:37.035: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:02:38.035: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    Username:
    *Mar 24 02:03:05.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached!
    Username: Cisco
    Password:
    APfc99.47a2.2ef7>
    *Mar 24 02:04:31.603: %IP-4-DUPADDR: Duplicate address 10.10.107.5 on BVI1, sourced by 0006.f661.d880?
      memory  set memory parameters
    APfc99.47a2.2ef7#set
    *Mar 24 02:04:33.103: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-start
    *Mar 24 02:04:33.207: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
    *Mar 24 02:04:33.207: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
    *Mar 24 02:04:33.207: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
    *Mar 24 02:04:33.207: %CAPWAP-3-ERRORLOG: Failed to process timer messag
    APfc99.47a2.2ef7#
    *Mar 24 02:04:38.159: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Mar 24 02:04:38.223: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
    *Mar 24 02:04:38.315:  status of voice_diag_test from WLC is false
    Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
    *Mar 24 02:04:38.315: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:04:39.223: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 24 02:04:39.275: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar 24 02:04:39.283: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.10.107.5:5246
    *Mar 24 02:06:58.999: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Mar 24 02:05:59.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.107.5 peer_port: 5246
    *Mar 24 02:05:59.003: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar 24 02:05:59.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 24 02:06:00.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 24 02:06:00.039: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:06:01.039: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    APfc99.47a2.2ef7#
    APfc99.47a2.2ef7#
    *Mar 24 02:09:50.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached!
    APfc99.47a2.2ef7#
    APfc99.47a2.2ef7#
    APfc99.47a2.2ef7#
    Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
    *Mar 24 02:10:20.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.10.107.5:5246
    *Mar 24 02:10:21.055: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Mar 24 02:10:21.123: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
    *Mar 24 02:10:21.207:  status of voice_diag_test from WLC is false
    *Mar 24 02:10:21.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:10:22.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 24 02:10:22.175: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar 24 02:10:22.183: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 24 02:10:23.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:10:24.211: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Mar 24 02:10:25.787: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
    *Mar 24 02:10:25.787: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
    *Mar 24 02:10:25.787: %MESH-6-LINK_UPDOWN: Mesh station fc99.47a2.2ef7 link Down
    *Mar 24 02:10:30.211: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
    *Mar 24 02:10:30.215: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar 24 02:10:30.223: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 24 02:10:31.215: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 24 02:10:31.251: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:10:32.251: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
    *Mar 24 02:10:49.211: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
    *Mar 24 02:10:49.215: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar 24 02:10:49.223: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 24 02:10:50.215: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 24 02:10:50.251: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:10:51.251: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
    *Mar 24 02:11:08.211: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
    *Mar 24 02:11:08.215: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar 24 02:11:08.223: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 24 02:11:09.215: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 24 02:11:09.247: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:11:10.247: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Mar 24 02:11:16.607: %IP-4-DUPADDR: Duplicate address 10.10.107.5 on BVI1, sourced by 0006.f661.d880
    *Mar 24 02:11:18.107: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Mar 24 02:11:18.211: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
    *Mar 24 02:11:18.211: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
    *Mar 24 02:11:18.211: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
    *Mar 24 02:11:18.211: %CAPWAP-3-ERRORLOG: Failed to process timer message.
    *Mar 24 02:11:23.163: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Mar 24 02:11:23.227: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
    *Mar 24 02:11:23.319:  status of voice_diag_test from WLC is false
    Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
    *Mar 24 02:11:23.319: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:11:24.227: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 24 02:11:24.275: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar 24 02:11:24.283: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 24 02:11:25.311: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:11:26.311: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Mar 24 02:11:33.319: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
    *Mar 24 02:11:33.323: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar 24 02:11:33.331: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 24 02:11:34.323: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 24 02:11:34.355: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:11:35.355: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Mar 24 02:11:43.319: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Mar 24 02:12:43.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.107.5 peer_port: 5246
    *Mar 24 02:12:43.003: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar 24 02:12:43.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 24 02:12:44.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 24 02:12:44.035: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:12:45.035: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
    *Mar 24 02:17:05.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.10.107.5:5246
    *Mar 24 02:17:06.055: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Mar 24 02:17:06.119: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
    *Mar 24 02:17:06.203:  status of voice_diag_test from WLC is false
    *Mar 24 02:17:06.207: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:17:07.119: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 24 02:17:07.171: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar 24 02:17:07.179: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 24 02:17:08.203: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:17:09.203: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Mar 24 02:17:10.787: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
    *Mar 24 02:17:10.787: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
    *Mar 24 02:17:10.787: %MESH-6-LINK_UPDOWN: Mesh station fc99.47a2.2ef7 link Down
    *Mar 24 02:17:15.207: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
    *Mar 24 02:17:15.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar 24 02:17:15.219: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 24 02:17:16.211: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 24 02:17:16.247: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:17:17.247: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Mar 24 02:17:53.207: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
    *Mar 24 02:17:53.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Mar 24 02:17:53.219: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar 24 02:17:54.211: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar 24 02:17:54.247: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar 24 02:17:55.247: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Mar 24 02:18:01.607: %IP-4-DUPADDR: Duplicate address 10.10.107.5 on BVI1, sourced by 0006.f661.d880
    *Mar 24 02:18:03.107: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Mar 24 02:18:03.207: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
    *Mar 24 02:18:03.207: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Even
    Show requirement for AP:-
    APfc99.47a2.2ef7#show version
    Cisco IOS Software, C3600 Software (AP3G2-K9W8-M), Version 12.4(25e)JA, RELEASE SOFTWARE (fc2)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2012 by Cisco Systems, Inc.
    Compiled Fri 27-Jan-12 21:27 by prod_rel_team
    ROM: Bootstrap program is C3600 boot loader
    BOOTLDR: C3600 Boot Loader (AP3G2-BOOT-M) LoaderVersion 12.4(23c)JY, RELEASE SOFTWARE (fc1)
    APfc99.47a2.2ef7 uptime is 7 minutes
    System returned to ROM by power-on
    System image file is "flash:/ap3g2-k9w8-mx.124-25e.JA/ap3g2-k9w8-mx.124-25e.JA"
    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    A summary of U.S. laws governing Cisco cryptographic products may be found at:
    http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
    If you require further assistance please contact us by sending email to
    [email protected].
    cisco AIR-CAP3602I-A-K9    (PowerPC) processor (revision A0) with 167926K/81920K bytes of memory.
    Processor board ID FGL1644Z15P
    PowerPC CPU at 800Mhz, revision number 0x2151
    Last reset from power-on
    LWAPP image version 7.2.1.72
    1 Gigabit Ethernet interface
    2 802.11 Radio(s)
    32K bytes of flash-simulated non-volatile configuration memory.
    Base ethernet MAC Address: FC:99:47:A2:2E:F7
    Part Number                          : 73-14521-02
    PCA Assembly Number                  : 800-37501-02
    PCA Revision Number                  : A0
    PCB Serial Number                    : FOC16414A83
    Top Assembly Part Number             : 800-35852-02
    Top Assembly Serial Number           : FGL1644Z15P
    Top Revision Number                  : C0
    Product/Model Number                 : AIR-CAP3602I-A-K9
    Configuration register is 0xF
    show inventry
    NAME: "AP3600", DESCR: "Cisco Aironet 3600 Series (IEEE 802.11n) Access Point"
    PID: AIR-CAP3602I-A-K9 , VID: V01, SN: FGL1644Z15P
    show requirement on WLC
    (Cisco Controller) >show sysinfo
    Manufacturer's Name.............................. Cisco Systems Inc.
    Product Name..................................... Cisco Controller
    Product Version.................................. 7.4.100.0
    Bootloader Version............................... 1.0.1
    Field Recovery Image Version..................... 6.0.182.0
    Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
    Build Type....................................... DATA + WPS
    System Name...................................... Cisco_61:d8:84
    System Location..................................
    System Contact...................................
    System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
    Redundancy Mode.................................. Disabled
    IP Address....................................... 10.10.107.5
    Last Reset....................................... Software reset
    System Up Time................................... 0 days 1 hrs 4 mins 25 secs
    System Timezone Location......................... (GMT +3:00) Baghdad
    System Stats Realtime Interval................... 5
    System Stats Normal Interval..................... 180
    Configured Country............................... IQ  - Iraq
    Operating Environment............................ Commercial (0 to 40 C)
    --More-- or (q)uit
    Internal Temp Alarm Limits....................... 0 to 65 C
    Internal Temperature............................. +40 C
    External Temperature............................. +24 C
    Fan Status....................................... OK
    State of 802.11b Network......................... Enabled
    State of 802.11a Network......................... Enabled
    Number of WLANs.................................. 1
    Number of Active Clients......................... 0
    Memory Current Usage............................. Unknown
    Memory Average Usage............................. Unknown
    CPU Current Usage................................ Unknown
    CPU Average Usage................................ Unknown
    Burned-in MAC Address............................ 00:06:F6:61:D8:80
    Power Supply 1................................... Present, OK
    Power Supply 2................................... Absent
    Maximum number of APs supported.................. 100
    WLC after debug enable
    *spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp:AC Name message element length = 58
    *spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp: WTP Radio Information msg length = 67
    *spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp: CAPWAP Control IPV4 Address len = 77
    *spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp: CAPWAP Control IPV6 Address len = 99
    *spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp: Mwar type payload len = 110
    *spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp: Time sync payload len = 125
    *spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery Response sent to 10.10.107.60:8944
    *spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery Response sent to 10.10.107.60:8944
    *spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 WTP already released
    *spamApTask2: Mar 24 04:56:19.133: fc:99:47:a2:2e:f7 CAPWAP Control Msg Received from 10.10.107.5:8944
    *spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 packet received of length 123 from 10.10.107.5:8944
    *spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Msg Type = 1 Capwap state = 0
    *spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery Request from 10.10.107.5:8944
    *spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 20
    *spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Total msgEleLen = 94
    *spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 40 msgEleType = 39
    *spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Total msgEleLen = 50
    *spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 41
    *spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Total msgEleLen = 45
    *spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 44
    *spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Total msgEleLen = 40
    *spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 10 msgEleType = 37
    *spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Vendor specific payload from AP  54:78:1A:43:CA:D0 validated
    *spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Total msgEleLen = 26
    (Cisco Controller) >*sshpmLscTask: Mar 24 05:02:01.461: sshpmLscTask: LSC Task received a message 4
    *Oct 13 01:33:48.191: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    User Access Verification
    Username:
    Username:
    Username:
    *Oct 13 01:33:50.191: %LINK-3-UPDOWN: Interface BVI1, changed state to up
    *Oct 13 01:33:50.191: %IP-4-DUPADDR: Duplicate address 10.10.107.5 on BVI1, sourced by 0006.f661.d880
    *Oct 13 01:33:51.191: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
    *Oct 13 01:33:52.019: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
    *Oct 13 01:33:52.019: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
    *Oct 13 01:33:52.019: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
    *Oct 13 01:33:52.019: %CAPWAP-3-ERRORLOG: Failed to process timer message.
    *Oct 13 01:33:53.251: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Oct 13 01:33:53.315: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to ad
    Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)ministratively down
    *Oct 13 01:33:53.407:  status of voice_diag_test from WLC is false
    *Oct 13 01:33:53.411: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Oct 13 01:33:54.315: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Oct 13 01:33:54.367: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
    *Oct 13 01:33:54.375: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Oct 13 01:33:55.399: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
    *Oct 13 01:33:56.399: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 22 msgEleType = 37
    nable
    (Cisco Controller) >*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Vendor specific payload from AP  54:78:1A:43:CA:D0 validated
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Total msgEleLen = 0
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Join Priority Processing status = 0, Incoming Ap's Priority 4, MaxLrads = 100, joined Aps =0
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 1. 0 0
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 2. 232 3
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 3. 0 0
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 4. 100 0
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: AC Descriptor message element len = 40
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 acName = Cisco_61:d8:84
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp:AC Name message element length = 58
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: WTP Radio Information msg length = 67
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: CAPWAP Control IPV4 Address len = 77
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: CAPWAP Control IPV6 Address len = 99
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: Mwar type payload len = 110
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: Time sync payload len = 125
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery Response sent to 10.10.107.5:8944
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery Response sent to 10.10.107.5:8944
    *spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 WTP already released
    *spamApTask6: Mar 24 04:56:28.440: fc:99:47:a2:2e:f7 CAPWAP Control Msg Received from 10.10.107.60:8945
    *spamApTask6: Mar 24 04:56:28.440: 54:78:1a:43:ca:d0 packet received of length 123 from 10.10.107.60:8945
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Msg Type = 1 Capwap state = 0
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery Request from 10.10.107.60:8945
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 20
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 94
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 40 msgEleType = 39
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 50
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 41
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 45
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 44
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 40
    *spamApTask7: Mar 24 04:56:28.441: fc:99:47:a2:2e:f7 CAPWAP Control Msg Received from 10.10.107.61:8945
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 10 msgEleType = 37
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 packet received of length 123 from 10.10.107.61:8945
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Vendor specific payload from AP  54:78:1A:43:CA:D0 validated
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Msg Type = 1 Capwap state = 0
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 26
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 22 msgEleType = 37
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery Request from 10.10.107.61:8945
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 20
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Vendor specific payload from AP  54:78:1A:43:CA:D0 validated
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 94
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 40 msgEleType = 39
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 0
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 50
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 41
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Join Priority Processing status = 0, Incoming Ap's Priority 4, MaxLrads = 100, joined Aps =0
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 45
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 44
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 1. 0 0
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 40
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 2. 232 3
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 10 msgEleType = 37
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 3. 0 0
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Vendor specific payload from AP  54:78:1A:43:CA:D0 validated
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 4. 100 0
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 26
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 22 msgEleType = 37
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery resp: AC Descriptor message element len = 40
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Vendor specific payload from AP  54:78:1A:43:CA:D0 validated
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 acName = Cisco_61:d8:84
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 0
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery resp:AC Name message element length = 58
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery resp: WTP Radio Information msg length = 67
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Join Priority Processing status = 0, Incoming Ap's Priority 4, MaxLrads = 100, joined Aps =0
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 1. 0 0
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 2. 232 3
    *spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery resp: CAPWAP Control IPV4 Address len = 77
    *spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 3. 0 0

  • Cisco Prime Infrastructure 2.1 can't add Cisco ISE 1.2 to "External Management Servers"

    Hi all,
    I'm trying to add Ciso ISE 1.2 (1.2.0.899 with version 13 patch) servers (primary and secondary) as "External Management Servers" in Cisco PI 2.1 (2.1.0.0.87) but there appears such message indicating that ISE server is not reachable: 
    The weird thing is that ISE servers are reachable from PI and vice-versa (I can ping each other from their CLIs)
    There were added ISE servers to PI long ago (primary and secondary ISE) and then secondary was deleted from PI. Primary ISE still persists in PI but its status is unreachable:
    But I can see info about wired clients authenticating on the switchs (NADs for ISE) - weird, status is unreachable but client info is being received from ISE.
    I tried application stop NCS/application start NCS on PI and application stop ise/application start ise on ISE - no success for that issue.
    So I can't find a way to solve that weird issue, maybe you can help me find out the cause of such things. Thanks. 

    Hi,
    -- Please Go to Administration > Logging > set the Message level to TRACE > Click save
    -- Then try to add the ISE.
    -- Once it fails, collect the logs from Administration > Logging > 
    check the "ncs-0-0.log"  & search the file for "ERROR" & paste the results here. This will give us exact reason.
    - Ashok
    Please rate the post or mark as correct answer as it will help others looking for similar information

  • SNMP TRAP ON Secondary WLC 5508

    Hi I'm Louis,
    I work on 2 WLC 5508 with version 7.4 and Prime Infrastructure 1.3
    We have activate AP SSO to work with a primary and secondary controller.
    We have added the controller to Prime infrastructure and activated SNMP.
    We receive correctly the alarms on Prime.
    But when we work on Primary WLC, and the secondary crash we haven't got information about that. No SNMP received.
    That is normal ?
    Thx for your reply
    Regards

    I find this, in Monitoring and Troubleshooting the Redundancy States
    http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/1.2/user/guide/chgdevconfig.html
    On my primary controller, in SNMP => Trap Log , I can see :
    RF failure notification ErrorType: 34 Reason :Lost Peer, Moving to Active-No-Peer State! => When I unplug RP link
    RF progress notification unitId: -1407319963 peerUnitId :14 unitState: -1407319863 peerUnitState :5
    RF progress notification unitId: -1407319963 peerUnitId :14 unitState: -1407319863 peerUnitState :9  => When I plug the RP link.
    So I can see the trap on my controller but there is nothing in Prime ...

Maybe you are looking for