<?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 Cisco ISE 1.3 - Mab authentication with different vlan for each foor in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-mab-authentication-with-different-vlan-for-each/m-p/2768490#M54395</link>
    <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;A customer wants to implement MAB authentication with different vlan for every&amp;nbsp;floor. I found a tedius solution,&lt;/P&gt;&lt;P&gt;i configure the following:&lt;/P&gt;&lt;P&gt;- &amp;nbsp;different authentication profile with different vlan.&lt;/P&gt;&lt;P&gt;- add endpoint (printer etc)&amp;nbsp;on identity endpoint.&lt;/P&gt;&lt;P&gt;- create identity group endpoint that recall endpoint.&lt;/P&gt;&lt;P&gt;- at the end i create &amp;nbsp;a rule of&amp;nbsp;authorizzation that recall all element .... and Work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You know if there is a faster way to or another way to solve the problem ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks all&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 05:58:56 GMT</pubDate>
    <dc:creator>Augustgood</dc:creator>
    <dc:date>2019-03-11T05:58:56Z</dc:date>
    <item>
      <title>Cisco ISE 1.3 - Mab authentication with different vlan for each foor</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-mab-authentication-with-different-vlan-for-each/m-p/2768490#M54395</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;A customer wants to implement MAB authentication with different vlan for every&amp;nbsp;floor. I found a tedius solution,&lt;/P&gt;&lt;P&gt;i configure the following:&lt;/P&gt;&lt;P&gt;- &amp;nbsp;different authentication profile with different vlan.&lt;/P&gt;&lt;P&gt;- add endpoint (printer etc)&amp;nbsp;on identity endpoint.&lt;/P&gt;&lt;P&gt;- create identity group endpoint that recall endpoint.&lt;/P&gt;&lt;P&gt;- at the end i create &amp;nbsp;a rule of&amp;nbsp;authorizzation that recall all element .... and Work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You know if there is a faster way to or another way to solve the problem ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks all&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 05:58:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-mab-authentication-with-different-vlan-for-each/m-p/2768490#M54395</guid>
      <dc:creator>Augustgood</dc:creator>
      <dc:date>2019-03-11T05:58:56Z</dc:date>
    </item>
    <item>
      <title>Well, mab in some</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-mab-authentication-with-different-vlan-for-each/m-p/2768491#M54396</link>
      <description>&lt;P&gt;Well, mab in some environments, could be replaced by profiling, and for the rules, instead af having an authz rule for each floor, you could name your vlans in your switches the same name for "Printers", everywhere, then you would only need one authz rule, where you use the name of the vlan instead of the id number, then it doesn't matter where that printer is located, it will end up in the "Printer" vlan, whatever that might be in that specific switch.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Aug 2015 19:36:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-mab-authentication-with-different-vlan-for-each/m-p/2768491#M54396</guid>
      <dc:creator>jan.nielsen</dc:creator>
      <dc:date>2015-08-17T19:36:39Z</dc:date>
    </item>
  </channel>
</rss>

