Provision Fleet Service Points on Cisco ENCS devices - BlueCat DNS Edge

DNS Edge User Guide (Fleet Service Point)

Locale
English
Product name
BlueCat DNS Edge

This section gives detailed instructions for provisioning a Fleet Service Point on Cisco ENCS devices.

Prerequisites:

The following prerequisites must be met before you begin:
  • You have a Cisco ENCS device running ENCS5408/K9 NFVIS-4.1.1-FC1
  • The Cisco ENCS device must have at least 2 CPU cores and 3 GB of RAM
  • The Cisco ENCS device must be configured with internet connectivity and allow internet connectivity for VMs
Downloading the Fleet Service Point tarball image:
  1. Log in to the Edge Cloud Instance.
  2. In the top navigation bar, click and select Fleet Service Points.
  3. Click on the Fleet Service Points page. The Download Fleet Service Point Image window appears.

  4. From the drop-down menu, select Cisco ENCS.
  5. Click next to Image to download the Fleet Service Point tarball image.
    Note: You can use the same tarball image to provision multiple Fleet Service Points.
  6. Click next to Checksum to download the Fleet Service Point tarball image checksum file.
Configuring Fleet Service Point configuration details:
  1. To add a new Fleet Service Point, click on the Fleet Service Points page.
  2. Under Setup, enter the following information:
    • Name: enter the name of the new Fleet Service Point.
    • Description: add a description. This is optional.
  3. Under Type, select Cisco ENCS from the drop-down menu.
  4. Click Save and Download. A window appears where you can copy the configuration information.
  5. Click the copy icon next to the Registration Key and Registration Endpoint values.
    Attention: The registration key and registration endpoint of the Fleet Service Point can only be retrieved at this point and cannot be recovered later. These values are required when configuring the VM on Cisco ENCS.
Provisioning a Fleet Service Point on Cisco ENCS:
  1. Log in to the Cisco NFVIS portal on the Cisco ENCS device.
  2. Navigate to VM Life Cycle > Deploy.
  3. Click and drag an OTHER instance onto the VM deployment diagram.
  4. Click and drag the OTHER instance circle towards the network that you wish to connect to with the VM.
  5. Click the OTHER instance circle and enter the following information:
    • VM Name: enter the name of the Fleet Service Point virtual machine.
    • Image: select the Fleet Service Point tarball package that was downloaded when you created the Fleet Service Point.
    • Profile: this field is populated when you upload the Fleet Service Point image. The profile name is DefaultEdgeFleetProfile.
    • VNC Password: leave this field empty.
    • HOSTNAME: enter the hostname of the Fleet Service Point virtual machine.
    • REGISTRATION KEY: enter the registration key returned from the creation of the Fleet Service Point in the Edge UI.
      Attention: Once you have entered the registration key, it becomes invalidated upon the provisioning of the Fleet Service Point. To configure an additional Fleet Service Point, you must use a new registration key.
    • REGISTRATION ENDPOINT: enter the registration endpoint URL returned from the creation of the Fleet Service Point in the Edge UI. For example, https://service-layer.us.fleet.bluec.at.
    • SSH PUB KEY: enter a public key that corresponds with a private key to use to SSH into the virtual machine.
      Note: The SSH Public Key is applied to the operations user account.
    • IPV4 ADDR: enter the IPv4 address of the Fleet Service Point virtual machine.
    • IPV4 NETMASK: enter the IPv4 subnet mask of the network where the Fleet Service Point virtual machine will be provisioned.
    • IPV4 GATEWAY: enter the IPv4 gateway address of the network.
    • DNS SERVERS: enter a list of IP addresses of DNS servers used by the Fleet Service Point virtual machine. The list must be in JSON list format. For example: ["8.8.8.8"] for a single DNS server or ["1.1.1.1", "8.8.8.8"] for multiple DNS servers.
      Note:
      • If you do not want to configure any DNS servers, you must enter an empty list. For example: [].
      • If you do not configure any DNS servers, the Fleet Service Point will use 8.8.8.8 as the default DNS server.
    • NTP SERVERS: enter a list of IP addresses or FQDNs of NTP servers used by the Fleet Service Point virtual machine. The list must be in JSON list format. For example: ["1.2.3.4"] for a single NTP server or ["ntp.example.com", "ntp2.example.com"] for multiple NTP servers.
      Note:
      • If you do not want to configure any NTP servers, you must enter an empty list. For example: [].
      • If you do not configure any NTP servers, the Fleet Service Point will use the following default Debian NTP servers:
        • 0.debian.pool.ntp.org
        • 1.debian.pool.ntp.org
        • 2.debian.pool.ntp.org
        • 3.debian.pool.ntp.org
    • (Optional) If you are configuring the Fleet Service Point to use an HTTP proxy, enter the following information:
      • PROXY SCHEME: enter the proxy scheme. For example, http.
      • PROXY HOST: enter the IP address of the proxy.
      • PROXY PORT: enter the port number to connect to the proxy. By default, the value is 443.
      • PROXY USERNAME: enter the username to authenticate with the proxy.
      • PROXY PASSWORD: enter the password to authenticate with the proxy.
    • CONSOLE PASSWORD: Enter the console password for the Fleet Service Point. The password must meet the following requirements:
      • It must contain lowercase characters
      • It must contain uppercase characters
      • It must contain numbers
      • It must contain symbols
      • It must not contain spaces
      • It must contain at least 12 characters
    • Deployment Disk: select a disk where the Fleet Service Point will be provisioned.
    • Leave the Add Storage configurations unset.
  6. Click Deploy.

Once you have provisioned the Fleet Service Point VM, you can deploy DNS resolver service. For more information, refer to DNS Resolver Services.

Attention: You can use the Fleet Service Point diagnostics API to verify that the Fleet Service Point has successfully registered. The registrationStatus field within the Fleet Service Point diagnostics API response returns a value of REGISTERED when the Fleet Service Point has successfully registered with the DNS Edge Cloud. If the value is not REGISTERED, this may indicate that there is an issue with the Fleet Service Point provisioning and the service point may not operate as intended.

For more information on the Fleet Service Point diagnostics APIs, refer to Fleet Service Point status and diagnostics APIs.