Monitoring Versa Networks Devices

Overview

Add Versa Directors to TOS using the Open Policy Model (OPM). OPM expands device coverage in TOS to additional vendors. Tufin provides device connectors that collect the device's configuration and policy data and import it into SecureTrack.

The Versa device connectors support onboarding Versa Directors using HTTPS API and OAuth authentication. SecureTrack pulls topology and rule data from the Director on a defined schedule, based on sync settings in Tufin Integrations.

For supported features, see Features by Vendor in SecureTrack and Features by Vendor in SecureChange.

The Versa integration is supported only with Versa Director version 22.X or later.

Prerequisites

  • Versa Orchestrator only: HTTPS API access with OAuth authentication

  • Customer Portal access to download the OPM package

  • Admin credentials for SecureTrack and SecureChange to be defined through Tufin Integrations before configuring device sync

  • TOS server:

    • sudo permissions to run the installer

    • File upload permissions to /opt/misc

  • On systems with non-Tufin OS, python3 and bzip2 packages installed

Install the OPM package

Install the OPM package from the shell on the TOS server. The steps are identical for both new installations and upgrades.

If you have existing OPM packages, the OPM installer automatically detects and upgrades older versions.

  1. Go to the Download center.

  2. Select Versa Secure SD-WAN.

  3. Click Download to Computer.

  4. Upload the downloaded file to /opt/misc (recommended) on the TOS server:

    sh <package-name>

    where:

    <package-name> is the name of the package you downloaded in the format install-<vendor>-1.0.0.aur.run

  5. Wait for the installation to complete. The installer installs PS Proxy and Tufin Integrations if they don't exist. If an older version is installed, the script upgrades it.

SecureTrack or SecureChange credentials are not required for and during installation.

After the installation, before you sync devices, make sure you define the credentials through Tufin Integrations.

Add a device

  1. In SecureTrack, go to Monitoring > Devices > Device Viewer.

  2. Click Add Device, and then select Add OPM Device.

  3. In the ADD OPM DEVICE define the device details:

    • Vendor: The vendor with the device to add, Versa Networks.

    • OPM agent: Select Tufin-Versa-Networks. The agent is displayed only if it was installed successfully.

    • Type: Select Director.

    • Display name: The name to display for this device in SecureTrack

    • IP: The IP address of the device.

  4. Click Next.The Configure Device properties form is displayed.

  5. Configure the device properties:

    TOS must have connectivity to both TCP 9182 and 9183 ports on the Versa Director.

    • API port:  The port used to connect to the Versa Director REST API. Default is 9182.

    • OAuth authenticate port: The port used for OAuth authentication. Default is 9183.

      OAuth client ID*: The client ID provided by your administrator.

    • OAuth client secret*: The secret provided with your client ID. See how to create OAuth credentials in the Versa Director REST API.

    • Username: The API username for the device.

    • . Password: The API user password for the device.

  6. To confirm settings and add the device, click Save.

Sync device with SecureTrack

Use Tufin Integrations to configure how SecureTrack syncs with your OPM-managed device. Tufin Integrations is the web interface for managing OPM devices. It is automatically installed when installing the OPM package if it does not exist.

  • Configuring SecureTrack to sync with your OPM-managed device includes:

  • Defining user credential for SecureTrack and SecureChange

  • Importing devices and assigning them to a cluster

  • Scheduling sync and reviewing run details

When configuration is complete, SecureTrack runs a script that connects to the device, retrieves configuration data (such as interfaces, routes, and rules), and imports the data. This process enables scheduled or manual data collection.

Step 1: Go to Tufin Integrations

  • Do one of the following:

    • Go to https://<tos-vip>/apps/integrations.

    • In SecureTrack , from the list of Tufin Extensions , select Tufin Integrations.

Step 2: Set user credentials for Tufin API

For API configuration, define the username and password to connect to SecureTrack and SecureChange. If the credentials are not defined, Tufin Integrations cannot retrieve the devices.

  1. From the sidebar, select Settings > Tufin API Configuration.

    OR

    Go to https://<tos-vip>/apps/integrations/configuration/tufin-api.

  2. Define the username and password credentials for SecureTrack and SecureChange.

  3. Click Save.

    Credentials are automatically validated.

  4. Verify that Credentials Valid appears next to SecureTrack and SecureChange, indicating that the credentials are correct.

  5. If Credentials Invalid appears, correct the credentials, save, and validate again.

Step 3: Select OPM vendor and import devices

Run discovery to import the devices for vendors.

  1. Return to the Dashboard.

  2. Below OPM Device Connectors, select the OPM client or vendor with the devices to monitor.

  3. Click IMPORT DEVICES and then click RUN DISCOVERY.

    The available devices are displayed.

  4. Select the parent management device, or select a specific device.

  5. Right-click and select Enable Devices.

  6. Click Save.

    The enabled devices are added to the vendor list.

Step 4: Activate device monitoring and configure monitoring options

Activate monitoring for devices, and assign them to the current cluster or to a different cluster. In multi-domain deployments, you can migrate devices to different SecureTrack domains.

You can assign devices to different TOS clusters for monitoring. For example, you can monitor one OPM device from the main cluster and another from a remote collector. Remote collectors are available only if they are configured in TOS.

Migrating the device to a new domain, automatically removes the device from reports, queries, audits and alerts configured in the previous domain.

  • Retains device permissions for administrators of the target domain, but removes device permissions from users.

For automated or manual sync to run, you must enable monitoring for the device.

  1. Select one or more devices.

  2. Right-click the device or devices and select Start to start monitoring them.

  3. Optional. To move the selected devices to a new domain, right-click and select Move Device to New Domain.

  4. Optional. To monitor the selected devices from a different cluster, right-click and select one of the following:

    • Migrate to main: Monitor the device from the primary cluster.

    • Migrate to <remote_collector>: Monitor the device from a remote collector, for example, RC4.  Available only if a remote collector is configured in TOS. The actual name of the remote collector differs by environment.

Step 5: Set automated sync schedule and view run details

Schedule automated syncs or trigger a manual sync on demand when monitoring is enabled for the device. View per-device status, start/end time, and message after each agent run.

  1. In the Configuration section, set the automated sync schedule:

    1. Set Interval as hourly, daily, weekly, or monthly.

    2. Choose the Time or Day of execution.

    3. To enable the script, select Enabled.

    4. Click Save.

  2. To start collecting revisions immediately, click RUN.

    If not triggered manually, the sync is triggered as scheduled.
    Every script execution retrieves the configuration from all devices assigned to the vendor’s OPM agent.

  3. Verify the results in the Run Details popup:

    In the Device Connector Runs (last 10) table, in the Run Details column, click the blue information icon information icon .

    The popup shows the status, start and end time, and a message for each device in the run.

Below is an example of the device connector page for Huawei, with the device list, Configuration panel, and Device Connector Runs.

Delete child devices

OPM management platforms can delete child devices through Tufin Integrations.

  1. In SecureTrack , from the list of Tufin Extensions , select Tufin Integrations.

  2. From the list of devices, select one or more devices to delete.

  3. Right-click and select Delete Child Device.

    The Delete Child Devices page opens.

  4. Do one of the following:

    • To select all child devices, select the parent device.

    • To select specific child devices, select the devices.

  5. In the confirmation field, to enable the Delete button, type delete.

  6. Click Delete.

How do I get here?

SecureTrack > Monitoring > Devices > Device Viewer