<?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: Cisco Wireless: cannot add Access points  to WLC2500 in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4695957#M246586</link>
    <description>&lt;P&gt;Thank you and not sure if manufacturing certificate expiry is the issue here as one of it is expiring on 2037&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(Cisco Controller) &amp;gt;show certificate all&lt;/P&gt;&lt;P&gt;--------------- Verification Certificates ---------------&lt;BR /&gt;Certificate Name: ACT2 EC CA cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;O=Cisco, CN=ACT2 ECC SUDI CA&lt;BR /&gt;Issuer Name :&lt;BR /&gt;O=Cisco, CN=Cisco ECC Root CA&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;02&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Apr 4 08:26:13 2013 GMT&lt;BR /&gt;End : Apr 4 08:15:43.704 2053 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;ecdsa-with-SHA384&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 32:78:95:b8:c4:e0:3c:ec:14:ae:d9:70:ef:99:c8:d9:34:0b:80:e6&lt;BR /&gt;SHA256 Fingerprint : f2:a3:92:57:1e:33:54:9a:b4:36:93:ef:55:67:fb:e6:0 7:8b:98:28:05:71:0c:26:fe:f6:d8:4a:c6:e8:4b:db&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: ACT2 EC ROOT CA cert&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;O=Cisco, CN=Cisco ECC Root CA&lt;BR /&gt;Issuer Name :&lt;BR /&gt;O=Cisco, CN=Cisco ECC Root CA&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;01&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Apr 4 08:15:44 2013 GMT&lt;BR /&gt;End : Apr 4 08:15:44.704 2053 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;ecdsa-with-SHA384&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 52:ec:7d:bb:5c:65:11:dd:c1:c5:46:db:bc:29:49:b5:ab: e9:d0:ee&lt;BR /&gt;SHA256 Fingerprint : 8d:b4:9f:4b:13:ee:ad:89:c5:cc:a2:9e:c0:33:72:59:1 4:45:86:5b:7a:fd:e8:2c:33:76:0f:1c:94:7f:3b:fe&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: ACT2 RSA CA cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;O=Cisco, CN=ACT2 SUDI CA&lt;BR /&gt;Issuer Name :&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;O=Cisco Systems, CN=Cisco Root CA 2048&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;61096E7D00000000000C&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Jun 30 17:56:57 2011 GMT&lt;BR /&gt;End : May 14 20:25:42 2029 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha1WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : f6:96:9b:bd:48:e5:f6:12:5b:93:4d:01:e7:1f:e9:c2:7c: 6f:54:7e&lt;BR /&gt;SHA256 Fingerprint : 65:fa:b0:4a:ef:29:8b:e3:b9:42:e6:0e:1a:94:17:b9:c 0:c6:a1:8e:e0:45:f2:d1:11:4d:55:67:42:65:83:fb&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Cisco Manufacturing CA SHA2 cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;O=Cisco, CN=Cisco Manufacturing CA SHA2&lt;BR /&gt;Issuer Name :&lt;BR /&gt;O=Cisco, CN=Cisco Root CA M2&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;02&lt;BR /&gt;Validity :&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;Start : Nov 12 13:50:58 2012 GMT&lt;BR /&gt;End : Nov 12 13:00:17 2037 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha256WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 90:b2:e0:6b:7a:d5:da:ff:cf:d4:31:87:29:09:f3:81:37: 47:1b:f8&lt;BR /&gt;SHA256 Fingerprint : 95:a0:e5:8a:99:8e:80:2a:c7:7a:d5:29:b9:ad:d8:e5:b 4:0c:f9:0a:f3:9a:85:6d:b5:14:a3:63:46:50:1e:c5&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Cisco Root CA SHA2 cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;O=Cisco, CN=Cisco Root CA M2&lt;BR /&gt;Issuer Name :&lt;BR /&gt;O=Cisco, CN=Cisco Root CA M2&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;01&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Nov 12 13:00:18 2012 GMT&lt;BR /&gt;End : Nov 12 13:00:18 2037 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha256WithRSAEncryption&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 93:3d:63:3a:4e:84:0d:a4:c2:8e:89:5d:90:0f:d3:11:88: 86:f7:a3&lt;BR /&gt;SHA256 Fingerprint : cd:85:16:7b:39:35:e2:7b:cc:3b:0f:5f:a2:4c:84:57:8 8:2d:0b:b9:94:f8:82:69:a7:f7:28:29:d9:57:ea:e9&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Cisco Manufacturing CA SHA1 cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;O=Cisco Systems, CN=Cisco Manufacturing CA&lt;BR /&gt;Issuer Name :&lt;BR /&gt;O=Cisco Systems, CN=Cisco Root CA 2048&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;6A6967B3000000000003&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Jun 10 22:16:01 2005 GMT&lt;BR /&gt;End : May 14 20:25:42 2029 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha1WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : e3:e7:83:d3:cc:9c:30:ae:de:ff:cd:eb:5e:cf:ee:08:ff: 8f:16:84&lt;BR /&gt;SHA256 Fingerprint : c7:4d:4b:4a:14:51:9d:d0:65:19:1d:96:84:5e:8d:4e:c 8:51:43:6b:c5:59:c4:a4:5e:24:ca:5c:7c:01:fc:d3&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;--More-- or (q)uit&lt;BR /&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Cisco Root CA SHA1 cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;O=Cisco Systems, CN=Cisco Root CA 2048&lt;BR /&gt;Issuer Name :&lt;BR /&gt;O=Cisco Systems, CN=Cisco Root CA 2048&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;5FF87B282B54DC8D42A315B568C9ADFF&lt;BR /&gt;Validity :&lt;BR /&gt;Start : May 14 20:17:12 2004 GMT&lt;BR /&gt;End : May 14 20:25:42 2029 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha1WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : de:99:0c:ed:99:e0:43:1f:60:ed:c3:93:7e:7c:d5:bf:0e: d9:e5:fa&lt;BR /&gt;SHA256 Fingerprint : 83:27:bc:8c:9d:69:94:7b:3d:e3:c2:75:11:53:72:67:f 5:9c:21:b9:fa:7b:61:3f:af:bc:cd:53:b7:02:40:00&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Airespace Build CA cert&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;--More-- or (q)uit&lt;BR /&gt;Subject Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Airespace Inc., OU=Engineering, CN=A irespace Build CA, emailAddress=support@bstormnetworks.com&lt;BR /&gt;Issuer Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Airespace Inc., OU=Engineering, CN=A irespace Root CA, emailAddress=support@airespace.com&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;01&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Jul 31 13:41:31 2003 GMT&lt;BR /&gt;End : Apr 29 13:41:31 2013 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;md5WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : e3:50:2f:94:f5:54:b9:e4:c2:b3:cb:3c:f8:5c:6b:ca:86: 0f:5f:8d&lt;BR /&gt;SHA256 Fingerprint : e6:50:49:d6:d5:c7:f2:3c:e7:e9:f6:5e:48:32:5d:f1:3 9:82:60:06:f7:61:41:a2:60:89:37:cc:53:b6:90:76&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Airspace device CA cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Airespace Inc., OU=Engineering, CN=A irespace Device CA, emailAddress=support@airespace.com&lt;BR /&gt;Issuer Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Airespace Inc., OU=Engineering, CN=A irespace Root CA, emailAddress=support@airespace.com&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;03&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Apr 28 22:37:13 2005 GMT&lt;BR /&gt;End : Jan 26 22:37:13 2015 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;md5WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : ae:25:ff:04:12:8a:62:f0:f8:4a:e8:76:b1:fe:c3:0d:78: dd:c6:1b&lt;BR /&gt;SHA256 Fingerprint : 92:09:e5:a9:e3:97:5c:6c:56:bc:9c:11:d4:8b:b1:c0:a 4:c5:10:97:e7:0b:02:51:ee:bd:07:61:48:f5:fb:79&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Airespace Root CA cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Airespace Inc., OU=Engineering, CN=A irespace Root CA, emailAddress=support@airespace.com&lt;BR /&gt;Issuer Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Airespace Inc., OU=Engineering, CN=A irespace Root CA, emailAddress=support@airespace.com&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;0&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Jul 31 13:41:22 2003 GMT&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;End : Apr 29 13:41:22 2013 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;md5WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 94:ec:7d:ba:e4:e6:fb:f1:e0:44:03:81:cb:ed:ef:32:79: c9:90:b5&lt;BR /&gt;SHA256 Fingerprint : 92:62:22:3e:92:a6:48:07:0c:86:54:c4:6f:1b:04:af:5 b:1d:58:c5:7a:f2:bc:b8:76:db:41:5b:5e:7b:07:60&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Old Airespace CA cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=airespace Inc, OU=none, CN=ca, email Address=support@airespace.com&lt;BR /&gt;Issuer Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=airespace Inc, OU=none, CN=ca, email Address=support@airespace.com&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;0&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Feb 12 23:38:55 2003 GMT&lt;BR /&gt;End : Nov 11 23:38:55 2012 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;md5WithRSAEncryption&lt;BR /&gt;Hash key :&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;SHA1 Fingerprint : 05:87:eb:cc:ab:55:a3:67:56:f4:59:75:cb:b1:65:47:45: 6d:84:9c&lt;BR /&gt;SHA256 Fingerprint : 96:b4:a7:47:1e:50:d8:38:4c:4d:4f:49:e3:53:61:f6:5 0:7c:a4:8f:78:07:7b:0f:9c:8c:40:6c:5b:94:40:f3&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;-------------- Identification Certificates --------------&lt;BR /&gt;Certificate Name: Cert for Web Authentication&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;C=US, O=Cisco Systems Inc., OU=DeviceSSL (WebAuth), CN=1.1.1.1&lt;BR /&gt;Issuer Name :&lt;BR /&gt;C=US, O=Cisco Systems Inc., OU=DeviceSSL (WebAuth), CN=1.1.1.1&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;07661740&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Apr 22 23:00:01 2019 GMT&lt;BR /&gt;End : Apr 22 23:00:01 2029 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha256WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 00:a4:ca:1c:3b:a5:e8:d1:bc:d2:78:73:37:85:ed:d9:9c: e6:af:91&lt;BR /&gt;SHA256 Fingerprint : 41:62:7c:ed:79:1e:2f:47:41:23:ae:6b:24:d6:a2:a6:c 4:55:10:8c:cb:7e:2c:8d:0a:e6:b2:4f:bc:e2:e8:ef&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Cert for Web Admin&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;C=US, O=Cisco Systems Inc., OU=DeviceSSL (WebAdmin), CN=10.255.185.1&lt;BR /&gt;Issuer Name :&lt;BR /&gt;C=US, O=Cisco Systems Inc., OU=DeviceSSL (WebAdmin), CN=10.255.185.1&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;07661740&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Apr 22 23:00:01 2019 GMT&lt;BR /&gt;End : Apr 22 23:00:01 2029 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha256WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 41:47:40:e4:8b:a0:40:1e:87:40:0c:aa:d6:2a:1d:22:9b: 4a:1d:97&lt;BR /&gt;SHA256 Fingerprint : 2a:c7:ab:35:8e:9a:a1:02:8e:68:4e:30:6c:e0:b4:52:b 5:64:13:ae:40:94:25:c9:22:03:cf:f1:df:99:04:5e&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Cisco SHA1 device cert&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Cisco Systems, CN=AIR-CT2504-K9-203a 07661740, emailAddress=support@cisco.com&lt;BR /&gt;Issuer Name :&lt;BR /&gt;O=Cisco Systems, CN=Cisco Manufacturing CA&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;6F454BA80000000D78FC&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Sep 7 23:08:37 2012 GMT&lt;BR /&gt;End : Sep 7 23:18:37 2022 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha1WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 35:cf:5a:c5:f5:79:b0:87:ac:08:d2:ef:ce:e3:1f:18:7b: 56:61:11&lt;BR /&gt;SHA256 Fingerprint : 89:ba:39:23:5b:0e:c6:13:7d:ea:0f:7a:08:ba:91:6d:1 e:de:5c:61:13:7b:99:10:1d:1b:ff:02:3a:6c:82:46&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Airespace Id cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Airespace Inc., OU=MWAR Device, CN=0 00b85236d90, emailAddress=support@airespace.com&lt;BR /&gt;Issuer Name :&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Airespace Inc., OU=Engineering, CN=A irespace Device CA, emailAddress=support@airespace.com&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;04EB8E&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Mar 13 02:07:09 2006 GMT&lt;BR /&gt;End : Mar 10 02:07:09 2016 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;md5WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : e3:68:a6:0f:89:46:b5:6b:37:eb:11:8c:d0:67:2e:51:e1: d8:5e:59&lt;BR /&gt;SHA256 Fingerprint : f1:21:a6:ef:a6:c3:67:06:73:90:12:55:1a:a3:49:e6:0 9:fa:8a:b6:22:2e:85:2f:48:b3:40:49:aa:97:c5:50&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Old Airespace Id cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=airespace Inc, CN=000b85236d90, emai lAddress=support@airespace.com&lt;BR /&gt;Issuer Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=airespace Inc, OU=none, CN=ca, email Address=support@airespace.com&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;04C88C&lt;BR /&gt;Validity :&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;Start : Mar 13 02:07:12 2006 GMT&lt;BR /&gt;End : Dec 11 02:07:12 2015 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;md5WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 51:0c:17:6d:94:2c:cf:e4:eb:66:ba:4b:26:0b:ed:11:26: 99:3c:b1&lt;BR /&gt;SHA256 Fingerprint : 9b:ec:a6:03:6b:7b:60:fe:17:e1:0e:4f:b4:2d:f3:b9:f 6:c5:07:bb:97:6d:db:1b:3e:7f:80:f0:d3:86:1a:20&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 29 Sep 2022 13:11:18 GMT</pubDate>
    <dc:creator>mathewmnu7</dc:creator>
    <dc:date>2022-09-29T13:11:18Z</dc:date>
    <item>
      <title>Cisco Wireless: cannot add Access points  to WLC2500</title>
      <link>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4686022#M245965</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am trying to add 2 Access points which we recently purchased to Controller.&amp;nbsp;&lt;/P&gt;&lt;P&gt;can see AP's are getting DHCP&amp;nbsp; and logs below on WLC.&amp;nbsp;&amp;nbsp;10.158.177.51 and&amp;nbsp;10.158.177.50 are the AP's in question.&amp;nbsp;&lt;/P&gt;&lt;P&gt;*spamApTask3: Sep 13 10:43:04.515: %DTLS-5-PEER_DISCONNECT: openssl_dtls.c:1004 DTLS peer 10.158.177.50 has closed connection.&lt;BR /&gt;*spamApTask3: Sep 13 10:43:04.442: %DTLS-5-ESTABLISHED_TO_PEER: openssl_dtls.c:880 DTLS connection established to 10.158.177.50&lt;BR /&gt;*spamApTask2: Sep 13 10:42:54.348: %DTLS-5-PEER_DISCONNECT: openssl_dtls.c:1004 DTLS peer 10.158.177.51 has closed connection.&lt;BR /&gt;*spamApTask2: Sep 13 10:42:54.197: %DTLS-5-ESTABLISHED_TO_PEER: openssl_dtls.c:880 DTLS connection established to 10.158.177.51&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mathew&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2022 09:58:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4686022#M245965</guid>
      <dc:creator>mathewmnu7</dc:creator>
      <dc:date>2022-09-13T09:58:40Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Wireless: cannot add Access points  to WLC2500</title>
      <link>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4686031#M245966</link>
      <description>&lt;P&gt;What firmware version running on your 2504 and what AP model you are trying to register to it&lt;/P&gt;
&lt;P&gt;"show sysinfo" from WLC &amp;amp; "show version" from your AP will help us to see why it is failing.&lt;/P&gt;
&lt;P&gt;I would check this compatibility matrix table as a starting point&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html#ctrl_release-ap-support" target="_self"&gt;https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html#ctrl_release-ap-support&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;HTH&lt;BR /&gt;Rasika&lt;BR /&gt;*** Pls rate all useful responses ***&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2022 10:20:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4686031#M245966</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2022-09-13T10:20:13Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Wireless: cannot add Access points  to WLC2500</title>
      <link>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4686241#M245983</link>
      <description>&lt;P&gt;Wireless controller version: 8.3.150.0 and currently i dont have access to Access point. Will below details help ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;AP model: AIR-AP1832-E-K9&lt;/P&gt;&lt;P&gt;&amp;gt;show sysinfo&lt;/P&gt;&lt;P&gt;Manufacturer's Name.............................. Cisco Systems Inc.&lt;BR /&gt;Product Name..................................... Cisco Controller&lt;BR /&gt;Product Version.................................. 8.3.150.0&lt;BR /&gt;Bootloader Version............................... 1.0.20&lt;BR /&gt;Field Recovery Image Version..................... 7.6.101.1&lt;BR /&gt;Firmware Version................................. PIC 16.0&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;OUI File Update Time............................. Sun Sep 07 10:44:07 IST 2014&lt;/P&gt;&lt;P&gt;Build Type....................................... DATA + WPS&lt;/P&gt;&lt;P&gt;System Name...................................... P185-&lt;BR /&gt;System Location..................................&lt;BR /&gt;System Contact...................................&lt;BR /&gt;System ObjectID.................................. 1.3.6.1.4.1.9.1.1279&lt;BR /&gt;IP Address....................................... 10.158.191.251&lt;BR /&gt;IPv6 Address..................................... ::&lt;BR /&gt;Last Reset....................................... Software reset&lt;BR /&gt;System Up Time................................... 0 days 23 hrs 28 mins 28 secs&lt;BR /&gt;System Timezone Location......................... (GMT) London, Lisbon, Dublin, Edinburgh&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;System Stats Realtime Interval................... 5&lt;BR /&gt;System Stats Normal Interval..................... 180&lt;/P&gt;&lt;P&gt;Configured Country............................... GB - United Kingdom&lt;BR /&gt;Operating Environment............................ Commercial (0 to 40 C)&lt;BR /&gt;Internal Temp Alarm Limits....................... 0 to 65 C&lt;BR /&gt;Internal Temperature............................. +37 C&lt;BR /&gt;External Temperature............................. +42 C&lt;BR /&gt;Fan Status....................................... 5600 rpm&lt;/P&gt;&lt;P&gt;State of 802.11b Network......................... Enabled&lt;BR /&gt;State of 802.11a Network......................... Enabled&lt;BR /&gt;Number of WLANs.................................. 1&lt;BR /&gt;Number of Active Clients......................... 116&lt;/P&gt;&lt;P&gt;OUI Classification Failure Count................. 603&lt;/P&gt;&lt;P&gt;Burned-in MAC Address............................ 20:3A:07:66:17:40&lt;BR /&gt;Maximum number of APs supported.................. 75&lt;BR /&gt;System Nas-Id....................................&lt;BR /&gt;WLC MIC Certificate Types........................ SHA1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2022 13:50:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4686241#M245983</guid>
      <dc:creator>mathewmnu7</dc:creator>
      <dc:date>2022-09-13T13:50:03Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Wireless: cannot add Access points  to WLC2500</title>
      <link>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4686322#M245989</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;U&gt;&lt;EM&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;gt;currently&lt;FONT color="#FF6600"&gt; i dont have access&lt;/FONT&gt; to Access point.&amp;nbsp;&lt;/EM&gt;&lt;/U&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; You will probably need to find some ways to provide the ap boot process output&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2022 16:33:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4686322#M245989</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2022-09-13T16:33:41Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Wireless: cannot add Access points  to WLC2500</title>
      <link>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4687156#M246044</link>
      <description>&lt;P&gt;can see below console messages&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:41.9385] CAPWAP State: Discovery&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:41.9584] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:41.9584] Discovery Response from 10.158.191.251&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.0000]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.0000] CAPWAP State: DTLS Setup&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.0000] dtls_connectionDB_add_connection: Number of DTLS connections exceeded two&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.2699] dtls_load_ca_certs: LSC Root Certificate not present&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.2699]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.2699] dtls_verify_con_cert: Controller certificate verification error&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.2699] dtls_process_packet: controller cert verification failed&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.2699] DTLS: Received packet 0x26f0000 caused DTLS to close connection&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.2699] sendPacketToDtls: DTLS: Closing connection 0x2696000.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.2699]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.2699] Lost connection to the controller, going to restart CAPWAP...&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.2699]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.2699] Restarting CAPWAP State Machine.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.2799] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Setup(3).&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.2999] Failed to disconnect DTLS-CTRL session.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.2999]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.2999] CAPWAP State: DTLS Teardown&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:51.3199] DTLS: Error while processing DTLS packet 0x2700000.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:55.9285]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:55.9285] CAPWAP State: Discovery&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:55.9485] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:58:55.9584] Discovery Response from 10.158.191.251&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.0000]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.0000] CAPWAP State: DTLS Setup&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.0000] dtls_connectionDB_add_connection: Number of DTLS connections exceeded two&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.1999] dtls_load_ca_certs: LSC Root Certificate not present&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.1999]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.2099] dtls_verify_con_cert: Controller certificate verification error&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.2099] dtls_process_packet: controller cert verification failed&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.2099] DTLS: Received packet 0x26f0000 caused DTLS to close connection&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.2099] sendPacketToDtls: DTLS: Closing connection 0x26b4c00.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.2099]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.2099] Lost connection to the controller, going to restart CAPWAP...&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.2099]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.2099] Restarting CAPWAP State Machine.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.2199] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Setup(3).&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.2199] Failed to disconnect DTLS-CTRL session.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.2199]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.2199] CAPWAP State: DTLS Teardown&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:06.2299] DTLS: Error while processing DTLS packet 0x26dd000.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:10.9285]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:10.9285] CAPWAP State: Discovery&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:10.9485] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:10.9485] Discovery Response from 10.158.191.251&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.0000]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.0000] CAPWAP State: DTLS Setup&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.0000] dtls_connectionDB_add_connection: Number of DTLS connections exceeded two&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.2599] dtls_load_ca_certs: LSC Root Certificate not present&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.2599]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.2599] dtls_verify_con_cert: Controller certificate verification error&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.2599] dtls_process_packet: controller cert verification failed&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.2699] DTLS: Received packet 0x26f0000 caused DTLS to close connection&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.2699] sendPacketToDtls: DTLS: Closing connection 0x2696000.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.2699]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.2699] Lost connection to the controller, going to restart CAPWAP...&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.2699]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.2799] DTLS: Error while processing DTLS packet 0x26f4000.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.2799] Restarting CAPWAP State Machine.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.2899] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Setup(3).&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.3099] Failed to disconnect DTLS-CTRL session.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.3099]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:20.3099] CAPWAP State: DTLS Teardown&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:24.9285]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:24.9285] CAPWAP State: Discovery&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:24.9485] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:24.9485] Discovery Response from 10.158.191.251&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.0000]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.0000] CAPWAP State: DTLS Setup&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.0000] dtls_connectionDB_add_connection: Number of DTLS connections exceeded two&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.1999] dtls_load_ca_certs: LSC Root Certificate not present&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.1999]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.2099] dtls_verify_con_cert: Controller certificate verification error&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.2099] dtls_process_packet: controller cert verification failed&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.2099] DTLS: Received packet 0x26dd000 caused DTLS to close connection&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.2099] sendPacketToDtls: DTLS: Closing connection 0x26b4c00.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.2099]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.2099] Lost connection to the controller, going to restart CAPWAP...&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.2099]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.2099] Restarting CAPWAP State Machine.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.2199] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Setup(3).&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.2199] Failed to disconnect DTLS-CTRL session.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.2199]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.2199] CAPWAP State: DTLS Teardown&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:35.2299] DTLS: Error while processing DTLS packet 0x26f0000.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:39.9285]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:39.9285] CAPWAP State: Discovery&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:39.9385] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:39.9485] Discovery Response from 10.158.191.251&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.0000]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.0000] CAPWAP State: DTLS Setup&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.0000] dtls_connectionDB_add_connection: Number of DTLS connections exceeded two&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.2699] dtls_load_ca_certs: LSC Root Certificate not present&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.2699]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.2699] dtls_verify_con_cert: Controller certificate verification error&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.2699] dtls_process_packet: controller cert verification failed&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.2699] DTLS: Received packet 0x26dd000 caused DTLS to close connection&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.2699] sendPacketToDtls: DTLS: Closing connection 0x2696000.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.2699]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.2699] Lost connection to the controller, going to restart CAPWAP...&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.2699]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.2699] Restarting CAPWAP State Machine.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.2799] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Setup(3).&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.2999] Failed to disconnect DTLS-CTRL session.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.2999]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.2999] CAPWAP State: DTLS Teardown&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:49.3199] DTLS: Error while processing DTLS packet 0x2700000.&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:53.9385]&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:53.9385] CAPWAP State: Discovery&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:53.9584] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)&lt;/P&gt;&lt;P&gt;[*09/14/2022 13:59:53.9584] Discovery Response from 10.158.191.251&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2022 14:28:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4687156#M246044</guid>
      <dc:creator>mathewmnu7</dc:creator>
      <dc:date>2022-09-14T14:28:51Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Wireless: cannot add Access points  to WLC2500</title>
      <link>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4687172#M246046</link>
      <description>&lt;P&gt;Access Point output&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;APC4B9.CDEC.2EE8#show run&lt;BR /&gt;AP Name : APC4B9.CDEC.2EE8&lt;BR /&gt;Admin State : Enabled&lt;BR /&gt;AP Mode : Local&lt;BR /&gt;AP Submode : None&lt;BR /&gt;Location : default location&lt;BR /&gt;Reboot Reason : Reload command&lt;BR /&gt;Primary controller name :&lt;BR /&gt;Primary controller IP :&lt;BR /&gt;Secondary controller name :&lt;BR /&gt;Secondary controller IP :&lt;BR /&gt;Tertiary controller name :&lt;BR /&gt;Tertiary controller IP :&lt;BR /&gt;AP join priority : 1&lt;BR /&gt;IP Prefer-mode : Unconfigured&lt;BR /&gt;CAPWAP UDP-Lite : Unconfigured&lt;BR /&gt;Last Joined Controller name:&lt;BR /&gt;DTLS Encryption State : Disabled&lt;BR /&gt;Discovery Timer : 10&lt;BR /&gt;Heartbeat Timer : 30&lt;BR /&gt;CDP State : Enabled&lt;BR /&gt;Watchdog monitoring : Enabled&lt;BR /&gt;RRM State : Enabled&lt;BR /&gt;LSC State : Disabled&lt;BR /&gt;SSH State : Disabled&lt;BR /&gt;AP Username : Cisco&lt;BR /&gt;Session Timeout : 300&lt;BR /&gt;Extlog Host : 255.255.255.255&lt;BR /&gt;Extlog Flags : 0&lt;BR /&gt;Extlog Status Interval : 0&lt;BR /&gt;Syslog Host : 255.255.255.255&lt;BR /&gt;Syslog Facility : 0&lt;BR /&gt;Syslog Level : errors&lt;BR /&gt;Core Dump TFTP Ip Addr : 0.0.0.0&lt;BR /&gt;Core Dump Flag: : 0&lt;BR /&gt;Core Dump Filename :&lt;BR /&gt;WLC Link LAG status : Disabled&lt;BR /&gt;AP Link LAG status : Disabled&lt;BR /&gt;AP WSA Mode : Disabled&lt;BR /&gt;APC4B9.CDEC.2EE8#show version&lt;BR /&gt;Restricted Rights Legend&lt;/P&gt;&lt;P&gt;Use, duplication, or disclosure by the Government is subject to&lt;BR /&gt;restrictions as set forth in subparagraph (c) of the Commercial&lt;BR /&gt;Computer Software - Restricted Rights clause at FAR sec. 52.227-19 and&lt;BR /&gt;subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer&lt;BR /&gt;Software clause at DFARS sec. 252.227-7013.&lt;/P&gt;&lt;P&gt;Cisco Systems, Inc.&lt;BR /&gt;170 West Tasman Drive&lt;BR /&gt;San Jose, California 95134-1706&lt;/P&gt;&lt;P&gt;This product contains cryptographic features and is subject to United&lt;BR /&gt;States and local country laws governing import, export, transfer and&lt;BR /&gt;use. Delivery of Cisco cryptographic products does not imply&lt;BR /&gt;third-party authority to import, export, distribute or use encryption.&lt;BR /&gt;Importers, exporters, distributors and users are responsible for&lt;BR /&gt;compliance with U.S. and local country laws. By using this product you&lt;BR /&gt;agree to comply with applicable laws and regulations. If you are unable&lt;BR /&gt;to comply with U.S. and local laws, return this product immediately.&lt;/P&gt;&lt;P&gt;A summary of U.S. laws governing Cisco cryptographic products may be found at:&lt;BR /&gt;&lt;A href="http://www.cisco.com/wwl/export/crypto/tool/stqrg.html" target="_blank"&gt;http://www.cisco.com/wwl/export/crypto/tool/stqrg.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;If you require further assistance please contact us by sending email to&lt;BR /&gt;export@cisco.com.&lt;/P&gt;&lt;P&gt;This product contains some software licensed under the&lt;BR /&gt;"GNU General Public License, version 2" provided with&lt;BR /&gt;ABSOLUTELY NO WARRANTY under the terms of&lt;BR /&gt;"GNU General Public License, version 2", available here:&lt;BR /&gt;&lt;A href="http://www.gnu.org/licenses/old-licenses/gpl-2.0.html" target="_blank"&gt;http://www.gnu.org/licenses/old-licenses/gpl-2.0.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;This product contains some software licensed under the&lt;BR /&gt;"GNU Library General Public License, version 2" provided&lt;BR /&gt;with ABSOLUTELY NO WARRANTY under the terms of "GNU Library&lt;BR /&gt;General Public License, version 2", available here:&lt;BR /&gt;&lt;A href="http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html" target="_blank"&gt;http://www.gnu.org/licenses/old-licenses/lgpl-2.0.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;This product contains some software licensed under the&lt;BR /&gt;"GNU Lesser General Public License, version 2.1" provided&lt;BR /&gt;with ABSOLUTELY NO WARRANTY under the terms of "GNU Lesser&lt;BR /&gt;General Public License, version 2.1", available here:&lt;BR /&gt;&lt;A href="http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html" target="_blank"&gt;http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;CO/label/corsica], (ap1g4), [cheetah-build5:/san/BUILD/workspace/83MR5_Cheetah_C--More--&lt;BR /&gt;Technical Support: &lt;A href="http://www.cisco.com/techsupport" target="_blank"&gt;http://www.cisco.com/techsupport&lt;/A&gt;&lt;BR /&gt;Copyright (c) 1986-2015 by Cisco Systems, Inc.&lt;BR /&gt;Compiled Thu Apr 11 13:30:13 PDT 2019&lt;/P&gt;&lt;P&gt;ROM: Bootstrap program is U-Boot boot loader&lt;BR /&gt;BOOTLDR: U-Boot boot loader Version 31&lt;/P&gt;&lt;P&gt;APC4B9.CDEC.2EE8 uptime is 0 days, 3 hours, 58 minutes&lt;BR /&gt;Last reload time : Mon Sep 12 09:28:30 UTC 2022&lt;BR /&gt;Last reload reason : unknown&lt;/P&gt;&lt;P&gt;cisco AIR-AP1832I-E-K9 ARMv7 Processor rev 0 (v7l) with 967420/734068K bytes of memory.&lt;BR /&gt;Processor board ID KWC210708TV&lt;BR /&gt;AP Running Image : 8.3.150.0&lt;BR /&gt;Primary Boot Image : 8.3.150.0&lt;BR /&gt;Backup Boot Image : 8.2.141.0&lt;BR /&gt;2 Gigabit Ethernet interfaces&lt;BR /&gt;2 802.11 Radios&lt;BR /&gt;Radio FW version : c5d79906494f60ee03674c0779e5c30b&lt;BR /&gt;NSS FW version : NSS.AK.1.0.c10-00017-E_custC-1.67978.1&lt;/P&gt;&lt;P&gt;Base ethernet MAC Address : C4:B9:CD:EC:2E:E8&lt;BR /&gt;Part Number : 0-0000-00&lt;BR /&gt;PCA Assembly Number : 074-104313-02&lt;BR /&gt;PCA Revision Number : 01&lt;BR /&gt;PCB Serial Number : KWC210708TV&lt;BR /&gt;Top Assembly Part Number : 000-00000-00&lt;BR /&gt;Top Assembly Serial Number : KWC210708TV&lt;BR /&gt;Top Revision Number : A0&lt;BR /&gt;Product/Model Number : AIR-AP1832I-E-K9&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2022 14:46:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4687172#M246046</guid>
      <dc:creator>mathewmnu7</dc:creator>
      <dc:date>2022-09-14T14:46:56Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Wireless: cannot add Access points  to WLC2500</title>
      <link>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4687194#M246055</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp;- FYI :&amp;nbsp;&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/support/docs/field-notices/639/fn63942.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/field-notices/639/fn63942.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2022 15:15:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4687194#M246055</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2022-09-14T15:15:51Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Wireless: cannot add Access points  to WLC2500</title>
      <link>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4687206#M246057</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1404244"&gt;@mathewmnu7&lt;/a&gt;&amp;nbsp;did you carefully read and follow the field notice as per&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/291804"&gt;@Mark Elsen&lt;/a&gt;&amp;nbsp;above?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2022 15:32:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4687206#M246057</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2022-09-14T15:32:28Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Wireless: cannot add Access points  to WLC2500</title>
      <link>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4695957#M246586</link>
      <description>&lt;P&gt;Thank you and not sure if manufacturing certificate expiry is the issue here as one of it is expiring on 2037&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(Cisco Controller) &amp;gt;show certificate all&lt;/P&gt;&lt;P&gt;--------------- Verification Certificates ---------------&lt;BR /&gt;Certificate Name: ACT2 EC CA cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;O=Cisco, CN=ACT2 ECC SUDI CA&lt;BR /&gt;Issuer Name :&lt;BR /&gt;O=Cisco, CN=Cisco ECC Root CA&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;02&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Apr 4 08:26:13 2013 GMT&lt;BR /&gt;End : Apr 4 08:15:43.704 2053 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;ecdsa-with-SHA384&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 32:78:95:b8:c4:e0:3c:ec:14:ae:d9:70:ef:99:c8:d9:34:0b:80:e6&lt;BR /&gt;SHA256 Fingerprint : f2:a3:92:57:1e:33:54:9a:b4:36:93:ef:55:67:fb:e6:0 7:8b:98:28:05:71:0c:26:fe:f6:d8:4a:c6:e8:4b:db&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: ACT2 EC ROOT CA cert&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;O=Cisco, CN=Cisco ECC Root CA&lt;BR /&gt;Issuer Name :&lt;BR /&gt;O=Cisco, CN=Cisco ECC Root CA&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;01&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Apr 4 08:15:44 2013 GMT&lt;BR /&gt;End : Apr 4 08:15:44.704 2053 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;ecdsa-with-SHA384&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 52:ec:7d:bb:5c:65:11:dd:c1:c5:46:db:bc:29:49:b5:ab: e9:d0:ee&lt;BR /&gt;SHA256 Fingerprint : 8d:b4:9f:4b:13:ee:ad:89:c5:cc:a2:9e:c0:33:72:59:1 4:45:86:5b:7a:fd:e8:2c:33:76:0f:1c:94:7f:3b:fe&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: ACT2 RSA CA cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;O=Cisco, CN=ACT2 SUDI CA&lt;BR /&gt;Issuer Name :&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;O=Cisco Systems, CN=Cisco Root CA 2048&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;61096E7D00000000000C&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Jun 30 17:56:57 2011 GMT&lt;BR /&gt;End : May 14 20:25:42 2029 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha1WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : f6:96:9b:bd:48:e5:f6:12:5b:93:4d:01:e7:1f:e9:c2:7c: 6f:54:7e&lt;BR /&gt;SHA256 Fingerprint : 65:fa:b0:4a:ef:29:8b:e3:b9:42:e6:0e:1a:94:17:b9:c 0:c6:a1:8e:e0:45:f2:d1:11:4d:55:67:42:65:83:fb&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Cisco Manufacturing CA SHA2 cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;O=Cisco, CN=Cisco Manufacturing CA SHA2&lt;BR /&gt;Issuer Name :&lt;BR /&gt;O=Cisco, CN=Cisco Root CA M2&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;02&lt;BR /&gt;Validity :&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;Start : Nov 12 13:50:58 2012 GMT&lt;BR /&gt;End : Nov 12 13:00:17 2037 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha256WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 90:b2:e0:6b:7a:d5:da:ff:cf:d4:31:87:29:09:f3:81:37: 47:1b:f8&lt;BR /&gt;SHA256 Fingerprint : 95:a0:e5:8a:99:8e:80:2a:c7:7a:d5:29:b9:ad:d8:e5:b 4:0c:f9:0a:f3:9a:85:6d:b5:14:a3:63:46:50:1e:c5&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Cisco Root CA SHA2 cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;O=Cisco, CN=Cisco Root CA M2&lt;BR /&gt;Issuer Name :&lt;BR /&gt;O=Cisco, CN=Cisco Root CA M2&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;01&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Nov 12 13:00:18 2012 GMT&lt;BR /&gt;End : Nov 12 13:00:18 2037 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha256WithRSAEncryption&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 93:3d:63:3a:4e:84:0d:a4:c2:8e:89:5d:90:0f:d3:11:88: 86:f7:a3&lt;BR /&gt;SHA256 Fingerprint : cd:85:16:7b:39:35:e2:7b:cc:3b:0f:5f:a2:4c:84:57:8 8:2d:0b:b9:94:f8:82:69:a7:f7:28:29:d9:57:ea:e9&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Cisco Manufacturing CA SHA1 cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;O=Cisco Systems, CN=Cisco Manufacturing CA&lt;BR /&gt;Issuer Name :&lt;BR /&gt;O=Cisco Systems, CN=Cisco Root CA 2048&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;6A6967B3000000000003&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Jun 10 22:16:01 2005 GMT&lt;BR /&gt;End : May 14 20:25:42 2029 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha1WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : e3:e7:83:d3:cc:9c:30:ae:de:ff:cd:eb:5e:cf:ee:08:ff: 8f:16:84&lt;BR /&gt;SHA256 Fingerprint : c7:4d:4b:4a:14:51:9d:d0:65:19:1d:96:84:5e:8d:4e:c 8:51:43:6b:c5:59:c4:a4:5e:24:ca:5c:7c:01:fc:d3&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;--More-- or (q)uit&lt;BR /&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Cisco Root CA SHA1 cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;O=Cisco Systems, CN=Cisco Root CA 2048&lt;BR /&gt;Issuer Name :&lt;BR /&gt;O=Cisco Systems, CN=Cisco Root CA 2048&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;5FF87B282B54DC8D42A315B568C9ADFF&lt;BR /&gt;Validity :&lt;BR /&gt;Start : May 14 20:17:12 2004 GMT&lt;BR /&gt;End : May 14 20:25:42 2029 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha1WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : de:99:0c:ed:99:e0:43:1f:60:ed:c3:93:7e:7c:d5:bf:0e: d9:e5:fa&lt;BR /&gt;SHA256 Fingerprint : 83:27:bc:8c:9d:69:94:7b:3d:e3:c2:75:11:53:72:67:f 5:9c:21:b9:fa:7b:61:3f:af:bc:cd:53:b7:02:40:00&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Airespace Build CA cert&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;--More-- or (q)uit&lt;BR /&gt;Subject Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Airespace Inc., OU=Engineering, CN=A irespace Build CA, emailAddress=support@bstormnetworks.com&lt;BR /&gt;Issuer Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Airespace Inc., OU=Engineering, CN=A irespace Root CA, emailAddress=support@airespace.com&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;01&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Jul 31 13:41:31 2003 GMT&lt;BR /&gt;End : Apr 29 13:41:31 2013 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;md5WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : e3:50:2f:94:f5:54:b9:e4:c2:b3:cb:3c:f8:5c:6b:ca:86: 0f:5f:8d&lt;BR /&gt;SHA256 Fingerprint : e6:50:49:d6:d5:c7:f2:3c:e7:e9:f6:5e:48:32:5d:f1:3 9:82:60:06:f7:61:41:a2:60:89:37:cc:53:b6:90:76&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Airspace device CA cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Airespace Inc., OU=Engineering, CN=A irespace Device CA, emailAddress=support@airespace.com&lt;BR /&gt;Issuer Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Airespace Inc., OU=Engineering, CN=A irespace Root CA, emailAddress=support@airespace.com&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;03&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Apr 28 22:37:13 2005 GMT&lt;BR /&gt;End : Jan 26 22:37:13 2015 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;md5WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : ae:25:ff:04:12:8a:62:f0:f8:4a:e8:76:b1:fe:c3:0d:78: dd:c6:1b&lt;BR /&gt;SHA256 Fingerprint : 92:09:e5:a9:e3:97:5c:6c:56:bc:9c:11:d4:8b:b1:c0:a 4:c5:10:97:e7:0b:02:51:ee:bd:07:61:48:f5:fb:79&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Airespace Root CA cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Airespace Inc., OU=Engineering, CN=A irespace Root CA, emailAddress=support@airespace.com&lt;BR /&gt;Issuer Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Airespace Inc., OU=Engineering, CN=A irespace Root CA, emailAddress=support@airespace.com&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;0&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Jul 31 13:41:22 2003 GMT&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;End : Apr 29 13:41:22 2013 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;md5WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 94:ec:7d:ba:e4:e6:fb:f1:e0:44:03:81:cb:ed:ef:32:79: c9:90:b5&lt;BR /&gt;SHA256 Fingerprint : 92:62:22:3e:92:a6:48:07:0c:86:54:c4:6f:1b:04:af:5 b:1d:58:c5:7a:f2:bc:b8:76:db:41:5b:5e:7b:07:60&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Old Airespace CA cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=airespace Inc, OU=none, CN=ca, email Address=support@airespace.com&lt;BR /&gt;Issuer Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=airespace Inc, OU=none, CN=ca, email Address=support@airespace.com&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;0&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Feb 12 23:38:55 2003 GMT&lt;BR /&gt;End : Nov 11 23:38:55 2012 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;md5WithRSAEncryption&lt;BR /&gt;Hash key :&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;SHA1 Fingerprint : 05:87:eb:cc:ab:55:a3:67:56:f4:59:75:cb:b1:65:47:45: 6d:84:9c&lt;BR /&gt;SHA256 Fingerprint : 96:b4:a7:47:1e:50:d8:38:4c:4d:4f:49:e3:53:61:f6:5 0:7c:a4:8f:78:07:7b:0f:9c:8c:40:6c:5b:94:40:f3&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;-------------- Identification Certificates --------------&lt;BR /&gt;Certificate Name: Cert for Web Authentication&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;C=US, O=Cisco Systems Inc., OU=DeviceSSL (WebAuth), CN=1.1.1.1&lt;BR /&gt;Issuer Name :&lt;BR /&gt;C=US, O=Cisco Systems Inc., OU=DeviceSSL (WebAuth), CN=1.1.1.1&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;07661740&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Apr 22 23:00:01 2019 GMT&lt;BR /&gt;End : Apr 22 23:00:01 2029 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha256WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 00:a4:ca:1c:3b:a5:e8:d1:bc:d2:78:73:37:85:ed:d9:9c: e6:af:91&lt;BR /&gt;SHA256 Fingerprint : 41:62:7c:ed:79:1e:2f:47:41:23:ae:6b:24:d6:a2:a6:c 4:55:10:8c:cb:7e:2c:8d:0a:e6:b2:4f:bc:e2:e8:ef&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Cert for Web Admin&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;C=US, O=Cisco Systems Inc., OU=DeviceSSL (WebAdmin), CN=10.255.185.1&lt;BR /&gt;Issuer Name :&lt;BR /&gt;C=US, O=Cisco Systems Inc., OU=DeviceSSL (WebAdmin), CN=10.255.185.1&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;07661740&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Apr 22 23:00:01 2019 GMT&lt;BR /&gt;End : Apr 22 23:00:01 2029 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha256WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 41:47:40:e4:8b:a0:40:1e:87:40:0c:aa:d6:2a:1d:22:9b: 4a:1d:97&lt;BR /&gt;SHA256 Fingerprint : 2a:c7:ab:35:8e:9a:a1:02:8e:68:4e:30:6c:e0:b4:52:b 5:64:13:ae:40:94:25:c9:22:03:cf:f1:df:99:04:5e&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Cisco SHA1 device cert&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Cisco Systems, CN=AIR-CT2504-K9-203a 07661740, emailAddress=support@cisco.com&lt;BR /&gt;Issuer Name :&lt;BR /&gt;O=Cisco Systems, CN=Cisco Manufacturing CA&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;6F454BA80000000D78FC&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Sep 7 23:08:37 2012 GMT&lt;BR /&gt;End : Sep 7 23:18:37 2022 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha1WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 35:cf:5a:c5:f5:79:b0:87:ac:08:d2:ef:ce:e3:1f:18:7b: 56:61:11&lt;BR /&gt;SHA256 Fingerprint : 89:ba:39:23:5b:0e:c6:13:7d:ea:0f:7a:08:ba:91:6d:1 e:de:5c:61:13:7b:99:10:1d:1b:ff:02:3a:6c:82:46&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Airespace Id cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Airespace Inc., OU=MWAR Device, CN=0 00b85236d90, emailAddress=support@airespace.com&lt;BR /&gt;Issuer Name :&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Airespace Inc., OU=Engineering, CN=A irespace Device CA, emailAddress=support@airespace.com&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;04EB8E&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Mar 13 02:07:09 2006 GMT&lt;BR /&gt;End : Mar 10 02:07:09 2016 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;md5WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : e3:68:a6:0f:89:46:b5:6b:37:eb:11:8c:d0:67:2e:51:e1: d8:5e:59&lt;BR /&gt;SHA256 Fingerprint : f1:21:a6:ef:a6:c3:67:06:73:90:12:55:1a:a3:49:e6:0 9:fa:8a:b6:22:2e:85:2f:48:b3:40:49:aa:97:c5:50&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;Certificate Name: Old Airespace Id cert&lt;/P&gt;&lt;P&gt;Subject Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=airespace Inc, CN=000b85236d90, emai lAddress=support@airespace.com&lt;BR /&gt;Issuer Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=airespace Inc, OU=none, CN=ca, email Address=support@airespace.com&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;04C88C&lt;BR /&gt;Validity :&lt;/P&gt;&lt;P&gt;--More-- or (q)uit&lt;BR /&gt;Start : Mar 13 02:07:12 2006 GMT&lt;BR /&gt;End : Dec 11 02:07:12 2015 GMT&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;md5WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 51:0c:17:6d:94:2c:cf:e4:eb:66:ba:4b:26:0b:ed:11:26: 99:3c:b1&lt;BR /&gt;SHA256 Fingerprint : 9b:ec:a6:03:6b:7b:60:fe:17:e1:0e:4f:b4:2d:f3:b9:f 6:c5:07:bb:97:6d:db:1b:3e:7f:80:f0:d3:86:1a:20&lt;/P&gt;&lt;P&gt;----------------------------&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Sep 2022 13:11:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4695957#M246586</guid>
      <dc:creator>mathewmnu7</dc:creator>
      <dc:date>2022-09-29T13:11:18Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco Wireless: cannot add Access points  to WLC2500</title>
      <link>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4696116#M246590</link>
      <description>&lt;P&gt;Certificate Name: Cisco SHA1 device cert&lt;BR /&gt;Subject Name :&lt;BR /&gt;C=US, ST=California, L=San Jose, O=Cisco Systems, CN=AIR-CT2504-K9-203a 07661740, emailAddress=support@cisco.com&lt;BR /&gt;Issuer Name :&lt;BR /&gt;O=Cisco Systems, CN=Cisco Manufacturing CA&lt;BR /&gt;Serial Number (Hex):&lt;BR /&gt;6F454BA80000000D78FC&lt;BR /&gt;Validity :&lt;BR /&gt;Start : Sep 7 23:08:37 2012 GMT&lt;BR /&gt;End : Sep 7 23:18:37 2022 GMT&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&lt;BR /&gt;Signature Algorithm :&lt;BR /&gt;sha1WithRSAEncryption&lt;BR /&gt;Hash key :&lt;BR /&gt;SHA1 Fingerprint : 35:cf:5a:c5:f5:79:b0:87:ac:08:d2:ef:ce:e3:1f:18:7b: 56:61:11&lt;BR /&gt;SHA256 Fingerprint : 89:ba:39:23:5b:0e:c6:13:7d:ea:0f:7a:08:ba:91:6d:1 e:de:5c:61:13:7b:99:10:1d:1b:ff:02:3a:6c:82:46&lt;/P&gt;</description>
      <pubDate>Thu, 29 Sep 2022 14:50:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cisco-wireless-cannot-add-access-points-to-wlc2500/m-p/4696116#M246590</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2022-09-29T14:50:33Z</dc:date>
    </item>
  </channel>
</rss>

