EasyDCIM Documentation
Back Home
Free Trial Request Get Started

Remote Agent Network Requirements

Troubleshooting Center

# Remote Agent Network Requirements

This guide helps you verify firewall rules, ports, and basic connectivity required by Remote Agents.

Some checks are visible in the Remote Agent dashboard or preflight checks, but network devices and firewalls can still block traffic between specific networks. Use this page when the agent is online, but polling, provisioning, IPMI, Redfish, SNMP, or noVNC-related functions do not work as expected.

# Traffic Overview

Source Destination Protocol / port Used for
Remote Agent EasyDCIM master panel HTTPS, usually TCP 443 Internal API communication, polling device list, stats updates.
PXE booting server Remote Agent UDP 67/68 DHCP request and response during PXE boot.
PXE booting server Remote Agent UDP 69 TFTP bootloader download.
PXE booting server Remote Agent TCP 8080 by default iPXE scripts, kickstart/preseed/autoinstall data, OS installation files served by the Remote Agent.
Windows installer / provisioning client Remote Agent TCP 445 SMB access for Windows installation files, when Windows provisioning is used.
Remote Agent Switches, PDUs, servers UDP 161 SNMP polling and discovery.
Remote Agent BMC / IPMI interface UDP 623 IPMI power control and IPMI checks.
Remote Agent BMC / Redfish interface HTTPS, usually TCP 443 Redfish power usage, power sensors, thermal sensors, and Redfish discovery.
Remote Agent Network devices TCP 22 or vendor-specific ports Switch drivers or SSH-based automation, if configured.
User browser EasyDCIM server TCP 6081-6200 noVNC sessions when IPMI Proxy/noVNC is used.

The exact ports can differ if your environment uses custom web ports, reverse proxies, non-standard BMC ports, or custom Remote Agent settings.

# Remote Agent to EasyDCIM Communication

The Remote Agent must be able to reach the EasyDCIM master panel URL configured for the agent.

For polling, the agent calls:

/internal/api/app/{APP_ID}/polling/devices

Quick test from the Remote Agent server:

curl -k -sS -o /tmp/polling-devices.json -w \
  "http_code=%{http_code} time_total=%{time_total}s\n" \
  -H "Accept: application/json" \
  -H "X-Authorization: [YOUR_API_KEY]" \
  "https://[MASTER_IP]/internal/api/app/[APP_ID]/polling/devices"

If this request times out, check routing, DNS, firewall rules, and the EasyDCIM master panel response time. See also: Remote Agent Polling.

# PXE and OS Installation Traffic

PXE boot requires more than one protocol. A successful DHCP response does not mean that TFTP or HTTP access also works.

Check DHCP traffic:

tcpdump -n -i any udp port 67 or udp port 68

Check TFTP traffic:

tcpdump -n -i any udp port 69

Check whether the Remote Agent HTTP endpoint is reachable from the provisioning network:

curl -I http://[REMOTE_AGENT_PXE_IP]:8080/

If the PXE client is in a different VLAN than the Remote Agent, configure DHCP relay / IP helper on the router or L3 switch. Broadcast DHCP requests normally do not cross VLAN boundaries without relay.

For detailed PXE boot troubleshooting, see OS Installation Troubleshooting.

# SNMP, Redfish, and IPMI Traffic

The Remote Agent must be able to reach the management interfaces of devices assigned to it.

# SNMP

SNMP is used for switches, PDUs, traffic counters, ports, and some discovery operations.

snmpwalk -v2c -c [COMMUNITY] [DEVICE_IP] SNMPv2-MIB::sysObjectID.0

If this fails, check:

  • SNMP version and credentials,
  • ACLs on the device,
  • UDP 161 between the Remote Agent and the device,
  • whether the device allows SNMP from the Remote Agent IP address.

# Redfish

Redfish is used for server power usage, power sensors, thermal sensors, and Redfish discovery.

curl -k -u '[USER]:[PASSWORD]' https://[BMC_IP]/redfish/v1/

If this fails, check:

  • BMC IP address,
  • Redfish credentials,
  • HTTPS access to the BMC,
  • vendor-specific Redfish support,
  • whether the BMC uses a non-standard HTTPS port.

# IPMI

IPMI is used for power control and IPMI-based actions.

ipmitool -I lanplus -H [BMC_IP] -U [USER] -P '[PASSWORD]' chassis status

If this fails, check UDP 623, BMC credentials, IPMI-over-LAN settings, and firewall rules between the Remote Agent and the BMC network.

# SSH Connectivity

Some operations require SSH access from the Remote Agent to network devices or from EasyDCIM tooling to the Remote Agent host, depending on your configuration.

Basic test:

ssh [USER]@[HOST]

If SSH fails, check:

  • TCP 22 or the custom SSH port,
  • allowed source IP addresses,
  • key or password authentication,
  • device-side ACLs,
  • whether the SSH service is running.

# noVNC and IPMI Proxy

When IPMI Proxy/noVNC is used, users connect to noVNC sessions through the EasyDCIM server. The documented noVNC range is:

TCP 6081-6200

If the browser opens a black screen, disconnects immediately, or cannot connect, check whether this port range is reachable from the user network to the EasyDCIM server.

For IPMI Proxy configuration details, see IPMI Proxy.

# Useful First Checks

On the Remote Agent server:

easydcim-control agent status
easydcim-control agent logs -f

For service-level details, see Remote Agent Logs and Diagnostics.