PIM_SNOOPING
tmnxPimSnpgIfMaxNbrReached
Property name  | Value  | 
|---|---|
Application name  | PIM_SNOOPING  | 
Event ID  | 
2005  | 
Event name  | tmnxPimSnpgIfMaxNbrReached  | 
SNMP notification prefix and OID  | TIMETRA-PIM-SNOOPING-MIB.tmnxPimSnpgNotifications.5  | 
Default severity  | minor  | 
Source stream  | 
main  | 
Message format string  | Discarding hello on pim service $SvcId$ with SAP $sapId$ as maximum of $tmnxPimSnpgIntfNbrCount$ pim-snooping neighbor limit is reached.  | 
Cause  | The tmnxPimSnpgIfMaxNbrReached is generated when PIM snooping interface has received more than 10K neighbors.  | 
Effect  | We restrict the number of neighbors to 10K per interface.  | 
Recovery  | The operator should be informed that the limit is higher than allowed.  | 
tmnxPimSnpgIfNeighborLoss
Property name  | Value  | 
|---|---|
Application name  | 
PIM_SNOOPING  | 
Event ID  | 2001  | 
Event name  | tmnxPimSnpgIfNeighborLoss  | 
SNMP notification prefix and OID  | 
TIMETRA-PIM-SNOOPING-MIB.tmnxPimSnpgNotifications.1  | 
Default severity  | 
minor  | 
Source stream  | main  | 
| 
 Message format string  | Lost neighbor $tmnxPimSnpgIfNbrAddress$ on $ifName$  | 
Cause  | The PIM adjacency with a neighbor was lost.  | 
| 
 Effect  | N/A  | 
Recovery  | N/A  | 
tmnxPimSnpgIfNeighborUp
Property name  | Value  | 
|---|---|
Application name  | 
PIM_SNOOPING  | 
Event ID  | 2002  | 
Event name  | tmnxPimSnpgIfNeighborUp  | 
SNMP notification prefix and OID  | 
TIMETRA-PIM-SNOOPING-MIB.tmnxPimSnpgNotifications.2  | 
Default severity  | 
minor  | 
Source stream  | main  | 
| 
 Message format string  | Snooped new neighbor $tmnxPimSnpgIfNbrAddress$ on $ifName$  | 
Cause  | The PIM adjacency with a new neighbor was established.  | 
Effect  | N/A  | 
Recovery  | N/A  | 
tmnxPimSnpgMaxNbrReached
Property name  | Value  | 
|---|---|
Application name  | 
PIM_SNOOPING  | 
Event ID  | 2006  | 
Event name  | tmnxPimSnpgMaxNbrReached  | 
SNMP notification prefix and OID  | 
TIMETRA-PIM-SNOOPING-MIB.tmnxPimSnpgNotifications.6  | 
Default severity  | 
minor  | 
Source stream  | main  | 
| 
 Message format string  | Discarding hello on pim service $SvcId$ as maximum of $tmnxPimSnpgNbrCount$ pim-snooping neighbor limit is reached.  | 
Cause  | The tmnxPimSnpgMaxNbrReached is generated when PIM snooping 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 the limit is higher than allowed.  | 
tmnxPimSnpgSGLimitExceeded
Property name  | Value  | 
|---|---|
Application name  | 
PIM_SNOOPING  | 
Event ID  | 2003  | 
Event name  | tmnxPimSnpgSGLimitExceeded  | 
SNMP notification prefix and OID  | 
TIMETRA-PIM-SNOOPING-MIB.tmnxPimSnpgNotifications.3  | 
Default severity  | 
warning  | 
Source stream  | main  | 
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  | 
tmnxPimSnpgSnoopModeChanged
Property name  | Value  | 
|---|---|
Application name  | 
PIM_SNOOPING  | 
Event ID  | 2004  | 
Event name  | tmnxPimSnpgSnoopModeChanged  | 
SNMP notification prefix and OID  | 
TIMETRA-PIM-SNOOPING-MIB.tmnxPimSnpgNotifications.4  | 
Default severity  | 
warning  | 
Source stream  | main  | 
Message format string  | PIM-Snooping Operational Mode changed to $tmnxPimSnpgGenOperState$. Configured mode is $tmnxPimSnpgGenMode$  | 
Cause  | A snooping mode was changed from proxy to snoop or vice versa.  | 
Effect  | N/A  | 
Recovery  | N/A  |