Enabling dedicated management on BlueCat DNS for Google Cloud Platform - BlueCat Address Manager - 9.3.0

BlueCat DNS for Google Cloud Platform

English (United States)
Product name
BlueCat Address Manager

To enable and use the dedicated management interface on BlueCat DNS for Google Cloud Platform, you must have two interfaces (Service and Management) already configured on your instance.

Attention: To enable multiple interfaces on an instance in BlueCat DNS for Google Cloud Platform, each interface must be in a different virtual private cloud (VPC). For more information on configuring multiple interfaces, refer to https://cloud.google.com/vpc/docs/create-use-multiple-interfaces.
Note: BlueCat DNS for Google Cloud Platform virtual appliances already in production must be removed from Address Manager control before enabling dedicated management.

To remove BlueCat DNS for Google Cloud Platform from Address Manager control:

  1. From the Address Manager user interface, disable the server:
    1. Select the Servers tab, then click the name of the multi-interface server.
    2. Click the server name and select Disable.
  2. From the BlueCat DNS for Google Cloud Platform Administration Console, run the following commands to remove the server from Address Manager control:
    Adonis> configure system
    Adonis:configure:system>set state no-proteus-control

To enable dedicated management:
  1. Connect to your instance as the admin user via an SSH connection to the Services interface:
    ssh -i <key_pair_file_name> admin@<service_interface_ip>
  2. From Main Session mode, run the following commands to enable dedicated management:
    Adonis> configure interfaces
    Adonis:configure:interfaces>set dedicated-management enable
    Enabling dedicated management will disconnect your SSH connectivity to the Services interface. Once you enable dedicated management, you must re-establish the SSH connection to the Management interface.
    Note: You must enable dedicated management using an SSH connection. When you connect to the instance using SSH, a static route is created using the IP address of the SSH client which is required to connect to the management interface. Connecting through the serial console does not create the static route, resulting in the dedicated management configuration to fail.