Building

Configure the plug-in for each technology in your environment.
cavna32
Virtual Network Assurance
 collects performance data for virtual networks. To enable data collection, configure the plug-in for each technology in your environment.
The following video shows an example of plug-in configuration with the Cisco ACI plug-in:
 

 
 
 
Configure a Plug-in
For each technology in your environment, configure an instance of the plug-in. Ensure that the technology is set up correctly to enable data collection. For more information, see the relevant page for the specific plug-in.
 
Follow these steps:
 
  1. Navigate to the 
    Virtual Network Assurance
     API:
    http://
    gateway_host
    :8080/vna/
     
  2. Expand 
    Admin
    .
  3. Select the following GET call, specify the 
    pluginName
    , and click 
    Try it out!
     
    /v1/admin/plugins/{pluginName}/template
     To list all installed plug-ins, use the following GET call:
    /v1/admin/plugins
  4. Copy the content of the template and complete the configuration details. For examples of the configuration JSON template, see the documentation for each plug-in.
     In the configuration JSON template, use the IP address to identify the technology. 
    Do not
     use the hostname.
  5.  POST the configuration JSON template to the following endpoint:
    /v1/admin/plugins/{pluginName}
     To update the configuration an existing plug-in, PUT the updates to the following endpoint:
    /v1/admin/plugins/{pluginName}
  6. Specify the 
    pluginName
    , and write a meaningful description in 
    configDesc
    . After you post the configuration JSON template, you cannot view the configuration details. The description is required to identify the configuration.
  7. Update the required details in the JSON template, and click 
    Try it out!
    Virtual Network Assurance
     uses the configuration details to connect to the technology and begin collecting performance and inventory data.
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, specify the 
    pluginName
    , and click 
    Try it out!
     
    /v1/admin/plugins/{pluginName}/configs
  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, specify the 
    configId
     value as the 
    engineid
    , and click 
    Try it out!
     
    /v1/admin/engines/{engineid}
    If the plug-in is operating correctly, the response body is 
    RUNNING
    .
Upload a New Plug-in
For plug-ins that are delivered outside the release, upload the plug-in to the gateway before you configure the plug-in. The procedure requires CURL.
 
Follow these steps:
 
  1. Download the new plug-in from CA Technologies and copy the plug-in 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 gateway. To collect data, configure the plug-in.
 To revert a plug-in to an earlier version, add the following parameter to the URL:
?forceDowngrade=true