Juniper-PIM-MIB :: juniPimNumHelloRcvd

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › Juniper-PIM-MIB › juniPimNumHelloRcvd

juniPimNumHelloRcvd

Module: Juniper-PIM-MIB

OID (symbolic): Juniper-PIM-MIB::juniPimNumHelloRcvd

OID (numeric): 1.3.6.1.4.1.4874.2.2.43.1.1.1

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: Total number of Hellos received by PIM on this router.

What is juniPimNumHelloRcvd?

A router-wide counter of PIM Hello messages received across all interfaces, letting an admin get a quick sense of PIM neighbor-discovery activity without walking the per-interface table.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.43.1.1.1
snmpwalk -v2c -c public <target> Juniper-PIM-MIB::juniPimNumHelloRcvd

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.43.1.1.1.1
snmpget -v2c -c public <target> Juniper-PIM-MIB::juniPimNumHelloRcvd.1

Start monitoring Juniper E-series router (PIM multicast protocol counters) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Juniper-PIM-MIB::juniPimNumHelloRcvd OID value, configure state conditions and alerts, and monitor any Juniper E-series router (PIM multicast protocol counters) from a single console.

How to Use in IPNetwork Monitor

Select a Juniper E-series router (PIM multicast protocol counters) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type juniPimNumHelloRcvd into the Find box to locate it in the OID tree, then select it and click OK. It reports the total number of Hellos received by PIM on this router. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an Integer32-type OID, Value bounds is the most useful condition here — trigger an alert if the count changes from its expected baseline, since that would indicate the underlying set of items changed unexpectedly. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.4874juniperUniJuniper-UNI-SMI
1.3.6.1.4.1.4874.2juniperUniMibsJuniper-UNI-SMI
1.3.6.1.4.1.4874.2.2juniMibsJuniper-MIBs
1.3.6.1.4.1.4874.2.2.43juniPimMIBJuniper-MIBs
Numeric OIDNameModule
1.3.6.1.4.1.4874.2.2.43.1juniPimMIBObjectsJuniper-PIM-MIB
1.3.6.1.4.1.4874.2.2.43.1.1juniPimGlobalJuniper-PIM-MIB
1.3.6.1.4.1.4874.2.2.43.1.1.1juniPimNumHelloRcvdJuniper-PIM-MIB