Additional configurations after enabling dedicated management - BlueCat Address Manager - 9.1.0

BlueCat DNS for Google Cloud Platform

prodname
BlueCat Address Manager
version_custom
9.1.0

This section describes additional configurations that you must set to reconnect to your virtual appliances after enabling dedicated management.

Connecting to the management port

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.

To reconnect to your instance after enabling dedicated management:

Run the following command to establish your SSH connection to the Dedicated management interface:
ssh -i <key_pair_file_name> bluecat@<dedicated_management_ip>

Adding a static route

After enabling dedicated management, if Address Manager and BlueCat DNS for Google Cloud Platform are not on the same subnet, you must manually add a static route on BlueCat DNS for Google Cloud Platform to allow connectivity to Address Manager via the Dedicated management interface.

To add a static route for Address Manager:

Run the following command to add a static route, indicating the location where the BlueCat DNS for Google Cloud Platform server should send packets:
Adonis> configure network
Adonis:configure:network> add static-route network <BAM_SUBNET/NETMASK> via-address <dedicated_management_interface_gateway_IP>
Note: You may also need to add static routes for the following scenarios:
  • If you are connecting to your VM instance using SSH from a different client, you must add a static route for the new client from which you are connecting.
  • If database replication is enabled, you must add a static route for both Address Manager appliances in replication.
  • You must add a static route to any devices that require access through the dedicated management interface, such as SSH clients and SNMP management servers.