ALCATEL-IND1-IPMCAST-MIB :: alaIpMcastRouteDifferentInIfOctets

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsALCATEL-IND1-IPMCAST-MIBalaIpMcastRouteDifferentInIfOctets

alaIpMcastRouteDifferentInIfOctets

Module: ALCATEL-IND1-IPMCAST-MIB

OID (symbolic): ALCATEL-IND1-IPMCAST-MIB::alaIpMcastRouteDifferentInIfOctets

OID (numeric): 1.3.6.1.4.1.6486.801.1.2.1.10.10.2.1.1.2.1.22

Node type: OBJECT-TYPE

Type: Counter32

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 alaIpMcastRouteInIfIndex, 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 alaIpMcastRouteOctets, 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 alaIpMcastRouteTimeStamp.

What is alaIpMcastRouteDifferentInIfOctets?

Counts the bytes contained in multicast packets that were dropped because they arrived on an unexpected interface (RPF failures). A persistent increase alongside alaIpMcastRouteDifferentInIfPackets indicates ongoing RPF mismatches.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6486.801.1.2.1.10.10.2.1.1.2.1.22
snmpwalk -v2c -c public <target> ALCATEL-IND1-IPMCAST-MIB::alaIpMcastRouteDifferentInIfOctets

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6486.801.1.2.1.10.10.2.1.1.2.1.22.1
snmpget -v2c -c public <target> ALCATEL-IND1-IPMCAST-MIB::alaIpMcastRouteDifferentInIfOctets.1

Start monitoring Alcatel-Lucent Enterprise OmniSwitch switches with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ALCATEL-IND1-IPMCAST-MIB::alaIpMcastRouteDifferentInIfOctets OID value, configure state conditions and alerts, and monitor any Alcatel-Lucent Enterprise OmniSwitch switches from a single console.

OID Breakdown

Upper-level ancestors (13 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.6486alcatelALCATEL-IND1-BASE
1.3.6.1.4.1.6486.801alcatelIND1BaseMIBALCATEL-IND1-BASE
1.3.6.1.4.1.6486.801.1alcatelIND1ManagementALCATEL-IND1-BASE
1.3.6.1.4.1.6486.801.1.2managementIND1SoftwareALCATEL-IND1-BASE
1.3.6.1.4.1.6486.801.1.2.1softwareIND1EntitiesALCATEL-IND1-BASE
1.3.6.1.4.1.6486.801.1.2.1.10softentIND1RoutingALCATEL-IND1-BASE
1.3.6.1.4.1.6486.801.1.2.1.10.10routingIND1IpmrmALCATEL-IND1-BASE
Numeric OIDNameModule
1.3.6.1.4.1.6486.801.1.2.1.10.10.2alaIpMcastMIBALCATEL-IND1-IPMCAST-MIB
1.3.6.1.4.1.6486.801.1.2.1.10.10.2.1alaIpMcastMIBObjectsALCATEL-IND1-IPMCAST-MIB
1.3.6.1.4.1.6486.801.1.2.1.10.10.2.1.1alaIpMcastALCATEL-IND1-IPMCAST-MIB
1.3.6.1.4.1.6486.801.1.2.1.10.10.2.1.1.2alaIpMcastRouteTableALCATEL-IND1-IPMCAST-MIB
1.3.6.1.4.1.6486.801.1.2.1.10.10.2.1.1.2.1alaIpMcastRouteEntryALCATEL-IND1-IPMCAST-MIB
1.3.6.1.4.1.6486.801.1.2.1.10.10.2.1.1.2.1.22alaIpMcastRouteDifferentInIfOctetsALCATEL-IND1-IPMCAST-MIB