Sie sind auf Seite 1von 15

Manual Chapter: Working with Listeners

Table of Contents | << Previous Chapter | Next Chapter >>


4

Working with Listeners


Introducing listeners
Creating a listener for local resolution
Configuring listeners for traffic forwarding
Configuring a wildcard listener
Modifying listeners
Deleting listeners
Using listeners with VLANs
Introducing listeners
Before you can fully configure the Global Traffic Manager system to handle name resolution
requests, you must determine how the system integrates with your existing network. Part of this
integration includes identifying what network traffic is relevant to the Global Traffic Manager
and how the system responds to this traffic. In general, you have two options when handling
traffic with the Global Traffic Manager:
The Global Traffic Manager receives the traffic, processes it locally, and sends the appropriate
DNS response back to the querying server. Global Traffic Managers with this configuration are
considered to be running in node mode.
The Global Traffic Manager receives the traffic and forwards it; either to another part of the
network or another DNS server. Global Traffic Managers with this configuration are considered
to be running in either bridge mode or router mode, depending on where the system is
forwarding network traffic.
To control how the Global Traffic Manager handles network traffic, you configure one or more
listeners. A listener is a specialized resource that is assigned a specific IP address and uses port
53, the DNS query port. When traffic is sent to that IP address, the listener alerts the Global
Traffic Manager, allowing it to handle the traffic locally or forward the traffic to the appropriate
resource.
Tip: If you are familiar with the Local Traffic Manager, it might be helpful to consider a listener
as a specialized type of virtual server that is responsible for handling traffic for the Global Traffic
Manager.
Note: If you configure user accounts on the Local Traffic Manager, you can assign listeners, like
other virtual servers, to specific partitions. However, because listeners play an important role in
global traffic management, F5 Networks recommends that you assign all listeners to partition
Common.
You control how the Global Traffic Manager responds to network traffic on a per-listener basis.
For example, a single Global Traffic Manager can be the authoritative server for one domain,
while forwarding other requests to a separate DNS server. Regardless of how many listeners you
configure for the Global Traffic Manager, the system always manages and responds to requests
for any wide IPs that are configured on it.
To further illustrate how you configure listeners to control how the Global Traffic Manager
responds to DNS traffic, consider the fictional company SiteRequest. At this company, a Global
Traffic Manager is being integrated into a network with the following characteristics:
A DNS server already exists at IP address 10.2.5.37.
There are two VLANs, named external and guests.
There are two wide IPs: www.siterequest.com and downloads.siterequest.com.
Once integrated into the network, the Global Traffic Manager will be responsible for the
following:
Managing and responding to requests for the wide IPs
Forwarding other DNS traffic to the existing DNS server
Forwarding any traffic from the guests VLAN to the rest of the network
To implement this configuration, the Global Traffic Manager requires three listeners:
A listener with an IP address that equals the self IP address of the Global Traffic Manager. This
listener allows the system to manage DNS traffic that pertains to its wide IPs.
A listener with an IP address of 10.2.5.37, the IP address of the existing DNS server. This listener
allows the system to forward incoming traffic to the existing DNS server.
A wildcard listener enabled on the guests VLAN. This listener allows the Global Traffic Manager
to forward traffic sent from the guests VLAN to the rest of the network.
As you can see from this example, the role the Global Traffic Manager plays in managing DNS
traffic varies depending on the listener through which the traffic arrives. As a result, the Global
Traffic Manager becomes a flexible system for managing DNS traffic in a variety of ways.

Creating a listener for local resolution


Often, when you add a Global Traffic Manager to your network, you want the Global Traffic
Manager to be responsible for responding to at least a subset of your incoming DNS requests.
These requests can be directed to the wide IPs that are configured on the Global Traffic Manager;
however, you can also configure the Global Traffic Manager to respond to DNS requests for
other network resources that might not be associated with a wide IP, such as other DNS servers.
When a Global Traffic Manager is responsible for managing and responding to DNS traffic
locally, it is said to be operating in node mode. In this situation, you assign a listener to the
Global Traffic Manager that corresponds to an IP address that is specifically associated with the
system. If the Global Traffic Manager is operating as a standalone unit, this IP address is the self
IP address you assign to the Global Traffic Manager. If the Global Traffic Manager is part of a
redundant system for high availability purposes, this IP address is the floating IP address that
belongs to both systems.
To configure a listener for local resolution
1 On the Main tab of the navigation pane, expand Global Traffic and then click Listeners.
. The main listeners screen opens.
2 Click the Create button.
. The new listener screen opens.
In the Destination box, type the IP address on which the Global Traffic Manager listens for
network traffic.
3 In this case, the IP address that you add is either the self IP address of the system, or, in the
. case of a redundant pair setup, the floating IP address that corresponds to both systems.
4 From the VLAN Traffic list, select a VLAN setting appropriate for this listener.
. Note: Typically, if the Global Traffic Manager is handling traffic on this IP address locally, you
select All VLANs for this option.
5
. Click the Finished button to save the new listener.
Configuring listeners for traffic forwarding
Another common configuration you can use with the Global Traffic Manager is to integrate it
with your existing DNS servers. In this scenario, the Global Traffic Manager handles any traffic
related to the wide IPs you assign to it, while sending other DNS requests to another DNS server
on your network. When forwarding traffic in this manner, the Global Traffic Manager is
considered to be operating in bridge or router mode, depending on how the traffic was initially
sent to the Global Traffic Manager. In this configuration, you assign a listener to the Global
Traffic Manager that corresponds to the IP address of the DNS server to which you want to
forward to traffic.
Unlike the steps described in the section, Creating a listener for local resolution, you can create
more than one listener to forward network traffic. The number of listeners depends on your
network configuration and the ultimate destination to which you want to send specific DNS
requests.
To configure a listener for traffic forwarding
1 On the Main tab of the navigation pane, expand Global Traffic and then click Listeners.
. The main listeners screen opens.
2 Click the Create button.
. The new listener screen opens.
In the Destination box, type the IP address on which the Global Traffic Manager listens for
network traffic.
3 In this case, the IP address that you add is the IP address of the DNS server that you want to
. handle the DNS request.
From the VLAN Traffic list, select a VLAN setting appropriate for this listener.
4 Note: Typically, if you want the Global Traffic Manager to handle traffic on this IP address
. locally, select All VLANs.
5
. Click the Finished button to save the new listener.
Configuring a wildcard listener
In some cases, you might want the Global Traffic Manager to handle any traffic coming into your
network, regardless of the destination IP address of the given DNS request. In this configuration,
the Global Traffic Manager continues to process and respond to requests for the wide IPs that
you configure, but in addition it is responsible for forwarding any other DNS requests to other
network resources, such other DNS servers. To accomplish this type of configuration, you assign
a wildcard listener to the Global Traffic Manager.
To configure a wildcard listener
1 On the Main tab of the navigation pane, expand Global Traffic and then click Listeners.
. The main listeners screen opens.
2 Click the Create button.
. The new listener screen opens.
3
. In the Destination box, type: 0.0.0.0.
4
. From the VLAN Traffic list, select a VLAN setting appropriate for this listener.
5
. Click the Finished button to save the new wildcard listener.
Modifying listeners
After you create a listener, you can modify it as necessary. Common instances in which you need
to modify a listener include when you add an additional VLAN to the system, or when you want
to modify the IP address of a listener.
To modify a listener
1 On the Main tab of the navigation pane, expand Global Traffic and then click Listeners.
. The main listeners screen opens.
2 Click the name of the listener.
. The properties screen for that listener appears.
3
. Modify the settings for the listener.
4
. Click the Update button to save your changes to the listener.
Deleting listeners
In the event that a listener is no longer needed within the Global Traffic Manager, you can delete
it.
To delete a listener
1 On the Main tab of the navigation pane, expand Global Traffic and then click Listeners.
. The main listeners screen opens.
2
. Check the Select box that corresponds to the listener entry.
3 Click the Delete button.
. A confirmation screen appears.
4
. Click the Delete button to delete the listener.
Using listeners with VLANs
One of the features of a BIG-IP system is that you can create one or more VLANs and assign
specific interfaces to the VLANs of your choice. By default, each BIG-IP system includes at
least two VLANs, named internal and external. However, you can create as many VLANs as the
needs of your network demands.
When you assign listeners to the Global Traffic Manager, you must take into account any
VLANs that you have created. For example, a listener that forwards traffic to another DNS
server might only be appropriate for a specific VLAN, while a wildcard listener might be
applicable to all VLANs. You can configure a listener to be applicable to all VLANs, enabled
only on specific VLANs, or disabled on specific VLANs.
Note: For more information about BIG-IP systems and VLANs, see the TMOS Management
Guide for BIG-IP Systems.
Configuring a listener for all VLANs
When you are configuring a listener, set the VLAN Traffic setting to All VLANs if either of
these conditions exist:
The IP address you assign as a listener is valid for all VLANs for which the Global Traffic
Manager is responsible.
The Global Traffic Manager handles locally the traffic on the IP address you assign as a listener.
To configure a listener for all available VLANs
1 On the Main tab of the navigation pane, expand Global Traffic and then click Listeners.
. The main listeners screen opens.
2 Click the Create button.
. The new listener screen opens.
3 In the Destination box, type the IP address on which you want the Global Traffic Manager to
. listen for network traffic.
4
. From the VLAN Traffic list, select All VLANs.
5
. Click the Finished button to save your changes.
Enabling a listener for specific VLANs
If you want the Global Traffic Manager to manage traffic for only specific VLANs that are
configured on the Global Traffic Manager, use the Enabled on setting.
To configure a listener for specific VLANs
1 On the Main tab of the navigation pane, expand Global Traffic and then click Listeners.
. The main listeners screen opens.
2 Click the Create button.
. The new listener screen opens.
3 In the Destination box, type the IP address on which you want the Global Traffic Manager to
. listen for network traffic.
4 From the VLAN Traffic list, select Enabled on.
. A new setting, VLAN List, appears on the screen.
Select the appropriate VLANs from the Available list and use the Move buttons (<< >>) to
move them to the Selected list.
5 The listener alerts the Global Traffic Manager about traffic on only the VLANs in the Selected
. list.
6
. Click the Finished button to save your changes.
Disabling a listener for specific VLANs
If the Global Traffic Manager is configured with multiple VLANs, and you want to exclude
some of these VLANs from the listener, set the VLAN Traffic option to Disabled on.
To disable a listener for specific VLANs
1 On the Main tab of the navigation pane, expand Global Traffic and then click Listeners.
. The main listeners screen opens.
2 Click the Create button.
. The new listener screen opens.
3 From the VLAN Traffic list, select Disabled on.
. A new option, VLAN List, appears on the screen.
Select the appropriate VLANs from the Available list and use the Move buttons (<< >>) to
move them to the Selected list.
4 The listener alerts the Global Traffic Manager about traffic on all VLANs except those listed in
. the Selected list.
5
. Click the Finished button to save your changes
K13734: BIG-IP DNS synchronization group requirements
Non-Diagnostic

Original Publication Date: Apr 07, 2016


Updated Date: Dec 21, 2016

Applies to (see versions):

Topic

A BIG-IP DNS (formerly BIG-IP GTM) synchronization group is a collection of multiple BIG-IP
DNS systems that synchronize BIG-IP DNS configuration settings and metrics information. You
must meet several minimum requirements for BIG-IP DNS synchronization group members to
communicate and synchronize properly.

Description

For the BIG-IP DNS synchronization group members to properly synchronize their configuration
settings, verify that the following requirements are in place:

BIG-IP DNS synchronization group members must be running the same software
version

A BIG-IP DNS device should be running the same software version as other members in
the synchronization group. BIG-IP DNS devices that are running different software
versions will not be able to communicate and properly synchronize BIG-IP DNS
configuration and zone files. For information about displaying the software version, refer
to K8759: Displaying the BIG-IP software version.

Synchronization parameters must be properly defined for all members

Synchronization must be enabled and each device must have the same synchronization
group name. You can define the synchronization parameters by navigating to:
BIG-IP DNS 11.5.0 and later:

DNS > Settings > GSLB > General

BIG-IP GTM 10.0.0 - 11.4.1:

System > Configuration > Device > GTM > General

NTP must be configured on each device

Before you can synchronize BIG-IP DNS systems, you must define the network time
protocol (NTP) servers for all synchronization group members. Configuring NTP servers
ensures that each BIG-IP DNS synchronization group member is referencing the same
time when verifying the configuration data that needs to be synchronized. You can
configure NTP by navigating to System > Configuration > Device > NTP.

Port Lockdown must be set properly for the relevant self IP addresses

Port lockdown is a security feature that specifies the protocols and services from which a
self IP address can accept traffic. F5 recommends using the Allow Default option for self
IP addresses that are used for synchronization and other critical redundant pair
intercommunications. You can configure port lockdown by navigating to Network > Self
IPs.

TCP port 4353 must be allowed between BIG-IP GTM systems

BIG-IP DNS synchronization group members use TCP port 4353 to communicate. You
must verify that port 4353 is allowed between BIG-IP DNS systems.

Compatible big3d versions must be installed on synchronization group members

The big3d process runs on BIG-IP systems and collects performance information on
behalf of the BIG-IP DNS system. For metrics collection to work properly,
synchronization group members must run the same version of the big3d process. For
more information about verifying big3d version information, refer to K13703: Overview
of big3d version management.

A valid device certificate must be installed on all members

The device certificate is used by the F5 system to identify itself to a requesting F5 client
system. The default device certificate, /config/httpd/conf/ssl.crt/server.crt, must be
installed on each sync group member. You can verify the certificate validity by navigating
to System > Device Certificates.
Manual Chapter: Setting Up a Global Traffic Manager Redundant System
Configuration

Table of Contents | << Previous Chapter | Next Chapter >>


10
Setting Up a Global Traffic Manager Redundant System Configuration
Understanding Global Traffic Manager redundant system configurations
Setting up a Global Traffic Manager redundant system configuration
Understanding Global Traffic Manager redundant system configurations
With the BIG-IP Global Traffic Manager, you manage incoming DNS traffic, forwarding that
traffic to the appropriate DNS server or load balancing it to other resources on the network.
Typically, a given network has several Global Traffic Manager systems, with at least one system
installed at one of several data centers. With these systems in place, you can control the
distribution of DNS traffic across your resources, monitor these resources to determine their
availability, and ensure that any web-based applications have all the components necessary to
operate successfully.
A standard implementation of Global Traffic Manager systems is a redundant system
configuration. This is a set of two Global Traffic Manager systems: one operating as the active
unit, the other operating as the standby unit. If the active unit goes offline, the standby unit
immediately assumes responsibility for managing DNS traffic. The new active unit remains
active until another event occurs that would cause the unit to go offline, or you manually reset
the status of each unit.
The implementation tasks outlined in this chapter describe how to configure a Global Traffic
Manager redundant system. This example focuses on the fictional company, SiteRequest. Table
10.1 outlines the network characteristics at SiteRequest that pertain to this implementation.
Table 10.1 Network characteristics of SiteRequest
Component Characteristics

Data Center Name: New York Data Center


Global Traffic Host name: gtm1.siterequest.com
Manager (Active Self IP address: 10.1.1.20/24
Unit) Floating IP address: 10.1.1.50 (shared
with second Global Traffic Manager)
Management IP address:
192.168.15.16
Global Traffic Host name: gtm2.siterequest.com
Manager (Standby Self IP address: 10.1.1.21/24
Unit) Floating IP address: 10.1.1.50 (shared
with first Global Traffic Manager)
Management IP address:
192.168.15.17
VLAN Name: dns_requests
Assigned interfaces: 1.1 (untagged)
Default Gateway IP address: 10.1.1.100
NTP server IP address: 192.168.5.15
For this example, SiteRequest already has both Global Traffic Manager systems connected to the
network; however, they have not yet assigned IP addresses to the systems.
Setting up a Global Traffic Manager redundant system configuration
This implementation focuses on the fictional company SiteRequest. This company wants to
create a Global Traffic Manager redundant system configuration. They already have the systems
installed on the network; however, they have yet to fully configure them.
In this implementation, you accomplish the following tasks:
Configure the redundant system settings of each Global Traffic Manager.
Create a VLAN.
Assign Self IP addresses to both systems.
Create a floating IP address.
Configure the high availability options.
Define an NTP server.
Define the default gateway.
Define a listener for incoming DNS traffic.
Run a bigpipe config sync operation.
Define the data center to which the Global Traffic Manager systems belong.
Define the Global Traffic Manager systems.
Enable synchronization.
Conduct the initial configuration synchronization between systems through the gtm_add utility.
Configuring the redundant system settings
The first task in creating a redundant system configuration with two Global Traffic Manager
systems is to configure the redundant system settings. You configure two different systems: the
active system, which is initially online, and the standby system, which comes online only when
the active system goes offline.
Note: You can also complete the following procedure by running the Setup Utility. You can
access this utility through the main page of the Configuration utility of the Global Traffic
Manager.
To configure redundant system settings for the active system
1 On the Main tab of the navigation pane, expand System and then click Platform.
.
2
. From the High Availability list, select Redundant Pair.
3
. From the Unit ID list, select 1.
4
. Click Update.
To configure redundant system settings for the second system
1
. On the Main tab of the navigation pane, expand System and then click Platform.
2
. From the High Availability list, select Redundant Pair.
3
. From the Unit ID list, select 2.
4
. Click Update.
Creating VLANs
The next task in this implementation requires you to set up a VLAN. This VLAN encompasses
the IP addresses associated with the Global Traffic Manager systems and the other network
components that help manage DNS traffic.
You must apply the following procedures to both the active and standby systems.
To create a VLAN
1
. On the Main tab of the navigation pane, expand Network and then click VLANs.
2
. Click Create.
3
. In the Name box, type dns_requests.
4
. In the Interfaces area, use the Move buttons to assign interface 1.1 to the Untagged list.
5
. Click Finished.
Assigning self IP addresses
With VLANs in place, you can now assign self IP addresses to each Global Traffic Manager.
These self IP addresses identify the Global Traffic Manager on the network.
You must apply the following procedure to both the active and standby systems.
To assign self IP addresses
1
. On the Main tab of the navigation pane, expand Network and then click Self IPs.
2
. Click Create.
3 In the IP address box, type a self IP address to assign to the VLAN for DNS requests.
. For this example, type one of the following:
For gtm1.siterequest.com, type 10.1.1.20
For gtm2.siterequest.com, type 10.1.1.21
4 In the Netmask box, type the appropriate net mask.
. For this example, 255.255.255.0.
5
. From the VLAN list, select VLAN dns_requests.
6
. Click Finished.
Creating a floating IP address
In a redundant system configuration, both Global Traffic Manager systems share a common IP
address called a floating IP address. A floating IP address is an IP address that represents both the
active and standby units in a redundant system. To the rest of the network, this floating IP
address represents the active Global Traffic Manager. If the primary unit goes offline, the
secondary unit takes over traffic destined for the floating IP address. This setup ensures that DNS
traffic flows smoothly even in the event a fail-over occurs.
For this task, you configure only the active system. The settings you create are transferred to the
standby system during a synchronization that you initiate later in this process.
To create a floating IP address
1
. On the Main tab of the navigation pane, expand Network and then click Self IPs.
2
. Click Create.
3 In the IP address box, type the IP address of the system.
. For this example, type 10.1.1.50.
4 In the Netmask box, type the appropriate net mask.
. For this example, 255.255.255.0.
5
. From the VLAN list, select VLAN dns_requests.
6
. Check the Floating IP option.
7
. Click Finished.
Configuring the high availability options
Many of the options associated with creating a redundant system reside in the High Availability
section of the Configuration utility. These options include the IP addresses of each system, the
type of redundant system configuration, and other options.
You must apply the following procedure to both the active and standby systems.
To configure high availability options
1
. On the Main tab of the navigation pane, expand System and then click High Availability.
2
. On the menu bar, click Network Failover.
3
. Click the Network Failover box.
In the Peer Management Address box, delete the colons (::) and type the management IP
4 address of the peer unit.
. For this example, type 192.168.15.17.
5.In the Unicast area, add an entry:
a In the Configuration Identifier box, type a unique name for the unicast entry.
) For this example, type DNS requests.
In the Local Address box, type the self IP address associated with the failover VLAN you
b created on the unit you are configuring.
) For this example, type 10.1.1.20.
In the Remote Address box, type the self IP address associated with the failover VLAN you
created on the peer unit.
c) In this example, type 10.1.1.21.
d
) Click Add.
Note: In this example, for the gtm2.siterequest.com, use 192.168.15.16 for the Peer Management
Address, and reverse the values of the Local Address and Remote Address settings.
Defining an NTP server
The next task of this implementation requires you to define an NTP server that both Global
Traffic Manager systems use during synchronization options. This task is important because it
determines a common time value for both systems. During file synchronizations, the systems use
this time value to see if any newer configuration files exist.
To define an NTP server
1
. On the Main tab of the navigation pane, expand System and then click Configuration.
2
. From the Device menu, choose NTP.
3 In the Address box, type the IP address of the NTP server.
. In this example, 192.168.5.15.
4
. Click Add.
5
. Click Update.
Defining the default gateway route
Another task you must accomplish is defining the default gateway route for network traffic. The
Global Traffic Manager uses this route to send and receive network traffic.
To define the default route
1
. On the Main tab of the navigation pane, expand Network and then click Routes.
2
. Click Add.
3
. From the Type list, select Default Gateway.
4 From the Resource list, select Use Gateway and then type the IP address of default gateway.
. In this example, type 10.1.1.100.
5
. Click Finished.
Defining a listener
The Global Traffic Manager employs a listener to identify the DNS traffic for which it is
responsible. In this implementation, you need to create a listener that corresponds to the floating
IP address shared between the two Global Traffic Manager systems.
For this task, you configure only the active system. The settings you create are transferred to the
standby system during a synchronization that you initiate later in this process.
To configure the listener
1
. On the Main tab of the navigation pane, expand Global Traffic and then click Listeners.
2
. Click Create.
3 In the Destination box, type the IP address on which the system will listen for traffic.
. In this example, type 10.1.1.50.
4
. From the VLAN Traffic list, select All VLANs.
5
. Click Finished.
Running a config sync operation
If you are familiar with Global Traffic Manager, you might be familiar with its synchronization
feature. This feature ensures that all Global Traffic Manager systems share the same information
on wide IPs, pools, and other network configurations associated with DNS traffic management.
For a redundant system, you must employ an additional synchronization option to share the self
IP address, default route, and other information you configured on the active system with the
standby system.
To run a config sync operation
1
. On the Main tab of the navigation pane, expand System and then click High Availability.
2
. On the menu bar, click ConfigSync.
Click Synchronize TO Peer.
3 The system synchronizes settings to the standby Global Traffic Manager; in this example,
. gtm1.siterequest.com.
4
. Click OK.
Defining a data center
The next task is to define the data centers in the Global Traffic Manager. Data centers are
important entities within the Global Traffic Manager; you cannot add other entities, such as
server, without them.
For this task, you configure only the active system. The settings you create are transferred to the
standby system during a synchronization that you initiate later in this process.
To define a data center
1
. On the Main tab of the navigation pane, expand Global Traffic and then click Data Centers.
2
. Click Create.
3 In the Name box, type the name of the data center.
. In this example, type New York Data Center.
4 In the Location box, type the location of the data center.
. For this example, type New York, NY.
5 From the State list, select Enabled.
.
6
. Click Finished.
Defining the Global Traffic Manager systems
At installation, a Global Traffic Manager has no knowledge of itself. To have the Global Traffic
Manager communicate and operate with other systems, you must define it within the user
interface. For this example, you need to define both gtm1.siterequest.com and
gtm2.siterequest.com.
For this task, you configure only the active system. The settings you create are transferred to the
standby system during a synchronization that you initiate later in this process.
To define the Global Traffic Manager
1
. On the Main tab of the navigation pane, expand Global Traffic and then click Servers.
2
. Click Create.
3 In the Name box, type the name of the system.
. In this example, type gtm1.siterequest.com.
4
. From the Product list, select BIG-IP System (Redundant).
5
. For the Address List setting, complete the following tasks:
In the Address box, type the IP address of the system.
In this example, type 10.1.1.20.
Click Add.
6
. For the Peer Address List setting, complete the following tasks:
In the Address box, type the IP address of the second system.
For this example, type 10.1.1.21.
Click Add.
7 From the Data Center list, select a data center.
. In this example, select New York Data Center.
8
. From the Virtual Server Discovery list, select Disabled.
9
. Click Create.
You now repeat this procedure on the second Global Traffic Manager, reversing the IP addresses
in the Address List and Peer Address List options. In this example, you repeat this procedure for
the gtm2.siterequest.com system.
Enabling synchronization
For the next task, you enable the synchronization options and assign an appropriate name for the
synchronization group. For this implementation, the synchronization group name is North
America.
For this task, you configure only the active system. The settings you create are transferred to the
standby system during a synchronization that you initiate later in this process.
To enable synchronization
1 On the Main tab of the navigation pane, expand System, and then click Configuration.
.
2
. From the Global Traffic menu, choose General.
3
. Check the Synchronization check box.
4
. Check the Synchronize DNS Zone Files check box.
5 In the Synchronization Group Name box, type the name of the synchronization group.
. In this example, type North America.
6
. Click Update.
Running the gtm_add script
Next, you need to have the two systems share the same configuration. (For this example, that
means you need to have the Global Traffic Manager in Los Angeles acquire the configurations
established at the New York data center.) You must do this before you attempt to synchronize
these systems; otherwise, you run the risk of having the new Global Traffic Manager, which is
unconfigured, replace the configuration of older systems. To acquire the configuration files, you
run the gtm_add script.
Note: You must run the gtm_add script from the currently unconfigured Global Traffic Manager.
To run the gtm_add script
1 Log on to the unconfigured Global Traffic Manager.
. In this example, log on to gtn2.siterequest.com.
2
. At the command prompt, type gtm_add.
3
. Press the y key to start the gtm_add script.
4 Type the IP address of the configured Global Traffic Manager.
. For this example, type 10.1.1.20.
5
. Press Enter.
The gtm_add process begins, acquiring configuration data from the active Global Traffic
Manager; In this example gtn1.sitequrest.com. Once the process completes, you have
successfully created a redundant system consisting of two Global Traffic Manager systems.

Das könnte Ihnen auch gefallen