Red Hat NETWORK SATELLITE 5.1.1 - RELEASE NOTES, Reference Manual

Page: 239 / 268

Network Services::Remote Ping
227
C.8.7. Network Services::Remote Ping
The Network Services::Remote Ping probe determines if the monitored system can
ping
a specified
IP address. It also monitors the packet loss and compares the round trip average against the Warning
and Critical threshold levels. The required
Packets to send
value allows you to control how many
ICMP ECHO packets are sent to the address. This probe collects the following metrics:
• Round-Trip Average — The time it takes in milliseconds for the ICMP ECHO packet to travel to and
from the IP address.
• Packet Loss — The percent of data lost in transit.
The
IP Address
field identifies the precise address to be pinged. Unlike the similar, optional field
in the standard Ping probe, this field is required. The monitored system directs the ping to a third
address, rather than to the RHN Server. Since the Remote Ping probe tests connectivity from the
monitored system, another IP address must be specified. To conduct pings from the RHN Server
to a system or IP address, use the standard Ping probe instead. Refer to
Section C.8.5, “Network
Services::Ping”
.
Requirements
— The Red Hat Network Monitoring Daemon (
rhnmd
) must be running on the
monitored system to execute this probe.
Field Value
IP Address*
Packets to send*
20
Timeout* 10
Critical Maximum Round-Trip Average
Warning Maximum Round-Trip Average
Critical Maximum Packet Loss
Warning Maximum Packet Loss
Table C.43. Network Services::Remote Ping settings
C.8.8. Network Services::RPCService
The Network Services::RPCService probe tests the availability of remote procedure call (RPC)
programs on a given IP address. It collects the following metric:
• Remote Service Latency — The time it takes in seconds for the RPC server to answer a connection
request.
RPC server programs, which provide function calls via that RPC network, register themselves in 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.