Documentation forNetwork Performance Monitor

Versa Networks Versa SD-WAN

When you enable SD-WAN monitoring on your Versa Director orchestrators, you can monitor orchestrators, edge devices, and their interfaces polled via API. You can use alerts and reports relevant to SD-WAN monitoring.

Polling method

All data for Versa Networks devices, including basic node details, is polled via the Versa Director REST API.

SNMP, CLI, and direct device API polling are not supported for Versa appliances.

Monitor SD-WAN appliances

Add appliances managed by a monitored Versa Director to get further details via the Versa Director API.

  • You can display general details, such as appliance name, model, serial number, status, firmware version, vendor, and organization or site.
  • You can display all IP addresses for the appliance.
  • You can monitor CPU and memory utilization.
  • You can monitor interface status, general details, and traffic statistics.
  • You can monitor uplinks (WAN interfaces) and dynamic SD-WAN tunnels, including tunnel SLA metrics (latency, jitter, packet loss, and flaps).

Monitor orchestrators

  • You can display status and response time for the Versa Director, polled via the Versa Director REST API.
  • You can display the list of all appliances managed by the orchestrator and add them in a simplified discovery as API-only nodes.

Versa Networks Versa SD-WAN setup and monitoring steps

Before you begin

  • Make sure the appliances you want to monitor are managed by a Versa Director orchestrator that is reachable over the network from SolarWinds Observability Self-Hosted.

  • Make sure OAuth2 API access is enabled on Versa Director.

  • Get the following credentials from Versa Director:

    • OAuth2 client credentials: client ID and client secret
    • A user account (username and password) with permission to access the organizations you want to monitor

  • Use the DNS hostname of the Versa Director. IP addresses are not supported for the orchestrator node.

  • If the appliances are polled by a different polling engine than the orchestrator, make sure that polling engine can reach the Versa Director. Otherwise, SD-WAN polling fails.

Monitored properties

All metrics are polled via API from the Versa Director. Collected data includes:

  • Orchestrator inventory, status, and response time
  • General appliance details and IP addresses
  • CPU and memory utilization
  • Interfaces
  • Appliance uplinks (WAN interfaces)
  • SD-WAN tunnels and tunnel statistics (latency, jitter, packet loss)

Rate limits

By default, requests to a Versa Director are limited to 250 requests per 5 seconds for a polling engine, to avoid overloading the Versa Director API.

Session limit

A Versa Director user profile supports a limited number of parallel sessions (approximately 10). If other integrations or users use the same credentials, authentication can fail intermittently. SolarWinds recommends that you use dedicated Versa Director credentials for SolarWinds Platform polling.

Add new SD-WAN devices for monitoring in SolarWinds Observability Self-Hosted

To monitor SD-WAN, add the orchestrator as a node, and then add edge devices.

Each monitored Versa Director orchestrator uses a node license.

Add an orchestrator

  1. Log in to the SolarWinds Platform Web Console as an administrator.

  2. Click Settings > Manage Nodes, and then click Add Node.

  3. Enter the DNS hostname of the Versa Director.

  4. In Polling Method, select Orchestrators: API.

  5. Under Orchestrators, select Versa Devices.

  6. Enter the Username, Password, Client ID, and Client Secret.

  7. Click Get Organizations, and then select the Organization you want to monitor.

    The list of organizations is retrieved from Versa Director. If authentication fails, see Troubleshooting.

  8. Review and adjust the device properties, credentials, proxy settings, and polling intervals.

  9. (Optional): Configure custom properties and alert thresholds.

  10. Click OK, Add Node.

The added device is now monitored as an SD-WAN orchestrator. Add connected devices to complete the SD-WAN configuration.

You cannot add a Versa Director orchestrator using Network Discovery. Use the Add Node wizard with the Orchestrators: API polling method.

Add appliances connected to the orchestrator as API-only nodes

When you have added the orchestrator for monitoring, add the appliances you want to monitor.

  1. In SolarWinds Platform Web Console, click Settings > Manage Nodes.

  2. On the Manage Nodes view, click the added orchestrator node to open the orchestrator details view.

  3. On the SD-WAN Orchestrator Details view, click Discover Versa Devices in the Management widget.

    SolarWinds Observability Self-Hosted requests the list of appliances managed by the selected organization from Versa Director. A simplified version of Network Sonar Wizard opens.

  4. Review the appliances retrieved from the orchestrator, include only the appliances you want to monitor, and click Next.

  5. Complete the wizard by clicking Discover on the last tab. The wizard discovers the appliances based on the Versa Director API.

  6. Discovered appliances are listed in the Network Sonar Results wizard. Complete the wizard to add the appliances for monitoring.

When you finish the wizard, go to the SD-WAN Orchestrator Details page (Settings > Manage Nodes > click the orchestrator node). After the next poll, the page will display data not only for the orchestrator, but also for monitored edge devices.

View SD-WAN data for Versa Networks devices

When you enable SD-WAN monitoring for an orchestrator node and click it, the SD-WAN Orchestrator Summary view opens.

By default, it includes widgets you can use to manage the device, view the device details, active alerts, latest events, or AppStack for the device.

Orchestrator Inventory

This widget displays a list of devices connected to managed orchestrators. Devices managed by SolarWinds Observability Self-Hosted are marked in the Managed by Platform column.

To add unmanaged appliances, click the Discover Versa Devices button and add them for monitoring.

WAN UpLinks

On SD-WAN Orchestrator views, this widget displays WAN uplinks for all edges paired with the orchestrator.

On an edge Node Details view, the widget displays WAN uplinks for the edge.

SD-WAN Tunnels

On SD-WAN Orchestrator views, this widget displays dynamic SD-WAN tunnels and their SLA metrics (latency, jitter, and packet loss) for all appliances managed by the orchestrator.

On an appliance Node Details view, the widget displays SD-WAN tunnels for the appliance.

Hardware Health, VLAN, Topology, and High Availability widgets do not display data for Versa Networks devices because this data is not collected.

Monitor Versa Networks Versa SD-WAN interfaces

Interfaces on Versa Networks appliances are polled via the Versa Director API. Interfaces are discovered during the API discovery.

Interface polling intervals use the polling intervals set for nodes. As a result, to force polling interface details, select the parent node in Node Management and click Poll Now. The Poll Now option for individual interfaces is not available.

Known limitations

  • A DNS hostname is required for the orchestrator node. IP-only orchestrator nodes are not supported.
  • CPU utilization is reported as an overall percentage. A per-core CPU breakdown is not available.
  • If other consumers place additional load on the same Versa Director, requests can still be throttled or delayed, even with rate limiting applied on the SolarWinds Platform side.

Troubleshooting

Authentication fails when you add the orchestrator

Versa authentication requires both OAuth2 client credentials (client ID and client secret) and user credentials (username and password). Verify that all four values are correct.

If the credentials are correct but authentication still fails, the Versa Director user account might have reached its parallel session limit. Log the user out of Versa Director to close active sessions, and then try again.

The orchestrator or appliances are unreachable, or API errors occur

  • Make sure the orchestrator node was added with a DNS hostname, not an IP address.
  • Make sure the polling engine assigned to the appliances can reach the Versa Director.
  • If the appliances use a different polling engine than the orchestrator, verify connectivity from that polling engine as well.

Data is slow or delayed because of rate limiting

If a rate-limiting warning appears on the Versa orchestrator Node Details view, or a rate-limiting event is generated:

  • Reduce the number of other consumers of the Versa Director API, where possible.
  • In Advanced Configuration, adjust the Orchestrators.Versa settings, such as Versa Orchestrator Requests Limit, Versa Orchestrator Requests Limitation Period, or Versa Orchestrator Inventory Requests Cache Time to Live.