Connecting to a server - BlueCat Address Manager - 9.2.0

Address Manager Administration Guide

prodname
BlueCat Address Manager
version_custom
9.2.0

When you add a server to a configuration, you can choose not to connect to that server. The following describes how to connect to a server.

For example, you might do this to add a server to Address Manager that isn't yet physically installed. To connect to the server, use the Connect function from the server’s name menu.

To connect to a server:

  1. From the configuration drop-down menu, select a configuration.
  2. Select the Servers tab. Tabs remember the page you last worked on, so select the tab again to ensure you're on the Configuration information page.
  3. Under Servers, click the name of a server that isn't managed by Address Manager. The Details tab for the server opens.
  4. Click the server name and select Connect.
  5. Under Server, confirm the Management Interface IP address, hostname, and password.
    • Name—enter a name for the server. This name is used only in the Address Manager user interface and isn't associated with deployed DNS data.
    • Management Interface—the IP address assigned to the server.
    • Hostname—the hostname used for the server on the network.
    • Upgrade to latest version—by default, this option is deselected. This provides a safe environment to add an DNS/DHCP Server in Address Manager without applying an unintentional software update. Select the check box only if you wish to apply the latest version of Address Manager software once the appliance is under Address Manager control.
    • Password—enter the server password. For more information on the default server password, refer to BlueCat default login credentials (you must be authenticated to view this topic).
      Note: You must enter a password in order to use the Detect Server Settings button.
  6. Click Detect Server Settings. Address Manager will check the DNS/DHCP Server software version, interface count, state of Dedicated Management, IP address, and redundancy scenario (4-port appliances only).
  7. OPTIONAL: complete the following (available fields depend on the number of interfaces of your DNS/DHCP Server):
    • Service interface—set an IPv4 address and netmask that will be used only for services traffic such as DNS, DHCP, DHCPv6 and TFTP (3 and 4-port appliances only). If Dedicated Management has been previously enabled, you will see the IPv4 address you configured on eth2 in the DNS/DHCP Server Administration Console.
      • IPv6 Address and Subnet—configure an IPv6 address and subnet to the Service interface (eth2). If you assigned an IPv6 address from the DNS/DHCP Server Administration Console during initial set-up of the DNS/DHCP Server, the fields will be automatically populated. For example:
        • IPv6 address: 2001:db8::AC10:FE02
        • Subnet: 64
          Note: The configured IPv6 address is automatically set as the Primary IPv6 address. You must set the Primary IPv6 address BEFORE placing the server under Address Manager control.
          Note: You can't set the IPv6 gateway from the Address Manager user interface. You must configure an IPv6 gateway from the DNS/DHCP Server Administration Console to ensure correct operation of IPv6 functionality.
    • xHA Backbone—select the check box if you want to configure the xHA interface and specify the IPv4 address and netmask to be used.
    • Enable Redundancy—select the check box to enable networking redundancy (4-port appliances only) or deselect to disable network redundancy. From the Scenario drop-down menu, select either Active/Backup or Active/Active (802.3ad).
      Note: You can't enable network redundancy from the Add Server page if any VLAN interfaces are present on the Service interface (eth0). If necessary, remove any configured VLAN interfaces using the DNS/DHCP Server Administration Console, then add the server to Address Manager and enable network redundancy. Once the server is under Address Manager control you can configure VLAN interfaces from the Address Manager user interface (Servers > Service Configuration > Interfaces).

      If you require VLAN Tagging with port bonding, you must first enable bonding then immediately configure VLAN interfaces.

  8. OPTIONAL: Under HSM Support, complete the following:
    Note: In order to enable HSM support on managed DNS/DHCP Servers, you must have previously created an HSM configuration in Address Manager. For complete information on configuring HSM, refer to Configuring HSM.
    • Select the check box, Enable HSM Support. The Add Server page refreshes to show your HSM configuration and a drop-down menu of HSM servers.
    • From the HSM Servers drop-down menu, select an HSM server and click Add. Repeat this step to add multiple HSM servers.
    • To re-order the hierarchy of the HSM servers in the list, select an HSM server and click Move Up or Move Down. The HSM server at the top of the order will be the Primary; HSM servers below the Primary will be the Secondary, Tertiary. Click Remove to delete an HSM server from the list.

    In the General section of the Details tab, you will see Enable HSM Support: Yes — this confirms that HSM has been enabled on the managed BlueCat DNS Server. Also, the HSM Servers section lists the HSM server(s) linked to your managed DNS Server.

  9. Under Change Control, add comments, if required.
  10. Click Connect.