{"id":4956,"date":"2020-03-25T08:48:32","date_gmt":"2020-03-25T15:48:32","guid":{"rendered":"https:\/\/blogs.infoblox.com\/?p=4956"},"modified":"2020-05-06T10:26:50","modified_gmt":"2020-05-06T17:26:50","slug":"bridging-the-dtc-gap-dynamic-ratio-implementation-for-dtc-pools","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/community\/bridging-the-dtc-gap-dynamic-ratio-implementation-for-dtc-pools\/","title":{"rendered":"Bridging the DTC Gap – Dynamic ratio implementation for DTC pools"},"content":{"rendered":"

Introduction<\/strong><\/h3>\n

Infoblox DNS Traffic Control (DTC) integrates GSLB functionality with core DDI network services. Highly automated, it provides the performance, scalability, and availability that organizations require. DTC load balances DNS traffic based on client location, server location, and server availability. It monitors various parameters to ensure the client request is successfully served by a healthy server.<\/p>\n

This blog post talks about implementing a functionality responsible for dynamically modifying pool ratios at the LBDN level based on specific parameters.<\/p>\n

Dynamic Ratios for DTC Pools<\/strong><\/h3>\n

Infoblox DTC supports dynamic ratio as the load balancing method at the pool level which balances the DNS traffic on the server as per the server health.<\/p>\n

This blog describes a solution that aims at dynamically changing the DTC pool ratios based on parameters that can be polled using SNMP such as CPU Utilization, NIC Usage, Memory, RAM, etc. Please note that the current version of the project focusses on CPU Utilization.<\/p>\n

The solution takes the parameter threshold as an input. The DTC servers are polled for their current CPU Utilization and consolidated at the DTC pool level. Once the threshold is reached, the algorithm calculates the optimum configuration according to the current utilization metrics and modifies the ratios accordingly.<\/p>\n

Workflow<\/strong><\/h3>\n

\"\"<\/p>\n

 <\/p>\n

    \n
  1. User logs in with the Grid Master\u2019s IP Address, username, and password<\/li>\n
  2. After authentication, a list of all LBDNs is displayed with information about authoritative zones, patterns, load-balancing methods, and pools. This solution is only applicable for LBDNs with the load-balancing method as \u2018RATIO\u2019. Hence the dropdown does not include the LBDNs with a load-balancing method other than \u2018RATIO\u2019.
    \n\"\"<\/li>\n
  3. Post LBDN selection, details of all the pools present in the selected LBDN are displayed along with their current CPU Utilization and current ratios.The user is then asked to enter the CPU Utilization threshold value and is given an option to select the restart option for the grid. If it is unchecked, every time the ratio is modified, you would need to manually restart the services on the grid for the new configuration to take effect.
    \n\"\"<\/li>\n
  4. The solution starts monitoring the servers and starts consolidating the results at the pool level. Once the CPU threshold is reached, the algorithm calculates the optimum configuration according to the current utilization metrics and modifies the ratios dynamically. If the parameter values drop below the threshold, the pool ratios are reverted to the initial configuration and the monitoring continues.<\/li>\n<\/ol>\n

    Solution in Action<\/strong><\/h3>\n

    When the CPU Utilization is within the specified threshold:<\/p>\n

    \"\"<\/p>\n

    When the CPU Utilization crosses the specified threshold:<\/p>\n

    \"\"<\/p>\n

    Technology stack<\/strong><\/h3>\n

    The technology stack used for this solution:<\/p>\n