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). Warning: DO NOT switch from probes to patterns if you are already running Discovery with probes, and your CMDB is already populated. If you do so, it is possible that the pattern Discovery process does not synchronize on the same values that the probe Discovery process does. This could result in duplicate CIs in your CMDB. 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] 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.