Analysis on IPv6 deployment difficulties of H3C Routers

With the use of IPv4, IPv6 has started to come into our lives. At present, most infrastructures support IPv6, but IPv6 migration is not only a simple reconfiguration of devices from IPv4 to Ipv6, this is a system project. Let's take the H3C router as an example.

1. Most applications do not care about the network protocol (IP) of the underlying network, but some do not. For example, they use Session Initiation Initialization Protocol (SIP) for instant services. The SIP creator caused a serious error and encapsulated the IP address information into the SIP packet header. Manufacturers and SIP application developers must reset their applications to support IPv6 information in the SIP header.

2. Multi-line is a standard practice of most enterprises. the hierarchical structure of IPv6 address design is to simplify the route table by summarizing routes to aggregate routes. IPv6 designers do not consider the demand for private addresses or multiple leased lines, but enterprises want to be secure and elastic. To create a multi-line or v6 address translation policy, you must closely contact your service provider to have your own IPv6 address space.

3. Most vrouters and vswitches support IPv6, but these network devices have different forwarding methods. A high-capacity core router processes data packets on its dedicated hardware (such as a dedicated integrated circuit or network processor) to accelerate IPv4 forwarding. However, the hardware architecture usually does not support IPv6. this means that the router processes IPv6 data packets on a general-purpose processor, which leads to slow forwarding and low capacity.

4. IPv6 support is still very limited, especially for services such as MPLS and home Internet. Therefore, families or remote staff using FiOS cannot use IPv6 services without tunneling protocols. Many home routers do not support IPv6. many Internet architects worry that CGN has broken the end-to-end Internet mode. This means that carriers can allow them not to penetrate NAT to restrict unnecessary services.

In any case, CGN may be the only feasible solution to solve the interconnection problem between IPv4 and IPv6, as well as to minimize IPv4 and IPv6 route propagation, so as to reduce the Resource load of the carrier's border router.

5. The network is composed not only of routers, switches, and computers. WAN optimization and management platform, supply and change management procedures, sensors, M2M devices, management tools, and IT products must be considered when purchasing. IT engineers must analyze whether they support IPv6 to plan upgrades or gateway policies to ensure that existing applications and devices can coexist in a IPv4-IPv6 hybrid network.

The above are the several aspects we need to note when deploying IPv6. Only by solving all these problems can we build a stable and running network, the most important thing is whether the router used supports IPv6.