Implementing #IPv6 support requires more than just a change of address ….
F5 recently announced its Professional Services IPv6 Solution Offerings, designed to share our expertise in IPv6 implementation to enable organizations to realize a successful transition, but we’d also like to share some of the gotchas and lessons learned over the past few years during those implementations. Today we’re looking at the skills required to successfully transition to IPv6.
Transitioning from IPv4 to IPv6 isn’t as easy as merely learning how to subnet with longer IP addresses; there are a lot of interconnected data center skills and knowledge that must be applied to ensure you don’t miss a critical step in a transition.
While the exact services and infrastructure components impacted will vary based on which IPv6 model you’re implementing: Public Edge IPv6 Enablement, IPv6 Support for IPv4 Only Services, or Internal IPv6 Service / IPv6 NAT64 Offering. Luckily, there are common components and skills that will be necessary for any IPv6 transition plan.
- IPv6 as a Protocol
This might seem like a no-brainer, but it is at the heart of an IPv4 – IPv6 transition. The ability to configure and troubleshoot IPv6 connectivity is just the beginning; also important is the ability to apply that knowledge to connectivity between various network objects such as routers, switches, and firewalls, especially if your strategy is co-existence.
Acquire IPv6 address space from ISP/Arin then complete and test advertisement configuration of IPv6 address space for all ISPs.
Often overlooked, DNS is a critical component to an IPv6 migration. DNS has several new resource types specifically to support IPv6 enabled resources. You’ll need to identify the current authoritative DNS servers involved with the domains and/or applications that will be accessible via IPv6.
Latest F5 Information