<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: 2702 AP logs in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/2702-ap-logs/m-p/4853863#M257063</link>
    <description>&lt;P&gt;&lt;STRONG&gt;--Radio Resets:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;If there is no indication of interference (as Prime shows) what&amp;nbsp;&lt;SPAN&gt;environmental factors, or configuration problems could be causing the radio interfaces to reset?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Easy Admin Service&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;AP EasyAdmin ............................... Disable&lt;/P&gt;&lt;P&gt;So I don't know why an AP should have a problem from AP Easy Admin if it is disabled&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;-DHCP IP Renewal and Controller Discovery&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;We are using DNS as a discovery mechanism. What i know is: no other AP had a like problem&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;--Certificate Issues:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I think this is about 2702 APs that can't join the WLC after the 4th of December&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;--CleanAir State Changes:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;If there is no indication of interference, what could&amp;nbsp;&lt;SPAN&gt;environmental factors affecting the AP's performance be?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;--WIDS (Wireless Intrusion Detection System) Alarms:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;We have about 1000 APs and if i am not wrong all of them are sending logs about these "Attacks". How to decide what is an attack and what is a&amp;nbsp;&lt;SPAN&gt;false positive?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;--Hardware Random Number Generator ('HW TRNG') Failure:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I did restart the AP and will have an eye on it to see if these logs come again!&lt;/P&gt;</description>
    <pubDate>Tue, 13 Jun 2023 13:30:59 GMT</pubDate>
    <dc:creator>Moudar</dc:creator>
    <dc:date>2023-06-13T13:30:59Z</dc:date>
    <item>
      <title>2702 AP logs</title>
      <link>https://community.cisco.com/t5/wireless/2702-ap-logs/m-p/4853690#M257053</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I got this AP who did restarted CAPWAP on its own. That was very disruptive to clients!&amp;nbsp;&lt;/P&gt;&lt;P&gt;uptime is 29 weeks, 1 day, 21 hours, 14 minutes.&lt;/P&gt;&lt;P&gt;What can the problem be?&lt;/P&gt;&lt;P&gt;AP 2702, WLC 5520 running&amp;nbsp;8.10.181.3&lt;/P&gt;&lt;P&gt;Logs:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;*Jun 13 06:57:56.431: Failed to read from HW TRNG

*Jun 13 06:57:56.431: HW TRNG failed!

*Jun 13 07:26:04.995: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.0.0.148:5246
*Jun 13 07:26:04.999: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 27
*Jun 13 07:26:04.999: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 27
*Jun 13 07:26:04.999: %WIDS-6-DISABLED: IDS Signature is removed and disabled.
*Jun 13 07:26:05.063: %CAPWAP-5-AP_EASYADMIN_INFO: AP Easy Admin information - EASY_ADMIN is not set, turn off easy admin service!

*Jun 13 07:26:05.063: %CAPWAP-5-AP_EASYADMIN_INFO: AP Easy Admin information - Easy Admin is not enabled, turn it off!

*Jun 13 07:26:05.087: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 39
*Jun 13 07:26:05.087: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 39
*Jun 13 07:26:05.099: %CLEANAIR-6-STATE: Slot 0 down
*Jun 13 07:26:05.103: %CLEANAIR-6-STATE: Slot 1 down
*Jun 13 07:26:05.103: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Jun 13 07:26:05.103: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Jun 13 07:26:05.103: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 10
*Jun 13 07:26:05.107: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jun 13 07:26:05.711: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 10
*Jun 13 07:26:05.739: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jun 13 07:26:06.103: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jun 13 07:26:06.131: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Jun 13 07:26:06.139: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Jun 13 07:26:07.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jun 13 07:26:07.131: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Jun 13 07:26:07.167: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jun 13 07:26:07.179: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jun 13 07:26:07.187: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jun 13 07:26:08.167: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Jun 13 07:26:08.179: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jun 13 07:26:08.207: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jun 13 07:26:09.207: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jun 13 07:26:26.211: %LWAPP-3-CLIENTERRORLOG: Not sending the Delete mobile payload for 7C:50:79:E1:F9:24. CAPWAP State is not RUN

*Jun 13 07:26:55.743: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Jun 13 07:26:58.815: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.2.7.14, mask 255.255.255.0, hostname MST-Ullervad-Hus-A-Trapp-201-Ny

*Jun 13 07:27:06.743: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.0.0.147 obtained through DHCP
*Jun 13 07:27:06.743: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.0.0.148 obtained through DHCP
*Jun 13 07:27:16.747: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*Jun 13 07:27:17.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.0.0.148 peer_port: 5246
*Jun 13 07:27:17.223: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.0.0.148 peer_port: 5246
*Jun 13 07:27:17.223: %CAPWAP-5-SENDJOIN: sending Join Request to 10.0.0.148
*Jun 13 07:27:22.223: %CAPWAP-5-SENDJOIN: sending Join Request to 10.0.0.148
*Jun 13 07:27:22.307: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 56
*Jun 13 07:27:22.311: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jun 13 07:27:22.319: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jun 13 07:27:22.939: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 56
*Jun 13 07:27:22.943: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 10
*Jun 13 07:27:22.947: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller 5520New
*Jun 13 07:27:22.955: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jun 13 07:27:23.119: %WIDS-6-ENABLED: IDS Signature is loaded and enabled%CRYPTO_PKI: Cert not yet valid or is expired -
    start date: 21:36:50 UTC Nov 5 2013
    end   date: 21:36:50 UTC May 20 2022

*Jun 13 07:27:23.127: %DOT11-3-NA_SENSOR_CERT_ERROR: Certificate installation error: Error in saving WSA certificate.
*Jun 13 07:27:23.311: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jun 13 07:27:23.347: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Jun 13 07:27:23.355: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Jun 13 07:27:23.955: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Jun 13 07:27:24.339: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jun 13 07:27:24.391: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jun 13 07:27:24.399: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jun 13 07:27:24.407: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jun 13 07:27:25.391: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Jun 13 07:27:25.399: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jun 13 07:27:25.427: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jun 13 07:27:26.427: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jun 13 07:27:48.499: %CLEANAIR-6-STATE: Slot 0 enabled
*Jun 13 07:27:50.555: %CLEANAIR-6-STATE: Slot 1 enabled
*Jun 13 07:57:56.419: Failed to read from HW TRNG

*Jun 13 07:57:56.419: HW TRNG failed!

*Jun 13 08:29:47.991: %WIDS-4-SIG_ALARM: Attack is detected on Sig:Standard Id:5 Channel:11 Source MAC:089d.f400.f492
*Jun 13 08:29:48.995: %WIDS-4-SIG_ALARM: Attack is detected on Sig:Standard Id:5 Channel:11 Source MAC:089d.f400.f492
*Jun 13 08:49:48.731: %WIDS-6-SIG_ALARM_OFF: Attack is cleared on Sig:Standard Id:5 Channel:11
*Jun 13 08:49:49.735: %WIDS-6-SIG_ALARM_OFF: Attack is cleared on Sig:Standard Id:5 Channel:11
*Jun 13 08:57:56.779: Failed to read from HW TRNG

*Jun 13 08:57:56.779: HW TRNG failed!

*Jun 13 09:28:39.995: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.0.0.148:5246
*Jun 13 09:28:39.999: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 27
*Jun 13 09:28:39.999: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 27
*Jun 13 09:28:39.999: %WIDS-6-DISABLED: IDS Signature is removed and disabled.
*Jun 13 09:28:40.063: %CAPWAP-5-AP_EASYADMIN_INFO: AP Easy Admin information - EASY_ADMIN is not set, turn off easy admin service!

*Jun 13 09:28:40.063: %CAPWAP-5-AP_EASYADMIN_INFO: AP Easy Admin information - Easy Admin is not enabled, turn it off!

*Jun 13 09:28:40.087: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 39
*Jun 13 09:28:40.087: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 39
*Jun 13 09:28:40.099: %CLEANAIR-6-STATE: Slot 0 down
*Jun 13 09:28:40.103: %CLEANAIR-6-STATE: Slot 1 down
*Jun 13 09:28:40.103: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Jun 13 09:28:40.103: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Jun 13 09:28:40.103: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 10
*Jun 13 09:28:40.107: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jun 13 09:28:40.711: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 10
*Jun 13 09:28:40.739: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jun 13 09:28:41.103: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jun 13 09:28:41.131: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Jun 13 09:28:41.139: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Jun 13 09:28:42.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jun 13 09:28:42.131: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Jun 13 09:28:42.167: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jun 13 09:28:42.179: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jun 13 09:28:42.187: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jun 13 09:28:43.167: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Jun 13 09:28:43.179: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jun 13 09:28:43.207: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jun 13 09:28:44.207: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jun 13 09:29:01.215: %LWAPP-3-CLIENTERRORLOG: Not sending the Delete mobile payload for 7C:50:79:E1:F9:24. CAPWAP State is not RUN

*Jun 13 09:29:30.743: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Jun 13 09:29:33.815: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.2.7.14, mask 255.255.255.0, hostname MST-Ullervad-Hus-A-Trapp-201-Ny

*Jun 13 09:29:41.743: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.0.0.147 obtained through DHCP
*Jun 13 09:29:41.743: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.0.0.148 obtained through DHCP
*Jun 13 09:29:51.747: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*Jun 13 09:29:52.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.0.0.148 peer_port: 5246
*Jun 13 09:29:52.219: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.0.0.148 peer_port: 5246
*Jun 13 09:29:52.223: %CAPWAP-5-SENDJOIN: sending Join Request to 10.0.0.148
*Jun 13 09:29:57.219: %CAPWAP-5-SENDJOIN: sending Join Request to 10.0.0.148
*Jun 13 09:29:57.763: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 56
*Jun 13 09:29:57.771: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jun 13 09:29:57.779: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jun 13 09:29:58.395: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 56
*Jun 13 09:29:58.399: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio0 due to the reason code 10
*Jun 13 09:29:58.403: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller 5520New
*Jun 13 09:29:58.411: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jun 13 09:29:58.571: %WIDS-6-ENABLED: IDS Signature is loaded and enabled%CRYPTO_PKI: Cert not yet valid or is expired -
    start date: 21:36:50 UTC Nov 5 2013
    end   date: 21:36:50 UTC May 20 2022

*Jun 13 09:29:58.579: %DOT11-3-NA_SENSOR_CERT_ERROR: Certificate installation error: Error in saving WSA certificate.
*Jun 13 09:29:58.771: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jun 13 09:29:58.807: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Jun 13 09:29:58.815: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Jun 13 09:29:59.411: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Jun 13 09:29:59.799: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jun 13 09:29:59.851: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jun 13 09:29:59.859: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jun 13 09:29:59.867: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jun 13 09:30:00.851: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Jun 13 09:30:00.859: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jun 13 09:30:00.887: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jun 13 09:30:01.887: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jun 13 09:30:21.483: %CLEANAIR-6-STATE: Slot 0 enabled
*Jun 13 09:30:23.539: %CLEANAIR-6-STATE: Slot 1 enabled
*Jun 13 09:57:56.571: Failed to read from HW TRNG

*Jun 13 09:57:56.571: HW TRNG failed!&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jun 2023 10:09:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2702-ap-logs/m-p/4853690#M257053</guid>
      <dc:creator>Moudar</dc:creator>
      <dc:date>2023-06-13T10:09:05Z</dc:date>
    </item>
    <item>
      <title>Re: 2702 AP logs</title>
      <link>https://community.cisco.com/t5/wireless/2702-ap-logs/m-p/4853734#M257057</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/759057"&gt;@Moudar&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Thanks for the output.&lt;/P&gt;&lt;P&gt;It appears that there are a few potential issues that could be causing the AP to restart CAPWAP and disrupt clients.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;--Radio Resets:&lt;/STRONG&gt; The log entries show that the radio interfaces (Dot11Radio0 and Dot11Radio1) are being restarted due to reason codes 27, 39, and 10. These reason codes usually indicate radio interface errors or issues. Check for any interference sources, environmental factors, or configuration problems that could be causing the radio interfaces to reset.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;--Easy Admin Service and IDS Signature:&lt;/STRONG&gt; The log entries mention the Easy Admin service and IDS signature being disabled or not enabled. Review the AP's configuration related to these features to ensure they are correctly configured and not causing any conflicts or issues.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;--DHCP IP Renewal and Controller Discovery:&lt;/STRONG&gt; The AP attempts to renew its DHCP IP address and discovers the WLC addresses through DHCP options. Verify that the DHCP server is functioning properly and providing the correct WLC IP addresses. Ensure that the WLCs are reachable and properly configured.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;--Certificate Issues:&lt;/STRONG&gt; There are some certificate-related errors in the logs, such as certificate expiration and installation errors. Check the AP's certificate configuration and ensure that the certificates are valid and properly installed.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;--CleanAir State Changes:&lt;/STRONG&gt; The CleanAir feature on slot 0 and slot 1 undergoes state changes. This could indicate interference or environmental factors affecting the AP's performance. Investigate any potential sources of interference or environmental changes that might be impacting the AP's operation.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;--WIDS (Wireless Intrusion Detection System) Alarms:&lt;/STRONG&gt; The logs show WIDS alarms related to detected attacks on specific signatures and channels. These alarms could be a result of actual attacks or false positives. Analyze the WIDS alarms further to determine their significance and whether they could be triggering the AP restarts.&lt;/P&gt;&lt;P&gt;Not the least-&amp;nbsp;&lt;STRONG&gt;--Hardware Random Number Generator ('HW TRNG') Failure:&lt;/STRONG&gt;&amp;nbsp;This failure could be a hardware issue with the AP, which might require further investigation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please, check all these points.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jun 2023 10:58:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2702-ap-logs/m-p/4853734#M257057</guid>
      <dc:creator>M02@rt37</dc:creator>
      <dc:date>2023-06-13T10:58:36Z</dc:date>
    </item>
    <item>
      <title>Re: 2702 AP logs</title>
      <link>https://community.cisco.com/t5/wireless/2702-ap-logs/m-p/4853762#M257059</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; - FYI :&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/aironet-3700-series/117869-technote-ap-00.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/aironet-3700-series/117869-technote-ap-00.html&lt;/A&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvs56322" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvs56322&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;But in general and since both aireos and aireos based controllers are getting older consider using&amp;nbsp;&lt;A href="https://software.cisco.com/download/home/286284738/type/280926587/release/8.10.185.0" target="_blank"&gt;https://software.cisco.com/download/home/286284738/type/280926587/release/8.10.185.0&lt;/A&gt;&amp;nbsp; as adviced per&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/200046-tac-recommended-aireos.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/200046-tac-recommended-aireos.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Meaning :&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;U&gt;&lt;FONT color="#008000"&gt;&lt;EM&gt; better is to use the last or latest release that they can run&amp;nbsp; .&amp;nbsp;&lt;/EM&gt;&lt;/FONT&gt;&lt;/U&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jun 2023 11:30:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2702-ap-logs/m-p/4853762#M257059</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2023-06-13T11:30:42Z</dc:date>
    </item>
    <item>
      <title>Re: 2702 AP logs</title>
      <link>https://community.cisco.com/t5/wireless/2702-ap-logs/m-p/4853796#M257061</link>
      <description>&lt;P&gt;I will restart the AP and hope for the best &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jun 2023 12:11:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2702-ap-logs/m-p/4853796#M257061</guid>
      <dc:creator>Moudar</dc:creator>
      <dc:date>2023-06-13T12:11:01Z</dc:date>
    </item>
    <item>
      <title>Re: 2702 AP logs</title>
      <link>https://community.cisco.com/t5/wireless/2702-ap-logs/m-p/4853863#M257063</link>
      <description>&lt;P&gt;&lt;STRONG&gt;--Radio Resets:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;If there is no indication of interference (as Prime shows) what&amp;nbsp;&lt;SPAN&gt;environmental factors, or configuration problems could be causing the radio interfaces to reset?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Easy Admin Service&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;AP EasyAdmin ............................... Disable&lt;/P&gt;&lt;P&gt;So I don't know why an AP should have a problem from AP Easy Admin if it is disabled&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;-DHCP IP Renewal and Controller Discovery&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;We are using DNS as a discovery mechanism. What i know is: no other AP had a like problem&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;--Certificate Issues:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I think this is about 2702 APs that can't join the WLC after the 4th of December&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;--CleanAir State Changes:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;If there is no indication of interference, what could&amp;nbsp;&lt;SPAN&gt;environmental factors affecting the AP's performance be?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;--WIDS (Wireless Intrusion Detection System) Alarms:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;We have about 1000 APs and if i am not wrong all of them are sending logs about these "Attacks". How to decide what is an attack and what is a&amp;nbsp;&lt;SPAN&gt;false positive?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;--Hardware Random Number Generator ('HW TRNG') Failure:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I did restart the AP and will have an eye on it to see if these logs come again!&lt;/P&gt;</description>
      <pubDate>Tue, 13 Jun 2023 13:30:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2702-ap-logs/m-p/4853863#M257063</guid>
      <dc:creator>Moudar</dc:creator>
      <dc:date>2023-06-13T13:30:59Z</dc:date>
    </item>
    <item>
      <title>Re: 2702 AP logs</title>
      <link>https://community.cisco.com/t5/wireless/2702-ap-logs/m-p/4854226#M257090</link>
      <description>&lt;P&gt;And like Marce said - update the software to at least eliminate known bugs.&lt;/P&gt;
&lt;P&gt;AP and radio crashes happen from time to time, and they certainly aren't going to get fixed in AireOS or 2702 now, so upgrading to the latest software and hoping for the best is about all you can do.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jun 2023 01:45:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/2702-ap-logs/m-p/4854226#M257090</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2023-06-14T01:45:08Z</dc:date>
    </item>
  </channel>
</rss>

