NetScaler has a new nFactor feature used for authentication. The nFactor feature enables a new set of authentication possibilities. Administrators using nFactor have AAA flexibility when configuring authentication factors for virtual servers. The number of policy banks can be extended to suit different needs. Based on previous factors, nFactor determines a method of authentication. Dynamic login forms and on-failure actions are possible by using nFactor.

NetScaler Insight Center is now supported on KVM hypervisors.

When doing forms based SSO, if the back-end server sets a cookie with the login form, NetScaler does not send those cookies to the client. This behavior was observed after a successful forms SSO attempt. This applies to forms based SSO access in both Gateway and AAA-TM products.

If AAA-TM logout is configured through a traffic policy on the Netscaler appliance, and the server sends a chunked response, the user encounters an error.

You cannot add an authentication virtual server as the target of a content switching virtual server in a partition.

If you add a Negotiate Server with a Keytab file with a GUI, an error is issued: "Error in retrieving file. Directory does not exist." The error is only issued when it is executed within partition.

In a partitioned NetScaler appliance, for GSLB services that point to a local load balancing virtual server, the monitors that are bound to that GSLB service fail. Also, connection proxy between local load balancing virtual servers does not work.

If a client submits a form that includes a field named "as_fid", and the application-firewall profile has signatures enabled, the signatures might block form submissions from that client.

The application firewall's SQL Injection special-character transform does not work properly if either of the following parameters is enabled in a profile:

-crossSiteScriptingTransformUnsafeHTML

-SQLInjectionTransformSpecialChars

On a partitioned NetScaler appliance, connections for incoming requests might be reset if the application firewall feature is enabled.

In a cluster deployment, the NetScaler web application firewall (WAF) fails if starturl closure is enabled.

The secondary node in an HA deployment attempts to directly connect to AWS for signature auto updates. Instead, it should sync from the primary node.

When the application firewall signature has upper case or mixed case characters in the name, the configured profile bindings for such a signature are not displayed in the signatures pane in the configuration utility.

If referer header protection is enabled on the application firewall and the starturl action specified is either "stats" or "learn," webpages might not load correctly.

After an upgrade from release 10.5 to a release 11.0 build, uploading a Word document triggers false positives for application firewall SQL and XSS violations during the file upload operation. With this fix, the behavior is the same as in 10.5. The application firewall inspects text, Javascript , HTML, XML and JSON contents when a file is uploaded. It doesn't inspect any other contents.

Starturl relaxations might not work if regex expressions use grouping for matching multiple terms. The URL might not get matched against all the terms in the group.

The NetScaler appliance fails if you enable or disable the IP Reputation feature in any partition other than the default partition.

The VRRP Feature does not work in a cluster setup that includes a node with a node ID of zero (0).

For some commands, such as "add cs policy" and "add server," the ID generated on a non-CCO node already exists for another command of same type on the cluster configuration coordinator (CCO). Therefore, command execution on the non-CCO node fails.

The NetScaler CLI exhibits the following issues on running the "show" and "stat" commands on a service group.

- When using the "show servicegroup -includeMembers" command: This command lists only one service per service group, although more than 1 service are bound to the service group(s).

- When using the "stat servicegroupMember <ServiceGroupName> <Service-IP-address> <port>" command: This command does not work if you specify the <Service-IP-address>. Instead, you must specify the <Service-Name>.

Non-standard query packets are altered before they are forwarded to back-end servers, which causes the server to respond with a "FORMAT error" message.

If the NetScaler appliance receives a prelogin message request from a Visual Studio 2015 client, it sends an incorrect response. As a result, the client becomes unresponsive.

When the MEP connection between two GSLB sites is reestablished after going down, the connection becomes active immediately, but the NetScaler GUI and CLI do not show it as UP for about 9 seconds.

In a GSLB deployment, if monitors are bound to GSLB services and the trigger monitor is set to MEP_DOWN. The remote GSLB services are incorrectly marked as down when MEP goes down due to temporary network outage but the MEP connection is still active.

If integrated cache is enabled on a NetScaler appliance running software version 11.0-65.x or earlier, web insight reports are not available in the Insight Center.

If you set the PINNED option for a cache content group, caching continues in this group even if the group uses more than its allocated memory, until the integrated caching memory is exhausted. Because cached objects in these groups cannot be removed until the appliance is restarted, there might be a situation in which no more objects can be cached and the appliance resets the connections of clients who send additional requests.

If a large number of concurrent NITRO requests are issued, many requests time out.

Workaround: Do not allow more than 20 NITRO calls at any given point.

The Goto Priority Expression field is missing for a Traffic Management session policy bound to a AAA user or group under Netscaler > Security > AAA > Policies > Session.

Certificate authentication does not work from the CLI if the Client Authentication option is not set on the NetScaler Gateway Virtual Server. Using NSGClient, it only works if you do the following: enter Preferences/Configuration, enter the Password for the certificate, and log in.

The issue has been resolved except for the following case:

- When TwoFactor is set to OFF, and SSL Reneg is set.

If Netscaler Gateway is configured with SmartControl, the SmartControl Policies are not applied for some network conditions that cause the ICA packets to be fragmented when they reach the Gateway.

End Point Analysis (EPA) scan to check if the Windows update agent is enabled/disabled fails intermittently.

If SSO is enabled on an AAA TM or Gateway configuration, the Netscaler appliance might fail.

Perl script was modified to avoid a variable used for the password.

Adding a proxy server to a NetScaler Gateway traffic policy causes monitoring every five seconds. This can cause excessive monitoring of network packets.

The pre-auth EPA scan for F-Secure antivirus fails.

LDAP referrals do not allow the AAA auth user to log on. An attempt to log on as an AAA auth user causes the NetScaler appliance to fail.

The NetScaler appliance issued negative values for Total_bytes_recv within the SSLVPN ICAEND_CONNSTAT ns.log message.

A login script intermittently fails to execute if deployed on a file share that requires domain authentication, if the client machine is joined to a domain whose name is longer than 16 characters.

The NetScaler appliance failed shortly after an upgrade from software release 10.1 build 129.11 to release 10.5 build 61.11. This failure is rare. It happens when core-to-core (packetEngine-to-packetEngine) copying of AAA sessions exceeds the 64KB limit.

If, when defining an application in the CloudBridge application classifier, you include a colon (:) in the name, the application's data is not exported correctly to the AppFlow collector.

In HDX-Insight, the location of public IP addresses is not displayed on the geo map.

In Security Insight, there might be a delay in receiving the safety profile configuration data for some applications.

The 11.0 66.11 SDX platform release now supports the following SDX appliances: SDX 14000, SDX 14000-40G, and SDX 25000-40G.

The SDX platform release consists of two separate images, one for SVM and one for the SDX platform. When upgrading to this platform release from an earlier release, upgrade the two images in the order suggested above.

Also, NetScaler VPX instances based on release 11.0 66.11 can be used on SDX 14xxx/25000 series appliances running either 11.0 66.11 or an earlier version of the platform software, such as 10.5 62.x that supports these series of appliances.

Note: NetScaler VPX is not part of SDX platform release, and it can be based on any NetScaler release version / build that supports SDX 14xxx/25xxx series.

A NetScaler VPX instance that is deployed on the Hyper-V may crash or unexpectedly reboot if it uses three or more virtual interfaces in the VPX instance.

The NetScaler appliance sends GARP request for a non-addressable virtual server when the virtual server's state changes to UP or DOWN.

In an active-active deployment using VRRP, a NetScaler appliance does not match its configured bridge ACL rules to the packets received from the inactive VIP addresses of the other NetScaler appliances.

The NetScaler appliance might fail if secure management access (HTTPS) is enabled on a SNIP6 address that is configured for a traffic domain.

The NetScaler appliance does not retain the entire 64 bit ID of IPv6 fragments of a session. As a result, the session might fail.

The T1120 and T1300-40G platforms with NIC firmware 4.53 are now supported in this release.

Note: T1300-40G platform with NIC firmware 4.26 has backward compatibility.

After you upgrade to this build, configuring a front-end service, or creating an internal service, with default ciphers results in a cipher inconsistency between a packet engine and the cluster configDB.

A NetScaler appliance fails if the Front End Optimization (FEO), Application Firewall, and SSL features are all enabled and the appliance encounters an error while parsing an HTML response.

In a wildcard virtual server configuration, a NetScaler appliance dynamically identifies an origin service by opening a probe connection. If the origin responds with a jumbo Maximum Segment Size (MSS), the appliance uses the MSS for future connections with the origin. If the jumbo frame support is disabled, it results in transactions failure.

The NetScaler appliance might fail if both of the following conditions are met:

- One or more of the following features are configured on the appliance: cache redirection, content switching, AAA-TM, Clientless VPN, full tunnel VPN, forward proxy.

- The client connection times out while the DNS name is being resolved using the FQDN of back-end servers.

A NetScaler appliance fails when an MPTCP subflow receives an Infinite DSS mapping in a partially retransmitted packet.

A high availability pair fails if an HTTP response from a back-end server contains carriage return line feeds (CRLFs) after the HTTP Content Length and at the start of a new packet.

The "start nstrace" command has a new parameter, -capsslkeys, with which you can capture the SSL master keys for all SSL sessions. If the capsslkeys option is enabled, a file named nstrace.sslkeys is generated along with the packet trace and imported into Wireshark to decrypt the SSL traffic in the trace file.

When the NetScaler appliance is configured as a SAML Identity Provider (IdP) with Negotiate/Kerberos, authentication fails if you are running a client debugger such as Fiddler, that does not send negotiate headers.

Workaround: Do not use Fiddler or a similar client debugger in such use cases.

You cannot load balance external AAA servers, such as LDAP, RADIUS, or TACACS servers, in a non-default partition.

The NetScaler appliance exhibits some inconsistency in the way expired cookies (TEMP) are handled:

- On an existing TCP connection, access to backend resources is allowed.

- On a new TCP connection, the request is denied.

The NetScaler appliance fails if authentication is disabled while user authentication is in progress.

The NetScaler implementation of Kerberos does not fully implement the ktutil functionality. While this does not affect Kerberos authentication, it restricts some administrative tasks, such as the ability to merge keytab files.

Forms based authentication on NetScaler failed once in 11.0 62.x. However, it never resurfaced. Users are advised to use later versions of 11.0.

After adding an admin partition, make sure you save the configurations on the default partition. Otherwise, the partition setup configurations will be lost on system reboot.

With stateful connection failover configured on a partitioned NetScaler appliance, heavy FTP traffic and frequent failovers can cause the appliance to become unresponsive and fail.

In a non-default partition, if the network traffic exceeds the partition bandwidth limit, the FTP control connection fails but data connection remains established.

The following two issues can occur if you add an external group as a system group on a NetScaler appliance and use the "set system group" command to configure the prompt string and timeout parameters at the system group level:

1. Session timeout-When a user from an external group logs on to the NetScaler command line interface (CLI), the session timeout set for the group is not applicable to sessions in the default and non-default partitions. However, if you configure the timeout parameter by using the "set system parameter" or "set cli mode -timeout <seconds>" commands, the session times out as specified.

2. Prompt string missing-When a user from an external group logs on to the NetScaler command line interface (CLI), the prompt string does not appear in the default and non-default partitions. For example, in a default partition, instead of "<pstring>" only ">" appears, and in a non-default partition, instead of "<pstring-partitionname>" only "partitionname>" appears.

However, if you set the prompt string by using the "set system parameter" or "set cli prompt" commands, the prompt string is displayed. For example, cliprompt> appears in a default partition, and cliprompt-partitionname> appears in a non-default partition.

The auto synchronization of GSLB configuration fails if the local and remote GSLB sites are configured on two different partitions of a NetScaler appliance.

RPCSVR services cannot be configured in admin partitions.

Admin partitions are not supported on FIPS appliances. However, owing to this issue, you can create admin partitions on FIPS appliances. You are advised against creating such partitions as they will not function properly.

When a user is authenticated, the persistence cookie is set, and any subsequent request that includes the cookie and matches the basic pattern is granted access to the server. However, in a non-default partition, if you specify a value for the ns_aaatm_tempc_allow_patterns default pattern set, the value is ignored.

The NetScaler appliance does not perform policy evaluation for traffic other than related to SSL and Load balancing configurations. As a result, the appliance does not create AppFlow records for these traffic.

A NetScaler load balanced server responds with a 411 error code for a corrupted HTTP request.

The NetScaler appliance does not export L7 AppFlow records when using HTTP/2.

Workaround: Disable AppFlow or specify HTTP/1.1.

When a NetScaler appliance is upgraded from a 10.1 build to a 10.5 build, the application firewall signature names are converted to all lowercase characters. If the name of the signature contains any uppercase character, the conversion affects the binding between profile and signature. Any attempt to modify either the profile or the signature object displays an error message in the configuration utility.

NetScaler Application Firewall Default Signature object now has rules that can be enabled to protect against Shellshock vulnerability (CVE-2014-6271, CVE-2014-7169) which could allow arbitrary code execution.

Application firewall memory allocation failures might occur, when the integrated cache is also enabled and the memory usage limit for the cache parameter is set to a high value.

In a high availability (HA) deployment with application firewall signatures configured on the NetScaler appliances, a file synchronization issue can lead to mismatched schema versions, which can affect signature management and functionality after a firmware upgrade to install a new build.

Workaround: If you have not yet upgraded your firmware, perform the first of the following procedures. If the firmware has already been upgraded, perform the second procedure.

Recommended procedure for upgrading the firmware in an HA deployment if application firewall signatures are configured

1. Before you upgrade the firmware, disable Signature auto-update (if set).

2. Drop into the shell from the CLI and delete the /nsconfig/updated_signatures.xml file (if present) from the primary appliance first, and then from the secondary appliance.

3. Proceed with the recommended HA rolling upgrade procedure

Recommended workaround if you have already done the firmware upgrade without the above steps and have encountered the issue

1. Drop into the shell from the CLI and delete the /nsconfig/updated_signatures.xml file from the primary appliance, and then delete it from the secondary.

2. On the primary, use the GUI to export all user-defined signatures from the primary and save them in a local file.

3. Unbind the signatures from the profile(s) if already bound.

4. Delete all user-defined signatures.

5. Use the GUI to import all the signatures that you saved in the local file.

6. Bind the signatures to the target profiles.

When you use the NetScaler GUI to perform the Skip operation, the application firewall learned rules might not be deleted. This occurs because NITRO is sending wrong "Location" ("Field") data to the GUI. With this fix, the GUI converts "Field" into "FORMFIELD," and the Skip operation removes the skipped rules, as expected.

The customer's application does not work when the application firewall is deployed to inspect the request for security check violations. When the application firewall forwards the request to the backend server, the server responds with a 403 HTTP error code, indicating that it cannot properly validate the CORBA session, and sends the page without the expected data in the form fields. The root cause is under investigation.

Workaround: Turn off form field tagging and credit card checks.

If the server sends less data than the amount specified in the Content-length header, the NetScaler application firewall might send a 9845 response and reset the connection.

The application firewall Graphical User Interface might display a warning when the Qualys signature file is uploaded to the NetScaler appliance. The transformation program that reads the input file is treating a warning message as an error.

On a NetScaler appliance running release 11.0 or later, the web application firewall (WAF) does not always function as expected if the DefaultCharset in a profile is not specified correctly. If a request does not have a content-type header, the WAF uses the DefaultCharset specified in a profile.

When editing application firewall signatures, you cannot sort on the "Enabled" column.

The application firewall learning engine is not able to connect to the packet engine in certain circumstances. When this happens, the aslearn process does not start and the application firewall learning functionality stops working.

If a user request triggers an application firewall policy that is bound to the APPFW_BYPASS profile, the application firewall might fail to generate an SNMP alarm.

The application firewall allows configuring default field format parameters. The valid range for the maximum field format length is 1-65535. The GUI as well as CLI currently accepts zero as input even though zero is outside the allowed range.

In NetScaler 9.3, if there is a standalone application firewall license, the user is able to bind a classic application firewall policy to the load balancing virtual server. However, in NetScaler 10.1, the design is changed. If the load balancing feature is not licensed, binding a classic application firewall policy to the load balancing virtual server now results in an error message.

A POST request with an attached word document is silently blocked by the application firewall for a customized application.

On a NetScaler appliance that has standalone application firewall license, when you bind a classic application firewall policy to a load balancing virtual server, an error message is displayed in the graphical user interface. The binding operation is successful. The error message is harmless and can be safely ignored.

The application firewall learning engine stops recommending new rules when the learning database grows to approximately 20-22 megabytes in size. The database size limit is applied on a per profile basis.

In a high availability (HA) deployment, a memory leak can occur if auto-update of application firewall signatures is enabled or you update the signatures by using the -mergedefault option.

During an upgrade of a NetScaler appliance from version 10.0 to version 10.1 (build 121.1 or subsequent), the default JSON content type is not automatically configured. The default JSON content type is configured when version 10.1 (build 121.1) is installed on new hardware or in a new VPX instance. To check whether your appliance or instance has the correct default setting, log onto the NetScaler command line and type the following command:

show appfw JSONContentType

If the default content type is configured, the command output is similar to the following example:

> show appfw JSONContentType

1) JSONContenttypevalue: "^application/json$" IsRegex: REGEX

Done

If it is not, the screen shows only the following:

> show appfw JSONContentType

Done

To add the default content type to the configuration, after upgrading to 10.1 (121.1), log onto the NetScaler command line, and then type the following commands to configure the default content type and verify the configuration:

add appfw JSONContentType ^application/json$ -isRegex REGEX

show appfw JSONContentType

If you use the NetScaler GUI to access the application firewall security check violation log messages from a profile, the syslog viewer cannot display the logs if they are not in the CEF log format. You can enable CEF logging from the application firewall settings pane in GUI the or use the following command from CLI:

> set appfw settings CEFLogging ON

The cookie consistency behavior has changed in release 11.0. In earlier releases, the cookie consistency check invokes sessionization. The cookies are stored in the session and signed. A "wlt_" suffix is appended to transient cookies and a "wlf_" suffix is appended to the persistent cookies before they are forwarded to the client. Even if the client does not return these signed wlf/wlt cookies, the application firewall uses the cookies stored in the session to perform the cookie consistency check.

In release 11.0, the cookie consistency check is sessionless. The application firewall now adds a cookie that is a hash of all the cookies tracked by the application firewall. If this hash cookie or any other tracked cookie is missing or tampered with, the application firewall strips the cookies before forwarding the request to the back end server and triggers a cookie-consistency violation. The server treats the request as a new request and sends new Set-Cookie header(s).

The application firewall has memory limitations on the size of a WSDL that can be imported into the NetScaler appliance. The import operation might fail if the size of the WSDL file exceeds the allocated memory.

During synchronization and saving a system configuration, if Cache Redirection (CR) policy is configured before an audit message action, it results in an improper sequence of CR policy and audit message actions.

In a cluster deployment, if a request is received by a node other than the node on which the client request is received, a packet loop delays the response to the request.

RADIUS/TACACS remote server auditing does not work.

When WIonNS is deployed in a cluster setup, an error is thrown when you rename a service that points to the IP address of the cluster configuration coordinator.

When WIonNS is deployed in a cluster setup, an error is thrown if you change the IP address of the WI service to point to the IP address of the cluster configuration coordinator.

When WIonNS is deployed in a cluster setup, if the service IP address is modified using the "set" command, the "show" command continues to display the previous IP address.

When a cluster is connected to more than one upstream router:

- When AS OVERRIDE is not configured on the upstream router, spare nodes will learn VIP routes from one of the routers, but they will be dropped as the path contains its own AS to prevent loop formation.

- When AS OVERRIDE is configured on any upstream router for cluster neighbors, upstream router will change AS path in VIP to its own AS while sending updates to cluster neighbors. Spare nodes will not detect any loop and learnt VIP routes are advertised to other routers.

Spare nodes will not advertise their configured VIP routes but there is no such restriction on BGP learnt routes.

When a node is removed from a L3 cluster, IPv6 SNIP addresses and routes are being erroneously cleared from the appliance. This behavior is seen only for IPv6 entities. IPv4 SNIPs and routes are not being removed from the appliance.

When L2 mode and MBF is enabled in a cluster deployment, access to * 80 services can fail intermittently.

When you use the Net::SSH::Perl library to connect to the NetScaler appliance, and run a command where an argument has a @ character, an error message appears indicating that the argument does not exist.

For example, an error message appears if you use the @ character in the tacacsSecret parameter of the following command:

> set authentication tacacsAction TACACS-0101 -tacacsSecret Sl4make5f0rd@enc5

Workaround: Use one of the following alternate approaches:

- If you use the Net::SSH::Perl library, include double quotes around the command when calling $ssh->cmd().

- Use the Net::Telnet library.

- Use the Net::SSH::Expect library.

The NetScaler command line interface exits abruptly upon executing the "show dns addRec -format old" command.

You cannot upgrade to NetScaler 11 from the following builds by using the Upgrade Wizard of the NetScaler GUI:

- All builds of NetScaler 9.3

- All builds of NetScaler 10.1

- Any build before Build 57.x of NetScaler 10.5

Workaround: Use the command line interface to upgrade the NetScaler appliance.

A NetScaler appliance configured for DNSSEC offloading might fail because of a race condition that can occur when the appliance receives a DNS query for a type A record for a domain that also has a CNAME record, and the canonical name identifies a domain that is in the zone offloaded for DNSSEC processing.

In a deployment with heavy DNS traffic and many DNS cache entries, some entries in the cache might not get updated or deleted, even after the TTL expires.

GSLB force sync option fails, if the following conditions are met:

* The same load balancing (LB) monitor is bound to a GSLB service as well as other LB entities.

* The server IP address already exists in the slave node under non-GSLB entity (the entity with same server IP address but with different server name) and the master node tries to synchronize the configuration.

If you rename a server associated with a GSLB service and then run the sync gslb command, the GSLB configuration might not synchronize with the other GSLB sites.

Workaround: Manually update the server name in the other GSLB sites.

On a NetScaler appliance, the default memory allocation is 10 MB per partition. In certain use cases, the allotted memory might not be sufficient for adding the maximum number of entities. You can increase the memory allocation by running the following command:

set partition <partition_name> -MaxMemLimit <limit>

For example, To increase the partition memory allocation to 50MB, at the NetScaler command prompt, type:

set partition p1 -MaxMemLimit 50

In a typical GSLB deployment, when internal user logon is disabled, GSLB auto sync uses SSH keys to synchronize the configuration. In a partitioned environment, however, GSLB auto sync cannot use SSH keys to synchronize the configuration across the GSLB sites.

Workaround: To use GSLB auto sync in partitioned environment, enable internal user logon and make sure that the partition user name is the same at the local and remote GSLB sites.

Gateway Insight does not report authentication based failures unless the enableEnhancedAuthFeedback parameter is ENABLED in the AAA parameter settings on the NetScaler appliance.

> set aaa parameter enableEnhancedAuthFeedback YES

If you upgrade a NetScaler appliance in a high availability (HA) setup to the latest build of the same release, HA synchronization and command propagation are disabled during the upgrade process. However, after both the appliances are upgraded to the same NetScaler software version, HA synchronization and command propagation are enabled automatically.

The IC memory once set for an admin partition, cannot be reduced. An appropriate error message is displayed.

For example, if the IC memory of admin partition is 10 GB, you cannot reduce it to 8 GB. The memory limit can however be increased to a required value.

After an upgrade, Content Acceleration feature is not supported.

A NetScaler appliance fails multiple times after a cache parameter is enabled during an HA persistency test.

A subscriber cannot initiate more that eight simultaneous sessions.

The NetScaler appliance does not support an outbind operation. That is, the appliance does not support an operation in which the message center initiates an SMPP session to an ESME.

IPV6 addresses are trimmed when data is retrieved from the packet engine because the prefix length variable is unset during the GET operation.

If a NetScaler appliance sending a DNSSEC negative response over UDP is not able to include the required records (for example, SOA, NSECs, and RRSIG records) in the Authority section, the appliance might send a truncated response in the wrong packet format.

In rare cases, during a high level of CPU usage, if you disable and enable a service with zero delay, the state of the service might be inconsistent on different packet engines.

When displaying the results of the "show lb monitor" command, the numbering of the user-defined monitors restarts from 1 instead of continuing the numbering from the list of built-in monitors.

If the IP address and port of a dispatcher for a user monitor are set to the IP address and port of a service, and this service is later deleted, the appliance fails if you try to add a service with the same IP address and port.

For external users that require challenge-response, authentication through NITRO does not work.

When using the NITRO API to upload a file, make sure that each directory in the file path has the 755 (read, write, execute) permission.

For example, to upload a file to the "/nsconfig/ssl/" directory, the following directories must have the 755 permission:

- flash (because the "/nsconfig" folder is actually a link to "/flash/nsconfig/" directory)

- nsconfig

- ssl

When using the .NET SDK, the application cannot establish HTTPS connection with the NetScaler appliance. This is a result of some certificate validation issues.

Information published in eDocs states that NSG firmware v11.0 supports NSG Plug-in v10.1. NSG Firmware only supports v11.0.

The following XM wizard names: _XM_<VIP_IP> should be reserved. These names should not be re-used for additional configuration entities. If the same convention is re-used, the edit/delete of the XM wizard could delete the configuration; even though, it was not pushed by the wizard.

An interface does not appear as tagged or untagged in the network visualizer.

The Surge protection feature cannot be configured in an admin partition. Since, surge protection parameters are part of the Change Global System Settings (System > Settings) dialog, when you try to update the global settings, the "Operation not supported" message is displayed.

If a policy is bound to or unbound from system global or the priority of the policy is modified, the changes are not reflected automatically. To see the current status, click the Refresh icon at the top right corner of the policy view. After you refresh the view, the policies display their bound status as well as their priorities.

In the NetScaler GUI, the page at System> Network > IPs does not display the Type for LSN NATIPs, and the value shown for Traffic Domain is incorrect.

Workaround: Run the sh nsip command to display the values in the command line interface.

If you specify an invoke label, such as policy label or virtual server, in your policy you cannot view the details of the invoke label directly.

Workaround: Select the invoke label and click Edit.

In the network visualizer, if you click a tagged interface that is part of two or more VLANs, only the VLAN at the top of the list of bound VLANs is highlighted.

The bridge group and VLAN association is not displayed in the network visualizer.

On Android 4.4.2.devices, after frequent network changes, the VPN session may disconnect. Until the device is rebooted, a new VPN session can not be established. Upgrading the Android version resolves the problem.

If the STA service goes down, entries are not written to the ns.log/syslog, and SNMP traps are not sent.

NetScaler Gateway will not sync the sessions between the primary and secondary in a HA pair, during rolling upgrade, if one of the appliances is running 11.0-64.x and the other one is running 11.0-65.x.

When customizing a portal theme according to older processes, for example using the command "set vpn parameter -UITHEME CUSTOM" the administrator needs to copy the CSS files in the NetScaler shell. Because of the design changes for Portal customization in NetScaler Gateway 11.0, copying the CSS files is required. Complete the steps described in the documentation page at:

http://docs.citrix.com/en-us/netscaler-gateway/10-5/ng-connect-users-wrapper-con/ng-connect-users-cr-integration-con/ng-connect-custom-theme-page-tsk.html

The following changes to the steps are needed:

After step 3,

4) At command prompt, type "cd /var/netscaler/logon/themes/ "

If you want to customize the Greenbubble theme, then

"cp -r Greenbubble Custom"

Or if you want to customize the Default theme, then

"cp -r Default Custom"

Now, you can make changes to files under "/var/netscaler/logon/themes/Custom"

Make edits to css/base.css

Copy custom logo to the /var/ns_gui_custom/ns_gui/vpn/media folder

Make changes to labels in the files in resources/ directory. These correspond to different languages.

Note: You can use WinSCP to transfer the files.

If changes to html pages or javascript files are also needed, then edits in "/var/ns_gui_custom/ns_gui/" would be needed.

After all changes are complete for the files in "/var/ns_gui_custom/ns_gui"

At command prompt, type

"tar -cvzf /var/ns_gui_custom/customtheme.tar.gz /var/ns_gui_custom/ns_gui/*"

5. Use the configuration utility to switch to the custom theme.

The previous Step 5 is not required in NetScaler Gateway 11.0. Once changes are made to one appliance, they propagate to all appliances in HA or cluster configurations.

If certificate authentication is configured with renegotiation and if 'Deny SSL Renegotiation' is set to 'All', user connections fail. The 'Deny SSL Renegotiation' parameter must be set to 'No'.

To configure Deny SSL Renegotiation

1. In the configuration utility, on the Configuration tab, in the navigation pane, expand Traffic Management and then expand SSL.

2. In the details pane, under Settings, click 'Change advanced SSL settings'.

3. Select 'No' for 'Deny SSL Renegotiation' and then click OK.

If you create a new password that does NOT meet the minimum requirements or use a recent password again.The error message States: Password Expired. Please Enter a new Password.

The Expected error message should be the following: Could not update your password.

The password must meet the length, complexity, and history requirements of the domain.

This issue only occurs if there is more than one policy bound on the Gateway in cascading format. If one of the policies are removed, then the error message is correct.

WebFront does not work with StoreFront 3.0. WebFront relies on NPAPI to interacting with the Receiver.

The NetScaler Gateway URL cannot be added to a Store with Receiver for Windows if only the SHA 384 cipher is enabled in the Receiver OS.

During VPN session removal, a crash occurs. It happens while detaching the VPN session policies, inherited from VPN virtual server, due to inconsistent data structures

If accessing full OWA through the CVPN, the following options are not rewritten on the NetScaler Gateway Server:

- Set Automatic Replies

- Manage Apps

- Change Passwords

- Sign-out

The pop-up messages for NetScaler Gateway Plug-in for Windows appear behind the active applications (such as browsers) on Windows 8.

A device crashed and rebooted. The cause is under investigation.

The logo does not appear on the home page.

The Tomcat server fails intermittently after installing Web Front.

Portal Customization: customization changes take a maximum of 120 seconds to reflect on the browser due to the Integrated Caching feature that polls for updated Gateway resources every 120 seconds.

When Unified-Gateway is deployed with GSLB configured with sitePersistence as ConnectionProxy, then access to published applications with -ssotype selfauth will not work when the connection is proxied from one site to another.

When using the Smart Control configuration, the ICASESSIONTIMEOUT feature is always enabled. There is not an option to disable it.

The ICA-Proxy Session Timeout Termination does not work if the app is launched after the authentication session has timed out. If the session times out, or is removed before ICA file is launched, then this feature does not apply.

If an Autoproxy script is configured on a client's machine, but the Autoproxy URL in that script is inaccessible from the client's machine, the client receives a prompt to overwrite the EPA package files. This issue occurs intermittently.

When logging in from Chrome (with NPAPI disabled) and the plug-in is installed (old plugin that doesn't know the new custom URL implementation) in the machine and is not running, you are prompted to Download instead of auto-upgrade.

The receiver redirects to the URL page after Profile installation.

When you navigate to Settings > Options > Account in an Outlook Web Access browser, the account information does not appear. This issue occurs on IE 10 and IE 11 browsers.

Currently, only one Gateway virtual server is allowed as a target behind the Content Switching virtual server. We do not allow multiple Gateway virtual servers to be bound to same Content Switching virtual server.

In the EULA and native client, some French characters do not render properly.

The NetScaler appliance issue the following message: Your sign-on has expired, please sign-on again to continue WorxHome.

Workaround: Customer rebooted the NS and issue got resolved.

The VPN plugin resets the tunneled TCP connection if either party tries to close the connection by sending FIN.

If Pre-Auth EPA is configured and the EPA Plugin is installed, the NPAPI prompts a "Launch Application" on "f_ndisagent.html" before the VPN Plugin installation is started.

After the NetScaler 11.0 65.31 upgrade, the NetScaler appliance had problems connecting to the AppController via XenMobile. This issue has been assigned and under investigation.

Certificate based authentication fails for devices running Android versions before 5.0. This is applicable if only TLSv1.2 is enabled on server.

When set in the Authentication Profile of a load balancing virtual server that is behind a Unified Gateway, the Authentication Domain parameter will cause single sign-on to fail when the authentication is performed by a traffic manager in a different traffic domain.

A selected certificate does not get saved when SSL renegotiation with two-factor authentication is enabled. The certificate does get saved when certificate authentication is enabled.

Android devices prior to version 5.0, SSL renegotiation fails when TLS1.2 is enabled.

The Linux NetScaler Gateway client fails to launch its system tray icon after installation in Ubuntu 14.04.

Root cause: Ubuntu has turned off whitelisting since version 13.10.

Steps to fix:

sudo apt-add-repository ppa:gurqn/systray-trusty

sudo apt-get update

sudo apt-get upgrade

Then logoff and log in again.

References:

http://ubuntuforums.org/showthread.php?t=2217458

http://askubuntu.com/questions/456950/system-tray-icons-disappeared-after-installing-ubuntu-14-04

https://launchpad.net/~gurqn/+archive/ubuntu/systray-trusty

In Linux, an EPA scan fails for scan strings that contain an underscore character (_) in the file or process name.

OPSWAT scan fails to detect System Center Endpoint Protection for Mac. The issue is assigned and under investigation.

The NetScaler appliance is not able to connect a Mac computer to the VPN if only SSLv2 is enabled.

The NetScaler Gateway Client icon in Launchpad is not updated with the new client installation. Launchpad continues to show the previous Black Lock icon even though the new Blue Lock icon is shown elsewhere in the Finder. This happens because the Finder caches application icons and their aliases. As a result, the Launcher does not update the alias icon when the application's icon has been changed.

Workaround - Clear the Finder's icon cache using following article's instructions: http://apple.stackexchange.com/questions/151549/symbolic-link-icons-dont-update (requires reboot) OR modify the application aliias name in /Applications/Citrix by adding few spaces (minimum two).

During login, the icon present in the dock is changed to the previous version's icon. After the login process is finished, the icon changes to the new icon.

Workaround: Quit the plugin and restart it. The new icon shows normally during the login process.

Users with Microsoft User State Virtualization (roaming profiles + folder redirection + offline folder support) enabled on laptops are having issues using SSL VPN through NetScaler Gateway. Users without MS USV are working with SSL VPN without any issues.

The NetScaler Gateway client plug-ins will not decouple immediately for previously installed clients after the 'Show VPN Plugin-in icon with Receiver' option is enabled. Users needs to exit the plugin process and restart to complete the decoupling.

If you are using IE11 to configure CVPN, security may be compromised when using non-secure sources on a HTTPS page.

When authprofile and authentication are configured to enable load balancing, the NetScaler appliance displays the /VPN/ Index page when it should display the HTTP Error 401- unauthorized access message. This happens intermittently when forms authentication enabled load balancing is modified for 401 authentication.

The following EPA configuration is not supported on Linux NSGClient.

add preauthenticationaction <name> ALLOW

-defaultEPAGroup <string>

-deletefiles <string>

-killProcess <string>

When the following command is configured on a NetScaler appliance, an empty CSEC string is sent to the client. As a result, browser plug-in or executable is terminated. "Error: Not a privileged User" is displayed and login is blocked.

This issue is seen on 64-bit machine.

End users are unable to access some versions (builds) of Outlook Web Access 2013 through NetScaler Gateway after the 11.0.63.x. firmware upgrade.

A seamless Single Sign-On (SSO) to the same URL domain fails when a plug-in is launched in native mode.

Endpoint analysis (EPA) does not start a security scan on the user's device, and the VPN session does not launch with the proxy configured on a Chrome browser.

In a HA setup using the GUI wizard to install the WebFront package, we can select files from the local machine. These files get uploaded to /var/ folder in the primary. But they are not uploaded to secondary. The command fails on the secondary, and the package is not installed on it.

Workaround: Manually, copy the files to the same folder in the secondary node to make it work.

The NetScaler appliance crashes when the corrupted NSB structure member is de-referenced.

After you bind a NetProfile to a DTLS virtual server, DTLS connections between a client and the NetScaler Gateway virtual server might fail at the DTLS handshake stage.

Workaround: Unbind and rebind the SSL certificate-key pair on the NetScaler Gateway virtual server.

Two NSC_AAAC cookies are seen when a request is sent by a Client to the VIP. The value is the same for both cookies. One cookie is for FQDN; the other cookie is for the domain.

Two NSC_AAAC cookies are no longer seen after the version 11.0 beta.

The global settings for the graphical user interface are not shown correctly.

The install files (JRE and WF package) cannot be synced between the nodes.

Workaround: The install files (JRE and WF package) must be present in all the NetScaler appliances and must be in the same location.

POST content sent by WorxWeb through SecureBrowse for forms authentication is not passed to the back-end server under the following set of conditions:

- A traffic policy is on the NetScaler appliance routes traffic coming from the WorxWeb clients that connect to a proxy through SecureBrowse.

- The proxy requires authentication for every request.

If a user adds multiple personal bookmarks with the same URL or fileshare address, but each bookmark has a different name, then deleting one bookmark will delete all of bookmarks with the same address.

If an End User License Agreement (EULA) is bound to the VPN virtual server, the EULA check box does not appear if the nFactor authentication is enabled for Gateway.

When the icon decoupling feature is enabled, the NetScaler Gateway plugin also will quit upon a user issuing the quit command on the Citrix Receiver.

si_Cur_Clints counter increments whenever we begin a transaction at virtual server, and decrements when the corresponding server transaction is completed. However, this counter does not seem to be decremented correctly resulting in incorrect statistics

Users are blocked from sending Calendar invitations through the CVPN using owa2013. However, if the user inserts or attaches any type document, they are able to send a calendar invitation.

The NetScaler AAA daemon can fail during authentication. The error message "kevent: errno =12" was issued under stress conditions when the RADIUS user accounting is turned on. The failure is due to the system limit being reached with respect to timers.

The workaround for this is to increase the system limit for the timers.

The NetScaler appliance failed to detect the latest Chrome or Firefox browsers with OPSWAT EPA.

On the Unified Gateway Dashboard, the ICA sessions counter increases when a Full VPN session is established. Although the ICA sessions counter is not configured to collect ICA data, the ICA sessions counter increases.

A NetScaler Gateway appliance occasionally fails when SSLVPN clients are connected.

If NetScaler Gateway is configured with Pre-authentication End Point Analysis and Client Certificate Authentication policy, the policies configured with REQ.SSL.CLIENT.CERT expression does not evaluate to true.

The DNS resolution fails through NetScaler Gateway/Plugin when the clients has IPv6 enabled on the adapter, and ISP provides the IPv6 DNS address on the IPv6 stack.

Two-factor off and username extraction is not working when SSL renegotiation is enabled.

Once the Unified Gateway wizard completes, it does not enable the SSO for the session action, bound to the newly created VPN virtual server. Also, the NT Domain is not set. Manually, go to the session action and configure both, the SSO parameter and the NT Domain to achieve Single Sign-on.

The NetScaler appliance was enhanced to support binding a Netscaler Gateway virtual server as a default virtual server to Content Switching virtual server. However this support is not yet available in a Cluster setup.

Customized pages are not loaded successfully in Internet Explorer. This is a known limitation of the browser. To get the customized page in IE, open developer tools by pressing F12. Browse to the NetScaler Gateway URL, and access the customized WebFront site. Customized pages are successfully loaded in Chrome.

When Unified Gateway is deployed with seamless SSO enabled for virtual server authentication, then the authentication servers and policy realms bound at the authentication virtual server will be ignored. Instead, those authentication policies at Gateway are utilized for authentication. Authentication policies at the authentication virtual server are used when step-up authentication is configured using authentication profiles. Increasing the authentication profile's "authentication level" is the method used to step-up authentication.

Active user sessions GUI view shows Client IP as 0.0.0.0 and Server IP as 0.0.0.0 in the first row of each active user session.

The wizard does not support the creation of two Intranet Application type seamless SSO URLs using same LB with different site relative string.

The EULA feature of NetScaler does not work when Certificate Authentication is configured. EULA works fine with all other Authentication types on NetScaler Gateway.

WorxNotes does not syncing after deleting the root folder. This is not a bug.

Workaround: Add a DNS entry for the share file server in the CS virtual server.

If you log on to a Netscaler Gateway appliance that is deployed in a full tunnel mode and access numerous URLs and IP addresses, Gateway Insight reports these URLs and IP addresses as Applications on the Application tab.

When Web Insight displays URL records, the maximum size of a URL is limited to 1472 bytes.

NetScaler Insight Center displays the latency value between two hops as 0 ms, though the minimum latency value is 1 ms.

When, during a scale-out deployment of NetScaler Insight, you configure the database and connector nodes and register them with the Insight server, the console might display error code 0003 for the connectors and databases.

If you change the GUI access setting from HTTPS (the default) to HTTP, NetScaler Insight Center might not display CloudBridge reports.

The current-connection details displayed on the NetScaler Insight Center dashboard have a latency of about 2 minutes.

Gateway Insight displays the Total Byte count as 0 for remote users who have logged on to the NetScaler Gateway appliance but have not launched any application.

In NetScaler Insight Center, the Postgres database might become unresponsive if there are any hardware related faults in the Insight Center system.

In HDX Insight, Geo maps does not show city if the values for latitude and longitude are not specified.

NetScaler Insight Center does not report an application-launch failure caused by a user trying to launch an application or desktop to which the user does not have access.

If you export CSV files of WAN Insight reports, many of the fields in the CSV files might be empty.

Security Insight might display an incorrect total-violations count for some applications, because of a delay in receiving the safety profile configuration data.

If you have configured the ICA session timeout value to a high value, say 10 minutes or more, and there is no traffic flow from the NetScaler appliances, neither the timeline chart nor the tabular chart displays any data. However, the Active sessions and Active Desktops columns display the data until the ICA session timeout occurs.

To generate HDX Insight reports in a Netscaler Gateway deployment in which a content switching virtual server is bound to a VPN virtual server, a valid SSL certificate must be bound to the VPN virtual server, and the virtual server must be UP.

In NetScaler Insight Center, export functionality is not supported in Security Insight.

If you select Enable URL Data Collection in the Web Insight URL Data Collection Settings, the NetScaler Insight Center virtual appliance's available memory reduces rapidly.

Adding a new database node is now driven by auto-registration. When a kernel is imported, it requests input from user and auto-registers with the NetScaler Insight Center server. Removing a database node is currently not supported.

Insight Agent should only be added after configuring and deploying Insight DB Cluster.

In NetScaler Insight Center, some countries are not displayed on the Google geo chart.

Hiding or displaying a URL, or changing the configuration, might take longer than expected.

Feature NetScaler Insight Center

If you access a NetScaler Gateway appliance by using the IP address instead of the FQDN, single sign-on (SSO) fails, and NetScaler Insight Center fails to display Gateway Insight reports.

The HDX Insight dashboard might display the host delay value for XenDesktop 7.5 as zero.

If NetScaler Insight Center does not get a connection closure update for a particular connection ID, and the ID is reused, the source IP address of the previous connection might be displayed.

If you perform a factory reset on a CloudBridge SDX appliance that is included in the Netscaler Insight Center Inventory, the CloudBridge accelerator instance gets locked out and provisioning fails.

In NetScaler Insight Center, the Google geo chart sometimes does not display all regions.

Gateway Insight does not report DNS lookup failures.

If using any port other than 1494 or 2598 as an ICA or CGP port, you must explicitly configure it as a global ICA port in order for the HDX Insight LAN user configuration to function properly.

If the ICA Rtt column is the column in extreme left of the session details table, the pop-up box gets cropped in display.

Gateway Insight does not provide a summary view for ICA Desktops, although it does provide a summary view of ICA Applications.

If you upgrade NetScaler Insight Center to release 10.5, build 55.8xxx.e, the compression ratio values are displayed as -NA-.

Unexplained failure of a NetScaler appliance. The issue has been assigned and is being investigated.

If you enable the Appflow feature for ICA traffic on a NetScaler appliance running release 11.0, build 64.x, the appliance might become unresponsive.

Web Insight includes geo data in daily, weekly, and monthly reports only.

If advanced encryption is enabled for ICA in HDX Insight, the following sequence of events might cause the NetScaler appliance to become unresponsive:

1. A server sends improper public key information during shared-key negotiation.

2. Either the client or the server disconnects.

"XenServer HTTP not working" events can occur because of the system not assigning enough memory to the XenServer hypervisor. The cause is under investigation.

NetScaler cluster on a NetScaler SDX appliance does not support Jumbo Frames.

On adding many VPX instances, you may hit the default cache memory limit which could result in unexpected behavior.

Workaround: Increase the default cache memory limit.

In SDX systems, sometimes interface or channel binding to a VLAN fails. This happens only if the interface is down or one of the member interfaces of a channel is down.

The Management Service command-line interface (CLI) might fail if you access it over Telnet by using a Perl script with a Net::Telnet object.

If you configure Jumbo MTU with MTU greater than 1500 on an interface which is used by cluster nodes or instances on NetScaler SDX, the management service does not display any error and also the Jumbo MTU functionality does not work.

If you are upgrading NetScaler SDX 11.0 beta to NetScaler SDX 11.0 GA, then the information displayed on the screen is not proper. This does not affect the upgrade process.

The NetScaler VPX appliance is now supported on VMware ESX server version 6.0.

In rare circumstances, a NetScaler VPX instance deployed on Microsoft Azure cloud can dump kernel core after a warm restart.

On a NetScaler instance deployed on Azure, dummy policies, actions, and load balancing virtual server configurations on an instance are lost if you restart the instance.

In a Unified Gateway deployment, if the first policy that's configured in an authentication cascade is SAML, the user is taken to the NetScaler logon page instead of to SAML IDP. Redirect to SAML IDP happens after authentication on NetScaler fails. To redirect the user to SAML IDP, the administrator must configure a load balancing virtual server with a SAML configuration similar to that of a classic AAA-TM deployment.

For an RNAT connection, the NetScaler appliance drops the first packet that the server sends to the client.

In a cluster environment, vPath encapsulation may fail when MAC based forwarding is enabled.

In an active-active high availability configuration using Virtual Router Redundancy Protocol (VRRP) protocol, a ping to a virtual IP address (VIP) might fail from a node that is a backup node for this VIP address.

If you configure an INAT rule with the useproxyport parameter disabled, connections to the server fail if the source port is in the reserve port range (0-1023).

In a high availability (HA) setup, high latency might occur during configuration synchronization, resulting in some configurations not getting synchronized to the secondary node. In this situation, an HA failover results in loss of configuration.

A TCP connection involved in INAT times out at 120 seconds, regardless of what global timeout value you set for TCP client and server connections. For example, the connection times out at 120 seconds even after you run the following command:

set ns timeout -anyTcpClient 50 -anyTcpServer 50

The NetScaler appliance might become unresponsive while processing a route dependency check for multiple recursive BGP routes if the next hop for any of the routes changes or goes down.

Interfaces on NetScaler VPX appliances are not hot-pluggable, except on NetScaler VPX appliances running on Amazon AWS.

Workaround: Shut down the NetScaler VPX appliances before adding or deleting the interfaces.

With heavy traffic, some MPX 7500 appliances might either spontaneously restart (MCE panic) or become unresponsive. In extreme cases, you might have to power down and restart the appliance.

MPX-9500 and MPX-10500 systems can also be affected.

If you add an NTP time server by specifying the server name (host name), and the ns.conf file is very large, the result is a race condition in which the NTP daemon (NTPD) is started before host name services are ready.

Workaround: Do one of the following:

-Restart the NTP daemon after starting the NetScaler appliance.

-Add the NTP server by specifying the IP address of the server instead of specifying the host name.

The command for configuring a content filtering action is being saved in a wrong order in the ns.conf file. Service is a mandatory parameter for adding a add content filtering action, but the add content filter action command is saved before the command that adds the service. As a result, when the build is upgraded, the content filtering action is not configured as required.

While evaluating default syntax expression for local time zone, a NetScaler appliance incorrectly applies US daylight savings time (DST) rules in non-US timezone. This results in setting an offset time for an hour. For example, the default expression !(SYS.TIME.GE (LOCAL 8h) & SYS.TIME.LE(LOCAL 17h)) returns 'False' if the local time in US timezone is between 0800 and 1700. In the UK timezone, this expression incorrectly returns 'False' if the local time is between 0700 and 0759 and returns 'True' if the local time is between 1700 and 1759 from 8 Mar 2015 (the start of US DST) to 28 Mar 2015 (the day before the start of UK DST) and also from 25 Oct 2015 (the day after the end of UK DST) to 31 Oct (the day before the end of US DST).

After a restart, a NetScaler auto-provision daemon fails to communicate with the configuration engine.

If you have configured a DTLS virtual server and also enabled the Default profile, clearing the configuration might cause the appliance to fail.

Note: On some STA services, if you enable DTLS, you don't have to explicitly create a DTLS virtual server, because it is automatically created. The automatically created DTLS server does not cause the configuration to fail if the Default profile is enabled.

The output of the "stat ssl -detail" command is different for back-end entities than for front-end entities. The output for back-end entities does not include statistics for sessions, handshakes, or client authentications for TLS protocol versions 1.1 and version 1.2.

At the back end, the label “Authorizations” is incorrect. It should be “Authentications.”

FIPS keys that are created on firmware version 2.2 are lost after you downgrade to firmware version 1.1.

Workaround: Export the FIPS keys before you downgrade the firmware. Import the FIPS keys after the downgrade.

A certificate signing request (CSR) created by using the configuration utility might not be usable if you have not specified a common name.

Secure renegotiation using SSLv3 protocol fails on MPX-FIPS appliances running firmware version 2.2.

The number of SSL cards that are UP is not displayed in the non-default partitions. Because SSL cards are shared between the default partition and the non-default partitions, the total number of SSL cards that are UP in all the non-default partitions is equal to the number of cards that are UP in the default partition.

If you have configured an SSL_Bridge type service and bound an HTTPS monitor to it, an SSL handshake with an IIS server that uses the TLS v1.2 protocol fails. This is because the handshake requires a signature algorithm in the client hello.

Even though the clientAuthUseBoundCAChain parameter can be enabled and disabled in the backend profile, it is supported only on the front end profile.

The output of the "stat ssl vserver" command includes the statistics for non-SSL virtual servers.

If you bind a certificate-key pair to a DTLS virtual server, the following incorrect error message might appear. Ignore it. No usable ciphers configured on the SSL vserver

If you try to add a certificate bundle with the complete path to a certificate-bundle file, an error message appears. For example,

> add ssl certkey bundle -cert /nsconfig/ssl/bundle3.pem -key /nsconfig/ssl/bundle3.pem -bundle YES

ERROR: Processing of certificate bundle file failed.

Workaround: Specify only the file name. For example,

> add ssl certkey bundle -cert bundle3.pem -key /nsconfig/ssl/bundle3.pem -bundle YES

Server Name Indication (SNI) is not supported on a DTLS virtual server. However, if you enable SNI on a DTLS virtual server, an appropriate error message does not appear.

Even though TLS protocol versions 1.1 and 1.2 are not supported by firmware version 1.1, the protocols incorrectly appear as enabled by default on an SSL virtual server.

Workaround: Disable TLS1.1/1.2 explicitly on the virtual server.

If you use the add crl command in release 9.3 to add a certificate revocation list (CRL) with refresh enabled, and you don't specify a method, the add crl command returns an error after an upgrade to a later release. Unlike 9.3, later releases do not have a default method.

Adding a certificate revocation list (CRL) on the NetScaler appliance fails with the error message "Certificate Issuer Mismatch" for a DER certificate, and with the error message "Invalid CRL" for a PEM certificate. This issue is seen because the attribute type of the common name field for the CA certificate and the CRL are different.

After you bind a profile to an SSL virtual server, the "show running config" command incorrectly displays the settings that were in effect before the profile was bound to the virtual server. The SSL profile settings override any virtual server settings.

If importing a certificate-key file fails because of a wrong file, and you run the command again with the correct file, the operation fails and the following error message appears:

"ERROR: Import failed. Another resource with the same name being processed"

Workaround: Import the file with a different name.

Security Insight uses late accounting for historical reporting. When you view the reports in the dashboard, you might observe the following behavior for the selected duration options:

[1] 1 hour: Data for security violations triggered in last 1 minute might not be included.

[2] 1 day: Data for security violations triggered in last 1 hour might not be included.

[3] 1 week: Data for security violations triggered in last 1 day might not be included.

[4] 1 month: Data for security violations triggered in last 1 day might not be included.

The HTML-injection feature generates a special request for each embedded object, for sending timestamp-related information to the EdgeSight server. The request URL contains the content type of the object. If the Content-Type field in the request contains a space, it should be percent-encoded, but the HTML-injection feature inserts the space as is. Therefore, by HTTP standards, the request is invalid. If the "drop invalid requests" option is enabled in the applicable HTTP profile, the request is dropped and the connection is closed. Also, if the URL spans multiple packets, the NetScaler appliance crashes while processing the next packet after the request is marked invalid.

If the maximum memory limit of a TCP Buffer (TCPB) is unequally divided among Packet Engines (PE) running on a NetScaler appliance, the PE will install the TCPB on a TCP connection without sufficient memory buffer. This leads to a connection reset.

The initial client connection on the NetScaler appliance might fail if a wildcard virtual server is configured and the useProxyPort option is disabled globally on the appliance.

After the 11.0 upgrade, frequently the secondary node becomes unreachable and goes into an 'unknown' state. The NetScaler appliance must be rebooted from the LOM to get back connectivity.

A NetScaler Policy Infrastructure (PI) connection reset code for a non HTTP type virtual server might cause a memory leak.

modify interface operations are not supported with Cisco BD qsfp

After an upgrade, a system user is unable to log on to a NetScaler appliance.

The updated host name for a NetScaler appliance does not appear on the LCD panel until after the appliance is restarted.

For a client connection to a TCP virtual server, the NetScaler appliance incorrectly decrements the current number of client connections counter even when the TCP connection is terminated before the 3-way handshake is completed. The appliance incorrectly displays a large positive number of client connections even when there are no clients connected to the virtual server.

The NetScaler appliance might fail after it frees session entries for long lived TCP connections.

When client sends a small window size (less than 8190 bytes) in its request packet to a NetScaler appliance, the appliance advertises a window size of 8190 bytes to the back-end server. Upon receiving this information, the server sends up to 8190 bytes of data to the appliance, and in turn the appliance, in transparent mode, sends the same amount of data to the client, even if the actual window size is less than the window size advertised by the client. If a device between the appliance and client checks the window size before accepting the data, that device might drop the data that does not fit in the client’s window size.

Workaround: Enable the end point device (for example, TCP Buffer) in the NetScaler appliance.

FTP connections through a TCP wildcard virtual server on the NetScaler appliance might fail for one of the following reasons:

- A mismatch in TCP parameters is preventing the appliance from reusing the probe connection.

- The server is sending data before the client-side TCP connection is established.

On a NetScaler VPX appliance provisioned on Microsoft Hyper-V servers, if more than 4 interfaces are assigned to the appliance, the interfaces might get scrambled and appear in a different order in both the NetScaler command line and the NetScaler GUI.

If an LACP channel is bound to nine or more interfaces and is a member of a tagged VLAN, deleting the channel from a service VM can cause the NetScaler appliance to fail intermittently.

In previous releases, evaluation of an interface-based expression was based on the information available in the connection block and in the individual frame. Now, only the information in the frame is considered, and this information can change during the course of a transaction. As a result, the evaluation might be incorrect.

Workaround: Use VLAN-based expressions instead.

The default setting for auto-negotiation is 'OFF', which causes an error if you configure the interface from the SVM.

Connection failover might fail, if it is enabled on virtual servers that have the same IP address and port, but different listen policies.

In a high availability environment, if you add Network Time Protocol (NTP) to a primary node by specifying the NTP server's DNS name, the command is not propagated to the secondary node.

Workaround: Specify the NTP server's IP address.

If the HTML injection feature is enabled, the NetScaler appliance injects JavaScript into responses sent to clients. If a subsequent request from one of the clients is generated from the JavaScript, the appliance responds with a 404 error.

A memory-availability check can result in TCP optimization being bypassed for an incoming connection when memory being used by other data structures (for example, PCB) and later freed. When this issue occurs, TCP optimization does not resume until you warm reboot the appliance.

In an Openstack Environment, if a custom flavor with an Ephemeral Disk of Size of less than 8GB is used to a start a NetScaler VPX or Cisco Nexus 1000v instance, the config drive is not attached to the instance.

In an LSN deployment, FTP over Jumbo interfaces might not work.

In a Large Scale NAT deployment, the NetScaler appliance does not generate and send an ICMP error message to the subscriber in the event of a port allocation failure.

In a DS-Lite configuration with a server behind the B4 device, the NetScaler appliance does not properly process FTP packets that have the following set of characteristics:

* Are from clients on the Internet

* Are destined to the server

* Match DS-Lite static NAT maps configured on the NetScaler appliance

An RTSP request might be logged on two different Syslog servers.

If the provisional response to a SIP REGISTER message does not contain an expiry value, the NetScaler appliance drops the message.

In the output of the "show lsn sipalgcall -callid" command, the port value of the SIP control channel is incorrect.

If a SNIP address is added to subnet other than the one that includes the NSIP address, loop-back services go down.

If the NetScaler appliance is upgraded from version 10.1 to 10.5 and the maxSite setting of WIonNS is 3, the system does not have sufficient memory to handle 5000 users accessing WIonNS.

For NetScaler 10.5 and later releases, Web Interface on NetScaler (WIonNS) must use the OpenJDK7 package since NetScaler now uses FreeBSD 8.x/amd64. You can download the package from either one of the following links:

* http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/amd64/8.4-RELEASE/packages/java/openjdk-7.17.02_2.tbz

* ftp://mirror.is.co.za/FreeBSD/ports/amd64/packages-8.4-release/devel/openjdk-7.17.02_2.tbz

Background: When the NetScaler is upgraded to version 10.5, it still has OpenJDK1.6 instead of OpenJDK1.7 which is required for NetScaler version 10.5. Therefore, when the configurations are saved (after upgrading), the Web Interface sites become inaccessible.

Workaround: Before you save the configurations on the upgraded appliance, make sure you reinstall the Web Interface on NetScaler version 10.5 by using OpenJDK1.7.

Since the install wi package command takes more than usual time to complete, it is not possible to return the status from other nodes. Hence it is required that all the WI related packages, that is, JRE+WI be present on system on the same path for all the nodes.

The NetScaler appliance now stores AAA authentication logs.

- Errors and warnings are logged in the /var/nslog/ns.log file

- Information and debug level logs are logged in the /var/log/nsvpn.log file.

When used as a SAML IdP (identity provider), the NetScaler appliance now allows logon using certificates.

The NetScaler AAA-TM feature now supports OAuth and OpenID-Connect mechanisms for authenticating and authorizing users to applications that are hosted on applications such as Google, Facebook, and Twitter.

Note: OAuth on NetScaler is currently qualified only for Google applications.

A major advantage is that user's information is not sent to the hosted applications and therefore the risk of identity theft is considerably reduced.

In the NetScaler implementation, the application to be accessed is represented by the AAA-TM virtual server. So, to configure OAuth, an action must be configured and associated with a AAA-TM policy which is then associated with a AAA-TM virtual server. The configuration to define a OAuth action is as follows:

> add authentication OAuthAction <name> -authorizationEndpoint <URL> -tokenEndpoint <URL> [-idtokenDecryptEndpoint <URL>] -clientID <string> -clientSecret <string> [-defaultAuthenticationGroup <string>] [-Attribute1 <string>] [-Attribute2 <string>] [-Attribute3 <string>] ....

Note:

- Refer to the man page for information on the parameters.

- Attributes (1 to 16) are attributes that can be extracted in OAuth response. Currently, these are not evaluated. They are added for future reference.

When used as a SAML IdP (identity provider), the NetScaler appliance can now be configured to send 16 additional attributes in addition to the NameId attribute. These attributes must be extracted from the appropriate authentication server. For each of them, you can specify the name, the expression, the format, and a friendly name.

These attributes must be specified in the SAML IdP profile as follows:

From the CLI:

> set authentication samlIdPProfile <name> [-Attribute1 <string> -Attribute1Expr <string> [-Attribute1FriendlyName <string>] [-Attribute1Format ( URI | Basic )]] [-Attribute2 <string> -Attribute2Expr <string> [-Attribute2FriendlyName <string>] [-Attribute2Format ( URI | Basic )]]

For example, the following command adds the attribute "MyName":

> add authentication samlIdPProfile ns-saml-idp -samlSPCertName nssp -samlIdPCertName nssp -assertionConsumerServiceURL "http://nssp.nsi-test.com/cgi/samlauth" -Attribute1 MyName -Attribute1Expr http.req.user.name -Attribute1FriendlyName Username -Attribute1Format URI

From the GUI:

Navigate to the screen where you configure the SAML IdP profile, and specify the additional attributes as required.

When used as a SAML IdP (identity provider), the NetScaler appliance can now be configured to digitally sign assertions by using the SHA256 algorithm. Additionally, you can configure the appliance to accept only digitally signed requests from the SAML SP (service provider).

These configurations must be specified in the SAML IdP profile as follows:

From the CLI:

> set authentication samlIdPProfile <name> [-rejectUnsignedRequests ( ON | OFF )] [-signatureAlg ( RSA-SHA1 | RSA-SHA256 )] [-digestMethod ( SHA1 | SHA256 )]

From the GUI:

Navigate to the screen where you configure the SAML IdP profile, and specify the corresponding parameters.

When used as a SAML SP (service provider), the NetScaler appliance can now decrypt the encrypted tokens that it receives from the a SAML IdP. No configuration is required on the NetScaler.

When used as a SAML IdP (identity provider), the NetScaler appliance now allows logon using the following 401-based authentication mechanisms: Negotiate, NTLM, and Certificate.

The output of "show ns ip" now also includes the aaadnatIp address.

When used as a SAML IdP (identity provider), the NetScaler appliance can now be configured to encrypt the assertions by using the public key of the SAML SP (service provider).

Note:

- Make sure the SAML SP certificate is specified.

- For enhanced security, it is recommended that you encrypt assertions that contain sensitive information.

This configuration must be specified on the SAML IdP profile as follows:

On the CLI:

> set authentication samlIdPProfile <name> [-encryptAssertion ( ON | OFF )] [-encryptionAlgorithm <encryptionAlgorithm>]

On the GUI:

Navigate to the screen where you configure the SAML IdP profile and specify the corresponding parameters.

The configuration of a AAA-TM virtual server in the NetScaler GUI is simplified for ease of configuring the required authentication mechanism.

In a deployment where a NetScaler appliance is configured as a SAML IdP (identity provider) for multiple SAML SPs (service provider), the appliance allows a user to access multiple SPs without explicitly authenticating every time.The appliance creates a session cookie for the first authentication and every subsequent request uses this cookie for authentication.

When the NetScaler appliance is configured for Negotiate authentication and sends a 401 Negotiate response to client, if client is not able to reach domain controller or is not domain joined, then it automatically falls back to NTLM authentication and the client starts NTLM handshake. The NetScaler appliance is able to verify the credentials presented as part of NTLM authentication.

This feature allows user logins locally or remotely.

When used as a SAML SP (service provider), in addition to POST bindings, the NetScaler appliance now supports redirect bindings. In redirect bindings, SAML assertions are in the URL, as against POST bindings where the assertions are in the POST body.

Using the CLI:

> add authentication samlAction <name> . . . [-samlBinding ( REDIRECT | POST )]

The NetScaler appliance now supports the SiteMinder SAML SP.

When authentication is configured to be done by using certificates and then followed by LDAP or other authentication mechanisms, the following behavior holds true:

- In previous releases: If certificate authentication fails (or was skipped), the other authentication mechanism is not processed.

- From this release onwards: Even if certificate authentication is not done, the other authentication mechanism is processed.

The NetScaler appliance now supports a new approach to configuring multi-factor authentication. With this approach, you can configure any number of authentication factors. You can also customize the login form as required.

In NetScaler terminology, this feature is called "nFactor Authentication." For more information, see http://docs.citrix.com/en-us/netscaler/11/security/ns-aaa-app-trafc-wrapper-con-10/multi-factor-nfactor-authentication.html.

In the SAML Service Provider (SP) module, names of the attributes that can be extracted from an incoming SAML assertion can be up to 127 bytes long. The previous limit was 63 bytes.

When used as a SAML SP, the NetScaler appliance can now extract multi-valued attributes from a SAML assertion. These attributes are sent is nested XML tags such as:

<saml:Attribute FriendlyName="groups" Name="groups" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified?>

<saml:AttributeValue xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string?>

<AttributeValue>grp1</AttributeValue>

<AttributeValue>grp2</AttributeValue>

<AttributeValue>grp3</AttributeValue>

</saml:AttributeValue>

</saml:Attribute>

A NetScaler appliance can be configured to provide SAML authentication to an application by playing the role of the SAML Identity Provider (IdP) and/or the SAML Service Provider (SP). If the system time on NetScaler SAML IdP and the peer SAML SP is not in sync, the messages might get invalidated by either party.

To avoid such cases, you can now configure the time duration for which the assertions will be valid. This duration, called the "skew time," specifies the number of minutes for which the message should be accepted. The skew time can be configured on the SAML SP and the SAML IdP.

- When the NetScaler is used as a SAML IdP, configure the skew time on the SAML IdP profile, to accept incoming requests from SP and to send assertions.

--- Using the CLI: > set samlidpProfile <name> -skewTime 30

--- Using the GUI: Navigate to Security > AAA - Application Traffic > Policies > Authentication > Advanced Policies > Policy, and in the required SAML IdP policy, configure the skew time for the SAML IdP profile.

- When the NetScaler is used as a SAML SP, configure the skew time on the SAML action.

--- Using the CLI: > set samlaction <name> -skewTime 30

--- Using the GUI: Navigate to Security > AAA - Application Traffic > Policies > Authentication > Advanced Policies > Policy, and in the required SAML SP policy, configure the skew time for the SAML action.

When used as a SAML IdP, the NetScaler appliance can now send multi-valued attributes in a SAML assertion.

When used as a SAML Identity Provider (IdP), the NetScaler appliance can be configured to serve assertions only to SAML Service Providers (SP) that are pre-configured on or trusted by the IdP. For this configuration, the SAML IdP must have the service provider ID (or issuer name) of the relevant SAML SPs.

Using the CLI:

> set samlidpProfile <name> -serviceProviderID <string>

Using the GUI:

Navigate to Security > AAA - Application Traffic > Policies > Authentication > Advanced Policies > Policy, and in the required SAML IdP policy, configure the SP ID for the SAML IdP profile.

When used as a SAML Identity Provider (IdP), the NetScaler appliance now supports redirect bindings (in addition to POST binding).

Using the CLI:

> set authentication samlIdPProfile <name> -samlBinding REDIRECT

Using the GUI:

Navigate to Security > AAA - Application Traffic > Policies > Authentication > Advanced Policies > Policy, and in the required SAML IdP policy, configure the SAML binding as "Redirect" for the SAML IdP profile.

Scriptable monitors can now be configured on the admin partitions that are available on a NetScaler appliance.

Integrated caching (IC) can now be configured for admin partitions. After defining the IC memory on the default partition, the superuser can configure the IC memory on each admin partition such that the total IC memory allocated to all admin partitions does not exceed the IC memory defined on the default partition. The memory that is not configured for the admin partitions remains available for the default partition.

For example, if a NetScaler appliance with two admin partitions has 10 GB of IC memory allocated to the default partition, and IC memory allocation for the two admin partitions is as follows:

- Partition1: 4 GB

- Partition2: 3 GB

Then, the default partition has 10 - (4 + 3) = 3 GB of IC memory available for use.

Note: If all IC memory is used by the admin partitions, no IC memory is available for the default partition.

Using the NetScaler Web Logging (NSWL) client, the NetScaler can now retrieve the web logs for all the partitions with which the logged in user is associated. To view the partition for each log entry, customize the log format to include the %P option. You can then filter the logs to view the logs for a specific partition.

While dynamic routing (OSPF, RIP, BGP, ISIS, BGP+) is by default enabled on the default partition, in an admin partition, it must be enabled by using the following command:

> set L3Param -dynamicRouting ENABLED

Note: A maximum of 63 partitions can run dynamic routing (62 admin partitions and 1 default partition).

You can now generate the NetScaler trace for a specific admin partition. To do so, you must access that admin partition and run the "nstrace" operation. The trace files for the admin partition will be stored in the /var/partitions/<partitionName>/nstrace/ directory.

On a partitioned NetScaler appliance, the scope of updating the L2 and L3 parameters is as follows:

- For L2 parameters that are set by using the "set L2Param" command, the following parameters can be updated only from the default partition, and their values are applicable to all the admin partitions: maxBridgeCollision, bdgSetting, garpOnVridIntf, garpReply, proxyArp, resetInterfaceOnHAfailover, and skip_proxying_bsd_traffic. The other L2 parameters can be updated in specific admin partitions, and their values are local to those partitions.

- For L3 parameters that are set by using the "set L3Param" command, all parameters can be updated in specific admin partitions, and their values are local to those partitions. Similarly, the values that are updated in the default partition are applicable only to the default partition.

When you update load balancing parameters in an admin partition, the updates now apply to that partition only. You can have different load balancing parameter settings in different partitions.

Note:

- In previous releases, any updates to these parameters were applied across all partitions, regardless of the partition in which the changes were made.

- These parameters are set in the CLI by using the "set lb parameter" command or in the GUI by navigating to Traffic Management > Load Balancing.

The following load balancing features can now be configured in admin partitions:

- DBS autoscale

- Stateless connection mirroring

- RDP

- Radius

- Graceful shutdown

For the detailed list of NetScaler feature support on admin partitions, see http://docs.citrix.com/en-us/netscaler/11/system/admin-partition/admin-partition-config-types.html.

The NetScaler appliance now supports FTP load balancing in admin partitions.

The NetScaler appliance now supports the GSLB feature in admin partitions. You can now deploy, with an admin partition, applications that need the GSLB feature to distribute traffic across globally located datacenters.

The NetScaler appliance now supports stateful connection mirroring in admin partitions. You can now deploy TCP-based applications in an admin partition, so that failure of one NetScaler appliance does not make the application unavailable.

Note: The application must be deployed in a NetScaler high availability (HA) setup, and connection mirroring must be configured for the application.

The NetScaler appliance now supports the AAA-TM feature in admin partitions. You can now deploy, with an admin partition, enterprise applications that require authenticated access.

All application firewall graphical user interface (GUI) dialog boxes, including the ones for signatures, visualizer, and syslog viewer, are now completely free from any java dependencies and show a significant improvement in the overall performance. The HTML based GUI dialogues have been re-organized for enhanced user experience and intuitive workflow of information. Instead appearing in of pop-up dialog boxes with tabs, the information is now displayed as an in-line expansion. You can expand all the configuration sections and scroll up and down for a comprehensive view.

The application firewall is fully supported in striped, partially striped, or spotted configurations. The two main advantages of striped and partially striped virtual server support in cluster configurations are the following:

- Session failover support: Striped and partially striped virtual server configurations support session failover. The advanced application firewall security features, such as Start URL Closure and the Form Field Consistency check, maintain and use sessions during transaction processing. In ordinary high availability configurations, or in spotted cluster configurations, when the node that is processing the application firewall traffic fails, all the session information is lost and the user has to reestablish the session. In striped virtual server configurations, user sessions are replicated across multiple nodes. If a node goes down, a node running the replica becomes the owner. Session information is maintained without any visible impact to the user.

- Scalability: Any node in the cluster can process the traffic. Multiple nodes of the cluster can process the incoming requests served by the striped virtual server. This improves the application firewall's ability to handle multiple simultaneous requests, thereby improving the overall performance.

Security checks and signature protections can be deployed without the need for any additional cluster-specific application firewall configuration. You just do the usual application firewall configuration on the configuration coordinator (CCO) node for propagation to all the nodes.

Cluster details are available at http://docs.citrix.com/en-us/netscaler/11/system/clustering.html.

The field format rules specify the inputs that are allowed in the target form fields. You can also limit the minimum and the maximum allowed length for the inputs. The application firewall learning engine monitors the traffic and provides field format recommendations based on the observed values. If the initial field format learned rules are based on a small sample of data, a few non typical values might possibly result in a recommendation that is too lenient for the target field. Updates to the application firewall have now decoupled violations and learning for the field formats. The firewall learns the field formats regardless of the violations. The learning engine monitors and evaluates all the incoming new data points to recommend new rules. This allows fine tuning the configuration to specify optimal input formats with adequate min/max range values. If a rule has already been deployed for a field/URL combination, the GUI allows the user to update the field format. A dialog box asks for confirmation to replace the existing rule. If you are using the command line interface, you have to explicitly unbind the previous binding and then bind the new rule.

Geolocation, which identifies the geographic location from which requests originate, can help you configure the application firewall for the optimal level of security. For example, if an excessively large number of requests are received from a specific area, it is easy to determine whether they are being sent by users or a rogue machine. The application firewall offers you the convenience of using the built-in NetScaler database or any other geolocation based database to identify the source of origin of coordinated attacks launched from a country. This information can be quite useful for enforcing the optimal level of security for your application to block malicious requests originating from a specific geographical region. Geolocation logging uses the Common Event Format (CEF).

To use Geolocation Logging

1. Enable CEFLogging and GeoLocationLogging.

>set appfw settings GeoLocationLogging ON CEFLogging ON

2. Specify the database

>add locationfile /var/netscaler/inbuilt_db/Citrix_Netscaler_InBuilt_GeoIP_DB.csv

or

add locationfile <path to database file>

All application firewall graphical user interface (GUI) dialog boxes, including the ones for signatures, visualizer, and syslog viewer, are now completely free from any java dependencies and show a significant improvement in the overall performance. The HTML based GUI dialogues have been re-organized for enhanced user experience and intuitive workflow of information. Instead appearing in of pop-up dialog boxes with tabs, the information is now displayed as an in-line expansion. You can expand all the configuration sections and scroll up and down for a comprehensive view.

The NetScaler application firewall offers SQL/XSS security check protections to detect and block possible attacks against the applications. You now have much tighter security control when configuring SQL/XSS protections. Instead of deploying relaxation rules that completely bypass the security check inspection for a field, you now have an option to relax a specific subset of violation patterns. You can continue to inspect the relaxed field in the incoming requests to detect and block the rest of the SQL/XSS violation patterns. The commands used in relaxations and learning now have optional parameters for value type and value expression. You can specify whether the value expression is a regular expression or a literal string.

Command Line Interface:

bind appfw profile <name> -SQLInjection <String> [isNameRegex (REGEX | NOTREGEX)] <formActionURL> [-location <location>] [-valueType (Keyword| SpecialString|Wildchar) [<valueExpression>][-isValueRegex (REGEX | NOTREGEX) ]]

unbind appfw profile <name> -SQLInjection <String><formActionURL> [-location <location>][-valueType (Keyword|SpecialString|Wildchar) [<valueExpression>]]

bind appfw profile <name> -crossSiteScripting <String> [isNameRegex (REGEX | NOTREGEX)] <formActionURL> [-location <location>] [-valueType (Tag| Attribute|Pattern) [<valueExpression>][-isValueRegex (REGEX | NOTREGEX) ]]

unbind appfw profile <name> -crossSiteScripting <String> <formActionURL> [-location <location>] [-valueType (Tag|Attribute|Pattern) [<valueExpression>]]

The NetScaler application firewall module offers data leak prevention and supports credit card protection. It can examines the credit card numbers in the response and takes the specified action if a match is found. In some scenarios, it might be desirable to exclude a specific set of numbers from the credit card security check inspection. For example, server responses for some internet applications might include a string of digits that is not a credit card number but matches the pattern of a credit card number. These responses can trigger false positives and therefore get blocked by the application firewall's Credit Card security check. The application firewall now offers the ability to learn and deploy relaxations for the credit card numbers. The credit card relaxation rule provides the flexibility to exclude a specific string of numbers from the safe commerce check without compromising credit card security. These numbers are not examined in the responses even if the credit card check is ON.

Examples of CLI Commands:

1. Bind the credit card number to profile:

bind appfw profile <profile-name> -creditCardNumber <any number/regex> "<url>"

2. Unbind credit card number from profile:

unbind appfw profile <profile-name> -creditCardNumber <credit card number> "<url>"

3. Log: Enable Logging of credit card Numbers

add appfw profile <profilename> - doSecureCreditCardLogging <ON/OFF>

set appfw profile <profilename> - doSecureCreditCardLogging <ON/OFF>

4. Learn:

show appfw learningdata <profilename> creditCardNumber

rm appfw learningdata <profilename> -creditcardNumber <credit card number> "<url>"

export appfw learningdata <profilename> creditCardNumber

NetScaler now supports the IP Reputation feature, which is useful in identifying an IP address that is sending unwanted requests. You can use the IP reputation list to preemptively reject requests that are coming from an IP with a bad reputation. NetScaler uses WebRoot as the service provider for the dynamically generated malicious IP database and the metadata for those IPs. The IP Reputation feature can be configured by using PI Expressions in a policy. For example, you can configure an application firewall policy using expressions such as: CLIENT.IP.SRC.IPREP_IS_MALICIOUS.

You can now use default syntax expressions in cache redirection policies. The NetScaler appliance provides built-in cache redirection policies based on default syntax expressions, or you can create custom cache redirection policies to handle typical cache requests. In addition to the same types of evaluations done by classic cache redirection policies, the default syntax policies enable you to analyze more data (for example, the body of an HTTP request) and to configure more operations in the policy rule (for example, directing requests to either cache or origin server).

You can now configure the time interval for "Hard Disk Drive error" and "Compact Flash error" SNMP traps in a NetScaler appliance.

The NetScaler appliance now supports transferring IPv6 traffic through a IPV4 GRE tunnel. This feature can be used for enabling communication between Isolated IPv6 networks without upgrading the IPv4 infrastructure between them.

For configuring this feature, you associate an PBR6 rule with the configured IPv4 GRE tunnel through which you want the NetScaler to send and receive IPv6 traffic. The source IPv6 address and destination IPv6 address parameters of the PBR6 rule specify the IPv6 networks whose traffic is to traverse the IPv4 GRE tunnel.

In a dynamic cluster link aggregation (LA) deployment that has link redundancy enabled, you can configure the cluster to select the partner channel or interface on the basis of its throughput. To do this, configure a threshold throughput on the channel or interface as follows:

> set channel CLA/1 -linkRedundancy ON -lrMinThroughput <positive_integer>

The throughput of the partner channels is checked against the configured threshold throughput. The partner channel that satisfies the threshold throughput is selected in FIFO manner. If none of the partner channel meets the threshold, or if threshold throughput is not configured, the partner channel with the maximum number of links is selected.

By default, a NetScaler cluster steers traffic over the cluster backplane, from the flow receiver node to the flow processor node. You can disable steering so that the process becomes local to the flow receiver and thereby ensure that the flow receiver also becomes the flow processor. Such a configuration can come in handy when you have a high latency link.

Note: This configuration is applicable only for striped virtual servers.

Steering can be disabled at the global NetScaler level or at the individual virtual server level. The global configuration takes precedence over the virtual server setting.

- At the global level, steering can be disabled for all striped virtual servers. It is configured at cluster instance level. Traffic meant for any striped virtual server will not be steered on cluster backplane. The command is:

> add cluster instance <clId> -processLocal ENABLED

- At a virtual server level, you can disable steering for a specific striped virtual server. It is configured on a striped virtual server. Traffic meant for that virtual server will not be steered on cluster backplane. The command is:

> add lb vserver <name> <serviceType> -processLocal ENABLED

For more information, see http://docs.citrix.com/en-us/netscaler/11/system/clustering/cluster-managing/cluster-steering-disable.html.

In a L3 cluster, different nodegroups can have different VLANs and subnets associated with them. This can result in a VLAN getting exposed only in some nodes. Therefore, you can now configure dynamic routing on a VLAN to expose the VLAN to ZebOS even when there are no IP addresses with dynamic routing that are bound to it. The command to configure this is:

> add/set vlan <id> -dynamicRouting (ENABLED | DISABLED)

Note:

- This option is also available for VXLAN and BridgeGroups.

- This configuration can also be used for L2 clusters.

BridgeGroups are now supported in a NetScaler cluster deployment.

You can now run dynamic routing on a striped SNIP address in a NetScaler cluster. The routes advertised by the cluster have the striped SNIP as the next hop. There is just one adjacency with the cluster. Internally, the cluster picks one of the active nodes as the routing leader. When the current routing leader goes down, the routing ownership moves to an active node.

Note:

- Striped SNIP addresses are useful mainly for cluster LA (link aggregation) deployments. They can also be used for ECMP, but the multipath routing functionality is unavailable.

- Striped SNIP addresses can also be used in asymmetrical topologies.

- Routing on striped SNIPs and routing on spotted SNIPs can coexist in a cluster.

To specify leader node configurations, in the VTYSH shell, use the "owner-node leader" command.

A cluster nodegroup can now be configured to provide datacenter redundancy. In this use case, nodegroups are created by logically grouping the cluster nodes. You must create active and spare nodegroups. When the active nodegroup goes down, the spare nodegroup which has the highest priority (the lower priority number) is made active and it starts serving traffic.

For more information, see http://docs.citrix.com/en-us/netscaler/11/system/clustering/cluster-managing/cluster-nodegroups-datacenter-redundancy.html.

You can now create a cluster that includes nodes from different networks. To configure a cluster over L3, you must add the nodes of different networks to different nodegroups. For more information, see http://docs.citrix.com/en-us/netscaler/11/system/clustering/cluster-setup.html.

You can transition an existing L2 cluster to an L3 cluster. For instructions, see http://docs.citrix.com/en-us/netscaler/11/system/clustering/cluster-usage-scenarios/cluster-migrate-between-l2-l3.html.

With the Equal Cost Multiple Path (ECMP) mechanism, virtual server IP addresses are advertised by all active cluster nodes. This means that traffic can be received by any cluster node, which then steers the traffic to the node that must process the traffic. While there are no hassles in this approach, there can be a lot of redundant steering in case of spotted and partially striped virtual servers. Therefore, from NetScaler 11 onwards, spotted and partially striped virtual server IP addresses are advertised only by the owner nodes. This reduces the redundant steering.

You can override this default behavior, by entering the following command in the VTYSH shell:

ns(config)# ns spotted-vip-adv all-nodes

FTP load balancing is now supported in a NetScaler cluster deployment.

WIonNS can now be configured on a NetScaler cluster deployment. To use WIonNS on a cluster, you must do the following:

1. Make sure that the Java package and the WI package are installed in the same directory on all the cluster nodes.

2. Create a load balancing virtual server that has persistency configured.

3. Create services with IP addresses as the NSIP address of each of the cluster nodes that you want to serve WI traffic.

4. Bind the services to the load balancing virtual server.

Note: If you are using WIonNS over a VPN connection, make sure that the load balancing virtual server is set as WIHOME.

When you are upgrading a cluster to NetScaler 11.0 build 64.x from an earlier NetScaler 11.0 build, cluster configuration propagation is disabled.

Traditionally, this issue occurred only during an upgrade of a cluster to a different NetScaler version (for example, from 10.5 to 11.0). This exception arises because the cluster version in build 64.x is different from the one in previous NetScaler 11.0 builds.

Note: Normally, the cluster version matches the NetScaler version.

Configuration propagation remains disabled until all the cluster nodes are upgraded to Build 64.x.

You can now set the dead interval for a cluster instance to a minimum value of 1 second.

Note: If the dead interval value is less than 3 seconds, set the hello interval parameter to 200 ms.

The NetScaler administrator can now specify the maximum number of concurrent sessions a user can log on to the CLI. Although logons to the configuration utility do not count against the limit, all logon attempts are denied after the limit is reached. For example, if the maximum number of concurrent sessions is set to 20, a user can log on to the CLI 19 times and can log on to the configuration utility any number of times. Once the user logs on to the CLI for the 20th time, he or she can no longer log on to the CLI or the configuration utility. Any logon attempt then results in a system error message.

You can now configure a NetScaler appliance to log DNS requests and responses. The logs are in SYSLOG format. You can use these logs to:

- Audit the DNS responses to the client

- Audit DNS clients

- Detect and prevent DNS attacks

- Troubleshoot

The NetScaler appliance supports caching of negative responses for a domain. You can enable or disable negative caching from the command line, by setting cacheNegativeResponses with the set dns parameter command, or in the configuration utility, in the Configure DNS Parameters dialog box.

Note: You can enable or disable negative caching independent of global caching. By default, negative caching is enabled.

The rewrite and responder features now support DNS. You can now configure rewrite and responder functionalities to modify DNS requests and responses as you would for HTTP or TCP requests and responses.

Support for binding a single Virtual Server as a backup for multiple GSLB Virtual servers

In a GSLB site deployment, you can now bind a single virtual server as a backup virtual server for multiple GSLB virtual servers in the deployment.

Description: You can now configure a content switching (CS) policy to customize a GSLB deployment so that you can:

* Restrict the selection of a GSLB service to a subset of GSLB services bound to a GSLB virtual server for the given domain.

* Apply different Load Balancing methods on the different subsets of GSLB services in the deployment.

* Apply spillover policies on a subset of GSLB services, and you can have a backup for a subset of GSLB services.

* Configure a subset of GSLB services to serve a specific type of content.

* Define a subset GSLB services with different priorities, and define the order in which the services in the subset are applied to a request.

For more information, see Configuring GSLB Service Selection Using Content Switching.

In GSLB deployments, the NetScaler appliance now supports DNS queries with NAPTR records. You can now configure a NetScaler appliance to receive DNS queries with NAPTR records from clients (for example, Mobile Management Entity (MME))and respond with the list of services configured for a domain. Also, the NetScaler appliance monitors the health of the services and in the response it provides only the list of services that are up.

You can now configure the NetScaler appliance to use GSLB Site IP address as the source IP address for an RPC node.

HDX Insight now supports displaying of Appflow records from Netscaler cluster.

The following global timeouts has been introduced for TCP sessions on a NetScaler appliance related to RNAT rules, forwarding sessions, or load balancing configuration of type ANY:

* Any TCP Client. Global idle timeout, in seconds, for TCP client connections. Client timeout set for an entity overrides the global timeout setting.

* Any TCP Server. Global idle timeout, in seconds, for TCP server connections. Server timeout set for an entity overrides the global timeout setting.

These timeout can be set either from the NetScaler command line (set ns timeout command) or from the configuration utility (System > Settings > Change Timeout Values page).

Note: For applying these timeouts to a virtual server or service of type ANY, set these timeouts before adding the virtual server or the service.

You can now use IPv6 addresses in the following monitors:

- USER

- SMTP

- NNTP

- LDAP

- SNMP

- POP3

- FTP_EXTENDED

- STOREFRONT

- APPC

- CITRIX_WI_EXTENDED

Note: The monitor for MySQL does not support IPv6 addresses.

If you configure cookie persistence and custom cookie on a virtual server, and later change the name or IP address of the virtual server, persistence is not honored.

You can now monitor LDAP services over SSL. To monitor the LDAP services over SSL, use the built-in LDAP monitor or create a user monitor and enable the "secure" option.

In earlier releases, if the internal dispatcher failed, the services that used scriptable monitors also went down and the appliance had to be restarted. From release 11, if the internal dispatcher fails, the pitboss process restarts it. As a result, you no longer have to restart the appliance. For information about user monitors, see http://docs.citrix.com/en-us/netscaler/11/traffic-management/load-balancing/load-balancing-custom-monitors/understand-user-monitors.html.

If you have set the persistence type to COOKIEINSERT, you can now encrypt the cookie in addition to any existing SSL encryption by using the NetScaler command line and configuration utility.

At the NetScaler command prompt, type:

set lb parameter -useSecuredPersistenceCookie Enabled-cookiePassphrase test

In the configuration utility, navigate to Traffic Management > Load Balancing > Change Load Balancing Parameters and select Use Secured Persistence Cookie and Cookie Passphrase and enter a passphrase.

If you have configured spillover on a virtual server and also configured a trap listener on the appliance, an SNMP trap is now sent to the trap listener when the virtual server experiences spillover. The trap message displays the name of the virtual server that experienced the spillover, the spillover method, the spillover threshold, and the current spillover value. If the spillover is policy based, the rule causing it appears in the Spillover Threshold field. If the virtual server is DOWN or disabled, the status message "vserver not up" appears in the trap message.

You can now set the maintenance state for your server with minimal interruption and without changing any configuration on the NetScaler appliance. In the maintenance state, the server continues to accept persistent client connections while new connections are load balanced among the active servers. On the NetScaler appliance, configure a transition out of service (TROFS)-enabled monitor and bind it to a service representing the server. Specify a trofsCode or trofsString in the monitor. Upon receipt of a matching code or string from the server in response to a monitor probe, the appliance places the service in the TROFS state. During this time, it continues to honor persistent client connections.

To avoid disrupting established sessions, you can place a service in the TROFS state by doing one of the following:

- Adding a TROFS code or string to the monitor: Configure the server to send a specific code or string in response to a monitor probe.

- Explicitly disable the service and:

- Set a delay (in seconds).

- Enable graceful shut down.

Adding a TROFS Code or String

Note: This enhancement is not applicable to GSLB services.

From release 11, if you bind only one monitor to a service, and the monitor is a TROFS-enabled monitor, it can place the service in the TROFS state on the basis of the server's response to a monitor probe. This response is compared with the value in the trofsCode parameter for an HTTP monitor or the trofsString parameter for an HTTP-ECV or TCP-ECV monitor. If the code matches, the service is placed in the TROFS state. In this state, it continues to honor the persistent connections.

If multiple monitors are bound to a service, the effective state of the service is calculated on the basis of the state of all the monitors that are bound to the service. Upon receiving a TROFS response, the state of the TROFS-enabled monitor is considered as UP for the purpose of this calculation. For more information about how a NetScaler appliance designates a service as UP, see http://docs.citrix.com/en-us/netscaler/10-5/ns-tmg-wrapper-10-con/ns-lb-wrapper-con-10/ns-lb-clienttraffic-con/ns-lb-clienttraffic-gracefulshutdown-tsk.html.

Important!

- You can bind multiple monitors to a service, but only one monitor must be TROFS-enabled.

- You can convert a TROFS-enabled monitor to a monitor that is not TROFS-enabled, but not vice versa.

A new global option, -retainDisableServer, enables you to retain a service-group member's state when a server is disabled and reenabled.

Previously, a member's state would change from DISABLED to ENABLED under the following set of conditions:

- Two applications are deployed on the same port on a virtual server.

- Two service groups with a common member are bound to this virtual server, and the common member is enabled in one group and disabled in the other.

- The server is disabled and then reenabled.

Under these conditions, disabling the server disables all the service group members, and reenabling the server enables all the members, by default, regardless of their earlier states. To bring the members back to the original states, you must manually disable those member(s) in the service group. This is a cumbersome task and prone to errors.

In earlier releases, the StoreFront monitor tried to authenticate anonymous stores. As a result, a service could be marked as DOWN and you could not launch XenApp or XenDesktop by using the URL of the load balancing virtual server.

The probe order has changed. The monitor now determines the state of the StoreFront store by successively probing the account service, the discovery document, and then the authentication service, and skips authentication for anonymous stores.

With the following new OID, you can use SNMP to learn the effective state of a virtual server.

vsvrCurEffState, 1.3.6.1.4.1.5951.4.1.3.1.1.75

With the following new OID, you can use SNMP to learn the current number of server connections per service.

svcCurSrvrConnections, 1.3.6.1.4.1.5951.4.1.2.1.1.59

In a distributed XenApp/XenDesktop deployment, StoreFront might not select an optimal datacenter when multiple equivalent resources are available from multiple datacenters. In such cases, StoreFront randomly selects a datacenter. It can send the request to any of the XenApp/XenDesktop servers in any datacenter, regardless of proximity to the client making the request.

With this enhancement, the client IP address is examined when an HTTP request arrives at the NetScaler Gateway appliance, and the real client IP address is used to create the datacenter preference list that is forwarded to StoreFront. If the NetScaler appliance is configured to insert the zone preference header, StoreFront 3.5 or later can use the information provided by the appliance to reorder the list of delivery controllers and connect to an optimal delivery controller in the same zone as the client. StoreFront selects the optimal gateway VPN virtual server for the selected datacenter zone, adds this information to the ICA file with appropriate IP addresses, and sends it to the client. Storefront then tries to launch applications hosted on the preferred datacenter's delivery controllers before trying to contact equivalent controllers in other datacenters.

For more information about this enhancement, see http://docs.citrix.com/content/dam/docs/en-us/netscaler/11/downloads/global-server-load-balancing-powered-zone-preference.pdf.

If a StoreFront application is created using the Unified Gateway Wizard, the configuration of the following session actions need to be updated.

If a configured wihome ends with "web", then update the wihome.

For example, if wihome is "/citrix/storeweb

set vpnsessionAction AC_WB_<UG_IPADDRESS> -wihome ?/citrix/storeweb?

set vpnsessionAction AC_OS_<UG_IPADDRESS> -wihome ?/citrix/storeweb?

Also, initiate the following commands before to update the "client choices" and "transparent" interception options.

set vpnsessionAction AC_WB_<UG_IPADDRESS> -clientchoices ON ?transparentinterception ON

set vpnsessionAction AC_OS_<UG_IPADDRESS> -clientchoices OFF ?transparentinterception OFF

These steps must be manually performed using the CLI or the NeScaler configuration utility.

1. Using the configuration utility, navigate to "NetScaler Gateway -> Policies -> Session -> Session Profiles and edit the relevant profile.

2. Navigate to "Published Application Tab" and update the "Web Interface Address" field ( this corresponds to the wihome setting mentioned above ).

3. Go to the "Client Experience" tab and then click to the "General" tab and update client choices as mentioned above for the corresponding actions.

4. On the "Client Experience" tab set the "plugin type" field as "Windows/ MAC OS X" for the relevant profiles as mentioned above.

SharePoint 2013 and Outlook Web Access 2013 are supported with clientless VPN access mode.

This enhancement adds support for cross-domain Kerberos constrained delegation when both the user and the service realm have a two-way shortcut trust. That is, if the user and service belong to different domains/realms, constrained delegation fails. However, if a user logs on with a user name and password, Kerberos Single Sign-On works for cross-domain access, because the NetScaler Gateway appliance does Kerberos impersonation with the user password. NetScaler Gateway currently does not otherwise support cross-domain constrained delegation.

The Unified Gateway Wizard for XenDesktop/Xenapp Application creates wrong configurations with the Storefront option. The client launches the Java plug-in instead of Win/Mac/iOS/Android plug-in.

Automatic session timeout can be enabled for ICA connections as a VPN parameter. Enabling this parameter forces active ICA connections to time out when a VPN session closes.

This enhancement adds support to disable Autoupdate for NetScaler Gateway Endpoint Analysis and VPN plug-in.

NetScaler Gateway virtual servers have improved intelligence for handling CGP traffic destined for the common CGP port, 2598, over WebSockets. This enhancement allows Receiver for HTML5 user sessions through NetScaler Gateway to support Session Reliability.

This feature extends NetScaler Gateway connectivity with access to any web application through a single URL, along with seamless single sign-on and sign-off. Single URL access can be configured for:

- Internal organizational web applications

- Software as a Service applications, including SAML based single sign-on when available

- Outlook Web Access and SharePoint as clientless applications

- Load balanced applications served through NetScaler load balancing virtual servers

- XenApp and XenDesktop published resources.

The feature can be configured and managed with the Unified Gateway wizard in the NetScaler configuration utility.

NetScaler now uses SPNEGO encapsulation on Kerberos tickets that are sent to backend web applications and servers.

The WebFront enhancement supports the transparent SSO feature when accessed from the Citrix Receiver. WebFront optimizes packet flow and improves performance for users accessing StoreFront through Gateway using Citrix Receivers. Data transferred over WAN is reduced by 41%.

The Portal Customization options have been expanded to allow end-to-end customization of the VPN user portal. Administrators can apply themes to their VPN portal design or use them as a foundation for their own customization or branding. An option to present VPN users an End User License Agreement (EULA) has also been added to the portal design. Portal themes and EULAs can be bound to a VPN virtual server or specified as global VPN parameters.

The SmartControl feature allows administrators to apply access policies for various XenApp and XenDesktop attributes through NetScaler Gateway without the need for identical policy duplication on the XenApp or XenDesktop servers.

NetScaler Gateway now has a full iOS VPN client plug-in. The plug-in is supported on iOS 7 and later releases.

The desktop client plug-ins icons can now be configured to operate independently from Native Citrix Receiver clients. Settings to manage Receiver integration with the NetScaler Gateway Plug-ins can be configured globally and within session policies.

WebFront is an alternative integration point for XenApp and XenDesktop deployments served by StoreFront. Resident on NetScaler, WebFront uses caching and packet flow optimization in the distribution of user stores. These techniques improve end user experience for Receiver for Web users and speeds up single sign-on for native Receiver users. In the NetScaler configuration utility, the WebFront feature is on the Configuration tab at System --> WebFront.

NetScaler Gateway now has a full Linux VPN client plug-in. The plug-in is supported on Ubuntu 12.04 and 14.04 distributions.

This feature allows administrators to deploy NetScaler Gateway with XenApp and XenDesktop in a striped style cluster where all nodes in the cluster serve traffic. Administrators can use existing Gateway configurations and scale seamlessly in a cluster deployment without having to restrict the VPN configuration to a single node.

Note that this feature is limited to ICA Proxy basic mode virtual servers and does not support SmartAccess.

NetScaler Gateway now has an Android client plug-in that supports full VPN capabilities. The plug-in supports Android versions 4.1 and later.

NetScaler Gateway now supports Windows 10.

NetScaler Gateway now supports the new UDP-based Framehawk virtual channel.

The NetScaler appliance was enhanced so the Portal Theme can be added using the NetScaler Gateway Wizard.

For Linux Clients, support for binding Intranet IPv6 to VPN Virtual Server is introduced.

IPv6 binding with VPN Global support is also introduced with the same.

The Dual-Hop enhancement enables next-hop requests to be distributed among several available NetScalers. The Dual-Hop feature expands the capability to load balance across any next-hop server, so that if one next-hop server is unavailable, connections can be re-established using another available server.

This enhancement supports the below configurations:

- Create a LB Vserver on DMZ NetScaler for the next-hop targets, and allow this LB to be added as a Next-Hop Server.

- Specify a next-hop server as an FQDN name so a GSLB solution could be used

Unified Gateway now supports the same cluster functionality as supported by the NetScaler Gateway. Earlier Unified Gateway did not support a cluster environment.

The default value for the VPN parameter "transparentInterception" is now set to OFF. You must set it to ON when full tunnel access is needed. For more information, see https://www.citrix.com/blogs/2015/12/11/new-vpn-default-in-netscaler-11-0.

Support for EPA verbose logging was added.

NetScaler Gateway provides an RDP enforcement feature. NetScaler administrators can disable RDP capabilities through the NetScaler Gateway configuration.

The following are configurable as part of the RDP client profile.

- Redirection of ClipBoard

- Redirection of Printers

- Redirection of Disk Drives

The VPN plugin was enhanced to acknowledge the intranet application protocol flag. ICMP blocking can be achieved by configuring separate intranet applications for UDP and TCP.

DTLS-TURN support for Unified Gateway was added. For Unified Gateway, the CS virtual server is the end-point that users connect. The VPN virtual server has to be bound as the target virtual server. This functionality enables support for secure external access using Framehawk display channel with XenApp and XenDesktop.

You can now increase the storage space of NetScaler Insight Center to 512 GB.

The NetScaler Insight Center configuration utility now displays the progress of the upgrade process.

Multi-Hop support for NetScaler Insight Center enables Insight Center to detect which Citrix appliances a connection passes through (CloudBridge, NetScaler, NetScaler Gateway), and in which order, for improved reporting.

You can now configure a DNS server when you set up NetScaler Insight Center. Configuring a DNS server helps resolve the host name of a server into its IP address.

For example, while creating an email server, you now have an option to specify the server name of the server rather than the IP address.

You can now configure NetScaler Insight Center to display the reports in your local time or GMT time.

You can now save the Web Insight reports or HDX Insight reports in PDF, JPEG, PNG , or CSV format on your local computer. You can also schedule the export of the reports to specified email addresses at various intervals.

For more information, see http://docs.citrix.com/en-us/netscaler-insight/11-0/viewing-reports/ni-export-report-con.html.

After an ICA connection is established between a client and a NetScaler Gateway appliance, errors or old receiver or server versions, can prevent the appliance from exporting the AppFlow records to NetScaler Insight Center.

In such cases, the NetScaler Insight Center dashboard now displays the reasons for which the NetScaler appliance does not export the AppFlow records.

You can configure NetScaler Insight Center to display the geo maps for a particular geographical location or LAN by specifying the private IP range (start and end IP address) for the location.

You can now improve the processing power of and increase storage space in your NetScaler Insight Center deployment by adding agents, connectors, and databases. An agent processes HTTP traffic and sends the data to the connectors that distribute this data across databases. You can add multiple agents, connectors, and databases to scale your deployment. In this deployment, you can also the decide the number of resources you have to allocate and determine the elements you need in the database architecture, on the basis of the number of HTTP requests per second, number of ICA sessions, and number of active WAN connections.

The WAN Insight feature of NetScaler Insight Center gives CloudBridge administrators an easy way to monitor the accelerated and unaccelarted WAN traffic that flows through CloudBridge datacenter and CloudBridge branch appliances, and it provides end-to-end visibility that includes client-specific data, application-specific data, and branch- specific data. With the ability to identify and monitor all the applications, clients, and branches on the network, you can effectively deal with the issues that degrade performance.

The HDX Insight reports now support hop diagrams, which provide complete details about the client, NetScaler ADC, and server in an active session.

To display the hop diagram, on the dashboard tab, navigate to HDX Insight > Users >, click on a user name and, in the Current Application Sessions table, click on the session diagram icon.

NetScaler Insight Center now supports monitoring NetScaler appliances deployed in LAN user mode. The dashboard now displays the following user access types, depending on the NetScaler deployment:

- Remote user: User connected to XenApp or XenDesktop server through a NetScaler Gateway.

- Transparent mode user: User connected to XenApp or XenDesktop server directly, with no intervening virtual server.

- LAN user: Internal user connected to XenApp or XenDesktop server directly, without configuring the routing rules on a NetScaler ADC.

You can now identify the root cause of a terminated ICA session by viewing the session termination reason on the HDX Insight node. Along with the termination reason, it also displays the session TCP metrics such as ICA RTT and WAN Latency.

Web and web service applications that are exposed to the Internet have become increasingly vulnerable to attacks. To protect applications from attack, you require visibility into the nature and extent of past, present, and impending threats, real-time actionable data on attacks, and recommendations on countermeasures. Security Insight provides a single-pane solution to help you assess your application security status and take corrective actions to secure your applications.

Security insight is included in NetScaler Insight Center, and it periodically generates reports based on your Application Firewall and NetScaler system security configurations. The reports include the following information for each application:

-Threat index. A single-digit rating system that indicates the criticality of attacks on the application, regardless of whether or not the application is protected by a NetScaler appliance. The more critical the attacks on an application, the higher the threat index for that application.

-Safety index. A single-digit rating system that indicates how securely you have configured the NetScaler devices to protect applications from external threats and vulnerabilities. The lower the security risks for an application, the higher the safety index.

-Actionable Information. Information that you need to lower the threat index and increase the safety index, which significantly improves application security. For example, you can review information about violations, existing and missing security configurations in Application Firewall and NetScaler security features, the rate at which the applications are being attacked, and so on.

The NetScaler Insight Center now displays the GET or POST requests that are sent by the client to a domain. To view the GET or POST requests, navigate to Domains > URLs > Clients > Http Request Method, or to Domains > URLs > Http Request Method > Clients.

Gateway Insight provides visibility into the failures encountered by all users, regardless of the access mode, at the time of logging on to NetScaler Gateway. You can view a list of all available users, number of active users, number of active sessions, and bytes and licenses used by all users at any given time. You can view the end-point analysis (EPA), authentication, single sign-on (SSO), and application launch failures for a user. You can also view the details of active and terminated sessions for a user.

Gateway Insight also provides visibility into the reasons for application launch failure for virtual applications. This enhances your ability to troubleshoot any kind of logon or application launch failure issues. You can view the number of applications launched, number of total and active sessions, and the number of total bytes and bandwidth consumed by the applications. You can view details of users, sessions, bandwidth, and launch errors for an application.

You can view the number of gateways, number of active sessions, and the total bytes and bandwidth used by all gateways associated with a NetScaler Gateway appliance at any given time. You can view the EPA, authentication, SSO, and application-launch failures for a gateway. You can also view the details of all users associated with a gateway, and their logon activity.

To enable Gateway Insight for your NetScaler Gateway appliance, you must first add the NetScaler Gateway appliance to NetScaler Insight Center. You must then enable AppFlow for the virtual server representing the VPN application in NetScaler Insight Center.

Navigation: Dashboard > Gateway Insight

The following thin clients now support HDX Insight:

-WYSE Windows based thin clients

-WYSE Linux based thin clients

-WYSE ThinOS based thin clients

-10Zig Ubuntu based thin clients

NetScaler SDX appliance now supports SNMP MIB configuration. You can configure SNMP MIB from Management Service by navigating to Configuration > System > SNMP > Settings > Configure SNMP MIB

You can now partially allocate licenses as required for your deployment. For example, if your license file contains ten licenses, but your current requirement is for only six licenses, you can allocate six licenses now, and allocate additional licenses later. You cannot allocate more than the total number of licenses present in your license file.

Management service now provides support for SNMP v3 traps in addition to the already existing support for SNMP v2 traps. SNMP v3 provides better administration and security capabilities through better encryption, authentication and data integrity mechanisms.

NetScaler SDX Appliance now displays the reboot progress. This helps in keeping the user informed about the various stages of the appliance reboot.

In the Management Service, the user interface for licensing the NetScaler SDX appliances is now identical to the user interface for licensing the NetScaler MPX and NetScaler VPX appliances.

Management service now provides support for XenServer 6.5.

You can use the Setup Wizard to complete all the first time configurations in a single flow. You can use the wizard to assign various management network IP addresses, configure system settings, change the default admin password, manage and update licenses.

You can also use this wizard to modify the network configuration details that you provided for the NetScaler SDX appliance during initial configuration.

To access the wizard, navigate to Configuration > System, under Setup Appliance, click Setup Wizard.

Options to disable and enable TLSv1, TLSv1.1, and TLSv1.2 has been added in the Management Service. To enable or disable TLS, navigate to Configuration > System. In the System Settings group, click on Change SSL Settings link.

The Initiate Virtual-NMI generates a core dump of a VPX instance. Initiating a virtual NMI is useful when your NetScaler instance has stopped responding. To generate a virtual NMI, click on Configuration > Diagnostics. Click Initiate NMI under Non-Maskable Interrupt.

If you create channels on SDX and use these channels in VPXs and then take a backup of the appliance to restore either the complete appliance or selected instances, then channels are not restored and instances may fail.

The default timezone when management service creates NetScaler instances is the NTP timezone. When this default timezone is modified using the management service, then the update is synchronized across the NetScaler instances

When you configure an LDAP server and provide the IP address of the LDAP server, the management service automatically fetches the attributes like Server Logon Name Attribute, Search Filter, Group Attribute, Sub Attribute Name. This helps in reducing the error during filling these details for LDAP configuration.

Syslog Viewer helps you in searching through the syslog messages based on various filters. You can narrow your search based on module like API, CLI, CONFIG, EVENT etc. You can further choose the type of message that you want to search through, like, ALERT, CRITICAL etc. Syslog Viewer also provides the option to search through regular expression or based on case sensitive text

When you use the NetScaler provisioning wizard, the option to upload the XVA file has been added to the wizard. To use the XVA file to create a NetScaler instance, you need to first upload the XVA file.

NetScaler SDX supports cluster with three tuple notation.

You can use the clean install feature to downgrade the software version of a NetScaler SDX appliance without losing the IP addresses or passwords. Clean install is different than factory reset in the manner that you can choose the SDX version to which you want to downgrade the appliance.

To perform a clean install, navigate to Configuration > System > System Administration. In the System Administration Group, click Appliance Reset and follow the prompts.

You can now specify an IP address as a static route when provisioning a NetScaler instance. The instance then uses this address, instead of the default route, to connect to the Management Service.

Using the Management Service interface, you can now disable the nsrecover login account. To disable the nsrecover login account, navigate to "Configuration > System > Configure System Settings" and clear the "Enable nsrecover Login" check box.

The Management Service now provides an option to encrypt the backup files.

You can select SSL cipher suites from a list of SSL ciphers supported by SDX appliances, and bind any combination of the SSL ciphers to access the Management Service securely through HTTPS

The NetScaler appliance supports IPv6 dynamic routing protocols for VXLANs. You can configure various IPv6 Dynamic Routing protocols (for example, OSPFv3, RIPng, BGP) on VXLANs from the VTYSH command line. An option IPv6 Dynamic Routing Protocol has been added to VXLAN command set for enabling or disabling IPv6 dynamic routing protocols on a VXLAN. After enabling IPv6 dynamic routing protocols on a VXLAN, processes related to the IPv6 dynamic routing protocols are required to be started on the VXLAN by using the VTYSH command line.

The NetScaler appliance does not block traffic that matches an ACL rule if the traffic is destined to the appliance's NSIP address, or one of its SNIP addresses, and a port in the 3008-3011 range.

This behavior is now specified by the default setting of the new Implicit ACL Allow (implicitACLAllow) parameter (of the L3 param command). You can disable this parameter if you want to block traffic to ports in the 3008-3011 range. An appliance in a high availability configuration makes an exception for its partner (primary or secondary) node. It does not block traffic from that node.

To disable or enable this parameter by using the command line interface

At the command prompt, type:

> set l3param -implicitACLAllow [ENABLED|DISABLED]

Note: The parameter implicitACLAllow is enabled by default.

Example

> set l3param -implicitACLAllow DISABLED

Done

In a static ARP entry, you can specify the VLAN through which the destination device is accessible. This feature is useful when the interface specified in the static ARP entry is part of multiple tagged VLANs and the destination is accessible through one of the VLANs. The NetScaler appliance includes the specified VLAN ID in the outgoing packets matching the static ARP entry. If you don't specify a VLAN ID in an ARP entry, and the specified interface is part of multiple tagged VLANs, the appliance assigns the interface's native VLAN to the ARP entry.

For example, say NetScaler interface 1/2 is part of native VLAN 2 and of tagged VLANs 3 and 4, and you add a static ARP entry for network device A, which is part of VLAN 3 and is accessible through interface 1/2. You must specify VLAN 3 in the ARP entry for network device A. The NetScaler appliance then includes tagged VLAN 3 in all the packets destined to network device A, and sends them from interface 1/2.

If you don't specify a VLAN ID, the NetScaler appliance assigns native VLAN 2 for the ARP entry. Packets destined to device A are dropped in the network path, because they do not specify tagged VLAN 3, which is the VLAN for device A.

To ensure that a backup VIP address takes over as the master VIP before the node of the current master VIP address goes down completely, you can configure a node to change the priority of a VIP address on the basis of the states of the interfaces on that node. For example, the node reduces the priority of a VIP address when the state of an interface changes to DOWN, and increases the priority when the state of the interface changes to UP. This feature is configured on each node. It applies to the specified VIP addresses on the node.

To configure this feature on a node, you set the Reduced Priority (trackifNumPriority) parameter, and then associate the interfaces whose state is to be tracked for changing the priority of the VIP address. When any associated interface's state changes to DOWN or UP, the node reduces or increases the priority of the VIP address by the configured Reduced Priority (trackifNumPriority) value.

For a configured GRE IP tunnel, the NetScaler appliance encapsulates the entire Layer 2 packet, including the Ethernet header and the VLAN header (dot1q VLAN tag). IP GRE tunnels between NetScaler appliances and some 3rd party devices might not be stable, because these 3rd party devices are not programmed to process some or the Layer 2 packet headers.

To configure a stable IP GRE tunnel between a NetScaler appliance and a 3rd party device, you can use a new parameter with the GRE IP tunnel command set. You can set the GRE payload parameter to do one of the following before the packet is sent through the GRE tunnel:

- Carry the Ethernet header but drop the VLAN header

- Drop the Ethernet header as well as the VLAN header

- Carry the Ethernet header as well the VLAN header

The NetScaler appliance supports sending static IPv6 routes through a VXLAN. You can enable the NetScaler appliance to send an IPv6 route through either a VXLAN or a VLAN. A VXLAN parameter is added to the static IPv6 route command set.

NetScaler VPX appliances now support receiving and transmitting jumbo frames containing up to 9216 bytes of IP data. Jumbo frames can transfer large files more efficiently than is possible with the standard IP MTU size of 1500 bytes.

A NetScaler appliance can use jumbo frames in the following deployment scenarios:

- Jumbo to Jumbo. The appliance receives data as jumbo frames and sends it as jumbo frames.

- Non-Jumbo to Jumbo. The appliance receives data as regular frames and sends it as jumbo frames.

- Jumbo to Non-Jumbo. The appliance receives data as jumbo frames and sends it as regular frames.

Jumbo Frames support is available on NetScaler VPX appliances running on the following virtualization platforms:

- VMware ESX (Note that NetScaler VPX appliances running on VMware ESX support receiving and transmitting jumbo frames containing up to only 9000 bytes of IP data.)

- Linux-KVM

For configuring Jumbo Frames on a NetScaler VPX appliance, you must:

- Set the MTU of the interface or channel of the VPX appliance to a value in the range 1501-9216. Use the NetScaler command line interface or the configuration utility of the VPX appliance to set the MTU size.

- Set the same MTU size on the corresponding physical interfaces of the virtualization host by using its management applications.

For ensuring the integrity, data origin authentication, and data confidentiality of OSPFv3 packets, OSPFv3 authentication must be configured on OSPFv3 peers.

The NetScaler appliance supports OSPFv3 authentication and is partially compliant with RFC 4552. OSPFv3 authentication is based on the two IPSec protocols: Authentication Header (AH) and Encapsulating Security Payload (ESP). The NetScaler supports only the AH protocol for OSPFv3 authentication.

OSPFv3 authentication use manually defined IPSec Security Associations (SAs) between the OSPFv3 peers and does not rely on IKE protocol for forming dynamic SAs. Manual SAs define the security parameter Index (SPI) values, algorithms, and keys to be used between the peers. Manual SAs require no negotiation between the peers; therefore, same SA must be defined on both the peers.

You can configure OSPFv3 authentication on a VLAN or for an OSPFv3 area. When you configure for a VLAN, the settings are applied to all the interfaces that are member of the VLAN. When you configure OSPFv3 authentication for an OSPF area, the settings are applied to all the VLANs in that area. The settings are in turn applied to all the interfaces that are members of these VLANs. These settings do not apply to member VLANs on which you have configured OSPFv3 authentication directly.

In an active-active deployment, all NetScaler nodes use the Virtual Router Redundancy Protocol (VRRP) to advertise their master VIP addresses and the corresponding priorities in VRRP advertisement packets (hello messages) at regular intervals.

VRRP uses the following communication intervals:

* Hello Interval-Interval between successive VRRP hello messages that a node sends, for all of its active (master) VIP addresses, to the other nodes of the VRRP deployment. For a VIP address, nodes on which the VIP address is in the inactive state use the hello messages as verification that the master VIP address is still UP.

* Dead Interval-Time after which a node of a backup VIP address considers the state of the master VIP address to be DOWN if VRRP hello messages are not received from the node that has the master VIP address. After the dead interval, the backup VIP address takes over and becomes the master VIP address.

You can change these intervals to a desired value on each node. They apply to all VIP addresses on that node.

A redundant interface set is a set of interfaces in which one interface is active and the others are on standby. If the active interface fails, one of the standby interfaces takes over and becomes active.

Following are the main benefits of using redundant interface sets:

- The back-up links between the NetScaler appliance and a peer device ensure connection reliability.

- Unlike link redundancy using LACP, no configuration is required on the peer device for a redundant interface set. To the peer device, a redundant interface set appears as individual interfaces, not as a set or collection.

- In a high availability (HA) configuration, redundant interface sets can minimize the number the HA failovers.

A redundant interface set is specified in LR/X notation, where X can range from 1 to 4. For example, LR/1.

As a part of BGP loop prevention functionality, if a router receives a BGP packet containing the router's Autonomous System Number (ASN) in the Autonomous Systems (AS) path, the router drops the packet. The assumption is that the packet originated from the router and has reached the place from where it originated.

If an enterprise has several sites with a same ASN, BGP loop prevention causes the sites with an identical ASN to not get linked by another ASN. Routing updates (BGP packets) are dropped when another site receives them.

To solve this issue, BGP AS-Override functionality has been added to the ZebOS BGP routing module of the NetScaler.

With AS-Override enabled for a peer device, when the NetScaler appliance receives a BGP packet for forwarding to the peer, and the ASN of the packet matches that of the peer, the appliance replaces the ASN of the BGP packet with its own ASN number before forwarding the packet.

A new wildcard mask parameter for extended ACLs and ACL6s can be used with the source MAC address parameter to define a range of MAC addresses to match against the source MAC address of incoming packets.

MAC Address Wildcard Mask for PBRs

A new wildcard mask parameter for PBRs and PBR6s can be used with the source MAC address parameter to define a range of MAC addresses to match against the source MAC address of outgoing packets.

In earlier releases, Layer 2 information (for example, destination MAC address, source VLAN, and Interface ID) about packets related to forwarding sessions were ignored during a PBR lookup. In other words, any packet related to a forwarding session was not considered for matching against a PBR having Layer 2 parameters as its condition.

Now, layer 2 information about a packet related to a forwarding session is matched against layer 2 parameters in the configured PBRs.

This feature is useful in a scenario where packets related to a forwarding session must be processed by another device before being sent to their destination.

Following are the benefits of this support:

- Instead of defining new PBRs that are based on Layer 3 parameters, you can use existing PBRs based on Layer 2 parameters for sending the packets related to forwarding sessions to the desired next hop device.

- In a deployment that includes NetScaler appliances and optimization devices (for example, Citrix ByteMobile and Citrix CloudBridge appliances), PBRs based on Layer 2 parameters can be very handy compared to other, complex configuration for identifying the forwarding session related packets for PBR processing.

- Identifying forwarding session related Ingress packets for sending them to the optimization device.

- Identifying egress packets, which also matched a forwarding session rule, from the optimization device for sending the packets to the desired next hop device.

The NetScaler appliance can now log header information of HTTP requests related to an LSN configuration. The following header information of an HTTP request packet can be logged:

- URL that the HTTP request is destined to.

- HTTP Method specified in the HTTP request.

- HTTP version used in the HTTP request.

- IP address of the subscriber that sent the HTTP request.

An HTTP header log profile is a collection of HTTP header attributes (for example, URL and HTTP method) that can be enabled or disabled for logging. The HTTP header log profile is then bound to an LSN group. The NetScaler appliance then logs HTTP header attributes, which are enabled in the bound HTTP header log profile for logging, of any HTTP requests related to the LSN group.

An HTTP header log profile can be bound to multiple LSN groups but an LSN group can have only one HTTP header log profile.

The NetScaler appliance, for INAT and RNAT rules, now supports using client port as the source port for server side connections. A parameter Use Proxy Port has been added to the INAT and RNAT command set. When Use Proxy Port is disabled for an INAT rule or a RNAT rule, the NetScaler appliance retains the source port of the client's request for the server side connection. When the option is enabled (default), the NetScaler appliance uses a random port as the source port for the server side connection.  

You must disable this parameter for proper functioning of certain protocols that require a specific source port in the request packet.

By default, for configurations with USIP option disabled or with USIP and use proxy port options enabled, the NetScaler appliance communicates to the servers from a random source port (greater than 1024).

The NetScaler supports using a source port from a specified port range for communicating to the servers. One of the use case of this feature is for servers that are configured to identify received traffic belonging to a specific set on the basis of source port for logging and monitoring purposes. For example, identifying internal and external traffic for logging purpose.

For more information, see http://docs.citrix.com/en-us/netscaler/11/traffic-management/load-balancing/load-balancing-manage-clienttraffic/use-specified-sourceport.html.

You can force a VIP address to always stay in backup state in a VRRP deployment. This operation is helpful in maintenance or testing of the deployment.

When a VIP address is forced to stay in backup state, it does not participate in VRRP state transitions. Also, it cannot become master even if all other nodes go down.

To force a VIP address to stay in backup state, you set the priority of the associated VMAC address to zero. To ensure that none of the VIP addresses of a node handle traffic during a maintenance process on the node, set all the priorities to zero.

For more information, see http://docs.citrix.com/en-us/netscaler/11/networking/interfaces/configuring-active-active-mode.html.

By default, a backup VIP address preempts the master VIP address immediately after its priority becomes higher than that of the master VIP. When configuring a backup VIP address, you can specify an amount of time by which to delay the preemption. Preemption delay time is a per-node setting for each backup VIP address.

The preemption delay setting for a backup VIP does not apply in the following conditions:

* The node of the master VIP goes down. In this case, the backup VIP takes over as the master VIP after the dead interval set on the backup VIP's node.

* The priority of the master VIP is set to zero. The backup VIP takes over as the master VIP after the dead interval set on the backup VIP's node.

For more information, see http://docs.citrix.com/en-us/netscaler/11/networking/interfaces/configuring-active-active-mode.html.

Connection failover helps prevent disruption of access to applications deployed in a distributed environment. The NetScaler appliance now supports stateful connection failover for connections related to RNAT rules in a NetScaler High Availability (HA) setup.

In an HA setup, connection failover (or connection mirroring) refers to the process of keeping an established TCP or UDP connection active when a failover occurs. The primary appliance sends messages to the secondary appliance to synchronize current information about the RNAT connections. The secondary appliance uses this connection information only in the event of a failover. When a failover occurs, the new primary NetScaler appliance has information about the connections established before the failover and hence continues to serve those connections even after the failover. From the client's perspective this failover is transparent. During the transition period, the client and server may experience a brief disruption and retransmissions.

Connection failover can be enabled per RNAT rule. For enabling connection failover on an RNAT rule, you enable the connFailover (Connection Failover) parameter of that specific RNAT rule by using either NetScaler command line or configuration utility. Also, you must disable the tcpproxy (TCP Proxy) parameter globally for all RNAT rules in order for connection failover to work properly for TCP connections.

The front end optimization feature now supports the conversion of GIF, JPEG, and PNG images to WEBP format as part of the image optimization functionality.

You can now monitor and display the statistics of the media traffic going through the NetScaler appliance.

The front end optimization feature now supports the conversion of GIF, JPEG, TIFF, and PNG images to JPEG-XR format as part of the image optimization functionality.

The MPX 25100T and MPX 25160T platforms are now supported in this release. For more information about these platforms, see http://docs.citrix.com/en-us/netscaler/11/netscaler-hardware-installation/netscaler-hardware-platforms/mpx-25100t-25160t.html.

In the Amazon AWS cloud, a NetScaler AMI can now be launched as an M4 EC2 instance. Some of the features of M4 EC2 instance type are:

* 2.4 GHz Intel Xeon E5-2676 v3 (Haswell) processors

* EBS-optimized by default at no additional cost

* Balance of compute, memory, and network resources

Note: A NetScaler AMI running as an M4 EC2 instance supports all M4 EC2 features except the enhanced networking features. For more information about M4 EC2 instance types, see https://aws.amazon.com/ec2/instance-types/.

The NetScaler appliance now supports policy extensions, which you can use to add customized functions to default syntax policy expressions. An extension function can accept text, double, Boolean or number values as input, perform a computation, and produce a text, double, Boolean or number result.

Transaction scope variables are added to variables feature. You can now use transaction scope variables to specify separate instances with values for each transaction processed by the NetScaler appliance. Transaction variables are useful for passing information from one phase of the transaction to another. For example, you can use a transaction variable to pass information about the request onto the response processing.

The NetScaler software has been enhanced to automatically detect the format of the certificate-key pair. To do so, the format of the certificate and key file should be the same. If you specify the format in the inform parameter, it is ignored by the software. Supported formats are PEM, DER, and PFX.

The NetScaler appliance now supports the following ECDHE ciphers at the back end:

- TLS1-ECDHE-RSA-RC4-SHA

- TLS1-ECDHE-RSA-DES-CBC3-SHA

- TLS1-ECDHE-RSA-AES128-SHA

- TLS1-ECDHE-RSA-AES256-SHA

Note: This feature is available only for NetScaler MPX platforms.

With this release, the default certificate on a NetScaler appliance is 2048-bits. In earlier builds, the default certificate was 512-bits or 1024-bits. After upgrading to release 11.0, you must delete all your old certificate-key pairs starting with "ns-", and then restart the appliance to automatically generate a 2048-bit default certificate.

If you configure a common name on an SSL service or service group for server certificate authentication, the subject alternative name (SAN), if specified, is matched in addition to the common name. Therefore, if the common name does not match, the name that you specify is compared to the values in the SAN field in the certificate. If it matches one of those values, the handshake is successful. Note that in the SAN field, only DNS names are matched.

The NetScaler VPX appliance now supports TLS protocol versions 1.1 and 1.2 on the front end. On an SDX appliance, TLSv1.1/1.2 are supported on the front end even if an SSL chip is not assigned to the VPX instance.

The following SNMP OIDs have been added to the display the SSL transactions per second:

NS-ROOT-MIB::sslTotTransactionsRate.0 = Gauge32: 0

NS-ROOT-MIB::sslTotSSLv2TransactionsRate.0 = Gauge32: 0

NS-ROOT-MIB::sslTotSSLv3TransactionsRate.0 = Gauge32: 0

NS-ROOT-MIB::sslTotTLSv1TransactionsRate.0 = Gauge32: 0

EDH, DHE, ADH, EXP, and ECDHE ciphers are now supported on a DTLS virtual server.

The NetScaler appliance now supports the TLS_FALLBACK_SCSV signaling cipher suite value. The presence of this SCSV extension in the Client Hello indicates that the client is retrying to connect to the server by using a lower SSL version, after its previous attempt to communicate with a higher version failed. Therefore, if the server finds this extension in Client Hello and also finds that the client is proposing a version that is lower than the maximum version supported by the server, it is a likely indication of a "man in the middle attack." The server drops these handshakes.

For more information, see http://docs.citrix.com/en-us/netscaler/11/traffic-management/ssl/customize-ssl-config/config-protocol-settings.html.

DH key generation is optimized on a VPX appliance by adding a new parameter dhKeyExpSizeLimit. You can set this parameter on an SSL virtual server or on an SSL profile and bind the profile to the SSL virtual server. The key generation is optimized as defined by NIST in http://csrc.nist.gov/publications/nistpubs/800-56A/SP800-56A_Revision1_Mar08-2007.pdf. Additionally, the minimum DH count is set to zero. As a result, you can now generate a DH key for each transaction as opposed to a minimum of 500 transactions earlier. This helps to achieve perfect forward secrecy (PFS).

The NetScaler appliance now supports SNI with a SAN extension certificate. During handshake initiation, the host name provided by the client is first compared to the common name and then to the subject alternative name. If the name matches, the corresponding certificate is presented to the client.

The show ciphersuite command now displays the IETF standard hexadecimal code of the cipher. It is helpful in debugging, because a hex code is unique to a cipher but the cipher name might differ on the NetScaler appliance, OpenSSL, and Wireshark.

At the NetScaler command line, type:

show ciphersuite

In the configuration utility, navigate to Traffic Management > SSL > Cipher Groups.

If user-defined ciphers or cipher groups are not bound to an SSL virtual server, the DEFAULT cipher group is used for cipher selection at the front end and the ALL cipher group is used for cipher selection at the back end. In this release, the predefined cipher suites, such as DEFAULT and ALL, are modified to give strong ciphers a higher priority. For example, earlier RC4-MD5 was given a higher priority but it is deprioritized in the new list because it is a weak cipher.

The NetScaler MPX appliance now supports TLS protocol versions 1.1 and 1.2 on the backend. MPX-FIPS appliances running firmware version 2.2 also support TLSv1.1/1.2 on the backend. On an SDX appliance, TLSv1.1/1.2 is supported on the backend only if an SSL chip is assigned to the VPX instance.

You can configure the SSL virtual server to accept only client certificates that are signed by a CA certificate bound to the virtual server. To do so, enable the ClientAuthUseBoundCAChain setting in the SSL profile bound to the virtual server.

For more information, see http://docs.citrix.com/en-us/netscaler/11/traffic-management/ssl/config-ssloffloading/ssl-profiles.html.

All NetScaler MPX, SDX, and VPX appliances except the MPX 9700/10500/12500/15500 appliances now support the Thales nShield(R) Connect external Hardware Security Module (HSM). With a Thales HSM, the keys are securely stored as application key tokens on a remote file server and can be reconstituted only inside the Thales HSM. Thales HSMs comply with FIPS 140-2 Level 3 specifications.

Thales integration with the ADC is supported for TLS versions 1.0, 1.1, and 1.2.

For more information about support for Thales nShield(R) HSM, see http://docs.citrix.com/en-us/netscaler/11/traffic-management/ssl/support_for_thales.html.

The SSL infrastructure on the NetScaler appliance is continually updated to address the ever growing requirements for security and performance. Vulnerabilities in SSLv3 and RC4 implementation have emphasized the need to use the latest ciphers and protocols to negotiate the security settings for a network connection. Implementing any changes to the configuration, such as disabling SSLv3, across thousands of SSL end points is a cumbersome process. Therefore, settings that were part of the SSL end points configuration have been moved to the SSL profile, along with the default ciphers. To implement any change in the configuration, including cipher support, you need only modify the profile. If the profile is enabled, the change is immediately reflected in all the end points that the profile is bound to.

Important: After the upgrade, if you enable the profile, you cannot reverse the changes. That is, the profile cannot be disabled.

Some operations - for example, updating a certificate to replace a potentially exposed certificate, using a stronger key (2048-bit instead of 1024-bit), adding/removing a certificate from a certificate chain, or changing any of the SSL parameters - should clean the SSL sessions gracefully instead of abruptly terminating existing sessions. With this enhancement, existing connections continue to use the current settings but all new connections use the new certificate or settings. However, connections that are in the middle of a handshake or sessions that are renegotiating are terminated, and session reuse is not allowed. To clear the sessions immediately after a configuration change, you must disable and reenable each entity.

Because TLS 1.1 and 1.2 are becoming the primary security protocols, the transaction and session statistics for these protocols are now included in the SSL statistics.

If you downgrade the software on your NetScaler appliance that does not have a license to release 9.3 build 61.66 or earlier, some commands related to the default server certificate might not be saved in the running configuration. As a result, after restarting, secure access (HTTPS) to the appliance fails.

Knowing the percentage utilization of all the SSL chips in an appliance over a period of time helps in capacity planning. The counter increments every 7 seconds and therefore provides real-time data, which can help you predict when an appliance is likely to reach capacity.

Note: This feature is available on only the MPX appliances that use N3 chips, which include MPX 11515/11520/11530/11540/11542 and MPX 220140/22060/22080/22100/22120/24100/24150 appliances.

Some models of MPX 14020/14030/14040/14060/14080/14100 and MPX 25100/25160/25200, which use N3 chips, also support this feature.

You no longer need a license on your VPX instance to generate a 2048-bit default certificate. After upgrading your VPX instance to release 11.0, if you want to replace the old internal default 512-bit certificate, delete all your old certificate-key pairs that have "ns-" as the first three characters, and then restart the instance to automatically generate a 2048-bit default certificate.

Knowing the percentage utilization of all the SSL chips in an appliance over a period of time helps in capacity planning. The counter increments every 7 seconds and therefore provides real-time data, which can help you predict when an appliance is likely to reach capacity.

Note: This feature is available on only the MPX appliances that use N3 chips, which include MPX 11515/11520/11530/11540/11542 and MPX 220140/22060/22080/22100/22120/24100/24150 appliances.

Some models of MPX 14020/14030/14040/14060/14080/14100 and MPX 25100/25160/25200, which use N3 chips, also support this feature.

The NetScaler appliance now supports the following "signature algorithms" extensions in the back end client hello message:

- RSA-MD5

- RSA-SHA1

- RSA-SHA256

The NetScaler VPX appliance now supports AES-GCM/SHA2 ciphers on the front end.

Two counters have been added to the output of the "stat ssl vserver" command as follows:

1. ssl_ctx_tot_clientAuth_success-Tracks the number of successful client authentications for each SSL virtual server.

2. ssl_ctx_tot_clientAuth_failures-Tracks the number of failed client authentications for each SSL virtual server.

The NetScaler VPX appliance now supports TLS protocol versions 1.1 and 1.2 on the back end.

The TCP profiles on a NetScaler appliance now support forward acknowledgement (FACK). FACK avoids TCP congestion by explicitly measuring the total number of data bytes outstanding in the network, and helping the sender (either a NetScaler ADC or a client) control the amount of data injected into the network during retransmission timeouts.

Call home support for NetScaler VPX models

Call home support has been added to NetScaler VPX models 1000 and higher.

The NetScaler appliance fails intermittently when trace is started in 'RX' mode.

In NetScaler release 11, the NTP version has been updated from 4.2.6p3 to 4.2.8p2.

If you upgrade your NetScaler appliance from any earlier release to release 11, the NTP configuration is automatically upgraded with additional security policies. For more information about configuring an NTP server, see http://docs.citrix.com/en-us/netscaler/11/system/basic-operations/configuring-clock-sychronization.html.

The NetScaler introduces a new role called sysadmin. A sysadmin is lower than a superuser is terms of access allowed on the appliance. A sysadmin user can perform all NetScaler operations with the following exceptions: no access to the NetScaler shell, cannot perform user configurations, cannot perform partition configurations, and some other configurations as stated in the sysadmin command policy.

If your NetScaler appliance has Internet connectivity, you can now directly upload the newly generated collector archive to the Citrix technical support server from the appliance.

The NetScaler Web Logging (NSWL) client logs a hyphen (-) instead of a user name when %u is specified in the log format.

You can now specify the minimum number of reuse pool connections to be opened from the NetScaler appliance to a particular server. This setting helps in optimal memory utilization and reduces the number of idle connections to the server.

The NetScaler appliance supports HTTP/2 connections with clients supporting HTTP/2 protocol.

The script used to upload collector archives to Citrix servers is now packaged as part of the official NetScaler build (collector_upload.pl). However, using this script directly is not recommended. Instead, use the -upload option in showtechsupport utility to upload the archives.

Support for milliseconds, microseconds, and nanoseconds in Time Format Definition table

You can now configure NetScaler web logging clients to capture transaction times in milliseconds, microseconds, and nanoseconds for logging on the NetScaler appliance.

During the execution of the "nstrace.sh" script (from shell) or the "start nstrace" command (from CLI), when the trace file is rolled over, some packets might not be available in the trace. The number of packets that will be dropped from the trace is directly proportional to the traffic rate.

You can now set the maximum congestion window size for a TCP profile on the NetScaler appliance.

The NetScaler appliance generates SNMP clear alarm traps for successful cases of haVersionMismatch, haNoHeartbeats, haBadSecState, haSyncFailure, and haPropFailure error events in an HA configuration.

The tech support bundle that is generated for a NetScaler MPX appliance that has a LOM port, generates a list of LOM sensors and stores this list in the support bundle in the "shell/ipmitool_sensor_list.out" file.

When configuring an auditlog action, you can specify the domain name of a syslog or nslog server instead of its IP address. Then, if the server's IP address changes, you do not have to change it on the NetScaler appliance.

You can now use a remotely saved backup to restore a NetScaler appliance through the "add system backup <filename>", that adds the metadata to the remote backup package, so that the restore operation can successfully use the backup package.

A client can now establish an MPTCP connection with NetScaler appliance even if the client's and the NetScaler appliance's MPTCP versions does not match. If the MPTCP version of the client is higher than the one supported on the appliance, the client falls back to a lower or equal version. If the appliance supports that version, the MPTCP session continues. Otherwise, the appliance falls back to a normal TCP session.

You no longer have to configure internet connectivity on the NetScaler appliance in order to use a hardware serial number or license activation code to allocate a NetScaler license. Instead, you can use a proxy server.

On the NetScaler GUI, navigate to Configuration > System > Licenses > Manage Licenses > Add a New License, select the Connect through Proxy Server check box, and specify the IP address and port of your proxy server.

You can now enable auto-bootstrapping on a NetScaler VPX or NetScaler 1000v instance running on Hyper-V, by attaching a DVD ROM with an appropriate ISO file to the instance before booting it up.

Service chaining is determining the set of services through which the outbound traffic from a subscriber must pass before going to the Internet. Multiple services, such as antivirus services, parental control services, firewalls, and web filter, are running in a Telco network. Different subscribers have different plans and each plan has specific services associated with it. The decision to direct a subscriber's request to a service is based on the subscriber information. Instead of sending all the traffic to all the services, the NetScaler appliance intelligently routes all requests from a subscriber to a specific set of services on the basis of the policy defined for that subscriber. The appliance receives the subscriber information from the PCRF over a Gx interface.

For more information about subscriber-aware service chaining, see http://docs.citrix.com/en-us/netscaler/11/solutions/netscaler-support-for-telecom-service-providers/lsn-telco-subscriber-management.html.

The NetScaler appliance can now dynamically receive the subscriber information through a RADIUS accounting message. It receives the subscriber IP address and MSISDN and uses this information to retrieve the subscriber rules from the PCRF server.

For more information about RADIUS Accounting Message, see http://docs.citrix.com/en-us/netscaler/11/solutions/netscaler-support-for-telecom-service-providers/lsn-telco-subscriber-management.html.

The NetScaler appliance can now dynamically receive the subscriber information over a Gx interface. The appliance communicates with the PCRF server over the Gx interface, receives the subscriber information, and uses this information to direct the flow of traffic. The PCRF server can send updates over this interface at any point during the subscriber session.

For more information about Gx interface, see http://docs.citrix.com/en-us/netscaler/11/solutions/netscaler-support-for-telecom-service-providers/lsn-telco-subscriber-management.html.

Because of the shortage of IPv4 addresses, and the advantages of IPv6 over IPv4, many ISPs have started transitioning to IPv6 infrastructure. But during this transitioning, ISPs must continue to support IPv4 along with IPv6 because most of the public Internet still uses only IPv4, and many subscribers do not support IPv6.

Dual-Stack Lite (DS-Lite) is an IPv6 transition solution for ISPs with IPv6 infrastructure to connect their IPv4 subscribers to the Internet. DS-Lite uses IPv6 tunneling to send a subscriber's IPv4 packet over a tunnel on the IPv6 access network to the ISP. The IPv6 packet is de capsulated to recover the subscriber's IPv4 packet and is then sent to the Internet after NAT address and port translation other LSN related processing. The response packets traverse through the same path to the subscriber.

The NetScaler appliance implements the AFTR component of a DS-Lite deployment and is compliant with RFC 6333.

For more information about the DS-Lite feature, see http://docs.citrix.com/en-us/netscaler/11/solutions/netscaler-support-for-telecom-service-providers/dual-stack-lite.html.

Traffic steering is directing subscriber traffic from one point to another based on subscriber information. When a subscriber connects to the network, the packet gateway associates an IP address with the subscriber and forwards the data packet to the NetScaler appliance. The appliance communicates with the PCRF server over the Gx interface to get the policy information. Based on the policy information, the appliance performs one of the following actions:

- Forwards the data packet to another set of services

- Drops the packet

- Performs LSN if configured on the appliance

For more information about subscriber-aware traffic steering, see http://docs.citrix.com/en-us/netscaler/11/solutions/netscaler-support-for-telecom-service-providers/lsn-telco-subscriber-management.html.

The Internet's phenomenal growth has resulted in a shortage of public IPv4 addresses. Large Scale NAT (LSN/CGNAT) provides a solution to this issue, maximizing the use of available public IPv4 addresses by sharing a few public IPv4 addresses among a large pool of Internet users. LSN translates private IPv4 addresses into public IPv4 addresses. It includes network address and port translation methods to aggregate many private IP addresses into fewer public IPv4 addresses. LSN is designed to handle NAT on a large scale.

The NetScaler supports LSN and is compliant with RFC 6888, 5382, 5508, and 4787. The NetScaler LSN feature is very useful for Internet Service Providers (ISPs) and carriers providing millions of translations to support a large number of users (subscribers) and at very high throughput. The LSN architecture of an ISP using Citrix products consists of subscribers (Internet users) in private address spaces accessing the Internet through a NetScaler appliance deployed in ISP's core network.

The following lists some of the LSN features supported on a NetScaler appliance:

* ALGs: Support of application Layer Gateway (ALG) for SIP, PPTP, RTSP, FTP, ICMP, and TFTP protocols.

* Deterministic/ Fixed NAT: Support for pre-allocation of block of ports to subscribers for minimizing logging.

* Mapping: Support of Endpoint-independent mapping (EIM), Address-dependent mapping ( ADM), and Address-Port dependent mapping.

* Filtering: Support of Endpoint-independent filtering (EIF), Address-dependent filtering, and Address-Port-dependent filtering.

* Quotas: Configurable limits on number of ports and sessions per subscriber.

* Static Mapping: Support of manually defining an LSN mapping.

* Hairpin Flow: Support for communication between subscribers or internal hosts using public IP addresses.

* LSN Clients: Support for specifying or identifying subscribers for LSN NAT by using IPv4 addresses and extended ACL rules.

* Logging: Support for logging LSN session for law enforcement. In addition, the following are also supported for logging:

** Reliable SYSLOG: Support of sending SYSLOG messages over TCP to external log servers for a more reliable transport mechanism.

** Load balancing of Log Servers. Support for load balancing of external log servers for preventing storage of redundant log messages.

** Minimal Logging: Deterministic LSN configurations or Dynamic LSN configurations with port block significantly reduces the LSN log volume.

For more information about the Large Scale NAT feature, see http://docs.citrix.com/en-us/netscaler/11/solutions/netscaler-support-for-telecom-service-providers/lsn-introduction.html.

An ISP often purchases international bandwidth from upstream ISPs, who then become layer 2 ISPs. To provide the redundancy required for reliable service to its customers, the purchasing ISP negotiates Service Level Agreements with multiple layer 2 ISPs. The SLAs stipulate a penalty in the event that the layer 2 ISP fails to maintain a specified level of service.

NetScaler Insight Center and the NetScaler cache redirection feature can now be used to monitor the traffic flowing through the NetScaler appliances and calculate SLA breaches. The NetScaler cache redirection feature helps save bandwidth over international links. NetScaler Insight Center works with the NetScaler cache redirection feature to calculate, and provide visibility into, the percentage of bandwidth saved and any breaches of the SLA. ISP administrators are alerted whenever there is a breach for response time, hit rate/sec, or bandwidth.

For a specific domain, NetScaler calculates the following SLA breaches and forwards the data to NetScaler Insight Center:

* SLA Breach. A breach that occurs when a metric (response time, hits, or bandwidth) crosses the defined threshold value. For example, SLA breach is considered if the response time for a specific domain crosses 100 ms.

* SLA Breach Duration. Time period in which a SLA breach lasted. For example, SLA Breach Duration is considered 5 mins, if the response time for a domain is greater than 100 ms consistently for 5 mins.

* Breached Request Percentage. Percentage of requests whose response time is not within the minimum response time and maximum response time range. For example, if you configure this value as 10%, then among 100 requests, the response time of 10 requests are not within the minimum response time and maximum response time.

NetScaler Insight Center then calculates the following SLA breaches:

* SLA Breach Frequency- SLA Breach Frequency is the defined as the number of times the SLA breach occurs for the SLA Breach Duration. For example, SLA Breach Frequency is considered 1, if the response time for a domain is greater than 100 ms consistently for 5 mins.

All of these metrics are calculated for a SLA group, which contains a list of domains defined by the ISP administrator.

In the absence of a high availability (HA) setup, the subscriber information that is received from the RADIUS client is lost if the appliance fails. With HA support, the subscriber sessions are continually synchronized on the secondary node. In the event of a failover, the subscriber information is still available on the secondary node.

The NetScaler appliance currently maintains millions of subscriber sessions in its database (subscriber store) but does not log these messages. Telco administrators need reliable log messages to track the control plane messages specific to a subscriber. They also need historical data to analyze subscriber activities. The appliance now supports logging of RADIUS control plane accounting messages and Gx control plane logging messages. Some of the key attributes are MSISDN and time stamp. By using these logs, you can track a user by using the IP address, and the MSISDN if available.

A telco user can be uniquely identified by the IPv6 prefix rather than the complete IPv6 address. The NetScaler appliance now uses the prefix instead of the complete IPv6 address (/128) to identify a subscriber in the database (subscriber store). For communicating with the PCRF server (for example, in a CCR-I message), the appliance now uses the framed-IPv6-Prefix AVP instead of the complete IPv6 address. The default prefix length is /64, but you can configure the appliance to use a different value.

A Mobile Station Integrated Subscriber Directory Number (MSISDN) is a telephone number uniquely identifying a subscriber across multiple mobile networks. The MSISDN is associated with a country code and a national destination code identifying the subscriber's operator.

You can configure a NetScaler appliance to include MSISDNs in LSN log entries for subscribers in mobile networks. The presence of MSISDNs in the LSN logs helps the administrator in faster and accurate back tracing of a mobile subscriber who has violated a policy or law, or whose information is required by lawful interception agencies.

For more information, see http://docs.citrix.com/en-us/netscaler/11/solutions/netscaler-support-for-telecom-service-providers/lsn-introduction/lsn-monitoring.html.

Deterministic NAT allocation for DS-Lite LSN deployments is a type of NAT resource allocation in which the NetScaler appliance pre-allocates, from the LSN NAT IP pool and on the basis of the specified port block size, an LSN NAT IP address and a block of ports to each subscriber (subscriber behind B4 device).

The appliance sequentially allocates NAT resources to these subscribers. It assigns the first block of ports on the beginning NAT IP address to the beginning subscriber IP address. The next range of ports is assigned to the next subscriber, and so on, until the NAT address does not have enough ports for the next subscriber. At that point, the first port block on the next NAT address is assigned to the subscriber, and so on.

The NetScaler appliance logs the allocated NAT IP address and the port block for a subscriber. For a connection, a subscriber can be identified by just its mapped NAT IP address and port block. For this reason, the NetScaler appliance does not log the creation or deletion of an LSN session.

For more information, see http://docs.citrix.com/en-us/netscaler/11/solutions/netscaler-support-for-telecom-service-providers/dual-stack-lite.html.

Deterministic NAT and Dynamic NAT with port block allocation significantly reduce the LSN log volume. For these two types of configuration, the NetScaler appliance allocates a NAT IP address and a block of ports to a subscriber.

The minimum port block size for deterministic LSN configuration and dynamic LSN configuration with port block has been reduced from 512 ports to 256. This reduction of the minimum port block doubles the maximum number of subscribers for a NAT IP address in an LSN configuration. It also reduces the number of unused ports assigned to subscribers who do not need more than 256 ports at a time.

The port block size parameter can be set while adding or modifying an LSN group as part of an LSN configuration. A value of 256 (default) or a multiple of 256 can be set to the port block size parameter.

For instructions on configuring Large Scale NAT, see http://docs.citrix.com/en-us/netscaler/11/solutions/netscaler-support-for-telecom-service-providers/lsn-introduction/configuration-steps-lsn.html.

For sample LSN configurations, see http://docs.citrix.com/en-us/netscaler/11/solutions/netscaler-support-for-telecom-service-providers/lsn-introduction/lsn-sample-configurations.html.

The NetScaler appliance supports manual creation of DS-Lite LSN mappings, which contain the mapping between the following information:

* Subscriber's IP address and port, and IPv6 address of B4 device or component

* NAT IP address and port

Static DS-Lite LSN mappings are useful in cases where you want to ensure that the connections initiated to a NAT IP address and port map to the subscriber IP address and port through the specified B4 device (for example, web servers located in the internal network).

For more information, see http://docs.citrix.com/en-us/netscaler/11/solutions/netscaler-support-for-telecom-service-providers/dual-stack-lite.html.

The NetScaler appliance supports translating a part of the source IP address instead of the complete address of packets received on the appliance. IP prefix NAT includes changing one or more octets or bits of the source IP address.

The NetScaler appliance supports IP prefix NAT for traffic related to virtual servers and services for which the NetScaler does not maintain any session information. For example, virtual servers and services of type ANY, UDP, and DNS.

IP prefix NAT is useful in a deployment of NetScaler appliances and optimization devices (for example, Citrix ByteMobile) for identifying traffic from different client networks, which share the same network address, for meeting different optimization needs for traffic from each client network.

For more information, see http://docs.citrix.com/en-us/netscaler/11/networking/ip-addressing/configuring-network-address-translation/Partial-Nat.html

Subscriber-session cleanup on the NetScaler appliance is based on control plane events, such as a RADIUS Accounting Stop message, a Diameter RAR (session release) message, or a "clear subscriber session" command. In some deployments, the messages from a RADIUS client or a PCRF server might not reach the appliance. Additionally, during heavy traffic, the messages might be lost. A subscriber session that is idle for a long time continues to consume memory and IP resources on the appliance. The idle session management feature provides configurable timers to identify idle sessions, and cleans up these sessions on the basis of the specified action.

The "show aaa session" command causes a high level of CPU usage when executed with the "-username" or "-group" option.

The NetScaler appliance might become unresponsive if the persistence cookie feature is enabled in AAA-TM deployments.

When IBM Tivoli IdP is used for SAML authentication with NetScaler appliance as the service provider, there could be an issue with SAML assertion verification.

When kerberos token decryption fails, the NetScaler appliance responds with a 200 response with error message, instead of sending a 401 response.

Single sign-on to server does not succeed when native clients, such as iOS clients, connect to the NetScaler appliance using Active Sync protocol and send cookies along with authorization header.

If the AAA virtual server is configured to an non-ActiveDirectory LDAP server, and an invalid password is used to logon, the NetScaler appliance becomes unresponsive.

The status of a LDAP server on the authentication dashboard of the NetScaler GUI, will be shown as UP, regardless of the actual status of the LDAP server, for the following combinations:

- Security type is SSL and port is 389.

- Security type is TLS or PLAINTEXT and port is 636.

When RADIUS is used in nFactor authentication, the NetScaler appliance fails to complete the request if user is prompted for password change.

On a NetScaler MPX-FIPS appliance, the AAA module becomes unresponsive if the configured RADIUS or TACACS policies are triggered. So, from this build onwards, RADIUS and TACACS policies are not supported on MPX-FIPS appliances.

Note: RADIUS and TACACS are not FIPS compliant protocols.

Authentication fails if the server name in an LDAP action is changed from an FQDN to an IP address by using the "set ldapaction" command.

The Netscaler appliance intermittently fails if a user accesses a very long URL without proper AAA context.

When the NetScaler appliance is configured as SAML Service Provider (SP), the SAML Identity Provider (IdP) dishonors a logout request that is performed on the traffic management virtual server (load balancing or content switching) that uses a AAA-TM traffic policy.

This happens because the NetScaler SP sends to the SAML IdP a SAML logoutRequest that contains "Conditions" XML tag.

In a multi-core NetScaler environment, user sessions sometimes do not get terminated if the decision to terminate is based on a force timeout value that is configured on a TM traffic action.

If a logout message from a session owner to a cached session is dropped, the NetScaler appliance might fail while trying to resend the message.

You cannot enter the FQDN for a RADIUS or LDAP server by using the NetScaler GUI.

A global flag that tracks stream sessions when the ICMP traffic processing begins is not initiated properly.

Partition administrators cannot upload scriptable monitor scripts to a partition. This can only be done by NetScaler superusers. Also, scriptable monitors for an admin partition cannot be configured by using the GUI.

On a partitioned NetScaler appliance, the scope of updating the L2 and L3 parameters is as follows:

- For L2 parameters that are set by using the "set L2Param" command, the following parameters can be updated only from the default partition, and their values are applicable to all the admin partitions: maxBridgeCollision, bdgSetting, garpOnVridIntf, garpReply, proxyArp, resetInterfaceOnHAfailover, and skip_proxying_bsd_traffic. The other L2 parameters can be updated in specific admin partitions, and their values are local to those partitions.

- For L3 parameters that are set by using the "set L3Param" command, all parameters can be updated in specific admin partitions, and their values are local to those partitions. Similarly, the values that are updated in the default partition are applicable only to the default partition.

In an admin partition, changes done to enable or disable a NetScaler feature or mode are not saved. Therefore, after the NetScaler appliance is rebooted, the status of the feature or mode is reset to its default value.

When creating an admin partition, you can now set the memory limit to a minimum value of 5 MB.

When the NSIP password is changed (by using the "set ns rpcnode" command) on the default partition, the GSLB auto-sync function does not work in the available admin partitions.

The order in which AppExpert evaluates application units cannot be changed. With this fix, the NetScaler GUI displays a burger icon for each application unit. After hovering over the icon, you can move an application unit up or down in the order of evaluation.

Navigation: Configuration > AppExpert > Application > Application Unit section

When routes are updated after an AppFlow collector is added, the NetScaler appliance sends ARP requests for the AppFlow collector IP address, even when the collector is reachable only through a router.

The NetScaler appliance might become unresponsive if you enable the client side measurement option for an AppFlow action.

The NetScaler appliance might become unresponsive if a request generated by a client is corrupted after execution of the client-side measurement script. This issue can occur if you enable the client side measurement option for an AppFlow action.

If, when processing a form for response-side security check inspection, the application firewall resets a connection, the partially parsed form is not freed. The result is a memory leak. With this fix, the memory allocated to the partially parsed forms is freed when a connection is reset.

After processing a request that consists of multiple headers of the same type, a subsequent request might invoke a 302 response due to the way the application firewall stores the information regarding the parsed headers. With this fix, the variable which stores the information regarding the headers is reinitialized accurately prior to processing the next request.

The NetScaler appliance might become unresponsive when processing a request, because of an interoperability issue between the application firewall, SSL, and the responder module. The issue arises under the following set of circumstances:

The configuration includes an application firewall profile protecting an SSL virtual server.

A responder policy is configured to reset the connection, and this policy is bound either globally or to the virtual server that receives the request.

During an application firewall security check inspection, a compressed response from the server might trigger a violation if the XML format check is enabled. With this fix, the Accept-Encoding request header is removed when the XML protections are enabled. If content compression is enabled on the server, the XML check inspection is bypassed when the server sends a compressed response.

After processing a request that consists of multiple headers of the same type, a subsequent request might invoke a 302 response due to the way the application firewall stores the information about the parsed headers. With this fix, the variable that stores the information regarding the headers is reinitialized accurately before the next request is processed.

If learning thresholds for the application firewall security checks are set to a value greater than 1, the configuration utility displays the following error message when you try to access the learned data: "communication error with aslearn."

Workaround: Use the command line interface (CLI) to access the learned data.

The Citrix application firewall silently resets the connection when it receives a malformed or invalid request. With this fix, the application firewall logs such events.

The NetScaler application firewall terminates the connection when the request comes with a tampered session cookie and the cookie protection is enabled.

If you use the default browser PDF plugin to view an application firewall report, embedded links might be inactive.

Workaround: Use the Adobe PDF browser plugin.

NetScaler application firewall resets the connection when the request contains tampered session cookie and the cookie protection is enabled.

The Skip operation for the application firewall learned rules might take longer than expected.

The NetScaler appliance might fail when the application firewall is processing the cookie header(s) in an HTTP request. This occurs when the cookie transform action is enabled and all other security checks that apply to establishing a user session are disabled.

Signatures version may not get updated correctly if updated_signatures.xml file is present in /nsconfig folder. With this fix, this file is removed during build installation and the version of the application firewall signatures is updated accurately.

Application firewall profiles that are exported and archived from one build cannot be restored to a system running a different build, because changes introduced in the newer releases can lead to compatibility issues. With this fix, the application firewall now logs an error message, in ns.log, if you attempt to restore an archived profile to a different build than the one from which it was exported.

The NetScaler appliance might become unresponsive when processing a request, because of an interoperability issue between the application firewall, SSL, and the responder module. The issue arises under the following set of circumstances:

The configuration includes an application firewall profile protecting an SSL virtual server. A responder policy is configured to reset the connection, and this policy is bound either globally or to the virtual server that receives the request.

The application firewall buffers the entire request for security check inspections. Therefore, when the client sends the expect 100-continue header in the request, the application firewall sends the 100-continue response to get the entire request from the client. The application firewall modifies the expect 100-continue header received from the client and corrupts it before forwarding the processed request to the server. In the 11.0 release, the header was not corrupted before it was forwarded request to server. With this fix, the expect 100-continue header from the client is modified and a corrupted header is sent to the server.

The NetScaler application firewall terminates the connection when the request comes with a tampered session cookie and the cookie protection is enabled.

NetScaler application firewall resets the connection when the request contains tampered session cookie and the cookie protection is enabled.

The application firewall has extended external format signature support for a new scan tool called WebInspect. The WebInspect scan tool, provided by Hewlett Packard (HP), is designed to analyze the web applications and web services for security vulnerabilities. As stated in the following Data Sheet link from HP, "WebInspect provides the broadest dynamic application security testing coverage and detects new types of vulnerabilities that often go undetected by black-box security testing technologies": http://www8.hp.com/h20195/V2/GetPDF.aspx/4AA1-5363ENW.pdf.

See http://docs.citrix.com/en-us/netscaler/11/security/application-firewall/signatures.html" for the details of importing and configuring signatures.

When URLTransform or CVPN policies are configured, application firewall code is invoked to carry out the validation of http packet information even if application firewall feature is disabled. When streaming code is engaged, the application firewall is not processing the conditional headers accurately and might reset connection and respond with RST code 9856. With this fix, parsing and validating the request headers is handled correctly by the application firewall module.

When the application firewall redirects a blocked request to a customized error page, the ${NS_APPFW_SESSION_ID};variable on the error page might not display the session ID accurately. If the request does not contain a session cookie, the variable might display a hyphen (-) instead of the session ID.

If the application firewall cookie proxy check is enabled and the server tries to expire and modify the same cookie in the same response, the NetScaler appliance might fail because of memory corruption.

In a cluster deployment, accessing the application firewall learned data might display "Error in retrieving Application Firewall learning data. Communication error with aslearn". This error is triggered if buffer overflow occurs when the cluster configuration coordinator tries to get learned data from the other nodes of the cluster.

The NetScaler appliance might fail when the application firewall is processing the cookie header(s) in an HTTP request. This occurs when the cookie transform action is enabled and all other security checks that apply to establishing a user session are disabled.

When a user-defined application firewall signature object is updated by using the configuration utility, the enabled rules might get disabled and the configured actions in some signature rules might not be preserved.

The NetScaler appliance might fail when the application firewall receives an HTTP response with an attribute value that exceeds 1 MB in length.

In NetScaler web application firewall high availability deployments, application firewall sessions are not cleaned up on the secondary node. As a result, memory usage increases on the secondary node.

You might encounter unexpected failures if form field consistency protection is enabled on the application firewall profile and you try to retrieve the form from Distributed Hash Table (DHT).

In release 10.5.e (enhancement builds only) as well as in the 11.0 release builds, application firewall processing of the Cookie header was changed. In those releases, every cookie is evaluated individually, and if the length of any one cookie received in the Cookie header exceeds the configured BufferOverflowMaxCookieLength, the Buffer Overflow violation is triggered. As a result of this change, requests that were blocked in 10.5 and earlier release builds might be allowed, because the length of the entire cookie header is not calculated for determining the cookie length. In some situations, the total cookie size forwarded to the server might be larger than the accepted value, and the server might respond with "400 Bad Request".

With this fix, the change has been reverted. The behavior is now similar to that of the non-enhancement builds of release 10.5. The entire raw Cookie header is now considered when calculating the length of the cookie. Surrounding spaces and the semicolon (;) characters separating the name-value pairs are also included in determining the cookie length.

When the application firewall cookie proxy check is enabled, the NetScaler appliance might become unresponsive while updating the cookies in the distributed hash table with a set of cookies from the server.

When you use the NetScaler GUI to perform the Skip operation, the application firewall learned rules might not be deleted. This occurs because NITRO is sending wrong "Location" ("Field") data to the GUI. With this fix, the GUI converts "Field" into "FORMFIELD," and the Skip operation removes the skipped rules, as expected.

The application firewall might experience a transient low-memory condition during a traffic surge if advanced security check protections (such as Form Field consistency, CSRF, form tagging and so on, which require rewriting the HTML forms in the response) are enabled for the profiles. This might result in a memory leak, and memory allocation failures might occur even after the traffic surge subsides.

When you use the NetScaler GUI to perform the Skip operation, the application firewall learned rules might not be deleted. This occurs because NITRO is sending wrong "Location" ("Field") data to the GUI. With this fix, the GUI converts "Field" into "FORMFIELD," and the Skip operation removes the skipped rules, as expected.

Application Firewall memory allocation errors might occur if the license on the NetScaler appliance restricts the number of packet engines.

The XSS transform for special characters in the application firewall might not work as expected if the -crossSiteScriptingTransformUnsafeHTML option or the sqlTransformAction option is set to ON in the profile.

In certain cases, if a custom error page containing variables is served to the client, the content length in the response is incorrect. As a result, the custom error page might not be visible in the client's browser.

In a cluster setup, while exporting application firewall learnt data, you might see the following error message:

"communication error with aslearn"

This message is because of a schema difference.

If you use the Mozilla Firefox browser to access the NetScaler GUI, you cannot make changes to the application firewall configuration.

NetScaler application firewall handles memory incorrectly if XSS and "CrossSiteScriptingCheckCompleteURLs" are enabled in the application firewall profile. The errors also appear if "checkrequestHeaders" and finegrained relaxations are enabled.

You can now customize the log levels for logs generated for AAATM user logon or logoff, and for logs generated for executive commands by a NetScaler administrative user.

If a request to a cache redirection virtual server resolves to an IP address that belongs to a content switching virtual server configured on the NetScaler appliance, the appliance might fail.

In the GUI, the Policy drop-down list does not display the cache redirection policies.

If RISE feature is not enabled and we try to disable it, an error message is displayed for all the features.

You cannot add LB routes in a link load balancing setup that is deployed on a cluster.

In a cluster setup, for active FTP, the server cannot initiate a data connection from a random port.

In a NetScaler cluster, a "sh nslogaction" command that is issued from the NSIP address of a cluster node, goes into an infinite loop. The issue is not observed when the command is issued from the cluster IP address.

In a cluster setup, a command that is executed on the cluster configuration coordinator is propagated to the other cluster nodes. Therefore, a command that takes a long time to complete (such as "save ns config"), can take a little extra time to complete on all the cluster nodes. During this time, if you execute another command on the cluster (through another session), that command will fail because the previous command is not yet complete.

When WIonNS is deployed in a cluster setup, if you add a service that points to the NSIP of a newly joined node, the command fails on the newly joined node but succeeds on the other cluster nodes.

A NetScaler cluster does not respond to cURL HTTP requests from outside the datacenter, because the Path MTU Discovery (PMTUD) mode gets disabled when a cluster is created.

A customized CLI prompt is not persisted after rebooting the appliance.

The operation to download the nstrace file from the configuration utility fails.

You cannot configure the service path AVP by using the configuration utility.

Workaround: Use the NetScaler command line to configure the service path AVP. At the command prompt, type:

set subscriber gxinterface -servicepathAVP 1001 1005

SUBSCRIBER expressions do not appear in the list for rewrite and responder policies and action.

You cannot configure the service path AVP by using the configuration utility.

Workaround: Use the NetScaler command line to configure the service path AVP. At the command prompt, type:

set subscriber gxinterface -servicepathAVP 1001 1005

The operation to download the nstrace file from the configuration utility fails.

The values for the parameters on the "Configure Load Balancing Parameters" page do not appear even though they have been set.

If you click a VLAN in the network visualizer, details such as VLAN ID and bound interfaces are not displayed in a separate pane.

The configuration utility does not reflect the correct count of cached objects whereas this number is shown correctly through the command line interface.

If you create a cipher group and do not add any ciphers to it, an error message appears when you try to open the cipher group in the configuration utility.

You cannot add user-defined values for the user name and group name fields on the Authentication CERT Profile page.

With this fix, you can specify a user-defined value by navigating to Security > AAA - Application Traffic > Policies > Authentication > Basic Policies > CERT > Profiles or NetScaler Gateway > Policies > Authentication > CERT > Profiles and selecting New in the User Name Field list and the Group Name Field list.

When an HTML page is imported, the content is copied to /nsconfig/ssl and then to /var/download/responder. The content is not removed from /nsconfig/ssl, although it serves no purpose there. With this fix, the content is copied directly to to /var/download/responder.

If you are using the configuration utility to run diagnostics on the NetScaler appliance, you cannot specify a traffic domain.

The integrated caching feature is not available on the GUI.

When starting a nstrace and another instance is already running, an option to stop this is not available in the configuration utility. One has to login through the command line interface to stop the trace.

You cannot install a server, client, or intermediate certificate with a FIPS key by using the configuration utility.

If you log on to the appliance by using the GUI, the list of licenses is not retrieved.

If a large number of content switching policies are bound to a content switching virtual server, using the configuration utility to bind a new policy without explicitly assigning a priority might result in the policy being assigned the priority of the first policy on the next page of the display. Since a policy is already assigned that priority, an error message stating that the priority is already used appears.

In certain cases, if the state of a load balancing virtual server changes, the NetScaler appliance might fail while changing the state of the associated content switching virtual server.

The query logs contain incorrect information if the UDP payload size in the OPT record is not 1280. Also, if a load balancing virtual server on the NetScaler appliance receives a request with the CD bit set, and the "RecusionAvailable" parameter is disabled on the DNS or DNS-TCP load balancing virtual server, the CD bit is not logged.

If, while a DNS-TCP client request is in surge queue, the NetScaler appliance receives a FIN from the client and responds with a FIN or ACK before the queued request is forwarded to the backend server, the appliance might fail.

The NetScaler appliance fails, if there is a cache miss when the backend DNS server is accessed directly through the NetScaler appliance.

If, while resolving a domain name in DNS resolver mode, the NetScaler appliance does not receive a response from the first name server, it tries to resolve the domain name with the other name servers. During this process, if the address record for the associated NS record is not present, the NetScaler appliance fails.

If a Netscaler appliance in DNS resolver mode is configured to resolve queries with suffixes, the appliance fails if there is no address record for the NS record associated with one of the suffixes.

A NetScaler client becomes unresponsive if:

1. The NetScaler appliance receives the complete response to the client's query from the server.

2. At the same time, the client sends an attention packet to the appliance.

The client becomes unresponsive because the appliance closes the server-side connection but does not send the client a response to the attention packet.

If you have configured the canonical name as the GSLB domain in NetScaler appliance, when the backend server returns the CNAME record without the requested record, NetScaler appliance changes the TTL value of the GSLB domain with the TTL value of the CNAME record.

GSLB virtual server configured with Dynamic Proximity as LB method fails.

Description: You can now configure a content switching (CS) policy to customize a GSLB deployment so that you can:

* Restrict the selection of a GSLB service to a subset of GSLB services bound to a GSLB virtual server for the given domain.

* Apply different Load Balancing methods on the different subsets of GSLB services in the deployment.

* Apply spillover policies on a subset of GSLB services, and you can have a backup for a subset of GSLB services.

* Configure a subset of GSLB services to serve a specific type of content.

* Define a subset GSLB services with different priorities, and define the order in which the services in the subset are applied to a request.

For more information, see Configuring GSLB Service Selection Using Content Switching.

Initiating 280k SIP sessions with 40k subscribers might cause the NetScaler appliance to fail.

If a server entity (for example, a server IP address or server name) is associated with both a GSLB entity and a non-GSLB entity on a GSLB site, and the GSLB configuration is synced to another site that does not include this server entity, the synchronization removes the server entity and all other entities associated with that server.

When using the GUI in a partitioned environment, you cannot add GSLB services.

For GSLB deployments in a partitioned environment, the options to synchronize the GSLB configuration and view the synchronization status are provided in the GUI.

If the ACK on PUSH option is disabled in the default TCP profile, the NetScaler appliance might fail while downloading the static proximity database.

In a content switching GSLB deployment, you can bind multiple domains to a CS GSLB virtual server, but the show cs vserver command shows only one domain bound to the CS GSLB virtual server.

The NetScaler appliance fails if you run the "show gslb domain" command on a non-gslb domain record.

In the GUI, on the GSLB statistics page, the local site MEP state is always displayed as DOWN instead of as a blank field.

The HA traffic between the HA pair is abnormally high. This issue is caused by a loop that repeatedly tries to push the same sessions to the secondary appliance after failover.

When there is a HA issue, the synchronization of persistence sessions between the primary and secondary appliances can fail. This can cause some of the persistence sessions not being replicated on the secondary appliance.

When there is a HA issue, the synchronization of persistence sessions between the primary and secondary appliances can fail. This can cause some of the persistence sessions not being replicated on the secondary appliance.

The NetScaler can stop responding when cache object persistency is configured in a HA setup.

When the "clear config" command is issued, the NetScaler appliance can become unresponsive if more than one CPU tries to free the same shared memory.

A NetScaler appliance performing integrated caching becomes unresponsive if the length of the URL is 2040 (including the hostname, query parameter, and other specific information).

A VPX system can repeatedly fail if HA cache persistence is used along with HTML-injection.

Disabling the Media Classification mode, even if the host header is missing in the GET request, does not cause a NetScaler appliance to fail.

When a NetScaler appliance uses a flash cache with HTTPS traffic, only the initial client request is serviced. Subsequent client requests fail.

If an SSL monitor is bound to a domain-based service that is configured with non-default SSL settings, the monitor might not show the service as UP.

The appliance fails if non-reachable autoscale entities that are part of a service group later become reachable and, in the interim, the service group name has changed.

When editing a service group in the configuration utility, the cacheable option is automatically set to true.

In a load balancing group configuration, the "sh run" command sometimes runs in a loop, which exponentially increases the size of the temporary configuration file. As a result, saving the configuration and synchronizing the nodes in a high availability setup might fail.

If the channel between the primary node and the secondary node is disrupted, the session deletion information sent from the primary node to the secondary node might get lost. As a result, while the persistent sessions are reduced to zero on the primary node, the secondary node reaches its limit.

In certain cases, if the name of an FTP virtual server is greater than 32 characters, the virtual server lookup fails and the request is not served.

In a high availability setup, if a large number of services and service groups are configured, service state updates might fail because of a timer issue.

In a link load balancing (LLB) deployment, if persistence is enabled on a NetScaler appliance and a policy based routing (PBR) or LB route is configured, the appliance might fail intermittently.

In a link load balancing (LLB) deployment, if persistence is enabled on a NetScaler appliance and a policy based routing (PBR) or LB route is configured, the appliance might fail intermittently.

A secure StoreFront monitor intermittently fails to sends probes.

Workaround: If your deployment allows non-secure connections, use a non-secure StoreFront monitor.

While probing the back-end HTTP server by using an HTTP monitor, the appliance does not send the port number in the HTTP host header. This behavior is not compliant with RFC 2616.

The NetScaler appliance fails while trying to load balance a request that was received on a recently closed connection. This happens because the server tries to keep the connection alive by sending an RTSP request but the appliance cannot find the corresponding client side connection.

Feature DNS

Due to a memory overwrite issue, the prev value of dns_tot_ServerQueries counter is set to zero everytime during the end of perf collection cycle, that is every 7 seconds. This results in the difference between cur and prev value get accumulated to the global counterpart even if there is no traffic.

In a high availability setup, if a large number of services and service groups are configured, service state updates might fail because of a timer issue.

In a high availability setup in admin partition mode, the persistent sessions are not synchronised to the secondary node after performing force ha sync or force failover operation.

The NetScaler appliance fails because of an incorrect initialization of template size in a stream analytics session info record.

Feature; AAA-TM

If you are using AAA-TM on an HTTP virtual server with no endpoint features enabled, the acknowledgement from the NetScaler appliance might not contain all the data that the client sent. This might cause some page elements to not load completely, or to time out.

The TCP connection is not persistent for NITRO requests. Therefore, the underlying TCP connection is getting closed for each NITRO request.

For the .NET SDK, when "nitro.dll" is used along with a version later than 4.0 of the "Newtonsoft.json.dll" file, "private" properties cannot be serialized.

The NetScaler appliance might become unresponsive when a NITRO request is fetching a large number of bound entities.

If the NetScaler appliance receives a logon request that contains both the session token and the request payload with the logon credentials, the appliance creates a new connection without closing the previous connection. If the appliance receives multiple such requests, the following error message appears: CFE limit exceeded.

Different languages use different keyboard layouts, causing problems with using special characters through the LOM console. With this fix, the LOM console supports additional keyboard layouts and keyboard control tools.

To change the keyboard layout, in the console, navigate to options > preferences and select a language.

Some Unified Gateway traffic management session do not terminate at VPN logout.

When the maxAAAUsers parameter is UNSET on a VPN virtual server, NetScaler Gateway does not update the value to previously set value. Due to this, numbers of users allowed on a vpn virtual server cannot be increased by applying an UNSET operation. Administrators need to configure a SET operation as a workaround.

For example, if the administrator configures 10 as the maxAAAUsers value, then issues a SET operation for 5, if he issues another UNSET, the number of allowed users does not go back to 10 users.

Applications configured with SAML or NetScaler self-authentication, on a Unified Gateway portal, return the following 403 error message : Not a privileged user.

When the HTTP/2 Protocol is used to access the VPN with external authentication, the transaction will not go through. Ensure HTTP/2 is disabled in nshttp_default_strict_profile.

In a Chrome browser, the home page is sometimes blank. Refreshing the page resolves the issue.

An error message is issued when a user tries to bind a CS policy to the VPN virtual server (CS-AG feature). The CS policy points to a VPN virtual server (Unified-Gateway feature). This is an expected behavior. The error message was improved to convey that it is an expected behavior.

When logging into NetScaler 11.0 using a clientless VPN, SharePoint 2013 does not load correctly. The SharePoint folders are not accessible.

App/VDA launch via HTML5 receiver fails when using Firefox.

When accessing SharePoint 2007 through Clientless VPN, the VPN session terminates, and some URL requests are not rewritten in Clientless VPN mode.

EULA feature: The EULA on a fresh HyperV image issues an error. It works fine for upgraded builds. Workaround is

1) Go to NetScaler shell

2) type the command: # perl /var/netscaler/logon/themes/EULA/eula_upgrade.pl

Now an EULA can be configured using the Management GUI.

When a VPN works as a SAML SP in a two-factor case, and if the Get /vpn/index after /cgi/samlauth comes to the same core, NetScaler resends the SAML Auth request.

Intermittent issues appear in multi-core systems. It works normally if both requests go to different cores.

If NetScaler Gateway is used to access SSL backend resources over Clientless VPN (CVPN) or SecureBrowse mode using a forward proxy, then in the event that client/browser is very slow in sending POST requests to gateway, the request times out.

Clearing the configuration does not remove the Themes directory from the NetScaler appliance's drive. If you want to remove this directory, use the shell to delete it from the following path:

/var/netscaler/logon/themes/

To remove just the EULA-string nodes, delete them from the following path:

/var/netscaler/logon/themes/EULA/resources

If you create a la portal theme, avoid using a name with spaces. Use an underscore instead of a space.

An unintentional automatic Linux exit happens under the following conditions:

* The NetScaler appliance is configured for dual, certificate authentication and LDAP authentication.

* The subject field of the client certificate doesn't contain an email attribute value.

The plug-in crashes when VPN logout is performed from browser.

This would cause the logout page to not load in browser which directs user to login page.

Work around:

Manually type NSG URL in browser to login again.

An internet connection is required for publisher verification for the NetScaler Gateway plug-in for Windows. If not connected to the internet when downloading the plug-in from the NetScaler Gateway, the error 'Publisher AGEE_setup.exe couldn't be verified' occurs.

When launching applications through NetScaler Gateway, which has an AppFlow policy bound with the type of OTHERTCP_REQUEST, the Gateway can fail. This failure is not seen if the AppFlow policy is bound with the type ICA_REQUEST.

The Total AAA Session Graph always shows 5 sessions active; even when, there are no active AAA sessions.

The Expression editor is missing the following new policy expressions: ICA.SERVER.IP, ICA.SERVER.IPV6, ICA.SERVER.PORT.

The Locale settings have been moved out of the Look and Feel section. Now, we have 2 separate sections :

- Section 1 is for settings the attributes related to the Look and Feel of portal pages.

- Section 2 is for choosing a locale.

Users can choose a locale to edit labels/texts for portal pages.

Chrome is phasing out NPAPI support. From Chrome version 42+ all NPAPI plugins will appear as if they are not installed. This will affect all existing customers. Affected customers will see a download prompt even though the VPN plugin is installed.

Workaround: Google has announced that Chrome will stop supporting NPAPI completely in version 45.

Until then, you can enable NPAPI as follows:

1) In the Chrome URL bar, type:

Chrome://flags

2) Enable the "Enable NPAPI" option.

3) Restart Chrome.

For more information about NPAPI deprecation, see https://support.google.com/chrome/answer/6213033?hl=en

When Netscaler Gateway is configured in a Striped cluster, and a force cluster sync operation is done on a NON CCO node, subsequent access can cause the NetScaler Gateway appliance to crash.

The Unified Gateway Wizard for XenDesktop/Xenapp Application creates wrong configurations with the Storefront option. The client launches the Java plug-in instead of Win/Mac/iOS/Android plug-in.

In a double hop setup, when SSL relay is enabled for XenApp and XenDesktop, the XenApp or XenDesktop resource launch fails. The builds affected: 10.1-118.X to 10.5-55.8.

When going to NetScaler Gateway > Policies > Content Switching, the breadcrumb shows Traffic Mgmt > Content Switching > Policies. The breadcrumb appears to be incorrect.

When launching applications through NetScaler Gateway, which has an AppFlow policy bound with the type of OTHERTCP_REQUEST, the Gateway can fail. This failure is not seen if the AppFlow policy is bound with the type ICA_REQUEST.

The Mac OS Endpoint Analysis (EPA) client only supports TLS1.0 and thus cannot perform EPA if the server has only TLS1.1/1.2 enabled.

There is no workaround for this problem, but a customer can still perform EPA with the Mac VPN plugin. EPA from a browser will not be available if TLS1.0 is not enabled.

Changes made to the Login page using the GUI are not reflected on the virtual server login page.

Workaround:

1. Use any browser other than IE to make changes to Portal themes.

If an invalid certificate is selected as part of login, when certificate Authentication is optional, and two factor authentication is ON, the login fails as expected. But an app saves the certificate, though login failed. The user has to manually delete the saved certificate from the EditConnection Page to retry with a valid/no certificate.

The NetScaler counters, used to verify connected users, displays a value that does not reflect actual connections.

The Client and EPA Plug-ins don't work with the latest Chrome versions as support for NPAPI is disabled by default. The support will be deprecated entirely in Chrome version 45 in September 2015.

From Chrome version 42, all NPAPI plugins will appear as if they are not installed. This will affect customers upgrading from 10.5 to 11.0. This is also applicable to customers who upgrade from 11.0 Beta builds and later Release builds. Affected customers will see a download prompt even though the VPN or EPA plugin is installed.

Workaround:

There is no work around to enable NPAPI for Chrome on Linux.

Users need to use a browser which allows NPAPI (e.g. Firefox).

More about NPAPI deprecation in Chrome browsers can be found at: https://support.google.com/chrome/answer/6213033?hl=en

Smart Control does not work for applications that have SSL relay enabled on the server with few ICAPOLICY rules.

The Portal Customization feature does not offer the option to cancel or remove the default GUI or custom GUI images.

Audio over UDP is not supported with ICA sessiontimeout enabled or with Smart Control.

RPC (Remote Procedure Call) over HTTP communication is blocked if the AppFlow or HTML Injection features are enabled.

During the installation of Logon Point, the following error message was issued: "Couldn't execute eula_upgrade.pl error".

For a VPN virtual server with ipaddress -0.0.0.0, listen policies and services are not allowed to be set. The NetScaler appliance terminated due to invalid memory access.

NetScaler Gateway sends the wrong error code back to the user when the active directory password has expired, and the user tries to change the password and violates password complexity rules.

RPC (Remote Procedure Call) over HTTP communication is blocked if the AppFlow or HTML Injection features are enabled.

On the Windows 10 system, if users log off from the NetScaler Gateway portal, the Windows VPN plugin crashes intermittently. As a workaround, users may use the VPN plugin's context menu for logging-out.

NetScaler unexpectedly terminates when accessing network share using the following apps: iOS Sharefile app /MDX Wrapped app.

You cannot bind an ECC curve to a NetScaler Gateway virtual server by using the NetScaler GUI.

The NetScaler EPA (Endpoint Analysis) timeout was increased to 5 minutes.

If the WI home is configured with FQDN, NetScaler modifies the host header with the IP address of the WI server when sending traffic to WI server. Similarly, if wihome is configured with the IP address, that IP address is sent in the host header to the WI server. In both these cases, the WI server returns an error.

After the fix, the host header is updated to the FQDN in the wihome as opposed to IPaddress. In cases where wihome FQDN resolves to the domain based server on Netscaler, The host header is updated with the FQDN of the domain based server

End users are experiencing performance degradation when connecting to their Avaya One-X via VPN connection. End users are able to establish 3-5 calls before the symptoms are exhibited. However, after a period of time, we are able to make calls again. The quality starts to decrease after the first few phone calls are made.

The workaround is to restart the VPN connection.

The NetScaler appliance crashed due to invalid memory access. The memory allocation failure occurred due to a bug processing a cookie.

If SSL SessionReuse is enabled on Gateway virtual server, if a user cancels certificate authentication prompt at the time of login, he sees an error. However, at times, a browser refresh shows login page and allows access.

Workaround: SessionReuse should be disabled.

Client traffic can slow down if ALL of the following conditions are satisfied:

- Single Sign-on (SSO) is ON.

- HTTP POST request is involved which requires to do SSO.

- NTLM authentication is needed to authenticate to back-end.

- Transferring large payload (greater than 2 MB).

- The back-end server is responding slow.

This issue is unlikely to occur if ANY ONE of the following conditions is satisfied:

- HTTP POST request Payload is in KBs.

- Back-end authentication method is non-NTLM ( such as AGBasic, Form-based SSO, and KCD).

- Non-HTTP POST request involved.

- SSO is not involved or disabled.

Workaround: Disable SSO for HTTP POST request.

In Unified Gateway deployment, if there are no matching Content Switching policies for the storefront requests in ICA Proxy mode, and default Load Balancing is used for serving this traffic, the NetScaler appliance might fail.

While assigning an IntranetIP, if Netscaler Gateway finds a duplicate, it cleans up associated session. In this process, occasionally Gateway might fail.

The EPA may fail if a high number of EPA scans are configured.

If you remove a Negotiate authentication profile that is available on NetScaler Gateway, the appliance can fail when checking for incorrect IPv6 mapping.

The RDP Proxy messages were enhanced to include information concerning the controls that are in place at the connection.

The Federated Service SSO fails when using the browser to access the NetScaler appliance.

With ICA policies configured or with ICA session timeout enabled and with Storefront 3.0 configured, Apps/Desktops won't launch because of a change in Storefront behavior that the Netscaler is not handling.

When the NetScaler Gateway virtual server is bound to a Content Switching virtual server, all web socket connections are passed to the NetScaler Gateway virtual server.

The NetScaler appliance experienced a system error due to a memory corruption issue.

If a user logs into a receiver on a machine, which is configured to use an AutoProxy Script, and that AutoProxy script URL is unreachable, the login fails.

A crash occurs when the packet engine is set up with an aync call with a NULL NSB pointer.

The customer experiences long set up times when using the following plug-ins: V10.1-128.8 or V10.5-55.8. If they downgrade back to receiver plugin 10.0-54.6, the issue disappears and they see immediate VPN setup times.

When a user tries to access the system and if that connection gets terminated while authentication is in progress, NetScaler might fail.

When users from INTL domain login via NetScaler ( a dual factor with RADIUS) by entering username only (no domain information in the login page) it fails. When users from Corp domain login via NetScaler (dual factor RADIUS) by entering username only (no domain information in the logon page) it works. The above is expected behavior. Storefront needs the domain\username information when a user from INTL domain logon. When entering domain\username format on the NetScaler login page, RADIUS rejects the login, and it does not pass the domain\username information to the Storefront server, so the login fails.

Single sign on (SSO) for the NavUI file share view does not honor the ssocredential configuration on the authentication action, and instead sends only the username from the authentication session. If a domain is configured to accept something other than the session username, SSO will fail. This fix makes NavUI file share properly honor the ssocredential setting and send what the administrator has configured.

Terminal Access Controller Access Control System (TACACS) counting sometimes causes memory corruption and the authentication daemon crashes. Multiple crashes of the authentication daemon lead to the NetScaler rebooting.

Applications using more than 128 simultaneous connections over VPN fail on Windows machines.

In a double hop setup, when SSL relay is enabled for XenApp and XenDesktop, the XenApp or XenDesktop resource launch fails. The following builds are affected: 10.1-118.X to 10.5-55.8.

The RDP Proxy feature on NetScaler Gateway now requires special licensing, and needs to be explicitly enabled using the 'enable feature rdpproxy' command. In addition, the 'psk' attribute, used to protect the user information sent to the STA server, is now mandatory whenever a rdpserverprofile is configured.

When configuring DTLS to be ON on an existing virtual server, unbind and rebind the SSL cert-key pair bound to the virtual server to connect with DTLS. If this is not done, the DTLS connection handshake between the client and the NetScaler Gateway appliance fails. After rebinding the SSL certkey pair, the handshake is accepted and the DTLS traffic goes through.

Smart Control does not work for applications that have SSL relay enabled on the server with few ICAPOLICY rules.

The NetScaler appliance connected to the Linux SSL VPN client, but could not connect to the DNS lookups. After a reboot of the appliance, the NetScaler appliance connected to the Linux SSL VPN client and the DNS lookups worked fine.

Two NetScale appliances rebooted themselves because the TACACS accounting code crashed. The crash occurred due to the presence of an invalid flag in the clientPCB.

The NetScaler Gateway plug-in for windows issues a force timeout warning with an incorrect timeout value. Even though the incorrect time is shown in the warning, the session is terminated correctly after a forced timeout.

When connected to the NetScaler Gateway, NSGClient adds a space before the following IP address: /etc/hosts file. The customer monitors suspicious entries and removes them. The space before the IP address is considered suspicious and is removed, so NSGClient cannot work.

If the intranet application feature is enabled, the NetScaler Gateway plug-in intermittently takes more than 2 minutes to complete a logout.

If CISCO ACS or any TACACS server is used to authorize command execution for NetScaler, executing lengthy CLI commands (>1460 bytes) results in the following ERROR: "Not authorized to execute this command." This issue occurs most frequently with the "set appfw profile" command, because of the large number of parameters, but it can occur with any lengthy CLI command. Frequently used commands are typically less than 1460 bytes, so the issue does not occur very often.

The client receiver is not sending an authentication cookie back on previously authenticated connection due to this the NetScaler appliance is sending a 403 error to the client.

If Gateway is deployed for a XenMobile use case, the webSSO between AppController and Sharefile fails intermittently due to an incorrect Host header that Gateway sends. As a workaround, a trailing slash (/) needs to be configured in the corresponding wihome configuration.

ClientCertPath is not read when a client uses the GUI to connect to NSGClient. The client certificate is repeatedly requested, even if the GUI is configured to provide it.

When a user in the INTL domain logs on through a NetScaler appliance (a dual factor with RADIUS) by entering only a user name (no domain information on the logon page), the logon fails. However, the same kind of logon attempt by a user in the Corp domain is successful. This behavior is expected. Storefront needs the domain and user-name information from a user in the INTL domain. When entering domain\username format on the NetScaler login page, RADIUS rejects the login, and it does not pass the domain and user-name information to the Storefront server, so the logon fails.

The DNS server fails to resolve internal URLs without an FQDN when using WorxWeb on Android devices.

If Storefront has been configured as WIHome parameter, then accessing the Store Apps in Applications tab in the homepage over Full vpn mode with Windows does not work and an error message "Cannot complete your request" is returned.

Users appear to lose their connections to Storefront. The user has to disconnect and reconnect to the server.

The user's session cookie is no longer accessible to rewrite and other modules. Customers cannot insert the session cookie as an HTTP header and send it to back-end servers. This change provides an alternative way to check for AAA cookie presence by using HTTP.REQ.USER.SESSIONID expression. It results in a non-empty string if an AAA session exists. This is equivalent to checking for a valid AAA cookie.

The clear config function does not clear the default DNS profile or the comand, tm sessionpolicy, from the packet engine. When the bulletins are applied as part of clear config command, the add dns profile and add tm sessionpolicy command fail.

Destination IP based expressions cannot be used for traffic policies that use SecureBrowse and CVPN modes.

If group extraction authentication policies are configured, and the Authentication Subsystem is unexpectedly restarted, the group extraction policies are not sent to the Authentication Subsystem on restart. The group extraction policies won't be evaluated during authentication attempts.

When encryption is enabled for client security expressions (in the VPN session action parameter), the device might fail occasionally.

If the HTTP connection stats are printed from a CPU other than the one from which the session originated, the TCP port for the HTTP traffic sent over the VPN is displayed incorrectly.

Smart access policies based on smart group rules do not work for existing sessions after HA failover, because Smartgroups and externalgroups are not synced to the secondary during session transfer.

After the user name is extracted from a certificate, the UserName field is not grayed out in GUI and is open for editing.

Destination IP based authorization policies do not work as expected in ICA Proxy Mode. Users see authorization failures despite having an authorization policy that allows traffic destined to Storefront server's IP address. As a workaround, Host header based authorization policy or user membership based policies can be used.

If the new session entry points to the same memory that was used for a previous session entry earlier, some of the values have to be reset.

The minimum and maximum value checks for RDP Cookie validity do not work as expected.

If a user on a substandard network launches an RDP Desktop through a NetScaler appliance, the user's screen might not display anything.

Single-sign-on to backend servers through an MPX-FIPS device sometimes fails.

The secondary page for radius authentication does not load the appropriate fonts when using the X1 theme.

If group extraction authentication policies are configured and the Authentication subsystem is unexpectedly restarted, the group extraction policies are not sent to the Authentication subsystem. Therefore, the group extraction policies are not evaluated during authentication attempts.

The EPA plugin window is now at the top of the screen. Its new position facilitates the user-consent step, especially for new users. The change does not affect EPA scanning.

If the client timeout interval is too long (for example, 12 hours), a memory allocation problem results in user disconnections and login failures.

If the network between the RDP client and the NetScaler appliance is substandard, users can get a blank screen when launching a RDP desktop using Netscaler Gateway.

This is a summary of how NS 11.0 behaves on FIPS systems with respect to RADIUS and TACACS policies. RADIUS & TACACS use non-FIPS algorithms which are not permitted if fipsUserMode is ENABLED. The default setting for fipsUserMode is DISABLED.

In 55.x/62.x/63.x GA builds:

- Config behavior: RADIUS & TACACS policies can be created.

- Runtime behavior: Possible system failure if fipsUserMode is ENABLED and a RADIUS or TACACS action is attempted.

In 64.34 GA build, 64.35 LCM build:

- Config behavior: RADIUS & TACACS policies cannot be created.

- Runtime behavior: no system failure.

In 64.36, 65.x GA Build:

- Config behavior: RADIUS & TACACS policies cannot be created if fipsUserMode is ENABLED. If fipsUserMode is DISABLED then RADIUS & TACACS policies can be created.

- Runtime behavior: no system failure.

After the upgrade, a parsing error occurred with packets on the mux channel. Because of the error, a new mux packet was tracked from a wrong offset and caused a failure.

The NetScaler appliance inserts an NS_ESNS cookie for page tracking (for showing a waterfall chart) when AppFlow is enabled. Cookie insertion was controlled by the clientSideMeasurements option in the appflow action in release 10.5, but in release 11.0 the default became to always insert the cookie when appflow is enabled. Android receiver (HTTP client) was not able to handle this cookie. This fix adds the Enable/Disable page tracking (cookie insertion) option to the appflow action.

The packet processing engine fails unexpectedly during an attempt to parse missing content.

Internet Explorer shows signature of file is invalid or corrupt when a user downloads EPA or VPN plugin. Users are advised to use a different browser (like Firefox or Google Chrome) for downloading and installing EPA or VPN plugin. After installation, users can use any browser without issues.

If there are more than 25 records to display in the skip flow window, then only 25 records are displayed as the window does not provide support for pagination.

Web Insight supports content and media type classification reports. Viewing these features are optional similar to the existing HTTP header fields User Agents, Operating Systems, Request Methods etc. You can enable or disable these features from the Configuration section. For media classification and httpContentType Appflow parameter, you must first enable Appflow on virtual server from Insight center configuration.

Insight Center's Web Insight dash board reports the following Media types:

1) Uncategorized

2) FLV F4V Audio

3) FLV F4V Video

4) MP4 M4V Audio

5) MP4 M4V Video

6) GP 3G2 Video

7) ADTS Audio

8) APPLE Video

9) MICROSOFT Video

10) AAC Audio

11) MICROSOFT PLAYLIST Video

12) APPLE PLAYLIST Video

13) MP3 Audio

14) Unknown

The NetScaler Insight Center appliance throws an error when modifying the name of a threshold record. To fix this issue, the name field has been made read-only.

The NetScaler Insight Center appliance might fail and not respond, when you add, update, or delete the private IP address block that is used for geo location.

An exported report displays the time duration as "custom" irrespective of the time duration selected in the report.

If you enable Appflow for ICA and there are a large number of ICA connections which have reconnected after a network disruption, the NetScaler appliance will experience a memory leak.

If you enable the Appflow feature, the NetScaler appliance might become unresponsive while processing ICA connections.

The NetScaler appliance might become unresponsive if Appflow reporting is enabled for ICA traffic and network disruptions occur while the ICA connections are being processed.

The NTP server configuration on NetScaler Insight Center is not propagated to the connector, agent, and database nodes.

Poor performance or latency is observed while accessing published applications over plain ICA port 1494 when AppFlow is enabled. This issue is not observed on ICA over CGP port 2598.

The SNMP daemon runs on NetScaler Insight Center even though NetScaler Insight Center does not support SNMP requests.

If the AppFlow feature is enabled for ICA applications, the NetScaler appliance might become unresponsive when Citrix Receiver performs a session reconnect with a ticket that starts with "NS" and the next two bytes have unrecognizable values.

If a failover occurs in a high availability configuration, an ICA connection that uses Automatic Client Reconnect (ACR) might fail to reconnect.

When Appflow for ICA is enabled, NeScaler can fail if the client reconnects with an invalid ticket and server responds with a CGP BINDRESP followed by some extra data.

When you configure authentication (Configuration > System > Authentication > Authentication Configuration), the Server Name field does not display the selected server.

NetScaler Insight Center does not cache reports after you enable database caching.

In the network panel in the XenDesktop Director GUI, the time slider for selecting the time period for a graph is not properly displayed.

Adding a private IP block in NetScaler Insight Center fails if you select a country name that has special characters.

If the two NetScaler appliances in a double hop deployment are running different NetScaler software editions (Platinum, Enterprise, or Standard), NetScaler Insight Center fails to generate reports for these appliances on the NetScaler Insight Center dashboard.

The NetScaler appliance might sometimes become unresponsive or experience intermittent HA failovers based on a particular ICA network condition.

The NetScaler appliance might become unresponsive if Appflow reporting is enabled for ICA traffic on the NetScaler appliance.

In NetScaler Insight Center, updating fields in a private IP block fails.

The network panel in the XenDesktop Director GUI does not display a graph with the session details when you select another user.

The network panel in the XenDesktop Director GUI displays session details of all users, instead of for just the selected user.

If you use the refresh button, it does not have any effect on the slider. Refresh operation does not have any affect on the time shown in the slider. Also, when you change tabs, it does not impact the slider. You can change the time by changing the time duration.

For some elements on the dashboard, NetScaler Insight Center does not fetch records for the specified time frame.

The network panel in the XenDesktop Director GUI displays the details of all of the administrative user's sessions, instead of just the details for the selected session.

The whitelist of Citrix Receiver versions used by HDX Insight now includes version 13.0.3.265571 of Citrix Receiver for Linux.

If you click on a country in the Geo Maps in the XenDesktop Director GUI, the GEO maps are not displayed.

NetScaler Insight Center restarts intermittently, and HDX insight reports might not show any data.

The network panel in the XenDesktop Director GUI does not display a graph with the session details for the selected user.

NetScaler Insight Center is now supported on KVM hypervisors.

The NetScaler appliance might become unresponsive if you attempt to delete an AppFlow action while the traffic is flowing.

NetScaler Insight Center might intermittently become unresponsive and not populate any reports.

NetScaler Insight Center fails to generate the technical support file, because the namedpipe file causes an error in the creation of the technical support file.

A memory leak occurs when a responder action has blocking expressions (for example, stream analytics, HTTP callout, matches_location) and body or payload based expressions.

After interface reset from management service, L2 mode will stop working for the 10G interface.

Workaround: Disable and re-enable L2 mode from SVM for the VPX.

If you are running a NetScaler SDX 11.0 beta version and upgrade to NetScaler 11.0, then some components may not be upgraded. This does not cause any malfunction in the running of the system. However, the upgrade is incomplete.

Workaround: Reset your appliance to factory defaults and upgrade to the latest 10.5 or 10.1 version and then upgrade the appliance to NetScaler SDX 11.0

You cannot change only the SSLReneg setting from the "Change SSL Settings" option in the configuration utility.

If a 10G interface is a part of the LACP channel, it might incorrectly report stalling of transmission (Tx) on VPX.

Workaround: Reset the 10G interface using the management service.

Citrix User Experience Improvement Program (CUXIP) collects data for the sole purpose of improving the graphical user interface. The collected data is used only by Citrix engineers. It is not shared with anyone.

CUXIP collects the following types of data:

1. Number of clicks by a user

2. Information about the client browser and operating system

For more information, see http://www.citrix.com/community/ux-improvement-program.html

You cannot restore any NetScaler instance from a backup file unless you first upload the XVA files for all of the instances that are included in the backup file.

Performing SNMP walk using the EMC SMART tool is slow.

The management Service does not support provisioning or modifying a NetScaler instance with gateway IP address from a different subnet as that of the NetScaler IP (NSIP) address.

Management Service now supports provisioning or modifying a NetScaler instance with gateway IP address from a different subnet as that of the NetScaler IP Address (NSIP).

The NetScaler SDX appliance displays the "SubSystem Down: svm_service" error message when the Management Service creates multiple SNMP requests at run time to fetch network configuration information from XenServer and Management Service configuration files.

On an SDX appliance, if a NetScaler instance is provisioned with more than 3.5 GB memory,

the state of the interfaces might continuously change between UP and DOWN (flap) when the instance processes traffic.

The warning message before a factory reset does not say anything about the physical connection to the appliance. With this fix, the warning message includes information about the physical connection.

When a user with nsroot or similar privileges modifies a VPX instance that was originally created by a user from admin domain, the modification might fail because of inadequate resources, even though the admin domain has enough resources.

If an nsroot user uses the Management Service to edit the resource attributes of devices, and the resource validation is done from the tenant to which the device belongs, the resource validation fails while validating the CPU cores.

A memory leak in the event subsystem causes all the subsystems in the Management Service virtual instance to go down. As a result, you cannot log onto the SDX appliance through either the GUI or the CLI.

In the SDX GUI, the Management Service virtual instance displays incorrect memory usage information, because it does not consider the inactive memory.

When you remove an admin partition, the NetScaler appliance fails or corrupts an SNMPD packet queue.

High availability (HA) synchronization fails if the NetScaler IP (NSIP) addresses of the nodes in the HA configuration are IPv6 addresses.

ICMPv6 requests with a payload greater than 1232 bytes (fragmented ICMPv6 requests) from a nondefault NetScaler admin partition might not succeed.

A PBR6 rule might not get evaluated if you set the operator option to NEQ (!=) for source and destination IPv6 addresses.

An ACL6 rule might not get evaluated if you set the operator option to NEQ (!=) for source and destination IPv6 addresses.

Duplicate address detection might fail for a global IPv6 address.

In a high availability configuration, when the connection between primary and secondary goes down and comes up again, the secondary node receives HA INIT request from the primary node and it terminates all BGP connections.

You cannot configure INAT46, INAT64, or INAT66 rules by using the configuration utility.

Workaround: Use the command line interface.

The NetScaler appliance might assign the NTP module a port that is used by some other feature module. Therefore, an incoming NTP response can be processed by the feature module. This can result in the failure of the NetScaler appliance.

The output of the show ACL does not display the correct hits for ICMP packets that match the ACL rules.

On a NetScaler appliance with a NetScaler owned IP address configured with a VMAC address on a traffic domain, when a peer device sends an ARP request with unicast MAC for this IP address, the NetScaler appliance responds with the physical MAC address instead of the VMAC address. As a result, the NetScaler appliance drops packets forwarded by the peer device if the packets are destined to the physical MAC address for that IP address.

In a high availability configuration, when the connection between primary and secondary goes down and comes up again, the secondary node receives HA INIT request from the primary node and it terminates all BGP connections.

A NetScaler appliance might consume a high percentage of CPU cycles, because the appliance repeatedly updates the active connections with changes in MAC addresses of servers.

The configuration utility does not display any route monitors configured on the NetScaler appliance.

If a connection matches a RNAT rule, the NetScaler appliance probes for the existence of the destination server before processing the connection based on the RNAT rule. The connection that is used for probing is sometimes left idle on the appliance and a new connection is opened once the client connection is successfully established. This probe connection stays idle for the configured idle timeout (2.5 hours) thus holding up resources on the server.

Now, these probe connections are flushed within a minute if they remain idle.

Binding a redundant interface set (for example, LR/1) to NSVLAN might cause the NetScaler appliance to become unresponsive.

For extended ACL rules that are associated in NAT configurations (for example, RNAT rules, Large Scale NAT configurations), the configuration utility displays the TCP established parameter as enabled for these ACL rules.

The NetScaler appliance might erroneously forward DHCP broadcast packets to the default router. As a result, the broadcast packets go in loops between the appliance and the router.

In an IPSec tunnel, the NetScaler appliance might remove sessions between client and server before encrypting (IPSec) DNS response packets, resulting in the loss of these DNS packets in the tunnel.

On a NetScaler appliance with a forwarding session rule configured and connection failover enabled, the appliance might become unresponsive when processing packets that match the forwarding session rule.

Workaround: Create a dummy load balancing virtual server with stateful connection failover enabled.

You cannot securely access (HTTPS) the NetScaler GUI by using a subnet IP (SNIP) address that is configured on a traffic domain.

For a sessionless virtual server configuration, the NetScaler appliance might forward packets for an incoming connection without changing their source MAC address with the MAC address of one of its interfaces. As a result, the connection fails.

The NetScaler appliance fails when it processes invalid UDP packets received at port 500 or port 4500.

FTP in passive mode does not work in this build.

For backend TCP connections, a NetScaler appliance might allocate the subnet IP address and port of an active connection to a new connection. As a result, the new TCP connection fails.

The dynamic routing module on a NetScaler appliance might incorrectly save the command "redistribute intranet" as "redistribute trill" in the ZebOS configuration file. Because the appliance does not support the "redistribute trill" command, after a failover in a high availability setup, the new primary node treats the "redistribute trill" command as an error and does not apply the subsequent commands in the ZebOS configuration file. This results in loss of configuration.

For extended ACL rules that are associated in NAT configurations (for example, RNAT rules, Large Scale NAT configurations), the configuration utility displays the TCP established parameter as enabled for these ACL rules.

After the clear config operation, reconfiguring a VXLAN entity fails to retrieve the VXLAN SNMP counters.

A clear config operation does not remove VXLANS. The configuration utility and the CLI continue to show the VXLANs, but with incorrect IDs.

On a NetScaler appliance, connections might get reset between routing processes. As a result, the dynamic routes are occasionally deleted and added back.

In a GSLB deployment of NetScaler appliances configured with OSPF routing protocol, the OSPF process running in one of the NetScaler appliances sources OSPF hello packets from the GSLB site IP address configured on the appliance. As a result, neighbour adjacency does not get established.

Forwarding sessions do no work as expected with bridge groups, because packets are not forwarded to the correct VLAN.

If an IPv6 virtual server with persistency enabled is removed from a traffic domain, the traffic domain information for the existing persistency sessions is lost, and the NetScaler appliance hosting the virtual server becomes unresponsive.

A customer using the NetScaler Gateway wizard to configure Storefront through "XenApp and Xen Desktop" might get Invalid Argument error messages.

Enabling the media classification feature causes the NetScaler appliance to become unresponsive.

A NetScaler appliance crashes when Media classification mode is enabled and HTTP request of bigger URLs are received.

NetScaler VPX instances, running on SDX 22040/22060/22080/22100/22120 and SDX 24100/24150 appliances, fail to start after you upgrade to the NetScaler SDX release 11 single bundle image. Starting the NetScaler instances manually also fails.

Workaround: Delete the VPX instances and provision them again by using the Management Service.

The memory usage statistic shown on the LCD display of a NetScaler appliance is the allocated memory. The NetScaler configuration utility displays the currently used memory. Therefore, the two values are different.

The LOM firmware on NetScaler MPX 11500/13500/14500/16500/18500/20500 and MPX 11515/11520/11530/11540/11542 appliances can report VTT sensor data, but the NetScaler appliance does not support it.

OpenSSL libraries are now integrated to operate in the FIPS mode.

The RAID controller is frequently reset. With this fix the, RAID controller's driver has been modified and the firmware upgraded to version 23.33.0-0023. The frequent resets no longer occur.

The NetScaler appliance fails to respond when a blocking log action is configured with a responder action.

Some IP based expressions might not work for IP addresses starting from octet 128 or greater (128.x.x.x - 254.x.x.x).

The following expressions are not impacted:

- EQ, IN_SUBNET, IS_IPV6, GET1, GET2, GET3, GET4, MATCHES, MATCHES_LOCATION, APPEND, TYPECAST_TEXT_T, TYPECAST_IPv6_ADDRESS_AT

The following expressions do not work:

GT, GE, LT, LE, BETWEEN, NE, ADD, SUB, MUL, DIV, MOD, NEG, BITAND, BITOR, BITXOR, BITNEG, LSHIFT, RSHIFT, TYPECAST_TIME_AT, TYPECAST_IP_ADDRESS_AT, TYPECAST_DOUBLE_AT, TYPECAST_UNSIGNED_LONG_AT, WEEKDAY_STRING, WEEKDAY_STRING_SHORT, SIGNED8_STRING, UNSIGNED8_STRING, SIGNED16_STRING, UNSIGNED16_STRING, SIGNED32_STRING

An HTTP callout that is configured for use with a virtual server does not work with a backup virtual server (if configured).

If packet tracing is configured with a default-syntax expression and non-TCP traffic is being processed, and rewrite action applied on a HTTP chunked message is occurring then the rewritten data maybe incorrect or it might crash a NetScaler appliance.

Workaround: Configure the packet tracing filter expression with a Classic syntax expression or avoid using filter expression.

The default timeouts for Rewrite Processing and for Advanced Expression Regex Evaluation have changed from 1 millisecond to less than the pitboss timeout of 5 seconds. This restores the default behavior for releases prior to 11.0. In addition, an optional -timeout parameter to "set the re-write param " CLI command was added. The time is measured in milliseconds - see the man page. A "set policy param -timeout &lt;value>" command has been added to the CLI. These ways of setting the timeout work for all partitions.

In release 11.0, the default timeouts for Rewrite Processing and for Advanced Expression Regex Evaluation have also changed from 1 millisecond to less than the pitboss timeout. This restores the default behavior from releases prior to 11.0. However, neither the CLI command, nor the GUI, nor the Nitro call is available. Instead, for 11.0, an nsapimgr command is available from the shell. This will only change the timeout on the default partition when Partitioning is used. Other partitions will only use the default. The syntax is as follows: "nsapimgr_wr.sh -ys arg1=&lt;value> -ys call=ns_pixl_regex_set_time_limit" to set the time limit on regular expression evaluation in Advanced expressions. "nsapimgr_wr.sh -ys arg1=&lt;value> -ys call=ns_rw_set_eval_time_limit" to set the time limit on Rewrite processing. For either of these, setting the value to 0 resets the limit to the default. These nsapimgr commands will not be supported after 11.0, and the CLI, GUI, or Nitro must be used.

Rewrite action block leading to subsequent action time outs.

If multiple rewrite policies evaluate to TRUE for a particular protocol and direction (for example HTTP request or TCP response), and more than one associated action is selected for execution, they might not all execute. If one of the actions is suspended (blocked), the next selected action will time out, and any subsequent actions will be skipped.

The following functions in expressions can block:

* HTTP_CALLOUT

* MATCHES_LOCATION

* STREAM

* CHECK_LIMIT

* MATCHES

* BODY

* PAYLOAD

* MSSQL

* MYSQL

* ORACLE

* SUBSCRIBER

* DETERMINE_SERVICES

* use of variables (in other words, $<variableName>)

Note: These expressions can block, depending on specific conditions that occur at the time of execution.

Under certain conditions, a NetScaler appliance does not insert an X-Forwarded-For field in the HTTP header for HTTP CONNECT requests that are forwarded to server.

The NetScaler appliance fails if it receives a new request while an embedded expression in the responder HTML page is in blocking state.

On a NetScaler MPX appliance, AES-GCM/SHA2 ciphers are supported only on the front end SSL entities.

You cannot enable TLSv1.1/1.2 on a front end SSL service after explicitly disabling it.

An incoming SSL record that spans more than 256 TCP packets and contains TCP header options causes memory corruption in the Cavium command buffer structure. As a result, the NetScaler appliance fails.

If you have a large number of SSL services (greater than 3000) in the backend, CPU usage increases exponentially and the appliance fails.

If you have configured optional client-certificate authentication and your policies target client certificate x509 extensions, such as auth keyid, a transaction with a client that doesn't have a certificate might cause the appliance to fail or to use stale values from a previous transaction.

In some cases, when client authentication is enabled, incorrect data form a client leads to a memory leak on the NetScaler appliance. If a large number of clients send incorrect data, the appliance fails.

If you use the "add ssl certkey" command to add an encrypted .pfx file, the password is now encrypted and saved in the configuration file (ns.conf). In earlier releases, the password was not saved, so automatic execution of the add ssl certkey command failed when the appliance was restarted.

If you downgrade the software on your NetScaler appliance that does not have a license to release 9.3 build 61.66 or earlier, some commands related to the default server certificate might not be saved in the running configuration. As a result, after restarting, secure access (HTTPS) to the appliance fails.

If you update the certificate-key pair for a service group, the change is not reflected in the individual services that are bound to this service group. As a result, the old certificate-key pair continues to be used for negotiation in the SSL handshake.

If TLS1.1/1.2 protocol is used with AES/3DES ciphers, the length of the TCP window at the back end shrinks to zero. As a result, after some time, the connection is terminated.

If TLS1.1/1.2 protocol is used with AES/3DES ciphers, the length of the TCP window at the back end shrinks to zero. As a result, after some time, the connection is terminated.

In release 10.5 or later, TLS protocol versions 1.1 and 1.2 are enabled by default, but you can disable them for all services except SSL_BRIDGE and dynamic services, which can't otherwise be configured. In this release, you can disable TLS1.1/1.2 on SSL_BRIDGE and dynamic services by enabling the new svctls1112disable and montls1112disable parameters, as follows:

> set ssl param -svctls1112disable enable -montls1112disable enable

After the new parameters are enabled, you cannot disable them by using the "set ssl param" command. You must edit the configuration (ns.conf) file as follows:

1. Remove these parameters from the "set ssl param" command.

2. Save the configuration.

3. Restart the appliance.

NetScaler VPX virtual appliances do not support AES-GCM/SHA2 ciphers, but in earlier builds you can bind these ciphers, incorrectly, to an SSL virtual server. From the current build, you cannot bind these ciphers to the virtual server. If you have bound AES-GCM/SHA2 ciphers to a VPX instance that you upgrade to the current build, the bind commands in the configuration return an error. In a comparison of the configurations of the old and new build, the missing bindings can be mistakenly construed as a configuration loss.

Even though SSL renegotiation is set to deny (that is, denySSLReneg is set to ALL), the server responds with the "server reneg" extension in the initial SSL handshake.

If you restart a NetScaler appliance that has FIPS firmware version 2.2, the FIPS key might be temporarily unavailable.

If the passphrase for a certificate contains the "$" character, the configuration utility becomes unresponsive.

In the OpenSSL interface in the NetScaler configuration utility, if you type a command before the OpenSSL> prompt appears, the OpenSSL> prompt might not appear at all. As a result, any commands that you type are not run in OpenSSL mode.

If you enable the DH parameter while creating an SSL profile by using the configuration utility, the following error message appears:

Error in retrieving File. Invalid args in query parameters

If you have configured optional client-certificate authentication and your policies target client certificate x509 extensions, such as auth keyid, a transaction with a client that doesn't have a certificate might cause the appliance to fail or to use stale values from a previous transaction.

If you bind a secure monitor to a service, such as SSL_BRIDGE, that does not allow SSL configuration, the default settings are used. The default SSL version sent in the SSL handshake record header is SSLv3.

Contact Citrix support if you want to disable SSLv3 and use the next higher protocol.

If you upgrade the FIPS firmware on your appliance to version 2.2 and then restart it, you might notice some loss in the configuration.

If you are running FIPS firmware 2.2 on your appliance, some commands might fail after 9 days.

An MPX-FIPS appliance might not restart if you attempt a warm reboot.

On an MPX-FIPS platform running firmware version 2.2, if you have configured SSL services at the back end, an attempt to download a file fails if its size is greater than 16KB.

The NetScaler appliance fails if it parses the value of an unknown certificate extension while the certificate is loading.

When clearing the NetScaler configuration, user-defined cipher groups that are bound to an internal SSL service might get corrupted. Subsequent cipher bind or unbind operations with that service will cause the appliance to become unresponsive.

You cannot install a certificate on the appliance if the certificate is not in the /nsconfig/ssl directory. With this fix, you can install a certificate in the appliance's default partition from any location. For other partitions, the certificate must be in the /nsconfig/partitions/ssl/ directory.

The option to set the transport type has been removed from the SET and UNSET operations. You can specify the transport type while adding a Syslog action. In a Syslog action, by default the transport type is set as UDP.

Note: Once you have set the transport type in a Syslog action, you cannot change the transport type.

The upgrade wizard in the configuration utility puts the NetScaler software in the /var directory instead of the /var/nsinstall/<build id> directory.

On rebooting the NetScaler appliance, the timeout is not set to the value specified by the "set ns timeout" command.

If you execute NTP commands, such as enable ntp sync and show ntp status, the NetScaler appliance might become unresponsive because of a memory leak.

If a NetScaler appliance that is sending auditlog messages over TCP (audit syslogaction specifies TCP as the transport protocol) has more than 200 million active sessions, the rate at which the syslogs are sent drops to 700 Kbps or lower, and the appliance consumes a high percentage of the CPU cycles.

In a high availability setup, if stateful connection failover is configured on a virtual server that has been serving traffic for some time, running the "clear config extended" command results in a warm restart on both the primary and secondary appliances. Unsetting connection failover on the virtual server results is a warm restart on only the secondary appliance.

For a NetScaler appliance with extended memory configured for Large Scale NAT (LSN) feature, after warm rebooting the appliance, when the appliance is added as secondary node to an appliance that does not have the extended memory configured for LSN, the secondary appliance becomes unresponsive.

After cleaning up an MPTCP session, the NetScaler appliance might not set the DATA_FIN flag in the TCP header of the data or acknowledgement packet if there is no subflow for sending the data.

The NetScaler appliance might become unresponsive if it receives a retransmitted TCP jumbo frame that carries the TCP FIN flag.

The NetScaler appliance might become unresponsive if front end optimization (FEO) is enabled with the SSL and rewrite features.

When SPDY Protocol is enabled and SPDY Traffic is received on the NetScaler appliance, the TCP current clients counter goes to negative values and shows a very large value in the stat or the SNMP OID.

Management CPU usage is high when you use the configuration utility's memory usage diagnostic tool (System > Diagnostics > Memory usage).).

In NetScaler Insight Center, NetScaler 1000V, and NetScaler VPX on ESX, the Vmtoolsd daemon fails during start up and creates a core dump in the directory /var/core. It does not affect normal VPX functionality. However, operations such as "Shut Down Guest" and "Restart Guest" from the vSphere client summary tab fail.

If a server advertises a maximum segment size (MSS) greater than 1460 bytes, a TCP transaction might not generate a response after passing through the NetScaler appliance.

In certain cases, the NetScaler appliance might not retransmit the lost TCP segments resulting in a transaction failure.

Failed SNMP requests were not removed properly, therefore, subsequent set requests were retained in the queue. This lead to all SNMP requests getting blocked and high memory usage, due to which the SNMP module stops responding.

In a HA setup, if a domain-based SNMP manager is added on the secondary appliance, the NetScaler appliance stops responding eventually. You must configure the SNMP manager on the primary appliance.

For a NetScaler appliance with extended memory configured for Large Scale NAT (LSN) feature, after warm rebooting the appliance, when the appliance is added as secondary node to an appliance that does not have the extended memory configured for LSN, the secondary appliance becomes unresponsive.

A NetScaler appliance might occasionally fail when a client connects to an HTTP/SSL server and the server sends a 101 (switching protocols) response. The connection is closed before data can be sent or received from the client.

When the NetScaler appliance receives MPTCP traffic, the number of established client connections is high, because both MPTCP sessions and subflows are treated as client connections.

With this fix, the SNMP OID of following MIBs have changed to:

mptcpCurSessWithoutSFs: 130

vsvrCurMptcpSessions: 73

vsvrCursubflowConn: 74

When adding a syslog action for which the netProfile parameter is set, the Subnet IP (SNIP) address is used as the source IP address for sending log messages. If the netProfile parameter is not set, the NetScalerIP (NSIP) address is used as the source IP for sending the log messages.

The appliance might fail under the following set of conditions:

1. A pipelined HTTP request is received that spans multiple TCP segments.

2. An internal HTTP response generated by NetScaler for the HTTP request in condition 1, is terminated by a TCP segment that has the TCP FIN flag set.

3. The appliance receives another HTTP request on the same connection.

If the NetScaler appliance receives a data or an acknowledgement packet without the Data Sequence Signal (DSS) option before the MPTCP connection is established, the appliance does not seamlessly fallback to regular TCP.

A Netscaler appliance has high memory consumption if Front End Optimization (FEO) feature is enabled.

Work around: Disable the feature or reboot the appliance.

When parsing a host name with no Path component, the URL parsing logic does not search for a question mark (?), so an entire string might be interpreted as the host name. This causes an error when the appliance tries to resolve the DNS name. With this fix, the parsing logic searches for question marks.

Eg: http://example.com.php?&curuserid=94315577&host=wscdny203.live.changba.com&token=T59d105c1c74042e&localip=221.235.187.75&clientip=80.95.239.1&bless=1&channelsrc=market_%E7%99%BE%E5%BA%A6

Some events may be logged twice if DEBUG level is enabled for syslog, by using the "set audit syslogParam" command.

The NetScaler appliance does not reduce the received Maximum Segment Size (MSS) to accommodate TCP options (such as timestamps). Therefore, the NIC drops such packets.

Syslog messages generated by user action are logged as error messages instead of informational messages.

If weblog data is sent over a TCP connection that the NetScaler appliance has terminated because of buffer overflow, the appliance fails. With the fix, the connection is checked to ensure that it is not closed before the weblog data is sent.

After you upgrade a Netscaler appliance to 10.5 build, the Client-Server Link Mapping check box is now available in the TCP Connections page

A NetScaler appliance might crash if you attempt to start the nstrace instance with advanced filter expression.

A NetScaler appliance does not support Base64 decoded TASS cookie IDs of more than 64 characters. If Security Assertion Markup Language (SAML) or federation results in an ID longer than 64 characters, the appliance does not support the cookie ID.

A configuration loss occurs when you upgrade Content Switching (CS) entities above the following limits:

Memory allotted to a packet engine 2GB 4GB

Max number of content switching virtual servers 1200 2500

Max number of content switching policies 1500 3500

Max number of content switching virtual server bindings 3000 4000

Commands entered in the NetScaler CLI or GUI might fail because of a shortage of system resources or failure of system socket connections.

With this fix, the NetScaler appliance attempts to reestablish the socket connections. After the socket connections are established, the appliance runs the failed commands internally.

The NetScaler Weblog client intermittently fails because of incorrect indexing, leading to segmentation failure

If, when processing a URL, the parser encounters a tag that has "#"as a source attribute, the URL is considered to be empty as # is a fragment identifier. This leads to corrupted values because we continue processing the empty URL.

You can now use a remotely saved backup to restore a NetScaler appliance through the "add system backup <filename>", that adds the metadata to the remote backup package, so that the restore operation can successfully use the backup package.

A NetScaler appliance might fail because of a segmentation fault if it receives a large HTTP/2 request Header that evicts the dynamic header table entry.

A NetScaler appliance fails when it receives an MP_CAPABLE final acknowledgement in a single packet with the FIN flag set.

With the default TCP congestion control, a NetScaler appliance recovering from packet loss reduces the congestion window to half its previous length. With multiple packet loss events, the congestion window becomes small and delays transactions.

A T1200 appliance that is used in a NetScaler deployment can become unresponsive or fail when generating the NetScaler tech support logs.

Management access to the NetScaler appliance can slow down or become unavailable when the traffic domain identifier is not initialized for jumbo frames. However, virtual servers continue to serve traffic.

A NetScaler appliance fails when it encounters an HTTP/2 connection level error on a TCP connection.

In certain cases, the NetScaler appliance might not retransmit the lost TCP segments resulting in a transaction failure.

When a NetScaler appliance is integrated with ESP or VPX devices functioning as E100 devices, it encounters buffer-allocation failure and packet-reception failure.

A NetScaler appliance becomes unresponsive when passing an HTML response with the HTML tag exceeding 16 characters.

In a high availability setup with stateful connection failover option enabled on a virtual sever, if a network link that is used for synchronizing connection information between the nodes becomes DOWN.

Both nodes take a lot a time to reestablish connection information synchronization through the remaining active links, as a result some connection information might not get synchronize to the secondary node.

You cannot shut down or restart the virtual machine by using the VMware vSphere tool.

A warning error message "Error =80000004 in nsagg_process_stat_request, closing connection" displays when a nscollect module requests counter information from a nsagregator daemon at every 5 minute interval. The nsaggregator daemon prints the warning message as response to the request received from nscollect module for more than 256 counters.

If, when establishing an MPTCP connection, a NetScaler appliance receives a duplicate acknowledgment in the 3-way handshake process, the appliance reverts to a normal TCP connection.

Client-based virtual machines are unable to access a NetScaler appliance if they are running on the same server (for example, VPX on Linux KVM). However, they are accessible if they are running on different servers.

Due to a bug in Hard Disk Drive (HDD) monitoring logic, if a message in /var/log/messages matches "*ad* Device not configured" string pattern, it results in producing false positive errors.

A NetScaler appliance fails when an MPTCP subflow receives an Infinite DSS mapping in a partially retransmitted packet.

After a failover occurs in a high availability configuration, some LSN static maps might become inactive on the new secondary node.

Workaround: Delete the LSN static maps on the primary node and then add them again.

In a network setup that includes both dynamic and deterministic types of clients, the first request from a deterministic client is not served if a dynamic client has sent a request.

SIP registration might fail, if authentication is enabled in the SIP proxy server.

In a high availability deployment with LSN and DS-Lite configuration, LSN and DS-Lite mappings for active FTP connections are not removed from the secondary node even after they time out or are flushed.

With a large number of active subscribers, and a high traffic rate for SIP over TCP, the NetScaler appliance can fail during ALG processing.

The default expression to route Unified Gateway VPN traffic does not include all of the necessary expressions which can cause a Receiver connection failure.

Work Around

The remedy is to create a compound expression using "is_vpn_url" along with "Citrix/Roaming/Accounts" to match the addition target URL: add cs policy <policy name> -rule "is_vpn_url || HTTP.REQ.URL.STARTSWITH(\"/Citrix/Roaming/Accounts\")" -action <gateway vserver>

After upgrading to nswi-1.8.tgz, existing WI sites are not accessible till you remove the sites and then add them back.

WIonNS v1.7 does not work when WebFront is installed.

Workaround: Upgrade to WIonNS v1.8.