<?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 This is resolved. I had the in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/no-https-ssh-access-after-testing-failover-in-ha-pair/m-p/2893300#M51075</link>
    <description>&lt;P&gt;This is resolved. I had the service port on the secondary controller configured for 192.168.1.1 which was part of the same vlan as the wired data network. I assumed it was not part of my customers wired data vlan. I configured the service port for another IP that was in an un-routed vlan. After I did this, I was able to https/SSH to the management IP while failed over to the secondary (secondary running as active).&lt;/P&gt;</description>
    <pubDate>Mon, 25 Apr 2016 20:32:24 GMT</pubDate>
    <dc:creator>jworth123</dc:creator>
    <dc:date>2016-04-25T20:32:24Z</dc:date>
    <item>
      <title>no https/SSH access after testing failover in HA pair</title>
      <link>https://community.cisco.com/t5/wireless/no-https-ssh-access-after-testing-failover-in-ha-pair/m-p/2893297#M51072</link>
      <description>&lt;P&gt;I cannot access the secondary controller, which is active after failing over while testing HA redundancy.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;The weird thing is, as soon as I enable management over wireless, I can then management it over wifi while failed over to the secondary. But, as soon as I plug in to the wired network, I can't access the GUI at all.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;These are 2 5508's with SSO enabled.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 11:56:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/no-https-ssh-access-after-testing-failover-in-ha-pair/m-p/2893297#M51072</guid>
      <dc:creator>jworth123</dc:creator>
      <dc:date>2021-07-05T11:56:12Z</dc:date>
    </item>
    <item>
      <title>what is the software version</title>
      <link>https://community.cisco.com/t5/wireless/no-https-ssh-access-after-testing-failover-in-ha-pair/m-p/2893298#M51073</link>
      <description>&lt;P&gt;what is the software version ?&lt;/P&gt;
&lt;P&gt;is the mgmt interface pingable from the wired ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 23 Apr 2016 17:09:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/no-https-ssh-access-after-testing-failover-in-ha-pair/m-p/2893298#M51073</guid>
      <dc:creator>ali aqrabawi</dc:creator>
      <dc:date>2016-04-23T17:09:39Z</dc:date>
    </item>
    <item>
      <title>8.0.121.0</title>
      <link>https://community.cisco.com/t5/wireless/no-https-ssh-access-after-testing-failover-in-ha-pair/m-p/2893299#M51074</link>
      <description>&lt;P&gt;8.0.121.0&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;yes, can ping from wired.&lt;/P&gt;</description>
      <pubDate>Sat, 23 Apr 2016 22:33:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/no-https-ssh-access-after-testing-failover-in-ha-pair/m-p/2893299#M51074</guid>
      <dc:creator>jworth123</dc:creator>
      <dc:date>2016-04-23T22:33:59Z</dc:date>
    </item>
    <item>
      <title>This is resolved. I had the</title>
      <link>https://community.cisco.com/t5/wireless/no-https-ssh-access-after-testing-failover-in-ha-pair/m-p/2893300#M51075</link>
      <description>&lt;P&gt;This is resolved. I had the service port on the secondary controller configured for 192.168.1.1 which was part of the same vlan as the wired data network. I assumed it was not part of my customers wired data vlan. I configured the service port for another IP that was in an un-routed vlan. After I did this, I was able to https/SSH to the management IP while failed over to the secondary (secondary running as active).&lt;/P&gt;</description>
      <pubDate>Mon, 25 Apr 2016 20:32:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/no-https-ssh-access-after-testing-failover-in-ha-pair/m-p/2893300#M51075</guid>
      <dc:creator>jworth123</dc:creator>
      <dc:date>2016-04-25T20:32:24Z</dc:date>
    </item>
  </channel>
</rss>

