|
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 |
Message format string |
Lost neighbor $tmnxPimSnpgIfNbrAddress$ on $ifName$ |
Cause |
The PIM adjacency with a neighbor was lost. |
Effect |
N/A |
|
Recovery |
N/A |
|
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 |
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 |
|
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 |
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 |
|
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 |
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 |