TruView Firewall ports: Difference between revisions

From wiki.comcert.com
Jump to navigation Jump to search
No edit summary
No edit summary
Line 108: Line 108:
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
|-
|-
| style="width: 234px;" | destination
| style="width: 234px;" | '''destination'''
| style="width: 106px;" | service
| style="width: 106px;" | '''service'''
| style="width: 143px;" | role
| style="width: 143px;" | '''role'''
|-
|-
| style="width: 234px;" | tcp/443
| style="width: 234px;" | tcp/443

Revision as of 20:34, 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 ports

destination service role
tcp/443 https User Portal
tcp/22 ssh Management CLI

TVC outbound ports

destination service role
udp/53 dns domain name service
tcp/389 ldap remote authentication
tcp/636 sldap secure remote authentication
udp/123 ntp network time synchronization
tcp/25 smtp mailrelay
udp/161 snmp  

TVF inbound ports

destination service role
tcp/443 https User Portal
tcp/22 ssh Management CLI
udp/2055, udp/6343 netflow  

TVF outbound ports

destination service role
udp/53 dns  
udp/123 ntp network time synchronization
udp/161 snmp  

TruView internal communication ports

destination service role
tcp/443 https TVC -> TVF
tcp/443 https TVF -> TVC