Arista CloudVision Integration

Overview

The Arista CloudVision integration discovers EOS device inventory from Arista CloudVision and ingests it into NetBox via the Diode SDK. It connects to CloudVision Portal (CVP) on-premises or CloudVision as a Service (CVaaS) using the CloudVision gRPC Resource API, reads the managed device inventory and device tag assignments, 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, models, software versions, 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

• Devices - EOS switches 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
• 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
• Management Interfaces - one management interface per device (Management0 or Management1, depending on the hardware model)
• MAC Addresses - the device system MAC address, assigned to the management interface

Key Features

• Device inventory discovery - reads all EOS devices managed by CloudVision from the arista.inventory.v1 Resource API
• 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
• 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)