Internal communications and firewall ports: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 12: | Line 12: | ||
=== Standalone nGeniusONE Server === | === Standalone nGeniusONE Server === | ||
<span style="color:#0000FF;">* | <span style="color:#0000FF;">* vSTREAM Agent packet streaming option</span> | ||
[[File:NG1Standalone.png|border|center|NG1Standalone.png]] | [[File:NG1Standalone.png|border|center|NG1Standalone.png]] | ||
Line 20: | Line 20: | ||
=== Distibuted nGeniusONE Server === | === Distibuted nGeniusONE Server === | ||
<span style="color:#0000FF;">* | <span style="color:#0000FF;">* vSTREAM Agent packet streaming option </span> | ||
[[File:NG1Distributed.png|border|center|NG1Distributed.png]] | [[File:NG1Distributed.png|border|center|NG1Distributed.png]] |
Revision as of 08:42, 15 February 2020
Introduction
These intra-nGenius ONE system communications must be allowed by every firewall and ACL in the path between these servers and data sources. All servers require access to DNS and NTP. If you opt for external user authentication (LDAP, RADUIS, ...), access to the authentication servers is required for nGenius Server, nGenius Global Manager, nGenius For Flows and nGenius Local Server.
We recommend you print these images and write the corresponding IP addresses on it; it will faciltate the creation of firewall policies.
Solution
Standalone nGeniusONE Server
* vSTREAM Agent packet streaming option
Distibuted nGeniusONE Server
* vSTREAM Agent packet streaming option