Lab Overview

This learning lab introduces the Unified Branch model and demonstrates how to deploy and manage it using Branch as Code. The lab is designed to help users understand the key concepts, configurations, and operational aspects of Branch as Code.

This document is a comprehensive guide to understanding Network as Code (NaC) which utilizes Infrastructure as Code (IaC) principles to manage configuration for Cisco Meraki Dashboard. The focus of this guide is specific to the Unified Branch as Code. The guide is structured to build a solid understanding of the concepts and toolchain required to deploy and operate Unified Branch environments, integrating Branch as Code automation with a cloud-managed architecture.

There are several sections in this guide; each section focusing on different aspects. It includes practical examples, best practices, and detailed explanations to help you understand the concepts.

If you have no environment of your own but still would like to try, we can provide a limited lab available in dCloud. If you need the lab shared with you, please reach out in our Network as Code Public Webex Space.

This guide contains elements to assist you in making changes. The primary interface that is used in this guide is a web-based version of Visual Studio Code (known as Code Server). This takes the role of a development environment (IDE - Integrated Development Environment) that you will use to modify the data model for Network as Code.

You will find in the guide both reference material for learning and then direct Steps for you to follow. These steps can also include code snippets or CLI commands for you to copy and paste into your Code Server terminal. In the guide you will see elements as:

cd ~/network-as-code/branch-as-code

That you can copy and paste easily via the button that appears when you hover over the code snippet. There are also screenshots of specific elements, including Meraki Dashboard to guide you on specific tasks.

Some of these commands that you copy seem redundant, but are designed such that the command always works even if you have changed directories, or explored different parts of the directory structure.

The guide is intended to be directional. Each section of the guide will provide you builds towards the next section and are all connected. The best approach is to follow the guide in order.

To complete this guide you will need access to:

• IDE / Code Server: to modify the Network as Code data model.
• Installed tools: Git, Terraform (>=1.9.0), Python (3.12).
• SCM platform: GitLab, GitHub, or similar.
• Meraki API Key (full write access): no hardware required. Generate an API key using this guide.
• Optional: CI/CD platform such as GitLab Pipelines or Jenkins

This table of contents provides a view of the different sections of the guide and the respective topics.