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 hardware load balancers as network devices 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 patternsStarting with the Jakarta release, Discovery uses out-of-box patterns to find some types load balancers for new instances (see table). Load balancer Pattern names and description CI table populated For more information A10 A10 LoadBalancer A10 Load Balancer [cmdb_ci_lb_a10] Load Balancer: A10 ACE 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] Load balancer: F5 BIG-IP NetScaler Netscaler Load Balancer Citrix NetScalers [cmdb_ci_lb_netscaler] Load balancer: Citrix Netscaler Radware - AppDirector AppDirector Load Balancer Radware Load Balancer [cmdb_ci_lb_radware] 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. Load Balancer: A10Discovery identifies and classifies information about A10 load balancers.Apache mod_jk and mod_proxy discoveryDiscovery uses SSH to find Apache connectors mod_jk and mod_proxy.Load balancer: Citrix NetscalerDiscovery of Citrix Netscaler load balancers is performed by SNMP.Load balancer: F5 BIG-IPDiscovery of F5 BIG-IP load balancers is performed via SNMP.Load balancer: HAProxyDiscovery of HAProxy load balancers is performed by SSH.Load balancer: NGINXDiscovery of NGINX load balancers is performed by SSH.Load balancer: Cisco GSSDiscovery of Cisco GSS load balancers is performed by both SNMP and SSH.Load balancer: Cisco CSSDiscovery of Cisco CSS load balancers is performed by SNMP.Load balancer fields and probesDiscovery stores load balancer information in several tables.