The ztp.Json file on the Apstra ZTP server contains the configuration parameters for each device that is onboarded using ZTP. One of the parameters is the State, which can be one of the following values:init,ready,in_progress,done,error, ordisabled. The State indicates the current status of the device in the ZTP process. For example, if the State isready, it means that the device is ready to be onboarded by the Apstra ZTP server. If the State isdone, it means that the device has completed the ZTP process and is managed by the Apstra server. The State can be manually set or changed in the ztp.Json file to control the behavior of the device during ZTP. For more information, seeApstra ZTP Configuration File.Reference:

Apstra ZTP Configuration File

Apstra ZTP Introduction

Configure Apstra ZTP

The Links table in the Staged tab shows the physical connections between the devices in the fabric. It provides information such as the source and destination device names, hostnames, serial numbers, roles, interfaces, and link status. The Links table can be used to assist the team that is installing and cabling the devices by verifying that the devices are connected correctly and that the links are operational. The Links table can also be used to troubleshoot any connectivity issues that may arise during the installation process. For more information, seeLinks (Staged).Reference:

Links (Staged)

Topology (Staged)

Staged

A configlet is a small piece of configuration that can be applied to a device or a group of devices to make persistent changes that are not overwritten by Apstra. Configlets can be used to install manual changes that are not part of the Apstra rendered configuration, such as custom commands, scripts, or features.Configlets can be created, edited, and deleted from the Apstra GUI or CLI12.Reference:

Configlets Overview

Configlets User Guide

VMware anomaly detection is a feature of Apstra that provides visibility and validation of the virtual network settings and the physical network settings in a VMware vSphere environment. To enable this feature, Apstra requires a connection to a vCenter server that manages the ESX/ESXi hosts and the VMs connected to the Apstra-managed leaf switches. The vCenter server must be configured under External Systems in the Apstra web interface, and the vCenter integration must be staged and committed in the blueprint. This allows Apstra to collect information about VMs, ESX/ESXi hosts, port groups, and VDS, and to flag any inconsistencies or mismatches that might affect VM connectivity. The other options are incorrect because:

VMware anomaly detection is not on by default. It must be enabled by configuring a vCenter server under External Systems and adding a virtual infra to the blueprint.

VMware anomaly detection does not require a VMware hypervisor with exports enabled. It only requires LLDP transmit to be enabled on the VMware distributed virtual switch to associate host interfaces with leaf interfaces.

VMware anomaly detection does not require an Apstra server running on VMware. It can run on any supported platform, such as Linux, Windows, or Docker.Reference:

VMware vCenter/vSphere Virtual Infra

Anomalies (Service)

A Better Experience: VMware + Juniper Apstra

According to the Juniper documentation1, EVPN route Type-3 is used to advertise the IP address of the VTEP and the VNIs that it supports. This allows the VTEPs to discover each other and form VXLAN tunnels for the VNIs that they have in common. EVPN route Type-2 is used to advertise the MAC and IP addresses of the hosts connected to the VTEPs. This allows the VTEPs to learn the MAC-to-IP bindings and the MAC-to-VTEP mappings for the hosts in the same VNI. Therefore, these two types of VXLAN tunnels will be automatically created by the EVPN control plane when using Juniper Apstra with the ERB design blueprint and two virtual networks in a common routing zone.Reference:Example: Configure an EVPN-VXLAN Centrally-Routed Bridging Fabric