How to start an IPv6 Pilot – kind of puzzling question, because everything we know about Networking must be enabled with IPv6. You can start from any side, but some sides are less steep and can let you walk up step by step instead of climbing overhanging walls.
Let’s look at deployment scenarios first. For majority of organizations, it would be one of the two following choices:
- Start on external perimeter (public DMZ) and expand to the inside.
- Start on internal core network and expand to the outside.
I believe that IPv6 pilot on external test DMZ is the most efficient way to learn IPv6, as with minimum investments the organization can obtain the wealth of knowledge.
What is needed for that?
- Obtain public IPv6 space (if you didn’t do it already).
- Confirm with your internet provider that they have IPv6 support. Ask to activate it for you at your test site.
- Create new DMZ segment dedicated to IPv6 pilot.
- Create new (virtual) servers as web front-end.
- Think about DNS. Do not create AAAA records for your public names; instead, use temporary names created for test purposes only.
Sounds simple? Yes it is. By now your test servers are live and reachable from internet. However that was not the pilot yet; just preparations. We need to think a level deeper.
- Check if you have decent IP Address Management tool to keep track of IPv6 allocations. Check if it is integrated with DNS. IPv6 addresses are so long that you don’t want to do them manually. As must as possible must be automated.
- If you don’t have the proper IP address allocation strategy company-wide, this is the time to create it. IPv6 is a greenfield deployment after all. Come up with best IP summarization policy that you can think of.
- Check how many ISP attachments you have, also on different continents. Although PI address ranges are not supposed to be bound to a particular region, you will still need to obtain PI IPv6 ranges in all regions.
- Check if your monitoring systems – for Network and for Servers – can operate via IPv6 and provide you all required reporting about IPv6.
- Check what ISP redundancy do you currently have. If it does not use BGP but relies on NAT, you may have a trouble. IPv6 ISP resiliency requires BGP.
- Check if your IPv6-enabled front-end can talk to IPv4 back-end servers and databases.
- Check if your public front-end servers would usually be reachable via Load Balancers. If so, assess LB capabilities and consider including them in IPv6 pilot setup.
- Enable both v4 and v6 for your test servers and evaluate the fail-over time from one protocol family to another.
- Assess the IPv6 security policy on your firewalls. Number of protocols have changed from v4 to v6; the expanded scope of ICMPv6 is the example.
- Assess first hop security on your test server segment. Create the model for the future deployment.
With all these little things put together, this pilot will give a good feeling of IPv6.
Alex Mavrin, CCIE #7846
Visit http://www.apteriks.com and use FREE ONLINE tools for network professionals.