<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Oswald Coker on Medium]]></title>
        <description><![CDATA[Stories by Oswald Coker on Medium]]></description>
        <link>https://medium.com/@leejones5?source=rss-1739f226560a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*8B22qQ0663e-etR_.jpeg</url>
            <title>Stories by Oswald Coker on Medium</title>
            <link>https://medium.com/@leejones5?source=rss-1739f226560a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:09:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@leejones5/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[VLANS IN ACI]]></title>
            <link>https://medium.com/@leejones5/vlans-in-aci-da2455b65de4?source=rss-1739f226560a------2</link>
            <guid isPermaLink="false">https://medium.com/p/da2455b65de4</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[data-center]]></category>
            <category><![CDATA[cisco]]></category>
            <category><![CDATA[software-defined-networks]]></category>
            <category><![CDATA[dns]]></category>
            <dc:creator><![CDATA[Oswald Coker]]></dc:creator>
            <pubDate>Mon, 15 Jan 2018 14:31:43 GMT</pubDate>
            <atom:updated>2018-01-15T14:31:43.708Z</atom:updated>
            <content:encoded><![CDATA[<p>In the past weeks, I have been undergoing a deep-dive study of ACI and one aspect that left me with much curiosity are the various VLAN’s that exist in the fabric. In light of this, I will explain to my best understanding the various VLAN’s that exist and how they differ from each other.</p><p>Please feel free to drop a comment and correct me wherever I come- short.</p><p>Based on the various resources I have perused through, there exist two major VLAN forms which are</p><ul><li>VLAN ID (<strong>VlanId</strong>)<br> This VLAN is a Platform Independent (PI) VLAN therefore, it is locally significant to each switch. It refers to the VLAN that is automatically bound to the Port-Group VLAN existing on the DVS derived from the VLAN pool existing in the Fabric Access Policies. It is automatically assigned within the switch.</li><li>Hardware VLAN ID (<strong>HW_VlanId</strong>)<br>Most Leaf Switch comprises of a Broadcom ASIC that is utilised when traffic is meant to be locally switched. This VLAN is utilised by the Broadcom ASIC chip.<br>To identify the VLAN that is assigned to every End-Point on a Leaf requires that you: -Connect to the Broadcom Shell on the Leaf <br><strong>vsh_lc<br>-</strong>Run the l2 show command to generate the end- points connected<br><strong>show system internal eltmc info vlan brief</strong></li></ul><p>The various VLAN types are:</p><ul><li><strong>BD_CTRL_VLAN<br> </strong>These are Infrastructure VLANs.</li><li><strong>BD_EXT_VLAN<br> </strong>These are External VLAN (eg External Layer 3 Out).</li><li><strong>FD_VLAN<br> </strong>These are VLANs used for EPGs. It is usually mapped to a specific EPG. On this VLAN, direct learning of endpoints from Hosts occurs.</li><li><strong>BD_VLAN<br> </strong>Known as Bridge Domain VLAN, it can map to a single or multiple encap (FD) VLANs and VXLANs. On this VLAN no direct learning occurs.</li></ul><p>In ACI the VLAN’s are further classified into a third form which comprises of:</p><ul><li><strong>Access_encap<br></strong>This refers to the Encapsulation VLAN that is bonded with the frame on the wire from the ACI Fabric to the Host.</li><li><strong>Fabric_encap<br></strong>This is a VXLAN ID which is universal to the fabric. The access encapsulation is mapped to the Fabric Encapsulation and it is always uniform across all the leaf nodes.</li><li><strong>BDVlan<br></strong>This is a PI VLAN for each VLAN. In relations to the VLAN types.<br>-BD_VLAN: This BDVlan is the exact same VLAN as the BD_VLAN.<br>-FD_VLAN: This BDVlan is the specific Bridge Domain to which the EPG is associated.</li></ul><p><strong>PRACTICAL</strong><br>In this section, I quickly cabled up two leaf nodes, one spine node and a single APIC to depict the VLAN’s present in a fully functional ACI Fabric.</p><p><strong>TOPOLOGY</strong><br>The topology is pictorially displayed below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/652/1*8NlJeGCqT_QWUWqgHOQLrQ.jpeg" /><figcaption>ACI Physical Topology</figcaption></figure><p>The Parameters used can be found below</p><ul><li>Name of the DVS: ASA-VMM</li><li>VLAN pool range used during creation: 100–200</li><li>Virtual Machines: <br>~<strong>Secure-VM</strong><br> -IP Address: 10.3.21.20/24<br> -Gateway: 10.3.21.1/24<br> -MAC address: 00:50:56:b5:41:46<br> -Port Group Mapping: Demo|Demo|Demo_1 <br> -VLAN from DVS: 103<br>~<strong>Unsecure-VM</strong><br> -IP Address: 10.2.20.10/24<br> -Gateway: 10.2.20.1/24<br> -MAC address: 00:50:56:b5:5e:32<br> -Port Group Mapping: Demo|Demo|Demo_2 <br> -VLAN from DVS: 172</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*MyXUwIkkSUqbJAKQC-nvIw.png" /></figure><p><strong>OBSERVATIONS</strong></p><p>On connecting to both Leaf101 and Leaf102, we can trace the {<strong>VlanId</strong>, <strong>HW_VlanId, Vlan Types </strong>and the <strong>ID assigned to the third class of category) </strong>of each individual Virtual Machines</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*asoqiBvEcktn5mMnn6-KhQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*66XbmJj8iRDkCj8dnBQyNA.png" /></figure><p>In the first image, the VLAN that is displayed is the <strong>VlanId </strong>of each VM on individual switches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EgWYrv2SAN8H5efs1zHENQ.png" /></figure><p>In the second image, you can deduce that VLANs are of type <strong>FD_VLAN </strong>representing the EPG to which they are mapped Demo-1</p><p>To obtain more information about the vlan, a command can be used <br><em>“show system internal eltmc info vlan xxx</em>”<br>For demonstration, we will consider the <strong>VlanId </strong>403.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*62IGUwgSgpt-PmaMSASPgQ.png" /></figure><p>As you can see, various parameters are shown that can assist in a deep-dive troubleshoot for each <strong>VlanId </strong>in the fabric.</p><p><strong>FOOTNOTES</strong></p><p>• <strong>vsh_lc</strong>: This is best described as a line card shell that can be utilised to check line card processes and forwarding tables specific to the Application Leaf Engine (ALE) ASIC.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da2455b65de4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>