Remote Agents In Short

Remote Agents functionality allows to separate some of the application options to make them work in a disperse way. EasyDCIM control panel is a host application, whereas the remote agent executes tasks delivered by such application only. The communication between the main platform and the remote agent is based on the HTTP protocol and a server working on the 8080 port. Tasks are executed in the real time via API. The current status of a task can be verified in the main application – EasyDCIM. Although both of the applications may work in separate subnets, communication between the main application and the remote agent is a must.

Do I need a Remote Agent?

By default, a remote agent is installed locally along with the main installation of EasyDCIM platform. If you have only one location or your network configuration allows it, you do not need to install additional remote agents. You can simply configure a remote agent to be responsible for your local location.

If you have many locations spread around the world, you need to configure an additional remote agent for each of them. It will be responsible for installing operating systems, collecting information in the polling process or the IPMI proxy server.


Here are the only requirements for remote agents:

  • Supported operating system: Debian 12 “bookworm”
  • EasyDCIM must be accessible from a remote agent in order to synchronize the data
  • Remote Agent must be accessible from EasyDCIM in order to synchronize the data
  • Open ports on the remote agent server: 8080, range 5901-6000 (for IPMI Proxy)

Memory and processor

When it comes to RAM and CPU, the requirements increase linearly as the number of devices and ethernet ports added in the system grows. A process that uses the most of system resources is ‘Pooling Process’, activated automatically within the 5-minute intervals. We recommend a machine with 4GB of RAM and several processor cores that will help to quicken loading graphs simultaneously.

Storage I/O throughput

Storage I/O Throughput is the narrowest bottleneck of the system. While drawing graphs or collecting data in the process of pooling there is a huge amount of reading/writing actions performed. We recommend the use of SSDs which provide considerable efficiency increase.