Define which network the Service Engines will use to talk back to the Controller. Install Guide: TKG and AKO 1.3 (Tanzu with Avi on vSphere)

Once the VM is up, access the Controller via its management IP address in a web browser. 3. Initial Setup Wizard

Choose the "Cloud" type you will be managing (e.g., VMware vCenter, OpenStack, or No-Access Mode). 4. Configuring the Cloud Connector

Depending on your platform (vSphere, OpenStack, or Bare Metal), the installation begins with deploying the Controller image:

Configure at least one DNS and one NTP server to ensure proper synchronization between the Controller and the Service Engines.

You will need an OpenRouter API key and a small balance ($5) if you are integrating with specific agentic systems like Dan Raine’s AVI project. 2. Controller Installation

The first step in any Avi deployment is setting up the , which serves as the "brain" of the ecosystem, managing policies and the Service Engines (SEs) that handle data traffic. 1. System Prerequisites

This is the most critical part of the initial phase as it allows the Controller to communicate with your infrastructure: