Routing
Highlighted
Routing

bgp.l2vpn route not reflected to the client !?

‎05-24-2020 09:08 AM

Hello colleagues .  I have this configuration  on my Route Reflector : 

run show configuration protocols bgp group iBGP-RR 


type internal;
local-address 10.0.0.1;
family inet {
unicast;
}
family l2vpn {
signaling {
no-install;
}
}
export [ 24bit-filter iBGP-OUT ];
cluster 10.0.0.1;
peer-as 28761;
neighbor 10.0.0.4 {
}
neighbor 10.0.0.18 {
}

 

run show configuration policy-options policy-statement iBGP-OUT

 

term 1 {
from {
prefix-list AS-DEFAULT;
}
then {
next-hop self;
accept;
}
}
term 200 {
then reject;
}


run show bgp summary group iBGP-RR

Groups: 23 Peers: 77 Down peers: 5

Table Tot Paths Act Paths Suppressed History Damp State Pending

inet.0

4707006 813708 0 0 0 0

bgp.l2vpn.0

2 2 0 0 0 0

 

10.0.0.4 28761 526 616 0 4 4:22:41 Establ
inet.0: 0/0/0/0
bgp.l2vpn.0: 1/1/1/0

 

10.0.0.18 28761 524 615 0 5 4:21:56 Establ
inet.0: 0/0/0/0
bgp.l2vpn.0: 1/1/1/0

 

run show route table bgp.l2vpn.0

 

10.0.0.4:1947:2:1/96

                                    *[BGP/170] 01:23:50, localpref 100, from 10.0.0.4
                                    AS path: I, validation-state: unverified

                                    > to 10.0.2.254 via ae4.2255, Push 1366

10.0.0.18:1947:1:1/96
                                    *[BGP/170] 01:30:16, localpref 100, from 10.0.0.18
                                     AS path: I, validation-state: unverified
                                    > to 10.0.2.174 via ae0.102, Push 1192

 

 

run show bgp neighbor 10.0.0.4

 

Table bgp.l2vpn.0 Bit: 70000
RIB State: BGP restart is complete
RIB State: VPN restart is complete
Send state: in sync
Active prefixes: 1
Received prefixes: 1
Accepted prefixes: 1
Suppressed due to damping: 0
Advertised prefixes: 0

 

run show bgp neighbor 10.0.0.18

 

Table bgp.l2vpn.0 Bit: 70000
RIB State: BGP restart is complete
RIB State: VPN restart is complete
Send state: in sync
Active prefixes: 1
Received prefixes: 1
Accepted prefixes: 1
Suppressed due to damping: 0
Advertised prefixes: 0

 

Colleagues, tell me why  Advertised prefixes: 0  

 

2 REPLIES 2
Highlighted
Routing
Solution
Accepted by topic author AfroAmestigon
‎05-24-2020 11:37 PM

Re: bgp.l2vpn route not reflected to the client !?

[ Edited ]
‎05-24-2020 08:53 PM

Hello,

 

Unconditional "term 200 then reject" is blocking ALL and ANY other routes to be advertised to Your RR clients.

You need to further tighten the policy to match only on "family inet" and "rib inet.0" (if You want to send only "family inet" with NHS):

 

set policy-options policy-statement iBGP-OUT term 1 from rib inet.0
set policy-options policy-statement iBGP-OUT term 1 from family inet
set policy-options policy-statement iBGP-OUT term 1 from prefix-list AS-DEFAULT
set policy-options policy-statement iBGP-OUT term 1 then next-hop self
set policy-options policy-statement iBGP-OUT term 1 then accept set policy-options policy-statement iBGP-OUT term 200 from rib inet.0 set policy-options policy-statement iBGP-OUT term 200 from family inet set policy-options policy-statement iBGP-OUT term 200 then reject

 

Last but not least - if You ever introduce BGP-LU with rib inet.3 into Your network, then You'd  need to rework this policy again.

 

HTH

Thx

Alex 

_____________________________________________________________________

Please ask Your Juniper account team about Juniper Professional Services offerings.
Juniper PS can design, test & build the network/part of the network as per Your requirements

+++++++++++++++++++++++++++++++++++++++++++++

Accept as Solution = cool !
Accept as Solution+Kudo = You are a Star !
Highlighted
Routing

Re: bgp.l2vpn route not reflected to the client !?

‎05-24-2020 11:38 PM

All ingenious is simple  ! Many thanks ! 

Feedback