<?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 Re: ISE inside ACI Fabric in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-inside-aci-fabric/m-p/4765178#M579476</link>
    <description>&lt;P&gt;Yup nothing special here.&amp;nbsp; ACI thinks ISE is just a normal server.&amp;nbsp; ISE thinks ACI is just a normal switch.&lt;/P&gt;</description>
    <pubDate>Mon, 30 Jan 2023 12:44:56 GMT</pubDate>
    <dc:creator>ahollifield</dc:creator>
    <dc:date>2023-01-30T12:44:56Z</dc:date>
    <item>
      <title>ISE inside ACI Fabric</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-inside-aci-fabric/m-p/4764342#M579457</link>
      <description>&lt;P&gt;We are planning the install of a new ISE 3.1 deployment and I have been asked to evaluate the pros and cons of installing the required SNS-3695 appliances within our data centre and physically connecting to our ACI fabric production tenant.&lt;/P&gt;&lt;P&gt;I have reviewed and I cant see anything technically wrong with connecting ISE physically to ACI unless there are considerations that we need to make if we plan to implement TrustSec and ACI integration. This is not something that we plan to in the near future, but I dont want to back ourselves into a corner if we decide to implement this at a later date. Has anyone deployed ISE within ACI before and are there any gotchas that we need to be aware of?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 28 Jan 2023 00:07:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-inside-aci-fabric/m-p/4764342#M579457</guid>
      <dc:creator>packet2020</dc:creator>
      <dc:date>2023-01-28T00:07:14Z</dc:date>
    </item>
    <item>
      <title>Re: ISE inside ACI Fabric</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-inside-aci-fabric/m-p/4764751#M579473</link>
      <description>&lt;P&gt;I don't believe there is anything special or unique about ISE and ACI. I am not an ACI expert, but from ACI's point&amp;nbsp;of view, ISE is just a simple server. There is an application network traffic layer (e.g. gig0 on ISE for SSH/HTTPS/RADIUS/TACACS etc.) and then also the CIMC on the SNS out of band server management traffic (you'd probably host the CIMC traffic on a separate VLAN - but it's not mandatory).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 29 Jan 2023 23:51:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-inside-aci-fabric/m-p/4764751#M579473</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2023-01-29T23:51:33Z</dc:date>
    </item>
    <item>
      <title>Re: ISE inside ACI Fabric</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-inside-aci-fabric/m-p/4765178#M579476</link>
      <description>&lt;P&gt;Yup nothing special here.&amp;nbsp; ACI thinks ISE is just a normal server.&amp;nbsp; ISE thinks ACI is just a normal switch.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 12:44:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-inside-aci-fabric/m-p/4765178#M579476</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-01-30T12:44:56Z</dc:date>
    </item>
  </channel>
</rss>

