Convert CCNP TSHOOT Troubleshooting Lab 1 from GNS3 to Containerlab

[Copilot]

Migrated the GNS3 CCNP TSHOOT Troubleshooting Lab 1 to Containerlab format, replacing Frame Relay with point-to-point Ethernet while preserving all routing protocols and intentional misconfigurations.

Topology

• 13 devices: 5 routers (R1-R4, ISP), 4 switches (DSW1/2, ASW1/2), 4 endpoints (Client1/2, FTPServer, WebServer)
• 20 links: Core mesh (OSPF), distribution layer (EIGRP), access layer (port-channels), external BGP

Configuration Changes

• Frame Relay subinterfaces → point-to-point Ethernet links (R1-R2-R3-R4 core)
• Serial0/0.12 → Ethernet0/0, FastEthernet1/0 → Ethernet0/1, etc.
• Added no shutdown to all interfaces (Containerlab requirement)
• Removed Frame Relay encapsulation and DLCI configs

Preserved Technologies

• OSPF multi-area with NSSA (area 0, 12, 34)
• EIGRP redistribution between R4 and DSW1/DSW2
• eBGP (AS 65001 ↔ AS 65002)
• HSRP, VLANs (10, 20, 200), IPv6 (OSPFv3, RIPng, tunnels)

Intentional Misconfigurations

Preserved original troubleshooting scenarios:

• R4 DHCP: network 10.2.10.0 with default-router 10.2.1.254 (Ticket Add eBGP and iBGP two-router containerlab labs #1)
• HSRP: DSW1 uses 10.2.1.200, DSW2 uses 10.2.1.254 (Ticket Add eBGP and iBGP two-router containerlab labs #1)
• EIGRP: auto-summary on DSW1, no auto-summary on DSW2 (Ticket Add script to compare CML and containerlab topologies #2)

Structure

containerlab/labs/troubleshooting/cisco/ccnp-tshoot-troubleshooting-1/
├── ccnp-tshoot-troubleshooting-1.clab.yml
├── README.md
└── clab-ccnp-tshoot-troubleshooting-1/
    └── {R1,R2,R3,R4,ISP,DSW1,DSW2,ASW1,ASW2,Client1,Client2,FTPServer,WebServer}/
        └── startup-config.cfg.partial

Original prompt

The "gns3vault-archive" lab contains a troubleshooting folder with a CCNP troubleshooting lab.

This folder contains a gns3 topology file and a folder with startup configs.

I want you to recreate this as a containerlab topology.

There is an existing Containerlab topology for ospf-network-type-p2p already in this repo. use that as a guideline for the topology file and folders.

Make sure to use correct interface names and numbers because those are different in Containerlab than those in gns3. also, routers in Containerlab require a "no shutdown" on the interfaces.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.