Red Hat NETWORK SATELLITE 5.1.0 - CHANNEL MANAGEMENT, Reference Manual

Page: 268 / 300

the RPC network by declaring a program ID and a program name. NFS is an example of a
service that works via the RPC mechanism.
Client programs that wish to use the resources of RPC server programs do so by asking the
machine on which the server program resides to provide access to RPC functions within the
RPC program number or program name. These conversations can occur over either TCP or
UDP (but are almost always UDP).
This probe allows you to test simple program availability. You must specify the program name or
number, the protocol over which the conversation occurs, and the usual timeout period.
Field Value
Protocol (TCP/UDP) udp
Service Name* nfs
Timeout* 10
Critical Maximum Remote Service Latency
Warning Maximum Remote Service Latency
Table C.44. Network Services::RPCService settings
8.9. Network Services::Secure Web Server (HTTPS)
The Network Services::Secure Web Server (HTTPS) probe determines the availability of the
secure Web server and collects the following metric:
• Remote Service Latency — The time it takes in seconds for the HTTPS server to answer a
connection request.
This probe confirms that it can connect to the HTTPS port on the specified host and retrieve the
specified URL. If no URL is specified, the probe fetches the root document. The probe looks for
a HTTP/1. message from the system unless you alter that value. Specifying another port
number overrides the default port of 443.
This probe supports authentication. Provide a username and password in the appropriate fields
to use this feature. Unlike most other probes, this probe returns a CRITICAL status if it cannot
contact the system within the timeout period.
Field Value
URL Path /
Expect Header HTTP/1
Expect Content
UserAgent* NOCpulse-check_http/1.0
Appendix C. Probes
254