PIM

vRtrPimNgBierInbInvBfrId

Table 1. vRtrPimNgBierInbInvBfrId properties

Property name

Value

Application name

PIM

Event ID

2017

Event name

vRtrPimNgBierInbInvBfrId

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.17

Default severity

minor

Message format string

bier inband JP with ( $vRtrPimNgNotifyBierInbSAddr$, $vRtrPimNgNotifyBierInbGAddr$) from IBBR $vRtrPimNgNotifyBierInbIAddr$ is dropped due to bfr-id mismatch, received bfr id $vRtrPimNgNotifyBierInbInvBfrId$.

Cause

The vRtrPimNgBierInbInvSD is generated when PIM receives a JP PDU with unsupported BFR id.

Effect

PIM will stop processing the Join/Prune PDU.

Recovery

The operator must ensure that downstream routers must have the bfr-id within 1..4096 range.

vRtrPimNgBierInbInvSD

Table 2. vRtrPimNgBierInbInvSD properties

Property name

Value

Application name

PIM

Event ID

2016

Event name

vRtrPimNgBierInbInvSD

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.16

Default severity

minor

Message format string

bier inband JP with ( $vRtrPimNgNotifyBierInbSAddr$, $vRtrPimNgNotifyBierInbGAddr$) from IBBR $vRtrPimNgNotifyBierInbIAddr$ is dropped due to sub-domain mismatch, received sub domain id $vRtrPimNgNotifyBierInbInvSDId$.

Cause

The vRtrPimNgBierInbInvSD is generated when PIM receives a JP Pdu with unsupported sub-domain id.

Effect

PIM will stop processing the Join/Prune PDU.

Recovery

The operator must ensure that downstream routers must have the same sub-domain id.

vRtrPimNgBSRStateChange

Table 3. vRtrPimNgBSRStateChange properties

Property name

Value

Application name

PIM

Event ID

2006

Event name

vRtrPimNgBSRStateChange

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.6

Default severity

minor

Message format string

BSR state changed to $vRtrPimNgAFGenBSRState$

Cause

There was a change in the BSR state on the router. The managed object vRtrPimNgGenBSRState indicates the current BSR state.

Effect

N/A

Recovery

N/A

vRtrPimNgDataMtReused

Table 4. vRtrPimNgDataMtReused properties

Property name

Value

Application name

PIM

Event ID

2012

Event name

vRtrPimNgDataMtReused

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.12

Default severity

warning

Message format string

The selective provider tunnel with index $vRtrPimNgDataMtIfIndex$ configured for source address $vRtrPimNgDataMtMdSourceAddress$ and group address $vRtrPimNgDataMtMdGroupAddress$ has now $vRtrPimNgDataMtNumVpnSGs$ or more C(S,G)s after being reused by C(S,G) ( $DataMtCGrpSrcSourceAddr$,$DataMtCGrpSrcGroupAddr$)

Cause

A selective provider tunnel was reused, i.e. a C (S,G) was mapped to a selective provider tunnel that is already in use by another C (S,G).

Effect

N/A

Recovery

N/A

vRtrPimNgGrpInSSMRange

Table 5. vRtrPimNgGrpInSSMRange properties

Property name

Value

Application name

PIM

Event ID

2005

Event name

vRtrPimNgGrpInSSMRange

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.5

Default severity

warning

Message format string

Received $vRtrPimNgNotifyMsgType$ message on interface $vRtrIfIndex$ for group $vRtrPimNgNotifyGroupAddr$ which is in the SSM group range.

Cause

The router received a register message, a (*,G) assert message, a (*,G) Join Prune message or a IGMP local membership message for the group defined in the SSM address range.

Effect

N/A

Recovery

N/A

vRtrPimNgHelloDropped

Table 6. vRtrPimNgHelloDropped properties

Property name

Value

Application name

PIM

Event ID

2007

Event name

vRtrPimNgHelloDropped

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.7

Default severity

warning

Message format string

Hello from neighbor $vRtrPimNgIfNeighborAddress$ on interface $vRtrIfIndex$ dropped because the multicast sender attribute on this interface is set to 'always'

Cause

A hello was dropped because the multicast sender attribute on the interface is set to 'always'.

Effect

N/A

Recovery

N/A

vRtrPimNgIfMaxNbrReached

Table 7. vRtrPimNgIfMaxNbrReached properties

Property name

Value

Application name

PIM

Event ID

2021

Event name

vRtrPimNgIfMaxNbrReached

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.21

Default severity

minor

Message format string

Discarding hello on interface $vRtrIfIndex$ as maximum of $vRtrPimNgIfNbrCount$ pim interface neighbor limit is reached.

Cause

The vRtrPimNgIfMaxNbrReached is generated when the PIM interface has received more than 10K neighbors.

Effect

We restrict the number of neighbors to 10K in both per interface.

Recovery

The operated should be informed that the limit is higher than allowed.

vRtrPimNgIfNeighborLoss

Table 8. vRtrPimNgIfNeighborLoss properties

Property name

Value

Application name

PIM

Event ID

2001

Event name

vRtrPimNgIfNeighborLoss

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.1

Default severity

minor

Message format string

Lost adjacency with neighbor $vRtrPimNgIfNeighborAddress$ on interface $vRtrIfIndex$

Cause

The PIM adjacency with a neighbor was lost.

Effect

N/A

Recovery

N/A

vRtrPimNgIfNeighborUp

Table 9. vRtrPimNgIfNeighborUp properties

Property name

Value

Application name

PIM

Event ID

2002

Event name

vRtrPimNgIfNeighborUp

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.2

Default severity

minor

Message format string

Adjacency with neighbor $vRtrPimNgIfNeighborAddress$ on interface $vRtrIfIndex$ came up

Cause

A PIM adjacency with a new neighbor was established.

Effect

N/A

Recovery

N/A

vRtrPimNgInstMaxNbrReached

Table 10. vRtrPimNgInstMaxNbrReached properties

Property name

Value

Application name

PIM

Event ID

2020

Event name

vRtrPimNgInstMaxNbrReached

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.20

Default severity

minor

Message format string

Discarding Hello, maximum of $vRtrPimNgInstNbrCount$ system pim neighbors reached.

Cause

The vRtrPimNgInstMaxNbrReached is generated when PIM instance has received more than 10K neighbors.

Effect

We restrict the number of neighbors to 10K per instance.

Recovery

The operator should be informed that that the limit is higher than allowed.

vRtrPimNgInvalidIPmsiTunnel

Table 11. vRtrPimNgInvalidIPmsiTunnel properties

Property name

Value

Application name

PIM

Event ID

2014

Event name

vRtrPimNgInvalidIPmsiTunnel

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.14

Default severity

warning

Message format string

Received intra-as a/d route with invalid i-pmsi tunnel group address $vRtrPimNgWrongMdtDefGrpAddr$ from $vRtrPimNgNotifySourceIp$, expected $vRtrPimNgAFGenMdtDefGrpAddress$

Cause

The vRtrPimNgInvalidIPmsiTunnel event is generated when an invalid default core group address specified by vRtrPimNgWrongMdtDefGrpAddr of the Multicast Distribution Tree(MDT) is received in PIM message from vRtrPimNgNotifySourceIp, instead of the expected address specified by vRtrPimNgAFGenMdtDefGrpAddress. It is considered to be a misconfiguration and the message will be dropped. This trap is intended to help network operators recognize the misconfiguration and adjust their configurations accordingly. This event is also generated when the tunnel type specified by vRtrPimNgWrongPmsiType is received in PIM message from vRtrPimNgNotifySourceIp which is different from the configured tunnel type.

Effect

The PMSI received in the PIM message from vRtrPimNgNotifySourceIp is not processed by PIM.

Recovery

Operator needs to look and adjust the configuration of vRtrPimNgNotifySourceIp in the VPRN specified by vRtrPimNgWrongVprnId. The objects vRtrPimNgWrongPmsiP2mpId, vRtrPimNgWrongPmsiTunnelId and vRtrPimNgWrongPmsiExtTunlAddr in the event vRtrPimNgInvalidIPmsiTunnel are valid only when vRtrPimNgWrongPmsiType is 'rsvp (2)'. The objects vRtrPimNgWrongMdtDefGrpAddrType and vRtrPimNgWrongMdtDefGrpAddr in the event vRtrPimNgInvalidIPmsiTunnel are valid only when vRtrPimNgWrongPmsiType is either 'pimSsm (0)' or 'pimSm (1)'. The objects vRtrPimNgWrongPmsiLdpLspId, vRtrPimNgWrongPmsiSenderAdrTyp and vRtrPimNgWrongPmsiSenderAddr in the event vRtrPimNgInvalidIPmsiTunnel are valid only when vRtrPimNgWrongPmsiType is 'ldp (3)'.

vRtrPimNgInvalidJoinPrune

Table 12. vRtrPimNgInvalidJoinPrune properties

Property name

Value

Application name

PIM

Event ID

2003

Event name

vRtrPimNgInvalidJoinPrune

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.3

Default severity

warning

Message format string

Received invalid Join Prune message from $vRtrPimNgNotifySourceIp$ with RP address $vRtrPimNgNotifyWrongRPAddr$ for group $vRtrPimNgNotifyGroupAddr$. Correct RP address for the group is $vRtrPimNgNotifyRPAddr$(0.0.0.0 if unknown)

Cause

An invalid Join Prune message was received. A Join Prune message is deemed invalid when there is an RP address disagreement between the router and the PIM Join Prune message.

Effect

N/A

Recovery

N/A

vRtrPimNgInvalidRegister

Table 13. vRtrPimNgInvalidRegister properties

Property name

Value

Application name

PIM

Event ID

2004

Event name

vRtrPimNgInvalidRegister

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.4

Default severity

warning

Message format string

Received invalid Register message from $vRtrPimNgNotifySourceIp$ with RP address $vRtrPimNgNotifyWrongRPAddr$ for group $vRtrPimNgNotifyGroupAddr$. Correct RP address for the group is $vRtrPimNgNotifyRPAddr$(0.0.0.0 if unknown)

Cause

An invalid PIM Register message was received. A Register message is deemed invalid when there is an RP address disagreement between the router and the PIM Register message.

Effect

N/A

Recovery

N/A

vRtrPimNgMaxGraftRetry

Table 14. vRtrPimNgMaxGraftRetry properties

Property name

Value

Application name

PIM

Event ID

2015

Event name

vRtrPimNgMaxGraftRetry

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.15

Default severity

minor

Message format string

Exceeded $vRtrPimNgNumGraftRetriesExcd$ retries for source address $vRtrPimNgNotifySourceAddr$, group address $vRtrPimNgNotifyGroupAddr$ and will stop trying.

Cause

The vRtrPimNgMaxGraftRetry is generated when the number of graft retries has exceeded 10.

Effect

We will stop retrying sending of graft messages and remain in ack-pending state.

Recovery

The recovery is caused by a subsequent graft ack or data which will move the state to forwarding.

vRtrPimNgMaxGrpsLimitExceeded

Table 15. vRtrPimNgMaxGrpsLimitExceeded properties

Property name

Value

Application name

PIM

Event ID

2011

Event name

vRtrPimNgMaxGrpsLimitExceeded

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.11

Default severity

warning

Message format string

The number of groups configured on the interface $ifName$ has exceeded the maximum limit of $vRtrPimNgIfMaxGroups$

Cause

An attempt was made to configure a group when the number of groups configured on the interface has exceeded the maximum limit.

Effect

N/A

Recovery

N/A

vRtrPimNgMcacPlcyDropped

Table 16. vRtrPimNgMcacPlcyDropped properties

Property name

Value

Application name

PIM

Event ID

2013

Event name

vRtrPimNgMcacPlcyDropped

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.13

Default severity

warning

Message format string

Group $vRtrPimNgNotifyGroupAddr$ is dropped because of multicast CAC policy $vRtrPimNgIfMcacPolicyName$ on interface $ifName$ PIM instance $vRtrID$

Cause

A PIM group was dropped on a given interface because of applying a multicast CAC policy.

Effect

N/A

Recovery

N/A

vRtrPimNgMDTLimitExceeded

Table 17. vRtrPimNgMDTLimitExceeded properties

Property name

Value

Application name

PIM

Event ID

2010

Event name

vRtrPimNgMDTLimitExceeded

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.10

Default severity

warning

Message format string

The selective provider tunnel configuration failed for PIM instance $vRtrID$, maximum selective provider tunnel limit of $vRtrPimNgGenMaxMdts$ exceeded

Cause

The configuration exceeded the maximum number of selective provider tunnels supported on the system.

Effect

N/A

Recovery

N/A

vRtrPimNgReplicationLmtExceeded

Table 18. vRtrPimNgReplicationLmtExceeded properties

Property name

Value

Application name

PIM

Event ID

2009

Event name

vRtrPimNgReplicationLmtExceeded

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.9

Default severity

warning

Message format string

Maximum number of replications reached for (S,G), ( $vRtrPimNgNotifySourceIp$, $vRtrPimNgNotifyGroupAddr$) on IOM $tmnxCardHwIndex$, failed to program OIF record

Cause

An IOM failed to program an OIF for an (S,G) record because the replication limit for that (S,G) on that IOM has been reached. The replication limit per (S,G) entry on an IOM is currently 127.

Effect

N/A

Recovery

N/A

vRtrPimNgSGLimitExceeded

Table 19. vRtrPimNgSGLimitExceeded properties

Property name

Value

Application name

PIM

Event ID

2008

Event name

vRtrPimNgSGLimitExceeded

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.8

Default severity

warning

Message format string

Maximum number of multicast (S,G) records reached on IOM $tmnxCardHwIndex$, failed to program OIF record

Cause

A (S,G) record failed to be programmed to an IOM because the supported (S,G) limit was exceeded. This limit is currently at 16000 (S,G) entries.

Effect

N/A

Recovery

N/A

vRtrPimNgUmhBMonFastFailPriToStb

Table 20. vRtrPimNgUmhBMonFastFailPriToStb properties

Property name

Value

Application name

PIM

Event ID

2018

Event name

vRtrPimNgUmhBMonFastFailPriToStb

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.18

Default severity

minor

Message format string

UMH bandwidth monitor based tunnel switch has happened at $vRtrPimNgUmhBMonTimeStamp$ from the primary interface mpls-if-$vRtrPimNgUmhBMonPrimaryIfIndex$ to the standby interface mpls-if- $vRtrPimNgUmhBMonStandbyIfIndex$ when primary rate was $vRtrPimNgUmhBMonPrimaryBW$ and standby rate was $vRtrPimNgUmhBMonStandbyBW$.

Cause

The vRtrPimNgUmhBMonFastFailPriToStb is generated when there is a traffic switch in data-path.

Effect

Data-packets switches to the active path from primary to standby due to bandwidth delta.

Recovery

Recovery is based on revertive timer and traffic should switch back to primary tunnel automatically when the traffic recovers, else it remains on the standby tunnel.

vRtrPimNgUmhBMonFastFailStbToPri

Table 21. vRtrPimNgUmhBMonFastFailStbToPri properties

Property name

Value

Application name

PIM

Event ID

2019

Event name

vRtrPimNgUmhBMonFastFailStbToPri

SNMP notification prefix and OID

TIMETRA-PIM-NG-MIB.vRtrPimNgNotifications.19

Default severity

minor

Message format string

UMH bandwidth monitor based tunnel switch has happened at $vRtrPimNgUmhBMonTimeStamp$ from the standby interface mpls-if-$vRtrPimNgUmhBMonStandbyIfIndex$ to the primary interface mpls-if- $vRtrPimNgUmhBMonPrimaryIfIndex$ when primary rate was $vRtrPimNgUmhBMonPrimaryBW$ and standby rate was $vRtrPimNgUmhBMonStandbyBW$.

Cause

The vRtrPimNgUmhBMonFastFailStbToPri is generated when there is a traffic switch in data-path.

Effect

Data-packets switches to the active path from standby to primary due to bandwidth delta.

Recovery

Recovery is based on revertive timer and traffic should switch back to primary tunnel automatically when the traffic recovers, else it remains on the standby tunnel.