<?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>sujet Re: NX-OS Fabric IP architecture dans Discussions de Data Center</title>
    <link>https://community.cisco.com/t5/discussions-de-data-center/nx-os-fabric-ip-architecture/m-p/4919632#M182</link>
    <description>&lt;P&gt;Look at the architecture to understand :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/dcn/whitepapers/cisco-application-centric-infrastructure-design-guide.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/dcn/whitepapers/cisco-application-centric-infrastructure-design-guide.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;satellite leaf, - May be referring remote location leaf switches (i am guessing the name can be made easy to locally understand).&lt;/P&gt;
&lt;P&gt;Remote Leaf Switch: Addresses the need to extend connectivity and consistent policies to remote locations that are connected using a private or a public network (such as a WAN) where it’s not possible or desirable to deploy a full Cisco ACI pod (with leaf and spine switches). The Cisco APIC cluster in the main location can manage the remote leaf switches connected over an IP network as if they were local leaf switches&lt;/P&gt;</description>
    <pubDate>Thu, 07 Sep 2023 15:49:19 GMT</pubDate>
    <dc:creator>balaji.bandi</dc:creator>
    <dc:date>2023-09-07T15:49:19Z</dc:date>
    <item>
      <title>NX-OS Fabric IP architecture</title>
      <link>https://community.cisco.com/t5/discussions-de-data-center/nx-os-fabric-ip-architecture/m-p/4919619#M181</link>
      <description>&lt;P&gt;Hello guys,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm new on the NX-OS Spine and leaf&amp;nbsp; Fabric IP Architecture, and i would like to understand some terms that i saw in our visio schemas like satellite leaf, centrale spine.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 15:34:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/discussions-de-data-center/nx-os-fabric-ip-architecture/m-p/4919619#M181</guid>
      <dc:creator>Kaneki007</dc:creator>
      <dc:date>2023-09-07T15:34:45Z</dc:date>
    </item>
    <item>
      <title>Re: NX-OS Fabric IP architecture</title>
      <link>https://community.cisco.com/t5/discussions-de-data-center/nx-os-fabric-ip-architecture/m-p/4919632#M182</link>
      <description>&lt;P&gt;Look at the architecture to understand :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/dcn/whitepapers/cisco-application-centric-infrastructure-design-guide.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/dcn/whitepapers/cisco-application-centric-infrastructure-design-guide.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;satellite leaf, - May be referring remote location leaf switches (i am guessing the name can be made easy to locally understand).&lt;/P&gt;
&lt;P&gt;Remote Leaf Switch: Addresses the need to extend connectivity and consistent policies to remote locations that are connected using a private or a public network (such as a WAN) where it’s not possible or desirable to deploy a full Cisco ACI pod (with leaf and spine switches). The Cisco APIC cluster in the main location can manage the remote leaf switches connected over an IP network as if they were local leaf switches&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 15:49:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/discussions-de-data-center/nx-os-fabric-ip-architecture/m-p/4919632#M182</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2023-09-07T15:49:19Z</dc:date>
    </item>
    <item>
      <title>Re: NX-OS Fabric IP architecture</title>
      <link>https://community.cisco.com/t5/discussions-de-data-center/nx-os-fabric-ip-architecture/m-p/4919662#M183</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1522062"&gt;@Kaneki007&lt;/a&gt;,&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;Satellite leaf switches are remote leaf switches connected to the central spine switches, and the central spine switches are the core switches that provide connectivity and manage the traffic within the Spine and Leaf Fabric IP architecture.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 07 Sep 2023 16:28:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/discussions-de-data-center/nx-os-fabric-ip-architecture/m-p/4919662#M183</guid>
      <dc:creator>M02@rt37</dc:creator>
      <dc:date>2023-09-07T16:28:32Z</dc:date>
    </item>
    <item>
      <title>Re: NX-OS Fabric IP architecture</title>
      <link>https://community.cisco.com/t5/discussions-de-data-center/nx-os-fabric-ip-architecture/m-p/4919668#M184</link>
      <description>&lt;P&gt;You are talking about Fabric ACI, i'm talking juste about standalone NX-OS Spine and leaf architecture, in ACI we're using ethier L3out or normal trunk link on the border leaf.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 16:39:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/discussions-de-data-center/nx-os-fabric-ip-architecture/m-p/4919668#M184</guid>
      <dc:creator>Kaneki007</dc:creator>
      <dc:date>2023-09-07T16:39:05Z</dc:date>
    </item>
    <item>
      <title>Re: NX-OS Fabric IP architecture</title>
      <link>https://community.cisco.com/t5/discussions-de-data-center/nx-os-fabric-ip-architecture/m-p/4919675#M185</link>
      <description>&lt;P&gt;But what i can't understand what is the difference between a leaf and satellite leaf, because both are directly connected to the Spines, i think the use of the satellite leaf is when we don't have more ports on a POD we add satellite leaf for ports extension but i'm not sure&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 16:42:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/discussions-de-data-center/nx-os-fabric-ip-architecture/m-p/4919675#M185</guid>
      <dc:creator>Kaneki007</dc:creator>
      <dc:date>2023-09-07T16:42:27Z</dc:date>
    </item>
    <item>
      <title>Re: NX-OS Fabric IP architecture</title>
      <link>https://community.cisco.com/t5/discussions-de-data-center/nx-os-fabric-ip-architecture/m-p/4919680#M186</link>
      <description>&lt;P&gt;If all are in same campus that may be your naming - to connect different devices. (may be)&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 16:49:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/discussions-de-data-center/nx-os-fabric-ip-architecture/m-p/4919680#M186</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2023-09-07T16:49:41Z</dc:date>
    </item>
    <item>
      <title>Re: NX-OS Fabric IP architecture</title>
      <link>https://community.cisco.com/t5/discussions-de-data-center/nx-os-fabric-ip-architecture/m-p/4919718#M187</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1522062"&gt;@Kaneki007&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Satellite leaf switches, as you mentioned, are used when you need to extend your network beyond the capacity of a single pod or data center. They are also directly connected to the spine switches, but they are located in remote or satellite data centers or locations. Satellite leaf switches effectively expand the Spine and Leaf architecture across multiple locations, providing connectivity to devices in those remote areas.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 18:13:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/discussions-de-data-center/nx-os-fabric-ip-architecture/m-p/4919718#M187</guid>
      <dc:creator>M02@rt37</dc:creator>
      <dc:date>2023-09-07T18:13:25Z</dc:date>
    </item>
  </channel>
</rss>

