--- title: Avi Vantage load balancer discovery description: The ServiceNow Discovery and Service Mapping applications use the Avi load balancer discovery patterns to find Avi Vantage load balancer components. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/discovery-and-service-mapping-patterns/avi-load-balancer-discovery.html release: australia product: Discovery and Service Mapping Patterns classification: discovery-and-service-mapping-patterns topic_type: reference last_updated: "2026-03-12" reading_time_minutes: 6 breadcrumb: [Available on-premise discovery patterns, Discovery patterns used by ITOM Visibility, ITOM Visibility, IT Operations Management] --- # Avi Vantage load balancer discovery The ServiceNow Discovery and Service Mapping applications use the Avi load balancer discovery patterns to find Avi Vantage load balancer components. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store. Discovery uses the Avi Load Balancer Controller pattern and the Avi Load Balancer Controller - Session-based pattern to run horizontal discovery. Both patterns use set of REST APIs to find the load balancers. They differ only in the type of authentication used when running the API queries. For top-down discovery, Service Mapping uses the Avi Load Balancer VIP pattern. The patterns support Avi infrastructure residing on AWS and VMware. They relate the discovered CIs to the infrastructure only when run on VMware . The patterns also support Global Server Load Balancing \(GSLB\). You can use these patterns on the ServiceNow AI Platform® using the release Madrid patch 5, New York or later. ## Request apps on the Store Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html). ## Prerequisites - Ensure that your instance supports the Avi Load Balancer CI class models by deploying the latest version of the CMDB CI Class Models store app. Install the application from the ServiceNow Store. - For the Avi Load Balancer Controller pattern: - In the Avi Controller, ensure that Basic Authentication is allowed. - Configure the following credentials: 1. Navigate to **Discovery** > **Credentials** 2. Click **New**. 3. Click **Basic Auth Credentials**, fill out the form, and then click **Submit**. |Field|Description| |-----|-----------| |Name|Credential name.| |Active|Option for enabling this credential for discovery. Select this check box to enable discovery.| |Applies to|Select **All MID servers**.| |Order|Order in which the platform tries this credential as it attempts to log on to devices. A smaller number indicates that the credential appears higher in the list. Establish the credential order when using large numbers of credentials or when security locks out users after three failed login attempts. If all the credentials have the same order number, or none, the instance tries the credentials in a random order. The default value is 100.| |User name|Name of the user for performing Avi Load Balancer discovery.| |Password|Password for this user.| 4. [Run a Quick Discovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/t_CreateADiscoverySchedule.md) on the IP address of the Avi Controller Cluster. - For the Avi Load Balancer Controller - Session-based pattern: - Create a Basic Authentication credential with an alias: 1. Navigate to **Connections & Credentials** > **Connection & Credential Aliases**. 2. Click **New**. 3. Enter a unique name for the alias and select **Credential** for the alias type. 4. Click **Submit**. 5. Open the new alias. 6. On the Credentials tab, click **New**. 7. Select **Basic Auth Credentials** for the credential type and fill out the form. |Field|Description| |-----|-----------| |Name|Credential name.| |User name|Name of the user for performing Avi Load Balancer discovery.| |Password|Password for this user.| 8. Click **Update**. - Create a [serverless discovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/serverless-discovery.md) schedule. Then do the following: 1. In the scheduler, click the **Serverless Execution Patterns** tab. 2. Click **New**. 3. Fill out the form and then click **Submit**. |Field|Description| |-----|-----------| |Name|Provide a descriptive name.| |Pattern|Select the Avi Load Balancer Controller - Session-based pattern.| 4. Open the record created in the previous steps, and configure these parameters: |Parameter|Description| |---------|-----------| |IP address|The Avi IP address.| |Credential alias|The name of the credential alias created above.| - For the Avi Load Balancer Controller pattern and the Avi Load Balancer Controller - Session-based pattern, provide a user with permissions to send the following API queries. - /api/cluster - /api/serviceengine - /api/pool - /api/vimgrvmruntime?controller\_vm=true - /api/cloud - /api/virtualservice - /api/serviceenginegroup - /api/gslbservice - /api/tenant - For the Avi Load Balancer VIP pattern: - [Create an service instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/create-it-services.md). - Before using the Avi Load Balancer VIP pattern, use one of the horizontal Avi load balancer discovery patterns to find the Avi infrastructure. ## Data collected by Discovery during horizontal discovery The discovered data includes the following tables and fields.
Table and field Description
Avi Controller \[cmdb\_ci\_avi\_controller\]
Name \[name\] Name of the Avi Controller.
Fully qualified domain name \[fqdn\] Hostname of the Virtual Machine \(VM\).
IP address \[ip\_address\] IP address of the FQDN.
Avi Service Engine \[cmdb\_ci\_avi\_service\_engine\]
Name \[name\] Name of the Avi Service Engine.
IP address \[ip\_address\] IP address of the Avi Service Engine.
Version \[version\] Version of the Avi Service Engine.
Object ID \[object\_id\] Unique identifier of the Avi Service Engine.
Avi Controller Cluster \[cmdb\_ci\_avi\_controller\_cluster\]
Cluster ID \[cluster\_id\] Unique identifier of the Avi Controller Cluster.
Name \[name\] Name of the Avi Controller Cluster.
IP address \[ip\_address\] IP address of the Avi Controller Cluster host.
Load Balancer Pool \[cmdb\_ci\_lb\_pool\]
Name \[name\] Name of the Load Balancer Pool.
Server ID \[server\_id\] Unique identifier of the Load Balancer Pool.
Load Balancing Method \[load\_balancing\_method\] Method that Avi Vantage uses to make its load balancing decision. The pattern translates the algorithms as follows:- "LB\_ALGORITHM\_LEAST\_CONNECTIONS": "least-connections" - "LB\_ALGORITHM\_ROUND\_ROBIN": "round-robin" - "LB\_ALGORITHM\_FASTEST\_RESPONSE": "fastest-response" - "LB\_ALGORITHM\_CONSISTENT\_HASH": "consistent-hash" - "LB\_ALGORITHM\_LEAST\_LOAD": "least-load" - "LB\_ALGORITHM\_FEWEST\_SERVERS": "fewest-servers" - "LB\_ALGORITHM\_RANDOM": "random" - "LB\_ALGORITHM\_FEWEST\_TASKS": "fewest-tasks" - "LB\_ALGORITHM\_NEAREST\_SERVER": "nearest-server"
Load Balancer Pool Member \[cmdb\_ci\_lb\_pool\_member\]
Name \[name\] Name of the Pool Member @ name of the Pool.
IP address \[ip\_address\] IP address of the Pool Member host.
Load Balancer Service \[cmdb\_ci\_lb\_service\]
Name \[name\] Name of the Virtual IP \(VIP\).
IP address \[ip\_address\] IP address of the VIP.
Object ID \[object\_id\] Unique identifier of the VIP.
Port \[port\] Port of the host VM.
Avi Tenant \[cmdb\_ci\_avi\_tenant\]
name Name of the Tenant​.
object\_id The object\_id of the Tenant​.
tenant\_url URL to the Tenant​.
The Dependency Views map shows discovered load balancer CIs and the relationships between them. \[Omitted image "avi-lb-dependency-views-map1.png"\] Alt text: CIs and connections on a Dependency Views map. The following image shows the results of top-down discovery using the Avi Load Balancer VIP pattern. \[Omitted image "avi-lb-top-down-discovery.png"\] Alt text: This image shows top-down discovery using the Avi Load Balancer VIP pattern. ## CI relationships These relationships are created to support Avi Load Balancer discovery: |CI|Relationship|CI| |---|------------|---| |Avi Controller Cluster \[cmdb\_ci\_avi\_controller\_cluster\]|Cluster of::Cluster|Avi Controller \[cmdb\_ci\_avi\_controller\]| |Avi Tenant \[cmdb\_ci\_avi\_tenant​\]|Hosted on::Hosts|Avi Controller Cluster \[cmdb\_ci\_avi\_controller\_cluster\]| |Contains::Contained by|Load Balancer Service \[cmdb\_ci\_lb\_service\]| |Load Balancer Pool \[cmdb\_ci\_lb\_pool\]|Used by::Uses|Load Balancer Service \[cmdb\_ci\_lb\_service\]| |Hosted on::Hosts|Avi Controller Cluster \[cmdb\_ci\_avi\_controller\_cluster\]| |Owns::Owned by|Load Balancer Pool Member \[cmdb\_ci\_lb\_pool\_member\]| |Avi Service Engine \[cmdb\_ci\_avi\_service\_engine\]|Hosted on::Hosts|Avi Controller Cluster \[cmdb\_ci\_avi\_controller\_cluster\]| |Avi Controller \[cmdb\_ci\_avi\_controller\]|Contains::Contained by|Avi Service Engine \[cmdb\_ci\_avi\_service\_engine\]| |Load Balancer Service \[cmdb\_ci\_lb\_service\]|Used by::Uses|Avi Service Engine \[cmdb\_ci\_avi\_service\_engine\]| |Runs on::Runs|Avi Controller Cluster \[cmdb\_ci\_avi\_controller\_cluster\]| |Load Balancer Pool Member \[cmdb\_ci\_lb\_pool\_member\]|Reference only|Avi Controller Cluster \[cmdb\_ci\_avi\_controller\_cluster\]| ## Troubleshooting If Avi load balancer top-down discovery fails, see KB article [KB0824019](https://support.servicenow.com/kb_view.do?sysparm_article=KB0824019) for a workaround. If the mapping process does not proceed as you expected, follow the following suggestions.
Symptom Cause Solution
Discovery fails. The discovery message contains the information about an error caused by the REST timeout. There are many CIs sending the REST call response in the deployment. The MID Server cannot process the REST call response without exceeding the time limit controlled by the **mid.sa.cloud.request\_timeout** parameter. By default, the **mid.sa.cloud.request\_timeout** parameter is set to 30000 milliseconds. Increase the value of this parameter on the relevant MID Server and run discovery again. **Note:** If the **Configuration Parameters** related list for the relevant MID Server does not show this parameter, you may need to add it.
Pattern Designer fails during a debug session. The Pattern Designer message contains information about an error caused by a timeout. The Pattern Designer fails because of a timeout during pattern debugging \(and not during discovery\). By default, the **sa.debugger.max\_timeout**parameter is set to 240 seconds.Increase the value of this parameter on the relevant MID Server.
**Parent Topic:**[Available on-premise discovery patterns](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery-and-service-mapping-patterns/available-patterns.md)