Signiant Control is a command line tool used to interact with Signiant applications. You can use Signiant Control, which is included in the SDCX Server deployment, to test your firewall configuration.
Testing using Signiant Control should be done prior to connecting servers via a route, and testing using the Jet management console.
You must stop all SDCX services on your local computer before running tests with Signiant Control.
To stop SDCX services:
Linux: In your terminal, run > sudo siginit stop.
Windows: In the Services control panel, right-click on any Signiant services and choose Stop.
To start SDCX services after testing:
Linux: In your terminal, run > sudo siginit start.
Windows: In the Services control panel, right-click on any Signiant services and choose Start.
Testing your firewall requires two SDCX servers, one running as the server and the other as a client, connecting to the server.
The server endpoint reports statistics related to the test, including the test duration, the number of files sent as part of testing, and the overall bit rate. Once the FILES and BITES statistics stop increasing in value, the test has completed.
Note: Signiant Control tests use diskless transfers to simulate transfer jobs. No files are read or written during the test.
To start an endpoint in server mode:
Stop all SDCX services:
Linux: sudo siginit stop
Windows: Stop all Signiant services from the Services control panel
At the command line, navigate to Signiant Control's install directory.
Linux: /usr/local/bin/
Windows: C:\Program Files\Signiant\Flight Gateway\
Start Signiant Control in server mode:
Linux: ./sigctl -test jet -server
Windows: sigctl.exe -test jet -server
To start an endpoint in client mode:
Stop all SDCX services:
Linux: sudo siginit stop
Windows: Stop all Signiant services from the Services control panel
Start the Signiant Communication Service:
Linux: sudo siginit start sigmsg
Windows: Start the Signiant Communication Service from the Services control panel
At the command line, navigate to Signiant Control's install directory.
Linux: /usr/local/bin/
Windows: C:\Program Files\Signiant\Flight Gateway\
Start Signiant Control in client mode:
Linux: > ./sigctl -test jet -client <server ip>
Windows: > sigctl.exe -test jet -client <server ip>
Signiant Control cannot be used for a full end-to-end test between source and destination through a relay server.
To test a relay implementation, run the connection test between the source and relay using the source as the client and relay as the server. Once completed, run another test with the relay as the client and destination as the server.
The following tests are run by the client as part of the test suite:
| Test name | Description |
|---|---|
| Jet Open Host Check | Checks if Jet services are available |
| Server Hostname Address Lookup | Checks if the server can be reached |
| Server Runtime CPU Count | Checks the number of available CPUs on the server |
| Server Runtime Memory Count | Checks the total available memory on the server |
| Jet Open TCP Port Check | Checks TCP ports 49221 and 50221 |
| Jet Open UDP Single-Port Check | Checks UDP ports 49221 and 49321 |
| Jet Open UDP Multi-Port Check | Checks UDP ports 49222 to 49320 and 49322 to 49421 |
| Jet Open UDP Port Loopback Check | Checks UDP ports 50222-50421 for loopback network interface |
| UDP MTU Path Check | Checks the maximum UDP MTU to the storage server |
| Network Latency Test | Checks overall network performance |
| Network Speed Test | Checks average connection speed |
| Storage Performance Check | Checks disk read and write speeds |
If a test fails on the client, ensure that the SDCX server is connected to your network, can reach the Internet, and that the network firewall is configured according to system requirements.
If the server fails with Error: server failed to run: listen tcp 0.0.0.0:50221: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted, another service is using a port required by the test. Ensure all Signiant services are stopped before beginning the test.
For more information on Operating System firewall troubleshooting, see Deployment Troubleshooting.