How to add a custom Vlink for multiple subnets

Description

A Vlink (virtual link) is a “virtual” aggregate bandwidth cap that can be applied to transfer sessions. It is also possible to add a Vlink to transfer sessions across multiple subnets. You can apply such a Vlink by editing your aspera.conf file, as in the instructions below.

The instructions assume you already have an existing Vlink applied on some transfers. For more instructions on how to create a Vlink, see https://support.asperasoft.com/entries/93918158-How-to-create-a-Vlink. For more instructions on how to apply a Vlink to transfers, see https://support.asperasoft.com/entries/93919868-How-to-apply-a-Vlink-to-your-transfers.

Instructions

The location of aspera.conf depends on your system and may be found in:

  • Linux: /opt/aspera/etc
  • Windows: C:\Program Files (x86)/Aspera/<product name>/etc (replace <product name> with your installed product)
  • Mac: /Library/Aspera/etc

Open this file in a text editor. Locate the Vlink you want to configure for multiple subnets, which will be specified by its Vlink ID within a <trunk_id> tag. See this Knowledge Base article for instructions if you need to create your Vlinks. Below is an example:

<trunks>
...
<trunk>
<id>201</id>
<name>local</name>
<capacity>
<schedule format="ranges">50000</schedule>
</capacity>
<on>true</on>
</trunk>
<id>202</id>
<name>local</name>
<capacity>
<schedule format="ranges">800000</schedule>
</capacity>
<on>true</on>
</trunk>

 <id>203</id>
<name>local</name>
<capacity>
<schedule format="ranges">300000</schedule>
</capacity>
<on>true</on>
</trunk>

</trunks>

You specify a subnet on a Vlink by using the peer_ip qualifier in the Vlink's <trunk_id> tag. Add a <trunk_id> tag with the peer_ip setting for each subnet you want to include. For instance, in the following we aggregate 3 subnets to different Vlinks with IDs 201, 202 and 203, and so include a <trunk_id> for each subnet:

<transfer>
            <in>
                <bandwidth>
                    <aggregate>
                        <trunk_id peer_ip="10.0.1.0/24">201</trunk_id>
                        <trunk_id peer_ip="10.2.72.0/24">202</trunk_id>
                        <trunk_id peer_ip="10.0.45.0/24">203</trunk_id>
                    </aggregate>
                </bandwidth>
            </in>
<out>
                <bandwidth>
                    <aggregate>
                        <trunk_id peer_ip="10.0.1.0/24">201</trunk_id>
                        <trunk_id peer_ip="10.30.2.0/24">202</trunk_id>
                        <trunk_id peer_ip="10.66.34.0/24">203</trunk_id>
                    </aggregate>
                </bandwidth>
            </out>
</transfer>
Note that if you want to target ONE specific IP address, you can omit the network mask portion, or use the mask /32, such as: 10.0.23.134/32.

After saving your changes in aspera.conf, ensure you have edited it correctly by running a validation command to check for errors. Use one of the following depending on your system.

For Mac OSX:

/Library/Aspera/bin/asuserdata -v  

For Windows: 

"C:\Program Files (x86)\Aspera\Enterprise Server\bin\asuserdata" -v 

For Linux:

/opt/aspera/bin/asuserdata -v
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk