Aspera Server

 

Copyright © 2002-2017 KEMP Technologies, Inc.. All rights reserved.. KEMP Technologies and the KEMP Technologies logo are registered trademarks of KEMP Technologies, Inc..

Limitations: This document and all of its contents are provided as-is. KEMP Technologies has made efforts to ensure that the information presented herein are correct, but makes no warranty, express or implied, about the accuracy of this information. If any material errors or inaccuracies should occur in this document, KEMP Technologies will, if feasible, furnish appropriate correctional notices which Users will accept as the sole and exclusive remedy at law or in equity. Users of the information in this document acknowledge that KEMP Technologies cannot be held liable for any loss, injury or damage of any kind, present or prospective, including without limitation any direct, special, incidental or consequential damages (including without limitation lost profits and loss of damage to goodwill) whether suffered by recipient or third party or from any action or inaction whether or not negligent, in the compiling or in delivering or communicating or publishing this document.

Portions of this software are; copyright (c) 2004-2006 Frank Denis. All rights reserved; copyright (c) 2002 Michael Shalayeff. All rights reserved; copyright (c) 2003 Ryan McBride. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE ABOVE COPYRIGHT HOLDERS ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of the above copyright holders..

Portions of the LoadMaster software are copyright (C) 1989, 1991 Free Software Foundation, Inc. -51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA- and KEMP Technologies Inc. is in full compliance of the GNU license requirements, Version 2, June 1991. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Portions of this software are Copyright (C) 1988, Regents of the University of California. All rights reserved.

Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Portions of this software are Copyright (C) 1998, Massachusetts Institute of Technology

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Portions of this software are Copyright (C) 1995-2004, Jean-loup Gailly and Mark Adler

This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution.

Portions of this software are Copyright (C) 2003, Internet Systems Consortium

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Used, under license, U.S. Patent Nos. 6,473,802, 6,374,300, 8,392,563, 8,103,770, 7,831,712, 7,606,912, 7,346,695, 7,287,084 and 6,970,933

1Introduction

The Aspera Server enables a large number of users to exchange files over a Wide Area Network (WAN). Utilising FASP© technology at its core, the Aspera Server delivers unmatched performance and includes all the exceptional transfer and user management capabilities of the industry standard Enterprise Server and Connect Server.

The KEMP LoadMaster is able to load balance the Aspera Server workload. The LoadMaster offers advanced Layer 4 and Layer 7 server load balancing, SSL Acceleration and a multitude of other advanced Application Delivery and Optimization (ADC) features. The LoadMaster intelligently and efficiently distributes user traffic among the application servers so that users get the best experience possible.

1.1Document Purpose

This document provides guidance on how to deploy Aspera Server with a KEMP LoadMaster. The KEMP Support Team is available to provide solutions for scenarios not explicitly defined.

The KEMP support site can be found at: https://support.kemptechnologies.com.

1.2Intended Audience

This document is intended for use by anyone deploying Aspera Server with a KEMP LoadMaster.

2Aspera Server Template

KEMP has developed a template containing our recommended settings for Aspera Server. This template can be installed on the LoadMaster and used when creating Virtual Services. Using a template automatically populates the settings in the Virtual Services. This is quicker and easier than manually configuring each Virtual Service. If needed, changes can be made to any of the Virtual Service settings after using the template.

Download released templates from the Templates section on the KEMP documentation page: http://kemptechnologies.com/documentation/.

For more information and steps on how to import and use templates, refer to the Virtual Services and Templates, Feature Description

For steps on how to manually add and configure each of the Virtual Services, refer to the Configure Aspera Server Virtual Services section of this document.

The Port Following settings are not configured by the template. Refer to Section 4.3 on how to configure Port Following.

 

3Architecture

4Configure Aspera Server Virtual Services

4.1Enable Subnet Originating Requests Globally

It is best practice to enable the Subnet Originating Requests option globally.

In a one-armed setup (where the Virtual Service and Real Servers are on the same network/subnet) Subnet Originating Requests is usually not needed. However, enabling Subnet Originating Requests should not affect the routing in a one-armed setup.

In a two-armed setup where the Virtual Service is on network/subnet A, for example, and the Real Servers are on network B - Subnet Originating Requests should be enabled on LoadMasters with firmware version 7.1-16 and above.

When Subnet Originating Requests is enabled, the LoadMaster will route traffic so that the Real Server will see traffic arriving from the LoadMaster interface that is in that network/subnet.

When Subnet Originating Requests is enabled globally, it is automatically enabled on all Virtual Services. If the Subnet Originating Requests option is disabled globally, you can choose whether or not to enable Subnet Originating Requests on a per-Virtual Service basis.

To enable Subnet Originating Requests globally, follow the steps below:

  1. In the main menu of the LoadMaster WUI, go to System Configuration > Miscellaneous Options > Network Options.

Figure 4‑1: Subnet Originating Requests

  1. Select the Subnet Originating Requests check box.

4.2Create the Aspera Virtual Services

The following sections describe the recommended settings for the Aspera Virtual Services.

4.2.1Aspera HTTPS Virtual Service

The following are the steps involved and the values recommended to configure the Aspera HTTPS Virtual Service:

  1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services> Add New.

Figure 4‑2: Virtual Services Parameters

  1. Type a valid IP address in the Virtual Address text box.
  2. Type 443 in the Port text box.
  3. Enter a recognizable Service Name, for example Aspera HTTPS Server.
  4. Ensure tcp is selected as the Protocol.
  5. Click Add this Virtual Service.
  6. Enter the details shown in the following table.

Section

Option

Value

Comment

Standard Options

Persistence Mode

Source IP Address

 
 

Timeout

6 Minutes

 
 

Scheduling Method

least connection

 

Advanced Properties

Add a Port 80 Redirector VS

https://%h%s

Click Add HTTP Redirector. This automatically creates a redirect on port 80.

Table 4‑1: Aspera HTTPS Server Virtual Service Settings

  1. Add the Real Servers:

a)Expand the Real Servers section.

b)Click Add New.

c)Type the address of the Aspera HTTPS Server.

d)Type 443 as the Port.

The Real Server Port should match the Virtual Service Port.

The Forwarding method and Weight values are set by default. An administrator can change these.

e)Click Add this Real Server. Click OK to the pop-up message.

f)Repeat the steps above to add more Real Servers as needed, based on the environment.

Create an Aspera HTTPS Virtual Service Offloaded HTTP Redirect Virtual Service

Clicking the Add HTTP Redirector button automatically creates a port 80 redirect Virtual Service. This is optional, but the purpose of this Virtual Service is to redirect any clients who have connected using HTTP to the HTTPS Virtual Service. KEMP also recommends changing the Real Server Check Method and Persistence Mode to None.

4.2.2Aspera HTTPS-Failback Virtual Service

The following are the steps involved and the values recommended to configure the Aspera HTTPS-Failback Virtual Service:

  1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services> Add New.

Figure 4‑3: Virtual Services Parameters

  1. Type a valid IP address in the Virtual Address text box.
  2. Type 8443 in the Port text box.
  3. Enter a recognizable Service Name, for example Aspera HTTPS-Failback.
  4. Ensure tcp is selected as the Protocol.
  5. Click Add this Virtual Service.
  6. Enter the details shown in the following table:

Section

Option

Value

Standard Options

Transparency

Enabled

 

Persistence Mode

Source IP Address

 

Timeout

6 Minutes

 

Scheduling Method

least connection

Real Servers

Checked Port

8443

Table 4‑2: Aspera HTTPS-Failback Virtual Service Settings

  1. Add the Real Servers:

a)Expand the Real Servers section.

b)Click Add New.

c)Type the address of the Aspera HTTPS-Failback Server.

d)Type 8443 as the Port.

The Real Server Port should match the Virtual Service Port.

The Forwarding method and Weight values are set by default. An administrator can change these.

e)Click Add this Real Server. Click OK to the pop-up message.

f)Repeat the steps above to add more Real Servers as needed, based on the environment.

4.2.3Aspera FASP UDP Virtual Service

The following are the steps involved and the values recommended to configure the Aspera FASP UDP Service:

  1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services> Add New.

Figure 4‑4: Virtual Services Parameters

  1. Type a valid IP address in the Virtual Address text box.
  2. Type * in the Port text box.
  3. Enter a recognizable Service Name, for example Aspera FASP UDP.
  4. Ensure udp is selected as the Protocol.
  5. Click Add this Virtual Service.
  6. Enter the details shown in the following table.

Section

Option

Value

Standard Options

Force L4

Disabled

 

Persistence Mode

Source IP Address

 

Timeout

6 Minutes

 

Scheduling Method

least connection

Table 4‑3: Aspera FASP UDP Virtual Service Settings

  1. Add the Real Servers:

a)Expand the Real Servers section.

b)Click Add New.

c)Type the address of the Aspera FASBUDP Server.

d)Type * as the Port.

The Real Server Port should match the Virtual Service Port.

The Forwarding method and Weight values are set by default. An administrator can change these.

e)Click Add this Real Server. Click OK to the pop-up message.

f)Repeat the steps above to add more Real Servers as needed, based on the environment.

4.2.4Aspera FASP Virtual Service

The following are the steps involved and the values recommended to configure the Aspera FASP Virtual Service:

  1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services> Add New.

Figure 4‑5: Virtual Services Parameters

  1. Type a valid IP address in the Virtual Address text box.
  2. Type 33001 in the Port text box.
  3. Enter a recognizable Service Name, for example Aspera FASP.
  4. Ensure tcp is selected as the Protocol.
  5. Click Add this Virtual Service.
  6. Enter the details shown in the following table.

Section

Option

Value

Basic Properties

Service Type

HTTP/HTTPS

Standard Options

Persistence Mode

Source IP Address

 

Timeout

6 Minutes

 

Scheduling Method

least connection

Advanced Properties

Port Following

No VIP Selected

 

Add HTTP Headers

Legacy Operation(X-ClientSide)

Real Servers

Checked Port

33001

Table 4‑4: Aspera HTTPS Server Virtual Service Settings

  1. Add the Real Servers:

a)Expand the Real Servers section.

b)Click Add New.

c)Type the address of the Aspera FASP Server.

d)Type 33001 as the Port.

The Real Server Port should match the Virtual Service Port.

The Forwarding method and Weight values are set by default. An administrator can change these.

e)Click Add this Real Server. Click OK to the pop-up message.

f)Repeat the steps above to add more Real Servers as needed, based on the environment.

4.3Port Following

Port following must be set on both Virtual Services as follows and is explained in detail in the following sections.

4.3.1Configure Port Following for the Aspera TCP Virtual Service

To configure port following for the Aspera TCP Virtual Service, follow the steps below:

  1. In the main menu, go to Virtual Services>View/Modify Services.
  1. Click Modify for the Aspera TCP Virtual Service which you created in Section 4.2.
  2. Expand the Advanced Properties section.

Figure 4‑6: Configure Port Following for the Aspera Server TCP Virtual Service

  1. Select the Aspera Server UDP Virtual Service from the Port Following drop-down list.
  2. Wait 10 seconds, or uncheck and check the Activate or Deactivate Service checkbox in the Basic Properties section for immediate activation.

4.3.2Configure Port Following for the Aspera TCP Virtual Service

To configure port following for the Aspera TCP Virtual Service, follow the steps below:

  1. In the main menu, go to Virtual Services>View/Modify Services.
  1. Click Modify for the Aspera Server TCP Virtual Service which you created in Section 4.2.2.
  2. Expand the Advanced Properties section.

Figure 4‑7: Configure Port Following for the Aspera Server UDP Virtual Service

  1. Select the Aspera TCP Virtual Service from the Port Following drop-down list.
  2. Wait 10 seconds, or uncheck and check the Activate or Deactivate Service checkbox in the Basic Properties section for immediate activation.

References

Unless otherwise specified, the following documents can be found at: http://kemptechnologies.com/documentation.

Virtual Services and Templates, Feature Description High Availability (HA), Feature Description

Document History

Date

Change

Reason for Change

Version

Resp.

Nov 2016

Initial Draft

First draft of document

1.0

POC

Jan 2017

Minor changes

Updated

2.0

LB

Was this article helpful?

0 out of 0 found this helpful

Comments