<?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: Layer 2 Border node ethernet map-cache in Software-Defined Access (SD-Access)</title>
    <link>https://community.cisco.com/t5/software-defined-access-sd-access/layer-2-border-node-ethernet-map-cache/m-p/4935263#M2688</link>
    <description>&lt;P&gt;I have two dedicated control plane nodes. Our border nodes are not map-servers&lt;/P&gt;</description>
    <pubDate>Fri, 06 Oct 2023 08:07:07 GMT</pubDate>
    <dc:creator>Jakob Mellberg</dc:creator>
    <dc:date>2023-10-06T08:07:07Z</dc:date>
    <item>
      <title>Layer 2 Border node ethernet map-cache</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/layer-2-border-node-ethernet-map-cache/m-p/4934139#M2684</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;We have deployed a stacked 9500 as our layer 2 border node, configured with lan-automation and have an issue with migrating wired clients.&lt;/P&gt;&lt;P&gt;We have a solution where clients authenticate with MAB over ISE and can migrate their wired connection to other buildings or offices.&lt;BR /&gt;When a client that uses a layer 2 vlan, not an anycast gateway network it works if the client have not been connected before.&lt;BR /&gt;But migrating a wired connection from one switch to another switch DHCP packets are being lost on the way back.&lt;/P&gt;&lt;P&gt;Looking on the layer 2 border node the ethernet map-cache locator for that mac-address points to the previous switch it was connected to, when manually clearing that cache-entry the layer 2 border node recreates the map-cache and gets the correct locator and sends the return data to the correct switch.&lt;/P&gt;&lt;P&gt;I have verified that the edge-nodes are sending deregister events to the control plane nodes for the mac-address. But the layer 2 border nodes seems to not be aware of this and keeps the ethernet map-cache towards the previous switch. The expire-time is very long on the layer 2 border node for ethernet map-caches, 24H.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there something I have missed when deploying the border node?&lt;/P&gt;&lt;P&gt;Are anyone of you aware of some good workaround?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Oct 2023 14:21:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/layer-2-border-node-ethernet-map-cache/m-p/4934139#M2684</guid>
      <dc:creator>Jakob Mellberg</dc:creator>
      <dc:date>2023-10-04T14:21:26Z</dc:date>
    </item>
    <item>
      <title>Re: Layer 2 Border node ethernet map-cache</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/layer-2-border-node-ethernet-map-cache/m-p/4935241#M2686</link>
      <description>&lt;P&gt;For anyone having the same issue.&lt;/P&gt;&lt;P&gt;It looks like this bug was the cause: &lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwc71236" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwc71236&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;We updated all our switches to 17.9.4 and now when we disconnect device the map-cache updates on the border node correctly.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Oct 2023 06:39:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/layer-2-border-node-ethernet-map-cache/m-p/4935241#M2686</guid>
      <dc:creator>Jakob Mellberg</dc:creator>
      <dc:date>2023-10-06T06:39:09Z</dc:date>
    </item>
    <item>
      <title>Re: Layer 2 Border node ethernet map-cache</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/layer-2-border-node-ethernet-map-cache/m-p/4935249#M2687</link>
      <description>&lt;P&gt;thanks for input, Jakob.&lt;BR /&gt;One Q pls: is you L2-handoff BN also configured as MSMR for the LISP L2VN-services on your Fabric Site?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Oct 2023 06:59:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/layer-2-border-node-ethernet-map-cache/m-p/4935249#M2687</guid>
      <dc:creator>Andrii Oliinyk</dc:creator>
      <dc:date>2023-10-06T06:59:22Z</dc:date>
    </item>
    <item>
      <title>Re: Layer 2 Border node ethernet map-cache</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/layer-2-border-node-ethernet-map-cache/m-p/4935263#M2688</link>
      <description>&lt;P&gt;I have two dedicated control plane nodes. Our border nodes are not map-servers&lt;/P&gt;</description>
      <pubDate>Fri, 06 Oct 2023 08:07:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/layer-2-border-node-ethernet-map-cache/m-p/4935263#M2688</guid>
      <dc:creator>Jakob Mellberg</dc:creator>
      <dc:date>2023-10-06T08:07:07Z</dc:date>
    </item>
  </channel>
</rss>

