How to resolve Cisco routing protocol conflicts?

With the deployment of IPV6, more and more companies and organizations are starting to use IPV6 as the main access line, which brings about a troublesome problem of conflict, the old network protocols and new network protocols will inevitably conflict, especially the IPV6 migration to DNS processing trouble, Here is an analysis of this problem.

The two-protocol stack model, which is the most feasible application mode, is compared with the tunnel and the conversion mode.

The reason is that deployment is the simplest and provides the broadest possible compatibility for terminal devices, and as a system engineering, it takes a long time for all real-world devices to migrate from current Internet standards to IPV6 's work. Want to implement large-scale operations from the IPV4 protocol to the IPV6 protocol. The progress of this process will be very slow and will take a few years. During this time, all users must be confronted with the need to support the operation of both protocols in some way.

Second, or in the current more popular cloud computing, to a large extent also need to rely on IP address to a large number of computing, storage and network resources to consolidate and connect, they also need to provide customers with DNS and other public services.

As a result, they set up a complex system based on scripting and management frameworks to oversee the automation and remote control projects necessary to deliver services, for cloud service providers, it is not only necessary to ensure that external services can support both versions, but also to ensure that internal systems, frameworks, and control functions must be compatible with this requirement.

Third, for cloud computing providers, especially those using software as a service model, it may be less difficult to work than the infrastructure that is the service class.

The reason is that the infrastructure, the service provider, needs to handle both the client configuration and its own virtual mirroring control, in which case many problems may depend on the IPV4 protocol rather than the IPV6 protocol, and vice versa.

For applications or other types of services, the IP address is often used to identify all integration services from outside or third parties. And, typically, these applications are controlled by the end user rather than by the vendor, which does not mean that the software, the service provider, can rest assured.

All applications deployed to the cloud computing environment need to be integrated into the enterprise data center, and vice versa, which means that the use of different IP versions to provide security or integration functionality can lead to incompatibilities or make the migration process impossible to complete.

The fact that such a large migration involves countless different variables means that we will face untold challenges; So it's definitely not a simple job that can be done with a flip switch.

Therefore, prior to the decision to migrate, the relevant parties must cooperate fully and carefully planned to ensure that the specific work can be carried out gradually without large-scale downtime.

Due to the fact that most of the basic equipment has already included the two-protocol stack, the related requirements can be fully satisfied. However, even if the two-protocol stack is running, it does not mean that the network and application-oriented services can be integrated into one another, and from the actual process of connecting the site, this work is much more complicated than it looks.

DNS servers need to be queried, packets need to be able to pass through routing, TCP sessions need to be initiated, and packets need to be exchanged at all times.

For the data center where the website is located, even the simplest work in response to the ICMP Echo request query requires the interaction of many components including software and hardware, since the two-protocol stack is not necessarily able to be included in the services compatible with the IPV6 protocol.

You can imagine, in this case, if a IPV4 terminal queries the Web site IP address, the DNS server must respond, for the DNS server, how to confirm the use of the correct version of the Protocol to respond to it?

When we migrate from the current version to the new version, the application environment needs to support both versions, which means that the Internet infrastructure must do the same, which makes the actual work much more complicated than it initially looks.