Product Documentation

Known Issues and Workarounds

May 15, 2015

The issues that exist in Build 7.4.

Advanced Optimization

  • Issue 549038: ICA sessions may fail to start if the datacenter includes a NetScaler appliance running in transparent mode with a build lower than and the deployment includes CloudBridge appliances running release 7.4.0. With Connection Chaining Enabled.

    Workaround: Upgrade the NetScaler to Build for CB 7.4 GA Build is or above. Or Disable Connection Chaining in NS and CB

  • Issue ID 543262: CloudBridge ICA acceleration is not compatible with releases prior to 7.3.1 by default. Accelerated ICA connections with partner appliances using releases prior to 7.3.1 will fail.

    Workaround: Either upgrade all older boxes to release 7.3.1 or above, or, on all appliances running 7.3.1 and above, set the parameter ICA.SupportCbUnawareClientServer to Off, using the Tuning page's General Parameters feature.

  • Issue ID 485986: The appliance sometimes becomes unresponsive after the user enables video caching, or when an appliance with video caching enabled is updated to a new release.

    Workaround: Reboot the appliance.

  • Issue ID 513139: If you delete the ALTHTTP application classifier, Receiver for HTML5 traffic will no longer be parsed. If you recreate the ALTHTTP classifier, it still will not parse the Receiver for HTML5 traffic.

    Workaround: Add port 8008 to the HTTP application classifier.

  • Issue ID 505623: Automatic client reconnection is not implemented with Citrix Receiver for HTML5. Hence, disabling acceleration on a CloudBridge appliance can disconnect existing Receiver for HTML5 sessions.


  • Issue ID 502854: In a XenApp and XenDesktop environment, if you add port 8008 to the Video Caching port list, clients fail to start HTML5 XenApp-hosted applications or XenDesktop-hosted desktops .

    Workaround: Create an exclude video source entry for the VDA subnet IP address. This prevents the appliance from proxying connections destined for the VDA subnet.


  • Issue 546885. Under some circumstances, secure acceleration performance may be up to 25% slower than with previous releases.

Configuration and Reporting

  • Issue ID 480374: (CloudBridge 4000/5000) Do not attempt to upgrade the software by using the "Upgrade software" mechanism before provisioning the appliance. Use the documented procedure, which involves updating the management service to release 7.4.0 first.

  • Issue ID 558463: After making any change to Network Adapter page, the GUI prompts for rebooting the appliance. Sometimes, after rebooting the appliance, the GUI reports that it is failing multiple times to connect to appliance. In fact, the appliance is up and the GUI is accessible.

    Workaround: Refresh the page in your browser.

  • Issue ID 558462: On the Network Adapters > Interfaces page, resetting a 1 Gbps Ethernet interface fails to reset the interface to its default (Auto) speed/duplex settings.

    Workaround: Manually set the interface to Auto.

  • Issue ID 284137, 302326, 368560, 422659, 447895: (CloudBridge 4000/5000). Detailed connection information is missing.

  • Issue 503925: New time presets for Russian time-zones are not available on CloudBridge Advanced platforms.

  • Issue ID 547672: If you add an initial certificate/key pair inside the Secure Peering Certificates and Keys section of the Secure Peering page, it is not displayed or selectable on the Certificate/Key Pair Name menu.

    Workaround: Add the certificate/key pair on the Secure Acceleration: Certificate and Keys page first.


  • Issue ID 562816: The Citrix eDocs documentation for this release was not complete at the time of release, and largely consists of the 7.3 documentation.

  • Issue ID 552919, 552920: The help icon (a question mark in a circle) takes the user to help topics for the NetScaler SDX rather than CloudBridge.

    Workaround: See Citrix eDocs online documentation for the desired information.

Installation and Upgrade

  • Issue ID 477773: CloudBridge 4000 or 5000 installation issues might arise if two or more CloudBridge 4000 or 5000 appliances are connected to the same broadcast domain.

  • Issue ID 419760: The accelerator's signaling IP address cannot be changed from the GUI of a CloudBridge 4000 or 5000 appliance.


    To change Signaling IP address:

    1. Log on to the NetScaler instance's GUI.

    2. Navigate to Configuration > Load Balancing > Virtual Servers > BR_LB_VIP_SIG.

    3. Modify the signaling IP address.

NetScaler Insight Center

  • Issue ID 500819: If you have already added a maximum number of four AppFlow collectors on a CloudBridge appliance, adding another collector by using NetScaler Insight Center will display an error, but Insight Center will continue to list the CloudBridge appliance in its list of added devices, and will not collect any AppFlow records from the CloudBridge appliance.

  • Issue ID 561139: (AppFlow) If you define an application in the CloudBridge application classifier that contains a colon (":") in the name, it will not be exported correctly to the AppFlow collector.

  • Issue ID 553170: The NetScaler Insight Center dashboard displays the WAN latency value as zero until the CloudBridge appliance acquires a number of traffic samples.

  • Issue ID 549679: If NetScaler Insight Center does not get a connection closure update for a particular connection ID, and the ID is reused, the IP data of the previous connection may be displayed.

  • Issue ID 549601: If a CloudBridge session is inactive, the WAN Insight node of NetScaler Insight Center continues to display older data.

    Workaround: Disable Database Cache Settings

    1. On the Configuration tab, in the navigation pane, click the System and in the right pane click Change Database Cache Settings.

    2. To clear the cache, select Reset Database Cache .

    3. To enable the cache, select Enable Database Cache.

    4. Click OK.

  • Issue ID 538570: The NetScaler Insight Center dashboard displays the server IP address as on all HDX Insight network topology diagrams.

  • Issue ID 533063: On the NetScaler Insight Center dashboard, the latency values displayed on the graph and the network topology diagram might not match due to time synchronization issues.


  • Issue ID 487997: After a high availability failover in a group mode topology, group mode might not be enabled.

    Workaround: Disable and enable group mode after the high availability failover.

  • Issue ID 552529: (CloudBridge 4000/5000) Internal signalling IP 169.254.x.x subnet is displayed in the CB monitoring connections page and the same is reported to Appflow connectors

  • Issue ID 539849: WCCP-GRE multicast routing does not work on appliances with a management service unless the "WCCP and Virtual Inline In-Band Management traffic support" option is enabled on the Tuning page.

  • Issue ID 525815: When you access a published application, the Insight Application Report will show multiple instances of the application if the application launches multiple connections (for example, Google Chrome.)

  • Issue ID 550723: Connections in the reverse direction (initiated in the datacenter) do not show an accurate WAN latency in NetScaler Insight Center.


  • Issue ID 539907: On a CloudBridge appliance in transparent mode, when CloudBridge Plug-in Exclude acceleration rules specified a port number (or range), the acceleration rules are parsed as if the port had not been specified. In redirector mode, the port specification is honored.


  • Issue ID 557747: (CloudBridge 4000/500) When updating an already-provisioned appliance from an old release, such as 6.2, the update may fail with a "Failed to upgrade CloudBridge Accelerator, Instance x.x.x.x is DOWN" message.

    Workaround: Restore the admin account password to the factory default (nsroot) and restart the update. Alternatively, perform a factory reset and then update using the procedure for release 7.1 and up, which will replace your existing configuration with the factory defaults for the current release, giving you a fully modern configuration.

  • Issue ID 547960: If you are using the Private CA feature, deleting either the CA or the Certificate-key pair (but not both) from that feature will prevent you from re-enabling it.

    Workaround: Delete both the CA and the certificate-key pair, then re-enable secure peering in Private CA mode. This will recreate the credentials.