Global Bandwidth Settings (Command Line)

To configure global bandwidth preferences using asconfigurator commands, you first create a Vlink for each bandwidth setting and then assign the Vlink to the transfer. In the following example, Vlink 108 is used to limit the upload bandwidth (outgoing transfers) to 88 Mbps (88000 Kbps) and Vlink 109 is used to limit the download bandwidth (incoming transfers) to 99 Mbps (99000 Kbps).

# asconfigurator -x "set_trunk_data;id,108;trunk_capacity,88000;trunk_on,true"
# asconfigurator -x "set_trunk_data;id,109;trunk_capacity,99000;trunk_on,true"
# asconfigurator -x "set_node_data;transfer_in_bandwidth_aggregate_trunk_id,108"
# asconfigurator -x "set_node_data;transfer_out_bandwidth_aggregate_trunk_id,109"

The commands create the following lines in aspera.conf.

<?xml version='1.0' encoding='UTF-8'?>
<CONF version="2">
    <trunk>          <!-- Create a Vlink with 88000 Kbps bandwidth cap. -->
      <id>108</id>   <!-- ID: 108 -->
        <schedule format="ranges">88000</schedule>
    <trunk>          <!-- Create a Vlink with 99000 Kbps bandwidth cap. -->
      <id>109</id>   <!-- ID: 109 -->
        <schedule format="ranges">99000</schedule>

  <default>   <!-- Global settings.-->
      <out>   <!-- Use Vlink ID: 108 for global outgoing bandwidth. -->
      <in>    <!-- Use Vlink ID: 109 for global incoming bandwidth. -->

The capacity of the Vlink is set within a <schedule> tag because the capacity can be scheduled as one value during a specified time period, and a default value at all other times. For more information on this configuration, see the knowledge base article Specifiying a time varying schedule for a Vlink at

You can edit aspera.conf manually, rather than running asconfigurator commands, by opening the file with write permissions from the following location:


Validate the aspera.conf file using the asuserdata utility:
# /opt/aspera/bin/asuserdata -v