A way to ensure that the TMG server can still communicate with the Nagios server after installing the client

Recently, as the company's business needs to be ready to build a Nagios platform under the Linux platform to monitor the performance of some important servers, disk and related services, personal feeling is very interesting, because in the previous posting also mentioned the current server monitoring in the enterprise we will generally use the Microsoft platform under the Scom, Third party manufacturers to develop some of their own monitoring platform, and secondly, there are many companies will be monitoring platform on the Linux platform, and the previous blog mentioned in the Nagios, that is, under the Linux platform a relatively good choice, and now, I also have the opportunity to contact and open some of the contents of the open platform, such as some things and Linux, of course, because has been studying Microsoft Windows Server platform, to tell the truth to begin to learn Linux is really some not adapt, Hee, after all, not as graphic as windows, On the Linux platform we know that many server management or platform software configuration is based on command line operations, in the recent research Nagios, there is no way, can only honestly to check some information and some documents to do, after a few configuration to this evening has been able to mail the alarm, Hee, Some small happy, although this is not too difficult, but I still went to consult some Linux New Bei people and their own to think about a period of time, feel the night reading and learning not in vain, Hee, the platform was completed, but yesterday, some colleagues to report that found to TMG installed Nsclient client, The relevant parameter content has also been modified, why other servers can be monitored normally, but only TMG and TMG based VPN platform has not been able to establish relevant monitoring connection with the server?

In fact, this problem is due to the server installed after the TMG, the firewall was taken over by TMG, and by default the TMG firewall was isolating itself from the existing network, and we did not have the ports to use to open and nagios connections, so we could not establish a normal connection, and to solve it, It's better to open the corresponding port. Nagios between the client and the server, need to use 5666 ports, according to this, we create a new port protocol to release, although we said that a new one on the TMG to allow internal to local all communication is also possible, but due to my personal habits, Prefer to open what port to open what port, this will be better, then how to operate it? Let's see.

This column more highlights: http://www.bianceng.cnhttp://www.bianceng.cn/Servers/zs/

1, first in the TMG firewall policy to click the "toolbox", select the Protocol list bar, where we click on the "new"/"agreement", as shown in the following figure;

2, in the pop-up "New Protocol Definition Wizard," Enter the protocol name, as shown in the following figure, I here to facilitate the distinction, I played a "Nagios_morport", and then click the "Next" button;

3, in the pop-up dialog box, we select the "New" button, in the new/Edit Protocol Connection dialog box, set the port range from 5666 to 5666, click the "OK" button, in the Returned dialog box, click the Next button.