| OID | 1.3.6.1.2.1.157.1.38 |
| Module | PIM-STD-MIB (ietf) |
| Nom | pimInvalidJoinPruneMsgsRcvd |
| Acces | readonly |
| Status | current |
| 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 pimGroupMappingPimMode. If there is no such
mapping, then the object pimGroupMappingPimMode is absent.
The RP address contained in the invalid Join/Prune is
pimInvalidJoinPruneRp.
Invalid Join/Prune messages are discarded. This may result
in loss of multicast data affecting listeners downstream of
pimInvalidJoinPruneOrigin, for multicast data addressed to
pimInvalidJoinPruneGroup.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, for example,
when the device is rebooted. |
| Syntaxe | Counter32 (SNMPv2-SMI) |
| Module | PIM-STD-MIB (Alcatel) |
| Nom | pimInvalidJoinPruneMsgsRcvd |
| Acces | readonly |
| Status | current |
| 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 pimGroupMappingPimMode. If there is no such
mapping, then the object pimGroupMappingPimMode is absent.
The RP address contained in the invalid Join/Prune is
pimInvalidJoinPruneRp.
Invalid Join/Prune messages are discarded. This may result
in loss of multicast data affecting listeners downstream of
pimInvalidJoinPruneOrigin, for multicast data addressed to
pimInvalidJoinPruneGroup.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, for example,
when the device is rebooted. |
| Syntaxe | Counter32 (SNMPv2-SMI) |
| Module | PIM-STD-MIB (Force10-9.14.2.1) |
| Nom | pimInvalidJoinPruneMsgsRcvd |
| Acces | readonly |
| Status | current |
| 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 pimGroupMappingPimMode. If there is no such
mapping, then the object pimGroupMappingPimMode is absent.
The RP address contained in the invalid Join/Prune is
pimInvalidJoinPruneRp.
Invalid Join/Prune messages are discarded. This may result
in loss of multicast data affecting listeners downstream of
pimInvalidJoinPruneOrigin, for multicast data addressed to
pimInvalidJoinPruneGroup.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, for example,
when the device is rebooted. |
| Syntaxe | Counter32 (SNMPv2-SMI) |
| Module | PIM-STD-MIB (FS) |
| Nom | pimInvalidJoinPruneMsgsRcvd |
| Acces | readonly |
| Status | current |
| 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 pimGroupMappingPimMode. If there is no such
mapping, then the object pimGroupMappingPimMode is absent.
The RP address contained in the invalid Join/Prune is
pimInvalidJoinPruneRp.
Invalid Join/Prune messages are discarded. This may result
in loss of multicast data affecting listeners downstream of
pimInvalidJoinPruneOrigin, for multicast data addressed to
pimInvalidJoinPruneGroup.
Discontinuities in the value of this counter can occur at
re-initialization of the management system, for example,
when the device is rebooted. |
| Syntaxe | Counter32 (SNMPv2-SMI) |