Internet Control Message Protocol (ICMP) defines a small number of messages used for diagnostic and management purposes. ICMP depends on IP to move packets around the network on its behalf. The fundamentals of ICMP are defined in RFC 792. RFC 1122 summarises the requirements that must be met by an ICMP implementation in an Internet host, and RFC 1812 summarises the ICMP requirements for an Internet router.

No. It requires root access on unix systems. However, using REBOL/Command you can call a DLL that supports it.

ICMP stands for 'Internet Control Message Protocol', it is a Network layer of Internet protocol that reports errors and provides other information relevant to IP packet processing. ICMP sends the following messages: Flow Control, Destination Unreachable, Redirecting Routes and Echo Message. For example, the UNIX command Ping is based on ICMP to test whether a particular computer is connected to the Internet.

A 'Ping' is a technique for sending an ICMP (Internet Control Message Protocol) packet(s) to a remote host. If the remote host is up, and supports ICMP, a control message, or packet, will be sent back to the sender. This technique provides a mechanism for feedback about communication problems in a networked environment. aspNetPing abstracts this mechanism in an easy to use manner for the programmer. For more information about ICMP, check out the RFC 792 at http://www.faqs.org/rfcs/rfc792.html

LB-8000 sends an ICMP echo request to real servers and sees if the ICMP reply comes back from that real server. If not, LB-8000 will think that real server is down and st

ICMP Rate Limiting is an ingress feature that limits inbound ICMP traffic to a percentage of bandwidth.

ICMP Redirect tells the recipient system to override something in its routing table. It is legitimately used by routers to tell hosts that the host is using a non-optimal or defunct route to a particular destination, i.e., the host is sending it to the wrong router. The wrong router sends the host back an ICMP Redirect packet that tells the host what the correct route should be.

ICMP timeout should be generated when the TTL field in the IP header of an incoming packet is one or zero before it is decremented. Only generating an ICMP message if the TTL of the packet is zero after decrementing will lead to strange traceroute output and won't get full credit. The stub code only saves the first 96 bytes of the packets it receives and the generated ICMP packets are 98 bytes, hence Ethereal's checksum does not take into account the last 2 bytes.

No. ICMP Rate Limiting is applied to all ICMP traffic and does not distinguish between different subtypes of ICMP traffic.

This is the kernel telling you that some activity is provoking it to send more ICMP or TCP reset (RST) responses than it thinks it should. ICMP responses are often generated as a result of attempted connections to unused UDP ports. TCP resets are generated as a result of attempted connections to unopened TCP ports.

Higher level of health check gives a more accurate result whether servers are functioning properly. For example, a server that correctly returns an ICMP request, i.e. OK on ICMP check, does not mean the application running on that server is working properly. However, if a web server can return the right web page, i.e. OK on contents check, you will be able to say that server is still alive.