The instructions for adding a new property to a domain are similar for most properties. The differences occur because not all properties have the same Basic - Info page fields, traffic target fields, or allow liveness tests.

See Property type descriptions for a description of each property type.

See the TABLE OF CONTENTS on the right side of this section to find the specific instructions for each property type.

1. Navigate to the Properties tab.

2. Click Add New Property. The New Property - Basic Info page opens.

3. Enter a name for the property. This defines the DNS subdomain to evoke the policy or behavior.

4. Select a Property Type from the list of options to define the behavior of the property. Click Show Other Descriptions to see details for all property types or see Property type descriptions.

5. Enter the basic property information that varies for each property type.

   • Comments. This is an optional field. You can enter a comment regarding the purpose of the property.

   • DNS TTL. The default is 60 seconds.

   • IP Type. Select whether IPv4 or IPv6 addresses will be handed out by the property.

   • Minimum Live Percentage. Defines the minimum percentage of servers in a datacenter that must be down before the datacenter is officially declared “down.” By default, this is 100%. That is, by default, a datacenter is only declared “down” if every server in the datacenter is down.

6. After you are done, click Add to Change List & Next.

7. On the next tab, enter the Traffic Targets you would like for your new property. Click Add to Change List & Next.

8. Enter the details for Liveness Test. Click Add to Change List & Next after you are done.

9. Review the details of your new property and click Add to Change List.

10. Follow the steps in Activate domain changes in Manage GTM domains to see the changes on your domain.

Add Mirror Failover property

Adding a Mirror Failover property to a domain lets you typically configure one or more data centers (typically two, a primary and a backup). GTM monitors the primary data center and as long as it is up
sends users there.

📘

You need a domain to which you can add the property.

1. On the Traffic management domains page, select the domain for which you want to add a property and click Add New Property.

2. Enter a name in the Property Name field. This is required.

3. Select Mirror Failover from the Property Type list and enter this information or accept the defaults.

   • Comments. This is an optional field. You can enter a comment regarding the purpose of the domain.

   • DNS TTL. The default is 60 seconds.

   • IP Type. Select whether IPv4 or IPv6 addresses will be handed out by the property.

   • Minimum Live Percentage (optional). The default behavior is that a data center is declared down when all the servers in it are declared down. This defines a minimum percentage of live servers in a data center, below which the data center is be declared down.

4. Click Add To Change List & Next. The Traffic Targets page opens.

5. Select the Data Center associated with a traffic target from the menu.

6. Enter server names or IP addresses for each target.

   If a handout CNAME is given, traffic distributed to a traffic target is sent to where the CNAME points. If servers are also given, liveness tests from these servers are used to determine if the traffic target is available. If no server is given, this traffic target is always considered available. If you have more than one server name, separate them with commas, spaces, or line breaks.

7. Click Set as Primary on a target to make it the primary traffic target.

8. To add a new target at this stage, click Add New Target. If you do not have an available data center, a clone for an existing one is created.

   To enable or disable a target, use the slider. To remove a target, click X.

9. Click Add To Change List & Next. The Liveness test page opens.

10. Enter this information for at least one test, or click Skip to proceed to the Review page. You can create a test later. This example uses the HTTP protocol. Other protocols have different or fewer fields to fill out. See Liveness Test.

    • Enabled. Click the Enabled checkbox to allow (enable) the liveness test for the selected property. Uncheck the box to disable the liveness test for the selected property.

    • Test Name. Specifies a name for the liveness test. This field is required.

    • Test Interval. Specifies, in seconds, how often liveness tests are run. The default is 60 seconds.

    • Test Timeout. Specifies, in seconds, how long the servermonitor waits without getting a response before declaring a timeout error. The default is 10 seconds. See Timeout back off.

    • Port. Specify the port number for requesting the test object

    • Protocol. Select a type from the menu (for example, HTTP, FTP, TCP)

    • Test Object Path (optional). Enter only the local part of the URL for the test object (for example, /data/results/test.html).

    • HTTP Headers. Select one or more HTTP headers from the drop-down menu and specify its value. Optionally, you can choose Other, which allows you to specify one or more customized HTTP headers. The customized header name must contain only letters, digits, hyphens, underscores, and dots. Blank spaces causes an error when you try to submit and validate the changes.

    Click the Validate HTTP Headers to verify the validity of the HTTP headers before saving the liveness test. A message displays only if HTTP header errors are detected.

    For more detailed information about HTTP Headers, see Liveness Test.

    • HTTP/FTP errors. Select the responses you want to consider for server failures.

    • Authentication. If you are using password authentication, provide a username and password.

11. Click Add To Change List & Next. The Review page opens. On the Review page you can view the basic property settings, traffic targets, and liveness tests and edit the settings if you want to make revisions.

📘

​Akamai​ uses the servers specified in the data center to determine if the traffic target is available. If the liveness test fails on all the servers in a data center, ​Akamai​ stops sending traffic to that data center. Also, if a handout CNAME is given, traffic distributed to a traffic target is sent to where the CNAME points. If servers are also given, liveness tests from these servers are used to determine if the traffic target is available. If no server is given, this traffic target is always considered available.

12. Click Add To Change List. The Properties tab opens. A green check mark appears next to the new property.

13. Click Review Change List. The Change List Detail dialog opens.

14. Review the Change List Detail dialog changes, validate them, add a required comment, and click Activate Domain to save them.

    See Review change List Detail.

Add Ranked Failover property

In a Ranked Failover property, GTM assigns traffic to the live datacenters with the highest precedence. Within each Ranked Failover property, the target with the highest precedence is labeled the Primary Traffic Target. Any additional targets in the property are listed in the property’s Traffic Distribution Targets page by their order of precedence. When a Primary Traffic Target isn't available, the traffic is directed to other available targets in their order of precedence. If there are two or more live datacenters with the same highest precedence, traffic is split randomly and evenly among them.

📘

You need a domain to which you can add the property.

1. On the Traffic management domains page, select the domain that you want to add a property to and click Add New Property.

2. Enter a name in the Property Name field. This is required.

3. From the Property Type list, select Ranked Failover and scroll down to enter the following information or accept the defaults.

   • Comments (optional). Enter a comment regarding the purpose of the domain.

   • DNS TTL. The default is 60 seconds.

   • IP Type. Select whether the property hands out IPv4 or IPv6 addresses.

   • Minimum Live Percentage (optional). As default behavior, the data center is declared down when all the servers in it are declared down. This defines a minimum percentage of live servers in a data center, below which the data center is declared down.

4. Click Add To Change List & Next. The Properties page for the new Ranked Failover property opens.

5. Click Property Basic Settings to enter the following information or modify the information added in step 3.

   • Handout Mode. Specify how IPs are returned when more than one IP is alive and available. Select Normal, Persistent Assignment, One IP chosen at random, One IP chosen by hash of request name, or All live IPs. The default is normal. Handout mode is relevant only when you have more than one server IP in a data center.

   • Handout Limit. Indicate the limit for the number of live IPs handed out to a DNS request. The Handout Limit applies only if Handout Mode is set to either Normal or Persistent Assignment for the property. If applicable, the Handout Limit default value is 8 or 0 if not. applicable

   • Failover Delay. Specify the failover delay in seconds. The minimum value is 0. If specified, when a server begins failing its liveness test, GTM only considers it down after the failover delay has elapsed and the errors persist.

   • Failback Delay. Specify the failback delay in seconds. The minimum value is 0. If specified, when a server has been down and comes back up, (that is, its liveness test starts succeeding again), GTM only considers it up after the failback delay has elapsed and tests continue to succeed.

   • Liveness Test Score Aggregation Type. When a property is configured with multiple tests, servermonitor aggregates the scores for a server across the tests to produce a single score. You can configure how these scores are aggregated by choosing from the methods mean, median, worst, and best.

   • Minimum Live Percentage. Select the checkbox and define a minimum percentage of live servers in a Data Center, below which the Data Center is declared down.

6. Click Traffic Distribution Targets to open the Traffic Targets page.

7. To add a new target, click Add New Target. If you do not have an available data center, a clone for an existing one is created.

   For each target, do the following:

   1. From the Data Center menu, select a Data Center to associate it with the traffic target or accept the default.

   2. Click Set as Primary on a target to make it the Primary traffic or accept the default Primary target.

   3. Enter Servers or Handout CNAMEs for each target.

      If a Handout CNAME is given, traffic distributed to a traffic target is sent to where the CNAME points. If Servers are also given, liveness tests from these servers are used to determine if the traffic target is available. If no Servers is given, this traffic target is always considered available. If you have more than one server name, separate them with commas, spaces, or line breaks.

   4. To set the order of precedence for all targets, use these options:

      • Click these arrows to move a target up or down in the order of precedence.
      • Click these arrows to to move a target to the top or bottom in the order of precedence. When you move a target to the top, it automatically becomes the Primary target.
      • To enable or disable a target, use the slider.
      • To remove a target, click X.
      • To create a group of targets with the same precedence, select the checkbox above the target's number on the left side of the page for each target. When you are done selecting the members of the group, click Group Selected Targets in the top right corner of the page.
      • To merge multiple groups to give them the same level of precedence, select the checkbox that's above the group's target number on the left side of the page for each group. When you are done selecting the groups you want to merge, click Merge Selected Groups in the top right corner of the page.

8. When you are done setting the status and order of precedence for all targets, click Add To Change List & Next.

9. Optionally, if you want to add Liveness tests to this Ranked Failover property, see Manage liveness tests.

10. Optionally, if you want to add Static record sets to this Ranked Failover propterty, see Manage static record sets.

11. When all changes are complete, click Add to Change List.

Add Static property

The static property type allows you to directly set and configure DNS record sets. You must have a domain to which you can add the static property.

Static properties return pre-configured DNS records. The record data for each DNS record type is managed as its own static record set. Static properties can only include static record sets. Static record sets do not support DNSSEC-related record types, AKAMAITLC record types, or AKAMAICDN record types. There are no traffic targets and no liveness tests.

1. On the Traffic Management Domains page, select the domain you want to add the static property to, and click Add New Property.

2. Enter a name in the Property Name field. Do not define a name at the apex by using @ in the name.

3. Select the property type Static.

4. As an option, you can add comments to the Comments field.

5. Click Add To Change List & Next. The properties page for the new static property opens.

6. In the Static record sets pane, click Add new record set. The Add new record set for dialog opens.

7. To add a new record set for this static property, enter this information.

   • Type (required). Select a record type from the list. When you select the Type, Record data help provides Instructions, Format, and Examples for the Record data field.

   • TTL (optional). Enter a TTL value in seconds.

   • Record data (required). Enter your record set information in accordance with the Record data help instructions for your chosen Type.

8. Click Add to Change List. The Change List Detail page opens. You return to the page for the static property.

9. Review the Change List Detail dialog changes, validate them, add a required comment, and click Activate Domain to save them.

   See Change List Detail Dialog.

Add Map by geographic location property

Geographic mapping lets you configure a property that returns a CNAME based on the requester's location. You can reuse maps for multiple properties or create new ones.

To configure a property for geographic mapping, your domain must have at least one geographic map defined.

1. On the Traffic Management Domains page, select the domain for which you want to add a property and click Add New Property.

2. Enter a name in the Property Name field. This is required.

3. Select Map by geographic location from the Property Type list.

4. Enter this information or accept the defaults.

   • Comments. This is an optional field. You can enter a comment regarding the purpose of the domain.

   • DNS TTL. The default is 60 seconds.

5. Click Add To Change List & Next. The Traffic Targets page opens.

6. Enter a handout CNAME for the geographic zones and default mapping zone.

7. Click Add To Change List & Next. The Review page opens. On the Review page, you can view the basic property settings and traffic targets and edit the settings if you want to make revisions.

8. Click Add To Change List. The Properties tab opens. A green check mark appears next to the new property.

9. Click Review Change List. The Change List Detail dialog opens.

10. Review the Change List Detail dialog changes, validate them, add a required comment, and click Activate Domain to save them.

See Review change List Detail.

Add Map by AS number property

Autonomous System (AS) maps split the Internet into multiple AS block zones. Properties using AS maps can specify handout CNAME for each zone. AS mapping lets you configure a property that directs users to a specific environment or to the origin.

To configure a property for AS mapping, your domain must have at least one AS map defined.

1. On the Traffic Management Domains page, select the domain for which you want to add a property and click Add New Property.

2. Enter a name in the Property Name field. This is required.

3. Select Map by AS number from the Property Type list.

1. Enter this information or accept the defaults.

   • Comments. This is an optional field. You can enter a comment regarding the purpose of the domain.

   • DNS TTL. The default is 60 seconds.

2. Click Add To Change List & Next. The Traffic Targets page opens.

3. Enter a handout CNAME for the geographic zones and default mapping zone.

4. Click Add To Change List & Next. The Review page opens. On the Review page, you can view the basic property settings and traffic targets and edit the settings if you want to make revisions.

5. Click Add To Change List. The Properties tab opens. A green check mark appears
   next to the new property.

6. Click Review Change List. The Change List Detail dialog opens.

7. Review the Change List Detail dialog changes, validate them, add a required comment, and click Activate Domain to save them.

   See Review change List Detail.

Add Map by IP address (CIDR blocks) property

CIDR maps split the Internet into multiple CIDR-block zones. Properties that use a map can specify a handout CNAME for each zone on the property's editing page.

To configure a property for CIDR mapping, your domain must have at least one CIDR map defined.

1. On the Traffic Management Domains page, select the domain for which you want to add a property and click Add New Property.

2. Enter a name in the Property Name field. This is required.

3. Select Map by IP address (CIDR blocks) from the Property Type list.

• Enter this information or accept the defaults.

  • Comments. This is an optional field. You can enter a comment regarding the purpose of the domain.

  • DNS TTL. The default is 60 seconds.

1. Click Add To Change List & Next. The Traffic Targets page opens.

2. Enter a handout CNAME for the geographic zones and default mapping zone.

3. Click Add To Change List & Next. The Review page opens. On the Review page, you can view the basic property settings and traffic targets and edit the settings if you want to make revisions.

4. Click Add To Change List. The Properties tab opens. A green check mark appears next to the new property.

5. Click Review Change List. The Change List Detail dialog opens.

6. Review the Change List Detail dialog changes, validate them, add a required comment, and click Activate Domain to save them.

   See Review change List Detail.

Add IP Version Selector property

In an IP Version Selector property, GTM provides answers for both A and AAAA queries, which eases migration to IPv6.

To create an IP Version Selector property, 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.

1. On the Traffic Management Domains page, select the domain for which you want to add a property and click Add New Property.

2. Enter a name in the Property Name field. This is required.

3. Select IP Version Selector from the Property Type list and enter this information or accept the defaults.

   • Comments. This is an optional field. You can enter a comment regarding the purpose of the domain.

   • DNS TTL. The default is 60 seconds.

4. Click Add To Change & Next. The Traffic Targets page opens.

5. Select a property for an A record target and a property for an AAAA record target. For a property to be eligible as a target for an IP Version Selector property, its type cannot be geographic or CIDR map-based load balancing, and it must not have any defined handout CNAMEs.

6. Click Add To Change List & Next. The Review page opens.

7. Click Add To Change List. The Properties tab opens. A green check mark appears next to the new property.

8. Click Review Change List.

9. Review the Change List Dialog changes, validate them, add a required comment, and click Activate Domain to save them.

   See Review change List Detail.

Add Weighted Random Load Balancing property

This property type divides traffic across data centers according to traffic weights that you supply. Each request is assigned to a data center selected at random with a probability based on the weights you provided.

1. On the Traffic Management Domains page, select the domain for which you want to add a property and click Add New Property.

2. Enter a name in the Property Name field. This is required.

3. Select Weighted Random Load Balancing from the Property Type list and enter this information or accept the default.

   • Comments. This is an optional field. You can enter a comment regarding the purpose of the domain.

   • DNS TTL. The default is 60 seconds.

   • IP Type. Select whether IPv4 or IPv6 addresses will be handed out by the property.

   • Minimum Live Percentage. Defines the minimum percentage of servers in a datacenter that must be down before the datacenter is officially declared “down.” By default, this is 100%. That is, by default, a datacenter is only declared “down” if every server in the datacenter is down.

4. Click Add To Change & Next. The Traffic Targets page opens.

5. Select the Data Center associated with a traffic target from the menu.

6. Enter server names or Handout CNAMEs for each target.

   If a handout CNAME is given, traffic distributed to a traffic target is be sent to where the CNAME points. If servers are also given, liveness tests from these servers are used to determine if the traffic target is available. If no server is given, this traffic target is always considered available. If you have more than one server name, separate them with commas, spaces, or line breaks.

7. Enter an IP address or CNAME in the Backup Answer field.

8. Click Balance All Targets Evenly if you want to split the load equally among all of your targets.

   You can manually enter load proportions in the Data Center Weight field of a target, which will be routed to the data center.

9. To add a new target, click Add New Target. If you do not have an available data center, a clone for an existing one is created.

   To enable or disable a target, use the slider. To remove a target, click X.

10. When you complete the target information, click Add To Change List & Next. The Liveness Test page opens.

11. Enter this information for at least one test, or click Skip to proceed to the Review page. You can create a test later. This example uses the HTTP protocol. Other protocols have different or fewer fields to fill out. See Liveness Test.

    • Enabled. Click the Enabled checkbox to allow (enable) the liveness test for the selected property. Uncheck the box to disable the liveness test for the selected property.

    • Test Name. Specifies a name for the liveness test. This field is required.

    • Test Interval. Specifies, in seconds, how often liveness tests are run. The default is 60 seconds.

    • Test Timeout. Specifies, in seconds, how long the servermonitor waits without getting a response before declaring a timeout error. The default is 10 seconds. See Timeout back off.

    • Port. specify the port number for requesting the test object.

    • Protocol. select a type from the menu (for example, HTTP, FTP, TCP)

    • Test Object Path (optional). Enter only the local part of the URL for the test object (for example, /data/results/test.html).

    • Host Header (optional)

    • HTTP/FTP errors. Select the responses you want to consider for server failures.

    • Authentication. If you are using password authentication, provide a username and password.

12. Click Add To Change List & Next. The Review page opens. On the Review page you can view the basic property settings, traffic targets, and liveness tests and edit the settings if you want to make revisions.

📘

​Akamai​ uses the servers specified in the data center to determine if the traffic target is available. If the liveness test fails on all the servers in a data center, ​Akamai​ stops sending traffic. Also, if a handout CNAME is given, traffic distributed to a traffic target is sent to where the CNAME points. If servers are also given, liveness tests from these servers are used to determine if the traffic target is available. If no server is given, this traffic target is always considered available.

1. Click Add To Change List. The Properties tab opens. A green check mark appears next to the new property.

2. Click Review Change List.

3. Review the Change List Detail dialog changes, validate them, add a required comment, and click Activate Domain to save them.

See Change List Detail Dialog.

Add Weighted Random Load Balancing with Data Center Stickiness property

Use this property to distribute traffic using percentages you configure. The data center assignments are sticky, meaning that a given name server stays mapped to the same data center unless that data center goes down.

1. On the Traffic Management Domains page, select the domain for which you want to add a property and click Add New Property.

2. Enter a name in the Property Name field. This is required.

3. Select Weighted Random Load Balancing with Data Center Stickiness from the Property Type list and enter this information or accept the defaults.

   • Comments. This is an optional field. You can enter a comment regarding the purpose of the domain.

   • DNS TTL. The default is 60 seconds.

   • IP Type. Select whether IPv4 or IPv6 addresses will be handed out by the property.

   • Minimum Live Percentage. Defines the minimum percentage of servers in a datacenter that must be down before the datacenter is officially declared “down.” By default, this is 100%. That is, by default, a datacenter is only declared “down” if every server in the datacenter is down.

4. Click Add To Change & Next. The Traffic Targets page opens.

5. Select the Data Center associated with a traffic target from the menu.

6. Enter server names or Handout CNAMEs for each target.

   If a handout CNAME is given, traffic distributed to a traffic target is sent to where the CNAME points. If servers are also given, liveness tests from these servers are used to determine if the traffic target is available. If no server is given, this traffic target is always considered available. If you have more than one server name, separate them with commas, spaces, or line breaks.

7. Enter an IP address or CNAME in the Backup Answer field.

8. Click Balance All Targets Evenly to split the load among the targets.

   You can manually enter load proportions in the Data Center Weight field of a target, which will be routed to the data center.

9. To add a new target at this stage, click Add New Target. If you do not have an available data center, a clone for an existing one is created.

   To enable or disable a target, use the slider. To remove a target, click X.

10. When you complete the target information, click Add To Change List & Next. The Liveness Test page opens.

11. Enter this information for at least one test, or click Skip to proceed to the Review page. You can create a test later. This example uses the HTTP protocol. Other protocols have different or fewer fields to fill out. See Liveness Test.

    • Enabled. Click the Enabled checkbox to allow (enable) the liveness test for the selected property. Uncheck the box to disable the liveness test for the selected property.

    • Test Name. Specifies a name for the liveness test. This field is required.

    • Test Interval. Specifies, in seconds, how often liveness tests are run. The default is 60 seconds.

    • Test Timeout. Specifies, in seconds, how long the servermonitor waits without getting a response before declaring a timeout error. The default is 10 seconds. See Timeout back off.

    • Port. Specify the port number for requesting the test object.

    • Protocol. Select a type from the menu (for example, HTTP, FTP, TCP).

    • Test Object Path (optional). Enter only the local part of the URL for the test object (for example, /data/results/test.html).

    • Host Header (optional)

    • HTTP/FTP errors. Select the responses you want to consider for server failures.

    • Authentication. If you are using password authentication, provide a username and password.

12. Click Add To Change List & Next. The Review page opens. On the Review page you can view the basic property settings, traffic targets, and liveness tests and edit the settings if you want to make revisions.

📘

​Akamai​ uses the servers specified in the data center to determine if the traffic target is available. If the liveness test fails on all the servers in a data center, ​Akamai​ stops sending traffic. Also, if a handout CNAME is given, traffic distributed to a traffic target is sent to where the CNAME points. If servers are also given, liveness tests from these servers are used to determine if the traffic target is available. If no server is given, this traffic target is always considered available.

13. Click Add To Change List. The Properties tab opens. A green check mark appears next to the new property.

14. Click Review Change List.

15. Review the Change List Dialog changes, validate them, add a required comment, and click Activate Domain to save them.

See the Change List Detail Dialog.

Add Weighted Random Load Balancing with Load Feedback property

This property type divides traffic across data centers based on the load metrics reported in the Load feedback resources. Data centers whose current load is lower than the target load receive a proportional share of traffic. See Load feedback resources.

This property type is available only if Load Feedback is enabled for the domain when it's created. You cannot edit the Load Feedback setting after the domain is created. To create a new domain, see Create a new domain.

1. On the Traffic Management Domains page, select the domain for which you want to add a property and click Add New Property.

2. Enter a name in the Property Name field. This is required.

3. Select Weighted Random Load Balancing with Load Feedback from the Property Type list and enter this information or accept the defaults.

   Data centers whose current load is lower than the target load receive a proportional share of traffic

   • Minimum Live Percentage. Defines the minimum percentage of servers in a datacenter that must be down before the datacenter is officially declared “down.” By default, this is 100%. That is, by default, a datacenter is only declared “down” if every server in the datacenter is down.

   • Comments. This is an optional field. You can enter a comment regarding the purpose of the domain.

   • DNS TTL. The default is 60 seconds.

   • IP Type. Select whether IPv4 or IPv6 addresses will be handed out by the property.

4. Click Add To Change & Next. The Traffic Targets page opens.

5. Select the Data Center associated with a traffic target from the menu.

6. Enter server names or Handout CNAMEs for each target.

   If a handout CNAME is given, traffic distributed to a traffic target is sent to where the CNAME points. If servers are also given, liveness tests from these servers are used to determine if the traffic target is available. If no server is given, this traffic target is always considered available. If you have more than one server name, separate them with commas, spaces, or line breaks.

7. Enter an IP address or CNAME in the Backup Answer field.

8. To add a new target at this stage, click Add New Target. If you do not have an available data center, a clone for an existing one is created.

   To enable or disable a target, use the slider. To remove a target, click X.

9. Click Add To Change List & Next. The Liveness Test page opens

10. Enter this information for at least one test, or click Skip to proceed to the Review page. You can create a test later. This example uses the HTTP protocol. Other protocols have different or fewer fields to fill out. See Liveness Test.

    • Enabled. Click the Enabled checkbox to allow (enable) the liveness test for the selected property. Uncheck the box to disable the liveness test for the selected property.

    • Test Name. Specifies a name for the liveness test. This field is required.

    • Test Interval. Specifies, in seconds, how often liveness tests are run. The default is 60 seconds.

    -- Test Timeout. Specifies, in seconds, how long the servermonitor waits without getting a response before declaring a timeout error. The default is 10 seconds. See Timeout back off.

    • Port. Specify the port number for requesting the test object.

    • Protocol. Select a type from the menu (for example, HTTP, FTP, TCP).

    • Test Object Path (optional). Enter only the local part of the URL for the test object (for example, /data/results/test.html).

    • Host Header (optional)

    • HTTP/FTP errors. Select the responses you want to consider for server failures.

    • Authentication. If you are using password authentication, provide a username and password.

11. Click Add To Change List & Next. The Review page opens. On the Review page you can view the basic property settings, traffic targets, and livenesstests and edit the settings if you want to make revisions.

📘

​Akamai​ uses the servers specified in the data center to determine if the traffic target is available. If the liveness test fails on all the servers in a data center, ​Akamai​ stops sending traffic. Also, if a handout CNAME is given, traffic distributed to a traffic target is sent to where the CNAME points. If servers are also given, liveness tests from these servers are used to determine if the traffic target is available. If no server is given, this traffic target is always considered available.

12. Click Add To Change List. The Properties tab opens. A green check mark appears next to the new property.

13. Click Review Change List.

14. Review the Change List Dialog changes, validate them, add a required comment, and click Activate Domain to save them.

    See Change List Detail Dialog.

Make sure that you configure a load feedback resource and associate it with the property before the property begins receiving production traffic. See Manage resources.

Add Performance-Based Load Balancing property

This property sends traffic to the target that is 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.

1. On the Traffic Management Domains page, select the domain for which you want to add a property and click Add New Property.

2. Enter a name in the Property Name field. This is required.

3. Select Performance-Based Load Balancing from the Property Type list and enter this information or accept the defaults.

   • Minimum Live Percentage. Defines the minimum percentage of servers in a datacenter that must be down before the datacenter is officially declared “down.” By default, this is 100%. That is, by default, a datacenter is only declared “down” if every server in the datacenter is down.

   • Comments (optional)

   • DNS TTL. The default is 60 seconds.

   • IP Type. Select whether IPv4 or IPv6 addresses will be handed out by the property.

4. Click Add To Change & Next. The Traffic Targets page opens.

5. Select the Data Center associated with a traffic target from the menu.

6. Enter server names or Handout CNAMEs for each target.

   If a handout CNAME is given, traffic distributed to a traffic target is sent to where the CNAME points. If servers are also given, liveness tests from these servers are used to determine if the traffic target is available. If no server is given, this traffic target is always considered available. If you have more than one server name, separate them with commas, spaces, or line breaks.

7. Enter an IP address or CNAME in the Backup Answer field.

8. Click Balance All Targets Evenly to split the load among the targets.

   You can also manually enter load proportions in the Data Center Weight field that is routed to the data center.

9. To add a new target at this stage, click Add New Target. If you do not have an available data center, a clone for an existing one is created.

   To enable or disable a target, use the slider. To remove a target, click X.

10. Click Add To Change List & Next. The Liveness Test page opens.

11. Enter this information for at least one test, or click Skip to proceed to the Review page. You can create a test later. This example uses the HTTP protocol. Other protocols have different or fewer fields to fill out. See Liveness Test.

    • Enabled. Click the Enabled checkbox to allow (enable) the liveness test for the selected property. Uncheck the box to disable the liveness test for the selected property.

    • Test Name. Specifies a name for the liveness test. This field is required.

    • Test Interval. Specifies, in seconds, how often liveness tests are run. The default is 60 seconds.

    • Test Timeout. Specifies, in seconds, how long the servermonitor waits without getting a response before declaring a timeout error. The default is 10 seconds. See Timeout back off.

    • Port. specify the port number for requesting the test object

    • Protocol. select a type from the menu (for example, HTTP, FTP, TCP)

    • Test Object Path (optional). Enter only the local part of the URL for the test object (for example, /data/results/test.html).

    • Host Header (optional)

    • HTTP/FTP errors. Select the responses you want to consider for server failures.

    • Authentication. If you are using password authentication, provide a username and password.

12. Click Add To Change List & Next. The Review page opens. On the Review page you can view the basic property settings, traffic targets, and liveness tests and edit the settings if you want to make revisions.

📘

​Akamai​ uses the servers specified in the data center to determine if the traffic target is available. If the liveness test fails on all the servers in a data center, ​Akamai​ stops sending traffic. Also, if a handout CNAME is given, traffic distributed to a traffic target is sent to where the CNAME points. If servers are also given, liveness tests from these servers are used to determine if the traffic target is available. If no server is given, this traffic target is always considered available.

1. Click Add To Change List. The Properties tab opens.

2. Click Review Change List.

3. Review the Change List Dialog changes, validate them, add a required comment, and click Activate Domain to save them.

See Change List Detail Dialog.

Add Performance-Based Load Balancing with Load Feedback property

This property sends traffic to the data center that is closest to the end user. The amount of traffic that GTM sends to each data center is adjusted based on the load metrics reported in the Load feedback resource.

This property type is available only if you enabled Load Feedback for the domain when it was created. You cannot edit the Load Feedback setting after the domain is created. To create a new domain, see Create a new domain.

1. On the Traffic Management Domains page, select the domain for which you want to add a property and click Add New Property.

2. Enter a name in the Property Name field. This is required.

3. Select Performance-Based Load Balancing with Load Feedback from the Property Type List and enter this information or accept the defaults.

   • Minimum Live Percentage. Defines the minimum percentage of servers in a datacenter that must be down before the datacenter is officially declared “down.” By default, this is 100%. That is, by default, a datacenter is only declared “down” if every server in the datacenter is down.

   • Comments (optional)

   • DNS TTL. The default is 60 seconds.

   • IP Type. Select whether IPv4 or IPv6 addresses will be handed out by the property.

4. Click Add To Change & Next. The Traffic Targets page opens.

5. Select the Data Center associated with a traffic target from the menu.

6. Enter server names or Handout CNAMEs for each target.

   If a handout CNAME is given, traffic distributed to a traffic target is sent to where the CNAME points. If servers are also given, liveness tests from these servers are used to determine if the traffic target is available. If no server is given, this traffic target is always considered available. If you have more than one server name, separate them with commas, spaces, or line breaks.

7. Enter an IP address or CNAME in the Backup Answer field.

8. To add a new target at this stage, click Add New Target. If you do not have an available data center, a clone for an existing one is created.

   To enable or disable a target, use the slider. To remove a target, click X.

9. Click Add To Change List & Next. The Liveness Test page opens.

10. Enter this information for at least one test, or click Skip to proceed to the Review page. You can create a test later. This example uses the HTTP protocol. Other protocols have different or fewer fields to fill out. See Liveness Test.

    • Enabled. Click the Enabled checkbox to allow (enable) the liveness test for the selected property. Uncheck the box to disable the liveness test for the selected property.

    • Test Name. Specifies a name for the liveness test. This field is required.

    • Test Interval. Specifies, in seconds, how often liveness tests are run. The default is 60 seconds.

    • Test Timeout. Specifies, in seconds, how long the servermonitor waits without getting a response before declaring a timeout error. The default is 10 seconds. See Timeout back off.

    • Port. specify the port number for requesting the test object

    • Protocol. Select a type from the menu (for example, HTTP, FTP, TCP)

    • Test Object Path (optional). only enter the local part of the URL for the test object (for example, /data/results/test.html).

    • Host Header (optional)

    • HTTP/FTP errors. Select the responses you want to consider for server failures.

    • Authentication. If you are using password authentication, provide a username and password.

11. Click Add To Change List & Next. The Review page opens. On the Review page you can view the basic property settings, traffic targets, and liveness tests and edit the settings if you want to make revisions.

📘

​Akamai​ uses the servers specified in the data center to determine if the traffic target is available. If the liveness test fails on all the servers in a data center, ​Akamai​ stops sending traffic. Also, if a handout CNAME is given, traffic distributed to a traffic target is sent to where the CNAME points. If servers are also given, liveness tests from these servers are used to determine if the traffic target is available. If no server is given, this traffic target is always considered available.

12. Click Add To Change List. The Properties tab opens. A green check mark appears next to the new property.

13. Click Review Change List.

14. Review the Change List Dialog changes, validate them, add a required comment, and click Activate Domain to save them.

    See Change List Detail Dialog.

    Make sure that you configure a load feedback resource and associate it with the property before the property begins receiving production traffic. See Manage resources.

Add Performance-Based Load Balancing with Load Feedback (targets computed from configured weights) Property to a Domain

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.

To create load feedback and performance-based property types you first need to create a new domain and enable Load Feedback. You cannot go back into a domain and change the Load Feedback setting to use these properties. To create a new domain, see Create a new domain.

1. On the Traffic Management Domains page, select the domain for which you want to add a property and click Add New Property.

2. Enter a name in the Property Name field. This is required.

3. Select Performance-Based Load Balancing with Load Feedback (targets computed from configured weights) from the Property Type list and enter this information or accept the defaults.

   • Minimum Live Percentage. Defines the minimum percentage of servers in a datacenter that must be down before the datacenter is officially declared “down.” By default, this is 100%. That is, by default, a datacenter is only declared “down” if every server in the datacenter is down.

   • Comments (optional)

   • DNS TTL. The default is 60 seconds.

   • IP Type. Select whether IPv4 or IPv6 addresses will be handed out by the property.

4. Click Add To Change & Next. The Traffic Targets page opens.

5. Enter server names or Handout CNAMEs for each target.

   If a handout CNAME is given, traffic distributed to a traffic target is be sent to where the CNAME points. If servers are also given, liveness tests from these servers are used to determine if the traffic target is available. If no server is given, this traffic target is always considered available.

6. Click Balance All Targets Evenly to split the load among the targets. You can manually enter a load value using the Data Center Weight field.

7. To add a new target at this stage, click Add New Target. If you do not have an available data center, a clone for an existing one is created.

   To enable or disable a target, use the slider. To remove a target, click X.

8. Click Add To Change List & Next. The Liveness Test page opens.

9. Enter this information for at least one test, or click Skip to proceed to the Review page. You can create a test later. This example uses the HTTP protocol. Other protocols have different or fewer fields to fill out. See Liveness Test.

   • Enabled. Click the Enabled checkbox to allow (enable) the liveness test for the selected property. Uncheck the box to disable the liveness test for the selected property.

   • Test Name. Specifies a name for the liveness test. This field is required.

   • Test Interval. Specifies, in seconds, how often liveness tests are run. The default is 60 seconds.

   • Test Timeout. Specifies, in seconds, how long the servermonitor waits without getting a response before declaring a timeout error. The default is 10 seconds. See Timeout back off.

   • Port. specify the port number for requesting the test object

   • Protocol. Select a type from the menu (for example, HTTP, FTP, TCP)

   • Test Object Path (optional). Enter only the local part of the URL for the test object (for example, /data/results/test.html).

   • Host Header (optional)

   • HTTP/FTP errors. Select the responses you want to consider for server failures.

   • Authentication. If you are using password authentication, provide a username and password.

10. Click Add To Change List & Next. The Review page opens. On the Review page you can view the basic property settings, traffic targets, and liveness tests and edit the settings if you want to make revisions.

📘

​Akamai​ will use the servers specified in the data center to determine if the traffic target is available. If the liveness test fails on all the servers in a data center, ​Akamai​ will stop sending traffic. Also, if a handout CNAME is given, traffic distributed to a traffic target will be sent to where the CNAME points. If servers are also given, liveness tests from these servers will be used to determine if the traffic target is available. If no server is given, this traffic target is always considered available.

1. Click Add To Change List. The Properties tab opens.

2. Click Review Change List.

3. Review the Change List Dialog changes, validate them, add a required comment, and click Activate Domain to save them.

See the Change List Detail Dialog.

Load Feedback and performance-based property types

Load Feedback is set at the domain level. Its default value is false so it is not enabled. When creating a new domain, a Load Feedback checkbox opens in the Settings section of the Add New Domain page to let you enable it. This checkbox appears only if the new domain's contract supports Performance-Based Load Balancing.

📘

After you create a domain, the Load Feedback setting cannot be changed in the user interface. You will have to create a new domain to change the setting.

Since Load Feedback is set at the domain level, all of the properties within a domain must follow the Load Feedback rules for that domain. This list indicates the performance-based property types available, depending on the Load Feedback state.

• Load Feedback Enabled

• Performance-Based Load Balancing with Load Feedback

• Performance-Based Load Balancing with Load Feedback (targets computed from configured weights)

• Performance-Based Load Balancing with Load Feedback Based on Liveness Test Download Scores (deprecated)

• Load Feedback Not Enabled

• Performance-Based Load Balancing