Velocloud FAQs

This behavior is expected. The VCO UI and the API apply different visibility rules:

  • VCO UI: Displays only links that have been active within a defined time window (default is 1 day). Links that are inactive or disconnected beyond this period are hidden.
  • API: Returns ALL links associated with an edge, including active, disconnected, and long-inactive links.

Example:
You may see two links in the VCO UI (both in a STABLE state), while the API returns three links (two STABLE and one DISCONNECTED). The third link is valid but has been inactive longer than the UI’s visibility window.

Bottom Line: The API provides a complete and accurate inventory, while the UI applies filtering to show only recently active links.

The API returns all links, including:

  • Currently active or connected links
  • Disconnected links
  • Links that have been inactive for extended periods (even years)

This design is intentional and allows full inventory visibility for audit and tracking purposes.

This occurs when physical or hardware changes happen at the edge device. The logicalId is generated by the edge and represents the physical identity of the link.

Common reasons for logicalId changes:

For Wired Links (Ethernet):

  • Network interface card changes
  • Cable swaps between ports
  • Interface reconfiguration

For Cellular Links (LTE/5G):

  • SIM card replacement
  • Modem hardware swap
  • Other cellular hardware changes

Important: When the logicalId changes, VeloCloud treats the link as a new link. As a result, the internalId (a UUID generated by VCO) also changes.

There are three main identifiers for links:

  • link.id (linkId)
    • Source: VCO database
    • Stability: STABLE - this is the database primary key and remains consistent
  • link.logicalId
    • Source: Edge device
    • Stability: VARIABLE - changes when physical/hardware changes occur
  • link.internalId
    • Source: VCO system
    • Stability: CONDITIONAL - changes whenever logicalId changes

Relationship: If the logicalId remains the same, the internalId also remains the same. If the logicalId changes, the internalId will change as well.

Based on observed behavior, the edgeLogicalId is generally stable and does not change in the same way as a link’s logicalId. For reliable tracking, it is recommended to use edgeLogicalId together with link.id.

Effectively, yes. When the logicalId changes:

  • VeloCloud treats the link as a new link
  • A new internalId (UUID) is generated
  • The link is recreated rather than just updated

This typically indicates a physical change at the edge device, such as hardware replacement or reconfiguration.

This is expected behavior due to how Internet Service Providers manage IP address pools.

How this happens:

  1. Link A connects and receives IP address X from the ISP’s DHCP pool
  2. Link A disconnects, and the IP address is returned to the pool
  3. Link B later connects and is assigned the same IP address X
  4. VeloCloud retains the last known IP address for both links

Key point: VeloCloud preserves historical IP information for audit and troubleshooting purposes. Seeing the same IP address on different links is not an error.

Important: IP addresses should not be used as unique identifiers. Always use link.id and edgeLogicalId.

VCO uses time-based visibility properties to determine which links appear in the UI.

System-wide setting:

  • Property: edge.link.show.limit.sec
  • Default: 86,400 seconds (1 day)
  • Scope: Applies to all edges across all enterprises

Enterprise-specific setting:

  • Property: enterprise.edge.link.show.limit.days
  • Default: Not set
  • Scope: Applies only to the specified enterprise
  • Note: Takes precedence over the system-wide setting when configured

Links that remain inactive or disconnected beyond these thresholds are hidden from the UI but still exist in the system.

Yes. There are two options:

Option 1 – System-wide: Increase the value of edge.link.show.limit.sec on the System Properties page.

Option 2 – Enterprise-specific: Configure enterprise.edge.link.show.limit.days for a specific enterprise. Values can range from 0.5 to 365 days and override the system-wide setting.

Recommendation: Start with a moderate value and adjust as needed.

Can customers change these visibility settings themselves?

Yes. The edge.link.show.limit.sec property can be modified through the System Properties page if you have the required privileges. Enterprise-level properties can be configured for individual enterprises.

Will changing visibility settings affect historical reports or analytics?

No. These settings only control what appears in the UI and API responses. They do not affect:

  • Historical reports
  • Analytics dashboards
  • Stored metrics or statistics
  • Previously collected data

All historical data remains fully accessible.

Are there any downsides to increasing the visibility window?

Consider the following:

  • UI performance: Displaying more links may increase load times in large environments
  • API response size: API calls may return more data and take longer to process
  • Historical data: No impact
  • System performance: Typically minimal, but should be monitored at scale

Recommendation: Adjust the visibility window based on deployment size and operational needs.

No. Links are never automatically deleted from the VeloCloud database. They remain indefinitely unless explicitly removed, ensuring:

  • Complete historical data retention
  • Compliance with data retention requirements
  • Full audit trail availability

No. Link deletion is not available through customer-facing features or APIs.

VeloCloud has internal deletion capabilities for support and operational use, but these are not exposed to customers to avoid potential impact on connectivity or traffic flow.

Best practices:

  • Use visibility settings to control which links appear in the UI
  • Configure enterprise.edge.link.show.limit.days for enterprise-specific needs
  • Filter API results using the lastActive timestamp or state field
  • For compliance or regulatory data removal requirements, contact your account team

Yes, on a case-by-case basis.

Important considerations:

  • Availability: Limited to compliance or regulatory requirements
  • Permanence: Deletion is irreversible
  • Requirements: Clear deletion criteria and risk acknowledgment are required
  • Process: Contact your account team to discuss the request

Currently, there are no customer-facing link archival or deletion features on the VeloCloud roadmap. If this capability is important, engage with your account team or product management to share your requirements and business justification.

Quick Reference Summary

  • The API returns all links, while the UI filters links based on configured visibility settings.
  • Use edgeLogicalId + link.id as the composite unique identifier.

logicalId Changes

  • Expected when physical or hardware changes occur at the edge device.
  • Normal ISP behavior; VCO preserves the last-known state for historical tracking.

Visibility Settings

  • Configurable using system-level or enterprise-level properties.
  • Not available to customers; contact support for compliance-related requirements.
  • Use getEnterpriseEdges with {“with”: [“links”]} to retrieve the complete link inventory.

Need More Help?

If your issue is not covered here or you require support-assisted actions:

  • Contact your account team
  • Open a support ticket with relevant details
  • Include edge IDs, link IDs, and timestamps for faster resolution