Citrix CloudBridge 7.0 Release Notes

Transcription

1 7.0 Release Notes 7.0

2 Copyright and Trademark Notice CITRIX SYSTEMS, INC., ALL RIGHTS RESERVED. NO PART OF THIS DOCUMENT MAY BE REPRODUCED OR TRANSMITTED IN ANY FORM OR BY ANY MEANS OR USED TO MAKE DERIVATIVE WORK (SUCH AS TRANSLATION, TRANSFORMATION, OR ADAPTATION) WITHOUT THE EXPRESS WRITTEN PERMISSION OF CITRIX SYSTEMS, INC., Systems, Repeater, Branch Repeater, WANScaler, Orbital Data, Orbital 5500, Orbital 6500, Orbital 6800, TotalTransport, AutoOptimizer Engine, and Adaptive Rate Control are trademarks of Corporation Systems assumes no responsibility for errors in this document, and retains the right to make changes at any time, without notice. Portions licensed under the Apache License, Version licenses/license-2.0. Portions licensed under the Gnu Public License, including xmlrpc++, glibc, rpmlibs, beecrypt. Portions licensed under the Gnu Public License with product-specific clauses, including the Linux kernel ( libstdc++, and libgcc. Portions are free software with vendor-specific licensing, including zlib ( netsnmp ( license.html), openssl ( krb5-libs ( /web.mit.edu/kerberos/krb5-1.3/krb /doc/krb5-install.html), tcp_wrappers (ftp://ftp.porcupine.org/pub/ security/tcp_wrappers_license), bzip2-libs ( sources.redhat.com/bzip2/), popt ( COPYING.DOC). Elfutils-libelf is licensed under the OSL 1.0 license, JPGraph licensed under the terms given in proversion.php LZS licensed from Hifn corporation, Iperf licensed under the terms given in ui_license.html. This product includes PHP, freely available from Document code: June :48:03

3 Contents Release Notes... 5 Enhancements...5 GUI Navigation Changes...7 Known Issues and Workarounds...9 Compatibility...15 Plug-in...16 Compatible Operating Systems Hardware Requirements...16 Plug-in and Receiver...17 Features Table Supported VPX Configurations Licensing, Upgrading, and Downgrading Licensing Upgrading Existing Installations Downgrading to an Earlier Release...28 Contacting Customer Support iii

4 Contents iv

5 7.0 release 7.0 is compatible with partner appliances running Branch Repeater release 5.5 or later, Branch Repeater with Windows Server release 2.0 or later, and release 6.2 or later. It can be used in a mixed environment that includes appliances running these earlier releases. Enhancements in this release include video caching and a redesigned administrative interface. Additionally, other key enhancements include Microsoft Hyper-V 2012, support for VPX, and Plugin for Windows 8. recommends that you upgrade your appliance to this release if you need any of these features on the appliance. Release Notes These release notes describe the enhancements, changes, and known issues in the 7.0 release. Enhancements The 7.0 release contains enhancements for the following (formerly Repeater) features. Branding Changes In release 7.0, the Branch Repeater and Repeater products are renamed as products, except the Repeater 8500 and Repeater 8800 series. The following table lists the product-name and model-number changes: Branch Repeater and Repeater Branch Repeater 100, 200, and 300 Branch Repeater with Windows Server (100, 200, and 300) Repeater 310, 500, and 1000 on SDX Repeater 1500 and 2000 on SDX Branch Repeater VPX Repeater Plugin 600 series 700 series 4000 series 5000 series VPX Plugin 5

6 7.0 New Improved User Interface The user interface has been changed to provide a better user experience, with easier navigation, less clutter, and other usability improvements. The Dashboard page and Monitoring pages are reorganized for a better visual experience. The main navigation menu items are organized as tabs on the header, and the navigation options are reorganized. The header provides bread crumbs for tracing your navigation path. Video Caching Release 7.0 adds a video caching feature to 600 and 2000 appliances. Video Caching improves the user experience for videos that are viewed more than once, especially on slower links, although first time viewing remains without benefit based on WAN speed. Due to video caching feature, video streams when re-watched will be delivered at the LAN speed from a device. Hence, significantly improving the overall viewing experience and reducing WAN usage for subsequent viewers. Limitations: Only Inline deployment mode is supported. Support for CLI and SNMP are not available. This feature is supported only on 001 and 002 models of 600 platforms. Plug-in for Microsoft Windows 8 The Plug-in is now supported by the Microsoft Windows 8 operating system (32-bit and 64-bit versions of Enterprise Edition). Support for Microsoft Hyper-V 2012 Standard and Datacenter Edition This release supports hosting of VPX appliances on the Hyper-V 2012 virtualization platform. GUI Navigation Changes For GUI navigation changes in this release, see GUI Navigation Changes. Connector on 4000 and 5000 Note: Connector is included as a Beta feature in this release. The Connector feature of the appliance connects enterprise datacenters to external clouds and hosting environments, making the cloud a secure extension of the enterprise network. Cloud-hosted applications appear as though they are running on one contiguous enterprise network. With Connector, enterprises can augment their datacenters with the infinite capacity and elastic efficiency provided by cloud providers. The primary purpose of the Connector is to enable enterprises to move their applications to the cloud while reducing costs and the risk of application failure. In addition, the Connector increases network security in cloud environments. 6

7 7.0 Release Notes Also, the WAN optimization feature of the appliance accelerates traffic in the Connector, providing LAN-like performance for applications running across enterprise datacenters and clouds. You can configure Connector between two datacenters or between a datacenter and a Cloud. GUI Navigation Changes Many nodes that were at the top level of the previous interface are now sub-nodes. The following table shows their locations. Table 1-1. Node Mapping Table Nodes in the previous version of GUI Location of the nodes in the current GUI Command Menu and sub-nodes Command Menu> Dashboard Command Menu> Features Command Menu> Quick Installation Command Menu> Logout Dashboard Tab Configuration Tab> Appliance Settings> Features No longer in the navigation menu, but the Quick Installation page is displayed when you logon the first time. Moved to header section of the browser. Monitoring and Sub nodes Monitoring > (ICA/CGP) Monitoring > Compression Monitoring > Connections Monitoring >Filesystem (CIFS/SMB) Monitoring > Optimization > (ICA/ CGP) Monitoring > Optimization > Compression Monitoring > Optimization > Connections Monitoring > Optimization > Filesystem (CIFS/SMB) Monitoring > Logging Monitoring > Appliance Performance > Logging Monitoring > Outlook (MAPI) Monitoring > Optimization > Outlook (MAPI) Monitoring > Repeater Partners Monitoring > Partners & Plug-ins > Partners 7

8 7.0 Nodes in the previous version of GUI Location of the nodes in the current GUI Monitoring > Repeater Plug-ins Monitoring > Partners & Plug-ins > Plug-ins Monitoring > Secure Partners Monitoring > Usage Graph Monitoring > Partners & Plug-ins > Secure Partners Monitoring > Optimization > Usage Graph Monitoring > WCCP Monitoring > Appliance Performance > WCCP Configuration node and sub nodes Configuration > Administrator Interface Configuration> Appliance Settings > Administrator Interface Configuration > Advanced Deployments Configuration> Appliance Settings > Advanced Deployments Configuration > Application Classifiers Configuration> Optimization Rules > Application Classifiers Configuration > Licensing Configuration> Appliance Settings > Licensing Configuration > Links Configuration> Optimization Rules > Links Configuration > Logging/Monitoring Configuration> Appliance Settings > Logging/Monitoring Configuration > Network Adapters Configuration> Appliance Settings > Network Adapters Configuration > Repeater Plug-ins Configuration> Appliance Settings > Plug-ins Configuration > Secure Partners Configuration > SSL Settings > Secure Partners Configuration > Service Classes Configuration> Optimization Rules > Service Classes Configuration > SSL Acceleration Configuration > SSL Encryption Configuration > SSL Settings > SSL Acceleration Configuration > SSL Settings > Encryption Configuration > Traffic Shaping Policies Configuration> Optimization Rules > Traffic Shaping Policies 8

9 7.0 Release Notes Nodes in the previous version of GUI Location of the nodes in the current GUI Configuration > Tuning Configuration> Optimization Rules > Tuning Configuration > Windows Domain Configuration> Appliance Settings > Windows Domain Reports node and sub-nodes Reports > Compression Monitoring > Appliance Performance > Compression Engine Reports > LAN vs WAN Reports > Links Usage Reports > Service Classes Reports > Top Applications Reports > Traffic Shaping Monitoring > Optimization > LAN vs WAN Monitoring > Optimization > Links Usage Monitoring > Optimization > Service Classes Monitoring > Optimization > Top Applications Monitoring > Optimization > Traffic Shaping System Maintenance node and subnodes System Maintenance > Backup/Restore Configuration > System Maintenance > Backup/Restore System Maintenance > Clear Statistics Configuration > System Maintenance > Clear Statistics System Maintenance > Date/Time Configuration > System Maintenance > Date/Time Settings System Maintenance > Diagnostics Configuration > System Maintenance > Diagnostics System Maintenance > Restart System Configuration > System Maintenance > Restart System System Maintenance > Update Software Configuration > System Maintenance > Update Software Known Issues and Workarounds The following issues have been identified in this release. 9

10 7.0 Issue ID : The wsbandwidthlimit SNMP object query is not supported in the 4000 and 5000 appliances, regardless of the platform model and the number of instances provisioned on the platform. Traffic is only accelerated to the licensed limit. Issue ID ( 600 and 2000): If the appliance is placed on a VLAN Trunk mode, all HTTP VLAN tagged traffic bypasses the video caching engine. Therefore, videos are not cached. Issue ID ( VPX): In a High Availability (HA) configuration of Windows Servers (2008 R2 or 2012), disk based compression stops functioning after a hypervisor (Windows Server) level HA operation. Issue ID ( 600 and 2000): On a appliance that has two pairs of accelerated ports, if an IP address is not assigned to an accelerated bridge interface, the network connected to that interface bypasses the video-caching engine. Workaround: To make use of the video caching feature, assign IP addresses to both the bridge interfaces in the subnet, from where the connections are initiated. Issue ID ( 2000): The video caching feature might not work properly on a 2000 appliance if the same IP address is assigned to more than one bridge adapter. Workaround: Assign different IP addresses for the accelerated bridge interfaces (apa and apb). Issue ID ( 2000): When you log on to the GUI, the logon fails and a "Please login to continue" message appears. Workaround: Close the browser, clear the browser cache, and log on again. Issue ID : In the Management Service of 2000 and 3000 appliances, interface speed settings are not supported if Auto Negotiation is set to OFF or Duplex is set to Half. Workaround: Set Auto Negotiation to ON and change the speed setting to either 10, 100, or 1000 Mbps. Issue ID : If you use Internet Explorer 8 to configure, the user interface displays error messages. Workaround: Upgrade to Internet Explorer 9 or later, or use a different browser, such as Chrome or Firefox. Issue ID : If a Windows 8 client opens a Microsoft Office (Word, Excel, or Powerpoint) file on a Windows Server 2008 R2 server and attempts a Save As operation, the attempt fails. Issue ID : HTTP videos do not benefit from video caching when watched on a Windows 8 mobile device. Issue ID : After an upgrade from release 6.2 to release 7.0, product-name changes introduced in the new release might not appear in your browser. Workaround: Clear the browser cache and restart the browser. Issue ID : Video caching benefits are available only to clients in the same subnet as the appliance's apa or apb client-side interface. 10

11 7.0 Release Notes Issue ID : The Notifications tab displays an incorrect alert message. Instead of "Maximum number of concurrent video connections have been reached. New requests will not get caching benefit," the message should say "Maximum number of concurrent HTTP connections have been reached. New HTTP connections will not get caching benefit." Issue ID : After you upgrade the appliance from release to 7.0.0, the user interface sometimes displays items incorrectly. Workaround: Close the current browser session and log on through a new browser session. Issue ID : The ICA diffserv code point (DSCP) marking on the 4000 and 5000 appliances does not work. Issue ID : In the video-caching settings, changing the value for maximum caching object size has no effect. Workaround: Restart the appliance. Issue IDs and : 4000 and 5000 appliances do not allow you to add Accelerator instances. Workaround: Add the Accelerator instances after performing the following steps: a. Perform a factory reset on the appliance. b. Apply the license. c. Provision the instances. d. Perform the software upgrade. Issue ID : When you upgrade a appliance from release to by using the Management Service, the upgrade process fails. Workaround: Use Accelerator to upgrade the appliance. Issue ID : The SNMP query wscompressioneffectivebandwidht is not supported on the 4000 and 5000 appliances. Issue ID : The Microsoft Management Console of 700 appliance displays an error message when accessing the Diagnostic Trace. Issue ID : HSRP is not supported in this release. Contact Support for specific deployment options. Issue IDs and : If you configure a 4000 appliance in a high availability setup to use a 1 Gbps interface in L2 mode, traffic does not flow through the interface if the appliance becomes primary after a failover event. Workaround: From the NetScaler command line, reset both the interfaces by entering the reset interface <Interface_ID> command. Example: If 1/1 and 1/2 are the bridge pair, enter the commands, reset interface 1/1 and reset interface 1/2. Issue ID ( VPX for XenServer): The XenServer distributed virtual switch controller feature is not compatible with VPX. 11

12 7.0 Workaround: The XenServer distributed virtual switch controller feature should not be configured or enabled when using VPX. Issue ID ( 4000 and 5000): Active FTP might not be accelerated on the appliance. Workaround: Enable acceleration for "Unclassified TCP" to get acceleration benefits. Issue ID : 700 series appliance does not work in some spanning tree enabled deployments. Workaround: Disable the spanning tree protocol on switches connected to the 700 series appliance. Issue ID : CLI support is not provided for 4000 and 5000 Repeater Unified Instance (Repeater broker). Issue ID : Uploading a CA certificate results in an error in an SDX Repeater Unified instance. Workaround: Copy and paste the certificates instead of uploading them. Issue ID : After you upgrade or restart the Repeater Instances, one of the instances might not start. Workaround: Start the instance from the SDX-UI. Issue ID ( VPX for Amazon): If a user defined DNS Server IP address is added as a Secondary DNS Server, the server fails to join the domain. Workaround: Add the DNS Server IP address as the Primary DNS Server. Issue ID ( 4000 and 5000): If you restart the SDX appliance from the SVM, the loopback interface might not be available. Workaround: Unplug the fiber loopback cable and plug it back in. Issue ID ( Cloudbridge VPX for XenServer): When you run the SNMP get requests command for any Enterprise SNMP OID on Branch Repeater, it randomly returns the "SNMP No Such Object" message. Workaround: Restart the VPX appliance. Issue ID : After a successful restore operation, the NetScaler and instances are not restored to the versions available in the backup. Issue ID : The management service on a 5000 series platform does not allow you to change the default loopback interface to 10/6. Workaround: Use an interface other than 10/6 as the loopback interface. Issue ID : Repeater UI fails to synchronize configuration to instances after performing the -Replication task from SVM. Workaround: Provision the instance by using the Service VM. Issue ID : If a VPX instance is deployed on XenServer 6.1.0, and the instance s bridged interfaces are mapped to Broadcom BCM5722 NICs with firmware version 3.08, VLAN tagged traffic does not flow through the bridged interfaces. Issue ID ( VPX for Amazon): TCP traffic on the Connector VPX stops working if you disable traffic processing. 12

13 7.0 Release Notes Workaround: a. Check the state of the Connector VPX SNMP monitor by using the NetScaler CLI, and enable it if it is not enabled. b. Navigate to Logging/Monitoring: SNMP in the Connector VPX configuration utility and do the following: Click the Enable SNMP Authorization Failure Traps check box under System Information. Enter the NetScaler IP address in the Management Station IP address field under Access Configuration. Issue ID : If the primary DNS server cannot resolve the Windows domain, the join operation throws a DNS_ERROR_BAD_PACKET error message. Issue ID ( VPX for Amazon): The VPX for Amazon fails to launch Outlook MAPI connections if the other TCP Traffic service-class policy is set to None. Workaround: Set the other TCP Traffic service-class policy to Flow Control. Issue ID ( VPX for Amazon): Un-accelerating the TCP connections in VPX for Amazon. The TCP connection establishment fails in VPX for Amazon if you set the corresponding service class policy to None. Workaround: VPX for Amazon should always have service class policy for other TCP traffic set to Flow Control. Configure the following policy on the Connector to bypass the TCP connections. The following example bypasses the HTTP port 80 and CIFS port 445. set lb vs BR_LB_VS_DYN_2 -listenpolicy client.tcp.dstport.eq(80).not&&client.tcp.dstport.eq(445).n ot Issue ID ( VPX for Amazon): VPX for Amazon does not forward ICMP packets. This results in the unaccelerated traffic getting blocked on the appliance. Issue ID ( 2000 and 3000): Use Internet Explorer, Chrome, or Firefox browsers for best results with the configuration utility. Safari browser is not supported in this release. Issue ID ( 2000 and 3000): The configurations of Repeater 8500 and Repeater 8800 series appliances cannot be restored to 2000 or 3000 appliances. Issue ID ( 2000 and 3000): The Refresh button on the Dashboard page of the configuration utility refreshes the graphs but not the values. 13

14 7.0 Issue ID : If the configuration utilities of the SVM and Repeater are opened at the same time in the same browser session, both log out automatically. Workaround: To access both the configuration utility at the same time, log on through different browser sessions. Issue ID : Not all Branch Repeater instances are updated with domain information. Only a few instances are added to the domain. Workaround: Attempt to join the domain again. Issue ID : When you update the virtual server (VIP) address from the GUI, the persistence rule is removed. Workaround: Run the following commands on NetScaler command line: rm lb vserver BR_LB_VIP_SIG add lb vserver BR_LB_VIP_SIG ANY <NS_SIG_IP> * -timeout rule client.tcp.repeater_option.ip -Listenpolicy "SYS.VSERVER(\"BR_LB_VIP_SIG \").STATE.EQ(UP)&&CLIENT.TCP.REPEATER_OPTION.EXISTS" - clttimeout l2conn ON bind lb vserver BR_LB_VIP_SIG BR_LB_SVC_<1> bind lb vserver BR_LB_VIP_SIG BR_LB_SVC_<2> bind lb vserver BR_LB_VIP_SIG BR_LB_SVC_<3> bind lb vserver BR_LB_VIP_SIG BR_LB_SVC_<4> bind lb vserver BR_LB_VIP_SIG BR_LB_SVC_<5> bind lb vserver BR_LB_VIP_SIG BR_LB_SVC_<6> bind lb group BR_LB_GROUP BR_LB_VIP_SIG Issue ID : Independent Network Configuration [INC] mode is not supported between BR-SDX/CB-SDX ( 4000/5000) appliances in an HA pair. Issue ID : Traffic sent from the NetScaler appliance to the router is not GRE encapsulated in the case of UDP inner fragmentation. Issue ID : The NetScaler appliance does not synchronize the configurations between HA partners if the appliances are on different builds of the same release. Workaround: Disable synchronization before upgrade and complete the following procedure: a. Disable HA Synchronization on the secondary appliance. Navigate to Configuration > System > High Availability. Clear the Secondary node will fetch the configuration from the primary check box. Save the running configuration. b. Upgrade the secondary appliance. c. Upgrade the primary appliance. d. The secondary appliance becomes the primary appliance. e. Enable HA synchronization on the new primary appliance: Navigate to Configuration > System > High Availability. 14

15 7.0 Release Notes Select the Secondary node will fetch the configuration from the primary check box. Save the running configuration. Issue ID : When the Management service is upgraded, SVM displays an error message even when the upgrade is successful. Compatibility Workaround: Ignore the error message and start a new session. The following table lists the supported products and platforms in release 7.0. Table 1-2. Supported Products and Platforms Appliance Type 2000 and 3000 series VPX for Amazon 4000 and 5000 series VPX (all models) 600 series VPX for XenServer platforms VPX for VMware ESX or ESXi platforms VPX for Microsoft Hyper-V 700 series Plug-in Repeater 8000 Series (New appliances): Units that list SM85 Series 3 or SM88 Series 3 on the System Hardware line of the System Status page Repeater 8000 Series (Earlier appliances): Units that list SM85 Series 2 or SM88 Series 2 on the System Hardware line of the System Status page Earlier Models Supported? Yes Yes Yes* Yes Yes Yes Yes Yes Yes Yes Yes No No * recommends that you contact technical support for more details before you upgrade your 4000 and 5000 appliances to this release. The following table lists the version matrix of release

16 7.0 Table 1-3. Version Matrix Versions NetScaler Version Management Service Version XenServer Version Supplemental Pack 7.0 ( 4000 and 5000) 7.0 ( 2000 and 3000) e e p 1.2 N/A e p 1.3 Plug-in Compatible Operating Systems The Plug-in is supported on desktop and laptop systems, but not on netbooks or thin clients. It is supported on the following operating systems: Windows 8 (32-bit and 64-bit versions of Enterprise Edition) Windows 7 (all 32-bit and 64-bit versions of Home Basic, Home Premium, Professional, Enterprise, and Ultimate) Windows Vista (all 32-bit versions of Home Basic, Home Premium, Business, Enterprise, and Ultimate) Windows XP Professional and Home edition Hardware Requirements The recommended hardware specifications for systems running Plug-in are: Pentium 4-class CPU 4 GB of RAM 2 GB of disk space Minimum hardware requirements for Plug-in are: 1.5 Ghz CPU 2 GB RAM 500 MB free disk space 16

17 7.0 Release Notes Plug-in and Receiver The Plug-in is supported by Receiver 3.0 and later, and can be distributed and managed by Receiver. Features Table Table 1-4. Features Table for 600, 700, 2000, and 3000 series appliances 600 series 700 series 2000 series 3000 series Release 7.0 Y Y Y Y Product Features Video Caching Y N Y N TCP Acceleration Y Y Y Y Compression Y Y Y Y Traffic Shaping Y Y Y Y XenApp/ XenDesktop Acceleration Windows Filesystem Acceleration SSL Acceleration Windows Outlook Acceleration Plug-In Support Pay-As-You- Grow Support Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N Y Y Y Y Y Y Hardware Features 17

18 series 700 series 2000 series 3000 series Network Bypass Card 10 Gbps Interfaces Y Y Y Y N N N N Fiber Support N N N Y LCD Front Panel Interface Support RS-232 Serial Interface Support Support for Initial Config over Network Y Y N N Y Y Y Y N N Y Y Modes Inline Y Y Y Y WCCP Y Y Y Y Virtual Inline Y Y Y Y Group Mode Y N Y Y High Availability Y N/R* Y Y VLANs Y N Y Y * = The accelerator portion of the product fails over seamlessly in high-availability mode, while the Windows Server portion does not. N/R = Not Recommended 18

19 7.0 Release Notes Table 1-5. Features Table for 4000 and 5000 series appliances, VPX, and VPX for Amazon 4000 series 5000 series VPX VPX for Amazon Release 7.0 Y* Y* Y Y Product Features Video Caching N N N N TCP Acceleration Y Y Y Y Compression Y Y Y Y Traffic Shaping XenApp/ XenDesktop Acceleration Windows Filesystem Acceleration SSL Acceleration Windows Outlook Acceleration Plug-In Support Pay-As-You- Grow Support Y Y Y N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N Y Y Y N Hardware Features Network Bypass Card 10 Gbps Interfaces Y Y N N Y Y ** N Fiber Support Y Y ** N 19

20 series 5000 series VPX VPX for Amazon LCD Front Panel Interface Support RS-232 Serial Interface Support Support for Initial Config over Network N N N N N N N N Y Y N N Modes Inline Y Y Y Y**** WCCP Y Y Y N Virtual Inline N/R N/R Y N Group Mode N N N N High Availability Y Y N N VLANs Y Y Y/Y/N*** N * recommends that you contact technical support for more details before you upgrade your 4000 and 5000 appliances to this release. ** = Depends on configuration of user-provided hardware. *** = If shown as three values, support is for XenServer/VMware/Hyper-V, respectively. If shown as one value, this value applies to all three hypervisors. **** = Refer WAN Optimization for. N/R = Not Recommended Table 1-6. Features Table for Repeater appliances and Plug-in Repeater 8820 Repeater 8520, 8540 Plug-In Release 7.0 Y Y Y Product Features 20

21 7.0 Release Notes Repeater 8820 Repeater 8520, 8540 Plug-In Video Caching N N N TCP Acceleration Y Y Y Compression Y Y Y Traffic Shaping Y Y N XenApp/ XenDesktop Acceleration Windows Filesystem Acceleration Y Y Y Y Y Y SSL Acceleration Y Y Y Windows Outlook Acceleration Plug-In Support Pay-As-You-Grow Support Y Y Y Y Y Y Y Y N Hardware Features Network Bypass Card Y Y N 10 Gbps Interfaces N N * Fiber Support Y N * LCD Front Panel Interface Support RS-232 Serial Interface Support Support for Initial Config over Network Y Y N Y Y N N N N Modes Inline Y Y N/A WCCP Y Y N/A Virtual Inline Y Y N/A 21

22 7.0 Repeater 8820 Repeater 8520, 8540 Plug-In Group Mode Y Y N/A High Availability Y Y N/A VLANs Y Y N/A * = Depends on configuration of user-provided hardware. N/A = Not Applicable Supported VPX Configurations Release 7.0 is supported on 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-7. Hypervisors Compatible with VPX XenServer XenServer 6.1, XenServer 6.02/Hotfix 602E007, XenServer (but not 5.6 FP1 or 5.6 SP2), XenServer 5.5 VMware Vsphere ESXi 5.1, ESXi 5.0, ESX/ESXi 4.1 Microsoft Hyper-V VPX for Amazon Hyper-V under Windows 2008 R2 SP1, Hyper-V 2012 Standard and Datacenter Edition Amazon Web Services (AWS) platform For instructions for changing the TSC emulation to maximize performance, see support.citrix.com/article/ctx VPX for Amazon VPX for Amazon is available only in the m1.large configuration. This translates to 2 vcpus and 7.5 GB RAM. The AMI is preconfigured with a 250 GB volume, which should not be resized. VPX for Amazon supports a single Elastic Network Interface (ENI) only. Table 1-8. Production Configurations, VPX for Amazon Type Max. WAN Speed* Max. Accel. Conn. 10 Mbps License 5 mbps 1, Mbps License 45 mbps 10,000 22

23 7.0 Release Notes *The Connector License is enforced on the aggregate of ingress traffic on all the interfaces hosted on the Connector. Table 1-9. Production Configurations, XenServer and VMware vsphere. Type vcpus RAM Disk Max. WAN Speed Max. Accel. Conn. Max. CloudBridg e Plug-Ins 2 GB production config. 4 GB production config. 4 GB production config.* 8 GB production config. 2 2 GB 100 GB 2 mbps 1, GB 250 GB 10 mbps 10, GB 250 GB 45 mbps 15, GB 500 GB 45 mbps 25, * With 45mbps license Table Other Configurations (not for production networks). Type vcpus RAM Disk Max. WAN Speed Max. Accel. Conn. Max. CloudBrid ge Plug- Ins VPX Express 2 1 GB 60 GB 512 kbps 10 5 Licensing, Upgrading, and Downgrading Licensing Release 7.0 supports both remote license servers and locally installed licenses. If you upgrade an existing system with a local license, it continues to work. For licensing information for all platforms, see support.citrix.com/article/ctx

24 7.0 Note: Licensing for VPX for Amazon uses the Connector license. It does not require a separate license. Upgrading Existing Installations Note: If you are using a standard evaluation license, you cannot upgrade to software versions that are newer than your license. VPX If you are upgrading from release 5.6, it is best to install a new virtual machine, rather than upgrading the existing virtual machine with the release, because the resource requirements have changed. Release 6.0 virtual machines can be updated with the release 6.2 binary. Repeater 8500, Repeater 8800, 600, 700, 4000 and 5000 Acquire the software from My. Installing the Update Note: If you are upgrading from a pre-6.0 release (such as release 5.3), you must update to release 6.x first, then release 7.0. Also, if you are upgrading from a pre-6.0 release, acceleration will not take place until you install the new license from. From the browser based user interface ( go to the System Maintenance > Update Software link, on the Configuration tab. In the Upgrade System Software table, use the Choose File button to select the patch file (the file you downloaded with FTP), and then press the Upload Patch button. (See the following figure.) 24

25 7.0 Release Notes Figure 1-1. Update Software Page The patch file is then copied to your appliance and tested for integrity. If you have downloaded a valid file, a Restart Unit? prompt appears. Click Yes. The settings from your current release are copied to the new one, so your configuration is retained in the new release. The process of installing the patch file continues during the restart, which might take several minutes longer than usual. This is normal. The new release is now running on your Appliance. Note: If your appliance still uses the old default password, it is changed when you install this upgrade. The default password is now password" and 3000 Release is the initial release of the software. To upgrade to release 7.0, perform the following procedure on a 2000 or 3000 appliance. 1. In the configuration utility, select System from the System/ dropdown menu. 2. Navigate to the System > Configuration > Management Service > Software Images page and upload the management service software image by clicking Upload, as shown in the following figure. 25

26 Navigate to System > Configuration > System > Upgrade Management Service and upgrade the Service VM (SVM). 4. From the System/ dropdown menu, select. 5. Navigate to Configuration > System Maintenance, and select Update Software. 6. In the Upgrade System Software table, click Choose File, select a patch file, and then click Upload Patch. 26

27 7.0 Release Notes The patch file is then copied to your appliance and tested for integrity. If you have downloaded a valid file, a Restart Unit? prompt appears. 7. At the Restart Unit? Prompt, click Yes. Note: After the clock timer goes to zero, navigate to System > Configuration> > Instances and click on Rediscover. The settings from your current release are copied to the new one, and your configuration is retained in the new release. The process of installing the patch file continues during the restart, which might take several minutes longer than usual. When the above procedure is completed, your 2000 or 3000 appliance has the new Service VM and release and 5000 series To upgrade 4000 and 5000, see Managing the Appliance. 27

28 7.0 Note: recommends that you contact technical support for more details before you upgrade your 4000 and 5000 appliances to this release. 700 series To upgrade a 700 appliance, see the Branch Repeater with Windows Server User's Guide, release 3.0, chapter 3. Troubleshooting Installation Related Issues The clockface showing the estimated update time is not always 100% accurate. If the installation ends with an error page displaying some kind of HTTP timeout error, wait a few minutes, and then attempt to connect to the unit s browser based management interface normally. Doing so usually shows that the newly installed version is up and running. Sometimes an update fails if it spans a large number of releases, such as a jump from release 4.x to 6.0. If this happens, installing an intermediate release first (for example, release 5.5) and upgrading in two steps usually works. Contact Support with any installation issues. Troubleshooting Installation Related Issues for VPX for Amazon For information about troubleshooting installation related issues for VPX for Amazon, see WAN Optimization for. Downgrading to an Earlier Release Upgrading creates a new software installation; it does not remove the previous version of the software or the previous configuration settings. Therefore, an Appliance can be returned to any release that it has previously used. You can revert to a previous version of the software by using the Downgrade Release feature, which is available on the System Maintenance: Update Software page. The downgrade returns 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 are lost. If you upgrade again, the upgrade copies the older release s settings into the newer release. The software can be downgraded to previously installed versions only. 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. Note: You cannot downgrade a 4000 or 5000 appliance to an earlier release. 28

29 7.0 Release Notes Contacting Customer Support To contact Support, call CITRIX or log on to My at You will be asked for your hardware serial number as part of the support process. Detailed instructions for contacting support can be found at: resources/dynamic/sup2nd/_hws_serialno.pdf. 29