avatar  

Log out

Recently viewed tickets

SiteManager GUI - GateManager & General & More

In the GateManager settings pressing the button will show all these hidden settings, which you can learn about here.

To hide them again press the button.

  • Remote Management

    Controls whether this SiteManager (and any Agents and Relays defined on the SiteManagers) connects to the central GateManager. You can choose the following options:
    • Enabled : Connect to the GateManager and provide remote access to the SiteManager (if Go To Appliance setting below allows it) and attached devices.
    • Heartbeat Only : Connect to the GateManager, but only to deliver periodic status information, and optionally provide remote access to the SiteManager itself (if Go To Appliance setting below allows it).
    • Relays and Heartbeat Only : Like Heartbeat Only , but it also allows data through configured Device/Server relays and LogTunnel connections.
    • Disabled : Do not connect to the GateManager, disabling all remote monitoring and management capabilities (similar to powering off this SiteManager).


  • Go To Appliance

    This option specifies if and how a GateManager administrator or LinkManager User can use the "Go To Appliance" function to connect to the User Interface of this SiteManager. It can not be set via Appliance Launcher.
    • Disabled : Access to "Go To Appliance" is blocked.
    • Manual Login : When you use "Go To Appliance", you must enter the SiteManager's normal user and password credentials in order to log into the SiteManager.
    • Automatic Login (default): When you use "Go To Appliance" in GateManager Portal or LinkManager Console's domain view, you will be allowed to use the dynamic password generated by GateManager. If your GateManager Console is configured for Automatic Login, the credentials are presented automatically to the SiteManager. If your GateManager Console is configured for Manual Login, you will be presented with the login dialog; consult the GateManager Reference Manual for instructions.
    • Manual/Automatic login, not LinkManager : As above, but "Go To Appliance" from LinkManager Console's domain view is not possible.


  • Input 1 Action

    This parameter defines the action performed based on Input port 1:
    • None
      Input port 1 is ignored.
    • Control Remote Management (default setting)
      Input port 1 controls whether Remote Management access enabled or disabled, by inverting the value of the Remote Management parameter above:

      INPUT 1
      Remote Management Parameter
      Disabled HB Only Relays/HB Only Enabled
      OFF Disconnected HB only Relays/HB Only Full Remote Management
      ON Full Remote Management Disconnected
      This means that setting Input 1 to (constant) ON will enable full remote management if the Remote Management parameter is Disabled or Relay/Heartbeat only , and disable remote management if the parameter is Enabled .
    • Trigger Alert INPUT1 if ON
      Trigger an "INPUT1" alert on the remote GateManager when input state changes from OFF to ON. Cancel alert when state changes back to OFF.
    • Trigger Alert INPUT1 if OFF
      Trigger an "INPUT1" alert on the remote GateManager when input state changes from ON to OFF. Cancel alert when state changes back to ON.


  • Input 2 Action

    This parameter defines the action performed based on Input port 2:
    • None
      Input port 2 is ignored.
    • Trigger Alert INPUT2 if ON
      Trigger an "INPUT2" alert on the remote GateManager when input state changes from OFF to ON. Cancel alert when state changes back to OFF.
    • Trigger Alert INPUT2 if OFF
      Trigger an "INPUT2" alert on the remote GateManager when input state changes from ON to OFF. Cancel alert when state changes back to ON.


  • Output 1 Signal

    This parameter defines an internal signal which may trigger Output port 1 to go ON:
    • None
      Output port 1 is manually controlled only.
    • GateManager Connected
      Output port 1 will go ON whenever the SiteManager has a working GateManager connection.
    • LinkManager Connected
      Output port 1 will go ON whenever a connection is made to the SiteManager with LinkManager and when connecting with Go To Appliance from GateManager, LinkManager Mobile, or LinkManager's domain view.


  • Output 2 Signal

    This parameter defines an internal signal which may trigger Output port 2 to go ON:
    • None
      Output port 2 is manually controlled only.
    • GateManager Connected
      Output port 2 will go ON whenever the SiteManager has a working GateManager connection.
    • LinkManager Connected
      Output port 2 will go ON whenever a connection is made to the SiteManager with LinkManager and when connecting with Go To Appliance from GateManager, LinkManager Mobile, or LinkManager's domain view.


  • Preferred Protocol

    By default, the SiteManager will automatically try a series of different methods and protocols to connect to the GateManager Address specified above. The preferred protocol option gives a hint to the SiteManager about which protocol it should try first (and force it to try only one protocol at a time); however, if the preferred protocol does not work, the SiteManager will still try the other methods. You can choose between the following options:
    • Automatic : Automatically select the first protocol to use; in fact, with this setting, the SiteManager may try several protocols simultaneously to more quickly get a working connection to the GateManager. It will also try to locate a local web proxy using WPAD and other methods (in addition to an explicitly configured Web Proxy).
    • ACM/PXP (port 11444) : This is a dedicated port for connecting to the GateManager server. Using a dedicated port is normally preferable as it separates the GateManager related traffic from other out-bound traffic in your network, so you can more easily track the GateManager traffic on your local network and on your Internet connection. But using a dedicated port also means that you will probably need to open this port in the company firewall, which may collide with corporate policy rules.
    • HTTPS/TLS (port 443) : This connects to the GateManager using the TLS protocol on port 443. This should work through firewalls that allow out-going HTTPS connections.
    • TLS over HTTP (port 80) : This connects to the GateManager using the standard HTTP port 80, but immediately upgrades that connection to a secure TLS connection. This may work through a firewall that only allows out-going HTTP connections.
    • TLS via Web-proxy : This connects through a specified Web Proxy (see below), requesting that Web Proxy to connect to the GateManager on port 443. Once established, the normal TLS protocol is used.
    • HTTP via Web-proxy : This connects through a specified Web Proxy (see below), requesting that Web Proxy to connect to the GateManager on port 80. Once established, the connection is upgraded to a secure TLS connection.


  • Connection Watchdog

    When enabled, the connection watchdog will automatically reboot the the SiteManager after one hour if it cannot connect to the GateManager. This is an attempt to recover from external issues like a stuck DEV1 switch port, malfunctioning DHCP server, or a stalled Mobile broadband modem.
    Note that the watchdog is disabled by default for SiteManager models with a built-in 4-port switch or built-in Mobile broadband modem.

  • Keep-Alive Interval

    If non-zero, this overrides the keep-alive interval defined by the GateManager Domain settings for this SiteManager. Notice that this setting only controls how often the SiteManager will send a keep-alive message to the server; the server still uses its own domain setting. This is primarily intended to be used to keep the GateManager connection alive in cases where the SiteManager is located behind an aggressive firewall that terminates the GateManager connection after a short period of inactivity.

  • Master Name Format

    Here you can specify the format in which you want the SiteManager's name to appear in the GateManager Console. The specification is a mixture of normal characters, format-codes "%X", grouping operators "{...}", choice lists "{...|...|...}", and conditional blocks like "{?...}".
    The default format is: "{%N|%D|%S}{ %W}".
    See Appendix D for a complete description of the formatting options.

  • Agent Name Format

    Here you can specify the format in which you want the "Appliance names" for the GateManager Agents to appear in the GateManager Console.
    The default format is: "{%n|%s} (%m){ - %t}{ %W}".
    See Appendix D for a complete description of the formatting options.

  • Relay Name Format

    Here you can specify the format in which you want the "Appliance names" for the Device and Server Relays to appear in the GateManager Console.
    The default format is: "{%n|%s} (%m) - %f{:%p} > %t". (The %t suffix is automatically appended if not already present.)
    See Appendix D for a complete description of the formatting options.

  • : Save the changes made on this page. Changes to the GateManager address or protocol settings are not activated if this SiteManager is already connected to the GateManager.
  • : Disconnect and reconnect to the GateManager using the current settings.
  • : Use this button to hide the advanced options again.
Creation date: 11/12/2019 13:18 (skr@secomea.com)      Updated: 16/01/2020 10:40 (skr@secomea.com)