<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Digital-Twin · Network Doodles</title><link>https://networkdoodles.com/tags/digital-twin/</link><description>Network automation, from first playbook to agentic operations. Ansible, NetBox, MCP, Python and the occasional doodle.</description><language>en-us</language><managingEditor>David Henderson</managingEditor><lastBuildDate>Sat, 21 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://networkdoodles.com/tags/digital-twin/index.xml" rel="self" type="application/rss+xml"/><item><title>Emulate the Question, Not the Network: Digital Twins at Scale (AutoCon 6, Part 2)</title><link>https://networkdoodles.com/posts/digital-twin-scale-containerlab/</link><pubDate>Sat, 21 Nov 2026 00:00:00 +0000</pubDate><dc:creator>David Henderson</dc:creator><guid>https://networkdoodles.com/posts/digital-twin-scale-containerlab/</guid><category>digital-twin</category><category>containerlab</category><category>testing</category><category>network-automation</category><category>ai</category><description>Russ White's AutoCon 6 tutorial on big ContainerLab twins: one twin per question, staged IS-IS bring-up, real scale limits, and where LLMs belong.</description><content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<div class="details admonition abstract open">
        <div class="details-summary admonition-title "><i class="icon admonition-icon icon-abstract"></i>Short answer<i class="details-icon  admonition-icon admonition-icon-arrow-right"></i></div>
        <div class="details-content">
            <div class="admonition-content">Don&rsquo;t try to build a digital twin of your whole network. Build a twin of the question you&rsquo;re asking: break the
network into functional pieces, emulate only the piece the question touches, and strip the containerized NOS
down to what the test needs. Script the topology yourself and let LLMs write helper scripts, because a model
asked to generate a 200-router topology gives you a different one every time.</div>
        </div>
    </div>
<p>I&rsquo;ve built network digital twins a few different ways: graph models for path tracing, emulated labs for change
testing. The <a href="https://networkautomation.forum/autocon6">AutoCon 6</a> talk closest to my own experience was Russ
White&rsquo;s tutorial on bringing up very large ContainerLab topologies, and it opened with the right principle. Don&rsquo;t
build a twin of the network. Build a twin of the question you&rsquo;re trying to answer.</p>
<h2 id="why-build-one-twin-per-question-instead-of-one-big-twin">Why build one twin per question instead of one big twin?</h2>
<p>A single all-encompassing twin isn&rsquo;t realistic today. CPU is the hard limit. Russ described twinning as a
continuum from two routers to thousands, and the job is finding the point on it that answers what you&rsquo;re asking.
Break the network into functional and topological pieces and run one twin per piece.</p>
<p>If you&rsquo;re testing control plane behavior, use the containerized version of your NOS and strip it down to the
routing stack. If you&rsquo;re testing data plane, keep the full stack but run fewer nodes. You don&rsquo;t need all 1,000
paths through a fabric to prove a forwarding behavior.</p>
<p>His three highest-value use cases:</p>
<ol>
<li>Validating orchestration and management tooling</li>
<li>Version control and model diffing</li>
<li>End-to-end policy verification across nodes</li>
</ol>
<h2 id="how-do-you-bring-up-a-large-containerlab-topology-without-crashing-the-host">How do you bring up a large ContainerLab topology without crashing the host?</h2>
<ul>
<li><strong>Split config by stage.</strong> Link addressing goes in the boot config. Routing and overlay get applied after boot.
Keep IS-IS and BGP out of base templates.</li>
<li><strong>One template per router type.</strong> Use placeholder characters that never appear in real config, and let a
script stamp out per-pod directories. Three router types means three templates.</li>
<li><strong>Stagger protocol bring-up.</strong> He set a unique IS-IS password per device at boot to block adjacencies, then
stripped them interface by interface to control the convergence rate.</li>
<li><strong>Set the Docker restart policy to none.</strong> Otherwise a host reboot restarts 500 containers at once and takes
the box down with them.</li>
<li><strong>Prefer IS-IS for lab scale.</strong> It&rsquo;s interface-based and easier to script than OSPF or BGP.</li>
</ul>
<h2 id="how-far-does-a-containerlab-topology-scale">How far does a ContainerLab topology scale?</h2>
<table>
  <thead>
      <tr>
          <th>Topology</th>
          <th>Result on an 8 vCPU / 32 GB VM</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>2 pods, 128 routers</td>
          <td>Comfortable on 4 vCPUs, full bring-up with IS-IS in 10-15 minutes</td>
      </tr>
      <tr>
          <td>3 pods, 160 routers</td>
          <td>About 6 vCPUs</td>
      </tr>
      <tr>
          <td>4 pods, 192 routers</td>
          <td>Every vCPU consumed</td>
      </tr>
      <tr>
          <td>224 routers</td>
          <td>Failed to converge 20-30% of the time, even with timer tuning</td>
      </tr>
  </tbody>
</table>
<p>Physical cores outperformed cloud vCPUs by a wide margin, and the Linux kernel&rsquo;s bridge limit becomes a hard
ceiling once you split a topology across ContainerLab instances. One bright spot: an FRRouting pull request for
optimized IS-IS flooding cuts CPU about 40%, which could roughly double those numbers.</p>
<h2 id="my-take-where-do-llms-fit-in-building-a-twin">My take: where do LLMs fit in building a twin?</h2>
<p>The part I agree with most: Russ wrote the scripts by hand first, then used LLMs to build helper scripts, not the
topology itself. Ask a model to generate a 200-router topology and you&rsquo;ll get a different one every time. A twin
that isn&rsquo;t repeatable isn&rsquo;t a twin. It&rsquo;s the same principle I apply to agents in production: let the model help
build deterministic tooling, then run the tooling.</p>
<p>Most enterprises don&rsquo;t need 200 routers in ContainerLab. They need the 15 devices in the path of the change
they&rsquo;re about to make, generated from their source of truth on demand. That only works if the twin knows what
the change can break, which is the <a href="/posts/observability-business-impact/">blast radius argument from my observability post</a>.
And if you want a lab NOS with a familiar CLI for the small version of this, that&rsquo;s why I built
<a href="/posts/capeos-lab-network-os/">CapeOS</a>.</p>
<p>The scale work matters because it shows you where the ceiling is. Deciding which question the twin answers is
what makes it useful.</p>
<p>This is part 2 of my <a href="/series/autocon6/">AutoCon 6 series</a>.</p>
]]></content:encoded></item></channel></rss>