Network Configuration of A10 HarmonyTM Controller

The Harmony Controller has networking configuration at the following places:

  1. At Harmony Controller Appliances - if they are being used
  2. At nodes (mostly VMs) where Harmony Controller Software is installed
  3. Floating IP Address
  1. Appliance Networking Configuration
    When Harmony Controller appliance is powered on for the first time, an IP address needs to be configured along with its gateway on the appliance management port. This step needs to be repeated for all the appliances. For exact steps, please refer the hardware manual. The appliance IP is needed to login to the appliance and start the Harmony Controller installation. Later access to this may be needed to run any Hypervisor (KVM) level command.
  2. Node Networking Configuration
    The VM(s) need to be configured using public bridge networking. This requires unique IP address to be assigned to each VM, and this IP address should be accessible from the local network (on which the appliance is configured). Please note that the VM IP address should not be the same as any of the other VM IP addresses or any of the appliance IP addresses.
  3. Floating IP Address
    A floating IP address is assigned to the elected NodeZero. In case this node fails, the floating IP address is automatically moved to the next elected NodeZero. All external communication happens through the floating IP address. This IP address must be an unused IP address in the same subnet as nodes. This feature is not available in cloud environments (AWS, Azure, GCP, OpenStack, etc.).

Changing Network Configuration

In the current version, IP address of any of the Harmony Controller node (NodeZero, NodeOne and NodeTwo IP) and External IP address cannot be changed after installation i.e. the Harmony Controller will stop working if IP address of any node is changed.

Other networking configuration like subnet mask, Gateway IP address, DNS server address etc. can be changed using commands provided by operating system on which Harmony Controller is installed.

Configuring Proxy Settings

Incase the proxy settings are set, add no_proxy parameter and required http_proxy and https_proxy parameters under /etc/environment file and restart the system for the Harmony Controller to work properly. The no_proxy parameters are added with all the Master and node IP address along with the network that we use.

Monitoring Health of the Nodes

All the nodes of Harmony Controller should be monitored for the health of the nodes with the system being used by the customer for monitoring other machines. If the NodeZero goes down, please contact A10 Customer Support immediately. They will help create another installation of Harmony Controller using the data backup stored by the user.

If status of any other nodes is down, try to bring up the node with the same IP address. If it is not possible to bring back the node, login to the NodeZero and run the command to delete the node from the controller cluster:

# kubectl delete node <name-of-the-node-which-went-down>

After deleting the node please contact A10 Customer Support for procedure to replace the node.

Note: When you need to reboot the nodes in a multi-node environment, you need to bring-up the NodeOne and NodeTwo first and later reboot the NodeZero.

Backup Utility

Management backup is configured along with Harmony Controller deployment. Metrics backup setup should be optionally setup to be added in the schedule. This is available in node0 cron.

Backup Locations:

One node:

Management backups:  /a10harmony/harmony_backup
Metrics snapshot backup: /a10harmony/harmony_backup/esbackup

Three node:

Management backups:  /a10cvol/cfs/data/harmony_backup
Metrics snapshot backup: /a10cvol/cfs/data/harmony_backup/esbackup
Argument
Description
metrics
Set as yes if metrics backup has to be taken. Default value is “no”, metrics backup has to enabled using the
utility metrics_backup_setup.sh
retention
Retention for backups count. Default is 10
remoteuser
Username of remote server, with enough privileges to copy the backups to the default location on remote server. If | your are using non-root user as remote user to access the server then you need to have sudo passwordless privileges | for the user.
remotehost
Remote server where the backups are placed

Restore Utility

Restore utility is used to manually trigger the restore for backup bundle. By default this uses latest available backup in default locations. Optionally you can trigger selective restore method.

Log location:

/var/log/hc_restore

Log file name:

“harmony_restore-<timestatmp>.log”

Argument
Description
metrics
Set as yes if metrics backup has to be taken. Default value is “yes”, metrics backup has to be enabled using the | utility metrics_backup_setup.sh for metrics restore.
remotehost
Remote server where the backups has to be copied, if the backups are in different location.
remoteuser
Username of remote server, with enough privileges to read the backups from default location on remote server. If | your are using non root user as remote user to access the server, then you need to have sudo passwordless | privileges for the user.
remotelocation
Location on remote server from the backup exists.
auth
Need to enable passwordless ssh access to the remote server.
selectiverestore
Set to true if you are restoring from specific backup file, default is set as false.
configds0
Path of config-datastore-0 backup file, mandatory when selectiverestore is se to true.
configds1
Path of config-datastore-1 backup file, mandatory when selectiverestore is set to true and if it is 3 node.
configds2
Path of config-datastore-2 backup file , mandatory when selectiverestore is set to true and if it is 3 node.

Disaster Recovery Setup Utility

Disaster recovery setup utility is used to attach the remote system for scheduled pushing of backup bundle. One time setup to run for setting up disaster recovery remote system to store the offsite backup. Automatically sets up the remote location and passwordless access for remote location and for periodic schedule in cron.

Log location:

/var/log/hc_restore

Log file name:

“drsetup-<timestatmp>.log”

Details needed during the setup:

  • IP address of the remote server
  • User name to access the remote server.
  • If the remote user is non-root then it needs to have sudo password less access.
  • You need to enable a password less ssh access to the remote server to copy the backups.