Multi IP Ping Monitoring is a monitoring utility that enhances device reachability checks by considering all IP addresses physically associated with a device. It automatically pings these IPs at a configured interval and determines whether the device is reachable.

Business Use Case: Monitors device reachability state by pinging device discovered IP at the first step. If the discovered IP is not reachable, monitor tries to get the reachability info using multiple ips provided as part of a custom parameter at the time of template assignment. If a custom IPs list is not provided, this monitor will try to get the device ip’s list through SNMP by querying OID “1.3.6.1.2.1.4.20.1.1”, and check for the device reachability state. If any of the IPs are being pinged, then the metric values would be 1 - REACHABLE else 0 - UNREACHABLE

Prerequisites

  • A Gateway Management Profile must be mapped to the resource.
  • SNMP-type credentials must be configured on the resource to:
    • Retrieve alternative IPs using the IP-MIB.
    • Retrieve HSRP IPs using the CISCO-HSRP-MIB.

Applying Multi IP Ping Monitoring

To assign the monitoring template:

  1. Go to All Clients and select the desired client.
  2. Navigate to Infrastructure > Resources.
  3. Select the resource where monitoring needs to be applied.
  4. Go to the Templates tab and click + Assign Templates. The Apply Templates screen is displayed.
  1. From the Available Templates , select:
  • Template: Multiple IPs Ping Reachability Monitor - v2.
  • Collector Type: Set to Gateway
  1. Click Assign to configure the template parameters. The Enter Configurations section is displayed.


  1. Enter Value for the Assigned Templates and Configuration Parameters and click Assign.


The templates screen displays the selected templates.

Configuration Parameters

ParameterDisplay NameDefault ValueDescription
multi.ip.ping.reachability.data.bytesData Bytes64Number of bytes in each ping packet.
multi.ip.ping.reachability.pkt.intervalPacket Interval1000Time interval (in ms) between ping packets.
multi.ip.ping.reachability.pkts.countPacket Count5Total number of ping packets per IP.
multi.ip.ping.reachability.discovery.frequencyDiscovery Frequency (in mins)60Frequency at which SNMP discovery runs.
multi.ip.ping.reachability.ip.listCustom IPs ListNoneProvide a comma-separated list of IP addresses. If the management IP is not reachable, these IPs will be used to check the device's reachability.
Note: If you do not assign any alternative IPs of the device, OpsRamp automatically gets them from the SNMP protocol through IP-MIB.
multi.ip.ping.reachability.exclude.ip.listExclude IPs ListNoneProvide a comma-separated list of IP addresses. The specified IPs will be excluded when evaluating the device's reachability.
Note: Users can define IPs to exclude from reachability checks. This parameter is available starting from SaaS version 2025.06-U1 and works with gateway version 19.2.0 onwards.
multi.ip.ping.reachability.include.discovery.ip.listInclude Discovery IPs ListYes/No
  • If set to Yes, OpsRamp considers both custom and discovered alternative IPs after excluding HSRP IPs from the alternative IPs list.
  • If set to No, OpsRamp consider discovered alternative IPs after excluding HSRP IPs from the alternative IPs list, but if custom IPs are configured, it will only consider the custom IPs.
This parameter is available starting from SaaS version 2025.06-U1 and works with gateway version 19.2.0 onwards.

Get Latest Metric Values

Graphical metrics representation

Sample Alert

An alert is triggered when all available IPs (including management and fallback IPs) fail to respond to ping.

Troubleshooting steps

You can verify whether monitoring data is being collected correctly from the Gateway by reviewing logs on either Classic or NextGen Gateway.

In Classic Gateway:

  1. Login in to the Gateway shell.
  2. Enter the Gateway CLI using:

gcli
  1. Enable logging for the monitor:
flag add multi.ip.ping.log on 30
  1. Exit the CLI:

exit
  1. View and verify the logs:

tail -100f /var/log/app/vprobe.log

In Nextgen Gateway:

  1. Login in to the Gateway shell.
  2. Access the vprobe container:
  • If a Kubernetes namespace is configured:
  kubectl exec -it nextgen-gw-0 -c vprobe -n <namespace> -- bash
  • If no namespace is applicable:

kubectl exec -it nextgen-gw-0 -c vprobe -- bash
  1. Enter the Gateway CLI:

gcli
  1. Enable logging for the monitor

flag add multi.ip.ping.log on 30
  1. Exit the CLI:

exit
  1. View the logs:

tail -100f /var/log/app/vprobe.log