FAQ ADCv3 Migration (Commercial) Description: ServiceNow is updating their load balancing system from ADCv2 to ADCv3 (Application Delivery Controller version 3). This upgrade will provide more resilient load balancing that will increase scalability and stability. This upgrade also includes improvements to monitoring and metrics collections. FAQs: When will the updates take place?Updates were first rolled out internal to ServiceNow in Q3 of 2023. Customers have been moving to ADCv3 since Q4 of 2023. This activity will continue through July 2024. What is the benefit of ADCv3?This activity moves customers to new hardware and introduces improvements to the monitoring system, the container and server software (NGINX), metrics collection systems, and orchestration pipelines. The update improves resiliency, efficiency, scaling, and operability over ADCv2. How is ADCv3 implemented?Instances will be migrated via Instance Automation from the old ADC Stack to the new ADC Stack (without a change in IP addresses). This is done on a VIP Cluster basis; the automation does not support splitting out or selecting individual instances for migration. The instance location will not change. What testing has ServiceNow done for this migration?ServiceNow has done thorough testing in ServiceNow labs. ServiceNow internal instances have been running on ADCv3 since October 2023. As noted, thousands of customers have been moved since Q4 of last year and have been running on ADCv3 in production. Will the Customer Instance IP address or hosting location change? No. There will be no change to any customer configuration parameters or hosted location during or after the migration. How will I know when my instances are being migrated?The update will be transparent so you will not notice when the update is in progress. We expect the migrations to be completed by end of July 2024. Can I opt out of the update?All instances will need to be migrated as part of this effort. There is no opt-out option. Do all my instances have to be migrated at once?Yes. ServiceNow will will migrate all of you sub-production and production instances. This is to maintain consistency for troubleshooting and testing across all environments. What preparation needs to be done prior to the migration?Pre-flight checks will be run by ServiceNow prior to the migration. Any instance still on deprecated MultiSSOv1 must be upgraded to MultiSSOv2 or it will be skipped by automation during the update to ADCv3. Please see KB1710888 for more information. Also, if the preflight automation observes a configuration anomaly or error, it will automatically stop the update and leave instances on ADCv2. Should any activities be avoided during this migration?Activities can be planned and carried out as normal. What will happen to any scheduled updates?ServiceNow is using conflict detection to ensure that this update does not interfere with your scheduled activities. Any updates in progress will cause our automation to skip your instance and will retry at a later time. Will there be any downtime?We do not anticipate there being downtime with the change from ADCv2 to ADCv3. Customers who have an open session during the migration may experience a slight pause as the session refreshes to use the new load balancers. Data will not be lost as part of this session refresh. Is there a way to rollback?Yes. During the update, the automation will automatically roll back to ADCv2 if any anomalies are encountered. In addition, ServiceNow Cloud Network Services engineers will be monitoring all migrations in real time. How can I check to see if I have been migrated and am running on ADCv3?To verify the ADC version you are running on go to: https://<instance>.service-now.com/adc/version. If you see a login page you have not been upgraded. If the page shows ADCv3 in a one line sentence your instance is running on ADCv3.NOTE: if you are accessing via a regulated environment, please reachout to ServiceNow support and reference this KB. The support team will be able to provide the relevant link.