<?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 Hi in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-psn-placement/m-p/3069192#M23724</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;You have to respect some latency and bandwidth. Take a look here:&amp;nbsp;https://communities.cisco.com/docs/DOC-64317&lt;/P&gt;
&lt;P&gt;There is an excel sheet provided for your design.&lt;/P&gt;
&lt;P&gt;From my personal experience, I've deployed some ISE cross Europe and Africa and I never installed any ISE locally (except 1 time where the line wasn't so reliable). All the time, based on customer design, there were in central points (Datacenters).&lt;/P&gt;
&lt;P&gt;I'm talking about Africa because a lot of sites where with Satellite connectivity and it is working well. However, we were below or equal to the limitations.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;As soon as you respect the limitations, you can deploy them as you want.&lt;/P&gt;
&lt;P&gt;Anyway, as I guess you'll have a POC phase (test phase), you can start with a central point (to validate that everything is working as expected) and deploy new PSN locally for very high latency sites.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks so much&lt;/P&gt;
&lt;P&gt;PS: Please don't forget to rate and mark as correct answer if this answered your question.&lt;/P&gt;</description>
    <pubDate>Tue, 28 Feb 2017 17:59:11 GMT</pubDate>
    <dc:creator>Francesco Molino</dc:creator>
    <dc:date>2017-02-28T17:59:11Z</dc:date>
    <item>
      <title>ISE PSN Placement</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-psn-placement/m-p/3069191#M23723</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;I am reading up on ISE and all the different deployment options. I am interested to know where people have placed their PSNs in a Network with many remote locations and is there any rule of thumb you follow?&lt;/P&gt;
&lt;P&gt;Do you try to keep them in a centralised location as it does not seem feasible or cost effective to have a PSN at every site. From a remote location, at what latency to the centralised PSN would you start thinking about having a local Node?&lt;/P&gt;
&lt;P&gt;If having a local node to a site - would you then configure different Radius Server group on this NADs?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Interested to hear how others have placed PSNs when having multiple remote locations (some over very high latency links), e.g Satellite.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 07:30:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-psn-placement/m-p/3069191#M23723</guid>
      <dc:creator>GRANT3779</dc:creator>
      <dc:date>2019-03-11T07:30:22Z</dc:date>
    </item>
    <item>
      <title>Hi</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-psn-placement/m-p/3069192#M23724</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;You have to respect some latency and bandwidth. Take a look here:&amp;nbsp;https://communities.cisco.com/docs/DOC-64317&lt;/P&gt;
&lt;P&gt;There is an excel sheet provided for your design.&lt;/P&gt;
&lt;P&gt;From my personal experience, I've deployed some ISE cross Europe and Africa and I never installed any ISE locally (except 1 time where the line wasn't so reliable). All the time, based on customer design, there were in central points (Datacenters).&lt;/P&gt;
&lt;P&gt;I'm talking about Africa because a lot of sites where with Satellite connectivity and it is working well. However, we were below or equal to the limitations.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;As soon as you respect the limitations, you can deploy them as you want.&lt;/P&gt;
&lt;P&gt;Anyway, as I guess you'll have a POC phase (test phase), you can start with a central point (to validate that everything is working as expected) and deploy new PSN locally for very high latency sites.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks so much&lt;/P&gt;
&lt;P&gt;PS: Please don't forget to rate and mark as correct answer if this answered your question.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Feb 2017 17:59:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-psn-placement/m-p/3069192#M23724</guid>
      <dc:creator>Francesco Molino</dc:creator>
      <dc:date>2017-02-28T17:59:11Z</dc:date>
    </item>
    <item>
      <title>Morning Francesco (Or</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-psn-placement/m-p/3069193#M23725</link>
      <description>&lt;P&gt;Morning Francesco (Or Afternoon / Evening wherever you are)&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks for that very useful reply, appreciated.&lt;/P&gt;
&lt;P&gt;In addition to my initial query -&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;At the moment I have a "small deployment" with two Nodes, Primary / Secondary. Each running all the Personas. I have some WiFi related Radius config already live on these.&lt;/P&gt;
&lt;P&gt;I will be looking to deploy x2 more Nodes and move the&amp;nbsp;PSN Personas from my current Nodes to these new ones. Ideally I would like to readdress my new PSNs with the current addresses used by Admin Nodes. Reason being my WLCs are already pointing to these addresses for Radius.&lt;/P&gt;
&lt;P&gt;Is there any serious deployment issues readdressing PANs in a deployment?&lt;/P&gt;
&lt;P&gt;Am I safer just keeping as is and giving my new PSNs different IPs, and then change the WLC radius server addresses? Seems an easier way..&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 01 Mar 2017 09:29:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-psn-placement/m-p/3069193#M23725</guid>
      <dc:creator>GRANT3779</dc:creator>
      <dc:date>2017-03-01T09:29:19Z</dc:date>
    </item>
    <item>
      <title>Hi</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-psn-placement/m-p/3069194#M23727</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;With ISE running ADM/MNT personas on the same machine allows you to have at least 5 PSN.&lt;/P&gt;
&lt;P&gt;I would recommend to deploy your new PSN, then it will be synced with your actual ISE infrastructure.&lt;/P&gt;
&lt;P&gt;After that, you can change/add your PSN IP in your WLC as tertiary radius server. It won't impact anything on the wireless side.&lt;/P&gt;
&lt;P&gt;If PSN are in different locations, and if you don't have any load balancer, I would recommend to use anycast to provide high availability. that's allow to have 1 IP to configure and then play with the routing table/IP SLA.&lt;/P&gt;
&lt;P&gt;This is something I'm using quite often and there is actually a good explanation on how it works. this blog has been done by Aaron Woland (Cisco Master ISE guy!):&amp;nbsp;http://www.networkworld.com/article/3074954/security/how-to-use-anycast-to-provide-high-availability-to-a-radius-server.html&lt;/P&gt;
&lt;P&gt;Thanks so much&lt;/P&gt;
&lt;P&gt;PS: Please don't forget to rate and mark as correct answer if this answered your question.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Mar 2017 13:45:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-psn-placement/m-p/3069194#M23727</guid>
      <dc:creator>Francesco Molino</dc:creator>
      <dc:date>2017-03-01T13:45:40Z</dc:date>
    </item>
    <item>
      <title>Hi Francesco,</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-psn-placement/m-p/3069195#M23728</link>
      <description>&lt;P&gt;Hi Francesco,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Just coming back to this - high latency sites.&lt;/P&gt;
&lt;P&gt;You quoted below -&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;Anyway, as I guess you'll have a POC phase (test phase), you can start with a central point (to validate that everything is working as expected) and &lt;STRONG&gt;deploy new PSN locally for very high latency sites.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Now if I have a high latency site and decide to put a local PSN there, could this PSN still be part of my overall single deployment. Reason I am asking is that I have read any Node in a deployment needs to be max of 300ms apart.&lt;/P&gt;
&lt;P&gt;If my remote site was say 700ms from my PANs and current PSNs, what affect would this have on any locally installed PSN at that site?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 07 Mar 2017 10:05:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-psn-placement/m-p/3069195#M23728</guid>
      <dc:creator>GRANT3779</dc:creator>
      <dc:date>2017-03-07T10:05:14Z</dc:date>
    </item>
    <item>
      <title>The bandwidth and latency</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-psn-placement/m-p/3069196#M23729</link>
      <description>&lt;P&gt;The bandwidth and latency between PSN and PAN is important because lot of things going on through them like DB replication, audit logging, profiling,...)&lt;/P&gt;
&lt;P&gt;Take a look on Cisco Live slides:&amp;nbsp;http://d2zmdbbm9feqrf.cloudfront.net/2016/usa/pdf/BRKSEC-3699.pdf&lt;/P&gt;
&lt;P&gt;You can test it to see if everything works as expected even with 700ms latency.&lt;/P&gt;
&lt;P&gt;If not working, you'll need to deploy a PAN/MnT locally&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks so much&lt;/P&gt;
&lt;P&gt;PS: Please don't forget to rate and mark as correct answer if this answered your question.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Mar 2017 16:49:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-psn-placement/m-p/3069196#M23729</guid>
      <dc:creator>Francesco Molino</dc:creator>
      <dc:date>2017-03-07T16:49:18Z</dc:date>
    </item>
  </channel>
</rss>

