![]() ![]() CPU monitoring, memory, disk space, services, processes etc.). ![]() On the NSClient for Windows environments, different monitoring possibilities can be defined on the NSCA section (expl. The NSCA daemon has to be configured in the way that the target IP of the NSCA daemon is the public IP of the central location, which is forwarded from the firewall to the NetEye server. On Linux environments, it is the NSCA, on Windows the NSClient agent is suggested, which also disposes of an NSCA daemon. Servers at the remote location have to have an internet connection (no fix public IP on remote side is needed) on port 5667 to the NetEye server. On the server, which has to be monitored, an NSCA daemon has to be installed. In the following article, I will show you on what you should pay attention. The monitoring of remote locations (locations without direct connection (VPN, MPLS, etc.) to the central NetEye server) is possible through a NSCA daemon. The former are facing a particular challenge, namely the monitoring of components, which are not directly, or via VPN, connected. IT service providers with several customers want to monitor the performance of their customer’s IT infrastructure, as also companies with several branch offices want to. 2015 TobiasGoller NetEye Monitoring Branch Offices Without Direct VPN Connection ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |