Unisphere-Data-PIM-MIB :: usdPimNumHelloRcvd

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › Unisphere-Data-PIM-MIB › usdPimNumHelloRcvd

usdPimNumHelloRcvd

Module: Unisphere-Data-PIM-MIB

OID (symbolic): Unisphere-Data-PIM-MIB::usdPimNumHelloRcvd

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 usdPimNumHelloRcvd?

The total count of PIM Hello messages this router has received across all interfaces, a baseline indicator that PIM neighbor discovery is actively working.

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> Unisphere-Data-PIM-MIB::usdPimNumHelloRcvd

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> Unisphere-Data-PIM-MIB::usdPimNumHelloRcvd.1

Start monitoring Unisphere/Juniper ERX multicast-enabled router (PIM Hello/Join-Prune/Assert counter status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Unisphere-Data-PIM-MIB::usdPimNumHelloRcvd OID value, configure state conditions and alerts, and monitor any Unisphere/Juniper ERX multicast-enabled router (PIM Hello/Join-Prune/Assert counter status) from a single console.

How to Use in IPNetwork Monitor

Select an Unisphere/Juniper ERX multicast-enabled router (PIM Hello/Join-Prune/Assert counter status) 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 usdPimNumHelloRcvd 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 (12 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
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
Numeric OIDNameModule
1.3.6.1.4.1.4874.2.2.43.1.1.1usdPimNumHelloRcvdUnisphere-Data-PIM-MIB