Applies To:

Show Versions Show Versions

Archived Manual Chapter: 3-DNS Administrator Guide v4.1: Adding 3-DNS Controllers to the Network
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

This article has been archived, and is no longer maintained.



5

Adding 3-DNS Controllers to the Network



Working with more than one 3-DNS Controller

When you are working with more than one 3-DNS Controller in your network, and you want the controllers to load balance to the same virtual servers, you can create your entire configuration on one controller and then add the second controller using the 3dns_add script. The 3dns_add script copies the entire configuration from the first controller onto the second controller, and synchronizes all of the settings between the controllers. When you are finished, the first controller acts as the principal controller in the sync group, and the second controller becomes a receiver controller. (For more information about sync groups, see Working with sync groups, on page 2-29 .)

The following sections of this chapter describe the procedures you follow to add a 3-DNS Controller into a network that already has at least one 3-DNS Controller configured and working properly. If you are adding the first 3-DNS Controller to your network, refer to Chapter 2, Essential Configuration Tasks .

Note: If you are adding a second 3-DNS Controller to your network but do not want it to be in the same sync group as your first controller, or you want the second 3-DNS Controller to load balance to a different set of virtual servers, then do not use the 3dns_add script.

Preparing to add a second 3-DNS Controller to your network

Before you run the 3dns_add script on any additional 3-DNS Controllers you are adding to your network, you should complete the following tasks:

  • Physically install the second 3-DNS Controller in its data center. (For more information on hardware installation, see the 3-DNS Installation Guide, or, if you are running the 3-DNS module on the BIG-IP Controller, refer to the BIG-IP Installation Guide.)
  • Run the First-Time Boot utility on the second controller. (For more information on the First-Time Boot utility, see the 3-DNS Installation Guide, or if you are running the 3-DNS module on the BIG-IP Controller, refer to the BIG-IP Installation Guide.)
  • Make the principal 3-DNS Controller aware of the IP address, fully-qualified domain name, and data center location of the second 3-DNS Controller. (See the following section, Making the principal 3-DNS Controller aware of the additional controller .)

    Completing these tasks ensures that when you run the 3dns_add script, the second 3-DNS Controller successfully copies the configuration information from the first 3-DNS Controller.

Installing the hardware and running the First-Time Boot utility

You can find detailed instructions on installing the 3-DNS Controller hardware in the Installation Guide. The Installation Guide also includes detailed instructions on running the First-Time Boot utility. When you have finished this part of the setup for the second controller, do not make any other changes to the configuration.

Note: If you are working with the 3-DNS module on the BIG-IP Controller, please refer to the BIG-IP Installation Guide, which is included in the Administrator Kit. If you are working with the standalone 3-DNS Controller, please refer to the 3-DNS Installation Guide, which is included in the Administrator Kit.

Making the principal 3-DNS Controller aware of the additional controller

Once you have installed the hardware and run the First-Time Boot utility on the new controller, you add its configuration information to the existing 3-DNS Controller. The existing controller becomes the principal controller in the sync group once you run the 3dns_add script on the new controller.

To add the new controller to the existing controller's configuration using the Configuration utility

  1. Add the second data center to the configuration.
  2. In the navigation pane, click Data Centers.
    The Data Centers screen opens.
  3. Click Add Data Center on the toolbar.
    The Add Data Centers screen opens.
  4. Add the information for the data center where you installed the new controller, and click Update.
  5. Add the second 3-DNS Controller to the configuration.
  6. In the navigation pane, expand the Servers item, and click 3-DNS Controllers.
    The 3-DNS Controllers screen opens.
  7. Click Add 3-DNS Controller on the toolbar.
    The Add New 3-DNS Controller screen opens.
  8. Add the information for the new controller and click Update.
  9. Add the new controller to the existing controller's sync group.
  10. In the navigation pane, click 3-DNS Sync.
    The System-Synchronization screen opens.
  11. Click Add to Group on the toolbar.
    The Add a 3-DNS to a Sync Group screen opens.

    c) Check the controller you just defined and click Add.
    The new controller becomes a receiver in the sync group of the existing controller.

    You have now successfully added the new controller to the existing controller's configuration. The following sections describe how to run the 3dns_add script and verify the configuration.

Running the 3dns_add script

You can run the 3dns_add script on the new 3-DNS Controller either using a remote secure shell session, or using a monitor and keyboard connected locally to the controller.

To run the 3dns_add script

  1. At the login prompt, type root.
  2. At the password prompt, type the password you configured when you ran the First-Time Boot utility.
  3. To run the script, type 3dns_add at the command line.
    The script copies the entire configuration of the existing 3-DNS Controller to the new controller.

Verifying the configuration

Once the script finishes, we recommend that you verify the following aspects of your configuration:

  • Verify that each 3-DNS Controller has the necessary agents and daemons running.
  • Verify that any servers you configured are up and available to receive load balancing requests.
  • Verify that any virtual servers you configured are up and available to respond to requests.
  • Verify that any wide IPs you configured are load balancing requests as you configured them.

    You can perform these verification tasks on any of the controllers in the sync group. The following sections describe the verification process in detail.

Tip: You may want to wait a few minutes before you verify the configuration so that the 3-DNS Controllers have time to synchronize with each other.

To verify that each 3-DNS Controller has the necessary agents and daemons running

  1. In the navigation pane, expand the Statistics item and click 3-DNS.
    The 3-DNS Statistics screen opens.
  2. Click the Refresh button.
  3. In the Server and Big3d columns, make sure the status is up, which is indicated by a small green ball.
  4. In the E/D column, make sure the controllers are enabled.
  5. If the status of any of your controllers is down, unknown, or unavailable, wait a few minutes and click Refresh again. If status of the controllers remains down, unknown, or unavailable, contact Technical Support for assistance.

To verify that the servers you configured are up

  1. In the navigation pane, expand the Statistics item and click Data Centers.
    The Data Centers Statistics screen opens.
  2. Click the Refresh button.
  3. In the Server column, make sure that the status of each BIG-IP Controller, EDGE-FX Cache, or host you configured is up, which is indicated by a small green ball.
  4. If the status of any of your servers is down, unknown, or unavailable, wait a few minutes and click Refresh again. If status of the servers remains down, unknown, or unavailable, contact Technical Support for assistance.

To verify that the virtual servers you configured are up

  1. In the navigation pane, expand the Statistics item and click Virtual Servers.
    The Data Centers Statistics screen opens.
  2. Click the Refresh button.
  3. In the OK column, make sure that the status of each virtual server you configured is up, which is indicated by a small green ball.
  4. If the status of any of your virtual servers is down, unknown, or unavailable, wait a few minutes and click Refresh again. If status of the virtual servers remains down, unknown, or unavailable, contact Technical Support for assistance.

To verify that the wide IPs are load balancing properly

  1. At the command prompt, type nslookup and press Enter.
  2. Type the following command where <IP_address> is the IP address of one of your 3-DNS Controllers, and press Enter.

    server <IP_address>

  3. Type the name of the wide IP (for example, news.domain.com) for which you want to verify load balancing and press Enter.

    If the virtual servers belonging to the wide IP appear in a pattern that reflects the load balancing mode you selected, you have successfully configured your 3-DNS Controllers. Note that you can repeat the previous procedure for each wide IP you configured.

    Note: This is the only verification task that you perform from the command line. The nslookup utility is part of DNS distributions. For more information on how to use the nslookup utility, please refer to the book, DNS and BIND, by Albitz and Liu.

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

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)