Firewall ports: Difference between revisions

Revision as of 15:36, 21 July 2018

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

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

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.

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

destination	service	role
tcp/443	https	communication with nPoint

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

Even when there's no Service Test running on the nPoint, the nPoint will contact nGeniusPULSE server every minute to update its configuration.

Revision as of 15:36, 21 July 2018 (view source) Bert (talk \| contribs) No edit summary ← Older edit		Revision as of 15:36, 21 July 2018 (view source) Bert (talk \| contribs) No edit summary Newer edit →
Line 110:		Line 110:
	(*) outbound services are depending on the Service Test configured on nGeniusPULSE.		(*) outbound services are depending on the Service Test configured on nGeniusPULSE.

	Even when there's no Service Test running on the nPoint, the nPoint will contact nGeniusPULSE server every minute to ~~collect new or updated~~ configuration.		Even when there's no Service Test running on the nPoint, the nPoint will contact nGeniusPULSE server every minute to update its configuration.