<?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 Thank Jan for responding. So in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-external-radius-server/m-p/2644743#M74773</link>
    <description>&lt;P&gt;Thank Jan for responding. So if I understand you correctly, I should only send the PSN IP addresses to JANET for registration?&lt;/P&gt;</description>
    <pubDate>Tue, 03 Feb 2015 16:36:17 GMT</pubDate>
    <dc:creator>grabonlee</dc:creator>
    <dc:date>2015-02-03T16:36:17Z</dc:date>
    <item>
      <title>ISE External radius server</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-external-radius-server/m-p/2644741#M74769</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Since the JRS roam servers have to be put in a Radius Server sequence on ISE, which node IP address is meant to be registered with JANET, PAN or each PSN IP address. I would have thought it to be the PAN since all the external radius servers are configured on the PAN, but thought I should ask just to be sure. Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 05:24:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-external-radius-server/m-p/2644741#M74769</guid>
      <dc:creator>grabonlee</dc:creator>
      <dc:date>2019-03-11T05:24:20Z</dc:date>
    </item>
    <item>
      <title>Only PSNs should be entered.</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-external-radius-server/m-p/2644742#M74771</link>
      <description>&lt;P&gt;Only PSNs should be entered.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Feb 2015 16:28:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-external-radius-server/m-p/2644742#M74771</guid>
      <dc:creator>jan.nielsen</dc:creator>
      <dc:date>2015-02-03T16:28:13Z</dc:date>
    </item>
    <item>
      <title>Thank Jan for responding. So</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-external-radius-server/m-p/2644743#M74773</link>
      <description>&lt;P&gt;Thank Jan for responding. So if I understand you correctly, I should only send the PSN IP addresses to JANET for registration?&lt;/P&gt;</description>
      <pubDate>Tue, 03 Feb 2015 16:36:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-external-radius-server/m-p/2644743#M74773</guid>
      <dc:creator>grabonlee</dc:creator>
      <dc:date>2015-02-03T16:36:17Z</dc:date>
    </item>
    <item>
      <title>Yes, even though the</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-external-radius-server/m-p/2644744#M74775</link>
      <description>&lt;P&gt;Yes, even though the configuration is done on the PAN, only the ise nodes that have the policy service role enabled, will be used to forward requests using the external radius proxy feature.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Feb 2015 16:39:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-external-radius-server/m-p/2644744#M74775</guid>
      <dc:creator>jan.nielsen</dc:creator>
      <dc:date>2015-02-03T16:39:23Z</dc:date>
    </item>
    <item>
      <title>Thanks very much for the</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-external-radius-server/m-p/2644745#M74777</link>
      <description>&lt;P&gt;Thanks very much for the clarification.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Feb 2015 16:45:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-external-radius-server/m-p/2644745#M74777</guid>
      <dc:creator>grabonlee</dc:creator>
      <dc:date>2015-02-03T16:45:37Z</dc:date>
    </item>
  </channel>
</rss>

