Details of command line parameters used by the SwitchCommandLine entry in the Tachyon Switch Host 's Tachyon.Switch.Host.exe.config file.

This page is for information only. Do not make configuration changes unless instructed to do so by 1E.

On this page:

Switch Command Lines

The Tachyon Switch Host has a Tachyon.Switch.Host.exe.config file, which has one or more SwitchCommandLine keys. The following is an example default key.

<add key="SwitchCommandLine" value="-cfgName=ACME-TCNMST-SW1 -config=ACME-TCNMST.acme.local:80/CoreInternal -NoStdOut -NoSumm -Log=0" />

The configuration file has a single command line for each Switch, which should not need to be updated after installation. However, there are some complex scenarios where 1E may instruct you to make some changes.



Specifies which row to use in the TachyonMaster database SwitchConfiguration table by matching the <name> using the following rules:

  1. If -cfgName=<name> is specified, then the Switch expects to find a matching name in the SwitchConfiguration table. The convention for <name>=<hostname>-<switchnumber> where Switch number is unique and starts with SW1
  2. If -cfgName=<name> is not specified, then the Switch will use the configuration where <name> is the hostname of the server on which the Switch is running
  3. If the SwitchConfiguration table does not have a row matching the server's name or hostname, then the Switch will use the default * row.

If there is no match then the Switch will log an error and will not start.

Example -cfgName=ACME-TCNMST-SW1

For a DMZ Server this will be -cfgName=ACME-TCNDMZ-SW1 if ACME-TCNDMZ is the hostname of the DMZ server.


The fully qualified domain name (fqdn) used by the Switch to connect to the core. For example -config=ACMESRV01.acme.local:80/CoreInternal

Default is HTTP for high performance. If HTTPS is required then this must be included in the config string, for example -config=https://tachyon.acme.local:443/Core

Included in template config
-NoStdOutPrevent the Switch echo logging to stdout in addition to the Switch log file. Remove only for testing.Included in template config

Prevent the Switch logging warnings about not being able to connect to the Summarizer component.

If this parameter is omitted, the Switch will attempt to report to a Summarizer using the URL specified in the SummaryUrl value in the SwitchConfiguration table, and log errors if it cannot connect.

The Summarizer component is used for performance monitoring and available as a separate installed component, only if required.

Included in template config
-NoSw2SwDisable switch-to-switch communications.Included in template config

-log.<log area>=<logging level>

Specifies the logging level for a logging area. The default value is -log=0 (same as -log=info) which provides logging of all Switch areas at info level.

The following table shows permitted logging levels.


Only outputs errors. An error is a serious problem, typically requiring operator intervention of some sort to restore full functionality.


Outputs errors and warnings. A warning indicates a potential problem, where the system can nonetheless function without intervention.


Outputs general information in addition to the errors and warnings. This is the default.


Outputs debugging information in addition to all the previous levels.

TraceOutputs the maximum information available. Used only in exceptional circumstances as it will generate huge amounts of logging output.
Logging levels should only be changed from info only if requested by 1E Support and reset to info after investigation is complete.

The method of configuring logging levels for the Tachyon Switch changed in v3.3 to using the above text values, but retains -log=0 as the default to mean the same as -log=info.

1E Support may ask you to increase or reduce specific areas of logging. The example below increases the level of logging for http, decreases metrics, and leaves other areas as normal.

-log=info -log.http=debug -log.metrics=warn
Included in template config as -log=0


Add this parameter to force Agent-Switch communications to use only FIPS-compliant algorithms.

Windows and .NET Framework support a range of cryptographic algorithms, collectively known as cipher suites. There are various ways you can configure operating systems to permit use of specific cipher suites and security policies, which can include or enforce the use of FIPS-compliant algorithms. Tachyon components, including Switches, use whichever algorithms you have permitted without additional configuration. To enforce use of FIPS-compliant algorithms therefore requires you to correctly configure the OS of servers and devices. Tachyon Switches are an exception because they do not rely on Windows, and will negotiate the strongest algorithm an Agent is permitted to use, which may not be FIPS-compliant, but will always negotiate the strongest FIPS-compliant algorithm if the -fips parameter is used.