Skip to main content

Quick Start

This guide walks through the minimum steps to connect gns3util to a GNS3v3 server, validate connectivity, and discover existing resources. Before continuing, complete the installation steps in getting-started/installation.md so the binary and prerequisites are ready.

Step 1 · Authenticate

If you plan to script commands with jq or other tooling, remember to add --no-color --raw so the output is easy to parse. See the cli-reference/commands.md page for all global flags.

Step 2 · Discover Projects and Topology

Spend a minute exploring what already exists before you modify anything.

Step 3 · Review Templates and Images

Templates define reusable topologies and appliances. Confirm what is available and gather metadata.
If the server is empty or you need teaching templates, jump to features/educational-workflows.md#template-management-workflow for creation workflows.

Step 4 · Check System Health and Connected Users

Confirm that the server is healthy before making changes.
Once you understand the environment, you can proceed to provisioning tasks or automation.

Step 5 · Explore Optional Workflows

Depending on your role, choose the next area to explore:
  • Education-focused labs: See features/educational-workflows.md for class, exercise, and student management automation.
  • Remote operations: features/remote-operations.md covers HTTPS setup, firewalls, and maintenance commands.
  • Sharing artifacts: Exchange projects and configs with peers using the workflow in features/sharing-and-collaboration.md.
  • Automation scripts: Review reusable shell scripts in scripts/overview.md and the full catalog in scripts/examples.md.

Troubleshooting & Help

  • Use --help on any command (for example gns3util project --help) to view available subcommands and flags.
  • Consult the full CLI reference at cli-reference/commands.md for a tree of every command group.
  • When piping output to other tools, run commands with --no-color --raw to avoid ANSI escape sequences.
  • If you encounter authentication or connectivity issues, re-run Step 1 and confirm the server URL, credentials, and TLS requirements.