Branch Repeater Family Release Notes Release 5.7.0/3.0.

0
June 3, 2010

Contents
About Release 5.7.0/3.0.0 . . . . . . . . . Compatibility . . . . . . . . . . . . . . . . . . Branch Repeater With Windows Server Initial Installation . . . . . . . . . . . . . . . Upgrading Existing Installations . . . . . Licensing . . . . . . . . . . . . . . . . . . . . . How to Contact Citrix Support . . . . . . Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2 3 4 4 9 9 9

About Release 5.7.0/3.0.0

This release introduces SSL acceleration for the Branch Repeater product family. It also introduces Repeater Plug-in support for 64-bit versions of Windows 7. (Previous releases supported only the 32-bit versions of Windows 7). Release Number. This release is named 3.0.0 for Branch Repeater with Windows Server and 5.7.0 for all other products.

New Feature in Release 5.7.0/3.0.0

SSL acceleration. Branch Repeater products can decrypt, compress, and re-encrypt SSL data passing through them when set up as security delegates for the endpoint server or endpoint client. Two modes are available: Split proxy, where the Branch Repeaters act as a security delegate for both the endpoint server and the endpoint client, and transparent proxy, where the Branch Repeaters act as a security delegate for the endpoint server. SSL acceleration is supported on Repeater, Branch Repeater, Branch Repeater with Windows Server, and Repeater Plug-in products. Windows Server 2008R2 Support for Branch Repeater with Windows Server. Optional Disk Encryption. Strong AES-256 encryption now secures user data on the disks, including compression history.

Copyright 2010 Citrix Systems Inc.

Compatibility
Compatible Appliances
See Figure 1-1 for supported hardware platforms.
Figure 1-1 Supported/unsupported platforms
Appliance Type (From System Hardware entry on System Status page) Repeater 8000 Series: Units that list SM85 Series 3or SM88 Series 3 on the System Hardware line of the System Status page. Branch Repeater Models 100, 200, and 300. Branch Repeater with Windows Server Models 100, 200, and 300. Other Models. Repeater units that list DL85 Series 2 or DL88 Series 2 on the System Hardware line of the System Status page, WANScaler SM65, WANScaler DL65, WANScaler 6800 Series (all models), WANScaler 6500 Series (all models), Orbital 7800, Orbital 7500, Orbital 6800, Orbital 6500B, Orbital 5500, Orbital LC Supported?

Yes

Yes Yes

No

Compatible Repeater Plug-in Platforms

Windows XP (all 32-bit versions) Windows Vista (all 32-bit versions) Windows 7 (all 32-bit and 64-bit versions)

Compatibility With Citrix VPNs

Note: To use SSL acceleration with an Access Gateway VPN, you will need a hotfix for your VPN appliance. See your Citrix Representative If your Repeater Plug-in-equipped systems use a Citrix Access Gateway VPN, you must upgrade your Access Gateway clients and Appliances to the following versions: 4.5.7 for Access Gateway Advanced Edition. 9.0.66 for Access Gateway Enterprise Edition. 4.5.7 for Access Gateway Standard Edition. Note: ICA Proxy Mode on Access Gateway Enterprise Edition is not supported.

Branch Repeater Family Release Notes

Branch Repeater With Windows Server

Supported Deployment Modes
Units without Microsoft ISA Server Enterprise Edition 2006 Web Cache: Inline, virtual inline, group mode, high-availability, and WCCP modes are supported. Units with Microsoft ISA Server Enterprise Edition 2006 Web Cache: Inline mode is the only supported mode. The only ISA feature that is supported is the Web Cache. Units running Windows Server 2008: ISA is not supported. Inline, virtual inline, group mode, high availability, and WCCP modes are supported.

Compatible Applications and Services

The following are fully compatible and tested with Branch Repeater with Windows Server. Other software is used at your own risk. Please refer to the Microsoft EULA (shipped with the Appliance) for more information. All contents of the Microsoft Windows Server distribution installed on Branch Repeater Microsoft ISA Server Enterprise Edition 2006 Web Cache (on Windows 2003 Server only) Microsoft SCOM Agent Symantec Antivirus McAfee Antivirus HP OpenView Operations, version 7.5 IBM Director Microsoft SMS SP3 (as secondary site)

Windows Server Support

This release is supported on Windows 2003 Server (Standard Edition) and Windows 2008 Server (Standard Edition).

Branch Repeater Family Release Notes

Initial Installation
Repeater and Branch Repeater Appliances
For installation instructions, see the Branch Repeater Family Installation and Users Guide, releases 5.5-5.7. Licensing.The Repeater Plug-in acquires its license from the Repeater Appliance, so the Appliance requires licenses for both itself and the desired number of Plug-ins if Plug-in support is desired.

Branch Repeater with Windows Server

Units are normally shipped from the factory with Windows Server pre-installed and activated. For the installation procedure, see the Branch Repeater with Windows Server Installation and Users Guide, releases 2.0-3.0.

Repeater Plug-in
See the Branch Repeater Product Family Installation and Users Guide, releases 5.5-5.7, Chapter 5.

Upgrading Existing Installations

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

Branch Repeater with Windows Server

Upgrading the Acceleration Software
Note: If you are upgrading from release 1.x and your Appliance contains an Ethernet bypass card, you must update the bypass cards firmware. See Updating the Ethernet Bypass Firmware below. The Branch Repeater with Windows Server software can be updated to the current revision as follows: If you are upgrading from release 1.0.x, download and install the Citrix License Server on your Appliance. It can be found at: https://www.citrix.com/English/ss/ downloads/results.asp?productID=1679389 Obtain the Release 3.0 software file from your Citrix representative.

Branch Repeater Family Release Notes

If you are upgrading from release 1.0.x, obtain a new license as described in the Installation chapter of the Users Guide.

For more information on updating the software, see the Branch Repeater with Windows Server Installation and Users Guide, release 2.0, Chapter 3.

Updating the Ethernet Bypass Firmware

To support release 2.0 and later, Citrix Branch Repeaters with Windows Server shipped with 1.5 and earlier code from the factory require a firmware update for the Ethernet bypass card. Requirements 1. The Citrix Branch Repeater with Windows Server must contain an Ethernet bypass card. See diagram below. If the only Ethernet ports on the unit are the two motherboard ports, do not follow this procedure.

2. The Appliance must be running software version 2.0 or later. 3. You must have physical access to the Appliance (a keyboard, mouse and monitor must be used for the update, as the bypass card will be disabled. Also, the unit will shut down and must be started manually after the update). 4. This procedure need only be run once, preferably immediately after the Appliance is upgraded from release 1.x to release 2.x. Procedure 1. Install Appliance software release 2.0 or later if this has not been done already. 2. Log into the Branch Repeater with Windows Server Appliance via a locally connected keyboard, mouse, and monitor. Network access will be interrupted by the update, and the update cannot be completed via remote login. 3. On the Branch Repeater with Windows Server, run C:\Program Files\Citrix\Branch Repeater\CitrixBR_n2265_utilv1.vbs, which brings up the following message box:

Branch Repeater Family Release Notes

4. Click Yes to verify the EEPROM version. This operation stops Citrix Branch Repeater service and verifies the EEPROM version. The following message box shows up if the EEPROM is not upgraded:

5. Click Yes to upgrade the bypass card EEPROM. The Appliance shuts down automatically after the upgrade. 6. Turn the box back on. To verify the upgraded EEPROM, please repeat steps 2 and 3. The following message box shows up if the EEPROM is upgraded successfully. After verifying this, reboot the unit:

7. If the message box does not show up, please redo steps 2 to 5. Please contact Citrix Support if the EEPROM fails to upgrade after few tries.

Using the Recovery Partition

Note: This procedure reimages the Appliance and destroys all user data and system customization, except for acceleration settings and licenses, which are retained. The unit can be restored to a factory-installed state by selecting WinPE re-image tool at boot time. Confirm (twice) that you wish to re-image the system and it will be restored to its initial configuration. This process is almost entirely automatic (requiring two confirmations before starting, and one Press Enter to reboot and launch Windows Setup partway through), installing the operating system and software, rebooting. No configuration information is required of the administrator during this process.

Branch Repeater Family Release Notes

As with any other re-imaging process, all data on the main partition (C:) is lost. The operating system is restored to a default state, and any programs or services you may have installed will be lost. Acceleration settings and licenses are retained, with the exception of the configuration of the Ethernet bridge, which is set to a default state.

Repeater and Branch Repeater

Acquire the release 5.7 software from MyCitrix.

Installing the Update

Note: If you are updating 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. See Figure 1-2
Figure 1-2 Update Software page.

The patch file will be copied to your Appliance and tested for integrity. If it is a valid file, a Restart Unit? prompt will appear. Click on Yes. The settings from your current release will be copied to the new one, so your configuration will be retained in the new release. The process of installing the patch file continues during the restart, which may take several minutes longer than usual. This is normal.

Branch Repeater Family Release Notes

The new release is now running on your Appliance. Note: If your appliances use the default password, it will be changed when you install this upgrade. The default password is now password.

Reverting to a Previous Release

Upgrading creates a new software installation; it does not remove the previous version of the software or the previous configuration settings. Thus, an Appliance can be returned to any release that it has previously used. (If you must revert to a lower-numbered release that has not been previously installed on the unit, use the Upgrade procedure. Do not do this unless asked to do so by Support.) You can revert to a previous version of the software using the Downgrade Release the System ToolsUpgrade Software page. This will also return the configuration to what it was for the older release, at the time the upgrade was applied. Any configuration changes you made with the newer release will be lost. If you upgrade again, the upgrade will copy the older releases settings into the newer release. The software can only be downgraded to previously installed versions. Neither the Upgrade Software nor the Downgrade Release feature supports the installation of patch files with a lower version number than the current one, except for versions already resident on the unit.

Installation Troubleshooting
The clock face giving the estimated update time is not always 100% accurate. If the installation ends with an error page giving some kind of HTTP timeout error, wait a few minutes, then attempt to connect to the units browser-based management interface normally. This will generally show that the newly installed version is up and running. Sometimes an update will fail if it spans a large number of releases, such as a jump between release 3.2 and 5.7. If this happens, installing an intermediate release first (for example, release 4.3) and upgrading in two steps will usually work. Contact Citrix Support with any installation issues.

Updating Repeater Plug-in

Acquire the Release 5.7 software file from MyCitrix. To install it, follow the prompts given by the installation program. You may wish to customize the release before distributing it to your users. See the Users Guide for more information.

Licensing
See the Installation and Users Guide for your product.

Branch Repeater Family Release Notes

How to Contact Citrix Support

To contact Citrix Support, call 1-800-4CITRIX or use the My Support section on MyCitrix at http://www.citrix.com. You will be asked for your hardware serial number as part of the support process. Detailed instructions for contacting support can be found at: http://citrix.com/site/ resources/dynamic/sup2nd/Citrix_HWS_SerialNO.pdf.

Known Issues
Issues are listed in reverse numerical order (newest items first). #75351. (Branch Repeater with Windows Server) Description: If the Appliance is not running release 6.8.9020 of the Citrix Licensing (the version that is shipped with the Appliance), installation will not proceed. Recommended action: Do not upgrade Citrix Licensing, or re-install version 6.8.9020. #74337. (Repeater Plug-in) Description: When importing security credentials into the Citrix Acceleratin Manager, setting File of Type to *.* causes all files and folders to vanish from the listing. Recommended action: Setting the File Name to *.* and pressing Enter will cause the files to reappear. #73499. (Branch Repeater with Windows Server) Description: High-availability and virtual inline modes do not work simultaneously. Recommended action: Disable high-availability mode or switch to inline or WCCP mode. #72671. (Repeater Plug-In) Description: Currently shipping versions of Access Gateway VPNs (AG-EE or AG-SE) do not support compression when SSL acceleration is enabled. Recommended action: Contact Support for a hotfix to the Access Gateway software. #67698. Description: SSL connections will not be compressed when SSL compression is used in SSL transparent proxy mode and the endpoint system uses TLS extensions with OpenSSL 0.9.8k or later. The connections will succeed and be accelerated but not compressed. Recommended action: None. #66449. (Repeater/Branch Repeater) Description: The MAPI connection list may not match on the client-side and server-side appliances. Closed connections that have been removed from the client-side MAPI connection display may persist on the server-side display. Recommended action: None. #66433. (Repeater Plug-in) Description: Under Windows 7, if a network port is configured with two IP addresses, acceleration over that port will not occur.
Branch Repeater Family Release Notes 9

Recommended action: Use only one IP address per port. #63169. (Branch Repeater with Windows Server) Description: The appliance may go into non-accelerated mode after the SCCM 2007 SP1 Secondary Site software is installed. Recommended action: Reboot the appliance. #62317. (Branch Repeater with Windows Server) Description: The serial console will not let you disable Ethernet ports by setting their IP addresses, netmasks, or gateways to 0.0.0.0. Recommended action: Do not use the serial console to manage ports. Instead, use the normal Windows Network Connections page. #62858, 62857, 34269. (Repeater/Branch Repeater) Description: The Asymmetric Routing alert throws false positives under a variety of circumstances. Recommended action: Real asymmetry is also indicated by the presence of connections on the Non-accelerated view of the Active Connections page. Such connections will have UR:3 in the Details column and a non-zero value in the Bytes Xfered column. If periodic checking reveals no long-running non-accelerated connections like this, your installation is not suffering from asymmetry. #60129. (Repeater/Branch Repeater) Description: Some older browsers or browser/ OS combinations are not compatible with the Repeater UI. This includes Internet Explorer 6.x. Recommended action: Use an up-to-date browser. #59718. (Branch Repeater with Windows Server) Description: A Windows-2008-based Appliance may crash if VLAN settings are changed while high availability is enabled. Recommended action: Disable high availability before changing VLAN setting, change the settings on both Appliances, then re-enable high availability. #58732. (Branch Repeater with Windows Server) Description: Updating a Windows-2008-based Appliance may fail if McAfee antivirus is installed. Recommended action: Disable virus protection temporarily before installing the Appliance software. #56804. (Repeater Plug-in) Description: Installing the Nortel VPN after installing the Plug-in sometimes fails. Recommended action: Install the Nortel VPN first. If necessary, uninstall the Repeater Plug-in, install the VPN, then reinstall the Repeater Plug-in. #58169. (Repeater Plug-in) Description: If Access Gateway Enterprise Edition is run in NAT mode, acceleration will not take place unless the correct addresses are used in the Appliances Client Acceleration Rules table. Recommended action: Include both the pre-NAT and post-NAT versions of the destination subnet in the Client Acceleration Rules.

10

Branch Repeater Family Release Notes

#55111. (Branch Repeater With Windows Server) Description: Group Mode and High Availability cannot be used at the same time. Recommended action: Use a different deployment option. (This is a highly implausible deployment mode for a branch-office in any case, since it requires four appliances.) #54447. (Repeater Plug-in) Description: When disconnecting from a Microsoft PPTP VPN, the Repeater Plug-in acceleration service sometimes exits and restarts. Recommended action: None. #54178. (Repeater/Branch Repeater) Description: If you use Bandwidth Schedules with hardboost on an HA pair, the bandwidth schedules will not be propagated to the secondary unit. Recommended action: Do not use bandwidth schedules. #50887. (Branch Repeater with Windows Server) Description: If the SMS Secondary Site software is installed on the Appliance, it may go into non-accelerated mode until it is rebooted. Recommended action: Reboot the Appliance. #50054. (Branch Repeater with Windows Server) Description: After enabling high-availability, the UI on the Secondary unit is supposed to display a banner that tells you to do all Appliance management on the Primary unit. But UI pages are not self-refreshing. This can cause confusion. Recommended action: When in doubt, press the Refresh link. #49751. Description: With ICA acceleration enabled, a Microsoft Office application that closes itself automatically through a macro may reopen again. Exiting the application normally always works, however. Recommended action: Close the application manually. #49255. (Repeater/Branch Repeater) Description: After rebooting the Appliance manually, an Unexpected Restart Alert and a core file may be generated. Recommend action: Delete the core file. #47084. (Branch Repeater with Windows Server) Description: Some non-standard USB keyboards and mice are not recognized by default by Citrix Branch Repeater. Recommended action: Use standard keyboards and mice that will be automatically recognized by Windows. #45125. (Branch Repeater with Windows Server) Description: The documentation installed on the unit's hard disk is obsolete. Workaround: Go to MyCitrix.com for up-to-date documentation. #44833, 44612, 44513. (Branch Repeater with Windows Server) Description: Various failures may be seen if the accelerated bridge and one or more motherboard ports are on the same subnet.

Branch Repeater Family Release Notes

11

Workaround: Motherboard ports must be on a different subnet from the accelerated bridge, or disabled. #43125. (Repeater Plug-in) Description: When updating an existing Repeater Plug-in installation, the default settings in the Repeater Plug-in installation file are ignored. Recommended action: This is normal behavior. To eliminate old defaults, uninstall the Repeater Plug-in or add the new defaults in by hand after upgrading. #42964. (Branch Repeater with Windows Server) Description: If the accelerated bridge is deleted on an ISA-equipped system, Branch Repeater stops accelerating. A message about running in degraded mode appears. Workaround. Do not delete the bridge. #42864. (Branch Repeater with Windows Server) Description: On ISA-equipped systems, the SCOM discovery process and automatic SCOM agent installation does not work because it is blocked by the ISA firewall. Workaround: This is not Citrix-related, but is a typical issue with the ISA firewall. See the Microsoft ISA documentation. A summary of the procedure follows: To allow the SCOM discovery process, right-click on Firewall Policy in the ISA Server Management program and select Edit System Policy... Un-check Enforce Strict RPC compliance. Create additional firewall rules to allow access from the SCOM server, and on each of these, right-click and select Configure RPC Protocol, and uncheck Enforce strict RPC compliance for the individual rule. Alternatively, create a firewall rule for port 5723 only, configure the SCOM server for Review new manual agent installations, and install the agent manually on the Branch Repeater. #42523. (Branch Repeater with Windows Server) Description: Event Viewer displays error messages from WSH that say, WANScalerServerDiscovery.js: Cannot execute Citrix_WS_Evergreeninfo_query: Received error: ... Recommended action: These error messages mean that the acceleration service is not running. Restart the service (called Citrix Branch Repeater in the Services list) if desired. Otherwise, ignore the messages. #42451. (Branch Repeater with Windows Server) Description: ISA cannot be uninstalled on a busy system. Workaround: Do not uninstall ISA. If for some reason this is necessary, contact Support. #41340. (Branch Repeater with Windows Server) Description: In SCOM 2007, the Topology pane of the Branch Repeater Dashboard is sometimes blank. Workaround: The contents will appear eventually. For a faster update, refresh the view (Dashboard Actions: Refresh).

12

Branch Repeater Family Release Notes

#41185. (Branch Repeater with Windows Server) Description: The information in an SCOM 2007 Object Properties window does not always show the latest value. Workaround: Exit and restart the SCOM Operation Console. #40545. Description: FTP transfers are slow when using Cygwin FTP in ASCII mode. This is not a WANScaler issue. The Cygwin FTP program is very slow when transferring in ASCII mode, with or without Branch Repeater. Recommended action: Use binary mode or use a different FTP program. #39578. (Repeater Plug-in) Description: Users with the Repeater Plug-in installed cannot access the management interfaces of Repeater Appliances. Recommended action: On the Appliance, add an Exclude rule for the apA management IP on the Acceleration Rules tab (add another for apB, if present). Alternatively, disable the Repeater Plug-in when managing Appliances. #36850. (Repeater Plug-in) Description: The Repeater Plug-in Installer reports successful completion of the installation, but the system application and event logs reveal that additional configuration was performed after the system was restarted. Recommended action: None. This is normal behavior. #36111. (Repeater Plug-in) Description: Sometimes the PC Tools Firewall blocks FTP and HTTP connections when the Repeater Plug-in is enabled. Recommended action: Uninstall and reinstall the PC Tools firewall. If the problem persists, use a different firewall. #35359. (Repeater Plug-in) Description: Repeater Plug-in will not run on a system running the eTrust Firewall. The eTrust firewall blocks access to localhost (IP address 127.0.0.1). The Repeater Plug-in returns the error message, Unable to setup wakeup connection. Access to 127.0.0.1 is essential to Repeater Plug-in operation. Recommended action: Configure the firewall to allow access to 127.0.0.1 or disable or remove the firewall. #34610. (Repeater 8500 Series) Description: The Repeater 8500 has removable hard drives. However, these systems do not support the hot-swapping of drives. Recommended action: Never remove drives unless instructed to by Support. Never remove drives while the Appliance is powered up. #34564. (Repeater Plug-in) Description: The default gateway sometimes changes when the Repeater Plug-in is installed. This seems to be a bug in the Microsoft NDIS code and occurs in non-Repeater network software as well. Recommended action: The original routes are usually restored after a reboot. If not, changing the interface metrics in the Advanced TCP/IP Properties for the individual interfaces may be necessary. The interface that should have the default gateway should be set to have the lowest interface metric.
Branch Repeater Family Release Notes 13

#34522. (Repeater/Branch Repeater) Description: Service classes may not be upgraded along with the software. If all the service classes on an Appliance are kept at their default settings, then they will be upgraded to the new defaults when you upgrade the software. However, if even one definition has changed, all the service classes will be kept as they were. Recommended action: This behavior is usually desirable. You can use the RESETTOFACTORY command on the serial interface or UI Save/Restore menu, then reconfigure your Appliance manually to gain the cumulative benefit of parameter changes. #33581. (Repeater/Branch Repeater) Description: Sometimes a false mode mismatch (hardboost/softboost mismatch) alert or log message is generated when every Appliance in the network is operating in the same mode. Recommended action: Verify correct configuration the first time this alert appears after a new Appliance is added to network, then disable the Alert if desired. #33579. Description: The Effective BW number on the Compression Status display may be less than the actual effective bandwidth. This number is derived by multiplying the bandwidth limit times the compression ratio. If a secondary bottleneck in the system prevents the bandwidth limit from being maintained at all times, the true effective bandwidth will be less. Recommended action: None. #33081. Description: Adding an Appliance to a site can cause BGP (Border Gateway Protocol) to fail. The Appliance decrements the TTL of all TCP packets. Protocols like BGP that use a TTL of 1 will thus fail when an Appliance is inserted between two units using it. Recommended action: Contact Support. #32397. (Repeater Plug-in) Description: If there is a pre-release-4.x Appliance along the route between the Repeater Plug-in and its target Appliance, Repeater Plug-in connections will be non-accelerated. Recommended action: Upgrade the offending Appliances to 4.x, or deploy the Repeater Plug-in Appliance so that there are no intervening Appliances running earlier software. #31782. (Repeater/Branch Repeater) Description: Cant achieve full bandwidth with a single connection under hardboost on fast, high-latency links. Recommended action: You should be able to achieve transfers that run very close to the bandwidth you set with the bandwidth limit. If not, contact Support.

14

Branch Repeater Family Release Notes

#31044. (Repeater/Branch Repeater) Description: The reported duration of accelerated connections is not what one would expect, and hence the average bandwidth of the connection is suspect. This is due to half-closed connections, where one side of the connection has been closed with the FIN flag, but the other side has not. Such connections are very common. Often, no data is transferred in the open direction, and idle time accumulates after the connection appears to be finished. #30702. (Repeater/Branch Repeater) Description. In hardboost, if an Appliance has open connections to two or more different sites, it divides its bandwidth between them statically, not based on actual demand. For example, if Site A is talking to Site B and Site C, it will allocate half its bandwidth to each, even if Site B has only an idle telnet connection open. Recommended action: Use softboost for topologies other than point-to-point and hub-and-spoke where the spokes speak only to the hub. Alternatively, use Service Class definitions to exclude long-running low-bandwidth connections such as telnet from acceleration. #30558. (Repeater/Branch Repeater) Description: Log files are not searchable. Recommended action: Enable the syslog feature on the Logging page. This will send complete log information to the syslog server of your choice. Search the log on the syslog server with your choice of tools (grep, etc.).

Branch Repeater Family Release Notes

15

16

Branch Repeater Family Release Notes