Skip to main content

Cloud-Managed Device Collection

Forward Enterprise supports onboarding cloud-managed infrastructure through:

  • Cisco Meraki Dashboard
  • Arista VeloCloud Orchestrator
  • Juniper Mist Cloud

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. For how Meraki MR access points are modeled and licensed, see Wireless.

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.

Juniper Mist Setup​

Overview​

Juniper Mist is a cloud-hosted platform for onboarding, managing, and configuring network devices. Forward Enterprise connects to the Mist cloud with an API key to discover the access points configured under a Mist organization and model them in snapshots. For how Mist access points are modeled and licensed, see Wireless.

Prerequisites​

  • A Mist organization containing the access points to be collected must be pre-configured.
  • The region of the access points must be known. This region determines the API host used for the connectivity test and collection.
  • A Mist API key, stored in Forward Enterprise.
  • Network reachability from Forward's collector to the Mist cloud is required.

Step 1 — Launch the Mist Setup Wizard​

Open the Cloud-managed onboarding wizard and select Juniper Mist.

Provide the following:

  • Mist setup name to represent the Mist organization.
  • A Region. This sets the API host for all subsequent calls.
  • An API key. Add it from the dropdown with Add credentials: give the credential a name to refer to it, and enter the key value in the password field.
  • (Optional) Maximum concurrent API requests.

Click Test connection to validate the credentials and access. Once the test succeeds, click Next. The setup is created in the background as you advance.

Step 2 — Device Discovery​

Forward automatically discovers all access points configured under the organization.

  • A slider to auto-detect and collect all currently discovered devices is on by default. New access points added to a Mist organization later are not picked up automatically. They need to be re-discovered by going to the setup's Devices view and clicking Refresh.
  • To collect only specific devices, turn the slider off and select the ones you want.
  • Discovered devices are listed by display name and MAC address.
  • You can assign locations and tags to the devices using the edit option for each device or the bulk edit option.

Select the devices to collect from and then click Next.

Step 3 — Completion​

A summary confirms the access points that were added. The devices appear in Inventory and are collected during subsequent snapshots.

Managing and Maintaining a Mist Setup​

After onboarding:

  • Edit settings
    Update the setup name, region, API key, or other connection parameters. You must run Test connection again if any connection parameters are edited.
  • Refresh devices
    New access points added to the Mist organization are not collected automatically. To pick them up, open the setup, go to Devices, click Refresh to re-discover, then Save.
  • Deleting a setup
    Removing the Mist setup stops all collection for that organization and removes its access points 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.
  • The Mist cloud does not consume a license; each Mist access point consumes a Lite license.