Product Documentation

Upgrade (OS) Process

The new WANOP OS Kernel upgrade is supported from which SD-WAN release?

Citrix SD-WAN release 10.1 and later.

Is the new OS supported on all SD-WAN platforms?

Yes. The OS upgrade is supported on all SD-WAN WANOP (VPX, Physical, Cloud), and Premium/Enterprise edition appliances.

What are the WANOP VPX profiles (RAM/Disk/vCPU) that are supported with release 10.1?

  • 6GB RAM, 100GB Disk and 2 vCPUs
  • 6GB RAM, 250GB Disk and 2 vCPUs
  • 8GB RAM, 500GB Disk and 4 vCPUs
  • 16GB RAM, 500GB Disk and 4 vCPUs

What are the key feature differences between WANOP running with release 10.0 or lower versus 10.1?

Feature 10.0 or earlier 10.1 or later Comments
Video Caching support on WANOP supported Not supported none
Minimum RAM requirement for WANOP VPX 4GB RAM 6GB RAM none
WANOP VPX deployment wizard supported Not supported none
Primary / apA Adapter Management IP address for WANOP VPX DHCP is disabled by default DHCP is enabled by default none
Upgrade support on existing standalone WANOP VPX on XenServer supported not supported. Fresh SD-WAN 10.1 XVA image should be imported none
Upgrade support on Physical WANOP platform that have XenServer 6.0 Hypervisor version (Platforms that are shipped with 7.2.2 or earlier factory base image version would have XenServer 6.0 version) release 10.1 supported You have to upgrade XenServer to 6.5 version (using WANOP XenServer 6.5 upgrade bundle) and then perform WANOP 10.1 upgrade Clicking on “Configuration” GUI, would display XenServer hypervisor version

Upgrade of WANOP VPX running on standalone XenServer (with WO build 10.0 or earlier) to 10.1 version is that supported, If not, why?

This upgrade is not supported because of PV to HVM conversion. You have to provision a fresh SD-WAN release on 10.1 XenServer WANOP VPX using the XVA image.

Upgrade of WANOP VPX running on standalone ESXi / Hyper-V (with WO build 10.0 or earlier) to 10.1 version is that supported, If not, why?

This upgrade is supported. Before upgrade, please be aware of the new RAM resource requirement changes.

Upgrade of WANOP on physical appliance (with WANOP build 10.0 or earlier) to 10.1 version is that supported, If not, why?

This upgrade is supported. Prerequisite for this upgrade is to have the hosting XenServer Hypervisor (on physical SD-WAN appliance) to have XenServer version 6.2 / 6.5 or higher version. This can be verified by using the Configuration tab.

localized image

If the physical WANOP appliance is not running with XenServer 6.2 / 6.5 or higher, what does the user have to perform?

You have to upgrade XenServer, before upgrading SD-WAN WO version.For example, in this below use case, let us consider planning to upgrade SD-WAN 800 WANOP platform running with 7.2.2 (that has XenServer 6.0 version).

  1. While upgrading this appliance to SD-WAN 10.1 release, the following error message would occur.

    localized image

  2. Upgrade XenServer to 6.5, using “ns-sdw-xen65-pkg_v1.5.upg” (this can be downloaded from Citrix Download website.

    localized image

  3. If SD-WAN WO does not have 9.0 or later version, then upgrade to XenServer 6.5 would not happen. The below error message would appear.

    localized image

  4. Let us assume, the user have upgraded the WO version to 10.0.2 now.

    localized image

  5. Now, upgrade XenServer to 6.5, using “ns-sdw-xen65-pkg_v1.5.upg”.

    localized image

    localized image

    localized image

    localized image

  6. Now, upgrade SD-WAN to 10.1 release.

    localized image

    localized image

Client to Server ICMP Ping is working fine, but TCP traffic is not going through the WANOP VPX appliance (disabling WANOP traffic processing works fine)?

Check the firewall settings on the Client, Server and Router. When WANOP VPX or Client/Server are hosted as VM, make sure that checksum is disabled on the end hosts VM.

Example Linux Commands:
    ethtool -K eth0 tx off
    ethtool -K eth0 rx off
    ethtool --offload eth0 tx off
    ethtool --offload eth0 rx off

Enable the “Checksum.SendForceSW” parameter on both WO VPXs should be “ON”.

Example:
    Checksum.SendForceSW on

Is there any change to SDWAN SE/EE/WO Appliance upgrade process due to new WO OS Kernel?

No.

Upgrade (OS) Process

In this article