This diagram visualizes the connections between the DPOD All-in-One instance and the other components on the network, and is followed by a table elaborating the firewall rules that need to be defined for DPOD to be able to communicate with the rest of the components.
...
From | To | Ports (Defaults) | Protocol | Usage |
|---|---|---|---|---|
DPOD Instance | Each Monitored Device | 5550 (TCP) | HTTPS | Monitored device administration management interface. If the SOMA port is different than 5550 - the port should be changed accordingly. |
DPOD Instance | DNS Server | 53 (TCP and UDP) | DNS | DNS services. Static IP address may be used. |
DPOD Instance | NTP Server | 123 (UDP) | NTP | Time synchronization |
DPOD Instance | Organizational mail server | 25 / 465 / 587 (TCP) | SMTP/S | Send reports/alerts/shares/etc. by email |
DPOD Instance | LDAP | 389 / 636 (TCP) 3268 / 3269 (TCP) | LDAP/S | Authentication & authorization. Can be over SSL. |
NTP Server | DPOD Instance | 123 (UDP) | NTP | Time synchronization |
Each Monitored Device | DPOD Instance | 60000-60009 (TCP) | Syslog | Syslog data |
Each Monitored Device | DPOD Instance | 60020-60029 (TCP) | HTTP | WS-M Payloads (optional) |
API-Connect Analytics Ingestion Pods | DPOD Instance | 60020-60029 (TCP) | HTTP/S | API-Connect Analytics Offload (optional) |
Users IPs | DPOD Instance | 443 (TCP) | HTTPS | DPOD's Web Console |
Admins IPs | DPOD Instance | 22 (TCP) | TCP | SSH |
...