<?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: SDA - Scalable Group Tag (SGT) allowed in two places - what is best practice? in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/sda-scalable-group-tag-sgt-allowed-in-two-places-what-is-best/m-p/4266777#M564554</link>
    <description>&lt;P&gt;IMO from my experiences this is preference related.&amp;nbsp; I personally like seeing the SGT assigned in the authz policy.&amp;nbsp; A brief overview of the two options is either doing it all (assigning SGT, VN, IP Pool) via the authz profile that is then referenced in the authz policy result.&amp;nbsp; Or creating the authz profile, assigning the DNAC specified string as the vlan (this unique string can be extracted via DNAC and/or from a simple #show vlan on an edge node that is a member of your fabric), and then reference that authz profile under your authz results column.&amp;nbsp; One difference would be if you wanted to onboard a node without assigning an SGT then you would probably want to use option 2.&amp;nbsp; For more info take a peek at the following links:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/networking-documents/how-to-sda-host-onboarding-with-ise/ta-p/4012430" target="_blank" rel="noopener"&gt;https://community.cisco.com/t5/networking-documents/how-to-sda-host-onboarding-with-ise/ta-p/4012430&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/cisco-digital-network/user-to-virtual-network-association/m-p/4054485" target="_blank" rel="noopener"&gt;https://community.cisco.com/t5/cisco-digital-network/user-to-virtual-network-association/m-p/4054485&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;HTH!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 05 Jan 2021 01:44:28 GMT</pubDate>
    <dc:creator>Mike.Cifelli</dc:creator>
    <dc:date>2021-01-05T01:44:28Z</dc:date>
    <item>
      <title>SDA - Scalable Group Tag (SGT) allowed in two places - what is best practice?</title>
      <link>https://community.cisco.com/t5/network-access-control/sda-scalable-group-tag-sgt-allowed-in-two-places-what-is-best/m-p/4266686#M564551</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In an SDA deployment (using DNAC), when assigning an SGT (Scalable Group Tag) in ISE, one can select from the Authorization Policy drop-down list (shown below)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sgt1.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/100837i29126DD1ED77B41D/image-size/large?v=v2&amp;amp;px=999" role="button" title="sgt1.png" alt="sgt1.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;or, specify it in the Authorization Result Profile - what is the difference?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="sgt2.png" style="width: 848px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/100838iA2BA7DBFAFB00CD2/image-size/large?v=v2&amp;amp;px=999" role="button" title="sgt2.png" alt="sgt2.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The endpoint VLAN ID can no longer be specified when selecting the Security Group in Authorization Profile - how then does one specify the VLAN ID (as per DNAC definition) ? In our case a VN (Virtual Network) is further subnetted, and hence there will be more than one IP subnet (VLAN) on the Edge Nodes for a VN.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Jan 2021 21:21:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/sda-scalable-group-tag-sgt-allowed-in-two-places-what-is-best/m-p/4266686#M564551</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2021-01-04T21:21:03Z</dc:date>
    </item>
    <item>
      <title>Re: SDA - Scalable Group Tag (SGT) allowed in two places - what is best practice?</title>
      <link>https://community.cisco.com/t5/network-access-control/sda-scalable-group-tag-sgt-allowed-in-two-places-what-is-best/m-p/4266777#M564554</link>
      <description>&lt;P&gt;IMO from my experiences this is preference related.&amp;nbsp; I personally like seeing the SGT assigned in the authz policy.&amp;nbsp; A brief overview of the two options is either doing it all (assigning SGT, VN, IP Pool) via the authz profile that is then referenced in the authz policy result.&amp;nbsp; Or creating the authz profile, assigning the DNAC specified string as the vlan (this unique string can be extracted via DNAC and/or from a simple #show vlan on an edge node that is a member of your fabric), and then reference that authz profile under your authz results column.&amp;nbsp; One difference would be if you wanted to onboard a node without assigning an SGT then you would probably want to use option 2.&amp;nbsp; For more info take a peek at the following links:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/networking-documents/how-to-sda-host-onboarding-with-ise/ta-p/4012430" target="_blank" rel="noopener"&gt;https://community.cisco.com/t5/networking-documents/how-to-sda-host-onboarding-with-ise/ta-p/4012430&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/cisco-digital-network/user-to-virtual-network-association/m-p/4054485" target="_blank" rel="noopener"&gt;https://community.cisco.com/t5/cisco-digital-network/user-to-virtual-network-association/m-p/4054485&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;HTH!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jan 2021 01:44:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/sda-scalable-group-tag-sgt-allowed-in-two-places-what-is-best/m-p/4266777#M564554</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2021-01-05T01:44:28Z</dc:date>
    </item>
    <item>
      <title>Re: SDA - Scalable Group Tag (SGT) allowed in two places - what is best practice?</title>
      <link>https://community.cisco.com/t5/network-access-control/sda-scalable-group-tag-sgt-allowed-in-two-places-what-is-best/m-p/4266780#M564555</link>
      <description>&lt;P&gt;I prefer to use SGT on the Authz, and not the result. It's such a pain in the you know what having to drill in to the results to find the SGT that should be assigned.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;We need to feature request something like a hover over a result in the policy sets and see a list of config.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jan 2021 01:57:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/sda-scalable-group-tag-sgt-allowed-in-two-places-what-is-best/m-p/4266780#M564555</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2021-01-05T01:57:32Z</dc:date>
    </item>
    <item>
      <title>Re: SDA - Scalable Group Tag (SGT) allowed in two places - what is best practice?</title>
      <link>https://community.cisco.com/t5/network-access-control/sda-scalable-group-tag-sgt-allowed-in-two-places-what-is-best/m-p/4266781#M564556</link>
      <description>&lt;P&gt;thanks&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/833210"&gt;@Mike.Cifelli&lt;/a&gt;&amp;nbsp;- link #1 works for me. Let's see how we go&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jan 2021 01:58:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/sda-scalable-group-tag-sgt-allowed-in-two-places-what-is-best/m-p/4266781#M564556</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2021-01-05T01:58:30Z</dc:date>
    </item>
  </channel>
</rss>

