Port monitor perfex command
Is there anyway we can find out what exact command sitescope is using for a port monitor? I am troubleshooting a port monitor which failed with status "unable to connect to server" but customer claims port was always available and wanted to know how sitescope does the check. I know that it is telnet what is being used to check but interested to see if any specific perfex command is there for it or not
Any help is appreciated...
it's my understanding that the Port monitor doesn't use perfex.
Please find below some troubleshooting hints:
The Port Monitor opens a socket to the specified remote on the port defined in the preferences and then sends a text stream to it. SiteScope captures the returned text stream and parses it for status and any content match set up in the monitor.
The port monitor only monitors the availability of the port itself, it cannot monitor any specific application running on a given port address.
This monitor inherits some properties from the URL Monitor. These are: timeout (if timeout is specified in the monitor definition) and URL status codes.
Everything that is sent and received from the Port monitor is placed in the SiteScope\logs\RunMonitor.log.
By default, the Port monitor will use TCP when connecting to the remote, however you can force it to use UDP by adding the following line to the SiteScope/groups/master.config file:
where <tab> refers to actual tab inserted white space. You will notice that there are other _portMonitor entries already in the master.config. These populate the drop down list in the monitor definition page.
How to Troubleshoot
1) View the SiteScope\logs\RunMonitor.log. This will tell you what was sent to the port and what was received in return.
2) If the monitor fails to connect, telnet to the port from the SiteScope server via the command line as follows:
telnet <server> <port>
If you get any response other than Connection failed OR Connection refused, the port is listening. Otherwise, either the port is not listening (service or daemon not running) or the there is not a valid communication medium between the SiteScope server and the remote server. The latter case would be generally evidenced by timeout's or errors like No route to host.
3) If the status of the monitor is "n/a", this means that the state was no status 200 and not a content match error.
4) By default SiteScope interprets a return code of 220 as a "Good" status. This can be changed by editing the monitor, going to the "Advanced Options" area, and specifying a different return code in the "Match String" field. This will override the default return code match.
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.