This section guides you through setting up, configuring, and managing the VMware NSX Advanced Load Balancer integration in OpsRamp.
Prerequisites
- OpsRamp Classic Gateway (Linux) version 15.0.0 or later.
- OpsRamp NextGen Gateway version 15.0.0 or later.
- OpsRamp recommends using the latest Gateway version for full coverage of recent bug fixes and enhancements.
- Ensure that the provided IP address/host name, port, and credentials are valid and accessible for successful integration.
- Verify network connectivity from the gateway using:
ping <IP Address/Host Name> - Check port accessibility using:
telnet <IP Address/Host Name> <Port>
- Verify network connectivity from the gateway using:
Configure VMware NSX Advanced Load Balancer Integration
To configure the integration:
- From All Clients, select a client.
- Navigate to Setup > Account.
- Select the Integrations tab.
- The Installed Integrations page, where all the installed integrations are displayed. Click + ADD on the Installed Integrations page.
- If you do not have any installed applications, you will be navigated to the Available Integrations page. The Available Integrations page displays all the available applications along with the newly created application with the version.
Note: Search for the application using the search option available. Alternatively, use the All Categories option to search. - Click ADD on the VMware NSX Advanced Load Balancer tile.
- From the Configurations page, click + ADD. The Add Configuration page appears.
- Enter the following BASIC INFORMATION:

| Field Name | Description | Field Type |
|---|---|---|
| Name | Enter the name for the configuration. | String |
| AVI EndPoint IP Address/Host Name | Enter the IP address/host name of the Commvault. It should be accessible from Gateway. | String |
| X-Avi-Version | X-Avi-Version of VMware NSX Advanced Load Balancer | Dropdown |
| Port | Enter the port number to communicate with OpsRamp's endpoints. It should be accessible from Gateway. Default Value: 8080 | Integer |
| Credential | Select the Credential from the drop-down list. Notes:
| Dropdown |
| Is Secure | Select this checkbox if you want the communication between your system and the specified endpoint to be secured using protocols such as HTTPS (HTTP over SSL/TLS). Default Selection: When selected, it signifies that the connection is encrypted, providing an added layer of security to the data being transmitted. | Checkbox |
| API Timeouts | When selected, this checkbox allows you to configure timeout settings for API requests made by the integration to the OpsRamp platform. | Checkbox |
| Connection Timeout in Secs | Select the maximum time, in seconds, that the integration must wait while establishing a connection with the OpsRamp API endpoint. Default Value: 60 | Dropdown |
| Connection Request Timeout in Secs | Select the maximum time, in seconds, required to process an HTTP call: from sending a request to receiving a response. Default Value: 10 | Dropdown |
| Socket Timeout in Secs | Select the maximum time of inactivity between two data packets when exchanging data with a server. Default Value: 10 | Dropdown |
| App Notification Notifications | When selected, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception. | Checkbox |
Notes:
- By default the Is Secure checkbox is selected.
- IP Address and Port should be accessible from Gateway.
- Select the following:
- App Failure Notifications: if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.
- Select the following Custom Attribute:
| Functionality | Description |
|---|---|
| Custom Attribute | Select the custom attribute from the drop down list. |
| Value | Select the value from the drop down list. |
Note: The custom attribute that you add here will be assigned to all the resources that are created by the integration. You can add a maximum of five custom attributes (key and value pair).
- In the Native Types section, select the native types to be discovered.
- In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:
- Minutes
- Hourly
- Daily
- Weekly
- Monthly
- Click ADD.
The configuration is saved and displayed on the configurations page after you save it.
Note: From the same page, you may Edit and Remove the created configuration.
- Under the ADVANCED SETTINGS, Select the Bypass Resource Reconciliation option, if you wish to bypass resource reconciliation when encountering the same resources discovered by multiple applications. Note: If two different applications provide identical discovery attributes, two separate resources will be generated with those respective attributes from the individual discoveries.
- Click NEXT.
- (Optional) Click +ADD to create a new collector. You can either use the pre-populated name or give the name to your collector.
- Select an existing registered profile.
- Click FINISH.
The integration is installed and displayed on the INSTALLED INTEGRATION page. Use the search field to find the installed integration.
Modify the Configuration
- See Modify an Installed Integration or Application article.
Note: Select VMware NSX Advanced Load Balancer.
View the VMware NSX Advanced Load Balancer Details
To discover resources for VMware NSX Advanced Load Balancer:
- Navigate to Infrastructure > Search > Load Balancer > VMware NSX Advanced Load Balancer. The VMware NSX Advanced Load Balancer page is displayed
- Select the application on the VMware NSX Advanced Load Balancer page
- The RESOURCE page appears from the right.
- Click the ellipsis (…) on the top right and select View Details.

- Navigate to the Attributes tab to view the discovery details.
- Click the Metrics tab to view the metric details for VMware NSX Advanced Load Balancer.

View resource metrics
To confirm VMware NSX Advanced Load Balancer monitoring, review the following:
- Metric graphs: A graph is plotted for each metric that is enabled in the configuration.
- Alerts: Alerts are generated for metrics that are configured as defined for integration.