HUAWEI-IPMCAST-MIB :: hwIpMcastRouteDifferentInIfOctets

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsHUAWEI-IPMCAST-MIBhwIpMcastRouteDifferentInIfOctets

hwIpMcastRouteDifferentInIfOctets

Module: HUAWEI-IPMCAST-MIB

OID (symbolic): HUAWEI-IPMCAST-MIB::hwIpMcastRouteDifferentInIfOctets

OID (numeric): 1.3.6.1.4.1.2011.5.25.149.1.1.1.5.1.22

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: The number of octets contained in IP datagrams which this router has received from these sources and addressed to this multicast group address, which were dropped because they were received on an unexpected interface.

For RPF checking protocols (such as PIM-SM), these packets arrived on interfaces other than hwIpMcastRouteInIfIndex, and were dropped because of this failed RPF check. (RPF paths are 'Reverse Path Forwarding' path; the unicast routes to the expected origin of multicast data flows).

Other protocols may drop packets on an incoming interface check for different reasons (for example, BIDIR-PIM performs a DF check on receipt of packets). All packets dropped as a result of an incoming interface check are counted here.

If this counter increases rapidly, this indicates a problem. A significant quantity of multicast data is arriving at this router on unexpected interfaces, and is not being forwarded.

For guidance, if the rate of increase of this counter exceeds 1% of the rate of increase of hwIpMcastRouteOctets, then there are multicast routing problems that require investigation.

Discontinuities in this monotonically increasing value occur at re-initialization of the management system. Discontinuities can also occur as a result of routes being removed and replaced, which can be detected by observing the value of hwIpMcastRouteTimeStamp.

What is hwIpMcastRouteDifferentInIfOctets?

Counts octets dropped because they arrived on an interface other than the one this route expected (an RPF check failure, or for BIDIR-PIM, a failed designated-forwarder check). The DESCRIPTION notes that if this counter's growth rate exceeds about 1% of hwIpMcastRouteOctets's growth rate, it signals a real multicast routing problem worth investigating.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2011.5.25.149.1.1.1.5.1.22
snmpwalk -v2c -c public <target> HUAWEI-IPMCAST-MIB::hwIpMcastRouteDifferentInIfOctets

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2011.5.25.149.1.1.1.5.1.22.1
snmpget -v2c -c public <target> HUAWEI-IPMCAST-MIB::hwIpMcastRouteDifferentInIfOctets.1

Start monitoring Huawei Layer 3 switch or router (IP multicast routing/forwarding) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HUAWEI-IPMCAST-MIB::hwIpMcastRouteDifferentInIfOctets OID value, configure state conditions and alerts, and monitor any Huawei Layer 3 switch or router (IP multicast routing/forwarding) from a single console.

OID Breakdown

Upper-level ancestors (9 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.2011huaweiHUAWEI-3COM-OID-MIB
1.3.6.1.4.1.2011.5huaweiMgmtHUAWEI-3COM-OID-MIB
1.3.6.1.4.1.2011.5.25huaweiDatacommHUAWEI-3COM-OID-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2011.5.25.149hwMcastHUAWEI-IPMCAST-MIB
1.3.6.1.4.1.2011.5.25.149.1hwIpMcastMibHUAWEI-IPMCAST-MIB
1.3.6.1.4.1.2011.5.25.149.1.1hwIpMcastMibObjectsHUAWEI-IPMCAST-MIB
1.3.6.1.4.1.2011.5.25.149.1.1.1hwIpMcastHUAWEI-IPMCAST-MIB
1.3.6.1.4.1.2011.5.25.149.1.1.1.5hwIpMcastRouteTableHUAWEI-IPMCAST-MIB
1.3.6.1.4.1.2011.5.25.149.1.1.1.5.1hwIpMcastRouteEntryHUAWEI-IPMCAST-MIB
1.3.6.1.4.1.2011.5.25.149.1.1.1.5.1.22hwIpMcastRouteDifferentInIfOctetsHUAWEI-IPMCAST-MIB