be performed manually through the web interface options available on the Configuration page.
ICA Connectivity and Client Session
Issue ID 658696: LINUX VDA version field for ICA Session information on WAN OPT appliance is blank or empty
Description: In a LINUX VDA session on a WAN OPT appliance, the VDA version field in the session information
table at ICA Advanced > Session/Conn is empty.
Issue ID 660501: Session Reconnection of NetScaler SD-WAN WAN OPT client fails with HTML5 Receiver version 2.1.
Description: When you attempt to reconnect to a NetScaler SD-WAN WAN OPT client session through
XenDesktop or XenServer with HT ML5 Receiver version 2.1, the session reconnect fails.
Steps:
1. In XenDeskop, click Launch application through the HTML5 Receiver.
2. In the storefront setting, select Always use HTML5 receiver.
3. Disrupt the connection for more than a minute, and they try to reconnect. The session reconnect fails and
the XenDesktop session closes with an error.
Licensing
Issue ID 659809: DBV check support for Remote Licensing Server configuration on Virtual-WAN and SD-WAN appliances
Description: T he DBV check fails and the appliance becomes unlicensed after an upgrade, if the Maintenance
date is expired, and when the customer has Remote License configured on the SD-WAN.
Workaround: Ensure that the Maintenance date in the license file is more recent than the Built date of the SD-WAN
or Virtual-WAN software image that is being upgraded.
Networking and Security
Issue ID 653039: IPsec Rekey based on Data (KB) not working properly
Description: In this release, NetScaler SDWAN does not support IPsec tunnel Rekey based on the assigned data
(Kilo Bytes). After the available data KB is exhausted, the IPsec tunnel is not brought down and rekeying does
not work. No data loss is observed.
Configure an IPsec Tunnel between the SD-WAN appliance Intranet and third-party appliance in the SD-WAN
network and set IKE and IPsec Lifetime in seconds to 3600 seconds, set IPsec Lifetime in KB to 500 KB. Use the
ping command to send basic ICMP traffic (for example, ping 6.2.1.1 -I 5.2.1.1 -s 1000 – i 0.001). Generate enough
traffic so that the IPsec SA lifetime in KB uses 500KB.
During this phase, the IPsec Rekey has to happen before expiration of Lifetime in KB, but the IPsec Tunnel is
deleted after data expiration and packets are dropped. The new IPsec tunnel is established after a few seconds.
Root Cause: All IKE/IPSec generated events are placed in an event queue with a timestamp attached to each entry
within the queue. When the queue timestamp expires, the queued event is processed, and the entry is removed from
the queue. In the case of data expiry, a duplicate entry already present in the event queue does not allow the rekey
