<?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 Import existing VXLAN evpn fabric into DCNM in Other Data Center Subjects</title>
    <link>https://community.cisco.com/t5/other-data-center-subjects/import-existing-vxlan-evpn-fabric-into-dcnm/m-p/3337215#M6331</link>
    <description>&lt;P&gt;As title, if I have a manually configured VXLAN evpn fabric, will this get all imported fine into DCNM if I add the devices?&lt;/P&gt;</description>
    <pubDate>Fri, 01 Mar 2019 16:44:24 GMT</pubDate>
    <dc:creator>siiiilky</dc:creator>
    <dc:date>2019-03-01T16:44:24Z</dc:date>
    <item>
      <title>Import existing VXLAN evpn fabric into DCNM</title>
      <link>https://community.cisco.com/t5/other-data-center-subjects/import-existing-vxlan-evpn-fabric-into-dcnm/m-p/3337215#M6331</link>
      <description>&lt;P&gt;As title, if I have a manually configured VXLAN evpn fabric, will this get all imported fine into DCNM if I add the devices?&lt;/P&gt;</description>
      <pubDate>Fri, 01 Mar 2019 16:44:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/other-data-center-subjects/import-existing-vxlan-evpn-fabric-into-dcnm/m-p/3337215#M6331</guid>
      <dc:creator>siiiilky</dc:creator>
      <dc:date>2019-03-01T16:44:24Z</dc:date>
    </item>
    <item>
      <title>Re: Import existing VXLAN evpn fabric into DCNM</title>
      <link>https://community.cisco.com/t5/other-data-center-subjects/import-existing-vxlan-evpn-fabric-into-dcnm/m-p/3337322#M6332</link>
      <description>I’ve run into issues with DCNM in the past if switch/route configuration is not blank it will erase the current configuration. This is supposed to be fixed soon. I would copy configuration and save to your computer before you try to import the device into DCNM</description>
      <pubDate>Sun, 25 Feb 2018 08:33:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/other-data-center-subjects/import-existing-vxlan-evpn-fabric-into-dcnm/m-p/3337322#M6332</guid>
      <dc:creator>Rick1776</dc:creator>
      <dc:date>2018-02-25T08:33:09Z</dc:date>
    </item>
    <item>
      <title>Re: Import existing VXLAN evpn fabric into DCNM</title>
      <link>https://community.cisco.com/t5/other-data-center-subjects/import-existing-vxlan-evpn-fabric-into-dcnm/m-p/3342838#M6349</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Are you are asking about importing with the ability to modify the individual VXLAN VRFs and VNIs to then push the modified configuration down to the device? If so, that ability I believe is in the works and is not available as of 10.4.2. At the moment however, just discovering the device will not remove any configuration unless you deliberately push a configuration change.&lt;/P&gt;
&lt;P&gt;After discovering the VXLAN configured device, you will be able to see the different VRFs and VNIs.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Mar 2018 00:15:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/other-data-center-subjects/import-existing-vxlan-evpn-fabric-into-dcnm/m-p/3342838#M6349</guid>
      <dc:creator>Branden Varney</dc:creator>
      <dc:date>2018-03-06T00:15:58Z</dc:date>
    </item>
  </channel>
</rss>

