Each Global Traffic Management property has a property mode (type) that determines its behavior. The following table describes each property type.
|Mirror Failover||Configure both a primary and a backup data center to support Mirror Failover. Global Traffic Management monitors the primary data center, and as long as it is up, GTM sends users there. If the primary data center goes down, GTM sends users to the backup data center.|
|Static Property||GTM returns pre-configured DNS records.
Static properties can manage only Static record sets. There are no traffic targets and no liveness tests. Therefore, Static properties are not necessary unless there are Static record sets.
|Map by geographic location||GTM returns a CNAME based on the location (country, or
country and state) of the requester.
Note: To configure this property type, define a geographic map.
|Map by AS (autonomous system) number||GTM returns a CNAME based on the AS number of the
requester. The Autonomous System Number (ASN) is a unique number
assigned to the autonomous system that identifies each network on the
Note: To configure this property type, you must define an AS map.
|Map by IP address (CIDR blocks)||GTM returns a CNAME answer based on the Classless
Inter-Domain Routing (CIDR) table entry for certain name servers and
clients. For example, internal corporate DNS servers receive one answer,
while all external resolvers receive another answer.
Note: To configure this property type, you must define a CIDR map.
|IP Version Selector||GTM provides answers for both A and AAAA queries. This
feature eases migration to IPv6. This property types lets you return
different answers depending on whether the query is for an IPv4 (A
record) or IPv6 (AAAA record) address.
You must have at least one IPv4 property and at least one IPv6 property configured within the same domain; neither property can have CNAMEs or backup CNAMEs.
|Weighted Random Load Balancing||GTM divides the traffic across your data centers according to traffic weights you supply. Each request is assigned to a data center selected at random with a probability based on the weights you provided. For example, if you have two data centers and specify a 2:1 traffic split, GTM chooses the first data center twice as often as it chooses the second. Assignments are made without regard to the location of the requester. For details, see Load Balancing.|
|Weighted Random Load Balancing with Data Center Stickiness||In this mode, GTM distributes traffic according to percentages you configure, as in Weighted Random Load Balancing. Data center assignments are "sticky," meaning a given nameserver stays mapped to the same data center unless that data center goes down. When a data center goes down, only users mapped there are re-mapped. All other mappings remain stable. For details, see Load Balancing.|
|Weighted Random Load Balancing with Load Feedback||GTM provides answers for two or more data centers based on the current load statistics available as reported in the Load Feedback objects. Data centers, whose current load is lower than the target load, receive a proportional share of traffic. As the reported current load approaches the target load, GTM begins to shift the traffic to other data centers that are below their target load. GTM does not provide answers on any data center whose current load is greater than the capacity for the same target, unless all targets are exceeding capacity. This property is available for Weighted Random Load Balancing domains only when Load Feedback is enabled. For details, see Load Balancing.|
|Performance-Based Load Balancing||Traffic is sent to the target that is geographically
closest to the user. You can modify the amount of traffic sent to each
target by changing the traffic weight for each target. The load
imbalance factor of the domain also affects how much traffic is sent to
each target. For details, see Load Balancing.
Note: Data center locations must be populated with as much info as possible. For example, including latitude and longitude is preferred.
|Performance-Based Load Balancing with Load Feedback||To balance traffic load, one or more measurements of traffic load (resources) are defined and supplied by each data center in real time. This property is available for Performance domains only when Load Feedback is enabled. For details, see Performance with load feedback.|
|Performance-Based Load Balancing with Load Feedback (targets computed from configured weights)||This property type is similar to Performance-Based Load Balancing with Load Feedback, except that you can give each traffic target a weight that is taken into account when GTM distributes traffic. This property is available for Performance domains only when Load Feedback is enabled. For details, see Performance with load feedback.|
|Performance-Based Load Balancing with Load Feedback Based on Liveness Test Download Scores||The edge network tracks the amount of time it takes to download the test objects specified for this property, sending more traffic to the traffic target with the shortest download times. This property is available for Performance domains only when Load Feedback is enabled. For details, see Performance with load feedback.|