Configure Multi Site Origin

1. Create cachegroups for the origin locations, and assign the appropriate parent-child relationship between the mid and org cachegroups (click the image to see full size). Each mid cachegroup can be assigned a primary and secondary origin parent cachegroup. When the mid cache parent configuration is generated, origins in the primary cachegroups will be listed first, followed by origins in the secondary cachegroup. Origin servers assigned to the delivery service that are assigned to neither the primary nor secondary cachegroups will be listed last.

2. Create a profile to assign to each of the origins:

3. Create server entries for the origination vips:

4. Check the multi-site check box in the delivery service screen:

5. Assign the org servers to the delivery service that will have the multi site feature. Org servers assigned to a delivery service with multi-site checked will be assigned to be the origin servers for this DS.

Note

“Origin Server Base URL” uniqueness: In order to enable MID caches to distinguish delivery services by different MSO algorithms while performing parent failover, it requires that “Origin Server Base URL” (OFQDN) for each MSO enabled delivery service is unique unless the exceptions listed afterwards. This means that the OFQDN of a MSO enabled delivery service should be different with the OFQDNs of any other delivery service, regardless of whether they are MSO enabled or not. The exceptions are:

1. If there are multiple CDNs created on the same Traffic Ops, delivery services across different CDNs may have the same OFQDN configured.
2. If several delivery services in the same CDN have the same MSO algorithm configured, they may share the same OFQDN.
3. If delivery services are assigned with different MID cache groups respectively, they can share the same OFQDN.
4. This OFQDN must be valid - ATS will perform a DNS lookup on this FQDN even if IPs, not DNS, are used in the parent.config.
5. The OFQDN entered as the “Origin Server Base URL” will be sent to the origins as a host header. All origins must be configured to respond to this host.

6. For ATS 5.x, configure the mid hdr_rewrite on the delivery service, example:

   cond %{REMAP_PSEUDO_HOOK} __RETURN__ set-config proxy.config.http.parent_origin.dead_server_retry_enabled 1 __RETURN__ set-config proxy.config.http.parent_origin.simple_retry_enabled 1 __RETURN__ set-config proxy.config.http.parent_origin.simple_retry_response_codes "400,404,412" __RETURN__ set-config proxy.config.http.parent_origin.dead_server_retry_response_codes "502,503" __RETURN__ set-config proxy.config.http.connect_attempts_timeout 2 __RETURN__ set-config proxy.config.http.connect_attempts_max_retries 2 __RETURN__ set-config proxy.config.http.connect_attempts_max_retries_dead_server 1 __RETURN__ set-config proxy.config.http.transaction_active_timeout_in 5 [L] __RETURN__
   

7. Create a delivery service profile. This must be done to set the MSO algorithm. Also, as of ATS 6.x, multi-site options must be set as parameters within the parent.config. Header rewrite parameters will be ignored. See ATS parent.config for more details. These parameters are now handled by the creation of a delivery service profile.

   1. Create a profile of the type DS_PROFILE for the delivery service in question.

      

   2. Click “Show profile parameters” to bring up the parameters screen for the profile. Create parameters for the following:

      Parameter Name	Config File Name	Value	ATS parent.config value
      mso.algorithm	parent.config	true, false, strict, consistent_hash	round_robin
      mso.parent_retry	parent.config	simple_retry, both, unavailable_server_retry	parent_retry
      mso.unavailable_server_retry_responses	parent.config	list of server response codes, eg “500,502,503”	defaults to the value in records.config when unused.
      mso.max_simple_retries	parent.config	Nubmer of retries made after a 4xx error	defaults to the value in records.config when unused.
      mso.max_unavailable_server_retries	parent.config	Nubmer of retries made after a 5xx error	defaults to the value in records.config when unused.

      

   3. In the delivery service page, select the newly created DS_PROFILE and save the delivery service.

8. Turn on parent_proxy_routing in the MID profile.