Routing

how does spoke work

thx in advacne

Maybe you save some problems with your devices. I've tested your config in my lab and I got the desired results:

 run show route receive-protocol bgp 1.1.1.1 

inet.0: 9 destinations, 9 routes (9 active, 0 holddown, 0 hidden)

inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)

VPN-A.inet.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
  Prefix		  Nexthop	       MED     Lclpref    AS path
* 0.0.0.0/0               1.1.1.1              0       100        I
* 192.168.16.0/24         1.1.1.1                      100        I

mpls.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)

bgp.l3vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
  Prefix		  Nexthop	       MED     Lclpref    AS path
  100:1:0.0.0.0/0                     
*                         1.1.1.1              0       100        I
  100:1:192.168.16.0/24                    
*                         1.1.1.1                      100        I

The bgp.l3vpn.0 table is missing on your r2 router. Maybe you should try a restart routing or reload.

Hi Rob,

It looks like BGP sessions with other PEs were down when you checked the routing table of r2.

Because, it doesn't show any routes recieved from remote PEs in the VPN-A.inet.0.

I couldn't find any issues in the config.

Regards,

Moses N

thx

Hi Rob,

1) with no-vrf-advertise , PE will not advertise any routes from that particular routing instance to other PEs.

this feature is helpful when you need spoke-to-spoke communication through the Hub CE. In that case, we need to configure two routing instances in the hub PE , one primary with no-vrf-advertise and other one as secondary. These two will exchange the routes between them and secondary will advertise the hub routes to other PEs.

you can find a similar example here 

http://netscreen.com/techpubs/software/junos/junos83/swconfig83-vpns/id-11137054.html

If we don't configure in this way, spoke to spoke communication will be through Hub PE. ( Not through Hub CE).

This is not preferable when you need any egress features required at Hub PE.

2) In Juniper Mpls VPN implementation , any routes learnt from a CE will be automatically advertised to other relevant PEs with the export communities. You don't need any policies. But on the other hands, routes learnt from remote PEs via MP-BGP will be advertised to local CEs, if local PE - CE protocol is bgp only. For other protocols , we need to have correct export policies.

regards,

Moses N

hi,Mose ,

now between pe and ce is ospf,so with vrf target ,junos will export all ospf learnt from ce to other PE automaticall,right?

Yes. That's correct.

haha,if between ce and pe is static route,I think it will not advertise,right?

No.

It doesn't matter,   If PE-CE is static, it will be advertised to other PEs.

Rgds

Moses N