<?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 vlan merge in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-vlan-merge/m-p/4770669#M579697</link>
    <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/990925"&gt;@JianfengWang5009&lt;/a&gt; As shown above, VLAN groups should help and most of Cisco catalyst switches will take the VLAN assignment from ISE and apply it as a VLAN group or a VLAN. Check out this blog -- &lt;A href="https://thecciejourney.wordpress.com/2017/07/13/802-1x-vlan-user-distribution-vlan-group/" target="_self"&gt;802.1x VLAN User Distribution (VLAN Group) -- the CCIE journey&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 07 Feb 2023 20:16:44 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2023-02-07T20:16:44Z</dc:date>
    <item>
      <title>ISE vlan merge</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-vlan-merge/m-p/4767707#M579602</link>
      <description>&lt;P&gt;Our ISE server return VLAN names for various user vlans as based on user identity. Some of them doesn’t apply to certain area. On those switches, there is no corresponding vlan. We want a certain vlan host all users in such area. Say HR user log in to a switch in branch, the HR vlan doesn’t exist. I want switch put user in employees instead. How can I put a vlan with 2 name or merge 2 vlans?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 18:58:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-vlan-merge/m-p/4767707#M579602</guid>
      <dc:creator>JianfengWang5009</dc:creator>
      <dc:date>2023-02-02T18:58:50Z</dc:date>
    </item>
    <item>
      <title>Re: ISE vlan merge</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-vlan-merge/m-p/4768117#M579615</link>
      <description>&lt;P&gt;Why change VLANs at all?&amp;nbsp; What is the use-case?&amp;nbsp; I don't think what you are describing is possible.&amp;nbsp; If you must change VLANs, then I would put the NADs that do not have the HR VLAN into a separate NAD group and make policies accordingly so ISE doesn't push the HR VLAN to those switches.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Feb 2023 13:59:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-vlan-merge/m-p/4768117#M579615</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-02-03T13:59:17Z</dc:date>
    </item>
    <item>
      <title>Re: ISE vlan merge</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-vlan-merge/m-p/4768150#M579616</link>
      <description>&lt;P&gt;hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/990925"&gt;@JianfengWang5009&lt;/a&gt;&amp;nbsp;, ISE is not capable of creating/merge vlans within a switch , the ISE is capable only to assign vlans with base on your authentications.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Feb 2023 14:37:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-vlan-merge/m-p/4768150#M579616</guid>
      <dc:creator>Rodrigo Diaz</dc:creator>
      <dc:date>2023-02-03T14:37:43Z</dc:date>
    </item>
    <item>
      <title>Re: ISE vlan merge</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-vlan-merge/m-p/4768163#M579617</link>
      <description>&lt;P&gt;I agree with&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/199513"&gt;@ahollifield&lt;/a&gt;&amp;nbsp;, I don't believe what you are trying to achieve is possible. End of the day, ISE just returns attributes via RADIUS, it doesn't really dictate anything on the switches in this case. One thing you can potentially do which is quite common is to configure a parking VLAN on all the switches, and then on ISE you associate that parking VLAN to the default authorization rule. By doing so if the user/machine does not match any of the specific authorization rules, they will hit the default rule and will be placed into the parking VLAN.&lt;/P&gt;</description>
      <pubDate>Fri, 03 Feb 2023 14:56:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-vlan-merge/m-p/4768163#M579617</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2023-02-03T14:56:49Z</dc:date>
    </item>
    <item>
      <title>Re: ISE vlan merge</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-vlan-merge/m-p/4768789#M579653</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/990925"&gt;@JianfengWang5009&lt;/a&gt;&amp;nbsp;I agree with all responded.&lt;/P&gt;
&lt;P&gt;Perhaps, you may use VLAN groups but you need to configure them on the switches. For example, on a switch, configure the following:&lt;/P&gt;
&lt;LI-CODE lang="java"&gt;vlan 10
 name Employees

vlan group HR vlan-list 10
vlan group Marketing vlan-list 10
&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 05 Feb 2023 03:09:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-vlan-merge/m-p/4768789#M579653</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2023-02-05T03:09:27Z</dc:date>
    </item>
    <item>
      <title>Re: ISE vlan merge</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-vlan-merge/m-p/4770489#M579692</link>
      <description>I think this is not ISE issue but how switch handles ISE reply. The user is authenticated successful with a policy match. It is just for some location, this VLAN assignment is not proper. If we don't have the VLAN name, the switch ends up with failed authorize. So, We'd like to use a working VLAN to give it a second name.&lt;BR /&gt;</description>
      <pubDate>Tue, 07 Feb 2023 14:49:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-vlan-merge/m-p/4770489#M579692</guid>
      <dc:creator>JianfengWang5009</dc:creator>
      <dc:date>2023-02-07T14:49:15Z</dc:date>
    </item>
    <item>
      <title>Re: ISE vlan merge</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-vlan-merge/m-p/4770669#M579697</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/990925"&gt;@JianfengWang5009&lt;/a&gt; As shown above, VLAN groups should help and most of Cisco catalyst switches will take the VLAN assignment from ISE and apply it as a VLAN group or a VLAN. Check out this blog -- &lt;A href="https://thecciejourney.wordpress.com/2017/07/13/802-1x-vlan-user-distribution-vlan-group/" target="_self"&gt;802.1x VLAN User Distribution (VLAN Group) -- the CCIE journey&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Feb 2023 20:16:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-vlan-merge/m-p/4770669#M579697</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2023-02-07T20:16:44Z</dc:date>
    </item>
  </channel>
</rss>

