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.

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).