Request to Join.

I have two tables...
in the 1st table lets say emp_sal I have used salary date wise.


for example:

100 20 APRIL 1, 2010
102 15 APRIL 1, 2010
100 30 APRIL 2, 2010

I need a query where I give the date settings and to_date it should return all emplyees sal and missing wage should return 0


For example... If is give 1st April 10 date and 2 April 10 as date, it should return

100 20 APRIL 1, 2010
102 15 APRIL 1, 2010
100 30 APRIL 2, 2010
102 0 2 APRIL 2010


Pls help

Outer join partitioned would be perfect here:

with emp_sal as (select 100 empno, 20 salary, to_date('01/04/2010', 'dd/mm/yyyy') dt from dual union all
                 select 102 empno, 15 salary, to_date('01/04/2010', 'dd/mm/yyyy') dt from dual union all
                 select 100 empno, 30 salary, to_date('02/04/2010', 'dd/mm/yyyy') dt from dual),
-- end of mimicking your data in a subquery called emp_sal. Hurrah for subquery factoring!
       dates as (select to_date('01/04/2010', 'dd/mm/yyyy') + level -1 dt  -- replace the dates with your from_date/to_date parameters
                 from   dual
                 connect by level <= to_date('02/04/2010', 'dd/mm/yyyy') - to_date('01/04/2010', 'dd/mm/yyyy') + 1)
select es.empno, nvl(es.salary, 0) salary, dates.dt
from   dates
       left outer join emp_sal es partition by (es.empno) on (dates.dt = es.dt);

     EMPNO     SALARY DT
---------- ---------- ----------
       100         20 01/04/2010
       100         30 02/04/2010
       102         15 01/04/2010
       102          0 02/04/2010

Tags: Database

Similar Questions

  • AP joined does not WLC

    Hello

    I'm WLC4404 6.0 image under the last one. the AP is does not reach the controller and it says invalid license in the application configuration.

    It is a start of one access point:

    11:05:59.025 Dec 11: % 3-CAPWAP-ERRORLOG: go join a capwap controller

    * 11:05:59.000 11 dec: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.140.248 peer_port: 5246

    * 11:05:59.000 11 dec: % CAPWAP-5-CHANGED: CAPWAP changed State to

    * 11:06:02.862 11 dec: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.140.248 peer_port: 5246

    * 11:06:02.863 11 dec: % CAPWAP-5-SENDJOIN: send request to join 172.16.140.248

    * 11:06:02.863 11 dec: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

    * 11:06:03.619 11 dec: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

    * 11:06:03.764 11 dec: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.140.248

    * 11:06:03.764 11 dec: % DTLS-5-PEER_DISCONNECT: Peer 172.16.140.248 has closed the connection.

    * 11:06:03.764 11 dec: % DTLS-5-SEND_ALERT: send WARNING: close notify alert at 172.16.140.248:5246

    * 11:06:03.803 11 dec: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 11:06:03.803 11 dec: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 11:06:13.824 11 dec: % 3-CAPWAP-ERRORLOG: go join a capwap controller

    * 11:06:14.000 11 dec: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.140.248 peer_port: 5246

    * 11:06:14.000 11 dec: % CAPWAP-5-CHANGED: CAPWAP changed State to

    * 11:06:18.644 11 dec: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.140.248 peer_port: 5246

    * 11:06:18.644 11 dec: % CAPWAP-5-SENDJOIN: send request to join 172.16.140.248

    * 11:06:18.644 11 dec: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

    * 11:06:19.587 11 dec: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

    * 11:06:19.722 11 dec: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.140.248

    * 11:06:19.722 11 dec: % DTLS-5-PEER_DISCONNECT: Peer 172.16.140.248 has closed the connection.

    * 11:06:19.722 11 dec: % DTLS-5-SEND_ALERT: send WARNING: close notify alert at 172.16.140.248:5246

    * 11:06:19.761 11 dec: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 11:06:19.761 11 dec: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    All Advisor,.

    Elijah

    The country code has been the problem.  Thank you.

    Brian

  • Denial of the Motorola Feedback team?

    This-

    SRS,

    I regret to inform you that your request to join the Group of Motorola Feedback team has been denied.

    Sincerely,
    Mark (Forums Manager)

    ----------------------------------------------------------------

    Well, I guess it's the only type of response we'll get Motorola on problems with the DroidX.

    If I was unhappy with the way they do business before, imagine how I feel now.

    -Steve

    @srs

    You have the message 'Motorola Feedback Team' was an oversight sent by an error in our notification system "groups". The group asked you to join was never formally (notice the difference in name) and is never intended to be visible to anyone on the community. Please ignore the message of refusal, you have received. If you want to participate in the Motorola feedback network , you can register via the link for future opportunities.

    Sorry for the confusion.

    Mark

    Support Forums Manager

  • AP c1130 and 7.4 WLC

    I have a problem what do I do?

    No session registration is currently active.

    * 14:29:38.000 Nov 5: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.10.1 peer_port: 5246
    * 14:29:39.343 Nov 5: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.10.1 peer_port: 5246
    * 14:29:39.344 Nov 5: % CAPWAP-5-SENDJOIN: send request to join 172.16.10.1
    * 14:29:39.346 Nov 5: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
    * 14:29:39.346 Nov 5: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
    * 14:29:39.347 Nov 5: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
    * 14:29:39.347 Nov 5: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.16.10.1 capwap
    * 14:29:39.547 Nov 5: % DTLS-5-ALERT: WARNING received: close notify alert 172.16.10.1
    * 5 Nov 14:29:39.548: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.10.1:5246
    * 5 Nov 14:29:39.609: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
    * 5 Nov 14:29:39.610: bsnInitRcbSlot: slot 1 has NO radio
    * 5 Nov 14:29:40.632: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
    * 14:29:40.714 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 14:29:40.719 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 14:29:40.724 Nov 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 14:29:41.749 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 5 Nov 14:29:42.749: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
    * 14:29:49.682 Nov 5: % 3-CAPWAP-ERRORLOG: go join a capwap controller
    * 14:29:49.000 Nov 5: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.10.1 peer_port: 5246
    * 14:29:50.347 Nov 5: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.10.1 peer_port: 5246
    * 14:29:50.348 Nov 5: % CAPWAP-5-SENDJOIN: send request to join 172.16.10.1% do not forget to ask the administrator of the CA to revoke your certificate.

    No session registration is currently active.

    * 14:29:50.350 Nov 5: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
    * 14:29:50.350 Nov 5: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
    * 14:29:50.350 Nov 5: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
    * 14:29:50.350 Nov 5: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.16.10.1 capwap
    * 14:29:50.548 Nov 5: % DTLS-5-ALERT: WARNING received: close notify alert 172.16.10.1
    * 5 Nov 14:29:50.548: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.10.1:5246
    * 5 Nov 14:29:50.609: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
    * 5 Nov 14:29:50.609: bsnInitRcbSlot: slot 1 has NO radio
    * 5 Nov 14:29:51.631: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
    * 14:29:51.663 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 14:29:51.668 Nov 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 14:29:52.693 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 5 Nov 14:29:53.694: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
    * 14:30:00.681 Nov 5: % 3-CAPWAP-ERRORLOG: go join a capwap controller
    * 14:30:01.000 Nov 5: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.10.1 peer_port: 5246
    * 14:30:02.340 Nov 5: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.10.1 peer_port: 5246
    * 14:30:02.341 Nov 5: % CAPWAP-5-SENDJOIN: send request to join 172.16.10.1% do not forget to ask the administrator of the CA to revoke your certificate.

    No session registration is currently active.

    * 14:30:02.343 Nov 5: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
    * 14:30:02.343 Nov 5: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
    * 14:30:02.343 Nov 5: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
    * 14:30:02.343 Nov 5: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.16.10.1 capwap
    * 14:30:03.166 Nov 5: % DTLS-5-ALERT: WARNING received: close notify alert 172.16.10.1
    * 5 Nov 14:30:03.166: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.10.1:5246
    * 5 Nov 14:30:03.229: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
    * 5 Nov 14:30:03.229: bsnInitRcbSlot: slot 1 has NO radio
    * 14:30:03.252 Nov 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
    * 14:30:03.303 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 14:30:03.304 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 14:30:03.309 Nov 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 5 Nov 14:30:04.251: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
    * 14:30:04.333 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 14:30:04.338 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 14:30:04.343 Nov 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 14:30:05.368 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 5 Nov 14:30:06.369: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
    * 14:30:13.302 Nov 5: % 3-CAPWAP-ERRORLOG: go join a controller capwap % do not forget to ask the administrator of the CA to revoke your certificate.

    No session registration is currently active.

    * 14:30:13.000 Nov 5: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.10.1 peer_port: 5246
    * 14:30:14.339 Nov 5: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.10.1 peer_port: 5246
    * 14:30:14.340 Nov 5: % CAPWAP-5-SENDJOIN: send request to join 172.16.10.1
    * 14:30:14.342 Nov 5: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
    * 14:30:14.342 Nov 5: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
    * 14:30:14.343 Nov 5: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
    * 14:30:14.343 Nov 5: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.16.10.1 capwap
    * 14:30:14.539 Nov 5: % DTLS-5-ALERT: WARNING received: close notify alert 172.16.10.1
    * 5 Nov 14:30:14.539: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.10.1:5246
    * 5 Nov 14:30:14.600: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
    * 5 Nov 14:30:14.600: bsnInitRcbSlot: slot 1 has NO radio
    * 5 Nov 14:30:15.622: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
    * 14:30:15.654 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 14:30:15.659 Nov 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 14:30:16.684 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 5 Nov 14:30:17.684: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
    * 14:30:24.674 Nov 5: % 3-CAPWAP-ERRORLOG: go join a capwap controller
    * 14:30:25.000 Nov 5: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.10.1 peer_port: 5246
    * 14:30:26.338 Nov 5: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.10.1 peer_port: 5246
    * 14:30:26.339 Nov 5: % CAPWAP-5-SENDJOIN: send request to join 172.16.10.1% do not forget to ask the administrator of the CA to revoke your certificate.

    No session registration is currently active.

    * 14:30:26.341 Nov 5: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
    * 14:30:26.341 Nov 5: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
    * 14:30:26.342 Nov 5: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
    * 14:30:26.342 Nov 5: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.16.10.1 capwap
    * 14:30:26.540 Nov 5: % DTLS-5-ALERT: WARNING received: close notify alert 172.16.10.1
    * 5 Nov 14:30:26.541: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.10.1:5246
    * 5 Nov 14:30:26.602: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
    * 5 Nov 14:30:26.602: bsnInitRcbSlot: slot 1 has NO radio
    * 14:30:26.676 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 14:30:26.678 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 14:30:26.683 Nov 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 5 Nov 14:30:27.624: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
    * 14:30:27.707 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 14:30:27.712 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 14:30:27.717 Nov 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 14:30:28.742 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 5 Nov 14:30:29.743: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
    * 14:30:36.676 Nov 5: % 3-CAPWAP-ERRORLOG: go join a capwap controller
    * 14:30:37.000 Nov 5: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.10.1 peer_port: 5246
    * 14:30:38.331 Nov 5: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.10.1 peer_port: 5246
    * 14:30:38.332 Nov 5: % CAPWAP-5-SENDJOIN: send request to join 172.16.10.1% do not forget to ask the administrator of the CA to revoke your certificate.

    No session registration is currently active.

    * 14:30:38.334 Nov 5: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
    * 14:30:38.334 Nov 5: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
    * 14:30:38.334 Nov 5: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
    * 14:30:38.334 Nov 5: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.16.10.1 capwap
    * 14:30:39.154 Nov 5: % DTLS-5-ALERT: WARNING received: close notify alert 172.16.10.1
    * 5 Nov 14:30:39.154: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.10.1:5246
    * 5 Nov 14:30:39.214: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
    * 5 Nov 14:30:39.215: bsnInitRcbSlot: slot 1 has NO radio
    * 14:30:39.237 Nov 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
    * 14:30:39.289 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 14:30:39.290 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 14:30:39.296 Nov 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 5 Nov 14:30:40.237: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
    * 14:30:40.321 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 14:30:40.326 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 14:30:40.331 Nov 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 14:30:41.356 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 5 Nov 14:30:42.356: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
    * 14:30:49.289 Nov 5: % 3-CAPWAP-ERRORLOG: go join a controller capwap % do not forget to ask the administrator of the CA to revoke your certificate.

    No session registration is currently active.

    * 14:30:49.000 Nov 5: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.10.1 peer_port: 5246
    * 14:30:50.339 Nov 5: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.10.1 peer_port: 5246
    * 14:30:50.340 Nov 5: % CAPWAP-5-SENDJOIN: send request to join 172.16.10.1
    * 14:30:50.342 Nov 5: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
    * 14:30:50.342 Nov 5: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
    * 14:30:50.342 Nov 5: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
    * 14:30:50.343 Nov 5: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.16.10.1 capwap
    * 14:30:50.542 Nov 5: % DTLS-5-ALERT: WARNING received: close notify alert 172.16.10.1
    * 5 Nov 14:30:50.542: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.10.1:5246
    * 5 Nov 14:30:50.604: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
    * 5 Nov 14:30:50.604: bsnInitRcbSlot: slot 1 has NO radio
    * 5 Nov 14:30:51.626: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
    * 14:30:51.659 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 14:30:51.664 Nov 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 14:30:52.689 Nov 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 5 Nov 14:30:53.689: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
    * 14:31:00.678 Nov 5: % 3-CAPWAP-ERRORLOG: go join a capwap controller
    * 14:31:00.000 Nov 5: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.10.1 peer_port: 5246
    * 14:31:01.339 Nov 5: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.10.1 peer_port: 5246
    * 14:31:01.340 Nov 5: % CAPWAP-5-SENDJOIN: send request to join 172.16.10.1% do not forget to ask the administrator of the CA to revoke your certificate.

    Below, wire and make sure that you got a version of the software which have a command to fix this cert.

    https://supportforums.Cisco.com/document/12453081/lightweight-AP-fail-create-capwaplwapp-connection-due-certificate-expiration

    HTH

    Rasika

    Pls note all useful responses *.

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

  • AP records do not with BASIC MAC

    We run WLC version 5.2.193.0 with 20 access points. But you can not save to the controller

    debugging on the wlc

    * 14:51:38.866 Jul 19: could not process CAPWAP 10.29.32.35:7173 package

    * 14:51:41.866 Jul 19: 00:12:01:c5:c0:c4 AP records do not with the Mac BASE.
    * 14:51:41.866 Jul 19: State 00:12:01:c5:c0:c4 machine Manager: failed to process the msg = State 5 = 8 from 10.29.32.35:7173 type

    connection to the access point:

    * 12:50:39.378 Jul 19: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
    * 12:50:39.379 Jul 19: % DTLS-5-SEND_ALERT: send WARNING: close notify alert at 10.29.25.241
    * 12:50:40.922 Jul 19: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY
    * 12:50:40.923 Jul 19: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY
    * 12:50:40.926 Jul 19: bsnInitRcbSlot: slot 0 has NO radio
    * 12:50:40.927 Jul 19: bsnInitRcbSlot: slot 1 has NO radio
    * 12:50:40.943 Jul 19: bsnUnlockDevice: not raise radio: radio 0 is disable admin
    * 12:50:40.943 Jul 19: bsnUnlockDevice: not raise radio: radio 1 is able to disable admin
    * 12:50:50.947 Jul 19: % 3-CAPWAP-ERRORLOG: go join a capwap controller
    * 12:50:51.000 Jul 19: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.29.25.241 peer_port: 5246
    * 12:50:52.806 Jul 19: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.29.25.241 peer_port: 5246
    * 12:50:52.808 Jul 19: % CAPWAP-5-SENDJOIN: send request to join 10.29.25.241
    * 12:50:52.808 Jul 19: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE
    * 12:50:53.366 Jul 19: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

    The AP is also in the authentication list

    (AUTO-FRWHMAG-ACCB1) > auth-list

    Allow the MIC APs against AAA... disabled
    Allow the LSC APs against Auth-list... disabled

    Let APs with MIC - manufactured installed... active c
    Let APs with SSC-... a self-signed certificate enabled
    Let APs with LSC - locally important disabled CERT...

    Key Type Mac Addr Cert hash
    -----------------------   ----------   ------------------------------------------
    00:12:01:C5:C0:C4 SSC f593d3bf2875508c5e7a2005820b56bc2ef48f50

    Unfortunately I did not access phyiscal to this access point, so I can't 'convert' it. Any other ideas?

    Thank you

    Frank

    Frank,

    Looks like you have a bad AP because it does not detect the installed radios:

    * 12:50:40.926 Jul 19: bsnInitRcbSlot: slot 0 has NO radio
    * 12:50:40.927 Jul 19: bsnInitRcbSlot: slot 1 has NO radio

    This case of wil the PA for not being able to join the WLC.  I will seek to have it replaced.

    Thank you

    Lee

  • Access point lose connection to WLC 7.6.130

    Hi all

    When we try to move the access points of 7.0.116 7.6.130 controller (5500). Access point is continuously lose the connection with wlc and the record of the return.

    Can someone please help! Here are the logs. Please let me know if you need more information.

    * 10:05:23.547 Nov 20: % LWAPP-3-CLIENTERRORLOG: connected mode
    (.,) 3 20 10:06:11.279: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (CAPWAP_WTP_EVENT_REQUEST
    * 10:06:11.283 Nov 20: LWAPP-3-CLIENTERRORLOG %: switch to standalone mode
    * 20 Nov 10:06:11.287: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
    * 10:06:11.287 Nov 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 10.50.65.61:5246
    * 10:06:21.343 Nov 20: % 3-CAPWAP-ERRORLOG: MWAR selected ' ERFWS019.u70015'(index 0).
    * 10:06:21.343 Nov 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
    * 10:06:22.000 Nov 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.50.65.61 peer_port: 5246
    * 10:06:22.615 Nov 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.50.65.61 peer_port: 5246
    * 10:06:22.615 Nov 20: % CAPWAP-5-SENDJOIN: send request to join 10.50.65.61
    * 10:06:22.671 Nov 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
    * 10:06:22.671 Nov 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
    * 10:06:22.671 Nov 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
    * 10:06:22.671 Nov 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 10.50.65.61 capwap
    * 10:06:22.763 Nov 20: "Promiscuous" from Ethernet mode
    * 10:06:23.163 Nov 20: % LWAPP-4-CLIENTEVENTLOG: OfficeExtend Localssid recorded Flash AP
    * 10:06:23.387 Nov 20: % CAPWAP-5-JOINEDCONTROLLER: AP joined controller ERFWS019.u70015
    * 10:06:24.439 Nov 20: LWAPP-4-CLIENTEVENTLOG %: No. Flex ACL to load map configuration file. To connect to the controller to get the configuration file
    * 10:06:24.439 Nov 20: LWAPP-4-CLIENTEVENTLOG %: No. Flex ACL to load map configuration file. To connect to the controller to get the configuration file
    * 10:06:24.439 Nov 20: % LWAPP-4-CLIENTEVENTLOG: map No. LS Flex to load ACL configuration file. To connect to the controller to get the configuration file
    * 10:06:24.439 Nov 20: LWAPP-4-CLIENTEVENTLOG %: no central Dhcp configuration file map to load. To connect to the controller to get the configuration file
    * 20 Nov 10:06:24.439: % 3-CAPWAP-ERRORLOG:
    Flash file: / configs/AP_LAYER2_ACL_MAPPING_PAYLOAD_file not found
    * 10:06:24.439 Nov 20: % 3-CAPWAP-ERRORLOG: flash Configuration file: / configs/AP_LAYER2_ACL_MAPPING_PAYLOAD_file read failed

    * 10:06:24.439 Nov 20: % LWAPP-3-CLIENTERRORLOG: connected mode
    (.,) 3 20 10:07:11.167: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (CAPWAP_WTP_EVENT_REQUEST
    * 10:07:11.171 Nov 20: LWAPP-3-CLIENTERRORLOG %: switch to standalone mode

    .

    Have you checked the details of mapping vlan are there in the AP?

    Try to put in local mode & set it up the new FlexConnect mode & see

    HTH

    Rasika

    Pls note all useful responses *.

  • 1602i assertion failure and radio crash

    Hello world

    I have 3 APs with some of the thorny issues. Here is the information below:

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

    Product/model number: AIR-CAP1602I-C-K9

    Controller: "Cisco 5500 Series Wireless LAN Controller.

    Product name... Cisco controller
    Version of the product... 7.4.110.0

    Logging:

    * 17:47:42.927 Mar 4: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (CAPWAP_WTP_EVENT_REQUEST
    ., 4)
    * 17:47:49.107 Mar 4: EVT-4-AVT %: write flash: / done event.capwap
    * 17:47:49.123 Mar 4: LWAPP-3-CLIENTERRORLOG %: switch to standalone mode
    * 17:47:49.131 Mar 4: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
    * 17:47:49.131 Mar 4: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 10.126.242.247:5246
    * 17:47:49.179 Mar 4: % FEDS-6-persons with DISABILITIES: Signature of IDS is removed and disabled.
    * 17:47:58.183 Mar 4: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-CAPWAP-CONTROLLER
    * 17:48:08.183 Mar 4: % 3-CAPWAP-ERRORLOG: MWAR selected ' xxxxxxxWLC001'(index 0).
    * 17:48:08.183 Mar 4: % 3-CAPWAP-ERRORLOG: go join a capwap controller
    * 17:47:59.000 Mar 4: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.126.242.247 peer_port: 5246
    * 17:47:59.747 Mar 4: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.126.242.247 peer_port: 5246
    * 17:47:59.751 Mar 4: % CAPWAP-5-SENDJOIN: send request to join 10.126.242.247
    * 17:47:59.823 Mar 4: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
    * 17:47:59.823 Mar 4: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
    * 17:47:59.823 Mar 4: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
    * 17:47:59.823 Mar 4: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 10.126.242.247 capwap
    * 17:47:59.911 Mar 4: "Promiscuous" from Ethernet mode
    * 17:48:00.623 Mar 4: LWAPP-4-CLIENTEVENTLOG %: OfficeExtend Localssid recorded Flash AP
    * 4 Mar 17:48:00.767: ac_first_hop_mac - IP:10.126.134.1 Hop IP:10.126.134.1 IDB:BVI1
    * 17:48:00.767 Mar 4: setting AC hop first MAC: 58f3.9cf2.5781

    * 17:48:00.807 Mar 4: % CAPWAP-5-JOINEDCONTROLLER: AP joined controller xxxxxxxWLC001
    * 17:48:00.855 Mar 4: LWAPP-4-CLIENTEVENTLOG %: No. Flex ACL to load map configuration file. To connect to the controller to get the configuration file
    * 17:48:00.855 Mar 4: LWAPP-4-CLIENTEVENTLOG %: No. Flex ACL to load map configuration file. To connect to the controller to get the configuration file
    * 17:48:00.855 Mar 4: LWAPP-4-CLIENTEVENTLOG %: map No. LS Flex to load ACL configuration file. To connect to the controller to get the configuration file
    * 17:48:00.855 Mar 4: LWAPP-4-CLIENTEVENTLOG %: no central Dhcp configuration file map to load. To connect to the controller to get the configuration file
    * 17:48:00.855 Mar 4: LWAPP-3-CLIENTERRORLOG %: connected mode
    * 17:48:01.579 Mar 4: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 17:48:01.587 Mar 4: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 17:48:02.579 Mar 4: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
    * 17:48:02.615 Mar 4: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 17:48:02.627 Mar 4: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
    * 17:48:02.635 Mar 4: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
    * 17:48:03.615 Mar 4: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
    * 17:48:03.627 Mar 4: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
    * 17:48:03.759 Mar 4: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
    * 17:48:03.775 Mar 4: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 17:48:03.783 Mar 4: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 17:48:04.691 Mar 4: FEDS-6-ACTIVATED %: Signature of IDS is loaded and enabled
    * 17:48:04.759 Mar 4: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
    * 17:48:04.807 Mar 4: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
    * 17:48:04.847 Mar 4: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 17:48:04.855 Mar 4: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
    * 17:48:04.863 Mar 4: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
    * 17:48:05.847 Mar 4: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
    * 17:48:05.855 Mar 4: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
    * 17:48:05.903 Mar 4: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
    * 17:48:06.903 Mar 4: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
    * 5 Mar 03:40:38.815: ac_first_hop_mac - IP:10.126.134.1 Hop IP:10.126.134.1 IDB:BVI1
    * 03:40:38.815 Mar 5: setting AC hop first MAC: 58f3.9cf2.5781

    * 03:40:38.819 Mar 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
    * 03:40:39.267 Mar 5: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
    * 03:40:39.443 March 5:
    Note: A Spanning Tree bridge identifier random address of 0000.0c8a.8a10
    has been chosen for bridge Group 2 for the selected mac address
    is already used by the bridge group 18.
    * 03:40:39.443 March 5:
    Make sure that this address is unique.

    * 03:40:39.819 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
    * 03:40:40.267 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
    * 5 Mar 03:40:43.299: ac_first_hop_mac - IP:10.126.134.1 Hop IP:10.126.134.1 IDB:BVI1
    * 03:40:43.299 Mar 5: setting AC hop first MAC: 58f3.9cf2.5781

    * 03:40:43.307 Mar 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 03:40:43.747 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
    * 03:40:44.343 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 03:40:44.351 Mar 5: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
    * 03:40:45.343 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
    * 03:40:45.391 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
    * 03:40:46.475 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
    * 5 Mar 03:40:59.319: ac_first_hop_mac - IP:10.126.134.1 Hop IP:10.126.134.1 IDB:BVI1
    * 03:40:59.319 Mar 5: setting AC hop first MAC: 58f3.9cf2.5781

    * 03:40:59.819 Mar 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
    * 03:40:59.911 Mar 5: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
    * 5 Mar 03:41:00.323: ac_first_hop_mac - IP:10.126.134.1 Hop IP:10.126.134.1 IDB:BVI1
    * 03:41:00.323 Mar 5: setting AC hop first MAC: 58f3.9cf2.5781

    * 03:41:00.991 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
    * 03:41:00.991 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
    * 03:41:01.555 March 5:
    Note: A Spanning Tree bridge identifier random address of 0000.0c8a.e070
    has been chosen for 3 Group of bridge for the selected mac address
    is already used by the bridge group 18.
    * 03:41:01.555 March 5:
    Make sure that this address is unique.

    * 03:41:02.323 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 03:41:02.771 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
    * 03:41:03.031 Mar 5: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
    * 03:41:04.023 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
    * 03:41:04.071 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
    * 03:41:04.079 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 03:41:04.087 Mar 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 03:41:05.071 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
    * 03:41:05.079 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
    * 03:41:05.115 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 03:41:05.123 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
    * 03:41:05.135 Mar 5: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
    * 03:41:06.115 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
    * 03:41:06.123 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
    * 03:41:06.175 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
    * 03:41:07.175 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
    * 5 Mar 10:28:52.083: aggr_params Assertion failed-> tcp_pkts_pending_aggr in dot11_ac_test_ready to 1136
    * 10:28:52.083 Mar 5: Traceback-= 292514z 8B0264z 908868z 9093B8z 8BBD4Cz 8BE768z AFC544z AFD67Cz AFE838z B01DECz 5E6FC4z 5E73D0z 52E448z 52B028z 52B028z 52E510z
    * 5 Mar 10:28:52.083:... STOP TA TRACK ON TCP PKT SAID...
    * 5 Mar 10:28:54.291: aggr_params Assertion failed-> tcp_pkts_pending_aggr in dot11_ac_test_ready to 1136
    * 10:28:54.291 Mar 5: Traceback-= 292514z 8B0264z 908868z 9093B8z 8BBD4Cz 8BE768z AFC544z AFD67Cz AFE838z B01DECz 5E6FC4z 5E73D0z 52E448z 52B028z 52B028z 52E510z
    * 5 Mar 10:28:54.851: aggr_params Assertion failed-> tcp_pkts_pending_aggr in dot11_ac_test_ready to 1136
    * 10:28:54.851 Mar 5: Traceback-= 292514z 8B0264z 908674z 90A400z 5294ACz 52E448z 52B028z 52B028z 52E510z 3F93CCz
    * 5 Mar 10:33:24.459: aggr_params Assertion failed-> tcp_pkts_pending_aggr in dot11_ac_test_ready to 1136
    * 10:33:24.459 Mar 5: Traceback-= 292514z 8B0264z 908868z 9093B8z 8BBD4Cz 8BE768z AFC544z AFD67Cz AFE838z B01DECz 5E6FC4z 5E73D0z 52E448z 52B028z 52B028z 52E510z
    * 5 Mar 10:33:29.307: aggr_params Assertion failed-> tcp_pkts_pending_aggr in dot11_ac_test_ready to 1136
    * 10:33:29.307 Mar 5: Traceback-= 292514z 8B0264z 908868z 9093B8z 8BBD4Cz 8BE768z AFC544z AFD67Cz AFE838z B01DECz 5E6FC4z 5E73D0z 52E448z 52B028z 52B028z 52E510z
    * 5 Mar 10:33:30.031: aggr_params Assertion failed-> tcp_pkts_pending_aggr in dot11_ac_test_ready to 1136
    * 10:33:30.031 Mar 5: Traceback-= 292514z 8B0264z 908868z 9093B8z 8BBD4Cz 8BE768z AFC544z AFD67Cz AFE838z B01DECz 5E6FC4z 5E73D0z 52E448z 52B028z 52B028z 52E510z
    * 18:18:49.611 Mar 5: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (CAPWAP_WTP_EVENT_REQUEST
    ., 4)
    * 18:18:49.623 Mar 5: LWAPP-3-CLIENTERRORLOG %: switch to standalone mode
    * 18:18:49.623 Mar 5: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
    * 18:18:49.623 Mar 5: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 10.126.242.247:5246
    * 18:18:49.667 Mar 5: % FEDS-6-persons with DISABILITIES: Signature of IDS is removed and disabled.
    * 18:18:58.671 Mar 5: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-CAPWAP-CONTROLLER
    * 18:19:08.671 Mar 5: % 3-CAPWAP-ERRORLOG: MWAR selected ' xxxxxxxWLC001'(index 0).
    * 18:19:08.671 Mar 5: % 3-CAPWAP-ERRORLOG: go join a capwap controller
    * 18:18:59.000 Mar 5: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.126.242.247 peer_port: 5246
    * 18:19:05.483 Mar 5: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.126.242.247 peer_port: 5246
    * 18:19:05.487 Mar 5: % CAPWAP-5-SENDJOIN: send request to join 10.126.242.247
    * 18:19:05.559 Mar 5: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
    * 18:19:05.559 Mar 5: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
    * 18:19:05.559 Mar 5: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
    * 18:19:05.559 Mar 5: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 10.126.242.247 capwap
    * 18:19:05.647 Mar 5: "Promiscuous" from Ethernet mode
    * 18:19:06.363 Mar 5: % LWAPP-4-CLIENTEVENTLOG: OfficeExtend Localssid recorded Flash AP
    * 5 Mar 18:19:06.459: ac_first_hop_mac - IP:10.126.134.1 Hop IP:10.126.134.1 IDB:BVI1
    * 18:19:06.459 Mar 5: setting AC hop first MAC: 58f3.9cf2.5781

    * 18:19:06.859 Mar 5: % CAPWAP-5-JOINEDCONTROLLER: AP joined controller xxxxxxxWLC001
    * 18:19:06.907 Mar 5: LWAPP-4-CLIENTEVENTLOG %: No. Flex ACL to load map configuration file. To connect to the controller to get the configuration file
    * 18:19:06.907 Mar 5: LWAPP-4-CLIENTEVENTLOG %: No. Flex ACL to load map configuration file. To connect to the controller to get the configuration file
    * 18:19:06.907 Mar 5: % LWAPP-4-CLIENTEVENTLOG: map No. LS Flex to load ACL configuration file. To connect to the controller to get the configuration file
    * 18:19:06.907 Mar 5: LWAPP-4-CLIENTEVENTLOG %: no central Dhcp configuration file map to load. To connect to the controller to get the configuration file
    * 18:19:06.907 Mar 5: % LWAPP-3-CLIENTERRORLOG: connected mode
    * 18:19:07.323 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 18:19:07.359 Mar 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 18:19:08.327 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
    * 18:19:08.355 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 18:19:08.367 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
    * 18:19:08.375 Mar 5: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
    * 18:19:09.407 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
    * 18:19:09.411 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
    * 18:19:09.587 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
    * 18:19:09.595 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 18:19:09.603 Mar 5: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 18:19:10.595 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
    * 18:19:10.595 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
    * 18:19:10.631 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 18:19:10.639 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
    * 18:19:10.647 Mar 5: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
    * 18:19:10.951 Mar 5: % FEDS-6-ACTIVATED: Signature of IDS is loaded and enabled
    * 18:19:11.631 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
    * 18:19:11.639 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
    * 18:19:11.687 Mar 5: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
    * 18:19:12.687 Mar 5: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
    * 6 Mar 01:03:58.255: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (CAPWAP_WTP_EVENT_REQUEST
    ., 3)
    * 6 Mar 01:03:58.255: % 3-CAPWAP-ERRORLOG: Retransmission count exceeded max, unaware that the ethernet is overloaded
    * 6 Mar 02:28:52.326: aggr_params Assertion failed-> tcp_pkts_pending_aggr in dot11_ac_test_ready to 1136
    * 02:28:52.326 Mar 6: Traceback-= 292514z 8B0264z 908868z 9093B8z 8BBD4Cz 8BE768z AFC544z AFD67Cz AFE838z B01DECz 5E6FC4z 5E73D0z 52E448z 52B028z 52B028z 52E510z
    * 6 Mar 02:28:55.722: aggr_params Assertion failed-> tcp_pkts_pending_aggr in dot11_ac_test_ready to 1136
    * 02:28:55.722 Mar 6: Traceback-= 292514z 8B0264z 908868z 9093B8z 8BBD4Cz 8BE768z AFC544z AFD67Cz AFE838z B01DECz 5E6FC4z 5E73D0z 52E448z 52B028z 52B028z 52E510z
    * 6 Mar 02:28:58.518: aggr_params Assertion failed-> tcp_pkts_pending_aggr in dot11_ac_test_ready to 1136
    * 02:28:58.518 Mar 6: Traceback-= 292514z 8B0264z 908868z 9093B8z 8BBD4Cz 8BE768z AFC544z AFD67Cz AFE838z B01DECz 5E6FC4z 5E73D0z 52E448z 52B028z 52B028z 52E510z
    * 6 Mar 04:48:00.926: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (CAPWAP_ECHO_REQUEST
    ., 3)
    * 6 Mar 04:48:00.938: % LWAPP-3-CLIENTERRORLOG: switch to standalone mode
    * 6 Mar 04:48:00.938: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
    * 6 Mar 04:48:00.938: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 10.126.242.247:5246
    * 6 Mar 04:48:00.986: % FEDS-6-persons with DISABILITIES: Signature of IDS is removed and disabled.
    * 6 Mar 04:48:09.986: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-CAPWAP-CONTROLLER
    * 6 Mar 04:48:19.986: % 3-CAPWAP-ERRORLOG: MWAR selected ' xxxxxxxWLC001'(index 0).
    * 6 Mar 04:48:19.986: % 3-CAPWAP-ERRORLOG: go join a capwap controller
    * 6 Mar 04:48:10.000: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.126.242.247 peer_port: 5246
    * 6 Mar 04:48:10.755: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.126.242.247 peer_port: 5246
    * 6 Mar 04:48:10.755: % CAPWAP-5-SENDJOIN: send request to join 10.126.242.247
    * 6 Mar 04:48:10.831: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
    * 6 Mar 04:48:10.831: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
    * 6 Mar 04:48:10.831: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
    * 6 Mar 04:48:10.831: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 10.126.242.247 capwap
    * 04:48:10.915 Mar 6: "Promiscuous" from Ethernet mode
    * 6 Mar 04:48:11.635: % LWAPP-4-CLIENTEVENTLOG: OfficeExtend Localssid recorded Flash AP
    * 6 Mar 04:48:11.727: ac_first_hop_mac - IP:10.126.134.1 Hop IP:10.126.134.1 IDB:BVI1
    * 04:48:11.727 Mar 6: setting AC hop first MAC: 58f3.9cf2.5781
              
    * 6 Mar 04:48:12.127: % CAPWAP-5-JOINEDCONTROLLER: AP joined controller xxxxxxxWLC001
    * 6 Mar 04:48:12.175: % LWAPP-4-CLIENTEVENTLOG: No. Flex ACL to load map configuration file. To connect to the controller to get the configuration file
    * 6 Mar 04:48:12.175: % LWAPP-4-CLIENTEVENTLOG: No. Flex ACL to load map configuration file. To connect to the controller to get the configuration file
    * 6 Mar 04:48:12.175: % LWAPP-4-CLIENTEVENTLOG: map No. LS Flex to load ACL configuration file. To connect to the controller to get the configuration file
    * 6 Mar 04:48:12.175: LWAPP-4-CLIENTEVENTLOG %: no central Dhcp configuration file map to load. To connect to the controller to get the configuration file
    * 6 Mar 04:48:12.175: % LWAPP-3-CLIENTERRORLOG: connected mode
    * 6 Mar 04:48:12.595: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 6 Mar 04:48:12.599: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 6 Mar 04:48:13.599: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
    * 6 Mar 04:48:13.647: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 6 Mar 04:48:13.659: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
    * 6 Mar 04:48:13.667: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
    * 6 Mar 04:48:14.675: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
    * 6 Mar 04:48:14.675: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
    * 6 Mar 04:48:14.851: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
    * 6 Mar 04:48:14.863: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
    * 6 Mar 04:48:14.871: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 6 Mar 04:48:15.859: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
    * 6 Mar 04:48:15.863: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
    * 6 Mar 04:48:15.899: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
    * 6 Mar 04:48:15.911: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
    * 6 Mar 04:48:15.919: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
    * 6 Mar 04:48:16.223: FEDS-6-ACTIVATED %: Signature of IDS is loaded and enabled
    * 6 Mar 04:48:16.899: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
    * 6 Mar 04:48:16.911: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
    * 6 Mar 04:48:16.959: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
    * 6 Mar 04:48:17.959: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to

    Does anyone have any ideas?

    Thank you very much!

    Aggr_params of failure AP assertion-> tcp_pkts_pending_aggr (no crash)
  • Trouble getting a Cisco 2600 series AP to stay connected to WLC 5508

    Hello

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

    AP, I do the test on:

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

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

    WLC in question:

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

    Product name... Cisco controller

    Version of the product... 7.3.112.0

    Bootloader Version... 1.0.1

    Retrieving Image Version field... 6.0.182.0

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

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

    System name... wificontroller

    Location of the system... Corp

    Contact System... Net engineer

    ObjectID of system... 1.3.6.1.4.1.9.1.1069

    Redundancy mode... People with disabilities

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

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

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

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

    The country is set... USA - United States

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

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

    -Other - or ITU (q)

    ... Internal temperature 38 C

    Outdoor temperature... + 20 C

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

    State of 802. 11 b network... Activated

    State of 802. 11A network... Activated

    Number of wireless LANs... 14

    Number of Active Clients... 71

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

    Power supply 1... Currently, OK

    Power supply 2... Absent

    Maximum number of taken access points supported... 100

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

    WT-4thFlr-AP3 #.

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

    ., 3)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    (. 11).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    WT-4thFlr-AP3 #debug capwap customer event

    Display debugging EVENT customer CAPWAP is on

    WT-4thFlr-AP3 #.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    WT-4thFlr-AP3 #.

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

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

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

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

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

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

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

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

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

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

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

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

    * 15:59:01.831 Dec 14:

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

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

    * 15:59:01.831 Dec 14:

    * 15:59:01.831 Dec 14:

    IE: UNKNOWN IT IS ABOUT 151

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

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

    * 15:59:01.831 Dec 14:

    52 80 46 00 AC

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

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

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

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

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

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

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

    * 15:59:20.931 Dec 14:

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

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

    * 15:59:20.931 Dec 14:

    * 15:59:20.931 Dec 14:

    IE: RRM_NEIGHBOR_CTRL_PAYLOAD

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

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

    * 15:59:20.931 Dec 14:

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

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

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

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

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

    01 01 01

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

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

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

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

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

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

    * 15:59:20.931 Dec 14:

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

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

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

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

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

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

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

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

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

    * 15:59:21.139 Dec 14:

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

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

    * 15:59:21.139 Dec 14:

    * 15:59:21.139 Dec 14:

    IE: RRM_NEIGHBOR_CTRL_PAYLOAD

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

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

    * 15:59:21.143 Dec 14:

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

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

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

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

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

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

    01 01 01 01 01

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

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

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

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

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

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

    * 15:59:21.143 Dec 14:

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

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

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

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

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

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

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

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

    * 15:59:25.547 Dec 14:

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

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

    * 15:59:25.547 Dec 14:

    * 15:59:25.547 Dec 14:

    IE: RRM_LOAD_DATA_PAYLOAD

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    * 15:59:25.795 Dec 14:

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

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

    * 15:59:25.795 Dec 14:

    * 15:59:25.795 Dec 14:

    IE: RRM_LOAD_DATA_PAYLOAD

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    * 15:59:30.375 Dec 14:

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

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

    SlotId: 0

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

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

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

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

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

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

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

    * 15:59:30.379 Dec 14:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    * 16:00:00.395 Dec 14:

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

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

    * 16:00:00.395 Dec 14:

    * 16:00:00.395 Dec 14:

    IE: UNKNOWN IT IS ABOUT 151

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

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

    * 16:00:00.395 Dec 14:

    52 80 81 00 AC

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

    Try reducing the mtu on ap 2600.

  • Help to set up a WLC2100

    Hello!

    I'm new to a wirelless world and my manager give me work to set up a wlc2100 and join an air lap1242g to the controller, so the problem is that I have configured the wlc connectivity and one have access to the browser web wlc... Next I configure a dhcp pool in my dhcp server and the lap1242 to connect to the network find the wlc but cannot join the wlc get ip.

    Please can someone help me?

    NEWSPAPERS

    LAP1242:****************************************************************************

    * 12:20:35.839 Feb 23: level 0 adjusted on the slot 1 to 140 power chan

    * 12:20:48.841 Feb 23: % 3-CAPWAP-ERRORLOG: go join a capwap controller

    * 12:20:49.000 Feb 23: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.50.51 peer_port: 5246

    * 12:20:50.688 Feb 23: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.10.50.51 peer_port: 5246

    * 12:20:50.690 Feb 23: % CAPWAP-5-SENDJOIN: send request to join 10.10.50.51

    * 12:20:50.690 Feb 23: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

    * 12:20:50.773 Feb 23: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

    * 12:20:50.775 Feb 23: % DTLS-5-ALERT: WARNING received: close notify alert from 10.10.50.51

    * 12:20:50.775 Feb 23: % DTLS-5-PEER_DISCONNECT: Peer 10.10.50.51 has closed the connection.

    * 12:20:50.775 Feb 23: % DTLS-5-SEND_ALERT: send WARNING: close notify alert at 10.10.50.51

    * 12:20:50.820 Feb 23: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 12:20:50.820 Feb 23: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 12:20:50.830 Feb 23: level 0 adjusted on slot 0 for 13 power chan

    * 12:20:50.830 Feb 23: level 0 adjusted on the slot 1 to 140 power chan

    * 12:21:03.831 Feb 23: % 3-CAPWAP-ERRORLOG: go join a capwap controller

    * 12:21:03.000 Feb 23: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.50.51 peer_port: 5246

    * 12:21:04.692 Feb 23: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.10.50.51 peer_port: 5246

    * 12:21:04.693 Feb 23: % CAPWAP-5-SENDJOIN: send request to join 10.10.50.51

    * 12:21:04.693 Feb 23: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

    * 12:21:04.777 Feb 23: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

    * 12:21:04.779 Feb 23: % DTLS-5-ALERT: WARNING received: close notify alert from 10.10.50.51

    * 12:21:04.779 Feb 23: % DTLS-5-PEER_DISCONNECT: Peer 10.10.50.51 has closed the connection.

    * 12:21:04.780 Feb 23: % DTLS-5-SEND_ALERT: send WARNING: close notify alert at 10.10.50.51

    * 12:21:04.823 Feb 23: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 12:21:04.824 Feb 23: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 12:21:04.833 Feb 23: level 0 adjusted on slot 0 for 13 power chan

    * 12:21:04.833 Feb 23: level 0 adjusted on the slot 1 to 140 power chan

    * 12:21:17.835 Feb 23: % 3-CAPWAP-ERRORLOG: go join a capwap controller

    * 12:21:18.000 Feb 23: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.50.51 peer_port: 5246

    ===========================================================================================

    See the (cisco Controller) > logging

    Logging to the buffer:

    -Buffer system message logging:

    -Logging filter level... Errors

    -Number of logged system messages... 137805

    -Number of messages fell system... 42720

    -Saving debugging messages for stamp... People with disabilities

    -Number of connected debug messages... 0

    -Number of debugging messages dropped... 0

    By connecting to the console:

    -Registration system to the console messages:

    -Logging filter level... Errors

    -Number of logged system messages... 0

    -Number of messages fell system... 180525

    -Saving debugging messages to console... Activated

    -Number of connected debug messages... 0

    -Number of debugging messages dropped... 0

    Logging into syslog:

    -Installation of Syslog... local0

    -Logging system in syslog messages:

    -Logging filter level... Errors

    -Number of logged system messages... 137805

    -Other - or ITU (q)

    -Number of messages fell system... 42720

    -Saving debugging in syslog messages... People with disabilities

    -Number of connected debug messages... 0

    -Number of debugging messages dropped... 0

    -Number of remote syslog hosts... 0

    - Host 0....................................... Not configured

    - Host 1....................................... Not configured

    - Host 2....................................... Not configured

    Logging tracing... Activated

    -Record tracing level... Errors

    Saving process information... Activated

    Save the file to the source of information... Activated

    Timestamp of messages...

    -Timestamp of the system messages... Activated

    -Timestamp format... Date and time

    -Timestamp of the debug messages... Activated

    -Timestamp format... Date and time

    Logging buffer (137805 connected, 42720 abandoned)

    * 13:22:00.769 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:22:00.767 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    -Other - or ITU (q)

    * 13:22:00.767 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:22:00.686 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:21:45.319 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:21:45.318 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    * 13:21:45.318 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    Previous message has happened 2 times.

    * 13:21:45.317 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:21:45.236 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:21:30.492 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:21:30.490 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    * 13:21:30.490 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:21:30.409 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:21:15.669 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:21:15.668 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    * 13:21:15.668 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:21:15.586 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:21:00.838 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:21:00.837 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    * 13:21:00.836 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:21:00.756 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    -Other - or ITU (q)

    * 13:20:46.012 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:20:46.010 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    * 13:20:46.010 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:20:45.928 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:20:31.175 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:20:31.173 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    * 13:20:31.173 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:20:31.092 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:20:16.346 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:20:16.345 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    * 13:20:16.344 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:20:16.262 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:20:01.519 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:20:01.518 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    * 13:20:01.517 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:20:00.811 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:19:46.063 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:19:46.062 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    -Other - or ITU (q)

    * 13:19:46.061 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:19:45.979 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:19:31.236 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:19:31.235 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    * 13:19:31.234 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:19:31.154 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:19:16.407 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:19:16.406 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message has happened 2 times.

    * 13:19:16.406 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:19:16.405 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:19:16.324 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:19:01.582 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:19:01.580 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    * 13:19:01.580 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:19:01.499 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:18:46.748 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:18:46.746 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    * 13:18:46.746 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:18:46.664 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    -Other - or ITU (q)

    * 13:18:31.923 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:18:31.922 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    * 13:18:31.922 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    Previous message has happened 2 times.

    * 13:18:31.921 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:18:31.841 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:18:17.087 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:18:17.086 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    * 13:18:17.085 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:18:16.379 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:18:01.636 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:18:01.634 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    * 13:18:01.634 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:18:01.554 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:17:46.814 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:17:46.813 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    * 13:17:46.813 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    Previous message has happened 2 times.

    * 13:17:46.812 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:17:46.731 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:17:31.989 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    -Other - or ITU (q)

    * 13:17:31.987 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    * 13:17:31.987 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:17:31.906 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:17:17.151 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:17:17.149 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    * 13:17:17.149 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:17:17.067 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:17:02.320 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:17:02.319 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    * 13:17:02.319 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:17:02.238 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:16:47.495 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:16:47.493 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Previous message occurred 3 times.

    * 13:16:47.493 Feb 23: LWAPP-3-RD_ERR7%: spam_lrad.c:9097 invalid country code (for AP 00: 3A): 98:47:c2:30

    * 13:16:47.411 Feb 23: RRM-3-RRM_LOGMSG %: rrmChanUtils.c:291 JOURNAL of MRR: Airewave Director: did not find lists of valid channel for 802.11bg

    * 13:16:32.664 Feb 23: % 3-CAPWAP-POST_DECODE_ERR: decode the capwap_ac_sm.c:3945 Post processing failed for the Config of AP 00: 3A status: 98:47:c2:30

    * 13:16:32.662 Feb 23: % LWAPP-3-RD_ERR4: field of Regulation No valid capwap_ac_sm.c:2239 802.11bg:-a 802. 11A:-A for the AP 00: 3A: 98:47:c2:30

    Try this... go wireless-> country-> select the country for your AP and reboot... see if it works...

  • New radio connect WLC for 60 seconds, then plug it back

    I have a 5508 with sw 7.0.98, I have 30 3500 ap connected mode local inn. When you connect a 1142ap on a remote site, the radio to connect the controller download sw stay there for about 40 to 90 seconds, the reconect. Another site remote against the same controller, is everything is ok.

    Journal

    / * Style definitions * / table. MsoNormalTable {mso-style-name: "Table Normal" "; mso-knew-rowband-size: 0; mso-knew-colband-size: 0; mso-style - noshow:yes; mso-style-priority: 99; mso-style-parent:" ";" mso-padding-alt: 0 cm 0 cm 5.4pt 5.4pt; mso-para-margin: 0 cm; mso-para-margin-bottom: .0001pt; mso-pagination: widow-orphan; do-size: 10.0pt; do-family: "Times New Roman", "serif" ;} "}

    * 08:05:20.997 17 August: % FEDS-6-persons with DISABILITIES: Signature of IDS is removed and disabled.
    * 08:05:20.998 17 August: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY
    * 08:05:30.998 17 August: % 3-CAPWAP-ERRORLOG: go join a capwap controller
    * 08:05:31.000 17 August: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.160.10 peer_port: 5246
    * 08:05:31.000 17 August: % CAPWAP-5-CHANGED: CAPWAP changed State to
    * 08:05:31.890 17 August: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 192.168.160.10 peer_port: 5246

    * 08:05:31.891 17 August: % CAPWAP-5-SENDJOIN: send request to join 192.168.160.10
    * 08:05:31.891 17 August: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE
    * 08:05:32.052 17 August: % CAPWAP-5-CHANGED: CAPWAP changed state CFG
    * 08:05:32.195 17 August: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 08:05:32.203 17 August: % CAPWAP-5-CHANGED: CAPWAP changed State to UP
    * 08:05:32.212 17 August: LWAPP-3-CLIENTEVENTLOG %: OfficeExtend Localssid recorded Flash AP
    * 08:05:32.382 17 August: % CAPWAP-5-JOINEDCONTROLLER: AP joined controller H1-WLC01-R132
    * 08:05:32.402 17 August: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to
    * 08:05:32.411 17 August: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
    * 08:05:32.436 17 August: LWAPP-3-CLIENTEVENTLOG %: connected mode
    * 08:05:32.437 17 August: % LWAPP-3-CLIENTEVENTLOG: SSID Statnett_Guest added to location [0]
    * 08:05:32.452 17 August: % DOT11-6-DFS_SCAN_START: DFS: scanning frequency 5680 MHz for 60 seconds.
    * 08:05:32.461 17 August: % LINK-3-UPDOWN: Interface Dot11Radio1, changed State to
    * 08:05:32.461 17 August: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 08:05:32.462 17 August: % LWAPP-3-CLIENTEVENTLOG: SSID Statnett_Ansatt added to location [0]
    * 08:05:32.601 17 August: % LWAPP-3-CLIENTEVENTLOG: SSID Statnett-VPN added to location [0]
    * 08:05:32.626 17 August: % LWAPP-3-CLIENTEVENTLOG: SSID Statnett_Guest added to location [1]
    * 08:05:32.642 17 August: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to
    * 08:05:32.646 17 August: % LWAPP-3-CLIENTEVENTLOG: SSID Statnett_Ansatt added to location [1]
    * 08:05:32.686 17 August: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
    * 08:05:32.702 17 August: % DOT11-6-DFS_SCAN_START: DFS: scanning frequency 5680 MHz for 60 seconds.
    * 08:05:32.703 17 August: % LINK-3-UPDOWN: Interface Dot11Radio1, changed State to
    * 08:05:34.077 17 August: % LWAPP-3-CLIENTEVENTLOG: SSID Statnett-VPN added to location [1]
    * 08:05:34.261 17 August: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
    * 08:05:34.277 17 August: % DOT11-6-DFS_SCAN_START: DFS: scanning frequency 5680 MHz for 60 seconds.
    * 08:05:34.286 17 August: % LINK-3-UPDOWN: Interface Dot11Radio1, changed State to
    * 08:05:34.287 17 August: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 08:05:34.303 17 August: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to
    * 08:05:34.388 17 August: FEDS-6-ACTIVATED %: Signature of IDS is loaded and enabled
    * 08:06:34.642 17 August: % DOT11-6-DFS_SCAN_COMPLETE: DFS scan complete on frequency 5680 MHz
    * 08:06:50.970 17 August: % 3-CAPWAP-ERRORLOG: Retransmission of packets exceeded max (. CAPWAP_ECHO_REQUEST, 3)
    * 08:06:50.971 17 August: LWAPP-3-CLIENTEVENTLOG %: switch to standalone mode
    * 08:06:50.971 17 August: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
    * 08:06:50.971 17 August: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 192.168.160.10:5246

    How many aPs are allowed on the WLC and how much is currently been met?

  • Amount of access points allowed on a 4402 (50 PA)?

    We habe a WLC 4402 race (SW Version 6.0.196.0) which is supposed to support access 50 points.

    It is a solution of WLAN of comments with 2 Wireless LANs that are tunneled through the FW to a WLC anchor that leads to the internet and 1 WLAN which is directly lead to the corporate network.

    For the moment, I have attached... access 47 points and my problem is, I can't tie up more than that.

    I tried to take one of the 47 offline and then I could attached a new. But the limit seems to be 47.

    What can be the reason why 3 AP licenses are taken?

    Here is the log of the AP, which tries to connect:

    * 09:38:15.711 Mar 23: % 3-CAPWAP-ERRORLOG: go join a capwap controller
    * 09:38:15.000 Mar 23: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.132.193 peer_port: 5246
    * 09:38:15.001 Mar 23: % CAPWAP-5-CHANGED: CAPWAP changed State to
    * 09:38:16.406 Mar 23: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.1.132.193 peer_port: 5246
    * 09:38:16.408 Mar 23: % CAPWAP-5-SENDJOIN: send request to join 10.1.132.193
    * 09:38:16.408 Mar 23: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE
    * 09:38:16.414 Mar 23: % DTLS-5-ALERT: WARNING received: close notify alert from 10.1.132.193
    * 23 Mar 09:38:16.414: % PEER_DISCONNECT-5-DTLS: Peer 10.1.132.193 has closed the connection.
    * 09:38:16.414 Mar 23: % DTLS-5-SEND_ALERT: send WARNING: close notify alert at 10.1.132.193:5246
    * 09:38:16.685 Mar 23: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY
    * 09:38:16.686 Mar 23: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY
    * 09:38:16.700 Mar 23: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
    * 09:38:16.700 Mar 23: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
    * 09:38:16.714 Mar 23: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to
    * 09:38:16.714 Mar 23: % LINK-3-UPDOWN: Interface Dot11Radio1, changed State to
    * 09:38:16.716 Mar 23: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
    * 09:38:16.745 Mar 23: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to
    * 09:38:16.746 Mar 23: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
    * 09:38:26.713 Mar 23: % 3-CAPWAP-ERRORLOG: go join a capwap controller

    Here is the log of the WLC:

    * 23 10:55:18.314 Mar: 00: 3A: 98:1 c: 50:60 join RESP: failed to encode the IPV4 of CAPWAP control address
    * 23 10:55:18.314 Mar: 00: 3A: 98:1 c: 50:60 failed code the response to 10.3.8.240:64388 join
    * 23 10:55:18.316 Mar: 00: 3A: 98:1 c: 50:60 Config response failure: failed to send response to join to 10.3.8.240:64388
    * 23 10:55:18.317 Mar: 00: 3A: 98:1 c: State 50:60 machine Manager: failed to process the msg = 3 State = 0 10.3.8.240:64388 type
    * 23 10:55:18.317 Mar: 00: 3A: 98:1 c: 50:60 impossible to analyze packets 10.3.8.240:64388 CAPWAP
    (* 23 10:55:18.320 Mar: 00: 3A: 98:1 c: 50:60 throw no - ClientHello Handshake or DTLS encrypted package to 10.3.8.240:64388) since DTLS session is not established
    * 23 10:55:18.399 Mar: 00: 3A: 98:1 c: 50:60 join priority Processing status = 0, priority 1 of incoming Ap, MaxLrads = 50, joined Aps = 47

    Hello

    Here is the bug, I guess that we are hitting... If please run the workaround and let me know if it works...

    http://Tools.Cisco.com/support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtf57349

    Let me know if this answers your question!

    Concerning

    Surendra

  • Cisco AIR-LAP1041N-E-K9 does not not with WLC 4402 version 7.0.116.0

    Hi all

    appreciate your support for a problem I started to deal with today. I have a Cisco WLC 4402 running the 7.0.116.0 version and it's great to work with 25 Cisco 1252 access points. We received a new 20 Cisco 1041N APs today and I installed one in our site, but it does not work. He well worked and loaded the flash image and obtained WLC ip through DHCP option address and began to show the below error:

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

    * 00:00:10.033 Mar 1: * CRASH_LOG = YES

    * 00:00:10.333 Mar 1: 1 Port is not presentSecurity base.

    MAC Ethernet address of base: C8:9 C: 1 D: 53:57:5E

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

    * 00:00:11.465 Mar 1: % LWAPP-3-CLIENTEVENTLOG: reading and initialized AP event log (contains, 1088 messages)

    * 00:00:11.494 Mar 1: State of the voice_diag_test of WLC is false

    * 00:00:12.526 Mar 1: % LINK-3-UPDOWN: Interface GigabitEthernet0, changed State to

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

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

    Cisco IOS software, software C1040 (C1140-K9W8-M), Version 12.4 (23 c) JA2, VERSION of the SOFTWARE (fc3)

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

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

    Updated Thursday, April 13, 11 12:50 by prod_rel_team

    * 00:00:13.647 Mar 1: % SNMP-5-start COLD: SNMP agent on host APc89c.1d53.575e knows a cold start

    * 00:08:59.062 Mar 1: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 1 Mar 00:08:59.062: bsnInitRcbSlot: slot 1 has NO radio

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

    * 00:08:59.837 Mar 1: % SSH-5-ACTIVATED: SSH 2.0 has been activated

    * 00:09:00.145 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

    * 00:09:09.136 Mar 1: % ADDRESS_ASSIGN-6-DHCP: Interface GigabitEthernet0 assigned address DHCP 172.16.26.81, mask 255.255.255.0, hostname APc89c.1d53.575e

    * 00:09:17.912 Mar 1: % PARSER-4-BADCFG: unexpected end of the configuration file.

    * 00:09:17.912 Mar 1: State of the voice_diag_test of WLC is false

    * 00:09:17.984 Mar 1: message logging LWAPP to 255.255.255.255.

    * 00:09:19.865 Mar 1: % CDP_PD-4-POWER_OK: full power - supply NEGOTIATED online

    * 00:09:19.886 Mar 1: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to

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

    * 00:09:20.874 Mar 1: % SYS-6-LOGGINGHOST_STARTSTOP: logging to host started 255.255.255.255 - initiated CLI

    Translate "CISCO-CAPWAP - CONTROLLER.atheertele.com"... the domain server (172.16.40.240)

    * 00:09:29.029 Mar 1: % CAPWAP-5-DHCP_OPTION_43: the 172.16.100.102 drive address obtained by DHCP

    * 08:27:02.000 may 25: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.100.101 peer_port: 5246

    * 08:27:02.001 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to

    * 08:27:03.175 may 25: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.100.101 peer_port: 5246

    * 08:27:03.177 may 25: % CAPWAP-5-SENDJOIN: send request to join 172.16.100.101

    * 08:27:03.177 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

    * 08:27:03.329 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

    * 08:27:03.333 may 25: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.100.101

    * 25 May 08:27:03.333: % PEER_DISCONNECT-5-DTLS: Peer 172.16.100.101 has closed the connection.

    * 08:27:03.333 may 25: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.100.101:5246

    * 08:27:03.378 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 08:27:03.378 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 25 May 08:27:03.378: bsnInitRcbSlot: slot 1 has NO radio

    * 25 May 08:27:03.448: State of the voice_diag_test of WLC is false

    * 08:27:14.000 may 25: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.100.101 peer_port: 5246

    * 08:27:14.001 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to

    * 08:27:15.185 may 25: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.100.101 peer_port: 5246

    * 08:27:15.186 may 25: % CAPWAP-5-SENDJOIN: send request to join 172.16.100.101

    * 08:27:15.186 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

    * 08:27:15.330 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

    * 08:27:15.333 may 25: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.100.101

    * 25 May 08:27:15.334: % PEER_DISCONNECT-5-DTLS: Peer 172.16.100.101 has closed the connection.

    * 08:27:15.334 may 25: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.100.101:5246

    * 08:27:15.379 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 08:27:15.379 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 25 May 08:27:15.379: bsnInitRcbSlot: slot 1 has NO radio

    * 25 May 08:27:15.450: State of the voice_diag_test of WLC is false

    * 08:27:26.000 may 25: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.100.101 peer_port: 5246

    * 08:27:26.001 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to

    * 08:27:27.182 may 25: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.100.101 peer_port: 5246

    * 08:27:27.183 may 25: % CAPWAP-5-SENDJOIN: send request to join 172.16.100.101

    * 08:27:27.184 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

    * 08:27:27.329 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

    * 08:27:27.333 may 25: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.100.101

    * 25 May 08:27:27.333: % PEER_DISCONNECT-5-DTLS: Peer 172.16.100.101 has closed the connection.

    * 08:27:27.333 may 25: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.100.101:5246

    * 08:27:27.377 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 08:27:27.377 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 25 May 08:27:27.377: bsnInitRcbSlot: slot 1 has NO radio

    * 08:27:27.433 may 25: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

    * 08:27:27.446 may 25: % PARSER-4-BADCFG: unexpected end of the configuration file.

    * 25 May 08:27:27.447: State of the voice_diag_test of WLC is false

    * 08:27:27.448 may 25: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to

    * 08:27:27.456 may 25: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

    * 08:27:38.000 may 25: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.100.101 peer_port: 5246

    * 08:27:38.001 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to

    * 08:27:39.183 may 25: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.100.101 peer_port: 5246

    * 08:27:39.184 may 25: % CAPWAP-5-SENDJOIN: send request to join 172.16.100.101

    * 08:27:39.184 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

    * 08:27:39.326 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

    * 08:27:39.329 may 25: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.100.101

    * 25 May 08:27:39.329: % PEER_DISCONNECT-5-DTLS: Peer 172.16.100.101 has closed the connection.

    * 08:27:39.330 may 25: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.100.101:5246

    * 08:27:39.375 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 08:27:39.375 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 25 May 08:27:39.375: bsnInitRcbSlot: slot 1 has NO radio

    * 25 May 08:27:39.446: State of the voice_diag_test of WLC is false

    * 08:27:49.000 may 25: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.100.101 peer_port: 5246

    * 08:27:49.001 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to

    * 08:27:50.179 may 25: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.100.101 peer_port: 5246

    * 08:27:50.180 may 25: % CAPWAP-5-SENDJOIN: send request to join 172.16.100.101

    * 08:27:50.180 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

    * 08:27:50.323 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

    * 08:27:50.326 may 25: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.100.101

    * 25 May 08:27:50.326: % PEER_DISCONNECT-5-DTLS: Peer 172.16.100.101 has closed the connection.

    * 08:27:50.326 may 25: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.100.101:5246

    * 08:27:50.370 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 08:27:50.370 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 25 May 08:27:50.370: bsnInitRcbSlot: slot 1 has NO radio

    * 08:27:50.425 may 25: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

    * 08:27:50.438 may 25: % PARSER-4-BADCFG: unexpected end of the configuration file.

    I searched the difference in regulatory areas between AIR-LAP1041N -E- K9 and AIR-LAP1041N -A- K9 and no difference was found which may affect the operation of this access point.
    to cite our WLC configuration for regulatory areas is:
    Country set AR codes
     
    Area of regulation 802. 11A:-A
    802.11bg:-a
    My question is should I just include my country in the WLC (IQ) add the field of requlatry (-E) to solve this problem? or change the country will affect the operation of all APs workers?
    Appreciate your kind support,
    Patrick Q.

    Try adding a European country to your regulatory domain.

  • Problem with WISN LAP-1131 and Cisco

    Hello

    I have a Cisco WISN running the 7.0.116.0 version and it works very well with a lot of access Cisco 1131/1232/1242 points. But with one I have a problem. He has worked and loaded the flash image and got the ip address controller and began to show the below error:

    * 12:26:40.001 June 8: % CAPWAP-5-CHANGED: CAPWAP changed State to

    * 12:26:41.386 June 8: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.23.2.244 peer_port: 526

    * 12:26:41.388 June 8: % CAPWAP-5-SENDJOIN: send request to join 172.23.2.244

    * 12:26:41.388 June 8: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

    * 12:26:41.577 June 8: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

    * 12:26:41.583 June 8: % DTLS-5-ALERT: WARNING received: close notify alert from 172.23.2.244

    * 12:26:41.583 June 8: % DTLS-5-PEER_DISCONNECT: Peer 172.23.2.244 has closed the connection.

    * 12:26:41.583 June 8: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.23.2.244:5246

    * 12:26:42.270 June 8: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 12:26:42.271 June 8: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 12:26:42.340 June 8: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

    * 12:26:42.340 June 8: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively

    * 12:26:42.341 June 8: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to

    * 12:26:42.370 June 8: State of WLC voice_diag_test is false

    * 12:26:42.371 June 8: % LINK-3-UPDOWN: Interface Dot11Radio1, changed State to

    * 12:26:42.372 June 8: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to down

    * 12:26:42.377 June 8: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

    * 12:26:42.398 June 8: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to

    * 12:26:53.000 June 8: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.23.2.244 peer_port: 5246

    * 12:26:53.001 June 8: % CAPWAP-5-CHANGED: CAPWAP changed State to

    * 12:26:54.389 June 8: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.23.2.244 peer_port: 526

    * 12:26:54.390 June 8: % CAPWAP-5-SENDJOIN: send request to join 172.23.2.244

    * 12:26:54.390 June 8: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

    * 12:26:54.577 June 8: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

    * 12:26:54.584 June 8: % DTLS-5-ALERT: WARNING received: close notify alert from 172.23.2.244

    * 12:26:54.584 June 8: % DTLS-5-PEER_DISCONNECT: Peer 172.23.2.244 has closed the connection.

    * 12:26:54.584 June 8: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.23.2.244:5246

    * 12:26:54.642 June 8: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 12:26:54.642 June 8: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 12:26:54.738 June 8: State of WLC voice_diag_test is false

    * 12:27:05.000 June 8: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.23.2.244 peer_port: 5246

    * 12:27:05.001 June 8: % CAPWAP-5-CHANGED: CAPWAP changed State to

    * 12:27:06.384 June 8: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.23.2.244 peer_port: 526

    * 12:27:06.385 June 8: % CAPWAP-5-SENDJOIN: send request to join 172.23.2.244

    * 12:27:06.385 June 8: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

    * 12:27:06.569 June 8: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

    * 12:27:06.574 June 8: % DTLS-5-ALERT: WARNING received: close notify alert from 172.23.2.244

    * 12:27:06.574 June 8: % DTLS-5-PEER_DISCONNECT: Peer 172.23.2.244 has closed the connection.

    * 12:27:06.575 June 8: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.23.2.244:5246

    * 12:27:06.635 June 8: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 12:27:06.636 June 8: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

    * 12:27:06.704 June 8: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

    * 12:27:06.705 June 8: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively

    * 12:27:06.706 June 8: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to

    * 12:27:06.735 June 8: State of WLC voice_diag_test is false

    * 12:27:06.735 June 8: % LINK-3-UPDOWN: Interface Dot11Radio1, changed state

    Thank you, Vincent a.

    Edit:

    When I look on the controller message logs, I see this line:

    * apfMsConnTask_0: 16:04:47.822 Jun 08: % LOG-6-Q_IND: spam_lrad.c:1517 application discovery elements in LWAPP 00:23:33:78:df:80 AP supporting CAPWAP

    Hi Vincent,.

    in this case, if the regulatory domain of the APs is different, consider that the WLC accept associations from the country set APs:

    http://www.Cisco.com/en/us/docs/wireless/controller/7.0/Configuration/Guide/c70lwap.html#wpxref84219

    You will see this in him debugs I sent you before.

    So, if you manage APs EI (ETSI, European) and - a (FCC, US) APs on the same WLC, you need to enable at least two country codes, one for each regulatory domain.

    Please also remember that the APs should be used on the countries they have been approved to in order to comply with local regulations.

    Thank you

    Federico

  • DistributedMember is null in the implementation of the Interface Authenticator?

    DistributedMember is null in the implementation of the authenticator Interface.

    http://www.gemstone.com/docs/current/product/docs/JAPI/com/gemstone/GemFire/security/authenticator.html

    Main authenticate (Properties props, DistributedMember member)

    Check the credentials provided in the properties for the client/peer such as specified in the Member ID and returns the main partner of the customer/peer

    I'm trying to implement authentication. I DistributedMember object as null in the newspapers of Locator when counterpart try to join the distributed system.

    Even if I take the method AuthenticationFailedException authenticate; my Member is still able to join the system of Distribuyed. It's somehow connected to locator * .dat file?

    Messages processed on the thread "UDP incoming Message Handler" are messages of closure of the process itself.  I looked at the code that calls the authenticator and it always affects the null member ID in this case.  I don't know why, but it's what he does.  In addition, in this case it deals a membership VIEW and not a request to join the system.

    You can safely ignore the requests with a null member ID.

    The client authentication is not handled by the Locator well - it is managed by the cache servers when the client tries to connect to them.  Only process GemFire "peer" are authenticated by locators.

    I hope this helps.  I shall notify the Department tech pubs on this subject so that they can update the documentation.

Maybe you are looking for