IPMROUTE-STD-MIB :: ipMRouteNextHopClosestMemberHops

MIB Reference — IPNetwork Monitor

All MIBsIPMROUTE-STD-MIBipMRouteNextHopClosestMemberHops

ipMRouteNextHopClosestMemberHops

Module: IPMROUTE-STD-MIB

OID (symbolic): IPMROUTE-STD-MIB::ipMRouteNextHopClosestMemberHops

OID (numeric): 1.3.6.1.2.1.83.1.1.3.1.9

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description:

The minimum number of hops between this router and any member of this IP multicast group reached via this next-hop on this outgoing interface. Any IP multicast datagrams for the group which have a TTL less than this number of hops will not be forwarded to this next-hop.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.83.1.1.3.1.9
snmpwalk -v2c -c public <target> IPMROUTE-STD-MIB::ipMRouteNextHopClosestMemberHops

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.83.1.1.3.1.9.1
snmpget -v2c -c public <target> IPMROUTE-STD-MIB::ipMRouteNextHopClosestMemberHops.1

How to Use in IPNetwork Monitor

Select a device implementing IPMROUTE-STD-MIB 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 locate ipMRouteNextHopClosestMemberHops under the ipMRouteNextHopEntry branch of IPMROUTE-STD-MIB, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports the minimum number of hops between this router and the nearest member of a given IP multicast group, reached via a specific next-hop. 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 hop count grows well beyond its normal baseline for that group, which can indicate a multicast routing topology problem. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Numeric OIDNameModule
1isoLANART-AGENT
1.3orgBIANCA-BRICK-PPP-MIB
1.3.6dodBIANCA-BRICK-PPP-MIB
1.3.6.1internetBIANCA-BRICK-PPP-MIB
1.3.6.1.2mgmtBKTEL-HFC862-BASE-MIB
1.3.6.1.2.1mib_2CHECKPOINT-MIB-2
1.3.6.1.2.1.83ipMRouteStdMIBIPMROUTE-STD-MIB
1.3.6.1.2.1.83.1ipMRouteMIBObjectsIPMROUTE-STD-MIB
1.3.6.1.2.1.83.1.1ipMRouteIPMROUTE-STD-MIB
1.3.6.1.2.1.83.1.1.3ipMRouteNextHopTableIPMROUTE-STD-MIB
1.3.6.1.2.1.83.1.1.3.1ipMRouteNextHopEntryIPMROUTE-STD-MIB
1.3.6.1.2.1.83.1.1.3.1.9ipMRouteNextHopClosestMemberHopsIPMROUTE-STD-MIB