HP Multi-Site Traffic Director sa9200 - Manual (Page 25)

C H A P T E R 3 Custom/Manual Configuration
19
SA9200. Secondaries get their configuration from their designated
primary SA9200 and store a copy of the received configuration
locally. Should a secondary be unable to contact a primary it
functions normally using its stored configuration. All SA9200s have
the same picture of the current Agent metrics and are equally capable
of responding. Should one fail the existing DNS protocol
automatically routes requests to the non-failed SA9200s.
The theoretical secondary ns2.xyz-ex.com (IP 10.100.68.2) can re-
solve requests for www.somedomain.xyz-ex.com by becoming a sec-
ondary of the SA9200 at 10.54.67.2. From the CLI on the proposed
second SA9200, execute the command:
NOTE: User-entered
names and IP addresses
in the example are for
illustrative purposes
only. The appropriate
values for your
installation may vary. #config dns secondary 10.54.67.2
Warning: Your current dns configurations will
be lost.
Are you sure you want to become a Secondary
(Yes/No):yes
Now running as a Secondary.
If the DNS configuration of 10.54.67.2 is changed, the new
configuration can be propagated to 10.100.68.2 by the
commit all
command.
Creating
Agents
NOTE: An HP Traffic
Director refers to an HP
Traffic Director Server
Appliance, Models
SA7200 and SA7220; or
HP e-Commerce Traffic
Director Server
Appliance, Models
SA8200 and SA8220. An agent refers to the HP Traffic Director at each site. They are used
to keep the SA9200 informed of site status, response time, and
number of current connections of the server farm they are balancing.
To add an agent, type the following:
HP SA9200# config dns agents create lb1 ip
10.54.67.4
HP SA9200# config dns agents create lb2 ip
10.100.68.4