<?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 ISE 1.1.1 firewall rules distributed deployment in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-1-1-1-firewall-rules-distributed-deployment/m-p/2137656#M199950</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try this for size.&lt;/P&gt;&lt;P&gt;In answer to the specific CoA question, I see no need for the WLC to send CoA to PSN, so just PSN to WLC as far as I can see.&lt;/P&gt;&lt;P&gt;You might be able to cut this list down, and you might have to add to it for any specific requirements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;From PSN to AD (potentially all AD nodes):&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;TCP 389, 3268, 445, 88, 464&lt;/P&gt;&lt;P&gt;UDP 389, 3268&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;From PSN to Monitoring nodes:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;TCP 443&lt;/P&gt;&lt;P&gt;UDP 20514&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;PSN to Admin Nodes (2Way):&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;TCP 443, 1521&lt;/P&gt;&lt;P&gt;ICMP echo and reply (heartbeat)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;WLC to PSN:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;TCP 443, 8443, 80, 8080&lt;/P&gt;&lt;P&gt;UDP 1645, 1646, 1812, 1813, 1700, 3799, 161, 162, 9993, 67&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;PSN to other PSN’s (2 way)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;UDP 30514, 45588, 45990&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Endpoint (Laptop) to PSN (Guest laptops just need to get to external PSN’s, internal users just to internal PSN’s)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;TCP 8443, 8905&lt;/P&gt;&lt;P&gt;UDP 8905&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Admin/Sponsor to all ISE nodes:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;TCP 22, 80, 443, 8080, 8443&lt;/P&gt;&lt;P&gt;UDP 161&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;PSN access to DNS servers:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;TCP/UDP 53&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;PSN access to NTP servers:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;UDP 123&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 06 Dec 2012 01:41:08 GMT</pubDate>
    <dc:creator>bikespace</dc:creator>
    <dc:date>2012-12-06T01:41:08Z</dc:date>
    <item>
      <title>ISE 1.1.1 firewall rules distributed deployment</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-1-1-1-firewall-rules-distributed-deployment/m-p/2137654#M199928</link>
      <description>&lt;P&gt;My question is in reference to the following link:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/ise/1.1.1/installation_guide/ise_app_e-ports.html" rel="nofollow" target="_blank"&gt;http://www.cisco.com/en/US/docs/security/ise/1.1.1/installation_guide/ise_app_e-ports.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Basically I am struggling in some areas to work out my firewall rules for a distributed deployment. The referenced documentation is not entirely clear in my opinion. In some instances it is easy to work out what ports need to be opened eg Admin node TCP 22,80,443 for management from administrator hosts/ranges. In other instances it difficult to work out eg TCP 1521 Database listener and AQ is this for ISE nodes only or for access devices aswell&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is whether there is a better document that details these requirements. What rules are meant to be ISE node - ISE node communications and which rules are for access device - ISE, or ISE - access device. One of the rules I am pretty confused about is the PSN CoA ports. SHould the rule be WLC - PSN on 1700 and 3799 or is it the otherway round or unidirectional?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am pretty sure that the ports are meant to be ISE-ISE in most instances barring the PSN for Radius and CoA.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 02:51:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-1-1-1-firewall-rules-distributed-deployment/m-p/2137654#M199928</guid>
      <dc:creator>Stephen McBride</dc:creator>
      <dc:date>2019-03-11T02:51:06Z</dc:date>
    </item>
    <item>
      <title>ISE 1.1.1 firewall rules distributed deployment</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-1-1-1-firewall-rules-distributed-deployment/m-p/2137655#M199941</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am having the same questions. So far I have opend SNMP from ISE to NAD and then all the probe trafic (DNS, DHCP...) from NAD to ISE. And I seem to be able to profile devices correctly.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Dec 2012 09:18:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-1-1-1-firewall-rules-distributed-deployment/m-p/2137655#M199941</guid>
      <dc:creator>Philip Vilhelmsson</dc:creator>
      <dc:date>2012-12-04T09:18:09Z</dc:date>
    </item>
    <item>
      <title>ISE 1.1.1 firewall rules distributed deployment</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-1-1-1-firewall-rules-distributed-deployment/m-p/2137656#M199950</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try this for size.&lt;/P&gt;&lt;P&gt;In answer to the specific CoA question, I see no need for the WLC to send CoA to PSN, so just PSN to WLC as far as I can see.&lt;/P&gt;&lt;P&gt;You might be able to cut this list down, and you might have to add to it for any specific requirements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;From PSN to AD (potentially all AD nodes):&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;TCP 389, 3268, 445, 88, 464&lt;/P&gt;&lt;P&gt;UDP 389, 3268&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;From PSN to Monitoring nodes:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;TCP 443&lt;/P&gt;&lt;P&gt;UDP 20514&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;PSN to Admin Nodes (2Way):&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;TCP 443, 1521&lt;/P&gt;&lt;P&gt;ICMP echo and reply (heartbeat)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;WLC to PSN:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;TCP 443, 8443, 80, 8080&lt;/P&gt;&lt;P&gt;UDP 1645, 1646, 1812, 1813, 1700, 3799, 161, 162, 9993, 67&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;PSN to other PSN’s (2 way)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;UDP 30514, 45588, 45990&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Endpoint (Laptop) to PSN (Guest laptops just need to get to external PSN’s, internal users just to internal PSN’s)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;TCP 8443, 8905&lt;/P&gt;&lt;P&gt;UDP 8905&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Admin/Sponsor to all ISE nodes:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;TCP 22, 80, 443, 8080, 8443&lt;/P&gt;&lt;P&gt;UDP 161&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;PSN access to DNS servers:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;TCP/UDP 53&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;PSN access to NTP servers:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;UDP 123&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2012 01:41:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-1-1-1-firewall-rules-distributed-deployment/m-p/2137656#M199950</guid>
      <dc:creator>bikespace</dc:creator>
      <dc:date>2012-12-06T01:41:08Z</dc:date>
    </item>
    <item>
      <title>ISE 1.1.1 firewall rules distributed deployment</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-1-1-1-firewall-rules-distributed-deployment/m-p/2137657#M199963</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You could also issue a show ports | inc ip &lt;PEER node=""&gt; from cli to see the ports that are successfully connected between each node. Also if you are deploying an inline node you will have to add 8443 to bikespace reference&lt;/PEER&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;PSN to Admin Nodes (2Way):&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;TCP 443, 1521, 8443&lt;/P&gt;&lt;P&gt;ICMP echo and reply (heartbeat)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2012 06:18:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-1-1-1-firewall-rules-distributed-deployment/m-p/2137657#M199963</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2012-12-06T06:18:24Z</dc:date>
    </item>
  </channel>
</rss>

