avatar  

Log out

Recently viewed tickets

SiteManager GUI - Appendix F

Vendor-specific Device Agents

The Vendor-specific Device Agents allow remote access to many well-known Ethernet and/or Serial attached devices using specific IP protocols and ports supported by each device type.

These agents support remote access via a LinkManager, through the GateManager Console "Go To Appliance" function (if supported by the device), and via automatically created static Device Relays on the GateManager.

In addition, these Agents may periodically send Ping requests to the device and makes the corresponding Agent Instance in the GateManager appear as "Connected" (Green) or "Failed" (Red) depending on whether the device responds to the pings or not.

Note: Do not include any whitespace in any of the field values.

Parameters ( field value ):

  • Device Address [Ethernet only] ( ):
    The IP address of the attached device.
    If the address is specified as .nnn , it is automatically combined with the primary IP address of the first device interface. For example, if you specify as the address, and the IP address of the interface is , the real target address is .
    Specify the symbol "SM" to target the SiteManager 1129 itself.
  • Address on LinkManager ( ):
    Specifies an alternate Device Virtual Address for the device when accessed via a remote LinkManager . Leave the field blank to use the Device Address (Ethernet attached) or SiteManager Local Address (Serial attached). Specify '#' to disable LinkManager access to this device.
  • Address on GateManager [Ethernet only] ( ):
    If non-empty, this fields specifies a static Device Virtual Address for the device when accessed via GateManager central server.
  • Baud Rate [Serial only] ( ):
    Can be specified to override the default serial port speed for the attached device.
    Supported values are: 300, 1200, 2400, 4800, 9600, 9600, 19200, 19200, 38400, 57600, 115200.
  • Data,Parity,Stop [Serial only] ( ):
    Can be specified to override the default serial port setting for number of databits D (7 or 8), parity P (N=none, E=even, O=odd), and stopbits S (1 or 2).
  • Always On [Ethernet only] ( ):
    Disable the normal ping-based checking for the presence of the device, and just assume that the device is online.
    A serial device is always assumed to be online; if you need to explicitly monitor a serial device, use the custom Serial agent.
  • Extra TCP ports ( ):
    If the standard vendor agent does not include all the necessary tcp port(s) you can add them here.
  • Extra UDP ports ( ):
    If the standard vendor agent does not include all the necessary usp port(s) you can add them here.
  • Extra GTA Service ( ):
    If the standard vendor agent does not include the service(*) necessary you can add it here. Only one extra service can be added. To add and extra service make sure that the needed port is also added to the Extra TCP ports option above.
    Example: If a device has a web interface and you want to add this service you add the "http,80" to the Extra GTA Service and you add "80" to the Extra TCP ports field.
    (*) A GTA service enables you to launch a service like http (WEB access) direct with a mouse-click from the LinkManager GUI.
  • Enable WWW/VNC/RDP service: ( ):
    Check mark this field and the http/vnc/rdp service will be included for this agent if not already defined.
    The option "LinkManager Only" means that this service will only be available when you make a connect from a LinkManager console; i.e. LinkManager Mobile and GateManager Portal will NOT show the service.
    You can check the "No OUTPUT1 signal" option, if you don't want the OUT 1 port to go ON [Remote Service Alert] when using Go To Appliance from GateManager portal, from the LinkManager console domain view, or LinkManager Mobile.

    NOTE: When enabling WWW, both HTTP and HTTPS GTA sessions will be established as encrypted and authenticated connections between your browser and the GateManager, and not the end-device. So observe the following:
    a) For HTTPS sessions the end device's TLS certificate is accepted by the GateManager acting as HTTPS client towards the end device and the validity of the certificate can therefore not be verified by your browser. Be careful using the "WWW Service" option if there is a risk that an end device could be maliciously exchanged for another device.
    b) Information that your browser may store locally based on a session with one end device via the "WWW Service" option may be transmitted to other end devices. If you use the "WWW Service" option to manage devices with different security levels or in different organisations, we recommend establishing connections via the WWW Service with the browser in Incognito mode.

  • Custom Settings:
    This field is used for special settings like those listed below; normally you should leave this field blank.
    • +NBC - Use Network Broadcasts
      If your vendor software uses UDP broadcasts for device discovery, and it fails to find a device, you can try to add this option to try a diffent kind of broadcasts.
    • +noproxy - Inhibit GateManager HTTPS/HTTP proxying for this device.
      If the web browser in your device for some reason is unable to handle or support the GateManager's automatic GoToAppliance HTTPS proxy for HTTP connections, you can add this option to use plain HTTP to access the device via the GoToAppliance function in GateManager Portal and LinkManager Mobile. Please note that this will disable the encryption of the connection between the browser and GateManager.
    • -X - Exclusive access
      If your vendor software requires exclusive access to the device (via the LinkManager), you can add this option to the custom settings.

Generic Agents

The Generic Agents are typically used to quickly connect a new device for which no vendor-specific agent is currently defined.
These agents simply allows a LinkManager to connect to all TCP and UDP ports on the device, and may also open for TCP connections from the device back to the LinkManager PC.

The following generic agents are defined:

  • NAT All, 1-way :
    Allow all ports from LinkManager to device, use SiteManager address as source (NAT).
  • NAT All, 2-way :
    Allow all ports from LinkManager to device, and all tcp-ports from device to LinkManager; use SiteManager address as source (NAT).
  • Transparent :
    Allow all ports from LinkManager to device, and all tcp-ports from device to LinkManager; use LinkManager address as source (no NAT).
    This typically requires that the device is setup to use the SiteManager as default gateway.

The AKA2XX Agent

The AKA2xx Agent is used for monitoring the status of a Danfoss AKA 244 or similar Gateway device connected to the Serial port.

Parameters ( field value ):

  • Query Interval ( ):
    Specify the period (in minutes) used by the Agent to actively poll the Gateway if there has been no traffic from it in the previous period. The default period is T =10 minutes.

The Device Agent

The Device Agent allows remote access to an network-attached device, via a LinkManager or GateManager device relay, using the IP/TCP and IP/UDP protocols.

The Device Agent also supports accessing the device through the GateManager Console "Go To Appliance" function.
In addition, the Device Agent periodically sends Ping or Snmp requests to the device and makes the corresponding Agent Instance in the GateManager appear as "Connected" (Green) or "Failed" (Red) depending on whether the device responds to the pings or not.

Parameters ( field value ):

  • Device Address ( ):
    The IP address of the attached device, e.g. .
    If the address is specified as .nnn , it is automatically combined with the primary IP address of the first device interface. For example, if you specify as the address, and the IP address of the interface is , the real target address is .
  • Address on LinkManager ( ):
    Specifies an alternate Device Virtual Address for the device when accessed via a remote LinkManager . Leave the field blank to use the Device Address. Specify '#' to disable LinkManager access to this device.
  • Address on GateManager ( ):
    If non-empty, this fields specifies a static Device Virtual Address for the device when accessed via GateManager central server.
  • TCP Ports ( ):
    If non-empty, this field specifies the TCP ports on the device that can be accessed via a remote LinkManager. A * specifies all ports.
  • UDP Ports ( ):
    If non-empty, this field specifies the UDP ports on the device which can be accessed via a remote LinkManager. A * specifies all ports.
  • Always On ( ):
    Disable the normal ping-based checking for the presence of the device, and just assume that the device is online.
  • Enable Server ( ):
    Allow attached device to make TCP connections to the remote LinkManager .
  • Transparent ( ):
    Disable the normal network address translation using the local interface's IP address as source address when connecting from a remote LinkManager to the device.
    Instead, to facilitate protocols which require transparent operation (such as FTP), the source adddress from the remote LinkManager's is used as source address.
    Note that this only works for devices attached to the DEV1 interface.
  • Exclusive Access ( ):
    Allow only one LinkManager at a time to access this device; if a second LinkManager tries to connect, the connection will be rejected.
  • Idle Timeout ( ):
    Connection idle timeout (in minutes). If no traffic is exchanged on a connection in T minutes, automatically close the connections. Default is 10 minutes.
  • Max Connections ( ):
    Allow maximum N simultaneous connections to the device through this agent. Default is 5 connections.
  • Service ( ):
    Optional service name for the "Go To Appliance" functionality. This service is associated with the first port in the TCP ports field.
    Note: If the service requires more than one open port to function properly, it can only really be used when an LinkManager connection is activated to the device; in this case, you can add a "-" prefix (e.g. -http) to exclude the service from the normal Go To Appliance drop-down list in the GateManager console and the service icon in the LinkManager console domain/appliance view.
  • User Name ( ):
    Optional user name for automatic login.
  • Password ( ):
    Optional password for automatic login.
  • Path ( ):
    Optional path component added to the "Go To Appliance" URL.
  • Use SNMP ( ):
    Query device using Snmp rather than Ping.
  • SNMP Profile ( ):
    Here you can specify an additional list of Object IDs (in the form of an SNMP Profile) whose values you want the Agent to retrieve and forward to the GateManager. If you don't select an SNMP profile, the agent only uses SNMP to test for the presence of the agent.
    On the GateManager, you can create Alert Rules that react on these values.
  • Community ( ):
    The name by which the SNMP Agent will identify itself to the device. The default community is "public".
  • Poll Interval ( ):
    Specifies how often the agent will send a simple SNMP request to the device to check for its presence. The Interval is the time between polls (in seconds), Retries specifies how many polls to send (if device does not respond), and Timeout is the number of seconds to wait between the poll retries if device does not respond. The defaults are 60 seconds interval, 3 retries, and 10 seconds timeout.
  • Status Update Interval ( ):
    Specifies how often the agent will send a full SNMP request to the device to update the available status for all objects in the SNMP profile. The Interval is the time between updates (in seconds).
    Note: A full SNMP request is always performed before sending a heartbeat to the GateManager.

The Forwarding Agent

The Forwarding Agent allows devices (like PLCs, PCs or servers) to communicate, even when they are connected to separate interfaces of the SiteManager.

Typical use:
The forwarding agent is used when a local server on the Uplink network needs to collect data from devices attached to the Device network (DEV), or when a device on the Device network needs to submit log data to a server on the Uplink network.

Activation:
When configured correctly the forwarding agent is always ON and does not need to be activated by a LinkManager connection.
Notice: The Forwarding Agent will not show up in the GateManager Console or the LinkManager Console.

Forwarding Rule Format

Each forwarding rule must be combined from a number of elements as follows (see examples below):

      [#|?] [[IN_IFACE*] [$LOCAL_IP]:] [PROTOCOL:] [SOURCE_IP[/MASK]:] [NAT_PORT] >[>] [OUT_IFACE[*]:] TARGET[/MASK] [:TARGET_PORT]

Elements in [...] are optional.
NOTE: Spaces are not allowed in the rule (they are inserted above for readability purposes).

  • # :
    A leading number sign in a rule specifies that the rule is disabled (i.e. to be ignored).
  • ? :
    A leading question mark specifies an optional rule, meaning that any errors related to this rule should not be treated as fatal (i.e. rule is ignored in case of errors).
  • IN_IFACE / LOCAL_IP ( ):
    This specifies the incoming interface (and/or local IP address/alias) for the connection; if omitted, it defaults to opposite of OUT_IFACE (if set), else UPLINK*. The * is a wildcard meaning any interface of the specified type, e.g. UPLINK* or DEV*.
    The $ character is both a separator (if IN_IFACE is also specified) and is used to differentiate LOCAL_IP from the SOURCE_IP element.
  • PROTOCOL ( ):
    This specifies the network protocol, either TCP, UDP, or ANY; if omitted, it defaults to TCP.
    When ANY is used in a rule with either NAT_PORT or TARGET_PORT, it means "both TCP and UDP"; otherwise it means "any IP protocol".
  • SOURCE_IP ( or ):
    This specifies a source IP address or subnet filter for this rule.
    Note: A hostname must start with a lower-case letter, a dash or a digit.
  • NAT_PORT ( ):
    This specifies the original destination port number (range) for port forwarding targeted at the IN_IFACE. Port forwarding means that traffic addressed to that specific port (range) on a SiteManager interface is translated and forwarded to a specific external target and port with translation.
    Notice: If you add a port forwarding rule for TCP port 443, this will disable access to the SiteManager WEB GUI from the rule's incoming interface. You can still access the WEB GUI using another interface or via the Appliance Launcher, or - if connected remotely - via LinkManager or GateManager.
  • > or >> :
    A double >> separator indicates that source NAT translation should be applied for traffic forwarded by this rule, making the SiteManager the source of the forwarded traffic.
    A single > indicates no source translation.
  • OUT_IFACE ( ):
    This specifies the outgoing interface for the connection; if omitted, it defaults to opposite of IN_IFACE (if set), else DEV*. The * is a wildcard meaning any interface of the specified type, e.g. UPLINK* or DEV*.
  • TARGET ( or ):
    The TARGET part specifies the allowed IP address or subnet for the connection on the "other side" of the SiteManager.
  • TARGET_PORT ( ):
    For a port forwarding rule (if NAT_PORT is specified), it specifies the target port (range) for the forwarded traffic; if omitted it defaults to the NAT_PORT.
    Note: If a port range is specified in NAT_PORT do not specify a port range here.
    Otherwise, the TARGET_PORT part specifies the allowed target port number(s) on the target system.

Example:
A data logger on the Uplink network needs to access two different devices attached to the DEV interface, both using TCP port 80 (WEB server).
The UPLINK interface has only one IP address, so the port option needs to specify using, say, port 80 for the first device and port 81 for the second device.
The two forwarding rules in the forwarding agent configuration will look like this:
UPLINK*:TCP:80>>192.168.1.2:80 (or just 80>>192.168.1.2:80)
UPLINK*:TCP:81>>192.168.1.3:80 (or just 81>>192.168.1.3:80)
With these rules, the Forwarding Agent will forwarding connections to ports 80 and 81 on the UPLINK IP address to port 80 on devices 192.168.1.2 and 192.168.1.3, respectively.

Optional parameters ( field value ):

  • Enable UPLINK Source Translation ( ):
    When this option is set, the Forwarding agent will apply Source NAT to all connections forwarded out through an UPLINK interface (from a device on a DEV interface), regardless of the > or >> settings in the forwarding rules. This means that the target system will see the SiteManager UPLINK IP address as the source address rather than the original Device IP address.
    You will usually enable this option when creating outbound forwarding rules (from DEV to UPLINK). If not enabled, you probably need to configure static routes on the target system pointing at the UPLINK IP address, in order for the target system to determine the gateway back to the device.
  • Enable DEV Source Translation ( ):
    When this option is set, the Forwarding agent will apply Source NAT to all connections forwarded out through a DEV interface (from a system on an UPLINK interface), regardless of the > or >> settings in the forwarding rules. This means that the target device will see the SiteManager DEV IP address as the source address rather than the original system's IP address. You will usually enable this option when creating inbound forwarding rules (from UPLINK to DEV).
  • DNS recheck interval (minutes) ( ):
    This number specifies the time interval between which, all DNS names used in the rules, are being reaffirmed. If a DNS name to IP address mapping has changed, the corresponding rules are also updated. If the DNS name no longer can be found, the rule is not updated. The value 0 means that DNS names are never reaffirmed. This is the default value.

The Http Agent

The HTTP Agent allows the GateManager Administrator to access a the Web interface of a network-attached device through the GateManager Console "Go To Appliance" function.
In addition, the HTTP Agent periodically sends Ping requests to the device and makes the corresponding Agent Instance in the GateManager appear as "Connected" (Green) or "Failed" (Red) depending on whether the device responds to the pings or not.

Parameters ( field value ):

  • Device Address ( ):
    The IP address of the attached device with optional port number, e.g. .
    If the address is specified as .nnn , it is automatically combined with the primary IP address of the first device interface. For example, if you specify as the address, and the IP address of the interface is , the real target address is .
  • Address on LinkManager ( ):
    Specifies an alternate Device Virtual Address for the device when accessed via a remote LinkManager . Leave the field blank to use the Device Address. Specify '#' to disable LinkManager access to this device.
  • Address on GateManager ( ):
    If non-empty, this fields specifies a static Device Virtual Address for the device when accessed via GateManager central server.
  • Always On ( ):
    Disable the normal ping-based checking for the presence of the device, and just assume that the device is online.
  • Idle Timeout ( ):
    Connection idle timeout (in minutes). If no traffic is exchanged on a connection in T minutes, automatically close the connections. Default is 10 minutes.
  • Max Connections ( ):
    Allow maximum N simultaneous connections to the device through this agent. Default is 5 connections.
  • HTTPS ( ):
    Select the https protocol rather than http (implies that the traffic is assumed to be encrypted, so no additional encryption is performed)
  • Bypass HTTPS proxy ( ):
    Inhibit the HTTPS to HTTP/HTTPS proxy function in GateManager. This may be necessary if client software does not support HTTPS.
  • Service ( ):
    Optional service name for the "Go To Appliance". Default is "http" (or "https").
  • User Name ( ):
    Optional user name for automatic login.
  • Password ( ):
    Optional password for automatic login.
  • Host ( ):
    Optional direct connection address to the device; if specified, do not connect via the GateManager proxy.
  • Path ( ):
    Optional path component added to the "Go To Appliance" URL.
  • Flags ( ):
    Control flags for connections. The value is the sum of the following integer values:
    1: encrypt data, 2: close proxy port after first connect.

The Modem Agent

The Modem Agent is used for connecting to a remote modem-attached serial device on a specific telephone number via a dial-out modem attached to the Serial port.

The Modem agent is "always on" (as we cannot monitor the remote serial device anyway).

Notice that Modem Agents will not be connected if you do "Connect All" from a LinkManager, This allows several instances of the Modem agent (with different telephone numbers) to share the same modem attached to the serial port, as you have to explicitly connect to the relevant modem instance to reach a specific remote location.

Parameters ( field value ):

  • Address on LinkManager ( ):
    Specifies an alternate Device Virtual Address for the device when accessed via a remote LinkManager . Leave the field blank to use the SiteManager Local Address. Specify '#' to disable LinkManager access to this device.
  • Telephone Number ( ):
    If non-empty, any data sent to the serial port is analyzed, looking for dial-out commands (ATD, ATDT, ATDP), and if found, the telephone number specified in the dial-out command is substituted by the phone_number specified here. This means that any random telephone number can be used by the remote application, and still reach the proper remote device.
    Caveat: If the modem is set to echo command characters, the application dialing out will receive the substituted phone number rather than the original phone number it sent itself; this may confuse some applications.
  • Service ( ):
    Optional service name for the "Go To Appliance". Default is "telnet".
  • User Name ( ):
    Optional user name for automatic login.
  • Password ( ):
    Optional password for automatic login.
  • Flags ( ):
    Control flags for serial connections. The value is the sum of the following integer values:
    1: do not encrypt data, 2: do not close proxy port after first connect.
  • Service 2 ( ):
    Optional secondary service name for the "Go To Appliance". Default is "raw".
  • User Name 2 ( ):
    Optional user name for automatic login to the secondary service.
  • Password 2 ( ):
    Optional password for automatic login to the secondary service.
  • Flags 2 ( ):
    Proxy control flags for serial connections to the secondary service.

The PC Agent

The PC Agent allows the GateManager Administrator to access a network-attached PC through the "Go To Appliance" function, as well as remote access via a LinkManager.
In addition, the PC Agent periodically sends Ping requests to the PC and makes the corresponding Agent Instance in the GateManager appear as "Connected" (Green) or "Failed" (Red) depending on whether the PC responds to the pings or not.

Parameters ( field value ):

  • Device Address ( ):
    The IP address of the PC.
    If the address is specified as .nnn , it is automatically combined with the primary IP address of the first device interface. For example, if you specify as the address, and the IP address of the interface is , the real target address is .
  • Address on LinkManager ( ):
    Specifies an alternate Device Virtual Address for the device when accessed via a remote LinkManager . Leave the field blank to use the Device Address. Specify '#' to disable LinkManager access to this device.
  • Always On ( ):
    Disable the normal ping-based checking for the presence of the PC, and just assume that it is online. You may need to do this if the PC has a local firewall which does not allow the PC to respond to Ping requests.
  • MS Remote Desktop ( ):
    Enable remote access to MicroSoft Remote Desktop service of the PC.
    Corresponding GateManager GoToAppliance service name is "rdp".
  • VNC Remote Desktop ( ):
    Enable remote access to VNC Remote Desktop service of the PC.
    Corresponding GateManager GoToAppliance service name is "vnc".
  • Netop Remote Desktop ( ):
    Enable remote access to Netop Client-to-Client Remote Desktop service of the PC.
    Corresponding GateManager GoToAppliance service name is "netop".
  • HTTP Server ( ):
    Enable remote access to an HTTP server on the PC.
    Corresponding GateManager GoToAppliance service name is "http".
  • HTTPS Server ( ):
    Enable remote access to an HTTPS server on the PC.
    Corresponding GateManager GoToAppliance service name is "https".
  • Bypass HTTPS proxy ( ):
    Inhibit the HTTPS to HTTP/HTTPS proxy function in GateManager. This may be necessary if client software does not support HTTPS.
  • User Name ( ):
    Optional user name for automatic login. Default is no user name.
  • Password ( ):
    Optional password for automatic login. Default is no password.
  • Custom Settings :
    The target ports for each of the above services can be modified by adding a custom setting like , e.g. .

The Ping Agent

The Ping Agent periodically sends Ping requests to a specified network-attached device and makes the corresponding Agent Instance in the GateManager appear as "Connected" (Green) or "Failed" (Red) depending on whether the device responds to the pings or not.

Parameters ( field value ):

  • Target Address ( ):
    The IP address of the attached device, e.g. .
    If the address is specified as .nnn , it is automatically combined with the primary IP address of the first device interface. For example, if you specify as the address, and the IP address of the interface is , the real target address is .
  • Ping Interval ( ):
    Specifies how often the agent will ping the target address to see if the device is alive. The Interval is the time between checks (in seconds), Retries specifies how many pings to send (if device does not respond), and Timeout is the number of seconds to wait between the ping retries if device does not respond. The defaults are 60 seconds interval, 3 retries, and 10 seconds timeout.

The Scada Agent

The Scada Agent allows upto 3 local Scada systems on the UPLINK interface of a SiteManager to connect to devices on the SiteManager DEV networks.

Notice: Neither the Scada Agent, nor the Scada PCs can be managed from GateManager via this agent.

Parameters ( field value ):

  • Scada Address 1 ( ):
    The IP address of the first Scada PC.
  • Scada Address 2 ( ):
    The IP address of the second Scada PC.
  • Scada Address 3 ( ):
    The IP address of the third Scada PC.
  • Enable UPLINK Source Translation ( ):
    When this option is set, the Scada agent will apply Source NAT to all connections forwarded out through an UPLINK interface (from a device on a DEV interface). This means that the target system will see the SiteManager UPLINK IP address as the source address rather than the original Device IP address.
  • Enable DEV Source Translation ( ):
    When this option is set, the Scada agent will apply Source NAT to all connections forwarded out through a DEV interface (from a system on an UPLINK interface). This means that the target device will see the SiteManager DEV IP address as the source address rather than the original system's IP address.

The Serial Agent

The Serial Agent is used for accessing and monitoring the status of a device connected to the Serial port.

Parameters ( field value ):

  • Address on LinkManager ( ):
    Specifies an alternate Device Virtual Address for the device when accessed via a remote LinkManager . Leave the field blank to use the SiteManager Local Address. Specify '#' to disable LinkManager access to this device.
  • Address on GateManager ( ):
    If non-empty, this fields specifies a static Device Virtual Address for the device when accessed via GateManager central server.
  • Telephone Number ( ):
    If non-empty, any data sent to the serial port is analyzed, looking for dial-out commands (ATD, ATDT, ATDP), and if found, the telephone number specified in the dial-out command is substituted by the phone_number specified here. This means that any random telephone number can be used by the remote application, and still reach the proper remote device.
    Caveat: If the modem is set to echo command characters, the application dialing out will receive the substituted phone number rather than the original phone number it sent itself; this may confuse some applications.
  • Always On ( ):
    Assume that the serial device is always powered on and alive. This disables both query polls and DTR low checking.
  • Query String ( ):
    When there has been no activity on the serial line for the time specified by the Query Interval , the serial agent sends this string on the serial line, expecting the attached device to send some response, indicating that it is alive; the response data are discarded. The query string should be harmless for the attached device, in the sense that it should simply cause the device to respond, but not perform any action.
    The string can contain normal alpha-numeric characters, as well as control characters using the format ^C , CR/NL/TAB as \r , \n , and \t , as well as arbitrary byte values specified in hexadecimal notation \xx . To include "\" or "^" in the string, double the character. To include a space, use "\20".
  • Query Interval ( ):
    Specify the period (in minutes) used by the Agent to actively poll the device if there has been no traffic from the device in the previous period. The default period is T =10 minutes.
  • Max DTR Low ( ):
    Normally, the Serial Agent will monitor the DTR pin on the serial connector to see if the attached device is powered on. Some devices will lower DTR for a brief period to disconnect the serial connection. To avoid interpreting this as a power down, the agent will ignore a DTR low condition that is shorter than the period (in seconds) specified by this parameter. The default is 60 seconds.
    If this field is set to 0 , the state of the DTR pin is ignored (i.e. it is assumed that the device is always powered on).
  • Idle Timeout ( ):
    Automatically disconnect connections after T minutes of inactivity. Default is 10 minutes. A value of 0 means no timeout.
  • Non-Exclusive ( ):
    Normally, the serial port can only be used by one LinkManager at a time; this allows simultaneous access from multiple LinkManagers.
  • Service ( ):
    Optional service name for the "Go To Appliance". Default is "telnet".
  • User Name ( ):
    Optional user name for automatic login.
  • Password ( ):
    Optional password for automatic login.
  • Flags ( ):
    Control flags for serial connections. The value is the sum of the following integer values:
    1: do not encrypt data, 2: do not close proxy port after first connect.
  • Service 2 ( ):
    Optional secondary service name for the "Go To Appliance". Default is "raw".
  • User Name 2 ( ):
    Optional user name for automatic login to the secondary service.
  • Password 2 ( ):
    Optional password for automatic login to the secondary service.
  • Flags 2 ( ):
    Proxy control flags for serial connections to the secondary service.

The Snmp Agent

The Snmp Agent periodically sends SNMP requests to a specified network-attached device and makes the corresponding Agent Instance in the GateManager appear as "Connected" (Green) or "Failed" (Red) depending on whether the device responds to the requests or not.

Parameters ( field value ):

  • Target Address ( ):
    The IP address of the attached device with optional port number, e.g. .
    If the address is specified as .nnn , it is automatically combined with the primary IP address of the first device interface. For example, if you specify as the address, and the IP address of the interface is , the real target address is .
  • Community ( ):
    The name by which the SNMP Agent will identify itself to the device. The default community is "public".
  • SNMP Profile ( ):
    Here you specify a list of Object IDs (in the form of a SNMP Profile) whose values you want the Agent to retrieve and forward to the GateManager.
    On the GateManager, you can create Alert Rules that react on these values.
  • Poll Interval ( ):
    Specifies how often the agent will send a simple SNMP request to the device to check for its presence. The Interval is the time between polls (in seconds), Retries specifies how many polls to send (if device does not respond), and Timeout is the number of seconds to wait between the poll retries if device does not respond. The defaults are 60 seconds interval, 3 retries, and 10 seconds timeout.
  • Status Update Interval ( ):
    Specifies how often the agent will send a full SNMP request to the device to update the available status for all objects in the SNMP profile. The Interval is the time between updates (in seconds).
    Note: A full SNMP request is always performed before sending a heartbeat to the GateManager.
  • Enable HTTP ( ):
    Enable http access to the managed device.

The TCP Agent

The TCP Agent allows remote access to an network-attached device using the IP/TCP protocol.

The TCP Agent supports remote access via a LinkManager and via a static device relay on GateManager, but it does not support accessing the device through the GateManager Console "Go To Appliance" function.
In addition, the TCP Agent periodically sends Ping requests to the device and makes the corresponding Agent Instance in the GateManager appear as "Connected" (Green) or "Failed" (Red) depending on whether the device responds to the pings or not.

Parameters ( field value ):

  • Device Address ( ):
    The IP address of the attached device and optional port numbers and port ranges, e.g. .
    If the address is specified as .nnn , it is automatically combined with the primary IP address of the first device interface. For example, if you specify as the address, and the IP address of the interface is , the real target address is .
  • Address on LinkManager ( ):
    Specifies an alternate Device Virtual Address for the device when accessed via a remote LinkManager . Leave the field blank to use the Device Address. Specify '#' to disable LinkManager access to this device.
  • Address on GateManager ( ):
    If non-empty, this fields specifies a static Device Virtual Address for the device when accessed via GateManager central server.
  • Always On ( ):
    Disable the normal ping-based checking for the presence of the device, and just assume that the device is online.
  • Enable Server ( ):
    Allow attached device to make TCP connections to the remote LinkManager .
  • Transparent ( ):
    Disable the normal network address translation using the local interface's IP address as source address when connecting from a remote LinkManager to the device.
    Instead, to facilitate protocols that require transparent operation (such as FTP), the source adddress from the remote LinkManager's is used as source address.
    Note that this only works for devices attached to the DEV1 interface.
  • Exclusive Access ( ):
    Allow only one LinkManager at a time to access this device; if a second LinkManager tries to connect, the connection will be rejected.
  • Idle Timeout ( ):
    Connection idle timeout (in minutes). If no traffic is exchanged on a connection in T minutes, automatically close the connections. Default is 10 minutes.
  • Max Connections ( ):
    Allow maximum N simultaneous connections to the device through this agent. Default is 5 connections.

The UDP Agent

The UDP Agent allows remote access to an network-attached device using the IP/UDP protocol.

The UDP Agent supports remote access via a LinkManager and via a static device relay on GateManager, but it does not support accessing the device through the GateManager Console "Go To Appliance" function.
In addition, the UDP Agent periodically sends Ping requests to the device and makes the corresponding Agent Instance in the GateManager appear as "Connected" (Green) or "Failed" (Red) depending on whether the device responds to the pings or not.

Parameters ( field value ):

  • Device Address ( ):
    The IP address of the attached device and optional port numbers and port ranges, e.g. .
    If the address is specified as .nnn , it is automatically combined with the primary IP address of the first device interface. For example, if you specify as the address, and the IP address of the interface is , the real target address is .
  • Address on LinkManager ( ):
    Specifies an alternate Device Virtual Address for the device when accessed via a remote LinkManager . Leave the field blank to use the Device Address. Specify '#' to disable LinkManager access to this device.
  • Address on GateManager ( ):
    If non-empty, this fields specifies a static Device Virtual Address for the device when accessed via GateManager central server.
  • Always On ( ):
    Disable the normal ping-based checking for the presence of the device, and just assume that the device is online.
  • Transparent ( ):
    Disable the normal network address translation using the local interface's IP address as source address when connecting from a remote LinkManager to the device.
    Instead, to facilitate protocols that require transparent operation (such as FTP), the source adddress from the remote LinkManager's is used as source address.
    Note that this only works for devices attached to the DEV1 interface.
  • Exclusive Access ( ):
    Allow only one LinkManager at a time to access this device; if a second LinkManager tries to connect, the connection will be rejected.
  • Idle Timeout ( ):
    Connection idle timeout (in minutes). If no traffic is exchanged on a connection in T minutes, automatically close the connections. Default is 10 minutes.
  • Max Connections ( ):
    Allow maximum N simultaneous connections to the device through this agent. Default is 5 connections.

The Vnc Agent

The VNC Agent allows the GateManager Administrator to access a network-attached PC through the "Go To Appliance" function, as well as remote access via a LinkManager or a static device relay on GateManager.
In addition, the VNC Agent periodically tries to connect to the VNC service port on the PC and makes the corresponding Agent Instance in the GateManager appear as "Connected" (Green) or "Failed" (Red) depending on whether the PC accepts the connection or not.

Parameters ( field value ):

  • Device Address ( ):
    The IP address of the PC with optional display or port number, e.g. or .
    If neither display nor port is specified, the default target port is 5900 . If a display D is specified, the port number is 5900+D . If the address is specified as .nnn , it is automatically combined with the primary IP address of the first device interface. For example, if you specify as the address, and the IP address of the interface is , the real target address is .
  • Address on LinkManager ( ):
    Specifies an alternate Device Virtual Address for the device when accessed via a remote LinkManager . Leave the field blank to use the Device Address. Specify '#' to disable LinkManager access to this device.
  • Address on GateManager ( ):
    If non-empty, this fields specifies a static Device Virtual Address for the device when accessed via GateManager central server.
  • Always On ( ):
    Disable the normal ping-based checking for the presence of the PC, and just assume that it is online. You may need to do this if the PC has a local firewall which does not allow the PC to respond to Ping requests.
  • Ping Device ( ):
    Use ICMP Ping requests instead of dummy TCP connects to query the device online state; this is less informative, as it doesn't really check whether it is possible to connect a VNC viewer to the device, but some VNC servers on some devices may have problems handling the dummy TCP connects.
  • No Close ( ):
    Allow VNC client to disconnect and reconnect via the GateManager connection. Normal VNC clients don't need this.
  • Idle Timeout ( ):
    Connection idle timeout (in minutes). If no traffic is exchanged on a connection in T minutes, automatically close the connections. Default is 10 minutes.
  • Max Connections ( ):
    Allow maximum N simultaneous connections to the device through this agent. Default is 1 connection.
  • Service ( ):
    Optional service name for the "Go To Appliance". Default is "vnc".
  • User Name ( ):
    Optional user name for automatic login. Default is "vnc".
  • Password ( ):
    Optional password for automatic login. Default is no password.
Creation date: 11/12/2019 13:21 (skr@secomea.com)      Updated: 11/12/2019 13:21 ()