Supported Load Balancers
BMC Discovery can discover and model the load balancing instances and their configuration for certain NetworkDevice nodes that were previously displayed with a Type of Layer 3 Switch. You can discover dedicated hardware load balancers such as Application Delivery Controllers from F5 or Citrix (NetScaler), or the virtualized versions of these devices.
Release notes and notices
Load Balancers updates are delivered as a part of monthly Technology Knowledge Update. For more information, please, see the latest TKU and OS Upgrade documentation.
Known and corrected issues
ID | Details | Corrected in |
|---|---|---|
| DRDC1-26305 | Updated Nginx LB pattern to avoid bogus LB nodes name | TKU-2025-Jun-1 |
| DRDC1-26403 | Improved LB Service to Member linkage | TKU-2025-Jun-1 |
| DRDC1-26477 | Added unhashed_key attribute to Apache LoadBalancerService node | TKU-2025-Jun-1 |
DRDC1-16833 | REST API only discovery of the Citrix NetScaler loadbalancers | |
DRDC1-23301 | Improved host discovery of AVI Load Balancer | |
DRDC1-23690 | Improved Common_LoadBalancer pattern performance | |
DRDC1-23266 | Updated AVI LB pattern to better handle child/parent virtual service | |
DRDC1-22688 | Updated AVI LB pattern to support /api/vsvip API call | |
DRDC1-22812 | Improved Common_LoadBalancer pattern performance | |
DRDC1-22581 | Updated F5 LB pattern to avoid ECA Error | |
DRDC1-22455 | Updated active versioning for HAProxy pattern | |
DRDC1-21950 | Improved Common_LoadBalancer pattern performance | |
DRDC1-21751 | Use configured name for LoadBalancerPool/Member instead of resolved IP address | |
DRDC1-20860 | HAproxy pattern updated to skip sibling 'haproxy' process | |
DRDC1-20405 | Enhanced the AVI LB pattern. | |
DRDC1-19469 | Discover LB Services for Fortinet with REST API | |
DRDC1-19462 | Updated HAProxy pattern to parse host name in bind/server arguments | |
DRDC1-19405 | Fixed ECA Error | |
DRDC1-19034 | Fixed ECA Errors | |
DRDC1-18800 | MS NLB. Added stop option for hosts without DDD | |
DRDC1-18827 | F5. Updated regex to parse pool | |
DRDC1-17567 | LTM policy support for F5 loadbalancers | |
DRDC1-17348 | Fixed ECA Error | |
DRDC1-17292 | Updated approach to create LB Members by port defined in LB Service | |
DRDC1-16527 | Netscaler load balancer pattern Updated to use HTTPS REST API request | |
DRDC1-16366 | Added dns_names attribute to LoadBalancerService | |
DRDC1-16365 | Updated to request configuration objects through all pages in API calls | |
DRDC1-16192 | Updated approach to create LB Members by rport defined in LB Service | |
DRDC1-15605 | Updated Nginx_LoadBalancer to support latest NginxFunctions.findIpPort() function. | |
DRDC1-15400 | Improved performance for Common_LoadBalancer.LBServiceToPoolMember and Common_LoadBalancer.PoolMemberToHost | |
DRDC1-14435 | Updated regexes to process upstream configuration block | |
DRDC1-14359 | Updated key for Microsoft Network LoadBalancer Cluster | |
DRDC1-13725 | Problem: Load balancer linking can incorrectly link SIs that are only listening on localhost. | |
DRDC1-10007 | Problem: Radware Load Balancer Discovery Incomplete Resolution: Code Fix. | |
DRDC1-11897 | Problem: No relationship between physical and virtual Citrix Load Balancer Resolution: Code Fix. | |
DRDC1-11283 | Problem: Nginx pattern config file parcing update Resolution: Code Fix. | TKU 2018-May-1 |
DRDC1-11296 | Problem: Request to remove TKU Pattern Dependencies. Resolution: Code Fix. | TKU 2018-May-1 |
DRDC1-11024 | Problem: Load Balancer pool is getting created with incorrect name causing linking issues with Load balancer Service. Resolution: Code Fix. | TKU 2018-Apr-1 |
DRDC1-10995 | Problem: Enhancement request for Microsoft_NLB. Resolution: Code Fix. | TKU 2018-Apr-1 |
TKU-3888 | Problem: A10 Networks Load Balancer pattern does not supoprt A10 Thunder series devices. Resolution: Code Fix. | |
QM001875570 | Problem: F5 GTM load-balancing is not supported. Resolution: Code Fix. | TKU 2015-May-1 |
Load Balancer Discovery
Load balancer information is discovered using SNMP. When BMC Discovery finds a hardware or virtualized Application Delivery Controller (ADC) that has load balancer options enabled, it creates a network device node and triggers the load balancer discovery TPL patterns to query the necessary information about the related load balancing components, including pools, hosts and services. As soon as these elements are discovered, the following nodes (with relationships) are modeled, where applicable:
- Load Balancer Group
- Load Balancer Instance
- Load Balancer Service
- Load Balancer Pool
- Load Balancer Member
Supported Load Balancers
The latest Technology Knowledge enables BMC Discovery discover and model the following load balancers: