<?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 Only the active unit is in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/5520-wlc-https-error-on-secondary-controller/m-p/2954602#M5735</link>
    <description>&lt;P&gt;Only the active unit is reachable via management. The standby unit is not reachable unless you console into the unit. You can ping the redundancy management interface to check its online, but you will see that on the show redundancy summary.&lt;/P&gt;
&lt;P&gt;-Scott&lt;/P&gt;
&lt;P&gt;*** Please rate helpful post ***&lt;/P&gt;</description>
    <pubDate>Thu, 24 Nov 2016 21:19:39 GMT</pubDate>
    <dc:creator>Scott Fella</dc:creator>
    <dc:date>2016-11-24T21:19:39Z</dc:date>
    <item>
      <title>5520 WLC: https error on secondary controller</title>
      <link>https://community.cisco.com/t5/wireless/5520-wlc-https-error-on-secondary-controller/m-p/2954600#M5733</link>
      <description>&lt;P&gt;Hi everybody!&lt;BR /&gt;&lt;BR /&gt;We have two 5520 WLC with redundancy enabled (SSO). When the primary controller is in standby mode we can't access the management interface web page with https.&lt;/P&gt;
&lt;P&gt;We try to generate web certificates on the secondary controller but after rebooting it, there no certificate (with "show certificate all" command).&lt;/P&gt;
&lt;P&gt;When the primary controller is in active mode the https web page work correctly.&lt;/P&gt;
&lt;P&gt;How can we fix this?&lt;BR /&gt;&lt;BR /&gt;Thank you for your help,&lt;BR /&gt;&lt;BR /&gt;Yoan&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 13:09:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/5520-wlc-https-error-on-secondary-controller/m-p/2954600#M5733</guid>
      <dc:creator>beta15</dc:creator>
      <dc:date>2021-07-05T13:09:40Z</dc:date>
    </item>
    <item>
      <title>Console into the WLC and see</title>
      <link>https://community.cisco.com/t5/wireless/5520-wlc-https-error-on-secondary-controller/m-p/2954601#M5734</link>
      <description>&lt;P&gt;Console into the WLC and see what is happening.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;What firmware version is the pair running on?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Nov 2016 21:12:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/5520-wlc-https-error-on-secondary-controller/m-p/2954601#M5734</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2016-11-24T21:12:42Z</dc:date>
    </item>
    <item>
      <title>Only the active unit is</title>
      <link>https://community.cisco.com/t5/wireless/5520-wlc-https-error-on-secondary-controller/m-p/2954602#M5735</link>
      <description>&lt;P&gt;Only the active unit is reachable via management. The standby unit is not reachable unless you console into the unit. You can ping the redundancy management interface to check its online, but you will see that on the show redundancy summary.&lt;/P&gt;
&lt;P&gt;-Scott&lt;/P&gt;
&lt;P&gt;*** Please rate helpful post ***&lt;/P&gt;</description>
      <pubDate>Thu, 24 Nov 2016 21:19:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/5520-wlc-https-error-on-secondary-controller/m-p/2954602#M5735</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2016-11-24T21:19:39Z</dc:date>
    </item>
    <item>
      <title>So when it comes to your</title>
      <link>https://community.cisco.com/t5/wireless/5520-wlc-https-error-on-secondary-controller/m-p/2954603#M5736</link>
      <description>&lt;P&gt;So when it comes to your certificate, do a force-failover to the co triller that doesn't have the proper certificate. When SSO is established, upload the certificate to that controller and save and issue another force-failover command. You have to install certificate separate and this is a nice workaround to get certificates installed without taking a downtime.&lt;/P&gt;
&lt;P&gt;-Scott&lt;/P&gt;
&lt;P&gt;*** Please rate helpful posts ***&lt;/P&gt;</description>
      <pubDate>Thu, 24 Nov 2016 21:22:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/5520-wlc-https-error-on-secondary-controller/m-p/2954603#M5736</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2016-11-24T21:22:11Z</dc:date>
    </item>
  </channel>
</rss>

