VeloCloud is a cloud network service solution enabling sites to deploy Enterprise grade access to legacy and cloud applications over both private networks and Internet broadband.

The following diagram shows the VeloCloud Software-defined WAN solution (SDWAN) components (in orange).

Basic VeloCloud discovery

The Server Manager provides these basic VeloCloud management services:
  • Provides end-to-end visibility into VeloCloud based SDWAN infrastructure.
  • Associates core MPLS network components and the VeloCloud overlay tunnels.

VeloCloud Architecture

Discovery Flow

The Server Manager imports initial topology from the IP Availability Manager. After the topology is imported, Server Manager discovers domain-specific entities related to the features and creates additional topology objects for those features.

As a first step of discovery, VeloCloud Orchestrator (VCO) is discovered based on ICMP discovery. If the orchestrator device is not ICMP pingable, then workaround would be to add the device manually to the IP server.
Note: To manually add the orchestrator device to IP server, refer VMware Telco Cloud Operations Configuration Guide.
On discovery of VeloCloud Orchestrator (Host) in SMARTS-IP domain manager, SMARTS ESM server imports the Host from IP Domain Manager and further does a complete discovery of Velocloud topology.

Incremental Discovery

The discovery time for a VeloCloud topology is proportion to the number of edges in the VeloCloud.

For, the VeloClouds with the large number of Edges the discovery takes hours. If the configuration is changed at a Tenant/Edge level, then to get just the new changes the incremental discovery can be used. There incremental discovery can be triggered for an existing Tenant/Edge.

The rediscovery can only be triggered using a remote API client or dmctl command of the Server Manager.

Incremental Tenant Discovery

To trigger an incremental tenant discovery,, run the following command:

dmctl -s <esm server> invoke Tenant::<TenantName> rediscover

Where, TenantName is the name of the tenant in the ESM topology for which the incremental discovery must be triggered.

The incremental tenant discovery discovers all the classes and attributes mentioned in the Topology section but for that particular Tenant.
Note: The incremental tenant discovery is available for all VCO user types (enterprise, MSP, and Operator).

Incremental Edge Discovery

To trigger an incremental edge discovery, run the following command:

dmctl -s <esm server> invoke VEdge::<EdgeName> rediscover

Where, EdgeName is the name of the VEdge instance in the ESM topology for which the incremental discovery must be triggered.

The incremental tenant discovery discovers IP, interfaces, and network connection for the Edge. It does not discovery relationships that are between edges (Hub and Spoke, Edge Cluster) and edge and Gateways(Tunnel).

Typically, configuration affecting these relationships are done at the profile level and pushed to set of Edges and so an incremental Tenant discovery is more suites here.
Note: The incremental Edge discovery is available for all VCO user types (enterprise, MSP, and Operator).

Monitoring Flow

For first time when discovery is initiated from SMARTS Domain Manager, DCF controller (part of the DCF framework) managing the lifecycle of the collectors instantiates and deploys the VeloCloud Discovery and Monitoring Collectors. The polling configuration applied to the VeloCloud Monitoring Collector polls VeloCloud Orchestrator based on specified polling cycle and frequency. The monitoring collector polls for the status attribute of the discovered Velocloud topology objects.