Hi Aman, The label is assigned manually as an example. I have not tried automated label assignment. These are the routes that you advertise to the PE. Thanks, Ashvin From: SHAIKH, AMAN (AMAN) [mailto:ashaikh@research.att.com] Sent: Thursday, March 01, 2018 9:06 PM To: Ashvin Lakshmikantha <ashvin.lakshmikantha@ericsson.com>; frog@lists.frrouting.org Subject: RE: How to configure RFC 4364 (BGP/MPLS) VPNs with FRR/bgpd Hi Ashvin Thanks for the instructions. Have a few questions; see inline. From: Ashvin Lakshmikantha [mailto:ashvin.lakshmikantha@ericsson.com] Sent: Wednesday, February 28, 2018 10:45 PM To: SHAIKH, AMAN (AMAN) <ashaikh@research.att.com<mailto:ashaikh@research.att.com>>; frog@lists.frrouting.org<mailto:frog@lists.frrouting.org> Subject: RE: How to configure RFC 4364 (BGP/MPLS) VPNs with FRR/bgpd HI Aman, Actually the configuration is a two step process. First, we need to create a vrf-policy under router bgp like so vrf-policy cust0 label 1357 ? Shouldn't label be assigned automatically by the zebra label manager? nexthop 15.44.4.165 ? Does this next-hop apply to routes going out to CE? Or routes going to the core (other PEs and/or route-reflector)? Or both? rd 437:612 rt import 452:424 rt export 516:943 exit-vrf-policy ! vrf-policy cust1 label 1730 nexthop 171.40.184.82 rd 66:33 rt import 906:551 rt export 890:543 exit-vrf-policy ! vrf-policy cust2 label 32639 nexthop 189.2.178.92 rd 14:619 rt import 904:272 rt export 233:507 exit-vrf-policy Then you need to exit the router bgp configuration and add routes to a particular vrf using add command add vrf cust0 10.30.40.89 ? What does 10.30.40.89 represent here? thx aman