|
|
| Line 11: |
Line 11: |
|
| |
|
| == Solution == | | == Solution == |
|
| |
| {| border="0" cellpadding="0" cellspacing="0" width="497"
| |
| |- height="20"
| |
| | colspan="3" height="20" style="text-align: center;" width="497" | '''TVC'''
| |
| |- height="20"
| |
| | colspan="3" height="20" style="text-align: center;" | Inbound
| |
| |- height="20"
| |
| | height="20" | Role
| |
| | Protocol/Port
| |
| | Service
| |
| |- height="19"
| |
| | height="19" | User Portal
| |
| | TCP/443
| |
| | HTTPS
| |
| |- height="19"
| |
| | height="19" | Management
| |
| | TCP/22
| |
| | SSH
| |
| |- height="20"
| |
| | height="20" |
| |
| |
| |
| |
| |
| |- height="20"
| |
| | colspan="3" height="20" style="text-align: center;" | Outbound
| |
| |- height="20"
| |
| | height="20" | Role
| |
| | Protocol/Port
| |
| | Service
| |
| |- height="19"
| |
| | height="19" | Service Enablers
| |
| | UDP/53
| |
| | DNS
| |
| |- height="19"
| |
| | height="19" |
| |
| | TCP/389, TCP/636
| |
| | LDAP
| |
| |- height="19"
| |
| | height="19" |
| |
| | UDP/123
| |
| | NTP
| |
| |- height="19"
| |
| | height="19" |
| |
| |
| |
| |
| |
| |- height="19"
| |
| | height="19" | Application
| |
| | UDP/161
| |
| | SNMP (NetFlow Devices)
| |
| |- height="20"
| |
| | height="20" |
| |
| |
| |
| |
| |
| |}
| |
|
| |
|
| | | |
|
| |
|
| | | |
Revision as of 20:05, 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