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.

Our application platform has recently been updated to a new operating environment designed to provide enhanced security, long-term support, and improved performance.

Due to the significant differences between the legacy and new environments, a direct upgrade is not possible. Customers currently running older platforms will need to plan for a fresh deployment using the latest release package (ISO/OVA or equivalent) provided by us. We are here to assist in this transition where needed.

Support for Hardware Appliances (E4 Series)

Effective immediately:

• E4 hardware appliances are now considered End of Life (EOL).
• Software updates for these appliances will be provided on a best-effort basis only.
• We are unable to guarantee resolution of any issues if they are already addressed within the latest platform release.
• We encourage all E4 appliance users to plan an upgrade to a supported platform to ensure continued stability and support.

Supported Hardware Platforms Moving Forward

• Newer HPE server platforms will be officially supported for deployments moving forward.
• Other hardware platforms may be supported on a case-by-case basis and must be pre-approved by our team prior to deployment.
• Customers considering alternative hardware should contact our support team in advance to discuss compatibility and supportability.

Application v4 and v5 Upgrade Paths

For customers using application version v4:

• Upgrade to application version v5.0.0C is available.
• Important: v5.0.0C will be the final version available for upgrades from v4.
• No further development or feature updates are planned for v5.0.0C.
• Customers should plan accordingly, as v5.0.0C will only receive critical updates on a best-effort basis.

For new deployments:

• All new installations will be based on application version v5.0.0R.
• Future development, enhancements, and support will continue exclusively on v5.0.0R.
• Deployments on the new platform will benefit from ongoing improvements and security updates.

Summary of Actions

Assistance and Planning Support

If you require assistance in planning your migration, assessing hardware compatibility, or have questions about your upgrade path, please contact our support team at support@edgenexus.io or your account representative.

Thank you for your continued support. We look forward to helping you take advantage of the updated platform’s new capabilities and long-term benefits.

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.