{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":30200,"path":"it-operations-management/discovery-and-service-mapping-patterns/vmware-nsx-lb-discovery.md","title":"VMware NSX Advanced load balancer discovery","bundle":null,"doc_type":null,"release":"australia","body":"\n# VMware NSX Advanced load balancer discovery\n\nThe ServiceNow Discovery application uses the VMware NSX Advanced load balancer discovery pattern to find VMware NSX load balancers. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.\n\nThe pattern uses a set of REST APIs to find the load balancers. It is triggered by the NSX HTTP classifier that responds to the **HTTP - Classify** probe. For more information, see [HTTP device discovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/itom-visibility/http-discovery.md).\n\n**Note:** There are two patterns available. The legacy VMware NSX Load Balancer pattern is for the S series. The new VMware NSX-T Load Balancer pattern is for the T series. The functionality and collected information remain the same.\n\n## Request apps on the Store\n\nVisit 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).\n\n## Prerequisites\n\n- **Enable NSX Basic Authentication**\n\n In VMware NSX, enable NSX Basic Authentication.\n\n- **Verify that the applications are up to date**\n - CMDB CI Class Models\n - Visibility Content\n - Discovery and Service Mapping Patterns\n- **Configure basic authentication credentials**\n\n On the ServiceNow AI Platform, configure basic authentication credentials. The credentials must have the following API permissions:\n\n - NSX:\n - /api/4.0/edges\n - /api/4.0/edges/<edge\\_id>loadbalancer/config\n - NSX-T: /api/v1/edge-clusters\n For more information about basic authentication credentials, see [Basic authentication credentials](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/r_BasicAuthCredentialsForm.md).\n\n- **Verify HTTP discovery is triggered against the NSX Main Controller IP**\n\n The HTTP discovery is triggered only if SSH or SNMP discovery is unsuccessful.\n\n- **Create a discovery schedule**\n\n Create the discovery schedule for VMware NSX load balancer discovery or run a quick discovery on the IP address of the NSX Main Controller. For more information about running a quick discovery, see [Run a Quick Discovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/t_CreateADiscoverySchedule.md).\n\n\n## Data collected by Discovery for VMware NSX Advanced load balancer\n\nDiscovery populates the data in the CMDB when running the VMware NSX Advanced load balancer patterns.\n\n|Field|Description|\n|-----|-----------|\n|Name \\[name\\]|Edge name.|\n|Object ID \\[object\\_id\\]|Edge ID.|\n|IP Address \\[ip\\_address\\]|IP address of the NSX Main Controller.|\n|Operational status \\[operational\\_status\\]|Load balancer status: Active or inactive.|\n\n|Field|Description|\n|-----|-----------|\n|Name \\[name\\]|Virtual server name.|\n|IP Address \\[ip\\_address\\]|Virtual server IP address.|\n|Object ID \\[object\\_id\\]|Virtual server object ID.|\n|Port \\[port\\]|Virtual server port with which to communicate.|\n|Listener Protocol \\[listener\\_protocol\\]|Listener protocol. For example: HTTP, HTTPS.|\n\n|Field|Description|\n|-----|-----------|\n|Name \\[name\\]|Pool name.|\n|Object ID \\[object\\_id\\]|Pool object ID.|\n\n|Field|Description|\n|-----|-----------|\n|Name \\[name\\]|Pool member name.|\n|IP Address \\[ip\\_address\\]|Pool member IP address.|\n|Object ID \\[object\\_id\\]|Pool member object ID.|\n|Service port \\[service\\_port\\]|Pool member port with which to communicate.|\n\n|Field|Description|\n|-----|-----------|\n|Name \\[name\\]|Monitor name.|\n|Object ID \\[object\\_id\\]|Monitor object ID.|\n|Timeout in seconds \\[timeout\\_sec\\]|Time in seconds to wait for a response.|\n|Interval in seconds \\[check\\_interval\\_sec\\]|Interval in seconds after which the monitor sends the request again.|\n|Monitor type protocol \\[monitor\\_type\\]|Monitor type. For example: HTTP, HTTPS, TCP.|\n|Request path \\[request\\_path\\]|Path where the monitor sends the request.|\n|Max retries \\[max\\_retries\\]|The maximum number of times the resource is tested before it is declared \"Down\".|\n\nThe Dependency Views map shows all discovered load balancer CIs and the relationships between them.\n\n\\[Omitted image \"dependency-nsx.png\"\\] Alt text: CIs and connections on a Dependency Views map\n\n## CI relationships\n\nDiscovery creates these relationships to support the VMware NSX load balancer discovery.\n\n|CI|Relationship|CI|\n|---|------------|---|\n|Load Balancer Service \\[cmdb\\_ci\\_lb\\_service\\]|Runs on::Runs|NSX Load Balancer \\[cmdb\\_ci\\_nsx\\_lb\\]|\n|Load Balancer Service \\[cmdb\\_ci\\_lb\\_service\\]|Uses::Used by|Load Balancer Pool \\[cmdb\\_ci\\_lb\\_pool\\]|\n|Load Balancer Pool \\[cmdb\\_ci\\_lb\\_pool\\]|Hosted on::Hosts|NSX Load Balancer \\[cmdb\\_ci\\_nsx\\_lb\\]|\n|Load Balancer Pool \\[cmdb\\_ci\\_lb\\_pool\\]|Owns::Owned by|Load Balancer Pool Member \\[cmdb\\_ci\\_lb\\_pool\\_member\\]|\n|Cloud Load Balancer Health Service \\[cmdb\\_ci\\_lb\\_health\\_service\\]|Hosted on::Hosts|NSX Load Balancer \\[cmdb\\_ci\\_nsx\\_lb\\]|\n|Cloud Load Balancer Health Service \\[cmdb\\_ci\\_lb\\_health\\_service\\]|Used by::Uses|Load Balancer Pool \\[cmdb\\_ci\\_lb\\_pool\\]|\n\n## Troubleshooting\n\nIf the mapping process does not proceed as you expected, follow the following suggestions.\n\n\n
\n\nSymptom\n\n\n\nCause\n\n\n\nSolution\n\n
\n\nDiscovery fails. The discovery message contains the information about an error caused by the REST timeout.\n\n\n\nThere 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.\n\n\n\nBy 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.\n\n**Note:** If the **Configuration Parameters** related list for the relevant MID Server does not show this parameter, you may need to add it.\n\n
\n\nPattern Designer fails during a debug session. The Pattern Designer message contains information about an error caused by a timeout.\n\n\n\nThe Pattern Designer fails because of a timeout during pattern debugging \\(and not during discovery\\).\n\n\n\nBy default, the **sa.debugger.max\\_timeout**parameter is set to 240 seconds.Increase the value of this parameter on the relevant MID Server.\n\n
**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)\n\n"}}