<?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 N+1 or 1+1 with client SSO in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/n-1-or-1-1-with-client-sso/m-p/3339846#M164240</link>
    <description>&lt;P&gt;I have to solve an issue with redundancy and i was wondering which option would require me less gear for redundancy?&amp;nbsp; would it be N+1 or 1+1 with SSO?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Would anyone have come across similar like issue?&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jul 2021 15:19:14 GMT</pubDate>
    <dc:creator>antonios.skoulariotis</dc:creator>
    <dc:date>2021-07-05T15:19:14Z</dc:date>
    <item>
      <title>N+1 or 1+1 with client SSO</title>
      <link>https://community.cisco.com/t5/wireless/n-1-or-1-1-with-client-sso/m-p/3339846#M164240</link>
      <description>&lt;P&gt;I have to solve an issue with redundancy and i was wondering which option would require me less gear for redundancy?&amp;nbsp; would it be N+1 or 1+1 with SSO?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Would anyone have come across similar like issue?&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 15:19:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/n-1-or-1-1-with-client-sso/m-p/3339846#M164240</guid>
      <dc:creator>antonios.skoulariotis</dc:creator>
      <dc:date>2021-07-05T15:19:14Z</dc:date>
    </item>
    <item>
      <title>Re: N+1 or 1+1 with client SSO</title>
      <link>https://community.cisco.com/t5/wireless/n-1-or-1-1-with-client-sso/m-p/3339923#M164241</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;N+1 requires less gear. But I think this is not the correct approach.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Both method provide redundancy however they are pretty much different in terms of efficiency.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;N+1 HA does not protect&amp;nbsp; your network from downtime. When the primary wlc goes down, all AP will reboot and the process of join in the backup wlc will take a minute or so.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;SSO in the other hands is totally transparent to the end user. It is truly redundancy.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-If I helped you somehow, please, rate it as useful.-&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Feb 2018 20:31:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/n-1-or-1-1-with-client-sso/m-p/3339923#M164241</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2018-02-28T20:31:06Z</dc:date>
    </item>
    <item>
      <title>Re: N+1 or 1+1 with client SSO</title>
      <link>https://community.cisco.com/t5/wireless/n-1-or-1-1-with-client-sso/m-p/3340132#M164242</link>
      <description>SSO: 2 WLCs&lt;BR /&gt;1+1: 2 WLCs&lt;BR /&gt;N+1: &amp;gt;2WLCs&lt;BR /&gt;&lt;BR /&gt;SSO is the preferred option, since you only need an SKU license on the redundant unit.</description>
      <pubDate>Thu, 01 Mar 2018 04:15:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/n-1-or-1-1-with-client-sso/m-p/3340132#M164242</guid>
      <dc:creator>biaacer2</dc:creator>
      <dc:date>2018-03-01T04:15:33Z</dc:date>
    </item>
    <item>
      <title>Re: N+1 or 1+1 with client SSO</title>
      <link>https://community.cisco.com/t5/wireless/n-1-or-1-1-with-client-sso/m-p/3340171#M164243</link>
      <description>&lt;P&gt;my 2 cent.......&lt;/P&gt;
&lt;P&gt;If you have 2504 WLCs then it will support&amp;nbsp; only HA N+1 not AP/Client SSO.&lt;/P&gt;
&lt;P&gt;5508 supports both but best would to go with SSO.&lt;/P&gt;
&lt;P&gt;Here are guide for both:&lt;/P&gt;
&lt;P&gt;1. For N+1:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://rscciew.wordpress.com/2014/06/07/n1-high-availability-configuration-on-cisco-2504wlc/" target="_blank"&gt;https://rscciew.wordpress.com/2014/06/07/n1-high-availability-configuration-on-cisco-2504wlc/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. For SSO:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://networkguy.de/?p=558" target="_blank"&gt;https://networkguy.de/?p=558&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Dont forget to rate helpful posts&lt;/P&gt;</description>
      <pubDate>Thu, 01 Mar 2018 06:10:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/n-1-or-1-1-with-client-sso/m-p/3340171#M164243</guid>
      <dc:creator>Sandeep Choudhary</dc:creator>
      <dc:date>2018-03-01T06:10:16Z</dc:date>
    </item>
    <item>
      <title>Re: N+1 or 1+1 with client SSO</title>
      <link>https://community.cisco.com/t5/wireless/n-1-or-1-1-with-client-sso/m-p/3824288#M164244</link>
      <description>&lt;P&gt;Hi.&lt;BR /&gt;I disagree that HA is better than N+1.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Sure if one controller goes down the AP's need to reboot and join a backup controller, although for installing newer software versions I think its easier to do first in the backup WLC, failover one test AP to the newer upgraded controller and do the necessary test before, failover the AP's during the night via Cisco Prime job, and in the next morning do the same upgrade on the second controller.&lt;BR /&gt;&lt;BR /&gt;In HA mode, as we configure just 'one' controller, the upgrade need to occur after working hours, that in some cases include weekends, or during the night via automatic scheduled task. and in this case there will be an outage.&lt;BR /&gt;&lt;BR /&gt;If everybody is saying that HA is better I would like to see your point of view.&lt;BR /&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jun 2021 08:20:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/n-1-or-1-1-with-client-sso/m-p/3824288#M164244</guid>
      <dc:creator>Bruno Dinis</dc:creator>
      <dc:date>2021-06-10T08:20:54Z</dc:date>
    </item>
  </channel>
</rss>

