Hi, Answers inline marked [nr]
/neale From: <vpp-dev@lists.fd.io> on behalf of Gulakh <holoogul...@gmail.com> Date: Saturday, 28 July 2018 at 13:45 To: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io> Subject: [vpp-dev] L3VPN in VPP Hi, I have setup a VPLS scenario successfully and now I want to setup a L3VPN scenario in VPP (L3VPN topology is in attachment). My configuration for VPLS is some how like this link<https://lists.fd.io/g/vpp-dev/topic/vpls_dev_in_vpp_1/18091281?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,18091281>. As far as I searched Internet, L3VPN has a VPN Label that I think is somehow like PW Label in VPLS with difference that VPN Label is used to select VRF and PW Label is used to select mpls tunnel (hence bridge). [nr] other label allocation schemes are available ☺ =============================== Part1: I guess I should configure the source PE as follow: In VPLS: mpls tunnel add l2-only via <PE-TARGET> out-labels <PW-LABEL> ip route add <PE-TARGET> via <NEXT-HOP> out-labels <MPLS-LABEL> In L3VPN: CMD1 ??????????????? (insert in customer VRF) ip route add <PE-TARGET> via <NEXT-HOP> out-labels <MPLS-LABEL> (insert in GLOBAL VRF) I don't know what command I should use for CMD1 ... This command must add VPN-LABEL which is selected base on the customer's VRF to the packet and then lookup the GLOBAL VRF to push the MPLS Label. just like VPLS that the mpls tunnel first adds a PW Label and then in the destination IP resolution, MPLS Label is added to packet. Question1: Am I right about the configurations in the source PE? [nr] ip route table <CUSTOMER> <PREFIX> via <PE-TARGET> out-labels <CUSTOMER-VRF-LABEL> you could use PREFIX=0.0.0.0/0 or many more specifics and your route to the PE-TARGET would be better as a non-recursive route (i.e. if it is learned via e.g. OSPF and this is not an inter-AS option C) otherwise you’ll need another labelled route for the next-hop non-recursive means specify the next-hop and interface. ================================ Part2: I guess I should configure the target PE as follow: In VPLS: mpls local-label add eos <PW-LABEL> via l2-input-on <MPLS-TUNNEL> In L3VPN: mpls local-label add eos <VPN-LABEL> via ip4-lookup-in-table <VRF-ID> (insert in GLOBAL VRF) Question2: Am I right about the configurations in the target PE? [nr] Yes. The mpls label is added to the MPLS global table, i.e. there’s no ‘insert in global-VRF’, since the instruction associated with the label is to lookup the exposed IP destination address in the customer’s VRF/ ================================= Part3: In order to fill customer's VRF, I should use control plane's RouteTarget (RT) to select the VRF ID and then use below command to fill the VRF: ip route add <DESTIANTION> via <NEXT-HOP> <INTERFACE> table <VRF-ID> Question3: Am I right? [nr] yes. thanks in advance
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9970): https://lists.fd.io/g/vpp-dev/message/9970 Mute This Topic: https://lists.fd.io/mt/23840657/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
