With deprecation of Load Balancer for IPv4, Load Balancer for IPv4 and IPv6 is the product replacing it. As with any product migration, there are bound to be questions on migration. This blog is to help with migration questions that you might have. In this introductory blog, I will talk about the new features which have been added in Load Balancer for IPv4 and IPv6, and touch upon the differences at a high level, which you would need to consider during migration
A few features were available in Load Balancer for IPv4, but not in Load Balancer for IPv6. To help customers with migration, a few important features have been added to Load Balancer for IPv6 in 8.5.5. These are :
1. Network Address Translation
2. Colocation on AIX and Linux
3. Content Based Router
4. Site Selector
Network Address Translation (NAT)
This is similar to what is available in Load Balancer for IPv4 in most of the ways. This forwarding mechanism is used to balance servers in a subnet different from that of the Load Balancer. This is in addition to encapsulation, which can also be used in scenarios where the servers are in a different subnet. And in terms of performance, it is recommended to use encapsulation. This is because, in NAT, the reverse path is also through the load balancer, while in encapsulation, the reverse path goes directly to the client.
The difference is however in the level at which NAT is enabled. In Load Balancer for IPv4, NAT is enabled at port level, while in Load Balancer for IPv6, it is available at server level. This will enable a more granular level control in the forwarding mechanism.
Also, Network Address Port Translation (NAPT), in Load Balancer for IPv6, is implemented leveraging the port translation feature which is available by default in the OS. The port translation is configured in the backend servers using OS features like iptables (on Linux), netsh (n Windows), ipfilter (on AIX, HP-UX, Solaris).
Colocation on AIX & Linux
Colocation is available on Load Balancer for IPv6 on AIX and Linux platform. Even in Load Balancer for IPv4, Colocation was not implemented in Windows, and this continues. The functionality in Load Balancer for IPv6 is similar to its predecessor. However, extreme caution needs to be exercised when implementing this feature in production environment, since this can affect the performance.
Content Based Router
This feature is similar to what it is in Load Balancer for IPv4. However SNMP and Remote administration is not available. This is because, today, there are advanced third party tools which are available for SNMP, and Remote administration comes by default with OS. Caching Proxy is a prerequisite product for this feature.
This feature is similar to what is available in Load Balancer for IPv4. Again, Remote Administration is not available, and use of the Remote Administration feature which comes with the OS is recommended.
Load Balancer for IPv6 performs the best on Linux, followed by AIIX and then Windows. Before migration, it is recommended that you evaluate the performance as well
In all the commands, Load Balancer for IPv4 has : as the delimiter, but Load Balancer for IPv6 has @ as the delimiter. This is because Load Balancer for IPv6 supports IPv6, where the IP address is delimited by :
Got more questions on migration? Post it here.....