--- 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 --- # Telecom discovery via Arista VeloCloud SD-WAN # Telecom discovery via Arista VeloCloud SD-WAN {#ariaid-title1} Release version: Australia Updated June 24, 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 Telecom discovery via Arista VeloCloud SD-WAN The Service Graph Connector for Arista VeloCloud enables ServiceNow customers to automatically discover and import SD-WAN inventory data from the VeloCloud Orchestrator into the CMDB. This integration helps keep your CMDB current with the latest configuration item (CI) information from your SD-WAN environment, supporting efficient network management and visibility. Show full answer Show less ## Key Features * **Automated Discovery:** Scheduled scans import comprehensive CI data from VeloCloud Orchestrator into the CMDB. * **Graphical Network Representation:** Uses Integration Hub ETL to visually map VeloCloud SD-WAN networks, including device relationships and dependencies. * **Support for Two Account Topologies:** * **Partner (MSP) Mode:** For enterprise proxy accounts managing multiple customer enterprises. * **Operator Mode:** For direct operators managing their own enterprises without a partner proxy. * **Discovery Sequence:** Includes account/partner lookup, gateway pool retrieval, enterprise listing, and detailed edge device discovery, ensuring comprehensive data import. * **Consistent Inventory Model:** Both modes build the same CMDB entities such as organizations, network sites, edge devices, and network service instances with accurate relationship mapping. * **CMDB Integrations Dashboard:** Provides a centralized interface to monitor the status, results, and errors of all Service Graph Connector imports for streamlined integration management. ## Why This Matters This connector ensures your CMDB reflects the latest SD-WAN infrastructure details, which is critical for reliable network operations, impact analysis, and change management. By automating discovery and maintaining data accuracy, it reduces manual effort and enhances operational visibility. ## What to Expect * Regular, automated updates of your SD-WAN environment data in the CMDB according to configured import schedules. * Visualization of the SD-WAN network topology and dependencies within ServiceNow via Integration Hub ETL. * Support for both MSP and direct operator account types without requiring manual mode configuration. * Access to comprehensive monitoring and troubleshooting tools through the CMDB Integrations Dashboard. ## Next Steps * Configure the Arista VeloCloud Service Graph Connector with your VeloCloud Orchestrator credentials. * Schedule and run the Arista VeloCloud SD-WAN import to populate and update your CMDB. * Use the CMDB Integrations Dashboard to monitor import status and resolve any processing errors. The Service Graph Connector for Arista VeloCloud discovers SD-WAN inventory from VeloCloud Orchestrator and imports it into the CMDB. ## Key benefits {#telecom-discovery-via-arista-velocloud__section_bqr_q1x_vfc} * Automatically scans VeloCloud Orchestrator to import all configuration item (CI) data based on import schedules. * Keeps the CMDB up to date with the latest CI information. * Uses Integration Hub ETL to provide a graphical representation of VeloCloud SD-WAN networks, device relationships, and dependencies. {#telecom-discovery-via-arista-velocloud__ul_i2f_4bx_vfc} Note: For a general overview of Service Graph Connector technology, see [Getting started with Service Graph Connectors](https://www.servicenow.com/docs/access?context=cmdb-sgc-intro&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). ## Arista VeloCloud SD-WAN architecture {#telecom-discovery-via-arista-velocloud__section_xzb_t2w_1hc} The Arista VeloCloud SD-WAN architecture consists of three key components: * VeloCloud SD-WAN Edge: An enterprise-class appliance deployed at branch sites that provides secure, optimized connectivity to applications. The Edge aggregates multiple links and steers traffic using Dynamic Multipath Optimization (DMPO) and deep application recognition (DAR). * VeloCloud SD-WAN Gateway: A distributed network component that optimizes data paths between branches, data centers, and cloud services. Gateways provide scalability, redundancy, and on-demand flexibility. * VeloCloud Orchestrator: A cloud-hosted or on-premises central management platform for configuring, provisioning, and monitoring the SD-WAN environment. The Service Graph Connector communicates with VeloCloud Orchestrator to discover and import inventory data into the CMDB. {#telecom-discovery-via-arista-velocloud__ul_u52_pyd_33c} ## Discovery modes {#telecom-discovery-via-arista-velocloud__section_velocloud_discovery_modes} The Service Graph Connector for Arista VeloCloud supports two VeloCloud account topologies: * Partner (MSP) mode: Applies to an Enterprise Proxy (partner) account that owns and manages many customer enterprises. * Operator mode: Applies to a direct operator account that manages its own enterprises without a partner proxy. {#telecom-discovery-via-arista-velocloud__ul_velocloud_modes} You don't need to specify the mode or provide an organization identifier. When discovery runs, the connector checks whether the supplied credentials belong to a Partner (Enterprise Proxy) account. If they do, discovery proceeds in Partner (MSP) mode; if not, the connector uses Operator mode. The same scheduled data import works for both account types. Both modes follow the same discovery sequence: 1. Account and partner lookup: The connector determines whether the account is a partner proxy. 2. Gateway pools: The connector retrieves the gateway pool information available to the account. 3. Enterprise list: The connector retrieves the list of enterprises (organizations). In Partner (MSP) mode, the list includes edge information. In Operator mode, the list is retrieved without edge information. 4. Edge devices: For each enterprise, the connector retrieves its edge devices, including high-availability status, configuration, licenses, links, and site details. Any edge device without a name is skipped during import in both modes. {#telecom-discovery-via-arista-velocloud__ol_velocloud_discovery_sequence} The main differences between the two modes are described in the following table. {#telecom-discovery-via-arista-velocloud__table_velocloud_discovery_modes__entry__3} | Aspect | Partner (MSP) mode | Operator mode | |-|-|-| | Account type | Enterprise Proxy (partner) | Direct operator | | Enterprise list source | `getEnterpriseProxyEnterprises` | `getNetworkEnterprises` | | Edge data in the enterprise list | Included | Retrieved separately for each enterprise | | Enterprises with no edge devices | Skipped | Retained | | Partner association | Each enterprise is linked to its parent partner | No partner parent | | Enterprise identification | Identified within the scope of the parent partner | Identified by a globally unique identifier | [Table 1. Discovery mode differences] {#telecom-discovery-via-arista-velocloud__table_velocloud_discovery_modes} Regardless of the mode, the connector builds the same inventory --- organizations, network sites, edge devices, and network service instances. The connector establishes the relationships between organizations and their network sites. For the full list of VeloCloud Orchestrator endpoints called during discovery, with sample responses, 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."). ## CMDB Integrations Dashboard {#telecom-discovery-via-arista-velocloud__section_r14_jdg_12c} The Integration Commons for CMDB application provides a dashboard with a central view of the status, processing results, and processing errors of all installed Service Graph Connectors. The dashboard displays metrics for all integration runs. You can filter the view to a specific integration, time duration, or integration run. For more details about monitoring integrations in the CMDB Integrations Dashboard, see [Integration Commons for CMDB](https://www.servicenow.com/docs/access?context=integration-commons-for-cmdb&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). **Related concepts** * [Configure Arista VeloCloud Service Graph Connector](https://www.servicenow.com/docs/4UrELOD~GWy7sJGVN1JJ7g "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).") **Related tasks** * [Run Arista VeloCloud SD-WAN Import](https://www.servicenow.com/docs/kzQq8M~OYhLEHHU5PP4HbA "Manually run a configured import schedule for the Arista VeloCloud Service Graph Connector (SGC) to verify that data from Arista VeloCloud was successfully imported or updated in the Configuration Management Database (CMDB). You can also perform the import to validate the connector setup, run one-off imports, or test newly configured connection aliases.")