---
sourceDocument: Australia Telecom Service Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/telecom-service-ops

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Telecom Service Operations Management

ft:clusterId :

    - tsom

bundleId :

    - tsom

workflow :

    - Customer and Industry


---

# Configure Arista VeloCloud SGC

# Configure Arista VeloCloud
Service Graph Connector {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Configure Arista VeloCloud Service Graph Connector

The Arista VeloCloud Service Graph Connector (SGC) enables ServiceNow customers to discover and import both physical and logical inventory data from their Arista VeloCloud environment into the Configuration Management Database (CMDB).
This integration uses the VeloCloud Orchestrator (VCO), Arista's centralized SD-WAN management platform, accessible as a self-hosted or SaaS deployment.
The connector accesses VCO's REST APIs via a MID Server to ensure the CMDB maintains accurate, current telecom inventory aligned with the TM Forum data model.
Show full answer Show less  

## Authentication

API authentication requires generating an API token from a VCO user account. Two token types are supported:

* **User token:** inherits the permissions of the creating user.
* **Organization token:** scoped to a single organization.

The discovery service uses the access token during bulk or targeted discovery operations to retrieve network equipment, interfaces, and services from VCO.

## Prerequisites and Requirements

* A valid Telecommunications Service Operations Management subscription is necessary to use this connector.
* Required plugins include Telecom Service Operations Core (sntsomcore) and Service Graph Connector for Velocloud Telco SD-WAN (sntsomvcloudconnector).
* An operational Arista VeloCloud instance with REST API access.
* A MID Server configured for secure connectivity to the Arista VeloCloud instance.

## Configuration and Management

Configuration is accessible via the Arista VeloCloud navigation pane and includes the following key sections:

* **Setup:** Configure the MID Server, define connections to Arista VeloCloud instances, and schedule import jobs.
* **Data Sources:** Manage predefined bulk and filtered discovery data sources, with optional parallel loading.
* **Import Schedules:** Schedule or manually run import jobs per connection alias.
* **Connections \& Credential Aliases:** Define aliases to store connection metadata and credentials securely.
* **Connections:** Specify connection details such as URL, MID Server, credentials, and alias references.
* **Credentials:** Create credentials using Basic Authentication for API access.
* **Filters:** Set filtering parameters (e.g., device IP or name) for targeted discovery.
* **Properties:** Adjust connector-specific system behavior properties.

## Guided Setup

ServiceNow provides a guided setup workflow to streamline and simplify the configuration process. This structured approach helps ensure a quick and correct integration of the Arista VeloCloud environment with the CMDB, including scheduling import jobs and managing connection settings efficiently.  
Configure the Arista VeloCloud
Service Graph Connector (SGC) to discover and import physical and logical inventory data from your Arista VeloCloud environment into the Configuration Management Database (CMDB).

Arista VeloCloud relies on VeloCloud Orchestrator (VCO) as its centralized management platform, available as either a self-hosted or SaaS deployment. VCO configures, monitors, and manages SD-WAN inventory across the network.

## Authentication {#configure-arista-velocloud-service-graph-connector__section_cwx_m3d_phc}

VeloCloud Orchestrator supports two types of user roles: MSP admins and organization admins. To authenticate API requests, users must generate an API token from their VCO account.  
There are two types of API tokens:

* User token: Inherits the same access permissions as the user who created it.
* Organization token: Provides access scoped to a single organization.

{#configure-arista-velocloud-service-graph-connector__ul_nnf_tsx_h3c}You must authenticate before initiating discovery. During the authentication process, the discovery service receives an access token, which it then uses for bulk or specific discovery operations. The integration uses VeloCloud REST APIs to discover managed elements such as network equipment, interfaces, and services.
This integration uses REST APIs (through a MID Server) so that the CMDB reflects accurate, up-to-date telecom inventory aligned with the TM Forum-based data model. For a list of API references, see [Arista VeloCloud Service Graph Connector API Endpoints](https://www.servicenow.com/docs/fWu~myWqulhsyK6ynMZ1wQ "The Service Graph Connector for Arista VeloCloud integrates VeloCloud Orchestrator API data into ServiceNow AI Platform Configuration Management Database (CMDB). This document details the API endpoints used and how data flows through the system.").  
Note:  
A valid Telecommunications Service Operations Management subscription is required to use this connector.

## Required plugins {#configure-arista-velocloud-service-graph-connector__section_bwx_kby_vfc}

{#configure-arista-velocloud-service-graph-connector__table_s1h_kby_vfc__entry__2}

| Plugin | Plugin ID |
|-|-|
| Telecom Service Operations Core | sn_tsom_core |
| Service Graph Connector for Velocloud Telco SD-WAN | sn_tsom_vcloud_connector |
[ ]

{#configure-arista-velocloud-service-graph-connector__table_s1h_kby_vfc}  
Note:  
External requirements:

* A running Arista VeloCloud instance with access to its REST API.
* A MID Server with secure connectivity to the Arista VeloCloud instance.
{#configure-arista-velocloud-service-graph-connector__ul_x2w_pby_vfc}

## Configuration tasks overview {#configure-arista-velocloud-service-graph-connector__section_xxb_vby_vfc}

The following sections are available under the Arista VeloCloud navigation pane. Use the following table for post-guided setup or to perform manual configurations.
{#configure-arista-velocloud-service-graph-connector__table_pyy_vby_vfc__entry__2}

| Section | Description |
|-|-|
| Setup | Configure MID Server, define Arista VeloCloud connections, and schedule imports. |
| Data Sources | Predefined data sources for bulk and filtered discovery (VeloCloud Full Discovery, VeloCloud Filtered Discovery). Enable parallel loading if needed. |
| Import Schedules | Manage scheduling for each Arista VeloCloud connection alias. Run jobs manually or at defined intervals. |
| Connections \& Credential Aliases | Define aliases for each Arista VeloCloud instance. Store connection metadata and credentials. |
| Connections | Define Arista VeloCloud instance details, such as URL, selected MID Server, credential reference, and connection alias reference. |
| Credentials | Create Arista VeloCloud credentials using Basic Auth. |
| Filters | Configure filtering parameters used in filtered discovery (for example, by device IP or name). |
| Properties | Modify system behavior using connector-specific properties. |
[ ]

{#configure-arista-velocloud-service-graph-connector__table_pyy_vby_vfc}

## Access the guided setup {#configure-arista-velocloud-service-graph-connector__section_uyj_rz1_wfc}

Use the guided setup to simplify the configuration process. This setup provides an organized sequence of steps to help you complete integration quickly and correctly. For more information, see
[Set up the Service Graph Connector for Arista VeloCloud schedule](https://www.servicenow.com/docs/myStarh7iYKjZ40Bnpn1pA "Set up and configure the Service Graph Connector for Arista VeloCloud SD-WAN. The process includes installation, optional demo data integration, connectivity configuration, and scheduling data collection for seamless Configuration Management Database (CMDB) integration.").

