BIER
vRtrBierBfrIdCollision
Property name | Value |
---|---|
Application name |
BIER |
Event ID | 2001 |
Event name | vRtrBierBfrIdCollision |
SNMP notification prefix and OID |
TIMETRA-BIER-MIB.vRtrBierNotifications.1 |
Default severity |
minor |
Source stream | main |
Message format string | Same BFR id $vRtrBierNotifyBfrId$ received from $vRtrBierPrefix1Address$ and $vRtrBierPrefix2Address$ by the sub-domain $vRtrBierNotifySubDomainId$ with BSL $vRtrBierNotifyBsl$ |
Cause | The vRtrBierBfrIdCollision is generated when BFR ID received from two different routes is the same. |
Effect | We will remove the duplicate BFR Id from neighbors f-BM (forwarding Bit Mask). |
Recovery | An operator intervention is needed to remove the duplicate BFR ID from the configuration. |
vRtrBierMtMismatch
Property name | Value |
---|---|
Application name |
BIER |
Event ID | 2002 |
Event name | vRtrBierMtMismatch |
SNMP notification prefix and OID |
TIMETRA-BIER-MIB.vRtrBierNotifications.2 |
Default severity |
minor |
Source stream | main |
Message format string | Multi-topology value $vRtrBierNotifyRecvMTId$ received by the sub-domain $vRtrBierNotifySubDomainId$ with BSL $vRtrBierNotifyBsl$ and multi-topology $vRtrBierNotifyMTId$ |
Cause | The vRtrBierMtMismatch is generated when the multi- topology sent by the peer is different from what is configured locally. |
Effect | We will ignore the advertisement. |
Recovery |
N/A |
vRtrBierSubDomainMismatch
Property name | Value |
---|---|
Application name | BIER |
Event ID |
2003 |
Event name | vRtrBierSubDomainMismatch |
SNMP notification prefix and OID | TIMETRA-BIER-MIB.vRtrBierNotifications.3 |
Default severity | minor |
Source stream |
main |
Message format string | Sub-domain value $vRtrBierNotifyRecvSubDomainId$ received by the sub-domain $vRtrBierNotifySubDomainId$ with BSL $vRtrBierNotifyBsl$ |
Cause |
The vRtrBierSubDomainMismatch is generated when the sub-domain in the received route is not configured locally. |
Effect | We will ignore the sub TLV. |
Recovery |
Operator may need to configure the mismatched sub-domains. |
vRtrBierUnsupportedNhop
Property name | Value |
---|---|
Application name |
BIER |
Event ID | 2004 |
Event name | vRtrBierUnsupportedNhop |
SNMP notification prefix and OID |
TIMETRA-BIER-MIB.vRtrBierNotifications.4 |
Default severity |
minor |
Source stream | main |
Message format string | Next-hop type $vRtrBierNextHopeType$ is not supported for the given prefix $vRtrBierPrefix1Address$, next-hop address $vRtrBierNextHopAddress$ and outgoing interface $vRtrIfIndex$ |
Cause | The vRtrBierUnsupportedNhop is generated when the next hop indicated by vRtrBierNextHopAddress is unsupported by the system. |
Effect | We will ignore it while calculating the next hop. |
Recovery | The recovery is caused on receiving the subsequent correct next hop and clearing this trap by setting vRtrBierUnsupportedNhopState to 'false'. |