netplex. is coming soon - you're seeing an early preview, full public launch is on its way.
Knowledge Base/Images & the pipeline

Supported Dynamips and Cisco IOL images

Reference5 min readUpdated July 2026

Short version: if you're wondering whether your Dynamips or Cisco IOL image will actually work in netplex., this page has the answer for the specific file you're holding, not a general "should be fine." We booted every one of these, wired it into a real lab, and pinged across the link - see the write-up for how we ran the campaign, or jump straight to importing a Dynamips image / importing an IOL image if you already know what you need.

How we tested

1

Every image below was imported the normal way through the Library, dragged onto a canvas, powered on, and reached over an actual netplex. link - not just booted in isolation. A "working" result means a real ping got a reply across that link. When one didn't behave as expected we didn't just write it off: we checked the interface's own packet counters and tried a self-ping on the box itself, to work out whether the problem was ours or the image's.

Dynamips - 23 images, all working

2

Every Dynamips platform we had came up clean across every build we had for it - full CLI, routing, and a successful ping every time:

  • c1700-adventerprisek9-mz 124-25d
  • c1710-bk9no3r2sy-mz 124-23
  • c2600-[1]-adventerprisek9_ivs-mz 124-25b
  • c2600-[2]-advipservicesk9-mz 124-25b
  • c2600-[3]-adventerprisek9-mz 124-25d
  • c2600-adventerprisek9-mz 124-25d
  • c2600-advsecurityk9-mz 124-15.t14
  • c2691-[1]-adventerprisek9_ivs-mz 124-25d
  • c2691-[2]advsecurityk9-mz 124-25d
  • c3640-a3js-mz 124-25d
  • c3640-[2]-telco-mz 124-25d
  • c3660-[1]-jk9s2-mz 124-25d
  • c3660-[2]-a3js-mz 124-25d
  • c3660-[3]-is-mz 124-25d
  • c3660-a3jk9s-mz 124-15.T14
  • c3660-a3jk9s-mz 124-25d
  • c3725-[1]-adventerprisek9-mz 124-25d
  • c3725-[2]-advipservicesk9-mz 124-25d
  • c3725-[3]-advsecurityk9-mz 124-25d
  • c3725-adventerprisek9-mz 124-15.T14
  • c3745-adventerprisek9-mz 124-25d
  • c3745-[2]-advipservicesk9-mz 124-25d
  • c3745-[3]-advsecurityk9-mz 124-25d

Cisco IOL - full routers

3

These three run as complete routers, nothing to flag:

  • i86bi_linux-adventerprisek9-ms 154-1.T_AntiGNS3
  • i86bi_Linux-L3-AdvEnterpriseK9 M2_157_3_May_2018
  • L3-ADVENTERPRISEK9-M 15.4-2T

Cisco IOL - full switch and router

4

Both builds below do everything the router-only images do, plus real Layer 2 switching - confirmed with a plain interface Vlan1 and a ping across the switched segment:

  • L2-ADVENTERPRISEK9-M 15.2
  • L2-ADVENTERPRISEK9-M 15.2-IRON

Cisco IOL - routers only (switching doesn't reach the SVI)

5

These five boot and route just fine, but a standard switchport-to-SVI setup never forwards traffic. We didn't stop at "doesn't work" - the interface's packet counters showed frames arriving, and a self-ping proved the IP stack itself was healthy. What's missing is the internal hop from the switchport into interface Vlan1; it just never happens in this image family. netplex.'s OVS wiring and TAP interfaces checked out fine the whole way through, so this sits inside the image, not our fabric.

  • i86bi_Linux-L2-AdvEnterpriseK9-M 152_May_2018
  • i86bi_Linux-L2-Adventerprisek9-ms SSA.high_iron
  • i86bi_linux_l2-advipservicesk9-ms.high_iron 20170202
  • i86bi_linux_l2-ipbasek9-ms.high_iron_aug9 2017b
  • i86bi-linux-l2-ipbasek9 15.1c

Workaround: skip the switchport, configure the interface as routed instead:

interface Ethernet0/0
 no switchport
 ip address <address> <mask>

Do that and all five ping cleanly and work as routers, no other changes needed.

Not supported

6

C7200 - 7 images, excluded. Not a netplex. issue: Dynamips itself never implemented the NPE-G1/NPE-G2 hardware these images need, so there's no code path to run them on any platform.

  • c7200-adventerprisek9-mz 152-4.S2
  • c7200-adventerprisek9-mz 152-4.S6
  • c7200-[1]-a3jk9s-mz 124-25g
  • c7200-[2]-adventerprisek9-mz 152-4.M7
  • c7200-[3]-advipservicesk9-mz 152-4.S2
  • c7200-[10]-adventerprisek9-mz 151-4.M2
  • c7200-[11]-advsecurityk9-mz 150-1.M9

2 metadata-only registry entries, excluded. These are stub records with no real image file behind them (iol-xe-17-12-01 and ioll2-xe-17-12-01) - there was nothing to import, let alone test.

If your exact image isn't listed above, it's untested rather than unsupported - most Dynamips-supported platforms and IOL builds we haven't explicitly run should still work, this list just reflects what we've personally confirmed with a real ping. Found one that behaves differently from what's written here? Let us know and we'll add it to the next pass.

← PreviousDrop files straight into the server uploads folder