Troubleshoot Containerlab

Runs read-only diagnostics on the containerlab hypervisor through AAP using the Containerlab SSH credential. Use this when day-2 jobs such as Backup or Report fail and you cannot export the hypervisor private key from AAP.

Prerequisites

• Containerlab hypervisor provisioned via NETWORK ǀ Deploy Containerlab Stack
• AWS credential configured for EC2 discovery
• Containerlab SSH credential populated during hypervisor provisioning

Survey prompts

Prompt	Variable	Type	Required
AWS Region	clab_aws_region	multiplechoice	Yes

Options: us-east-2 (default), us-west-2.

Job templates

Template	Playbook	Description
NETWORK ǀ Containerlab ǀ Troubleshoot	network/troubleshoot_containerlab.yml	Discovers the hypervisor, probes device ports, and collects containerlab and podman status

The job discovers the connected product_demos topology and recognizes previous split-lab records during migration.

What it checks

1. Hypervisor discovery — Finds the running EC2 instance tagged deployment=containerlab
2. External port probes — Tests TCP connectivity to hypervisor SSH and each deployed device management port from the execution node
3. Hypervisor health — Uptime, memory, and disk usage on the image volume
4. containerlab status — containerlab version and containerlab inspect
5. Podman containers — Lists containers for both ec2-user and root runtimes
6. Local device SSH probes — Checks whether all deployed device management services respond on the hypervisor
7. Recent container logs — Last 20 log lines for containers in the connected topology (and any remaining legacy lab during migration)

See other Network demos

Browse all Network demos →