Modifying Service Point network configurations - BlueCat Edge - Service Point v4.x.x

BlueCat Edge User Guide
ft:locale
en-US
Product name
BlueCat Edge
Version
Service Point v4.x.x
Once you have provisioned a Service Point instance, you can continue to deploy services to the service point. If required, you can modify the existing IP address, subnet mask, default gateway, and configured DNS servers of the service point. The following sections outline steps to modify the service point configurations depending on the platform that the service point is provisioned on.
Attention: Updating Service Point configurations when provisioned on AWS, GCP, or Cisco devices

You cannot modify the private IP address settings of the Service Point instance on AWS, GCP, and Cisco devices. To modify the IP address settings, you must provision a new Service Point instance with the updated configurations. With this approach, DNS clients would experience a brief downtime during the Service Point instance provisioning and DNS resolver service deployment process.

Attention: You can only modify the service point network configurations if there are no services bound to the IP addresses being modified. If you have any services listening on the IP addresses to be modified, you must first update the service so that it no longer listens on this address.

For more information on modifying DNS resolver service, refer to Modifying DNS resolver service.

For more information on modifying Identity service, refer to Modifying identity service.

Updating Service Point configurations when provisioned on VMware ESXi, Nutanix, and BlueCat hardware appliances

  1. Log in to the Service Point instance using the operations user and the VM console password through a console session.
    Attention: BlueCat recommends connecting to the Service Point instance using a console session, as the change in network configuration can result in the Service Point instance becoming unreachable using an SSH connection.
  2. Elevate your user permissions by running the following command:
    sudo su
  3. Modify the IP address, subnet mask, DNS servers, and default gateway of the eth0 interface within /etc/network/interfaces.d/50-cloud-init.
    Note: A warning appears at the top of the file stating that the contents of the file will be overwritten upon reboot. This message can be safely ignored, as the VMware network configuration only runs once for each Service Point instance and not upon each reboot.
  4. Save the changes to the file.
  5. Run the following command to reconfigure the eth0 interface with the new settings and restart the platform services:
    fleet newIP

    All services will restart and listen on the new IP address of the Service Point instance.

  6. If you had previously deployed DNS resolver service to the Service Point instance, update DNS resolver service so that it uses the updated IP address. For more information, refer to Modifying DNS resolver service.

While the platform services restart, the Service Point instance will be in an Unhealthy state for a few minutes. During this time, DNS clients will experience a brief downtime.

Updating Service Point configurations when provisioned on Azure

  1. Log in to the Azure portal.
  2. Click Virtual machines.
  3. Click the name of the Service Point instance virtual machine that you are reconfiguring the IP address on.
  4. Click Networking in the side bar and click the name of the network interface attached to the VM.
  5. Click IP configurations in the side bar and click the private IP address of the VM.
  6. Change the IP address configuration of the VM.
  7. Click Save.

    Once you have clicked saved, the VM reboots. After the VM has completed rebooting and its core services have restarted, all services will restart and listen on the new IP address of the Service Point instance.

  8. If you had previously deployed DNS resolver service to the Service Point instance, update DNS resolver service so that it uses the updated IP address. For more information, refer to Modifying DNS resolver service.

The Service Point instance takes at least 5 minutes to reboot on Azure and services take an additional two minutes to restart after the reboot has completed. While the platform services restart, the Service Point instance will be in an Unhealthy state for a few minutes. During this time, DNS clients will experience a brief downtime.

Note: During the restart process, you might see similar messages to the following within the serial console of the VM followed by no logging output for several minutes:
SMBus base address unitialized - upgrade BIOS or use force_addr=0xaddr
This is expected behaviour and does not indicate that an error has occurred during the reboot process.