BMC Atrium Discovery can now 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.
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.
|DRDC1-16366||Added dns_names attribute to LoadBalancerService||TKU-2021-Mar-1|
|DRDC1-16365||Updated to request configuration objects through all pages in API calls||TKU-2021-Mar-1|
|DRDC1-16192||Updated approach to create LB Members by rport defined in LB Service||TKU-2021-Feb-1|
|DRDC1-15605||Updated Nginx_LoadBalancer to support latest NginxFunctions.findIpPort() function.||TKU-2020-Dec-1|
|DRDC1-15400||Improved performance for Common_LoadBalancer.LBServiceToPoolMember and Common_LoadBalancer.PoolMemberToHost||TKU-2020-Oct-1|
|DRDC1-14435||Updated regexes to process upstream configuration block||TKU-2020-Feb-1|
|DRDC1-14359||Updated key for Microsoft Network LoadBalancer Cluster||TKU-2020-Feb-1|
|DRDC1-13725||Problem: Load balancer linking can incorrectly link SIs that are only listening on localhost.|
Solution: Code fix.
Problem: Radware Load Balancer Discovery IncompleteResolution: Code Fix.
Problem: No relationship between physical and virtual Citrix Load BalancerResolution: Code Fix.
Problem: Nginx pattern config file parcing updateResolution: Code Fix.
Problem: Request to remove TKU Pattern Dependencies.Resolution: Code Fix.
Problem: Load Balancer pool is getting created with incorrect name causing linking issues with Load balancer Service.
Resolution: Code Fix.
Problem: Enhancement request for Microsoft_NLB.
Resolution: Code Fix.
Problem: A10 Networks Load Balancer pattern does not supoprt A10 Thunder series devices.Resolution: Code Fix.
Problem: F5 GTM load-balancing is not supported.Resolution: Code Fix.
Load balancer information is discovered using SNMP. When BMC Atrium 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:
The latest Technology Knowledge enables BMC Atrium Discovery discover and model the following load balancers: