Firewall ports: Difference between revisions

From wiki.comcert.com
Jump to navigation Jump to search
No edit summary
No edit summary
Line 84: Line 84:
! scope="col" | role
! scope="col" | role
|-
|-
|  
| tcp/80
|  
| http
|  
| web UI
|-
|-
|  
| tcp/22
|  
| ssh
|  
| CLI when enabled
|}
|}


===   ===
===   ===


=== Outbound nPoint ===
=== Outbound nPoint* ===


{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px;"
Line 103: Line 103:
! scope="col" | role
! scope="col" | role
|-
|-
|  
| tcp/443
|  
| https
|  
| communication with nPoint
|-
|-
|  
|  
Line 112: Line 112:
|}
|}


(*) outbound services are depending on the features that are in use.
(*) outbound services are heavily depending on the Service Test that are configured on nGeniusPULSE.


 
 

Revision as of 15:30, 21 July 2018

Introduction

Solution

Please remember that Pulse, Software nPoint and Hardware nPoint are communication the same way.

Inbound nGeniusPULSE server

destination  service role
tcp/8443 https communication with nGeniusONE
tcp/443 https

secure web UI

communication with nPoint

tcp/80 http web UI
udp/514 syslog syslog receiver
tcp/22 ssh CLI
udp/123 ntp network time server

 

Outbound nGeniusPULSE server*

destination  service role
udp/123 ntp network time synchronozation
udp/161 snmp snmp
tcp/443 https

communication with virtual center and wireless controller

ip protocol #1 type 0 and 8 icmp echo request/reply ping monitorred devices

(*) outbound services are depending on the features that are in use.

 

Inbound nPoint

destination service role
tcp/80 http web UI
tcp/22 ssh CLI when enabled

 

Outbound nPoint*

destination service role
tcp/443 https communication with nPoint
     

(*) outbound services are heavily depending on the Service Test that are configured on nGeniusPULSE.