upgrade instructions_global traffic management 3.0 - Alibaba Cloud DNS

Overview

To simplify configuration, the new version elevates instance-level configurations to user-level configurations. IPAM pools and health checks are no longer bound to individual instances but are configured globally and can be referenced by all GTM domain instances. Health checks also support template configurations with built-in system templates for out-of-the-box use.

Release content

Type	Content
Configuration	Visual editor mode: Provides graphical orchestration capabilities for more intuitive GTM configuration and monitoring.
Scheduling	Support for health detection templates: Determines service endpoint health through multiple protocols for precise service availability monitoring. Extended load balancing policy: Supports flexible combinations of load balancing policies to adapt to complex scheduling scenarios. Multiple line type combinations: Combines ISP lines and regional lines for fine-grained scheduling in different network environments. Batch traffic shifting escape mechanism: Enables unified batch traffic shifting at the data center level or across multiple applications during failures to ensure business continuity.
Ultimate disaster recovery	Cloud/edge heterogeneous disaster recovery: Establishes a heterogeneous GTM disaster recovery plan between cloud and edge, providing local data and service backup for highly stable DNS resolution.
Operations	Global/custom alarm settings: All instances support unified global alarm configuration, while individual instances can use custom alarm settings. Status visualization: Displays GTM access domains, IPAM pools, address service availability, enabled status, and health detection status to help you quickly identify service issues.

Version comparison

	GTM Standard Edition	GTM Ultimate Edition	GTM 3.0 Standard Edition	GTM 3.0 Ultimate Edition
Network-wide failback time = fault switching time + network-wide effective time	With health check interval set to 1 minute, TTL to 60 seconds, and consecutive failure count to 2, GTM can accurately detect failures and switch in about 3 minutes. After fault switching, theoretically, it can take effect across the network in about 60 seconds, but the actual situation depends on the cache setting time of ISPs across the country.	With health check interval set to 15 seconds, TTL to 1 second, and consecutive failure count to 2, GTM can accurately detect failures and switch in about 1 minute. After fault switching, theoretically, it can take effect across the network in about 1 second, but the actual situation depends on the cache setting time of ISPs across the country.	With health check interval set to 1 minute, TTL to 60 seconds, and consecutive failure count to 2, GTM can accurately detect failures and switch in about 3 minutes. After fault switching, theoretically, it can take effect across the network in about 60 seconds, but the actual situation depends on the cache setting time of ISPs across the country.	With health check interval set to 15 seconds, TTL to 1 second, and consecutive failure count to 2, GTM can accurately detect failures and switch in about 1 minute. After fault switching, theoretically, it can take effect across the network in about 1 second, but the actual situation depends on the cache setting time of ISPs across the country.
Access policy type	Geographic location-based access policy	Geographic location-based access policy, access latency-based access policy	Source proximity (geographic location-based access policy), sequential, polling, weighted	Source proximity (geographic location-based access policy), sequential, polling, weighted
Access latency-based policy (supported address types)	Supported (IPv4)	Supported (IPv4)	N/A	N/A
Address Type	IPv4, IPv6, domain name	IPv4, IPv6, domain name	IPv4, IPv6, domain name	IPv4, IPv6, domain name
Health Check Interval	60 seconds	15 seconds, 60 seconds	60 seconds	15 seconds, 60 seconds
Load balancing policy between IPAM pools	Only primary/secondary policy	Only primary/secondary policy	Supports source proximity, sequential, polling, weighted scheduling policies	Supports source proximity, sequential, polling, weighted scheduling policies
Load balancing policy between addresses	Supports polling, weight ratio	Supports polling, weight ratio	Supports load balancing for application service IPs and IPAM pools	Supports load balancing for application service IPs and IPAM pools
Request lines	Supports mainland China by ISPs (China Unicom, China Telecom, China Mobile, Dr. Peng, Alibaba Cloud detailed to Region), by regions (North China, South China, East China, Northeast, Northwest, Southwest, Central China), and overseas by continent Note Also affected by the DNS instance version bound to the GTM access domain	Supports mainland China by ISPs (China Unicom, China Telecom, China Mobile, Dr. Peng, education network, radio and television network, Alibaba Cloud detailed to Region) and ISP-specific regions (to provinces and municipalities), by regions (North China, South China, East China, Northeast, Northwest, Southwest, Central China), overseas detailed to continents, countries (regions) Note Also affected by the DNS instance version bound to the GTM access domain	Supports mainland China by ISPs (China Unicom, China Telecom, China Mobile, Dr. Peng, education network, radio and television network, Alibaba Cloud detailed to Region) and ISP-specific regions (to provinces and municipalities), by regions (North China, South China, East China, Northeast, Northwest, Southwest, Central China), overseas detailed to continents, countries (regions). Not affected by DNS instance version	Supports mainland China by ISPs (China Unicom, China Telecom, China Mobile, Dr. Peng, education network, radio and television network, Alibaba Cloud detailed to Region) and ISP-specific regions (to provinces and municipalities), by regions (North China, South China, East China, Northeast, Northwest, Southwest, Central China), overseas detailed to continents, countries (regions). Not affected by DNS instance version
Region and ISP line combination configuration (ISP lines and region lines do not conflict)	Not supported	Not supported	Yes	Yes
Number of IPAM pools that can be created per instance	10 IPAM pools	20 IPAM pools	30 IPAM pools	50 IPAM pools
IP address limit in 1 IPAM pool	20 IPs & domain names	20 IPs & domain names	30 IPs & domain names	50 IPs & domain names
Minimum available address limit	1-200	1-200	Supports setting by percentage	Supports setting by percentage
Global TTL (minimum)	60 seconds Note Also affected by the DNS instance version bound to the GTM access domain	1 second Note Also affected by the DNS instance version bound to the GTM access domain	Supports customization, not affected by DNS instance version	Supports customization, not affected by DNS instance version
Number of health check monitoring nodes	Unlimited	Unlimited	Unlimited	Unlimited
Multiple detection template combination detection	Not supported	Not supported	Support	Support
Health check tasks (per month)	100	100	100	100
Text message alarm notification items	1000 text message notifications (monthly package)	2000 text message notifications (monthly package)	1000 text message notifications (monthly package)	2000 text message notifications (monthly package)
Alarm notification methods can be customized according to alarm event type	Support	Yes	Support	Support

How to upgrade from GTM to GTM 3.0

To use the new version, purchase and configure a GTM 3.0 instance, then update your DNS settings to point your subdomain to the CNAME access domain provided by the new GTM. For more information, see How to smoothly upgrade from the old version of GTM to GTM 3.0?

Pricing

GTM 3.0 uses the same purchase method and pricing as existing Global Traffic Management instances. Upgrading does not affect the cost of your current GTM instances. For pricing details, see Product Billing.

How to obtain

Global Traffic Management