Load balancer discovery
Discovery can collect data about network routers, switches, and applications.
Discovery supports data collection from the following applications and hardware:
- A10
- Apache mod_jk and Apache mod_proxy
- Big-IP F5 Traffic Manager
- Cisco
- Citrix NetScaler
- HAProxy
- NGINX
- Alteon
- ACE
- Radware
Important: Discovery treats load balancers as licensable entities and attempts to discover them primarily using SNMP. If a load balancer in your system, running on a Linux host, has SNMP and SSH ports open, Discovery might classify it based on the SSH port. This classification has priority over SNMP. To ensure that Discovery properly classifies your hardware load balancers, create a Discovery behavior for load balancers that includes SNMP but not SSH. Software load balancers are treated as applications.
Load balancer patterns
Starting with the Jakarta release, Discovery uses out-of-box patterns to find some types load balancers for new instances (see table).
Note: For information on Probe to Pattern migration see the knowledge article KB0694477.
| Load balancer | Pattern names and description | Main CI table populated |
|---|---|---|
| A10 | A10 LoadBalancer | A10 Load Balancer \[cmdb\_ci\_lb\_a10\] |
| ACE | ACE Load Balancer by SSH \(formerly ACE Load Balancer\) | ACE \[cmdb\_ci\_lb\_ace\] |
| Alteon | Alteon Load Balancer | Alteon \[cmdb\_ci\_lb\_alteon\] |
| F5 BIG-IP | F5 - HD, F5 Load Balancer | F5 BIG-IPs \[cmdb\_ci\_lb\_bigip\] |
| NetScaler | Netscaler Load Balancer | Citrix NetScalers \[cmdb\_ci\_lb\_netscaler\] |
| Radware - AppDirector | AppDirector Load Balancer | Radware Load Balancer \[cmdb\_ci\_lb\_radware\] |
| HAProxy load balancer discovery with patterns | HA Proxy | HAProxy Load Balancer \[cmdb\_ci\_lb\_haproxy\] |
To use patterns, verify that the correct pattern is specified in the horizontal pattern probe on the classifier. See Add the Horizontal Pattern probe to a classifier for instructions.
Load balancer discovery, Service Mapping, and customized CI fields
Discovery collects information about the install status and operational status of load balancers. If you are using Discovery with Service Mapping, do not customize the [operational_status] or [install_status] fields. By default, Service Mapping ignores all host CIs for which the value of the [operational_status] field is not 1 (Operational) or the value of the status [install_status] field is 100 (absent). For additional information, see Preparing customized ServiceNow deployments to work with Service Mapping [KB0647574] in the HI Knowledge Base.
- A10 load balancer discovery
Discovery and Service Mapping uses patterns to collect information about A10 load balancers. - Cisco ACE load balancer discovery
Discovery identifies and classifies information about ACE load balancers. - Cisco GSS load balancer discovery
Discovery of Cisco GSS load balancers is performed by both SNMP and SSH. - Cisco CSS load balancer
Discovery of Cisco CSS load balancers is performed by SNMP. - Citrix NetScaler load balancer discovery
Discovery and Service Mapping find Citrix NetScaler load balancers including Server Load Balancing (GSLB). - F5 BIG-IP load balancer discovery
Discovery and Service Mapping can find F5 BIG-IP load balancers via SNMP, SSH, and through the REST API. - HAProxy load balancer discovery using probes
Discovery of HAProxy Community edition load balancers is performed by SSH. - NGINX load balancer discovery
Discovery of NGINX load balancers is performed by SSH. - Radware Alteon load balancer discovery
Discovery identifies and classifies information about Alteon load balancers. - Radware-appDirector load balancer discovery
Discovery of Radware load balancers is performed by SNMP. - Load balancer fields and probes
Discovery stores load balancer information in several tables.
Parent Topic:Network device discovery