Page tree
Skip to end of metadata
Go to start of metadata

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. 

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

Corrected in
DRDC1-16527Netscaler load balancer pattern Updated to use HTTPS REST API requestTKU-2021-Apr-1
DRDC1-16366Added dns_names attribute to LoadBalancerServiceTKU-2021-Mar-1
DRDC1-16365Updated to request configuration objects through all pages in API callsTKU-2021-Mar-1
DRDC1-16192Updated approach to create LB Members by rport defined in LB ServiceTKU-2021-Feb-1
DRDC1-15605Updated Nginx_LoadBalancer to support latest NginxFunctions.findIpPort() function.TKU-2020-Dec-1
DRDC1-15400Improved performance for Common_LoadBalancer.LBServiceToPoolMember and Common_LoadBalancer.PoolMemberToHostTKU-2020-Oct-1
DRDC1-14435Updated regexes to process upstream configuration blockTKU-2020-Feb-1
DRDC1-14359Updated key for Microsoft Network LoadBalancer ClusterTKU-2020-Feb-1
DRDC1-13725Problem: Load balancer linking can incorrectly link SIs that are only listening on localhost.
Solution: Code fix.

Problem: Radware Load Balancer Discovery Incomplete

Resolution: Code Fix.

Problem: No relationship between physical and virtual Citrix Load Balancer

Resolution: Code Fix.


Problem: Nginx pattern config file parcing update

Resolution: Code Fix.
TKU 2018-May-1


Problem: Request to remove TKU Pattern Dependencies.

Resolution: Code Fix.
TKU 2018-May-1

Problem: Load Balancer pool is getting created with incorrect name causing linking issues with Load balancer Service.

Resolution: Code Fix.

TKU 2018-Apr-1

Problem: Enhancement request for Microsoft_NLB.

Resolution: Code Fix.

TKU 2018-Apr-1

Problem: A10 Networks Load Balancer pattern does not supoprt A10 Thunder series devices.

Resolution: Code Fix.
TKU 2015-Apr-1

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 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: 

  • Load Balancer Group
  • Load Balancer Instance
  • Load Balancer Service
  • Load Balancer Pool
  • Load Balancer Member

Supported Load Balancers

The latest Technology Knowledge enables BMC Atrium Discovery discover and model the following load balancers: