Arista CloudVision Integration

Overview

The Arista CloudVision integration discovers EOS devices and their layer-3 configuration from Arista CloudVision and ingests them into NetBox via the Diode SDK. It connects to CloudVision Portal (CVP) on-premises or CloudVision as a Service (CVaaS) over gRPC, reads the managed device inventory, device tag assignments, and each device's EOS running configuration, and maps them to NetBox objects. Discovered data is staged as deviations in NetBox Assurance, where you review and apply changes before they are written to NetBox. This gives you visibility and control over what enters your source of truth, without manual data entry.

Run the integration on a schedule to continuously surface operational drift. When devices, software versions, interfaces, addressing, or streaming status change in CloudVision, Assurance highlights exactly what has diverged from NetBox so you can act on it deliberately rather than finding discrepancies later.

What Gets Synchronized

From the CloudVision inventory and tag APIs:

• Devices - devices managed by CloudVision, with hardware model, EOS software version, serial number, and streaming status
• Device Types - created from the hardware model name reported by CloudVision, with a clearly labeled placeholder when no model is reported
• Platforms - created per EOS software version (EOS {version})
• Sites - resolved from the topology_datacenter CloudVision system tag, with a configurable fallback
• Device Roles - resolved from the topology_type CloudVision system tag, with a fallback role
• MAC Addresses - the device system MAC address, assigned to the management interface

From each device's EOS running configuration:

• Interfaces - physical ports, port-channels, SVIs, loopbacks, subinterfaces, and management ports, with type, speed, MTU, description, enabled state, switchport mode, VLANs, and VRF
• VLANs and VLAN Groups - VLANs from vlan stanzas, grouped and scoped per site
• VRFs - VRFs from vrf instance stanzas
• Prefixes - the networks containing interface addresses, scoped to their site
• IP Addresses - IPv4 and IPv6 interface addresses, including ip address virtual shared gateways as anycast addresses. Each device's management address is set as its primary IP

Key Features

• Device inventory discovery - reads all devices managed by CloudVision from the arista.inventory.v1 Resource API
• Layer-3 discovery from running configuration - parses interfaces, VLANs, VRFs, prefixes, and IP addresses from each device's EOS running configuration, retrieved through the CloudVision compliance API
• Multi-site address separation - keeps address ranges reused across sites, such as loopback and management ranges, as distinct NetBox records
• Resilient configuration retrieval - a device whose configuration cannot be read is skipped without failing the run, and device-level data is always synced
• Tag-driven site and role resolution - resolves each device's NetBox site from the topology_datacenter system tag and its role from the topology_type system tag, with fallbacks when tags are absent
• Dynamic device types and platforms - creates NetBox device types from hardware model names and platforms from EOS software versions as devices are discovered. Devices with no reported model, such as access points, get a placeholder device type instead of being labeled as Arista switches
• Streaming status tracking - records each device's CloudVision streaming status (active, inactive, or unknown) in a custom field
• Token or username/password authentication - authenticates with a CloudVision service account token or with a username and password
• CVP and CVaaS support - connects to CloudVision Portal on-premises or CloudVision as a Service over the gRPC Resource API
• Scope filtering - optionally restrict ingestion to specific sites or to devices carrying specific CloudVision tags
• Bootstrap mode - creates tags, custom fields, the manufacturer, and device roles in NetBox before the first full sync
• Operational drift detection - run on a schedule to surface CloudVision inventory changes as deviations in NetBox Assurance

Integration Architecture

The Arista CloudVision integration is built on the NetBox Labs controller integrations framework:

• Standardized integration pattern - consistent approach across all controller integrations
• NetBox Assurance integration - uses NetBox Assurance for safe data ingestion and deviation management
• Agent based - runs as part of the NetBox Discovery agent ecosystem using the Orb Agent Pro image
• One-way sync - data flows from CloudVision to NetBox only; no changes are written back to CloudVision

Compatibility

Supported NetBox Versions

• NetBox Cloud and NetBox Enterprise with NetBox Assurance

Supported Arista CloudVision Versions

• CloudVision Portal (CVP) on-premises, and CloudVision as a Service (CVaaS), reachable over the CloudVision gRPC Resource API (arista.inventory.v1 and arista.tag.v2)
• Layer-3 discovery also requires the CloudVision compliance API (compliancecheck). On a CloudVision version without it, or with credentials that cannot access it, the integration syncs device-level data only

Known Limitations

Some EOS configuration is not yet parsed, including VLAN range stanzas (vlan 10-20) and VXLAN VNI mappings. Access points and third-party devices receive a placeholder device type because CloudVision does not report their model or vendor. See Known Limitations for the full list.