MLD_SNOOPING
sapMldSnpgGrpLimitExceeded
| Property name | Value | 
|---|---|
| Application name | MLD_SNOOPING | 
| Event ID | 2001 | 
| Event name | sapMldSnpgGrpLimitExceeded | 
| SNMP notification prefix and OID | TIMETRA-MLD-SNOOPING-MIB.tmnxMldSnpgSapNotifications.1 | 
| Default severity | warning | 
| Source stream | main | 
| Message format string | The number of groups on SAP $sapEncapValue$ in service $svcId$ has exceeded the maximum limit of $sapMldSnpgCfgMaxNbrGrps$ - Dropping group $tmnxMldSnpgGroupAddress$ | 
| Cause | A MLD group is dropped on a given SAP because a user configurable upper limit given by sapMldSnpgCfgMaxNbrGrps has been reached. | 
| Effect | N/A | 
| Recovery | N/A | 
sapMldSnpgMcsFailure
| Property name | Value | 
|---|---|
| Application name | MLD_SNOOPING | 
| Event ID | 2003 | 
| Event name | sapMldSnpgMcsFailure | 
| SNMP notification prefix and OID | TIMETRA-MLD-SNOOPING-MIB.tmnxMldSnpgSapNotifications.2 | 
| Default severity | warning | 
| Source stream | main | 
| Message format string | Group $tmnxMldSnpgGroupAddress$ on SAP $sapEncapValue$ in service $svcId$ could not be synced to MCS - $tmnxMldSnpgMcsFailureReason$ | 
| Cause | A MLD group on a given SAP could not be synced to the MCS (multi-chassis synchronization) database. | 
| Effect | N/A | 
| Recovery | N/A | 
sdpBndMldSnpgGrpLimitExceeded
| Property name | Value | 
|---|---|
| Application name | MLD_SNOOPING | 
| Event ID | 2002 | 
| Event name | sdpBndMldSnpgGrpLimitExceeded | 
| SNMP notification prefix and OID | TIMETRA-MLD-SNOOPING-MIB.tmnxMldSnpgSdpBndNotifications.1 | 
| Default severity | warning | 
| Source stream | main | 
| Message format string | The number of groups on SDP Bind $sdpBindId$ in service $svcId$ has exceeded the maximum limit of $sdpBndMldSnpgCfgMaxNbrGrps$ - Dropping group $tmnxMldSnpgGroupAddress$ | 
| Cause | A MLD group is dropped on a given SDP bind because a user configurable upper limit given by sdpBndMldSnpgCfgMaxNbrGrps is reached. | 
| Effect | N/A | 
| Recovery | N/A |