Aspera fasp

  • 1
  • Question
  • Updated 9 years ago
  • Answered
Any suggestions for the best ways for LANGuardian to monitor Aspera "fasp" traffic?
Photo of Nobby Smith

Nobby Smith

  • 1 Post
  • 0 Reply Likes

Posted 9 years ago

  • 1
Photo of Michael Finn

Michael Finn

  • 35 Posts
  • 5 Reply Likes
An Aspera server runs an SSH server, running on a default port TCP 22, this port can be changed for example port 33001 is commonly used. When a transfer is started by an Aspera client, the client opens an SSH session to the SSH server on the designated TCP port and negotiates the UDP port over which the data will travel. Again the clients and servers are configured to to use a UDP port 33001 by default however this is also configurable. Once the connection is established both the client and the server will send and receive UDP traffic on this designated port.

The LANGuardian can be configured to discover this traffic by

- Creating a Custom report based on a Sessions where Protocol equals UDP and Server port is set to 33001

Now this is sufficient to track Aspera usage where the default settings apply. However to track usage on servers where not standard UDP ports are used you need to be more creative and track UDP sessions where the source port is the same as the destination port

- Create a Custom report based on a Flow report where IP Protocol is set to UDP, Src Port and Server Port values are the same.

Aspera is basically a fast file transfer service so a further refinement may be that a check could be introduced to determine if sufficient volumes of data were transferred in the flow to indicate file transfer activity.