OpManager keeps an eye on the availability of devices in your environment through the use of protocols such as SNMP, TCP and ICMP. Upon addition of a device to OpManager, the ICMP protocol is by default set as the protocol used for device availability monitoring. This monitoring is done using the "ping" command that sends ping packets (ICMP echo request) to the monitored device according to the configured monitoring interval frequency. The availability metrics like availability percentage, packet loss and response time as shown below, are calculated on the basis of the ping response (ICMP echo reply) received from the destination device.
OpManager executes a ping action based on a set of predefined parameters like count (no. of echo requests sent), timeout, packetSize, etc., each of which has a set of recommended values for the optimal working of OpManager. The new update of OpManager (build no. 126295) improves security and scalability by featuring a restricted range of values. It is now essential to use the values that lie within this restrictions in the "ping.properties" file, instead of using custom parameters.
Please refer to this table for the configuration of parameters in the "ping.properties" file :
|
Parameter Name |
Range |
Description |
|---|---|---|
|
count |
1 to 4 |
No. of ping packets sent |
|
successCount |
1 to 4 |
Ping packet count when device is up and running |
|
failureCount |
1 to 4 |
Ping packet count when device is currently down |
|
packetSize |
1 to 500 |
Size of the ping packet (in bytes) |
|
timeout |
1 to 20 |
Timeout for each reply (in seconds) |
|
retries |
1 to 5 |
Number of retries if device is unreachable. |
Note : In case the user configures the parameters with a value higher than recommended, OpManager will by default, consider the maximum permissible value within the range.
Thank you for your feedback!
