---
sourceDocument: Australia Telecommunications Service Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/telecom-service-ops

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Telecommunications Service Operations Management

ft:clusterId :

    - tsom

bundleId :

    - tsom

workflow :

    - Customer and Industry


---

# Configure Arista VeloCloud SGC

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

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

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, to configure, monitor, and manage 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 (via a MID Server) to ensure 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://servicenow-prod.fluidtopics.net/sY8TYi0Q~Zy5tHvebkDdUA "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.").  
Nota:  
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 | sn_tsom_vcloud_connector |
[ ]

{#configure-arista-velocloud-service-graph-connector__table_s1h_kby_vfc}  
Nota:  
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 (SGC-Arista VeloCloud Bulk Discovery, SGC-Arista VeloCloud Filtering Discovery). Enable parallel loading if needed. For more information on parallel loading. |
| 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. For more information, see. |
[ ]

{#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://servicenow-prod.fluidtopics.net/ojGCX2iX1nJ_9cJVsKWqsg "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.").