<?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 Mr Jainanshul on Medium]]></title>
        <description><![CDATA[Stories by Mr Jainanshul on Medium]]></description>
        <link>https://medium.com/@mr.jainanshul?source=rss-6da317cdf1ad------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*6EVGEjibm2g3G98p</url>
            <title>Stories by Mr Jainanshul on Medium</title>
            <link>https://medium.com/@mr.jainanshul?source=rss-6da317cdf1ad------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 12:25:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mr.jainanshul/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[⚔️ The Battle of Routing Protocols: When Networks Became a War Zone]]></title>
            <link>https://medium.com/@mr.jainanshul/%EF%B8%8F-the-battle-of-routing-protocols-when-networks-became-a-war-zone-ef0103d32931?source=rss-6da317cdf1ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef0103d32931</guid>
            <category><![CDATA[distributed-systems]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[bgp]]></category>
            <category><![CDATA[data-center]]></category>
            <category><![CDATA[cloud-networking]]></category>
            <dc:creator><![CDATA[Mr Jainanshul]]></dc:creator>
            <pubDate>Thu, 19 Mar 2026 04:42:18 GMT</pubDate>
            <atom:updated>2026-03-19T04:42:18.913Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/704/1*_DY41D7-82ST8NLkBNmZ-Q@2x.jpeg" /></figure><p>There was a time when networks were simple.</p><p>A few routers. Clear paths. Predictable traffic.</p><p>Back then, routing protocols were like skilled soldiers –</p><p>each one knew exactly where to go and what to do.</p><p>But today?</p><p>Networks have turned into a massive battlefield 🌍</p><p>Global, clouds, and data centers.</p><p>And not every soldier was ready for this war…</p><p>⸻</p><h3><strong>The Old Warriors</strong></h3><h4>🧭<strong> OSPF – The Tactical Commander</strong></h4><p>OSPF fights with precision.</p><p>It studies the battlefield, maps every path,</p><p>and chooses the shortest route to attack.</p><p>Perfect in controlled environments.</p><p>But when the battlefield became global…</p><p>its strategy became too heavy and slow.</p><p>⸻</p><h4>📐 <strong>IS-IS – The Master of Formation</strong></h4><p>IS-IS believes in structure.</p><p>Organized troops. Clear hierarchy. Strong discipline.</p><p>It dominates in well-planned wars.</p><p>But modern battles aren’t clean anymore…</p><p>they are chaotic, unpredictable, and constantly shifting.</p><p>⸻</p><h4>🪦 <strong>RIP – The Fallen Soldier</strong></h4><p>RIP fought bravely in the early days.</p><p>Simple tactics. Direct moves.</p><p>But in today’s high-speed, large-scale war…</p><p>it didn’t stand a chance.</p><p>⸻</p><h4>⚙️ <strong>EIGRP – The Skilled Fighter</strong></h4><p>EIGRP is fast and efficient.</p><p>A strong warrior in its own territory.</p><p>But this war is global…</p><p>and it couldn’t fight across every battlefield.</p><p>⸻</p><h3><strong>The War Changed</strong></h3><p>This is no longer about:</p><p>👉 Finding the shortest path</p><p>Now it’s about:</p><p>👉 Handling massive scale</p><p>👉 Adapting to constant change</p><p>👉 Following strategic policies</p><p>👉 Surviving continuous failures</p><p>⸻</p><h3><strong>The One That Won the War</strong></h3><h4>👑<strong> BGP – The Supreme Strategist</strong></h4><p>BGP doesn’t rush into battle.</p><p>It doesn’t try to find the quickest attack.</p><p>Instead…</p><p>👉 It controls the entire battlefield</p><p>⸻</p><h4><strong>Why BGP Wins</strong></h4><p>⚡ <strong>It Scales</strong></p><p>From small networks to the entire internet 🌍</p><p>⚡ <strong>It Adapts</strong></p><p>Cloud, data center, hybrid – every battlefield</p><p>⚡ <strong>It Controls Strategy</strong></p><p>It doesn’t just choose paths… it defines them</p><p>⚡ <strong>It Survives Chaos</strong></p><p>Built for a world where failures are constant</p><p>⸻</p><h3><strong>Real Battlefield</strong></h3><p>Modern giants like</p><p>Amazon Web Services,</p><p>Google Cloud Platform,</p><p>Microsoft Azure</p><p>run their massive infrastructures using BGP.</p><p>⸻</p><h3><strong>Final Thought</strong></h3><p>Other warriors fought to win battles.</p><p>BGP designed the war.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef0103d32931" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is Your CCIE Still Relevant? ]]></title>
            <link>https://medium.com/@mr.jainanshul/is-your-ccie-still-relevant-4c8c7836253b?source=rss-6da317cdf1ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c8c7836253b</guid>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[ccie-training]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-networking]]></category>
            <category><![CDATA[networking]]></category>
            <dc:creator><![CDATA[Mr Jainanshul]]></dc:creator>
            <pubDate>Fri, 06 Mar 2026 11:35:46 GMT</pubDate>
            <atom:updated>2026-03-06T11:37:23.305Z</atom:updated>
            <content:encoded><![CDATA[<p>(Hint: Yes… but maybe not in the way we once thought.🤔)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YpDJBwM3cBD2OtgHXUmoiQ.jpeg" /></figure><p>About 18 years ago, when I started my networking career, I had one big dream.</p><p><strong>CCIE. </strong>👑</p><p>Back then, the Cisco Systems CCIE wasn’t just another certification you put on your resume.</p><p>It was the crown.</p><p>Every network engineer I knew talked about it.<br>Studied for it.<br>Dreamed about it.</p><p>If someone had CCIE, you automatically respected them.</p><p>It meant they had spent years mastering routing, troubleshooting impossible problems, and understanding networks at a level most people never reached.</p><p>In many ways, it separated engineers from operators.</p><p>And honestly… it still carries that respect.</p><p>But the industry is shifting: value is no longer just in mastering devices, it’s in understanding entire systems.</p><p>⸻</p><h3>The Wake-Up Call</h3><p>Over the years, I’ve met incredibly talented engineers — many holding the Cisco Certified Internetwork Expert. Engineers who could read a BGP table instantly, design complex MPLS networks from memory, and troubleshoot in minutes what would take others weeks.</p><p>I used to look up to them — until the conversation began to shift.</p><p>Someone would bring up things like:</p><ul><li><strong><em>Cloud networking</em></strong></li><li><strong><em>Infrastructure as Code</em></strong></li><li><strong><em>Automation</em></strong></li><li><strong><em>APIs</em></strong></li><li><strong><em>CI/CD pipelines</em></strong></li></ul><p>And BOOM! suddenly the room felt different. The same engineers confident about BGP and MPLS would go quiet. Some looked skeptical. A few would even say: “That’s not real networking.”</p><p>That line stayed with me.</p><p>Because the truth is — the biggest networks on the planet today run inside</p><ul><li><strong><em>Amazon Web Services,</em></strong></li><li><strong><em>Microsoft Azure, and</em></strong></li><li><strong><em>Google Cloud</em></strong></li></ul><p>Built with code and APIs, not console cables.</p><p>That’s when it hit me: maybe the definition of real networking has changed — and many of us haven’t caught up yet.</p><p>⸻</p><h3>The Brutal Reality</h3><p>Sometimes I ask myself a simple question.<br>If networking was invented today… would it start with a CLI or an API?</p><p>The truth is, the AI era won’t wait for manual configs and midnight change windows.</p><p>And here’s the uncomfortable part: a CCIE who can’t design cloud and automated networks may no longer be at the top of the pyramid.</p><p>⸻</p><h3>Before anyone gets defensive, let me say this clearly</h3><p>The Cisco Systems CCIE is not irrelevant.</p><p>Understanding control planes, convergence, and high-availability design is powerful — many cloud engineers still struggle with these fundamentals.</p><p>But something has shifted: knowing BGP is impressive, automating BGP at scale is elite.</p><p>When I started my career almost two decades ago, networking meant mastering the CLI.<br>Your expertise was measured by how fast you could configure and troubleshoot devices.</p><blockquote>Today Networking has moved beyond just CLI and devices.<br>From someone working only inside telecom networks……to someone who can design infrastructure for banks, startups, SaaS companies, and global platforms, using cloud provider like AWS,Azure or GCP.</blockquote><p>The industry isn’t replacing network engineers; it’s replacing those who refuse to evolve.</p><p>⸻</p><h3>So here’s the real question.</h3><ul><li>Is your Cisco Systems CCIE the peak of your career… or just the foundation?</li><li>If the CLI disappeared tomorrow, would your expertise still dominate the industry?</li><li>Are cloud and automation the next evolution of networking… or just hype?</li></ul><p>Curious what fellow CCIEs and senior engineers think.Let’s hear it. 👇</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c8c7836253b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cloud Networking Under the Hood — Deep Dive from VM to Fabric.]]></title>
            <link>https://medium.com/@mr.jainanshul/cloud-networking-under-the-hood-deep-dive-from-vm-to-fabric-2b80666ea431?source=rss-6da317cdf1ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b80666ea431</guid>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[cloud-networking]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[evpn-vxlan]]></category>
            <category><![CDATA[data-center]]></category>
            <dc:creator><![CDATA[Mr Jainanshul]]></dc:creator>
            <pubDate>Mon, 02 Mar 2026 14:17:39 GMT</pubDate>
            <atom:updated>2026-03-06T11:32:32.877Z</atom:updated>
            <content:encoded><![CDATA[<p>From the outside, cloud networking feels effortless.<br>Click. “Create a VPC.”<br>“Launch a VM.”</p><p>And it just works.</p><p>As a network engineer, I used to stare at that screen and wonder — how?<br>• Where are the VLANs?<br>• Where are the VRFs?<br>• Who is programming the routes?</p><p>It all looks simple. But I knew it couldn’t be.<br>Behind that smooth click-click experience lives one of the most sophisticated distributed networking systems ever built. So I decided to go under the hood.</p><p>______________</p><h3><strong>In This Deep Dive</strong></h3><p>I’ll break down:<br>• What really happens when an EC2 launches<br>• How the cloud keeps customers completely isolated<br>• Why a VPC is basically a VRF in disguise<br>• How cloud networks scale across thousands of servers<br>• How the physical and virtual worlds work together<br>This is for network engineers like me — curious about what’s really happening behind the curtain.</p><h3>Before Starting : The Problem That Gave Birth to the Cloud</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TuaT0wlM8JcdJKmZsvpJAg.jpeg" /></figure><p>Before the cloud, innovation crawled through tickets and silos —getting a simple server felt like waiting in line at five different offices just to turn on a light……….a simple VM trapped behind VLANs, VRFs, firewalls, and weeks of manual gatekeeping.</p><p>The cloud changed that — now you press a button, and it’s there. Instantly.</p><h3>What Happens Behind the Click ? : The Underlay and Overlay That Make the Cloud Possible</h3><p>When I finally understood this, everything clicked.</p><p>Cloud networking separates the physical network from the virtual network.</p><h4><strong>Underlay — The Physical Network</strong></h4><p>This is the real fabric: switches, routers, cables.<br>Its job is simple, Just Move packets from point A to point B.<br>It doesn’t know about:<br> • Tenants<br> • VPCs<br> • Subnets<br>It only asks: Where did this packet come from?, Where does it need to go? and Nothing more.</p><h4><strong>Overlay — The Virtual Network</strong></h4><p>This is where the intelligence lives.<br>The overlay:<br>• Creates private networks for each customer<br>• Keeps tenants isolated<br>• Builds virtual subnets and routing<br>• Scales massively without changing physical hardware<br>Technologies like VXLAN and EVPN make this possible.<br><br>And together, they are the real foundation of cloud networking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/919/1*smMv3fwnjvFa3BN1y7axew.png" /></figure><p><em>Let’s go under the hood.</em></p><h3><strong>What Happen when you create New VPC ? The Truth No One Tells You: A VPC Is Just a VRF</strong></h3><p>In the cloud, the terminology sounds simple:<br>VPC……Subnet……ENI.<br><em>Clean. Friendly. Abstract.</em></p><p>But if you come from a traditional networking background, something should feel familiar. Because behind the curtain:<br>• A VPC is a VRF.<br>• A Subnet is a Layer-2 VNI.<br>• An ENI is a virtual NIC.</p><p>Cloud providers don’t say “VRF.” But that’s exactly what they built.<br>Every VPC has:<br>• Its own routing table<br>• Its own overlay identifier (VNI ID)<br>• Its own control-plane advertisements<br><br><em>It’s VRF-based isolation — engineered at massive scale.<br>It’s not magic.</em></p><h3><strong>What Really Happens When You Click “Launch VM” ?</strong></h3><p>Let’s say you click:<br>“Launch VM in VPC-RED.”<br>To you, it’s one action, in cloud it’s an orchestration event.</p><h4>Step 1: Validation</h4><p>The control plane checks:<br>• Who is this tenant?<br>• Which VPC?<br>• Which subnet?<br>• What security policies apply?<br>Behind the scenes, it maps something like:<br><em>Tenant RED → VRF 10 → L3 VNI 10010<br>Subnet-A → L2 VNI 10101</em><br>If anything doesn’t align, the VM doesn’t launch.</p><h4>Step 2: The Scheduler Chooses a Host</h4><p>Maybe Host17 is selected.<br>But the VM doesn’t boot immediately.<br>First, the network must be prepared.<br>Because in the cloud, networking is not an afterthought.<br>It is foundational.</p><h4>Step 3: The Host Programs the Dataplane</h4><p>Now the selected host begins its work.<br>It:<br>• Creates or validates the VRF<br>• Builds the VXLAN interface<br>• Attaches it to the correct VNI<br>• Programs routing entries<br>• Advertises the VM’s MAC and IP into the control plane<br>Only when all of this is complete…<br>The VM powers on.<br><br>Everything is automated, distributed, and pre-engineered.</p><h3>The Obvious Question</h3><p>A VM is up on Host17.<br>How does a VM on Host3 (same customer) know about it?<br>So what actually happens?</p><h3>Behind the illusion isn’t magic — it’s the Control Plane.</h3><h4>Step 1: What Happens When a VM Boots</h4><p>The moment a VM comes alive and gets:<br>• MAC<br>• IP<br>• VNI<br>The host advertises it into the EVPN control plane using a Type 2 route:<br>“MAC 00:11:22:33<br>IP 10.1.1.10<br>VNI 10101<br>Reach via VTEP 10.0.0.17”</p><p>This update is shared with each all EVPN participating hosts.</p><h4>Step 2: Remote Hosts Learn Instantly</h4><p>Host3 receives this update and immediately programs:<br>“If traffic for 10.1.1.10 arrives, send it to 10.0.0.17 using VXLAN. Using VNI VTEP and other announced details”</p><p><strong><em>No waiting.No ARP discovery.No flooding.</em></strong><br>The mapping is already installed before traffic starts.</p><p><strong><em>Now the obvious question Why There’s No Flooding</em></strong></p><p><em>With </em><strong><em>Ethernet VPN (EVPN)</em></strong><em>, the network already knows; every VM is announced, every path pre-written, every answer waiting before the question is even asked.</em></p><h3>Behind the curtain, the Data Plane performs the real trick… packet by packet.</h3><p>We saw how the control plane learns. Now let’s see how the packet moves.<br>Scenario:<br>• VM1 on Host1<br>• VM2 on Host17<br>• Both in VPC-RED (VNI 10101)<br>Control plane has already shared their MAC/IP mappings.<br>Now traffic starts.</p><h4>Step 1: VM1 Sends Traffic</h4><p>VM1 sends a normal Ethernet frame:<br>• Src IP: 10.1.1.5<br>• Dst IP: 10.1.1.10<br>To the VM, this looks like a regular local network.<br>It has no idea about VXLAN.</p><h4>Step 2: Host1 Uses EVPN Knowledge</h4><p>Host1 checks its EVPN table.<br>It already knows:<br>• 10.1.1.10 lives at VTEP 10.0.0.17<br>• Inside VNI 10101<br>No ARP.<br>No flooding.<br>The answer is already there.</p><h4>Step 3: VXLAN Encapsulation</h4><p>Host1 wraps the original packet:<br>Outer Header:<br>• Src IP: 10.0.0.1<br>• Dst IP: 10.0.0.17<br>VXLAN:<br>• VNI 10101<br>Inner Packet:<br>• Original VM frame<br>Now it becomes a simple IP packet carrying tenant traffic inside.</p><h4>Step 4 : Underlay Routes It</h4><p>The fabric sees only:<br>Source IP → 10.0.0.1<br>Destination IP → 10.0.0.17<br>It routes using ECMP.<br>It does not know:<br>• VPC<br>• VRF<br>• Tenant<br>• Subnet<br>It just forwards IP.</p><h4>Step 5 :Host17 Decapsulates</h4><p>Host17 removes:<br>• Outer IP header<br>• VXLAN header<br>Reads VNI 10101 → maps to VPC-RED.<br>Delivers packet to VM2.</p><p><strong><em>Cloud networking feels almost magical from the outside.</em></strong></p><p>No cables, No switch configurations, No VLAN spreadsheets, No late-night change windows.</p><p><em>Just click, click… and go.</em><br>But behind that smooth, effortless experience is one of the most advanced distributed networking systems ever built.</p><p>The moment you “Click,” routing tables are updated, virtual networks are created, tunnels are programmed, isolation boundaries are enforced, and traffic paths are recalculated across an entire physical fabric. Thousands of decisions happen in milliseconds.</p><p><em>Cloud networking doesn’t “just work.”<br>It works because a very smart and powerful system behind the scenes hides all the complicated parts from you.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b80666ea431" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>