This article will provide a look into the various different agent types.
Represent devices that have been configured for remote access.
To make configuration and management easier, the SiteManager offers pre-configured agents.
Generic Agents
The Generic Agents are pre-configured agents that simplify setup for common scenarios like VNC, RDP, SSH, etc.
These scenarios often use standardized ports (e.g., RDP on port 3389, VNC on port 5900), which make it possible to create a general agent that can fit multiple devices.
Below table shows an overview of the various Generic Agents available.
| Agent Name | Description / Reference | Ports (TCP / UDP) |
|---|---|---|
| LogTunnel Client | This agent type is specifically used for the LogTunnel feature. Please refer to the LogTunnel guides. | N/A |
| LogTunnel Master (Pull) | - | N/A |
| LogTunnel Master (Push) | - | N/A |
| Data Collector Module Device | This agent is specifically used for the Data Collection Module (DCM) feature. Please refer to the DCM guides. | N/A |
| Web Access | Please refer to GTA guides. | 80, 443 |
| Remote Desktop (RDP) | Please refer to GTA guides. | 3389 |
| Remote Desktop (VNC) | Please refer to GTA guides. | 5800, 5900 |
| Secure Shell (SSH) | Please refer to GTA guides. | 22 |
| View-only VNC | View-only VNC is used to limit a user to View-only VNC connection, and can be useful for monitoring access. | 5900 |
| Desktop PC | This agent is for Desktop PC scenarios, typically used with either VNC or RDP. Ports are manually configurable. | Configurable |
| All ports, 1-way NAT | Allow all ports from LinkManager to device; use SiteManager address as source (NAT). | All |
| All ports, 2-way NAT | Allow all ports from LinkManager to device, and all TCP-ports from device to LinkManager; use SiteManager address as source (NAT). | All |
| All ports, 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. | All |
| Mobile VPN | This agent facilitates creating restricted VPN tunnels between a "Mobile VPN"-enabled client application and remote devices controlled by this SiteManager. | Configurable |
| Subnet | This agent enables traffic between LinkManager and all Devices in a subnet of IP addresses. By default, all TCP ports (and no UDP ports) are forwarded from LinkManager to the devices, but you can specify which TCP and UDP ports are to be forwarded. | All or Configurable |
| Serial | The Serial Agent is used for accessing and monitoring the status of a device connected to the Serial port. This agent requires specific parameter such as Baud Rate, Parity, Stop, etc. These are configurable in the Parameter details. | N/A |
| USB-Serial Adapter | This agent is specific for Serial-Adapter connections. This agent supports the following USB IDs: Vendor ID: 0403 Product ID: 6001 Manufacturer: Future Technology Devices International, Ltd Product: FT232 Serial (UART) IC Vendor ID: 0501 Product ID: 1011 Manufacturer: Brainboxes, Ltd 1xRS232 Product: 1xRS232 Vendor ID: 0678 Product ID: 2303 Manufacturer: Prolific Technology, Inc. Product: L2303 Serial Port / Mobile Action MA-8910P |
N/A |
| USB-Ethernet Adapter | This agent is specific for Ethernet-Adapter connections. This agent supports the following USB IDs: Vendor ID: 0B95 Product ID: 772B Manufacturer: ASIX Electronics Corp. Product: AX88772B |
N/A |
| Device | A generic device agent to configure ports manually. | Configurable |
| FTP | This agent is for FTP scenarios. | 21 |
| Shared Folder | With this agent you can access a folder on a PC connected to SiteManager via a LinkManager connection. | 445 |
| Layer 2 | Layer 2 access allows you to broadcast search for devices on the DEV subnet of the SiteManager. If you have a PLC that has lost its IP address or is unknown, then you will have the ability to connect to this agent and, if your application allows it, search for devices on the remote network. Please refer to the Layer 2 guide for more information. | Layer 2 |
| Sniffer | The Sniffer agent is like the Generic 2-way NAT agent, i.e. it forwards all TCP, UDP, and ICMP traffic between LinkManager and the agent device, and collects relevant information about the actual TCP and UDP traffic. | N/A |
In-browser GTA Agents
From SiteManager/GateManager Release 11.0 the In-browser GTA Agents are available as a new Agent Type.
The In-browser agents allow a straightforward and alternative means to using external applications for RDP, VNC, SSH and Telnet. These agents only supports GTA, i.e. they do not allow for direct LinkManager Connect.
| Agent Name | Description |
|---|---|
| Remote Desktop (RDP) | Provides alternative to connection instead of using external applications: e.g. Windows Remote Desktop |
| Remote Desktop (VNC) | Provides alternative to connection instead of using external applications: e.g. TightVNC or UltraVNC. |
| Secure Shell (SSH) | Provides alternative to connection instead of using external applications: e.g. PuTTY, Xshell, WinSCP and other Terminals. |
| Telnet | Provides alternative to connection instead of using external applications: e.g. PuTTY and other Terminals. |
| WWW | Gives direct access to a website. E.g. an IP camera or website. |
| Legacy VNC | Provides alternative to connection instead of using external applications: e.g. TightVNC or UltraVNC. The Legacy VNC refers to the previous version of in-browser VNC known as “noVNC” |
Vendor Agents
Leveraging our over 15 years of experience working with OT equipment, we have developed numerous pre-configured agents for various vendors. The Vendor Agents are ideal for devices that share standard port configurations, and help to make setup simple and hassle-free.
Below table shows an overview of the vendors which have pre-configured agents available.
| Allen-Bradley | Hilscher | SEW |
| ABB | Hirschmann | COPA-DATA |
| Axis Communications | Priva | Kawasaki Robotics |
| B&R | Beijer | Sick |
| Beckhoff | Horner | Crouzet |
| Bihl+Wiedemann | Pro-face | Keyence |
| Bosch Rexroth | IDEC | Siemens |
| BRControls | Rockwell Automation | Danfoss |
| Cognex | ifm electronic | Kollmorgen |
| Comau Robotics | RRAMAC, LLC | Stoeber |
| Control Techniques | IMO | Delta Electronics |
| Crouzet | Saia-Burgess | Koyo |
| Danfoss | InduSoft | Trio Motion |
| Eaton Moeller | Schneider Electric | TP Radio |
| ELAU | Inovance | KUKA Robotics |
| Eminent | Secomea | Kvaser |
| ESA | Control Techniques | Unitronics |
| Exor | Invensys Wonderware | Universal Robots |
| FANUC Robotics | Mitsubishi Electric | Vacon |
| Fatek Automation | Moxa | VIPA |
| FlexEm | Omron | Wago |
| GE IP | Panasonic | Weintek |
| Grundfos | Parker | Yaskawa |
| Hakko | PEAK-System | |
| GE IP |
If you cannot find your particular vendor in the list, it simply means that there is no such pre-configuration yet. It does not indicate that connection to that specific vendor equipment is impossible.
Instead, it is the suggested to try either a Generic or Custom Agent.
Custom Agents
For specific use cases or devices with unique port configurations the SiteManager provides a option to create a “Custom Agent”. This agent type allows you to define the exact ports and settings for your specific device needs.
Besides agent customization options; the Custom Agent also contains Advanced Agent types such as Routing (Scada) agent, Forwarding agent, Ping Agent and more.
In summary, agents are the link between a device and the gate manager, defining the type of connection granted to the device.
Whether you're using a generic agent, a vendor-specific agent, or a custom configuration, agents ensure secure remote access is established according to your requirements.