Anycast migration
If you are running the Service Point v3 instances in an Anycast environment, you can provision new Service Point v4 instances and configure Anycast service on the Service Point v4 instances. Once that has been configured, you can add the Service Point v4 instances to the Anycast pool and deploy the DNS resolver service to use the Anycast IP address of the Service Point v4 instance. Once you have provisioned the required Service Point v4 instances that will replace the Service Point v3 instances, test them to ensure that they are configured correctly. You can then decommission the Service Point v3 instances in the Edge Cloud UI and delete the Service Point v3 VMs. With this approach, DNS clients would not experience any downtime.
IP address swap migration on vCenter and ESXi
For Service Point v3 instances that are configured on vCenter and ESXi, and are not part of an Anycast environment, you can perform an IP address swap where the provisioned Service Point v4 instance takes over the IP address of the Service Point v3 instance. To perform the IP address swap, provision the Service Point v4 instance using a temporary IP address and deploy the DNS resolver service to the Service Point v4 instance using the same site configuration as the Service Point v3 instance. Once you have tested the Service Point v4 instance to ensure that it is configured correctly, you can then decommission the Service Point v3 instance in the Edge Cloud UI and delete the Service Point v3 VM. Once you have removed the Service Point v3 instance, reconfigure the IP address on the Service Point v4 instance to match that of the Service Point v3 instance that was deleted.
Once you have decommissioned the Service Point v3 instance and deleted the Service Point v3 VM, reconfigure the IP address on the Service Point v4 instance. For more information, refer to Updating Service Point v4 configurations when provisioned on VMware ESXi, Nutanix, and BlueCat hardware appliances.
While the platform services restart, the Service Point v4 instance will be in an Unhealthy state for a few minutes. During this time, DNS clients will experience a brief downtime.
IP address swap migration on Azure
For Service Point v3 instances that are configured on Azure, you can perform an IP address swap where the provisioned Service Point v4 instance takes over the IP address of the Service Point v3 instance. To perform the IP address swap, provision the Service Point v4 instance using a temporary IP address and deploy the DNS resolver service to the Service Point v4 instance using the same site configuration as the Service Point v3 instance. Once you have tested the Service Point v4 instance to ensure that it is configured correctly, you can then decommission the Service Point v3 instance in the Edge Cloud UI and delete the Service Point v3 VM. Once you have removed the Service Point v3 instance, reconfigure the IP address on the Service Point v4 instance to match that of the Service Point v3 instance that was deleted.
Once you have decommissioned the Service Point v3 instance and deleted the Service Point v3 VM, reconfigure the IP address on the Service Point v4 instance. For more information, refer to Updating Service Point v4 configurations when provisioned on Azure.
The Service Point v4 instance takes at least 5 minutes to reboot on Azure and services take an additional two minutes to restart after the reboot has completed. While the platform services restart, the Service Point v4 instance will be in an Unhealthy state for a few minutes. During this time, DNS clients will experience a brief downtime.
SMBus base address unitialized - upgrade BIOS or use force_addr=0xaddr
This
is expected behaviour and does not indicate that an error has occurred during the
reboot process.Migrating Service Point v3 instances on AWS and GCP
Due to limitations with the Cloud provider, you cannot modify the private IP address of the Service Point v4 instance on AWS and GCP. If you have Service Point v3 instances deployed to AWS or GCP, you must first decommission the Service Point v3 instance in the Edge Cloud UI and delete the Service Point v3 VM. Once you have removed the Service Point v3 instance, provision a new Service Point v4 VM on your AWS or GCP environment with the IP address reclaimed from the Service Point v3 VM, and deploy DNS resolver service to the Service Point v4 VM using the same site configuration as the Service Point v3 VM. With this approach, DNS clients would experience a brief downtime during the Service Point v4 instance provisioning and DNS resolver service deployment process.