<?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: 802.1x Authentication and Port-Security simultaneously in multi-auth mode in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/802-1x-authentication-and-port-security-simultaneously-in-multi/m-p/3811184#M484744</link>
    <description>In a previous job we had a similar requirement. We manually implement port-security on 8021x host facing ports. However, the requirement we required from end users/different labs was how many hosts will you want on specific ports. From there we would implement port-sec and set the max to whatever the number was that got approved. It definitely created issues from time to time with end users being unaware or missing information, and simply moving hosts to other ports causing them to go err-disabled.&lt;BR /&gt;&lt;BR /&gt;HTH!</description>
    <pubDate>Wed, 27 Feb 2019 20:04:36 GMT</pubDate>
    <dc:creator>Mike.Cifelli</dc:creator>
    <dc:date>2019-02-27T20:04:36Z</dc:date>
    <item>
      <title>802.1x Authentication and Port-Security simultaneously in multi-auth mode</title>
      <link>https://community.cisco.com/t5/network-access-control/802-1x-authentication-and-port-security-simultaneously-in-multi/m-p/3811157#M484742</link>
      <description>&lt;P&gt;We were trying to determine if there is a solution to limit then number of MAC addresses learned on a port if 802.1x is deployed in multi-auth mode. I had previously read not to use 802.1x and port-security.&amp;nbsp; I have also read that is not a supported solution.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 19:03:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/802-1x-authentication-and-port-security-simultaneously-in-multi/m-p/3811157#M484742</guid>
      <dc:creator>Alex Pfeil</dc:creator>
      <dc:date>2020-02-21T19:03:18Z</dc:date>
    </item>
    <item>
      <title>Re: 802.1x Authentication and Port-Security simultaneously in multi-auth mode</title>
      <link>https://community.cisco.com/t5/network-access-control/802-1x-authentication-and-port-security-simultaneously-in-multi/m-p/3811171#M484743</link>
      <description>&lt;P&gt;to this date there is no solution to combine the 802.1x with port security. and it still stand not combine the port-security and dot1x on same port. as port-security is at switch level and 1.x is ISE feature.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Feb 2019 19:43:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/802-1x-authentication-and-port-security-simultaneously-in-multi/m-p/3811171#M484743</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2019-02-27T19:43:49Z</dc:date>
    </item>
    <item>
      <title>Re: 802.1x Authentication and Port-Security simultaneously in multi-auth mode</title>
      <link>https://community.cisco.com/t5/network-access-control/802-1x-authentication-and-port-security-simultaneously-in-multi/m-p/3811184#M484744</link>
      <description>In a previous job we had a similar requirement. We manually implement port-security on 8021x host facing ports. However, the requirement we required from end users/different labs was how many hosts will you want on specific ports. From there we would implement port-sec and set the max to whatever the number was that got approved. It definitely created issues from time to time with end users being unaware or missing information, and simply moving hosts to other ports causing them to go err-disabled.&lt;BR /&gt;&lt;BR /&gt;HTH!</description>
      <pubDate>Wed, 27 Feb 2019 20:04:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/802-1x-authentication-and-port-security-simultaneously-in-multi/m-p/3811184#M484744</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2019-02-27T20:04:36Z</dc:date>
    </item>
    <item>
      <title>Re: 802.1x Authentication and Port-Security simultaneously in multi-auth mode</title>
      <link>https://community.cisco.com/t5/network-access-control/802-1x-authentication-and-port-security-simultaneously-in-multi/m-p/3811185#M484745</link>
      <description>&lt;P&gt;to my knowledge cisco best practice is not to configure 1.x with port-security. unless they change this practice or i gone too old.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Feb 2019 20:06:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/802-1x-authentication-and-port-security-simultaneously-in-multi/m-p/3811185#M484745</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2019-02-27T20:06:49Z</dc:date>
    </item>
    <item>
      <title>Re: 802.1x Authentication and Port-Security simultaneously in multi-auth mode</title>
      <link>https://community.cisco.com/t5/network-access-control/802-1x-authentication-and-port-security-simultaneously-in-multi/m-p/3811208#M484746</link>
      <description>That's correct. And I've seen some issues with 802.1X and port-security enabled combined with MAB IP-Phones and 1X endpoints behind them where the switchport was err-disabled when a computer was plugged in the phone pass-through port.</description>
      <pubDate>Wed, 27 Feb 2019 20:27:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/802-1x-authentication-and-port-security-simultaneously-in-multi/m-p/3811208#M484746</guid>
      <dc:creator>Maxee</dc:creator>
      <dc:date>2019-02-27T20:27:38Z</dc:date>
    </item>
    <item>
      <title>Re: 802.1x Authentication and Port-Security simultaneously in multi-auth mode</title>
      <link>https://community.cisco.com/t5/network-access-control/802-1x-authentication-and-port-security-simultaneously-in-multi/m-p/3811351#M484747</link>
      <description>&lt;P&gt;I have read that it was not a best practice. I just wanted to make sure.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2019 00:49:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/802-1x-authentication-and-port-security-simultaneously-in-multi/m-p/3811351#M484747</guid>
      <dc:creator>Alex Pfeil</dc:creator>
      <dc:date>2019-02-28T00:49:11Z</dc:date>
    </item>
  </channel>
</rss>

