A10 Harmony Controller Installation

A10 Harmony Controller can be installed on one of the following types of infrastructure resources:

  • A10 Hardware Appliances
    • Harmony Controller 2000

    • Harmony Controller 8000

  • Bare metal or Virtual Machines provided by the customer

Installation Steps

Follow the steps to install Harmony Controller software on bare metal or virtual machines:

  1. Prepare the environment

    Prepare Linux machines (physical or virtual) with required CPU, memory, storage and network settings as described in the prerequisite section below. In case of A10 hardware appliances, virtual machine images of appropriate sizes are already loaded in the appliances.

  2. Download the Harmony Controller Installer

    Harmony Controller installer is a set of three tar files, one of which contains the installation scripts. The other two files contain other required packages and the images. All the three tar files need to be downloaded on the node where Harmony controller will be installed.

    [tar file 1: <<path/HC-5.3.0-P1-install-GA.tar.gz>>]
    [tar file 2: <<path/HC-5.3.0-P1-envsetup-GA.tar.gz>>]
    [tar file 3: <<path/HC-5.3.0-P1-images-GA.tar.gz>>]
    

    This step is not required for A10 hardware appliances as the installer packages are already loaded in the appliances.

  3. Unpack and run install script

    Unpack the installer tar file using the command below.

    [tar -zxvf <<path to the install file/HC-5.3.0-P1-install-GA.tar.gz>>]
    

    Unpacking the tar file will create a folder in the current directory with installation scripts in it.

    [folder: a10-harmony-controller-HC-5.3.0-P1]
    

    The folder contains “InstallHC” file, which is the main installer script to install Harmony Controller. Running the script will trigger the user prompts for required input and installation. Installation will take 30-45 minutes to complete.

Prerequisites

Network Prerequisites

To allow devices (Lightning ADC, Thunder ADC) to connect to the controller, the following ports need to be opened for ingress traffic on the node where Harmony Controller is installed.

_images/network_setup.png
  • List of ports on which traffic must be allowed from all sources (allow all)

    TCP

    443, 2222, 5671, 9093, 9094, 25500

    Important

    TCP port 5671 is required for LADC load balancer devices. TCP port 9094 must be opened for IPv6 deployment.

  • List of ports on which traffic must be allowed only from within the private subnet where Harmony Controller is deployed (restricted source originator)

    TCP

    83, 2379, 2380, 3300, 6443, 6783, 6789, 6820, 8081, 8087, 8443, 9092, 9898, 10250

    UDP

    123

Note

All IP addresses assigned to the nodes must be static IP addresses. If the IP address of a Harmony Controller node changes, Harmony Controller does not work. For more information, see maintenance information section.

External Access Prerequisites

  • If A10’s Global License Manager Access will be used to manage Harmony Controller and device licenses, all the three nodes should have outbound 443 access to reach the A10 Global License Manager from Harmony Controller.

    • DNS Server — DNS server must be configured on the nodes so that A10 Global License Manager URL can be resolved.

  • NTP Server — date and time of the nodes should be in sync during installation. NTP connectivity is required to node0 from node1 and node2. To set the NTP server, refer to Network Time Protocol section.

Installation on Bare metal or Virtual Machines

Harmony Controller software can be installed on any generic hardware servers or virtual machines. Two types of deployments are supported.

  • One node installation

    Installation on one physical or virtual machine.

  • Three node (High Availability) installation

    Installation on three physical or virtual machines.

Note

For disaster recovery, you need to set two identical Harmony Controller environments. For example, for a three node installation, you must set additional identical three node setup.

Resources Prerequisites

Operating System

Harmony Controller software can be installed on a Linux machine deployed in any environment. Please refer to the list of supported Linux distributions and versions below. Only US-English language versions are supported.

Supported Versions
Standard distribution, Centos 7.6, Centos 7.7, Centos 7.8, Centos 7.9, RHEL 7.6, RHEL 7.7, RHEL 7.8, RHEL 7.9

CPU and Memory

These are the recommended specs:

  • One node installation — 16 VCPUs and 64 GB RAM

  • Three node installation — 8 VCPUs and 32 GB RAM for each node

File System and Kernel

For Harmony Controller installation, kernel version of the Linux distribution is required to be 3.10.0-1127.el7.x86_64 (or higher) and the disk partition file system type should be XFS with fstype=1.

Storage

  • Persistent storage — It is recommended to use persistent storage when deploying Harmony Controller to keep the data intact in case of a node failure. In the event of a node failure, the storage can be attached to a new node for faster recovery. In case of public deployments external persistent storage volumes such as AWS Elastic Block Storage, Google Persistent Disk or Azure Disk can be used as the persistent data store for Harmony Controller deployment.

  • High speed storage — It is also recommended to use a storage disk with high IO (~2000 IOPS) for optimal performance of Harmony Controller.

  • Minimum storage size — The minimum storage required for one-node lab deployment is 110 GB. However, 1 TB storage is recommended for production deployment that requires storage for analytics, logs, and configuration data for longer duration. The size of the storage should be allocated based on:

    • The number of Thunder devices that would be managed from the Harmony Controller deployment.

    • The number of application services deployed on the Thunder devices.

    • The volume of traffic flowing through the Thunder devices.

The storage requirements and best practices discussed above for one-node deployment also apply to each node in a three node deployment.

Storage Setup

  • One Node deployment

    It is recommended to install Harmony Controller on a disk partition different from where node operating system (OS) is installed. This will ensure that Harmony Controller data is kept separate from the OS data. The OS is typically installed on the ‘/boot’ partition of the disk and Harmony Controller can be installed in ‘/’ partition on the same of a different disk. Please refer to the two example images below.

    Example 1:
    _images/installbaremetal_example1.png
    Example 2:
    _images/installbaremetal_example2.png

    The install script will prompt for the mount point for the partition where Harmony Controller will be installed.

  • Three Node deployment

    The three node deployment requires additional storage setup on top of the setup described for a one node deployment above. It requires an additional unmounted disk of minimum size of 100GB to be available on each of the three nodes. This unmounted disk is needed for running Ceph tool to monitor the Harmony Controller system status and overall storage management in the Harmony Controller deployment.

    Refer to the image below for an unmounted disk (‘sdb’) for reference:

    _images/installbaremetal_sdb.png

    The install script will additionally prompt for this unmounted storage for each node and will mount it automatically.

Checking System Readiness

A script to validate system readiness for Harmony Controller installation or upgrade checks whether the system meets the following criteria.

Note

Installation and upgrade scripts are run using a root Provider account or a non-root account with sudo access.

  • /tmp volume has exec permissions. The volume must not be mounted with noexec option.

    Tip

    Check if /tmp is mounted with noexec option:

    cat /proc/mounts | grep /tmp
    

    If you see noexec listed in mount-options used, please remount without noexec:

    mount -o remount,exec /tmp
    
  • Hostname of a node does not contain dot (.) character.

    Tip

    You can change the hostname with hostamectl / hostname command. For example, hostname hc-10-XX-XX-XX

  • IP forwarding is enabled.

    Tip

    To enable IP forwarding, open sysctl.conf using vi /etc/sysctl.conf Add or update line net.ipv4.ip_forward = 1 Reload sysctl with sysctl -p

  • IPv6 is enabled on the node.

    To enable IPv6 in kernel:

    1. Edit /etc/default/grub and change the value of kernel parameter ipv6.disable from 1 to 0 in line GRUB_CMDLINE_LINUX

    2. Regenerate a GRUB configuration file and overwrite existing one using the command grub2-mkconfig -o /boot/grub2/grub.cfg

    3. Restart the system with command reboot

    To enable IPv6 in sysctl:

    1. To get IPv6 running online, comment out or remove the following lines in /etc/sysctl.conf

      # cat /etc/sysctl.conf | grep ipv6
      # net.ipv6.conf.all.disable_ipv6 = 1 ### either comment/remove this line or change its value from 1 to 0
      # net.ipv6.conf.default.disable_ipv6 = 1 ### either comment/remove this line or change its value from 1 to 0
      
    2. Re-read the configuration file /etc/sysctl.conf

      sysctl -p
      
  • SELinux is running in Permissive mode

    Tip

    You can change SELinux mode using command setenforce Permissive Modify /etc/selinux/config file to update SELINUX=permissive to change it permanently

  • Root volume has minimum 10 GB free disk-space

  • In case of upgrade, kubernetes certificates are not expired

  • Optionally, you can validate that enough disk-space is available for installing Harmony Controller (Minimum: 110 GB, Recommended: 1 TB)

  • Optionally, you can validate that enough disk-size is allocated for Ceph volume that will be used as shared storage among multiple nodes of Harmony Controller.

Script sample:

# [root@hc-10-XX-X-XX a10-harmony-controller-HC-5.3.0-P1]# ./pre-install-upgrade-validations.sh

OR

# [admin@hc-10-XX-X-XX a10-harmony-controller-HC-5.3.0-P1]# sudo ./pre-install-upgrade-validations.sh

To perform disk validations, you can add –disk-partition and –ceph-partition parameters.

# [root@hc-10-XX-X-XX a10-harmony-controller-HC-5.3.0-P1]# ./pre-install-upgrade-validations.sh --disk-partition /a10vol/ --ceph-partition /dev/sdb

During the installation and upgrade the validation script runs automatically. If validation fails, installation or upgrade does not start until these issues are fixed.

One Node Installation

_images/1node.png

Before You Begin

  • Make sure all prerequisites are met.

  • Keep the following information ready:

    • Number of nodes

      Number of nodes being used for this installation. In this case it is 1.

    • Type of IP address version

      Version of the IP address that is being allocated to the Harmony Controller. Options are IPv4 or IPv6 or Dual.

    • IP address of the node

      This IP address is assigned to the Harmony Controller node. Please note that the Harmony Controller IP address can’t be changed after deployment without impacting it.

    • Mount point of the storage

      As described in the prerequisite storage section, mount point of the disk partition where Harmony Controller will be e-installed..

    • Type of storage disk

      Type of the storage disk on the node where Harmony Controller is being installed. Options are Hard Disk Drive (HDD) and Solid State Drive (SDD).

    • Password for super-admin user

      A password for the super-admin user that will be used to login to Harmony Controller after deployment.

    • Password for operator console user

      A password for the operator console user that will be used to login to Harmony Controller operator console after deployment.

    • Subnet range

      A subnet range (with 512 IP addresses) for the Harmony Controller’s internal network. If no subnet range is provided, installer will use a default subnet range.

    • TAR file path

      Download the install scripts or required docker images and other packages (to place in any one VM before running the deployment) from the support website . To avoid running out of space during installation, the downloaded files should be kept in the same storage volume where the installation is planned. Please go through the Release Notes before you proceed for compatibility information with other A10 product versions.

Install Harmony Controller Software

  1. Run the following commands to unpack install script bundle and extract the installer script:

    $ tar -zxvf HC-5.3.0-P1-install-GA.tar.gz
    $ cd a10-harmony-controller-HC-5.3.0-P1/
    
  2. Run the following command for installing the controller:

    $ sudo su
    

    # ./InstallHC

The installer script will prompt for the required information. When deploying Harmony Controller on a VM in the cloud such as AWS or OCI, you must add the parameter –iscloudsetup to the installation script and set it to Y as shown next:

$ sudo su
# ./InstallHC --iscloudsetup Y

One node installation may take about 40 minutes. Once the installation is complete, user will see the following successfully deployed message on the screen.

_images/suceess-msg.png

In case the installation does not complete properly, refer to the installation log file available in the logs sub-directory inside installer directory. <installer script directory>/logs/<log file name>

Next Steps

  • Configure SSL certificates for FQDN and email server using A10 Harmony Controller Operator Console in the Certificate section under Configuration Management.

  • Register your Thunder devices.

  • Log in to Harmony Portal to manage Thunder devices and/or creating Lightning ADC cluster and application.

  • Setup scripts for transferring scheduled backup files to external storage as described in maintenance information.

Three Node Installation

_images/3node.png

Before You Begin

  • Ensure all prerequisites are met.

  • SSH Key Set-up and Linux user setup as described below.

  • Name of unmounted partition or disk and as described in the prerequisite storage section.

Keep the following information ready:

  • Number of nodes

    Number of nodes being used for this installation. In this case it is 3.

  • Type of IP address version

    Version of the IP address that is being allocated to the Harmony Controller. Options are IPv4 or IPv6 or Dual.

  • IP address of NodeZero

    This IP address is assigned to the NodeZero. For dual stack, user needs to provide IPv4 and IPv6 addresses. Please note that the Harmony Controller IP address can’t be changed after deployment without impacting it.

  • IP address of NodeOne

    This IP address is assigned to the NodeOne (not NodeZero). For dual stack, user needs to provide both IPv4 and IPv6 addresses. Please note that the Harmony Controller IP address can’t be changed after deployment without impacting it.

  • IP address of NodeTwo

    This IP address is assigned to the NodeTwo (not NodeZero or NodeOne). For dual stack, user needs to provide both IPv4 and IPv6 addresses. Please note that the Harmony Controller IP address can’t be changed after deployment without impacting it.

  • Mount point of the storage

    As described in the prerequisite storage section, mount point of the disk partition where Harmony Controller will be installed.

  • Type of storage disk

    Type of the storage disk on the node where Harmony Controller is being installed. Options are Hard Disk Drive (HDD) and Solid State Drive (SDD).

  • Password for super-admin user

    A password for the super-admin user that will be used to login to Harmony Controller after deployment.

  • Password for operator console user

    A password for the operator console user that will be used to login to Harmony Controller operator console after deployment.

  • Tar file path

    Directory where the three Harmony Controller installer tar files are located.

  • NodeOne ssh user

    User name for the SSH user on NodeOne. This user must have sudo permissions.

  • NodeOne ssh user key

    Path to the SSH private key for login to NodeOne.

  • NodeTwo ssh user

    User name for SSH user on NodeTwo. This user must have sudo permissions.

  • NodeTwo ssh user key

    Path to the SSH private key for login to NodeTwo.

  • Cloud Environment

    User to confirm if the controller deployment resides in any of the public clouds for example AWS, Azure, GCP, OCI or OpenStack.

  • Floating IP address

    A floating IP address is assigned to the elected master node. In case this node fails, the floating IP address is automatically moved to the next elected master node. All external communication happens through the floating IP address. This IP address must be an unused IP address in the same subnet as nodes. All the IP addresses should be either IPv4 or IPv6 or dual stack. For dual stack, user needs to provide both IPv4 and IPv6 addresses. This feature is not available in cloud environments (AWS, Azure, GCP, OCI, and OpenStack).

  • Virtual Router Identification

    Harmony Controller uses Virtual Router Redundancy Protocol (VRRP) for moving Floating IP address among the nodes. The Virtual Router ID is a number between 1 and 255 that uniquely identifies group of devices in the network subnet. Assign an unique Virtual Router ID for the Harmony Controller.

  • Subnet range

    A subnet range (with 512 IP addresses) for the Harmony Controller’s internal network. If no subnet range is provided, installer will use a default subnet range.

SSH Key Set-up

SSH keys needs to be set-up so that nodes can be accessed programmatically without prompting for password during installation. Follow the steps to generate a SSH key pair for the nodes. The key pair is created on the NodeZero and the public key needs to be copied to the other two nodes. Path of the private key file will be provided to the installer script.

  1. Generate a key on NodeZero using:

    ssh-keygen -t rsa -N ''
    
  2. Create .ssh directory on NodeOne and NodeTwo using the following command for each node:

    ssh <user>@<node> mkdir -p .ssh
    
  3. Upload the generated public key to NodeOne and NodeTwo using the following command for each node:

    cat ~/.ssh/id_rsa.pub | ssh <user>@<node> 'cat >> .ssh/authorized_keys'
    
  4. Set permissions for the .ssh directory and uploaded public key file on NodeOne and NodeTwo using the following command on each node:

    ssh <user>@<node> "chmod 700 .ssh; chmod 640 .ssh/authorized_keys"
    

To use pre-existing SSH keys refer Use Pre-existing SSH Keys .

Linux User Set-up

Because passwordless SSH between the 3 nodes is mandatory for HC installation, if you have not setup key-based SSH, then these steps are required. To run sudo without password on CentOS Linux, follow the steps below:

  1. Backup /etc/sudoers file, run:

    sudo cp /etc/sudoers /root/sudoers.bak
    
  2. Edit the /etc/sudoers file on CentOS:

    sudo visudo
    
  3. Append the line to the sudoers file:

    admin ALL=(ALL) NOPASSWD:ALL
    
  4. Save and exit the file.

    Download the install scripts or required docker images and other packages (to place in any one VM before running the deployment) from the support website .

    To avoid running out of space during installation, the downloaded files should be kept in the same storage volume where the installation is planned. Please go through the Release Notes before you proceed for compatibility information with other A10 product versions.

Install Harmony Controller Software

Run the following commands to unpack install script bundle and extract the installer script:

$ tar -zxvf HC-5.3.0-P1-install-GA.tar.gz
$ cd a10-harmony-controller-HC-5.3.0-P1/

Run the following command for installing the controller:

$ sudo su
# ./InstallHC

The script will prompt for the required information. Follow the on-screen instructions to provide the inputs. When deploying Harmony Controller on a VM in the cloud such as AWS or OCI, you must add the parameter –iscloudsetup to the installation script and set it to Y as shown next:

$ sudo su
# ./InstallHC --iscloudsetup Y

Three node installation will take about an hour. Once the installation is complete, user will be see the following successfully deployed message on the screen.

_images/suceess-msg.png

In case the installation does not complete properly, refer to the installation log file available in the logs sub-directory inside installer directory. <installer script directory>/logs/<log file name>

Next Steps

  • Configure SSL certificates for FQDN and email server using A10 Harmony Controller Operator Console in the Certificate section under Configuration Management.

  • Register your Thunder devices.

  • Log in to Harmony Portal to manage Thunder devices and/or creating Lightning ADC cluster and application.

  • Setup scripts for transferring scheduled backup files to external storage as described in maintenance information.

Installation on A10 Hardware Appliances

Harmony Controller software can be installed on the Hardware appliances and Harmony Controller 2000 and Harmony Controller 8000 are the two models available.

KVM hypervisor is installed on these appliances and VMs are created on top of the KVM. Software installation happens on the VMs inside these appliances.

Following four combinations of the appliances are possible:

  • One Harmony Controller 2000 Appliance

    One VM inside the appliance

  • Three Harmony Controller 2000 Appliance

    Three total VMs: 1 in each appliance

  • One Harmony Controller 8000 Appliance

    One VM inside the appliance

  • Three Harmony Controller 8000 Appliance

    Three total VMs: 1 in each appliance

Hardware PreRequisites

Before starting to install Harmony Controller software on the appliances, following steps are to be carried out:

  1. Mount the appliances in a rack, connect power supply and other cables as described in the Installation Guide of the appliance.

  2. Set-up IP address for the appliances and change the default admin login password as described in the Quick Start Guide.

Please refer the documents shipped with the appliances for the detailed instructions of the steps above. Alternately, the docs are available at following locations:

Software Installation on one Harmony Controller 2000 Appliance

In case of one Harmony Controller 2000, one VM (node) is placed in the appliance and controller software is installed in that VM.

_images/HC2000.png

Before You Begin

  • Make sure all Prerequisites and Hardware PreRequisites are met.

  • Keep the following information ready:

    • Number of Appliances

      Installation can be done on 1 or 3 appliances as described in various sections in this document. As in this case installation is being done on 1 appliance, the answer should be 1.

    • IP address (IPv4 or IPv6 or dual stack) and Subnet prefix for NodeZero

      This IP address and Subnet mask will be assigned to the NodeZero after it is created and note that the IP address cannot be changed. All the IP address should be either IPv4 or IPv6 or dual stack. For dual stack, user needs to provide IPv4 and IPv6 addresses. This IP address may belong to different subnet from Appliance IP address as per your organizational policies. Keeping it in the same Subnet also works well.

    • Gateway IP address for NodeZero

      Gateway address of the Subnet where NodeZero is placed.

    • DNS IP address for NodeZero

      IP address of DNS server that NodeZero can use.

    • Password for root provider administrator

      Any password can be kept as per the password policy displayed at the time of installation.

    • Password for operator

      Operator Console is to manage and monitor Harmony Controller installation. User name for operator is ‘admin’. Any password can be kept as per password policy displayed at the time of installation.

    • Internal Subnet

      Assign an internal IP address range of 512 IP address to be used for all internal networks.

Install Harmony Controller Software

Following are the steps for installing Harmony Controller Software on appliance:

  1. Log in to Harmony Controller 2000 appliance as user admin with your password.

  2. Go to /a10data folder:

    # cd /a10data
    
  3. Type the following command to start the installation script:

    $ sudo su
    

    # StartHC

The script is interactive and will prompt for information. Follow the on-screen instructions and provide the value of items asked.

Next Steps

  • Configure SSL certificates for FQDN and email server information using A10 Harmony Controller Operator Console in the Certificate section under Configuration Management.

  • FQDN should be mapped to Floating IP address.

  • Setup scripts for transferring scheduled backup files to external storage as described in maintenance information.

Software Installation of Cluster on Three Harmony Controller 2000 Appliances

In case of three Harmony Controller 2000 appliances, three VMs (nodes) are placed in the appliances (one in each appliance). The controller software is installed in those VMs.

_images/2HC2000.png

Before You Begin

  • Make sure all Prerequisites and Hardware PreRequisites are met.

  • Keep the following information ready:

    • Number of Appliances

      Installation can be done on 1 or 3 appliances as described in various sections in this document. As in this case installation is being done on 3 appliance, the answer should be 3.

    • IP address for First Appliance

      This is the IP address for the first appliance.

    • IP address for Second Appliance

      This is the IP address for the second appliance.

    • IP address (IPv4 or IPv6 or dual stack) and Subnet prefix for NodeZero

      This IP address and Subnet mask will be assigned to the NodeZero after it is created and note that the IP address cannot be changed. All the IP address should be either IPv4 or IPv6. For dual stack, user needs to provide IPv4 and IPv6 addresses. This IP address may belong to different subnet from Appliance IP address as per your organizational policies. Keeping it in the same subnet also works well.

    • Gateway IP address for NodeZero

      Gateway address of the subnet where Node zero is placed.

    • DNS IP address for NodeZero

      IP address of DNS server that NodeZero can use.

    • IP address (IPv4 or IPv6 or dual stack) and Subnet prefix for NodeOne IP

      This IP address and Subnet mask will be assigned to the NodeOne and note that the IP address cannot be changed. All the IP address should be either IPv4 or IPv6 or dual stack. For dual stack, user needs to provide IPv4 and IPv6 addresses.

    • Gateway IP address for NodeOne

      Gateway address of the Subnet where NodeOne is placed.

    • DNS IP address for NodeOne

      IP address of DNS server that NodeOne can use.

    • IP address (IPv4 or IPv6 or dual stack) and Subnet prefix for NodeTwo IP

      This IP address and Subnet mask will be assigned to the NodeTwo and note that the IP address cannot be changed. All the IP address should be either IPv4 or IPv6 or dual stack. For dual stack, user needs to provide IPv4 and IPv6 addresses.

    • Gateway IP address for NodeTwo

      Gateway address of the Subnet where NodeTwo is placed.

    • DNS IP address for NodeOne

      IP address of DNS server that NodeTwo can use.

    • Password for root provider administrator

      Any password can be kept as per the password policy displayed at the time of installation.

    • Password for operator

      Operator Console is to manage and monitor Harmony Controller installation. User name for operator is ‘admin’. Any password can be kept as per password policy displayed at the time of installation.

    • Floating IP Address (IPv4 or IPv6 or dual stack)

      A floating IP address is assigned to the NodeZero. In case this node fails, the floating IP address is automatically moved to the next NodeZero. All external communication happens through the floating IP address. All the IP address should be either IPv4 or IPv6 or dual stack. For dual stack, user needs to provide IPv4 and IPv6 addresses. This IP address must be an unused IP address in the same subnet as nodes.

    • Virtual Router Identification

      Harmony Controller uses Virtual Router Redundancy Protocol (VRRP) for moving Floating IP among the nodes. The Virtual Router ID is a number between 1 and 255 that uniquely identifies group of devices in the network subnet. Assign an unique Virtual Router ID for the Harmony Controller.

    • Internal Subnet

      Assign an internal IP address range of 512 IP address to be used for all internal networks.

Install Harmony Controller Software

Following are the steps for installing Harmony Controller Software on appliance:

  1. Log in to Harmony Controller 2000 appliance as admin with your password.

  2. Go to /a10data folder:

    # cd /a10data
    
  3. Type the following command to start the installation script:

    $ sudo su
    

    # StartHC

The script is interactive and will prompt for information. Follow the on-screen instructions and provide the value of items asked.

Next Steps

  • Configure SSL certificates for FQDN and email server information using A10 Harmony Controller Operator Console in the Certificate section under Configuration Management.

  • FQDN should be mapped to Floating IP address.

  • Setup scripts for transferring scheduled backup files to external storage as described in maintenance information.

Software Installation of Cluster on one Harmony Controller 8000 Appliance

In case of one Harmony Controller 8000, one VM (node) is placed in the appliance and controller software is installed in that VM.

_images/HC8000.png

Before You Begin

  • Make sure all Prerequisites and Hardware PreRequisites are met.

  • Keep the following information ready:

    • Number of Appliances

      Installation can be done on 1 or 2 appliances as described in various sections in this document. As in this case installation is being done on 1 appliance, the answer should be 1.

    • IP address (IPv4 or IPv6 or dual stack) and Subnet prefix for NodeZero

      This IP address and Subnet mask will be assigned to the NodeZero after it is created and note that the IP address cannot be changed. All the IP address should be either IPv4 or IPv6 or dual stack. For dual stack, user needs to provide IPv4 and IPv6 addresses. This IP address may belong to different subnet from Appliance IP address as per your organizational policies. Keeping it in the same Subnet also works well.

    • Gateway IP address for NodeZero

      Gateway address of the Subnet where NodeZero is placed.

    • DNS IP address for NodeZero

      IP address of DNS server that NodeZero can use.

    • Password for root provider administrator

      Any password can be kept as per the password policy displayed at the time of installation.

    • Password for operator

      Operator Console is to manage and monitor Harmony Controller installation. User name for operator is ‘admin’. Any password can be kept as per password policy displayed at the time of installation.

    • Internal Subnet

      Assign an internal IP address range of 512 IP address to be used for all internal networks.

Install Harmony Controller Software

Following are the steps for installing Harmony Controller Software on appliance:

  1. Log in to Harmony Controller 8000 appliance as admin with your password.

  2. Go to /a10data folder:

    # cd /a10data
    
  3. Type the following command to start the installation script.

    $ sudo su
    # StartHC
    

The script is interactive and will prompt for information. Follow the on-screen instructions and provide the value of items asked.

Next Steps

  • Configure SSL certificates for FQDN and email server information using A10 Harmony Controller Operator Console in the Certificate section under Configuration Management.

  • FQDN should be mapped to Floating IP address.

  • Setup scripts for transferring scheduled backup files to external storage as described in maintenance information.

Software Installation of Cluster on Three Harmony Controller 8000 Appliances

In case of three Harmony Controller 8000 appliances, three VMs (nodes) are placed in the appliances (one in each appliance). The controller software is installed in those VMs.

_images/2HC8000.png

Before You Begin

  • Make sure all Prerequisites and Hardware PreRequisites are met.

  • Keep the following information ready:

    • Number of Appliances

      Installation can be done on 1 or 3 appliances as described in various sections in this document. As in this case installation is being done on 3 appliance, the answer should be 3.

    • IP address for First Appliance

      This is the IP address for the first appliance.

    • IP address for Second Appliance

      This is the IP address for the second appliance.

    • IP address (IPv4 or IPv6 or dual stack) and Subnet prefix for NodeZero

      This IP address and Subnet mask will be assigned to the NodeZero after it is created and note that the IP address cannot be changed. All the IP address should be either IPv4 or IPv6 or dual stack. For dual stack, user needs to provide IPv4 and IPv6 addresses. This IP address may belong to different subnet from Appliance IP address as per your organizational policies. Keeping it in the same subnet also works well.

    • Gateway IP address for NodeZero

      Gateway address of the subnet where NodeZero is placed.

    • DNS IP address for NodeZero

      IP address of DNS server that NodeZero can use.

    • IP address (IPv4 or IPv6 or dual stack) and Subnet prefix for NodeOne IP

      This IP address and Subnet mask will be assigned to the NodeOne and note that the IP address cannot be changed. All the IP address should be either IPv4 or IPv6 or dual stack. For dual stack, user needs to provide IPv4 and IPv6 addresses.

    • Gateway IP address for NodeOne

      Gateway address of the Subnet where NodeOne is placed.

    • DNS IP address for NodeOne

      IP address of DNS server that NodeOne can use.

    • IP address (IPv4 or IPv6 or dual stack) and Subnet prefix for NodeTwo IP

      This IP address and Subnet mask will be assigned to the NodeTwo and note that the IP address cannot be changed. All the IP address should be either IPv4 or IPv6 or dual stack. For dual stack, user needs to provide IPv4 and IPv6 addresses.

    • Gateway IP address for NodeTwo

      Gateway address of the Subnet where NodeTwo is placed.

    • DNS IP address for NodeTwo

      IP address of DNS server that NodeTwo can use.

    • Password for root provider administrator

      Any password can be kept as per the password policy displayed at the time of installation.

    • Password for operator

      Operator Console is to manage and monitor Harmony Controller installation. User name for operator is ‘admin’. Any password can be kept as per password policy displayed at the time of installation.

    • Floating IP Address (IPv4 or IPv6 or dual stack)

      A floating IP address is assigned to the NodeZero. In case this node fails, the floating IP address is automatically moved to the next NodeZero. All external communication happens through the floating IP address. All the IP address should be either IPv4 or IPv6 or dual stack. For dual stack, user needs to provide IPv4 and IPv6 addresses. This IP address must be an unused IP address in the same subnet as nodes.

    • Virtual Router Identification

      Harmony Controller uses Virtual Router Redundancy Protocol (VRRP) for moving Floating IP among the nodes. The Virtual Router ID is a number between 1 and 255 that uniquely identifies group of devices in the network subnet. Assign an unique Virtual Router ID for the Harmony Controller.

    • Internal Subnet

      Assign an internal IP address range of 512 IP address to be used for all internal networks.

Install Harmony Controller Software

Following are the steps for installing Harmony Controller Software on appliance:

  1. Log in to HC-8000 appliance as admin and type the password.

  2. Go to /a10data folder:

    # cd /a10data
    
  1. Type the following command to start the installation script.

    $ sudo su
    # StartHC
    

The script is interactive and will prompt for information. Follow the on-screen instructions and provide the value of items asked.

Next Steps

  • Configure SSL certificates for FQDN and email server information using A10 Harmony Controller Operator Console in the Certificate section under Configuration Management.

  • FQDN should be mapped to Floating IP address.

  • Setup scripts for transferring scheduled backup files to external storage as described in maintenance information.