<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Arista on Council of Elrond</title><link>https://songkou.github.io/tags/arista/</link><description>Recent content in Arista on Council of Elrond</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 21 Jul 2026 04:00:00 +0800</lastBuildDate><atom:link href="https://songkou.github.io/tags/arista/index.xml" rel="self" type="application/rss+xml"/><item><title>Cheat_Sheet</title><link>https://songkou.github.io/posts/cheat-sheet/</link><pubDate>Tue, 21 Jul 2026 04:00:00 +0800</pubDate><guid>https://songkou.github.io/posts/cheat-sheet/</guid><description>&lt;p&gt;Every verification and troubleshooting command from the lab posts on this blog, collected in one place and organized &lt;strong&gt;by vendor&lt;/strong&gt; — because that&amp;rsquo;s how you reach for a cheat sheet: you&amp;rsquo;re on a box, and you need to know what to run. Each subsection links back to the post it came from and explains what each command shows and what a healthy result looks like — a command you can&amp;rsquo;t interpret is just noise.&lt;/p&gt;</description></item><item><title>Arista_VXLAN_EVPN_Lab</title><link>https://songkou.github.io/posts/arista-vxlan-bum-her-vs-multicast/</link><pubDate>Tue, 21 Jul 2026 00:30:00 +0800</pubDate><guid>https://songkou.github.io/posts/arista-vxlan-bum-her-vs-multicast/</guid><description>&lt;p&gt;A VXLAN fabric has to answer one question before any host can talk: &lt;strong&gt;how does BUM traffic (Broadcast, Unknown unicast, Multicast) reach every remote VTEP?&lt;/strong&gt; There are only two data-plane answers — head-end replication (HER, also called ingress replication) or an IP multicast underlay — and two control-plane ways to drive each of them (static configuration or BGP EVPN).&lt;/p&gt;
&lt;p&gt;This lab builds the same Arista fabric four times, once per combination:&lt;/p&gt;</description></item><item><title>Arista_EOS_RoCEv2_Lossless_Config</title><link>https://songkou.github.io/posts/arista-eos-roce-config/</link><pubDate>Mon, 20 Jul 2026 04:00:00 +0800</pubDate><guid>https://songkou.github.io/posts/arista-eos-roce-config/</guid><description>&lt;p&gt;On Cisco NX-OS, enabling PFC for RoCE normally involves several MQC (Modular QoS CLI class-map -&amp;gt; policy-map -&amp;gt; system qos) layers. On Arista EOS, basic PFC can be enabled directly on an interface with two commands:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;priority-flow-control on
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;priority-flow-control priority 3 no-drop
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&lt;img src="https://songkou.github.io/posts/arista-eos-roce-config/config-comparison.svg" alt="PFC configuration size compared: Cisco NX-OS needs several MQC layers, while basic Arista EOS PFC needs two interface commands"&gt;&lt;/p&gt;
&lt;p&gt;Those two commands are only the PFC portion of a complete RoCEv2 design. A deployable configuration must also define classification, queue scheduling, ECN, watchdog behavior, buffer thresholds, and the policy on every possible congestion point.&lt;/p&gt;</description></item></channel></rss>