Skip to main content

Cloud-Managed Device Collection

Forward Enterprise supports onboarding cloud-managed infrastructure through:

  • Cisco Meraki Dashboard
  • Arista VeloCloud Orchestrator

Once configured, Forward automatically discovers the managed devices and includes them in snapshots using API-based collection.

Cisco Meraki Dashboard Setup​

Overview​

Forward Enterprise connects to the Meraki Dashboard API to gather device inventory and configuration/state data for modeling in snapshots.

Prerequisites​

  • A Meraki Dashboard user account with access to the networks to be collected.
  • A Dashboard API key stored in Forward Enterprise.
  • Two-factor authentication (2FA) must be disabled for the Dashboard user used for this integration.
  • When prompted, the user must provide a Dashboard Security Code.
    (This single use code is required by Meraki when certain API permissions or account conditions apply and must be entered in the setup wizard.)

Step 1 — Launch the Meraki Setup Wizard​

Open the Cloud-managed onboarding wizard and select Cisco Meraki.

The wizard will request:

  • A setup name
  • A region (select one; this determines the API endpoint)
  • Meraki login credentials
  • A stored API key

If Meraki requires a Dashboard Security Code, the wizard presents an input field for it during this stage.

A Test connection action validates the credentials and access.

Step 2 — Device Discovery and Auto-Selection​

After a successful connection test, Forward automatically retrieves all Meraki-managed devices available to the user.

By default:

  • All discovered devices are automatically selected for collection
  • The user may optionally deselect devices they do not wish to collect
  • By default, devices are configured for auto-collect, meaning all future devices added to the Meraki Dashboard under the same organization will be collected automatically without manual updates to the setup

Step 3 — Location Assignment (Optional)​

Meraki devices may be assigned locations to improve organization and navigation within Forward Enterprise. Bulk assignment is available.

Step 4 — Completion​

A summary displays the number of devices added. Devices appear in Inventory and are collected during subsequent snapshots.

Managing and Maintaining a Meraki Setup​

After onboarding:

  • Edit settings
    You can update API keys, region, login credentials, or the setup name.
  • Device list updates
    Devices added later in the Meraki Dashboard can be automatically collected if auto-select is enabled.
  • Removing devices from collection
    Devices may be removed from the collection set individually or by editing the setup configuration. Removing a device prevents further collection and removes it from future snapshots.
  • Deleting a setup
    Removing the Meraki setup stops all collection for that dashboard and removes all associated cloud-managed devices from future snapshots.

Arista VeloCloud Orchestrator Setup​

Overview​

Forward Enterprise integrates directly with a VeloCloud Orchestrator to retrieve device inventory and configuration/state information for Gateways and Edge devices.
The orchestrator itself is not modeled as a device and does not consume a license.

Collection uses both the REST API and the WebSocket API, which require a sufficiently privileged account.

Prerequisites​

  • A VeloCloud user account with the Enterprise Support role.
    (This role is required for WebSocket API access.)
  • A VeloCloud API key generated by that user.
  • A valid Base URL for the orchestrator; the URL must begin with http:// or https://.
  • Network reachability from Forward’s collector to the orchestrator APIs.

Step 1 — Launch the VeloCloud Setup Wizard​

Select the VeloCloud option and provide:

  • A setup name
  • The Base URL
  • The API key
  • (Optional) Proxy settings if required for outbound connectivity

A connection test validates access and retrieves enterprise context information.

Step 2 — Device Discovery​

After successful validation, Forward retrieves all devices (Gateways and Edges) managed by the orchestrator.

Important:

  • All discovered devices are automatically collected.
  • Devices are not selectively onboarded; the checkboxes in the wizard are used only for assigning Forward locations in bulk, not for choosing which devices to collect.

Step 3 — Location Assignment​

Users may assign locations to devices individually or in bulk.

Step 4 — Completion​

A summary page lists the number of Gateways and Edges added to the environment.

Managing and Maintaining a VeloCloud Setup​

After onboarding:

  • Edit settings
    Update the Base URL, API key, or setup name at any time.
  • Device changes
    Forward automatically includes newly added VeloCloud devices without additional configuration.
  • Removing devices
    Devices cannot be deselected from collection individually; removal occurs only if they are no longer reported by the orchestrator.
  • Deleting the setup
    Deleting the VeloCloud setup removes all associated cloud-managed devices from future snapshots.

Licensing​

  • The VeloCloud Orchestrator does not consume a license.
  • Each VeloCloud Gateway and Edge device consumes a device license.
  • Each Meraki device added through the Dashboard integration consumes a device license.