Citrix Branch Repeater 6.2.2

Written by Thomas Poppelgaard. Posted in Branch Repeater, Citrix

Citrix have released a new version of Citrix Branch Repeater. 6.2.2 is an maintenance release for 6.2.

This release is compatible with partner appliances running previous Branch Repeater releases 5.0 and later, and Citrix Branch Repeater with Windows Server releases 2.0 and later. It can be used in a mixed environment that includes units running these older releases.

New in This Release

Two New Hardware Platforms—CloudBridge 2000 and CloudBridge 3000

  • The Citrix CloudBridge 2000 and 3000 hardware platforms are 1U accelerators for use in datacenters and larger branch offices. These platforms offer a wide range of features, communication ports, and processing capacities. Both the platforms have multicore processors.
  • The CloudBridge 2000 can be thought of as a faster Repeater 8500 with two accelerated bridges, while the CloudBridge 3000 can be thought of as a faster Repeater 8800 with three accelerated bridges.
  • New management GUI for the above platforms.

Source

Release documentations

Download Appliance software upgrade 6.2.2 here (Require MyCitrix ID)

Citrix Branch Repeater 6.2

Written by Thomas Poppelgaard. Posted in Branch Repeater, Citrix, Hyper-V, Microsoft, VMware, vSphere, XenServer

Citrix have released a new version of Branch Repeater 5.7.4 (Appliance, Software, Plugins)

New enhancements in 6.2

The following enhancements are available in release 6.2.

  • Repeater, Branch Repeater, Branch Repeater VPX, and Repeater Plug-in In general, use the Branch Repeater Family User’s Guide, Release 6.0-6.2, for this release, at http://support.citrix.com/article/CTX134093.
    Additionally, a new page has been added to the GUI, Monitoring: Server Load Indicator. This page shows the appliance’s overall load, LAN packet and data rates, and input queue latency, which can be useful in determining whether the appliance is lightly or heavily loaded.
  • Repeater 310 for NetScaler SDX Repeater 310 for NetScaler SDX is a new member of the product line that supports WAN speeds of up to 310 Mbps. It shares the hardware platform of the newest Repeater 500/1000 for NetScaler SDX appliances and can be converted through a license upgrade into a Repeater 500 or 1000 for NetScaler SDX.
  • Hardware Changes on Repeater 310/500/1000 for NetScaler SDX The hardware platform for Repeater 310/500/1000 for NetScaler SDX has been upgraded to support network bypassing on most of the Gigabit Ethernet ports. This changes the front panel of the appliances, as shown below. Other than changes on the front-panel Ethernet ports, the appliance remains the same.
  • Branch Repeater now supports the none encryption level when configured on XenApp or XenDesktop.
  • Hardware Bypassing on Older Units
    1. All Repeater 1500/2000 for NetScaler SDX appliances include network bypassing hardware.
    2. Only Repeater 310/500/1000 for NetScaler SDX appliances that are shipped from the factory with release 6.2 include network bypassing hardware.
  • Enabling WCCP SupportWCCP support on Repeater SDX is shared between the NetScaler instance and the Repeater. The NetScaler instance offloads GRE encapsulation/decapsulation from the Repeater. The NetScaler instance also performs NAT between the router and the Repeater, since the Repeater instances are on a different subnet from the router, and NAT is required to allow WCCP-L2 support. On Repeater, WCCP support is enabled as usual, with the following exceptions and limitations:
    1. The NAT address used by the router for the UDP-level WCCP control channel must be specified, along with its subnet size. For example, if the router communicates with the Repeater on address 10.11.12.13/24, the “NetScaler WCCP VIP Address” field on the Configuration: Advanced Deployments page must be set to 10.11.12.13, and the “VIP Network Prefix” field must be set to 24.
    2. Multicast WCCP is not supported.
    3. The WCCP status page does not show packet counts.
    4. The WCCP forward and return methods must match for a given router, with both being L2 or both being GRE.
    5. Load-balancing involving multiple routers will not work properly. Repeater SDX will unbalance or drop such traffic. On the NetScaler instance, contact your Citrix representative for configuration support.
  • Support for L2 forwarding within Repeater SDX, in addition to L3 routing.
  • Traffic shaping is now supported on Repeater SDX A single traffic-shaping engine handles traffic shaping for all the Repeater instances. This traffic shaper performs the same tasks as in other Repeater appliances, and is configured in the same way, but operates in the sending direction only.
  • Citrix Branch Repeater with Windows Server Previously, Citrix Branch Repeater with Windows Server (CBRwWS) was not supported on release 6.x. With Release 6.2, CBRwWS has the same feature set as other Citrix appliances.
    See the Citrix Branch Repeater with Windows Server User’s Guide, Release 2.0-3.0, at http://kb.citrite.net/article/CTX126635 for installation instructions and other platform-specific information.
    See the Branch Repeater Family User’s Guide, Release 6.0-6.1, at http://support.citrix.com/article/CTX134093, for the acceleration features of this release.
  • Group mode is no longer supported for CBRwWS appliances.

Supported Branch Repeater VPX Configurations

Release 6.2 is supported on Branch Repeater VPX running on XenServer, VMware vSphere, and Microsoft-Hyper-V hypervisors. See the following table for the versions of hypervisor that are supported.

Table 1-4. Hypervisors compatible with Branch Repeater VPX

Citrix XenServer XenServer 6.02/Hotfix 602E007,
XenServer 5.6.0 (but not 5.6 FP1 or 5.6 SP2), XenServer 5.5
VMware Vsphere ESXi 5.0, ESX/ESXi 4.1
Microsoft Hyper-V Hyper-V under Windows 2008 R2 SP1

Source

Download Citrix Branch Repeater 6.2 (appliance, software and plug-in components) here
(Require MyCitrix ID)

Citrix Branch Repeater 6.1.2 (15)

Written by Thomas Poppelgaard. Posted in Branch Repeater, Citrix, HDX

Citrix have released a new version of Citrix Branch Repeater 6.1.2 (15)

Issues Resolved in Release 6.1.2

  • Issue ID 0273591: When a connection is migrated from one acceleration pair to another in a 4-port HSRP configuration, the connection resets.
  • Issue ID 0309316: CIFS module generates excessive logs, making it difficult to extract valuable log messages from the log file.
  • Issue ID 0313683: Accessing the Branch Repeater configuration utility’s Configuration Network Adapters > Ethernet tab > apA.2/apA.1 Links page on a highly loaded Branch Repeater might cause the appliance to restart.
  • Issue ID 0319151: The Show Tech Support feature hangs when you select the Reports option.
  • Issue ID 0325668: Memory corruption in MAPI module causes the Branch Repeater to restart.
  • Issue ID 0327412: WCCP service group priority field is not propagated to the highavailability secondary appliance.
  • Issue ID 0327708: When you upgrade the Branch Repeater software from 5.x to a higher version, it becomes unresponsive because of an invalid application ID.
  • Issue ID 0330699: Direction flag in service class rules is interpreted differently by the acceleration engine and the QOS engine, because of inconsistent result reports.
    Filtering is done per flow in the acceleration engine and per packet in the QOS engine.
  • Issue IDs 0331203, 0332364, 0333377,0333813, 0335352, 0335690, 0336352, 0336365, 0336931 and 0337371: When running ICA traffic in the Branch Repeater, a memory leak might cause the appliance to run out of memory and become unresponsive.
  • Issue ID 0331439: Printing on remote servers causes the appliance to restart.
  • Issue ID 0332261: MAPI connections go to the inactive state even when connections are active and processing pending requests, causing the appliance to restart.
  • Issue ID 0334234: The high-availability secondary appliance becomes unresponsive because of insufficient memory due to frequent parameter synchronization from the high availability primary appliance.
  • Issue ID 0335362: The CLI is not properly assigning values based on the userspecified “classification type” for adding an application. The problem is sometimes seen when Command Center is used to restore or deploy any user-created applications, because Command Center relies upon the CLI to ‘add’ these applications, and consequently even good entries made previously via the GUI can become corrupted.

Source

Download Citrix Branch Repeater 6.1.2 appliance for Hyper-V, VmWare vSphere, XenServer here
(Require MyCitrix ID)

Download Citrix Branch Repeater 6.1.2 Appliance Software here
(Require MyCitrix ID)

Download Citrix Plug-in 6.1.2 here
(Require MyCitrix ID)

Citrix Branch Repeater 6.1 – update

Written by Thomas Poppelgaard. Posted in Branch Repeater, Citrix, Hyper-V, Receiver, VMware, vSphere, XenServer

Update 5.09.2012

Statement from Citrix: XenServer 6.x isn’t supported with Citrix Branch Repeater 6.1 and it dosent work. 

Vmware vSphere 5.x is neither supported with Citrix Branch Repeater 6.x

Citrix have released a new version of Branch Repeater 6.1. This is a release many have been waiting for because all customers that are using a Microsoft Hyper-V environment havent been cable to use a VPX version of Branch Repeater for Hyper-V, i can with gladly inform you that now there is now available a Branch Repeater 6.1 VPX for Hyper-V Wuhuuu =o). Lets dig in whats new.

Overview

Release 6.1.0 is the software release for the Citrix Branch Repeater. This software release contains bug fixes and some enhancements. This software release is compatible with partner appliances running previous Branch Repeater releases 5.0 and later, and can be used in a mixed environment that includes units running these older releases.

Software Release Highlights in 6.1.0

In addition to the bug fixes, this software release includes the following enhancements:

  • Signed SMB2 support with Kerberos (supports NTLMv2)
  • Encrypted MAPI (with multi domain Support
  • Support for WCCP L2 with NSLB on all platforms (SDX and general BR appliances)
  • 6.1 Repeater Acceleration Plug-In
  • WCCP Mask enhancements to support low end routers
  • ShowTechSupport – Diagnostic Data Collections – Some UI enhancements
  • Branch Repeater VPX on Hyper-V
  • Customer Bug Fixes

Enhancements

  • Repeater VPX is now supported on Microsoft’s Hyper-V hypervisor running under 64-bit Windows 2008 R2 SP1, in addition to XenServer and VMWare vSphere. The features and specifications of Repeater VPX under Hyper-V are the same as those under the other hypervisors.
  • The Windows file system (CIFS) and Outlook/Exchange protocol (MAPI) are now supported with NTLM 2 and Kerberos encryption, allowing traffic on Windows domains running with the default security settings to be accelerated. Previously, only NTLM 1 encryption was supported, and NTLM 1 is not enabled by default in Windows domains. These features are available automatically whenever the appliances have joined a Windows domain and have designated a Kerberos delegate user.
  • The Windows file system (CIFS) and Outlook/Exchange protocol (MAPI) now support encrypted traffic involving multiple domains, such as when the client is a member of example1.com and the server is a member of example2.com, provided that the appliance, the client, and the server are all members of domains that have established mutual trust. This feature is available automatically when the appliance has joined one of the mutually trusting domains.
  • The Repeater Plug-in is now supported in release 6.1. Previously, it was supported only in release 5.x. New features include enhanced CIFS and MAPI support, matching those of the appliances, when appropriate security credentials are installed on the Plug-in.
  • To reduce the resources used on routers supporting the appliance in WCCP mode, the WCCP “MASK” option now uses a single-bit mask. The previous multibit mask could reduce performance on routers and smart switches with limited resources. This behavior is automatic

Bug Fixes

The following issues have been fixed in this release.

  • Issue ID 0174522: The WCCP protocol allows the use of a 1-to-7 bit mask to distribute the load across web caches, which provides a maximum of 128 maskelement values. The larger the number of values, the more TCAM resources the mask consumes on the router, so the mask should have only as many bits as necessary. In releases earlier than 6.1, Branch Repeater uses a hard-coded mask value of 0×1741, which translates to 64 mask element values.Branch Repeater now uses a 1-bit mask, which requires minimal TCAM resources on the router.
  • Issue ID 0272712: Idle FTP and VoIP control connections no longer time out while data is being transmitted on the associated data connections.
  • Issue ID 0303844: In some cases, when Cached Mode is disabled, users are unable to open or download file attachments. It displays an error message of file corruption.
  • Issue ID 0313614: Extremely short packets with bad IP checksums sometimes causes the Repeater to restart.
  • Issue ID 0318061: If the driver for the hardware watchdog in the Intel South Bridge chip set loads before the IPMI watchdog driver, the operating system reports a watchdog resource conflict that prevents the IPMI watchdog from loading.

Compatibility

The Repeater Plug-In is supported in release 6.1 but not in release 6.0. However, the release 5.5.x and 5.7.x versions of the Repeater Plug-in are compatible with release 6.0 Appliances, with one exception: Systems using XenApp 6.5 or XenDesktop 5.0 with Multiport/Multi-Stream ICA enabled require Release 5.7.2 of the Repeater Plug-in.

The Plug-in is supported by Citrix Receiver 1.2 and up, and can be distributed and managed by Citrix Receiver.

Branch Repeater with Windows Server is not included in release 6.1. However, appliances running release 6.1 interoperate with Branch Repeater with Windows Server appliances running earlier releases.

Supported Products

Appliance Type Supported?
Repeater for NetScaler SDX Models 500, 1000, 1500, and 2000 Yes
Branch Repeater VPX (all models) Yes
Branch Repeater Models 100, 200, and 300 Yes
Branch Repeater with Windows Server Models 100, 200 and 300 No
Repeater Plug-in Yes
Repeater 8000 Series (Newer Units): Units that list “SM85 Yes
Series 3”or “SM88 Series 3” on the “System Hardware” line
of the “System Status” page.
Repeater 8000 Series (Older Units): Units that list “SM85 No
Series 2”or “SM88 Series 2” on the “System Hardware” line
Older Models No

Supported Branch Repeater VPX Configurations

Release 6.1 is supported on Branch Repeater VPX running on both XenServer (5.5 and 5.6, but not 5.6 FP1) and VMware vSphere ESX/ESXi 4.1 hypervisors. ***

RAM and vCPU requirements have increased with this release. See the following tables.

Type vCPUs RAM Disk Max WAN Speed Max Accel. Conn.  Max Repeater Plug-ins
2 GB production 2 2 GB 100 GB 2 mbps 1000 50
4 GB production 2 4 GB 250 GB 10 mbps 10000 250
4 GB production* 2 4 GB 250 GB 45 mbps 15000 400
8 GB production* 4 8 GB 500 GB 45 mbps 25000 500

* With 45mbps license

Table 1-3. Other configurations (not for production networks).

Type vCPUs RAM Disk Max WAN Speed Max Accel. Conn.  Max Repeater Plug-ins
VPX Express 2 1 GB 60 GB 512 Kbps 10 5

Licensing, Initial Installation, and Upgrading

Licensing

Release 6.1 supports both remote license servers and locally installed licenses. If you upgrade an existing system with a local license, it continues to work.

Upgrading Existing Installations

Note:  If you are using a standard evaluation license, you cannot upgrade to software versions that are newer than your license.

Branch Repeater VPX
Since the resource requirements have changed, it is best to install a new 6.1.0 virtual machine rather than updating an existing one. Acquire the virtual machine from MyCitrix and follow the instructions in the User’s Guide.

Repeater and Branch Repeater
Acquire the software from MyCitrix.
Installing the Update

Note:  If you are upgrading from a pre-5.0 release (such as release 4.3), you must update to release 5.x first, then release 6.x. Also, if you are upgrading from a pre-5.0 release, acceleration will not take place until you install the new license from Citrix.

From the browser based user interface (http://appliance_ip_address), go to the “System Tools: Update Software” link. In the “Upgrade System Software” table, use the Browse button to select the patch file (the file you downloaded with ftp), and then press the Upload Patch button.

Source

Download – Branch Repeater VPX for XenServer, VMware vSphere and Hyper-V Software Rel 6.1.0 here
Require MyCitrix Account

Download – Branch Repeater Appliance Software Release 6.1.0 here
Require MyCitrix Account

Download – Repeater Appliance Software Release 6.1.0 here
Require MyCitrix Account

Download - Repeater Plug-in 6.1.0 (Citrix Acceleration Plug-in) here
Require MyCitrix Account

How To Set Up a Self Contained Repeater VPX Demo Environment

Written by Thomas Poppelgaard. Posted in Branch Repeater, Citrix, HDX, Windows 7, Windows Server 2008R2, XenApp, XenDesktop

Hi i want to share this awesome Whitepaper that Citrix have been so kind to share. Its a must if you are working with WAN emulation and WAN optimization.

Note (You can use latest version of XenServer 6.x)

Introduction

This guide is intended to be a quick step-by-step walk through of the setup and configuration of a self-contained Branch Repeater VPX demo environment with WAN Emulation. This environment is designed such that it can be easily replicated to a laptop or portable drive for customer or tradeshow demonstrations. Some skill set and environmental assumptions are made in this guide and are required prior to configuration of the demo environment:

  • XenServer 5.5 is installed and configured on the recommended hardware configuration (see below).
  • XenCenter 5.5 is installed and configured on a physical client machine for management.
  • The Branch Repeater VPX(s) are imported and licensed when possible.
  • The Windows Server VM has been created and a Windows Server operating system installed.
  • The Windows Client VM has been created and a Windows Client operating system installed.
  • The WANem ISO image has been downloaded and burned to a CDROM or DVD. (link provided above)

Products and Tools Required

  • 1 x XenServer 5.5
  • 1 x XenCenter 5.5
  • 2 x Branch Repeater VPX
  • 1 x Windows Client VM (Windows XP or higher)
  • 1 x Windows Server VM (Windows 2003 or higher)
  • 1 x WANem v2.2.x ISO

Read the full whitepaper, HINT click on Source ;o)

Enjoy /Poppelgaard

Source

Other articles thats in common with above, that i recommend you read

No network on WANem (Citrix XenServer) written by INGMAR VERHEIJ

How to use WANem in Citrix XenServer written by  José Luis Gómez Ferrer de Couto

Recent Comments

Thomas Poppelgaard

|

Hi Steve normal I install the GRID driver to device and when its workin, I disable the default VGA device.

Have you applied latest hotfix to the XS6.1 there are some crucial hotfixes to the GPU pass-through, that could crash the GRID’s, when you power on a VM with GPU pass-through.

Steve

|

Just a quick question on your setup. We just got a system similar to yours (R720, 2xGrid K2 cards, XenServer 6.1, XenApp 6.5). The GRID K2 driver installs (320.00), but the device shows up as stopped in device manager. Did you use any special options when installing the nVidia driver? Or somehow remove the default VGA device?

Dan

|

Hi Thomas,
Some features in your screenshots (eg create appointments and contacts) seem to be missing from the iOS version of @WorkMail that got released in April, do you know if these features are still coming in a future release? The Android client is far more functional by comparison.
Regards
Dan

Christian Eilskov

|

You can see the DHCP options here:

http://www.wyse.com/kb and search for 21501

You can transfer a image using Wyse Device Manager(WDM), the same goes for smaller updates like new ICA client and so.

Thomas Poppelgaard

|

Thank you Barry =)
The deep compression codec for Citrix XenDesktop HDX 3D Pro will be intergrated for Citrix XenApp in Excalibur so there is a big difference with bandwidth consumption. This means that XenApp in Excalibur will be the best platform for user density and works great over WAN with high latency as HDX 3D Pro have been known to deliver for several years. Yes i know of cases with WAN optimization, I will gather these and share them.

Best regards
Thomas

Feeds from Citrix Blog :