There are many things that you will need to consider when you are thinking about implementing IPv6. It is obvious that one of the biggest challenges that you will face is training your staff. Your technical staff will need to be familiar with IPv6 long before you plan to make the change. While professional training would be best there are many online options out there for short term training, such as the one that is offered by North American Network Operators Group (NANOG) at http://www.nanog.org/meetings/nanog51/agenda. Training your staff will be one of the challenges that you will face, but it is only one of them. You also need to consider many other factors like checking to make sure that your programs are compatible with IPv6, design an addressing plan, enabling IPv6 for DNS. When the time comes to fully implement IPv6 you do not want to be faced with programs that will not work or spend the time trying to manager your IPv6 space my hand. This is when those IPv6 programs will come in handy that we talked about earlier. Most Ipv4 networks are running IPv4 because this you will need to have your network security team confirm that your NAT will not create problems, or determine if you are going to turn off NAT and use IPv6 over the entire network. IPv6 has a Feature called Unique Local Addresses or ULA which can replace NAT. If you plan to do away with NAT all together it is important that before you make the switch you create a good addressing plan. An addressing plan is a network map that will determine what and where your IPv6 address will be allocated. In order to create a good addressing plan you need to know how many IPv6 address that you will need. “Normally every SITE should have a /48 but very large sites with complex network topologies may need more space. You will need a /64 per LAN” (Es.net, 2014) If you used a /64 this would give your
There are many things that you will need to consider when you are thinking about implementing IPv6. It is obvious that one of the biggest challenges that you will face is training your staff. Your technical staff will need to be familiar with IPv6 long before you plan to make the change. While professional training would be best there are many online options out there for short term training, such as the one that is offered by North American Network Operators Group (NANOG) at http://www.nanog.org/meetings/nanog51/agenda. Training your staff will be one of the challenges that you will face, but it is only one of them. You also need to consider many other factors like checking to make sure that your programs are compatible with IPv6, design an addressing plan, enabling IPv6 for DNS. When the time comes to fully implement IPv6 you do not want to be faced with programs that will not work or spend the time trying to manager your IPv6 space my hand. This is when those IPv6 programs will come in handy that we talked about earlier. Most Ipv4 networks are running IPv4 because this you will need to have your network security team confirm that your NAT will not create problems, or determine if you are going to turn off NAT and use IPv6 over the entire network. IPv6 has a Feature called Unique Local Addresses or ULA which can replace NAT. If you plan to do away with NAT all together it is important that before you make the switch you create a good addressing plan. An addressing plan is a network map that will determine what and where your IPv6 address will be allocated. In order to create a good addressing plan you need to know how many IPv6 address that you will need. “Normally every SITE should have a /48 but very large sites with complex network topologies may need more space. You will need a /64 per LAN” (Es.net, 2014) If you used a /64 this would give your