Configuring Agent Network Settings

On the Network tab, you can specify preferences such as source and destination port ranges, relays, and tunnels.

To add or edit Agent network settings:

  1. Navigate to Administration > Agents > List.
  2. Select an Agent and click Edit. The same settings can be applied to multiple Agents at once by selecting the Agents to edit and clicking Edit Multiple.
  3. Define settings on the Network tab.


  • IP Interface: Enter the IP interface (NIC) on which the Agent should send or receive traffic. This field is left blank by default. If the Agent is in a clustered environment, you must enter the cluster virtual IP address for each node of the cluster where the Agent has been installed. If you have multi-Manager Agents running UDP transfers, you must enter the Ethernet card address of the interface you want to use in the IP Interface field. If transferring over UDP, you must restart the UDP service manually after specifying an IP Interface value.
  • Use UDP To Configure Agent: Specify that all Agent configuration communication to the Agent from the Manager be done over UDP. This feature allows firewall administrators to open the port for this communication as UDP. Using UDP for job control communication is set separately as part of the job configuration.
  • UDP Payload Size (bytes): Enter the maximum size for a UDP packet in bytes.
  • Process Control Port: Define the port the process controller uses to monitor data transfers. The default port is 49221.
  • UDP Burst Quantum: This parameter can be used to override the default behavior of the Agent with respect to packet timing. Adjustments to this parameter should not be made without assistance from Signiant Support.

Note: Clustered or high-availability (HA) Manager installations is no longer supported for Manager software installations. For information about converting from a clustered installation to a single Manager installation, see Removing Clustered Installations.

Port Options

The Port Options tab allows you to specify a source UDP port range and a destination UDP port range. This option allows customer networking equipment to pass response UDP packets. You can specify separate source and destination port ranges.

If you do not configure the Base Port and Port Range Size, both the origin and destination are set to off and the host operating system allocates the port numbers for session-originating sockets.

To configure port options:

  1. On the Network tab, select Port Options.

    • Base Port Default: Sets the lower port range as one port above the default source port. The default source port is 49222.
    • Base Port Specified: Sets a different lower port range from the default port of 49222. The specified port must be between 1 and 65534.

    Note: Values below 49152 generate a warning when saved, indicating that the port number is low and may conflict with other services.

  2. In the Port Range Size field, specify a port range. This value is required and must be at or above the default of 100.

    • To specify a different port range on the target, enable Different Destination Port Range. If this option is not enabled, the destination port is set to the same value as the origin.
    • Base Port Default: Sets the lower port range as one port above the default source port. The default source port is 49222.
    • Base Port Specified: Sets a different lower port range from the default port of 49222.


A relay allows you to create application layer routing rules that map Agent names to IP addresses. By default, relays are not enabled. If Agents cannot communicate directly with one another, a relay directs the Agents to contact an IP address and TCP port that can in turn direct the communication to the appropriate Agent. For example, Agents may need to communicate through a firewall or another Agent that is able to communicate with both Agents, or you may need to resolve an Agent name to an alternate IP address when you cannot resolve the Agent's fully qualified domain name locally.

You can add data transfer system relays to Agents either by creating common relays that are included with all Agent software installations, as part of the installation information file, or by adding relays to an individual Agent using the Configure menu. You can run a UDP connection through a relay, unless the relay uses a tunnel, as UDP does not work with tunnels.

To configure Agent relays:

  1. On the Network tab, select Relays.

  2. Select Enable this agent to act as a relay.

  3. To specify the target Agent for the relay, click Add Destination.

  4. Select a destination Agent, or select Any Destination.

  5. Click Add Relay.

  6. Specify up to four relay Agents in the Relay Address field, or choose the Agent(s) from the drop-down menu.

    • Use * or \* to apply the relay definition to all remote Agents, except the local Agent itself.
    • Use *.subdomain (e.g. * to apply the relay definition to all remote Agents within the specified subdomain, except the local Agent itself.
    • In the Via this Hostname/IP field, use to refer to the relay host itself. Use 0 for the Via this Port to use the default port.

    After saving and closing the dialog, the Agent name displays as an IP address.

  7. Accept the default port number for the TCP port of the relay Agent, or specify a different number in the Port field. To run a UDP connection through a relay, specify the UDP port number. You can specify only one UDP relay per connection path.

To remove a relay rule from an Agent, select the relay rule to remove and click Delete.

Note: Including relay rules can impact file transfer performance.

Configuring an Agent Relay for Flight

Flight can be used with an Agent relay when the Signiant Flight client server does not have direct access to the Internet. In this configuration, the Flight client connects to an Agent relay deployed within the organization's perimeter network, which connects to Signiant Cloud Services. No data is written to disk on the relay. The content is only sent through Signiant Cloud Services.

When an Agent is only used for relaying, 30 simultaneous connections are available, and Flight uploads and downloads can occur simultaneously. If the Agent is a relay and a transfer endpoint, the Agent's relaying capacity is reduced.

By default, outbound UDP connections from the Agent relay use the 49221-49421 port range. To use the Agent relay with Flight, you must restrict the outbound UDP traffic to a single port (49221). This change impacts all UDP traffic, sending both Flight and non-Flight traffic over a single port, regardless of destination.

To configure an Agent relay:

Flight Gateway

  1. Configure the Agent to act as a relay.
  2. In your Manager, navigate to Flight > Flight Uploads and/or Flight Downloads.
  3. Select a Flight job from the list and click Edit.
  4. In the Transport Options section on the Advanced tab, select one or more Relay Agents to use.

Flight CLI

  1. Specify one or more Agent relays in the configuration file or on the command line:

    sigcli --relay <relay_URL>

  2. In your Manager, enable the Web Transfer API with default settings and set an authentication method for the Agent relay.


A tunnel allows remote Agents located behind uni-directional firewalls to securely communicate with Agents outside the firewall. A tunnel is established between specified Agents in the sigsetup.inf file by default during Agent installation. Usually the Manager is one of these Agents, although users can specify other default tunnels applied to all Agents by editing the default Agent configuration during installation. Only TCP transfers are supported when using tunnels.

To configure Agent tunnels:

  1. On the Network tab, select Tunnels
  2. Click Add.
  3. In the Tunnel Endpoint field, select an Agent, or enter the fully-qualified domain name of the Agent, to which you want to create a tunnel.

To add a tunnel to an Agent through the command line:

  1. On the Remote Access tab, enable Advanced.
  2. Click Add and select the Agent which is going to tunnel itself back to the Manager.
  3. In Job Environment region, choose the default value for how the job should run on the Manager (nt authority\system Windows or root on Linux).
  4. Click Apply.


You can specify an HTTP protocol server and an external port when communicating outside a firewall. Select Enable HTTP Protocol Server and Register External Port and specify the port number for each on the proxy Agent.

Note: You cannot set the port number to 80 or 443 as these ports must remain available to the Manager.


The Manager Event Broker is a Signiant service that allows the Manager to monitor non-native jobs among a set of specified Agents. A message broker running on each Signiant Agent enables communication between the Event broker and the Agent on which the event broker is enabled: Agents publish events to the message broker (that the Event broker is monitoring) and receive commands from the Manager. The primary Agent and the secondary Agent will both publish events to the Agent message broker service, but only the secondary will receive commands via the Agent message broker.

By default the Event Broker is enabled and configured with default values.

On the Events tab you can define the Event Time to Live (hours), which specifies the number of hours the event message is kept.

To view Managers connected to the Agent, click Show.

To disconnect a client from the Agent, select an Agent in the list, and click Disconnect. Enable the option in the Disconnect dialog to remove the Manager as a permitted Agent in the Access Entity on the Agent's Remote Access tab.


Job monitoring allows you to check the status of external Agent to Agent jobs, and Content Transfer Engine jobs via the Agent list. Specific monitoring can be enabled for one or both job types to monitor external jobs associated with an Agent.

Monitoring is available for all job types, except jobs that have been initiated by the monitoring Manager, or jobs that do not have the necessary details in the job event and statistics record to generate a job record on the Manager.

Agent Monitoring Status

An Agent's external job monitoring status is displayed on the Agent list:

  • Connected - Monitoring external jobs.
  • Disconnected - The monitoring Agent is disconnected and cannot monitor external jobs.
  • Error - Monitoring Authorization Error.
  • Retrying Connection - Retrying connection to an external Agent.
  • Unknown Monitoring State - Monitoring state cannot be determined.

If the External Job Monitor column is empty, the Agent is not configured to monitor external jobs.

Disabling Monitoring

When Agents are configured for monitoring, you can enable monitoring in the View menu at Administration > Agents > List. Select Disconnect to disable monitoring. You can only disable monitoring for clustered Agents on the Agent's Network tab at Administration > Agents > List.

Was this page helpful?
About SigniantSigniant’s intelligent file movement software helps the world’s top content creators and distributors ensure fast, secure delivery of large files over public and private networks. Built on Signiant’s patented technology, the company’s on-premises software and SaaS solutions move petabytes of high-value data every day between users, applications and systems with proven ease.LEARN MORE