Internal communications and firewall ports: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
== Solution == | == Solution == | ||
=== Standalone nGeniusONE Server === | === Standalone nGeniusONE Server === | ||
| Line 24: | Line 23: | ||
|- | |- | ||
| style="width: 52px;" | IS | | style="width: 52px;" | IS | ||
| style="width: 173px;" | InfiniStream/vSTREAM | | style="width: 173px;" | InfiniStream/vSTREAM | ||
|} | |} | ||
| Line 48: | Line 47: | ||
|- | |- | ||
| style="width: 52px;" | IS | | style="width: 52px;" | IS | ||
| style="width: 173px;" | InfiniStream/vSTREAM | | style="width: 173px;" | InfiniStream/vSTREAM | ||
|} | |} | ||
Revision as of 18:51, 14 February 2020
Introduction
These communication must be allowed by every firewall in the path between these devices. All servers require access to DNS and NTP. In case of external authentication (LDAPS, RADUIS, ...) access to these authentication servers is required for NGS or NGGM, NGFF and NGLS. Please note that you may have Flow Collectors (FC) and InfiniSteam (IS) on different locations and on different subnets.
We recommend you print this page and write the corresponding IP addresses on the map.
Solution
Standalone nGeniusONE Server
Legend:
| NGS | nGenius Server |
| FC | FlowCollector |
| IS | InfiniStream/vSTREAM |
Distibuted nGeniusONE Server
Legend:
| NGGM | nGenius Global Manager |
| NGFF | nGenius for Flow |
| NGLS | nGenius Local Server |
| FC | FlowCollector |
| IS | InfiniStream/vSTREAM |
