ALCATEL-IND1-PIM-STD-MIB :: alaPimInvalidJoinPruneMsgsRcvd

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsALCATEL-IND1-PIM-STD-MIBalaPimInvalidJoinPruneMsgsRcvd

alaPimInvalidJoinPruneMsgsRcvd

Module: ALCATEL-IND1-PIM-STD-MIB

OID (symbolic): ALCATEL-IND1-PIM-STD-MIB::alaPimInvalidJoinPruneMsgsRcvd

OID (numeric): 1.3.6.1.4.1.6486.801.1.2.1.10.6.2.1.38

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of invalid PIM Join/Prune messages that have been received by this device.

A PIM Join/Prune message is invalid if either

o the Group to RP mapping specified by this message does not match the Group to RP mapping on this device, or

o this device believes the group address to be within an SSM address range, but this Join/Prune (*,G) or (S,G,rpt) implies ASM usage.

These conditions can occur transiently while RP mapping changes propagate through the network. If this counter is incremented repeatedly over several minutes, then there is a persisting configuration error that requires correction.

The active Group to RP mapping on this device is specified by the object alaPimGroupMappingPimMode. If there is no such mapping, then the object alaPimGroupMappingPimMode is absent. The RP address contained in the invalid Join/Prune is alaPimInvalidJoinPruneRp.

Invalid Join/Prune messages are discarded. This may result in loss of multicast data affecting listeners downstream of alaPimInvalidJoinPruneOrigin, for multicast data addressed to alaPimInvalidJoinPruneGroup.

Discontinuities in the value of this counter can occur at re-initialization of the management system, for example when the device is rebooted.

What is alaPimInvalidJoinPruneMsgsRcvd?

Reports the total number of invalid PIM Join/Prune messages received by this device, where invalid means the Group-to-RP mapping in the message conflicts with the local mapping. This counter helps detect multicast routing inconsistencies.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6486.801.1.2.1.10.6.2.1.38
snmpwalk -v2c -c public <target> ALCATEL-IND1-PIM-STD-MIB::alaPimInvalidJoinPruneMsgsRcvd

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6486.801.1.2.1.10.6.2.1.38.1
snmpget -v2c -c public <target> ALCATEL-IND1-PIM-STD-MIB::alaPimInvalidJoinPruneMsgsRcvd.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-PIM-STD-MIB::alaPimInvalidJoinPruneMsgsRcvd 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.6routingIND1PimALCATEL-IND1-BASE
Numeric OIDNameModule
1.3.6.1.4.1.6486.801.1.2.1.10.6.2alaPimStdMIBALCATEL-IND1-PIM-STD-MIB
1.3.6.1.4.1.6486.801.1.2.1.10.6.2.1alaPimALCATEL-IND1-PIM-STD-MIB
1.3.6.1.4.1.6486.801.1.2.1.10.6.2.1.38alaPimInvalidJoinPruneMsgsRcvdALCATEL-IND1-PIM-STD-MIB