The Edgenexus EdgeADC can be successfully installed on OpenStack and serves as an excellent example of a Layer 7 advanced application delivery controller.

You will first require the KVM variant of Edgenexus ADC. This is available on our downloads page, which will be available to you after registration.

Next, you will require the Edgenexus Octavia Driver. This is available here:

Now install the EdgeADC as you would any KVM image onto OpenStack and use the Octavia driver provided.

We have two ADCs in our network, ADC101 and ADC102. These are in an Active-Passive cluster, with ADC101 being the current Active, and ADC102 being the current Passive.

For example, we wish to upgrade them from version 5.00 to version 5.01.

The advised process is as follows:

1. Log into each ADC and navigate to Advanced > Configuration
2. Download the configuration files of both ADCs
3. You will perform the upgrade on the Secondary first
4. Open the web console of the Secondary ADC
5. Navigate to Advanced > Software > Download from Cloud
6. You should see the build within the list
7. Click on it, and then click the Download Selected Software button.
   The build will download to the Apply Software section on the same page.
8. If the update is not present in the list, please locate the file you would have been provided or downloaded via our website.
   You will need the Machine ID and License ID of each ADC to do this.
   Go to https://appstore.edgenexus.io/software-update/ to perform a manual download.
   Once downloaded, navigate to the Upload Software section in Advanced > Software.
   
   Browse to the downloaded file, and click on Upload Apps and Software. The update is encrypted to the ADC’s Machine ID and License ID, and hence unique to the ADC.
   The update will now be made available in the Apply Software section.
9. Now that you have the update file in place, click on it and choose Apply Selected Software.

1. The build will now be installed, after which the ADC will restart.
2. Leave the ADCs to work for about hours to stablilise and replicate all the configuration from the Primary to the Secondary.

Now, we have to upgrade the Primary. In order to do this safely, and minimize downtime impact, please follow the steps below.

1. Now that synchronization and stabilization has completed, move the Secondary to become the Primary.
2. Leave it like this until you and your users are satisfied that all the services are operational to your level of satisfaction.
3. Once you are satisfied, you can upgrade the Secondary (previously Primary) using the same method as above.
4. You should now leave the newly upgraded secondary to settle and stabilize.
5. Once done, you could move it back to the Primary position, or leave it as is.

What if I am not happy and wish to revert?

If you wish to revert the Primary (new) to the older version, its simple to do.

1. Switch the Primary to become the Secondary.
2. Navigate to Advanced > Software > Apply Software
3. Choose the previously installed build.
4. Click Apply Selected Software Update.
5. The build will revert to the previous version and you’re good to go.

Important

We ask you to update the build and let it settle for stabilizaiton and then to determine user satisfaction.

Current Application Version	Upgrade Option	Future Updates	Action
v4 (Legacy)	Upgrade to v5.0.0C	No future development beyond this version	Recommended to plan migration to v5.0.0R
v5.0.0C	No upgrade within same OS environment	Only critical fixes on best-effort basis	Future migration to v5.0.0R advised
New Installations	Deploy v5.0.0R	Full support and ongoing development	Use latest ISO/OVA provided

Hardware Platform Support

Hardware Type	Support Status	Notes
New HPE Servers	Fully supported	Recommended hardware for all new deployments
Other Hardware	Case-by-case basis	Pre-approval required before deployment
E4 Appliances	End of Life (EOL)	Only best-effort support; migration strongly recommended or switch to Virtual licensing

Customer FAQ

1. What happens if I stay on v4?

• You can continue running v4, but only best-effort support will be available.
• We recommend upgrading to v5.0.0C as soon as possible to avoid security and support risks.

2. Can I upgrade from v4 directly to v5.0.0R?

• No. v4 systems can only upgrade to v5.0.0C.
• v5.0.0R requires a fresh deployment with new installation media.

3. Will v5.0.0C receive future updates?

• No. v5.0.0C is a final release for customers upgrading from v4.
• Only critical fixes (if any) will be provided on a best-effort basis.

4. What should I do if I’m on v5.0.0C?

• Plan a future migration to v5.0.0R to ensure you benefit from ongoing enhancements and long-term support.

5. What hardware is supported for the new deployments?

• HPE servers are the officially supported platforms for new deployments.
• If you wish to use other hardware, you must consult with our support team first to confirm compatibility.

6. What is the status of E4 hardware appliances?

• E4 appliances are End of Life (EOL).
  Only best-effort support will be provided for E4 units.
• Customers should plan a migration to supported hardware as soon as practical or switch to Virtual licencing

7. How do I get started with planning my migration?

• Please contact our support team at support@edgenexus.io or reach out to your account manager.
• We can assist with migration advice, hardware validation, and deployment options.

To migrate the ADC, you must first download the VM installation file from https://www.edgenexus.io. Do this by filling out the trial form at https://edgenexus.io/try and downloading the version you need for your virtualization environment.

Migrating a Clustered ADC environment

Note: Migrating will incur an element of downtime and is best done when there are no users

The cluster method is by far the easiest, but still requires a level of caution when performing the migration. Follow the steps below.

Stage 1 – Migrating the Original Secondary

• The first thing to do is set up TWO new VMs to become your new ADCs.
• We will start by migrating the Secondary first.
• Now, make a note of your current Secondary ADC’s IP address and the name of the ADC (found in Networking).
• Locate the original license key provided to you for this ADC. The license key is provided against the Machine ID.
• Now that you have these items, power down the secondary ADC.
• Choose one of the VMs that you created to be your new Secondary ADC.
• Configure its IP address to match the old Secondary. You can do this using the console and the command SET GREENSIDE={IP-ADDRESS}
• Log into the ADC using your browser.
• Import the license into the ADC
• Change the NAME to match your original Secondary.
• Log onto your Primary ADC.
• You will now see the new Secondary in the Unclaimed Devices section.

• Move it to the right side section to cluster the ADCs.
• You should now have the configuration of the Primary replicated to the new Secondary.
• Our advice is to run this setup for 24-48 hours to ensure the new Secondary is stable in your environment.
• Thoroughly test all the Virtual Services to ensure proper performance.

Stage Two – Migrating the Original Primary

• Now, we will migrate the original Primary to the new version.
• At this point, you need to understand that some users may get disconnected from their sessions.
• Move the order of the ADCs in the Clustering right side, so the new Secondary is on top of the original Primary.
• The ADCs should now flip, and the original Primary will be now be the Secondary.
• Make a note of the IP Address, Name and have the original license file ready.
• Log into the Secondary (original Primary) and backup the configuration from Advanced > Configuration.
• Shut down the ADC after performing the backup.
• Choose the remaining VM that you created.
• Configure its IP address to match the original Primary. You can do this using the console and the command SET GREENSIDE={IP-ADDRESS}.
• Log into the ADC using your browser.
• Import the license into the ADC.
• Change the NAME to match your original Primary.
• Log onto your new Primary ADC.
• You will now see the new Secondary in the Unclaimed Devices section.
• Move it to the right side section to cluster the ADCs.
• You should now have the configuration of the Primary replicated to the new Secondary.
• At this point you can continue to use this as your new Secondary, or wait for the advisory period and then flip the ADCs.

Migrating a single ADC environment – Non-Cluster method

Note: Migrating a single ADC will incur an element of downtime.

• Log into the ADC as an admin user
• Navigate to Advanced > Configuration
• Download the configuration file
• Proceed to Library > SSL Certificates
• Export the SSL certificates – select ALL and provide a password.
• The certificates will be exported as a JNBK encrypted file.

• Import the OVA or other format into your VM infrastructure
• Change the CPU, memory and any other custom parameters so they match the existing v4 ADC VM
• Start the new v5 VM
• Now, it is time to bring down the existing v4 ADC VM. Just power it off, but please do not delete it.
• Let’s move onto the new v5 ADC where we will finish the work.
• Import the configuration file into the new v5 ADC VM.
• Once done, power cycle the new ADC v5 VM.
• Proceed to Library SSL Certificates
• Choose Restore SSL Certificates

• Browse to the JNBK file and provide the password
• Click Restore
• The new v5 ADC should now be available using the original IP address and all its configuration intact.

We will use the VMWare OVA version of installation. This is a multi-step process and requires knowledge of shell commands in ProxMox. However, we have made the instructions as easy as possible to follow. We are going to assume that you are conversant with ProxMox and so will not go into ProxMox features in depth.

Uploading the OVA to ProxMox

Since we are using an OVA version, we will first need to upload the OVA to ProxMox.

• Log into the ProxMox console
• Create a folder called OVA_Import.
• You will now need to use an SFTP client such as WinSCP (Windows) or CyberDuck (Mac) to transfer the OVA file.
• Once the file is transferred, you will see it in the folder you created.
• Type the following command to extract the contents of the OVA file.
• Tar xvf {filename}. See thee example below.

tar xvf Edgenexus-ADC-6.8-64-OVA.1155-1961-9704-bam2221.ova

Once extracted, you should see something like the below example

root@proxmox:~/OVA_Import# ls
Edgenexus-ADC-6.8-64-OVA.1155-1961-9704-bam2221.ova
root@proxmox:~/OVA_Import# tar xvf Edgenexus-ADC-6.8-64-OVA.1155-1961-9704-bam2221.ova
Edgenexus-ADC-6.8-64-OVA.1155-1961-9704-bam2221.ovf
Edgenexus-ADC-6.8-64-OVA.1155-1961-9704-bam2221.mf
Edgenexus-ADC-6.8-64-OVA.1155-1961-9704-bam2221-disk1.vmdk
root@proxmox:~/OVA_Import#

• There are three files. The .ovf and .mf are the configuration. The .vmdk is the virtual disk holding the ADC.
• The next step is to import the VMDK into ProxMox and create the virtual machine.
• Type the following command to create the virtual machine using the configuration files.

qm importovf 137 ./{filename.ovf} local-lvm --format qcow2

• In this example, we have given an ID of 100, but this may be different for your installation if you already have virtual machines created in ProxMox. You can determine the next ID by starting the process of VM creation in ProxMox, or by choosing a number higher than 100 that is safely out of reach.
• The VM has now been created.

• The next step is to add a network interface to the VM.
• Click on Hardware on the right panel.
• Click Add and choose a Network Interface.

• Configure it as the image above shows. It’s important to choose the Model as VMware vmxnet3.
• Click Add once configured.
• You can additional network adapters as your needs dictate.
• You can now start the VM and proceed to use the instructions in the First Boot Configuration chapter.

Requirements and Versions

The guidance below does not cover the installation of KVM or its networking. We assumed that you downloaded the KVM virtual appliance and stored it on the host in an accessible location.

• The first step is to log into the Cockpit console.
• Click on Import VM
• The first dialog is where you will need to specify the details for the virtual appliance import. See the image below for the content of fields. You must specify Red Hat Enterprise 6.0 as the OS.

• Please ensure that you have the “Immediately Start VM” unchecked.
• Once you have filled in the details, please click the Import button.
• The next stage is to specify the vCPU and memory allocation you may wish to use.

• To allocate the memory, you will see a dialog similar to the one below.

• To allocate the vCPU, you will see a dialog similar to the one below.

• The choices we have made are only examples but workable unless you are using heavy throughput with SSL re-encryption, in which case, you will need to adjust accordingly by using the Hardware section under View > Statistics.
• You now have a working ADC installed in KVM.

You can either download the older version by contacting support@edgenexus.io if your support contract is current, or use the internal method as outlined below.

• Go to Advanced > Software
• Scroll down to the Apply Software section

• Locate the version you wish to downgrade to and click on it.
• Click the Apply Selected Software button.
• The software will be applied and the ADC will perform a reboot.

Built-In Method

In order to use the built-in method that fetches and deploys the upgrade, you must first be a registered license holder, and have an account on the Edgenexus App Store. The App Store is accessible at https://appstore.edgenexus.io.

• Log into the ADC as an admin user.
• Navigate to Advanced > Software using the navigation panel on the left.
• Locate the Download from Cloud section.
• You should see a notice in Green stating that the ADC is connected to the Cloud Services Manager.
• The Download from Cloud section will then be populated. See image below.

Select the update you wish to download and then click the Download Selected Software button.

The download will begin, and the update file will be placed in the section underneath Download from Cloud, called Apply Software (see image below).

Select the software you just downloaded, and click Apply Selected Software Update.

And, if you want to roll back, simply select the previous version, and click the Apply Selected Software Update once again.

Manual Method

Some organizations do not permit access to the Internet which results in the Cloud Services Manager being unreachable by the ADC. The CSM is required for licensing and updates to be downloaded directly into the ADC.

For these scenarios, Edgenexus permits the user to download updates using an Internet browser. Follow the instructions below:

• Navigate to the Edgenexus website.
• Click on the Resources menu and select the Software Update Download option
• Next, you will need the Machine ID and License ID of your ADC. This can be found in the System > Licensing section (example below)

• The Software Update Download page looks something like the image below:

• Enter the details in the form and click Submit.
• The update is then encrypted, following which it can be downloaded.
• NOTE: Do not change the filename or content in any manner.
• Once downloaded, navigate to Advanced > Software on the ADC.
• Scroll to the Upload Software section.

• Click the Browse button and locate the downloaded file.
• Click OK to select the file, and then click Upload Apps and Software.
• The new software will be uploaded and will apply in the Apply Software section right beneath the Upload Software section.

• Click on the new software and click the Apply Selected Software Update.
• The ADC will restart and the new software will be available to use.

To interrupt this process, click into the console window and press any key. You can then enter the following details manually.

• IP Address
• Subnet Mask
• Gateway
• DNS Server
• These changes are persistent and will survive a reboot and don’t need to be configured again on the VA.

First Boot – DHCP Successful

If you do not interrupt the network assignment process, your ADC will contact a DHCP server after a timeout to obtain its network details. If contact is successful, then your machine will be assigned the following information.

• IP Address
• Subnet Mask
• Default Gateway
• DNS Server

We advise that you do not operate the ADC VA using a DHCP address unless that IP address links permanently to the MAC address of the VA within the DHCP server. We always advise using a FIXED IP ADDRESS when using the VA. Follow the steps in Changing the Management IP Address and subsequent sections until you have completed the network configuration.

First Boot – DHCP Fails

If you do not have a DHCP server or the connection fails, the IP Address 192.168.100.100 will be assigned.

The IP address will increment by ‘1’ until the VA finds a free IP address. Equally, the VA will check to see if the IP address is currently in use, and if so, will increment again and recheck.

Changing the Management IP Address

You can change the IP address of the VA at any time using the command set greenside=n.n.n.n, as shown below.

Changing the Subnet Mask for eth0

The network interfaces use the prefix ‘eth’; the base network address is called eth0. The subnet mask or netmask can be changed using the command set mask eth0 n.n.n.n. You can see an example below.

Assigning a Default Gateway

The VA needs a default gateway for its operations. To set the default gateway, use the command route add default gw n.n.n.n as shown in the example below.

Checking the Default Gateway value

To check if the default gateway is added and is correct, use the command route. This command will display the network routes and default gateway value. See the example below.

You can now access the Graphical User Interface (GUI) to configure the ADC for production or evaluation usage.

Accessing the web interface

You can use any Internet browser with Javascript to configure, monitor, and deploy the ADC into operational use.

In the browser URL field, type either HTTPS://{IP ADDRESS} or HTTPS://{FQDN}

The ADC, by default, uses a self-signed SSL certificate. You can change the ADC to use the SSL certificate of your own choice.

Once your browser reaches the ADC, it will show you the login screen. The factory default credentials for the ADC are:

Default Username = admin / Default Password = jetnexus