This sample is very similar to the ping probe and port probe samples directly above. Thus, we describe it briefly, only.
FTP probe is used to make a connection to the FTP server and then it receives the response from FTP server and sends the QUIT command to terminate the connection. The connection status is saved in the property ftpstatus and the response in the property ftprespmsg.
In our sample, we probe a FTP server, which typically listens to port 21 (the default port for FTP). We send an email alert if the FTP probe cannot connect successfully to the FTP server.
Because this sample is so close to the previous ones, we do not create a new rule set specifically for email alerting. Please view "Ping Probe" for it. This is a good sample of rule set re-use. It might be clever to rename the rule set in such a case. For simplicity reasons, we have not done this here.
Therefore, we begin by creating the new service, done by right-clicking "Running Services":
Monitoring FTP server via a FTP Probe - Figure 1
Use a name of your choosing, leave the defaults as is and click "Next" and then "finish". We have used the name "FTP Probe" in our sample.
After doing so, select the newly created service in the tree view to look at its properties. Be sure to bind it to the "FTP Probe" rule set as seen below:
Monitoring FTP server via a FTP Probe - Figure 2
Save the configuration and restart the service. From now on, the following mail alert is generated when the port cannot be connected to:
Event message:
Facility: 16
Priority: 6
Source: 192.168.1.1
Message:
FTPProbe status="fail" target="192.168.1.1" port="21" netstate="10061" message="Couldn't connect to host"