Building

Configure the plug-in for each technology in your environment.
HID_View_VNA_Plugin_Config
DX NetOps Virtual Network Assurance
can collect performance and inventory data for virtual networks. To enable data collection, configure a plug-in for each virtual network technology in your environment.
The following video shows how to configure a plug-in, using the Cisco ACI plug-in as an example:

In this article:
Configure a Plug-in
Configure an instance of a plug-in for a virtual network technology in your environment.
DX NetOps Virtual Network Assurance
uses the configuration details to connect to the virtual network technology in your environment. After a connection has been established, it starts collecting performance and inventory data.
Prerequisite:
Ensure that you have set up the virtual network technology in your environment correctly to enable data collection.
You can configure a plug-in using the following methods:
This article describes how to configure a plug-in using the
DX NetOps Virtual Network Assurance
API.
Configure a Plug-in Using the
DX NetOps Virtual Network Assurance
API
Follow these steps:
  1. Go to the
    DX NetOps Virtual Network Assurance
    API:
    http://
    gateway_host
    :8080/vna/
  2. Expand the
    Admin
    resource.
  3. Retrieve an example plug-in configuration JSON. Select the following
    GET
    call, and then click
    Try it out!
    :
    /v1/admin/plugins/
    {pluginName}
    /template
    • pluginName
      is the name of the plug-in.
    You can list all installed plug-ins using the following GET call:
    /v1/admin/plugins
    The example plug-in configuration JSON is retrieved.
  4. Copy the contents of the example plug-in configuration JSON, and then update the required configuration details.
    You can get a description of the attributes for the plug-in configuration JSON in the topic for each plug-in, such as Viptela.
    In the plug-in configuration JSON, use the IP address to identify the technology.
    Do not
    use the hostname.
  5. POST the plug-in configuration JSON to the following endpoint, and then click
    Try it out!
    :
    /v1/admin/plugins/
    {pluginName}
    Or to update the configuration JSON of an existing plug-in, PUT the updates to the following endpoint:
    /v1/admin/plugins/
    {pluginName}
    • pluginName
      is the name of the plug-in.
    • configDesc
      is a meaningful description of the configuration. The description is required to identify the configuration.
    • engineConfig
      is the updated plug-in configuration JSON.
Verify Plug-in Status
To verify the status of a plug-in, change the engine status.
Follow these steps:
  1. Get the
    configId
    value of the plug-in. Select the following
    GET
    call, and then click
    Try it out!
    :
    /v1/admin/plugins/{
    pluginName
    }/configs
    • pluginName
      is the name of the plug-in.
    This call displays a list of the configurations for this plug-in.
  2. From the response body, copy the
    configId
    value for the plug-in. To identify the plug-in, use the
    configDesc
    .
  3. Select the following GET call, and then click
    Try it out!
    :
    /v1/admin/engines/{
    engineid
    }
    • engineid
      is the
      configId
      value.
If the plug-in is operating correctly, the response body is
RUNNING
.
Upload a New Plug-in
For plug-ins that are delivered outside of the release, upload the plug-in to the VNA gateway before you configure it so that is can collect data. This procedure requires CURL.
Follow these steps:
  1. Download the new plug-in, and then copy it to a system that has access to the gateway.
  2. Upload the plug-in to the gateway:
    curl -X POST http://
    gateway_host
    :8080/vna/rest/v1/admin/plugins -H "Context-Type: application/octet-stream" -T
    new-plugin
    .jar
    • new_plugin
      is the name of the plug-in JAR file.
The plug-in is uploaded to the VNA gateway.
To revert a plug-in to an earlier version, add the following parameter to the URL:
?forceDowngrade=true