TruView Firewall ports: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 94: | Line 94: | ||
| snmp | | snmp | ||
| | | | ||
|} | |||
TruView internal communication | |||
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;" | |||
|- | |||
| style="width: 234px;" | destination | |||
| style="width: 106px;" | service | |||
| style="width: 143px;" | role | |||
|- | |||
| style="width: 234px;" | tcp/443 | |||
| style="width: 106px;" | https | |||
| style="width: 143px;" | TVC -> TVF | |||
|- | |||
| style="width: 234px;" | tcp/443 | |||
| style="width: 106px;" | https | |||
| style="width: 143px;" | TVF -> TVC | |||
|} | |} | ||
Revision as of 20:23, 18 November 2019
Introduction
Please remember that Pulse, Software nPoint and Hardware nPoint are communication the same way.
In general, nPoint is contacting the nGeniusPULSE Server, not the other way around.
Service Test are executed by the nPoint. Device monitoring is done by nGeniusPULSE server or a Collector.
Even when there's no Service Test running on the nPoint, the nPoint will contact nGeniusPULSE Server every minute to update its configuration.
Solution
TVC inbound
| destination | service | role |
| tcp/443 | https | User Portal |
| tcp/22 | ssh | Management CLI |
TVC outbound
| destination | service | role |
| udp/53 | dns | |
| tcp/389,tcp/636 | ldap | |
| udp/123 | ntp | |
| udp/161 | snmp |
TVF inbound
| destination | service | role |
| tcp/443 | https | User Portal |
| tcp/22 | ssh | Management CLI |
| udp/2055, udp/6343 | netflow |
TVF outbound
| destination | service | role |
| udp/53 | dns | |
| udp/123 | ntp | |
| udp/161 | snmp |
TruView internal communication
| destination | service | role |
| tcp/443 | https | TVC -> TVF |
| tcp/443 | https | TVF -> TVC |