Citrix SD-WAN

Release Notes

This release note describes known issues, and fixed issues applicable to Citrix SD-WAN software release 10 version 2 for the SD-WAN Standard Edition, WANOP, and Premium Edition appliances.

For information about the previous release versions, see the Citrix SD-WAN documentation.

Fixed issues

NSSDW-13639: In a high availability environment, when you select all for multiple sites to perform an Edit operation, the schedule information is not updated for the secondary branch sites.

NSSDW-13538: A failed (auto) status is reported on the Change Management page after activating staged software with release 10 version 2 build 23 from release 10 version 3 on an MCN appliance using the local change management procedure.

NSSDW- 14516: In a high availability environment, fluctuating network changes or configuration updates that interrupt communication with HA peers or external tracking IPs can cause both appliances in a high availability pair to be in standby mode for up to 2 minutes.

SDWANHELP-184 (SR# 78095846): On the SD-WAN WANOP 4000 and 5000 platform editions, the appliance GUI restarts after a crash. Restart the accelerator VM from the XenServer to restart the appliance.

NSSDW-13269: When creating routing domains, if you attempt to add multiple routing domains with single configuration GUI workflow, errors occur.

NSSDW-11253: After upgrading existing network to release 10.x, the following error message is displayed when performing audit operation from the configuration editor: “One Site must have Appliance Mode set to primary MCN,” when associating an existing site to the new region.

NSSDW 13944: In release 10 version 2, an audit error occurs when attempting to add default route each pointing to different ZScaler gateways, even if there are gateways of different routing domains.

SDWANHELP-501 (SR# SR78262688): Unable to export or audit SD-WAN configuration after configuring GRE tunnels on an SD-WAN appliance using release 10.0 version 2.

SDWANHELP-509 (SR# SR78343050): On a 5100-SE platform, staging a previously working configuration fails after an upgrade to the latest release version and the routing information cannot be obtained.

SDWANHELP-512 (SR#: 78314443): In release 10 version 4, upon main registry updates such as, adding, deleting, or renaming WAN link, there is a downtime of 15 seconds to 40 seconds for the virtual path routing protocol to converge between SD-WAN deployed sites.

SDWANHELP-537 (SR# 78411542): In release 10 version 4, emails alerts are not reported in the SD-WAN Center for WAN link status.

SDWANHELP-538: In release 10 version 3, after configuration update upon removing a custom application stats object, the SD-WAN service restarts.

SDWANHELP-482 (SR# 78247128): In release 10 version 4, a new option to add local IKE-ID when configuring IPsec is added.

SDWANHELP-485 (SR# 78274277): In release 10 version 2, the application QoS configuration is not displayed in the Monitoring view of the SD-WAN web management interface on a 410-SE appliance.

SDWANHELP-489 (SR# 78293306): When the SD-WAN service is enabled, the SD-WAN routes are missing and all trusted interfaces become inactive.

SDWANHELP-490: A core dump error occurs when an ICMP echo packet that creates a firewall connection causes the packet to offload from the IP host thread to the DPI threads.

SDWANHELP-543 (SR# 78394675): During high availability switchover with multiple routing domains, routes are not synchronized properly in the routing tables.

SDWANHELP-544: The IPsec tunnel fails when changing parameters for the tunnel that is actively receiving packets on a site installed with new package.

SDWANHELP-549: In release 10 version 2, before the main software configuration update, the routes set with path eligibility remain in path state after main registry update without associating the current active path state causing routing issues.

SDWANHELP-550: In release 10 version 4, the Ping output for user-initiated ping displays responses for auto-generated pings.

SDWANHELP-553 (SR# 78428386): In release 10 version 3, the active appliance transmits only the most optimal OSPF routes for deletion or addition causing active and standby route tables to differ.

SDWANHELP-566 (SR# 78409673): In release 10 version 4, relayed DHCP packets are redirected or not transmitted, if packets from DHCP relay servers send packets using the client DHCP source port. This occurs even when not using the broadcast IP address.

NSSDW 13665: When sites are configured with WAN link templates for MPLS queue configuration, the site deletion takes longer than expected.

Known issues

NSSDW-14908: The application QoE value is reported as “zero,” if network conditions are outside of the configured thresholds for the real-time traffic.

SDWANHELP-520 (SR# 78300015): In rare instances, the SD-WAN appliance crashes due to invalid memory reference. The health monitoring process restarts the failed process automatically. This issue exists in all SD-WAN releases.

NSSDW-14883: The PPPoE sessions are re-established when activating an interface configuration change on a site. If only PPPoE links exist in the virtual path on that site, it becomes inactive for a brief period until new session is established.

NSSDW-15519: SD-WAN Center fails to discover regions for an MCN with high availability enabled. Switch back the primary MCN to active to resolve this issue.

NSSDW-5182: While converting a single region network to multi-region network, i.e. when adding regions and associate existing site to the newly created region, the error message “One Site must have Appliance Mode set to primary MCN” appears.

Workaround: Create virtual paths manually between MCN and all the RCNs.

SDWANHELP-651: On SD-WAN 2100 appliance, license installation fails when using Microsoft Edge browser.

Release Notes