{"id":5477,"date":"2026-10-25T07:34:32","date_gmt":"2026-10-25T07:34:32","guid":{"rendered":"https:\/\/geekmungus.co.uk\/?p=5477"},"modified":"2026-10-25T07:34:33","modified_gmt":"2026-10-25T07:34:33","slug":"arista-networks-simple-mlag-configuration-example-pattern","status":"publish","type":"post","link":"https:\/\/geekmungus.co.uk\/?p=5477","title":{"rendered":"Arista Networks &#8211; Simple MLAG Configuration Example Pattern"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">The MLAG (Multi Link Aggregation Group) allows two or more links to be bonded together to form a single virtual link, even when that is spread across two Leaf Switches. Fundamentally the approach for this is exactly the same as is the case with Extreme Networks, Cisco etc. only the syntax is slightly different.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"519\" height=\"444\" src=\"https:\/\/geekmungus.co.uk\/wp-content\/uploads\/2026\/10\/image-13.png\" alt=\"\" class=\"wp-image-5478\" srcset=\"https:\/\/geekmungus.co.uk\/wp-content\/uploads\/2026\/10\/image-13.png 519w, https:\/\/geekmungus.co.uk\/wp-content\/uploads\/2026\/10\/image-13-300x257.png 300w\" sizes=\"auto, (max-width: 519px) 100vw, 519px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Its a simple example where the two switches: leaf4a and leaf4b are connected together on ethernet 3 and ethernet 4 in a Port-Channel. Then an example host is connected up with a port channel to leaf4a and leaf4b Leaf Switches, however on the Leaf Switch side this is represented as an MLAG. So, from the host side it just sees a bonded connection between NIC1 and NIC2, but this at the Leaf switch side is an MLAG. So the loss of a link or the loss of a Leaf Switch does not affect connectivity to the host.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Its also worth noting that there needs to be a dedicated ISL (ISC) Inter-Switch-Link (Inter-Switch-Connection) VLAN tagged between the two Leaf Switches, each with an IP address configured at each end, so that the MLAG telemetry may take place between the two member switches of the MLAG.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Git Repository: <a href=\"https:\/\/github.com\/tristanhself\/arista-networks-useful-patterns\/tree\/main\/mlag\">https:\/\/github.com\/tristanhself\/arista-networks-useful-patterns\/tree\/main\/mlag<\/a><\/p>\n\n\n\n<h1 class=\"wp-block-heading\">Example Configuration<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">Example MLAG cluster configuration, coupled with the presentation of a VLAN 200 to a connected host (untagged, i.e. native) via two MLAG ports ethernet5 within Port-Channel 5. The configuration given below is just an excerpt, some configuration is omitted for brevity and clarity.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">A Side Leaf Switch (leaf4a)<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>vlan 200\n   name TESTVLAN1\n\nvlan 4094\n   name MLAG\n   trunk group MLAG\n\ninterface Vlan4094\n   description MLAG\n   mtu 1500\n   no autostate\n   ip address 10.255.1.64\/31\n\nmlag configuration\n   domain-id L3_LEAF4\n   local-interface Vlan4094\n   peer-address 10.255.1.65\n   peer-link Port-Channel3\n   reload-delay mlag 300\n   reload-delay non-mlag 330\n\ninterface Port-Channel3\n   description MLAG_leaf4b\n   switchport mode trunk\n   switchport trunk group MLAG\n\ninterface Port-Channel5\n   description SERVER-PC9-BOND1\n   switchport trunk native vlan 200\n   switchport mode trunk\n   mlag 5\n   spanning-tree portfast edge\n\ninterface Ethernet3\n   description MLAG-leaf4b-eth3\n   channel-group 3 mode active\n\ninterface Ethernet4\n   description MLAG-leaf4b-eth4\n   channel-group 3 mode active\n\ninterface Ethernet5\n   description SERVER-PC9-NIC1\n   channel-group 5 mode active<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">B Side Leaf Switch (leaf4b)<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>vlan 200\n   name TESTVLAN1\n\nvlan 4094\n   name MLAG\n   trunk group MLAG\n\ninterface Vlan4094\n   description MLAG\n   mtu 1500\n   no autostate\n   ip address 10.255.1.65\/31\n\nmlag configuration\n   domain-id L3_LEAF4\n   local-interface Vlan4094\n   peer-address 10.255.1.64\n   peer-link Port-Channel3\n   reload-delay mlag 300\n   reload-delay non-mlag 330\n\ninterface Port-Channel3\n   description MLAG_leaf4a\n   switchport mode trunk\n   switchport trunk group MLAG\n\ninterface Port-Channel5\n   description SERVER-PC9-BOND1\n   switchport trunk native vlan 200\n   switchport mode trunk\n   mlag 5\n   spanning-tree portfast edge\n\ninterface Ethernet3\n   description MLAG-leaf4a-eth3\n   channel-group 3 mode active\n\ninterface Ethernet4\n   description MLAG-leaf4a-eth4\n   channel-group 3 mode active\n\ninterface Ethernet5\n   description SERVER-PC9-NIC2\n   channel-group 5 mode active<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Configuration Deep-Dive<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Stepping through each part of the configuration in turn to explain.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We firstly have the VLAN 200 definition which creates the VLAN on the switch.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We then have the VLAN 4094 definition which creates the VLAN which will be used by the MLAG for the inter-switch communication. Its a member of the trunk group MLAG which we&#8217;ll come onto shortly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We then have the definition of the VLAN 4094 IP interface which specifies the IP address of this particular MLAG member, 10.255.1.64 or 10.255.1.65 in this case. These IPs are crucial, they are used for the MLAG cluster to communicate between each other to maintain state and switch traffic correctly to any member ports of the MLAG.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We then have the actual MLAG configuration that specifies the domain-id, a name for the MLAG pair, both members of the MLAG must have the same domain-id, &#8220;L3_LEAF4&#8221; in this example. The &#8220;local-interface&#8221; sets which VLAN\/interface is being used for the communication between each side of the MLAG, i.e. between the peers.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Here you also see the peer address, i.e. the IP address of the other side of the MLAG cluster. We also specify the Port-Channel 3 to denote which is the ISL to be used for this communication.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We then have all the interface configurations, in this case Port-Channel 3 is a LAG\/Ether-Channel\/Port-Channel that consists of two ports Ethernet3 and Ethernet4.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Then we have Port-Channel 5 which in this example is the MLAG used by Ethernet5 on leaf4a and leaf4b to be where the test Host is connected up to.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We also see on this Port-Channel 5 configuration, that &#8220;mlag 5&#8221; is specified that gives this MLAG an ID. Its strongly recommended to use the same MLAG ID as the ethernet number to make support simpler and easier to identify the member ports.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An interesting thing to notice is that unlike with Extreme Networks XOS, you don&#8217;t need to tag the user-facing VLANs across the ISL (inter-switch-link), the MLAG configuration does this for you. All you need to do is create the VLAN and then tag\/add it to the edge ports and the MLAG configuration will ensure it is present on the ISL for you.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The MLAG (Multi Link Aggregation Group) allows two or more links to be bonded together to form a single virtual link, even when that is spread across two Leaf Switches. Fundamentally the approach for this is exactly the same as is the case with Extreme Networks, Cisco etc. only the syntax is slightly different. Its &#8230; <a title=\"Arista Networks &#8211; Simple MLAG Configuration Example Pattern\" class=\"read-more\" href=\"https:\/\/geekmungus.co.uk\/?p=5477\" aria-label=\"Read more about Arista Networks &#8211; Simple MLAG Configuration Example Pattern\">Read more<\/a><\/p>\n","protected":false},"author":4,"featured_media":5479,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[64,17],"tags":[],"class_list":["post-5477","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-arista-networks","category-networking"],"_links":{"self":[{"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/5477","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=5477"}],"version-history":[{"count":1,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/5477\/revisions"}],"predecessor-version":[{"id":5480,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/5477\/revisions\/5480"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=\/wp\/v2\/media\/5479"}],"wp:attachment":[{"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=5477"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=5477"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/geekmungus.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=5477"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}