NetScaler SD-WAN 9.3.3 Release Notes
This release notes describes known issues, and fixed issues applicable to Citrix NetScaler SD-WAN software release 9.3.3 for the SD-WAN Standard Edition, WANOP, and Enterprise Edition appliances.
For information about the previous release versions, see the NetScaler SD-WAN documentation on docs.citrix.com.
Issue ID 700046: NetScaler SD-WAN appliance crashes when you try to generate STS while processing high traffic volume.
Issue ID 693737: In a HA deployment with NetScaler SD-WAN VPX appliance on VMware ESXi platform, the virtual path service becomes inactive.
Issue ID 697906: NetScaler SD-WAN service is disabled when MPLS QOS queues with all tagged queues are configured through a WAN Link Template, and on receiving a packet without DSCP tag.
Issue ID 699982: When GRE Routes with Gateway eligibility are enabled, ICMP Packets to check gateway eligibility are not guaranteed to be transmitted through the GRE Tunnel. If the tunnel is down or the gateway address does not route to the tunnel, the packet uses standard IP routing. This leads to a GRE route being eligible inappropriately.
Issue ID 7000247: When DPI multi-threading is enabled, it can cause conn_mgr/other threads to wait for connection lock on platforms. This occurs when the release conn->lock is removed before returning from firewall.
Issue ID 695993: Packets sent to the SD-WAN (IP host) Virtual IP address from a trusted WAN interface is dropped when the flow table is exhausted or unable to allocate flows. In this case, proper ICMP reply was expected from the SD-WAN appliance.
Issue ID 699665: When you configure Virtual Path IPsec between MCN appliance and two of the branch appliances, and when you attempt to send traffic from Branch1 appliance to Branch2, WAN-to-WAN forwarding packets with large size are dropped by IPsec due to buffer overflow.
Issue ID 700183: When GRE tunnel is transmitted through an untrusted interface, for example; Internet Service, the ping requests are responded, but the IP host will not forward replies/messages back to the GRE tunnel.
Issue ID 700285: Do not update VLAN ID in the packet descriptor after DPI processing is complete.
Issue ID 700585: Disabling service on SD-WAN appliances configured with BGP peering for more BGP holdtime duration, results in the BGP session becoming disabled after enabling the service.
Issue ID 701855: DHCP is enabled on LOM by default on some factory shipped 410-SE appliances. Assign an unreachable IP address to the LOM.
Issue ID 701845: SD-WAN Center encounters an internal error when trying to export configuration. The config file should be saved with a new name and then exported to change management to prevent internal error.
Issue ID 700181: The ability to reconfigure or disable two box mode is not possible when caches are configured with any other subnets other than /24.
Issue ID 698803: As part of change management procedure during SD-WAN appliance staging phase, configuration fails when you change MTU on the intermediate router to 600.
Issue ID 702520: NetScaler Management and Analytics System is not supported in SD-WAN 410 Standard Edition Platform.
Issue ID 686768: When you configure Primary MCN and Secondary MCN for the first time, the Primary MCN is incorrectly configured as secondary MCN.
Workaround: Configure the site, which must be the Secondary MCN, in client mode. Once the configuration is active, reconfigure the site as Secondary MCN and activate the new configuration.
SD-WAN VPX Appliances
Issue ID 694837: For High Availability in Amazon Web Services (AWS) environment, Virtual WAN service is disabled on a NetScaler SD-WAN VPX Primary (active) appliance citing duplicate IP address when the HA interface on the primary appliance goes down.
Issue ID 701427: On ESXi platform, converting SD-WAN VPX to VPX-L platform requires software re-image. You need to perform the first boot on a 16GB VM.
SD-WAN 4000 WANOP and 4000 SE
Issue ID 681550: On a NetScaler SD-WAN 4000 WANOP appliance, uploading DER encoded certificate for the SSL profile is ignored and no error message is displayed in the web GUI. Only PEM encoded certificates are accepted.
Two Box Mode
Issue ID 681680: After a factory reset on the SD-WAN SE appliance in a two box mode, configuration sync between SD-WAN WANOP and SD-WAN SE appliances fails due to stale SSL certificates.
Workaround: Disable and re-enable two-box mode on the SD-WAN WANOP appliance.
SD-WAN 1000 / 2000
Issue ID 681663: When you upgrade SD-WAN 1000 / 2000 appliance from release build version 18.104.22.168 to 9.2.x, a warning is displayed in the browser.
Workaround: Perform the upgrade in an in-cognito mode window of the Google Chrome browser.
HDX CGP over SSL
Issue ID 690794: HDX ICA/CGP over SSL session’s behavior In Virtual WAN Standard Edition:
- HDX sessions are not being negotiated as multi stream sessions even though MSI is enabled on the appliance and MSI+MP policies are set on incoming ICA traffic.
- HDX traffic is classified as belonging to Hyper Text Transfer Protocol Secure (https) application and web family.
- HDX traffic falls under interactive_very_low class. This may cause issues in QoS, bandwidth allocation and so on as application QoS will not be triggered because the traffic is not classified as HDX sessions.
WAN GRE Tunnel
Issue ID 681171: NetScaler SD-WAN appliance does not reassemble fragmented GRE tunnel packets properly.
IPsec Tunnel Configuration
Issue ID 681121: On a NetScaler SD-WAN VPX appliance, a web GUI error is displayed and configuration fails when you try to add and configure IPsec tunnel through the SD-WAN configuration editor.
Workaround: Configure IKE and IPsec parameters except protected networks and save the configuration. Edit the configuration to add protected networks.
Enterprise Edition as MCN – SSL Profile
Issue ID 680199: On a factory shipped Enterprise Edition appliance when you create an SSL profile and associate a Service Class to the profile with unidirectional setting, the SSL profile is not checked/enabled in the SSL Profile page of the SD-WAN EE web GUI. In addition, the service class is not associated to the SSL profile.
Workaround: Create a new SSL profile and associate unidirectional service classes.
Configuration and Reporting
Issue ID 683882: Audit errors are reported when you create more than one Service Class on an SD-WAN appliance with override options. This issue occurs only when you perform override for service class and create more than one service class. This behavior is not observed when you create only one Service Class under the default section.
Transparent proxy support for TLS 1.2
Issue ID 691900: In NetScaler SD-WAN WANOP 9.3.0, for SSL compression the SSL profile has to be configured in split mode only as transparent proxy mode is not supported.
Change Management (Single Step Upgrade) SD-WAN GUI
Issue ID 691571: On low-end platform editions, such as the SD-WAN 400, 100, 2000, or VPX appliances with 4 GB or smaller memory assigned, if concurrent local change management package downloads are initiated the appliance runs out of memory and becomes unresponsive.
Workaround: Download local change management package one at a time, this reduces the load on the appliance.
Issue ID 691953: During software upgrade on an appliance using a Standard Edition license, a WAN optimization related waring message appears. After the scheduled upgrade and after the WAN optimization, SVM and XenServer hotfixes are installed the warning message is cleared.
Workaround: Clear the warning messages manually or open the SD-WAN web UI in an incognito browser window.
Secure Peering Certificate and Keys
Issue ID 695363: In the SD-WAN GUI, on the Secure Peering Certificate and Keys page, the CA certificate contents are displayed when the private CA radio button is selected after setting the KeyStore password on a new appliance.
Workaround: You need to switch between the radio buttons of the ‘Private CA’ and ‘CA Certificate’ once to get the correct contents displayed under ‘Private CA’ and ‘CA Certificate’ for Secure Peering Certificate and Keys.
Issue ID 694894: When you configure Application QoS rule with match type as “Application” to match ‘icmp’ and change the class to Real-time, and mode to load balance which overrides the default rule, the multicast traffic is not processed.
DPI- ICMP Functionality
Issue ID 677356: A firewall policy for blocking ICMP as an application blocks only pings (echo requests). All other ICMP types are allowed to pass through.
Workaround: Instead of blocking ICMP as an application, block IP-protocol > ICMP.
DPI – Dual- mode IPERF test identifies traffic only from one node
Issue ID 678131: When dual-mode IPERF test is performed between two appliances, the traffic in NetScaler SD-WAN web management interface under Monitoring > Firewall > Connections with DPI identifies traffic flow only from one of the connections.
DPI –Traffic for Top App Family as “Standard” and Top App as “Unknown Virtual protocol” for a Standard Edition appliance**
Issue IDs 678373, 678339, 678545, 675063, 676017: On a NetScaler SD-WAN Standard Edition appliance, enable EDT policy for MSI+MP for Win7 and Win2K12 XD 7.12 VDAs on ports 2598, 2599, 2600, 2601 and subsequently disable Session Reliability policy for Win7 VDA.
Start sending internet traffic and check the monitoring flows in the Standard-Edition web management interface for Classes, Rule groups – ICAUDP and ICACGPUDP, and Firewall. Check the Dashboard and Reporting page in SD-WAN Center web management interface. The results display Top Application Family as Standard and Top Applications as Unknown Virtual Protocol.
Issue ID 692487: In the SD-WAN Center dashboard, configuration setup for monitoring 400 or more sites can take approximately 4 minutes to load.
Issue ID 693436: The clear connections/flows clears SD WAN connection table entries and subsequently all the ICA sessions The SD-WAN Center dashboard shows incorrect results for HDX TCP and EDT classification sessions and reports it as “Not Classified”.
Issue ID 693026: For HDX configuration, only UDP ICA sessions are classified by ICA classifier. The FrameHawk ICA session are ignored. The SD-WAN DPI fails to classify the FrameHawk sessions.
Issue ID 694541: NetScaler SD-WAN Center dashboard reports an MSI + MP session as single stream instead of multi stream. When you configure any of the default ICA/CGP ports, 1494 or 2598 as part of the DPI ICA Port range under the Global Application Settings, the ports will not be honored.
Workaround: Do not use that port for the port range.
Issue ID 692487: In a network setup with 550 sites, if you perform any network level changes in the setup, it takes approximately ~5-8 mins for the information to be displayed in the SD- WAN center Dashboard.
- The number of users is equal to the total number of HDX sessions. The number of users is not based on distinct user names. That is, two sessions started by a single user on two different machines or the same machine is counted as two users.
- HDX sessions are not being negotiated as Multi Stream Sessions even though MSI is enabled on the appliance and MSI+MP policies are set on incoming ICA traffic.
- HTML5 receiver and ICA over SSL are not supported.
- The audio over UDP ports; 16500 to 16509 for Real Time Transport traffic Classification and Reporting is not supported in release 9.3.1.x.
SD-WAN Center and Diagnostics Tool
- SD-WAN web GUI Diagnostic tool will not be supported on UNTRUSTED links and Dynamic Virtual Paths.
- In the SD-WAN Center Reporting page, the Application name, Application Family, and Site filter do not contain scrollable search drop-down menu.
- For SD-WAN Standard Edition, a connection with high latency is displayed as Poor Connection in the Citrix Quality Indicator (CQI) Tool. While, in SD-WAN Center the Network HDX QOE is still displayed as Good.
- After a VM is created and booted in Azure, the interfaces cannot be added or deleted. The VM profile (RAM/HD/CPUs) can be changed.
- Azure does not allow two network interfaces NIC on a VM to have IP address on same subnet. There is no L2 Support and bridging is not allowed. VPX-SE on Azure has to be deployed in Gateway mode.
- There is no concept of MAC address spoofing in Azure Cloud. The LAN subnet of the VPX-SE and the LAN subnet of the Client/Server Host have to be different. This will require additional routing configuration to be done in two places. – User Defined Routes (UDR) have to be added in Azure directing all Virtual WAN Data traffic from the Client/Server LAN Subnet to the LAN interface of the VPX-SE in Azure. – Routes have to be added in the Virtual WAN Configuration File directing all Virtual WAN Data traffic coming from the WAN to the Client/Server LAN Subnet.
- PCI Enumeration causes the order of NICs in an Azure VM to get switched on reboots. This might cause Management Subnet unreachability.