<?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: Interface templates in data center? in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/interface-templates-in-data-center/m-p/3467847#M519633</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Arron,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Typically DC environments are secured physically, so this requirement doesn’t arise with many of our customers. We do support 802.1X on some of our DC switches, but that isn’t officially validated with ISE. For ISE to be able to deny unauthorized access, some sort of authentication is necessary. I suggest you consult the DC engineers get tips on how to do it with some sort of DC managers like DCNM or APIC controller.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~Hari &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 22 Nov 2017 00:20:29 GMT</pubDate>
    <dc:creator>hariholla</dc:creator>
    <dc:date>2017-11-22T00:20:29Z</dc:date>
    <item>
      <title>Interface templates in data center?</title>
      <link>https://community.cisco.com/t5/network-access-control/interface-templates-in-data-center/m-p/3467846#M519632</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi team,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customer has a requirement to stop people plugging into switches/servers with their laptop etc in the data center. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customer currently uses ISE in branch locations with MAB (no dot1x). The requirement is less about authenticating users but more stopping anyone plugging in (there a physical controls like biometrics to get past) with a more centralised way of controlling the policy rather than things like port security (sticky MAC etc) as it's a higher administrative overhead. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Questions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. What would be a recommended way to lock down ports in a data center environment? Is ISE in the data center overkill here? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Will service or interface templates be something they could use here? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. What do we at Cisco use in our DC environment?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Appreciate your thoughts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Arron&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Nov 2017 16:43:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/interface-templates-in-data-center/m-p/3467846#M519632</guid>
      <dc:creator>kerai08</dc:creator>
      <dc:date>2017-11-21T16:43:37Z</dc:date>
    </item>
    <item>
      <title>Re: Interface templates in data center?</title>
      <link>https://community.cisco.com/t5/network-access-control/interface-templates-in-data-center/m-p/3467847#M519633</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Arron,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Typically DC environments are secured physically, so this requirement doesn’t arise with many of our customers. We do support 802.1X on some of our DC switches, but that isn’t officially validated with ISE. For ISE to be able to deny unauthorized access, some sort of authentication is necessary. I suggest you consult the DC engineers get tips on how to do it with some sort of DC managers like DCNM or APIC controller.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~Hari &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Nov 2017 00:20:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/interface-templates-in-data-center/m-p/3467847#M519633</guid>
      <dc:creator>hariholla</dc:creator>
      <dc:date>2017-11-22T00:20:29Z</dc:date>
    </item>
  </channel>
</rss>

