Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Configure the node VMs

This topic describes the steps required to configure the node VMs to prepare for deployment.

After you have created the node VMs and prepared them, configure the cluster parameters on the VMs before you deploy the Routing Director deployment cluster.

On KVM, Proxmox VE, and VMware ESXi

When all the node VMs are created, perform the following steps to configure the VMs.

  1. Connect to the node VM Web console of the first VM. You are logged in as root automatically.

  2. You are prompted to change your password immediately. Enter and re-enter the new password. You are automatically logged out of the VM.

    Note:

    We recommend that you enter the same password for all the VMs. If you configure different passwords for the VMs, enter the different passwords correctly when requested to Generate SSH keys for the cluster nodes when deploying the cluster.

  3. When prompted, log in again as root user with the newly configured password.

  4. Configure the following information when prompted.

    Table 1: VM Configuration Wizard

    Prompt

    Action

    Do you want to set up a Hostname? (y/n)

    Enter y to configure a hostname.

    Please specify the Hostname

    Enter an identifying hostname for the VM. For example: Primary1. The hostname should be under 64 characters and can include alphanumeric and some special characters.

    If you do not enter a hostname, a default hostname in the format controller-<VM-IP-address-4th-octet> is assigned.

    Note:

    Since you are deploying the cluster from one node and entering the IP addresses of the other nodes during the cluster configuration process, the roles are assigned automatically. In a multinode setup, the first three nodes to be configured are the primary and worker nodes. In a four-node setup, the last node is the worker-only node.

    The hostnames (and whether or not they match the role of the node), will not affect the operations of the cluster. However, for management purposes, we recommend that you pay attention to how you name the nodes and the order in which you entered their addresses during the cluster creation steps.

    We do not support changing the hostname after the cluster has been installed.

    Do you want to set up Static IP (preferred)? (y/n)

    Enter y to configure an IP address for the VM.

    Please specify the IP address in CIDR notation

    Enter the IP address in the CIDR notation. For example, 10.1.2.3/24.

    Your node VMs can be in the same subnet or in different subnets.

    Note:

    If you enter 10.1.2.3 instead of 10.1.2.3/24, you will see an Invalid IP address error message.

    Please specify the Gateway IP

    Enter the gateway IP address.

    Ensure that you enter the gateway IP address corresponding to the network of your node VM.

    Please specify the Primary DNS IP

    Enter the primary DNS IP address.

    Please specify the Secondary DNS IP

    Enter the secondary DNS IP address.

    Do you want to set up IPv6? (y/n)

    Enter y to configure IPv6 addresses.

    If you don't want to configure IPv6 addresses, enter n and proceed to Step 5.

    Please specify the IPv6 address in CIDR notation

    Enter the IPv6 address in the CIDR notation. For example, 2001:db8:1:2::3/64.

    Your node VMs can be in the same subnet or in different subnets.

    Note:

    If you enter 2001:db8:1:2::3 instead of 2001:db8:1:2::3/64, you will see an Invalid IP address error message.

    Please specify the Gateway IPv6

    Enter the gateway IPv6 address.

    Ensure that you enter the gateway IP address corresponding to the network of your node VM.

    Please specify the Primary DNS IPv6

    Enter the primary DNS IPv6 address.

    Please specify the Secondary DNS IPv6

    Enter the secondary DNS IPv6 address.

  5. When prompted if you are sure to proceed, review the information displayed, type y and press Enter.

    You are logged into Deployment Shell.

  6. Repeat steps 1 through 5 for the other VMs in a multinode cluster. Skip this step for a single node deployment.

  7. (Optional) Verify connectivity between the nodes. Log in again to all the node VMs. If you have been logged out, log in again as root with the previously configured password. You are placed in Deployment Shell operational mode. Type exit to enter the Linux root shell of the nodes. Ping the other three nodes from each node using the ping static-ipv4-address command to verify that the nodes can connect to each other.

  8. (Optional) Before you proceed to deploy the cluster, verify that the NTP server(s) is reachable. On any one of the cluster nodes, type start shell. At the # prompt, ping the server using the ping ntp-servers-name-or-address command. If the ping is unsuccessful, use an alternate NTP server.

  9. You have completed the node preparation steps and are ready to deploy the cluster. Go to Deploy the Cluster.

On AWS

Before you configure the node VMS, you must configure the required AWS resources for deployment. Set up security groups to control access to cluster nodes and services, launch EC2 instances, configure storage and networking, and set up target groups and load balancers.

Completing these steps ensures that the necessary images and network security settings are in place.

Go to Provision AWS Compute and Networking Components.

What's Next

To deploy the cluster on KVM, Proxmox VE, and VMware ESXi, go to Deploy the Cluster or to configure the required resources on AWS before deploying the cluster, go to Provision AWS Compute and Networking Components.