The Gopher Monitor is used to test a Gopher server for availability, as well as its level of responsiveness.
As the Gopher system predates the World Wide Web, it has limited application in today's network environment. However, it is sometimes used to organize files in a hierarchically structured list.
The Gopher Monitor:
- Connects to the Service, performs a blind query (CRLF) and waits for a response.
- Considers the test successful if a valid response is returned within the specified Maximum Test Duration.
- Safely disconnects from the server upon receipt of the opening message.
- Considers the test to have failed if the Gopher server fails to respond, or if it responds with an error code indicating that the Service is not available.
Use the Gopher Monitor to test that:
- A Gopher client can open a connection with a Gopher server
- The server adheres to the Gopher protocol by responding with the correct codes
- The server responds within a required number of seconds
The Test Parameters dialog box is used to specify the parameters that the Gopher Monitor will use to open a connection to the Gopher server.
IP Address / Domain Name
Specify the location of the Gopher server you want to monitor. Both IP Address and Domain Name are valid entries.
Examples of valid Domain names are: www.xyzcompany.com and xyzcompany.com
An example of a valid IP address is: 10.200.100.6
Note: Entering an IP address will eliminate any variables introduced by performing a lookup on the DNS server. If your network uses a DHCP server to dynamically assign IP addresses, enter an IP address only if it is "reserved", otherwise enter a Domain Name.
TCP Port
Specify the Port Number that the target server responds on. By default, the standard Port Number used for Gopher communication (Port 70) is already entered.
When the Monitor is in an Up state, test results are reported as shown in the example below:
rtt - Round-Trip Time. This value indicates the time it took the test packet to reach the monitored resource and return a response to ipMonitor. Round-trip time is measured in milliseconds (ms).
When the Monitor is in a Warn, Down, or Lost state, the Last Result field indicates the problem encountered. Different Monitor types generate specific Error Codes in accordance with the technical capabilities of the Monitor. Refer to the Error Codes section of this document for details.
For information on settings common to all Monitor types, such as Identification, Timing, Notification Control and Recovery Parameters, refer to General Monitor Settings.
The following error codes are generated by the Gopher Monitor. Error codes are displayed in Real-time and Historical Reports. They can also be added to Alerts using Tokens.
| Message | Details |
|---|---|
| Configuration information for this item is missing some required fields | A required element(s) for Monitor connectivity or testing was not supplied to ipMonitor. |
| Unable to connect to the remote device | The specified address to the connection-based Service is unavailable. |
| Could not obtain an IP address for the remote device | The supplied address was not a valid IP address OR the Server Domain Name could not be translated into an IP address. The Server Domain Name may refer to a local machine name, or a fully qualified domain name. |
| The remote device timed out before sending a response | The resource being monitored did not respond within the maximum allowable time. |
| Unexpected disconnection from the remote device | The server disconnected during the test transaction. |
For information on other features and concepts related to those discussed in this article, refer to the following ipMonitor resources:
< Back
Last Updated: March 30, 2007 | What did you think of this topic?