yes and no, the command makes FPC1 to install all the VRF routes and next-hops, so is not only the MPLS routes, you will have also any other routes that are local to the VRF, but Deepak bear in mind that your VRF also needs to be configured as VPN localized.
Being completely honest, I have never seen this in practice, it is a nice feature, but requires a lot of planning, my suggestion for you is to try to test it in the lab, most linecards in MX routers are capable of store an incredible number of routes, and there are ways to reduce the number of indexes in memory (composite NH, forwarding table policies, etc), my advise is to stay away from this.
------------------------------
GABRIEL FLORES
------------------------------
Original Message:
Sent: 09-20-2021 02:40
From: Unknown User
Subject: Question on VRF Localization
Hi all.
Consider the L3VPN topology below, where PE1's core-facing FPC is FPC1
ge-0/0/0 ge-1/0/0
CE1 ------------PE1--------------- PE2 -----------CE2
I have configured the following on PE1's FPC1:
set chassis fpc 1 vpn-localization vpn-core-facing-default
Does this mean that no FPC other than FPC1 will have the MPLS route required to forward traffic from remote CE2 to local CE1?
If not, what is the purpose of the vpn-core-facing-default knob?
Thanks,
Deepak
Juniper Business Use Only