Hi Xyxue, You said there are two scenarios; with MPLS (broken), without MPLS (working). Which scenario is this config for? And can I see the other one too please.
Thanks, neale From: 薛欣颖 <xy...@fiberhome.com> Date: Wednesday, 31 May 2017 at 08:10 To: "Neale Ranns (nranns)" <nra...@cisco.com>, vpp-dev <vpp-dev@lists.fd.io> Subject: Re: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Neale, The configuration is shown below: ######## ######## ######## ######## ####PE1 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface ip table host-eth1 0 set interface ip table host-eth0 1 set interface mac address host-eth0 00:03:7F:FF:FF:FF set interface mac address host-eth1 00:03:7F:FF:FF:FE set int ip address host-eth0 192.168.3.1/24 set int ip address host-eth1 2.1.1.1/24 set interface mpls host-eth1 enable set interface mpls host-eth0 enable mpls tunnel add via 2.1.1.2 host-eth1 out-label 34 set int state mpls-tunnel0 up ip route add 192.168.2.0/24 table 1 via mpls-tunnel0 out-label 33 mpls local-label add eos 1023 ip4-lookup-in-table 1 mpls local-label add non-eos 1024 mpls-lookup-in-table 0 ######## ######## ######## ######## ####PE2 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up set interface ip table host-eth0 1 set interface ip table host-eth1 0 set interface mac address host-eth0 00:50:43:00:02:02 set interface mac address host-eth1 0E:1A:0D:00:50:43 set int ip address host-eth0 192.168.2.1/24 set int ip address host-eth1 2.1.1.2/24 set interface mpls host-eth1 enable set interface mpls host-eth0 enable mpls local-label add eos 33 ip4-lookup-in-table 1 mpls local-label add non-eos 34 mpls-lookup-in-table 0 mpls tunnel add via 2.1.1.1 host-eth1 out-label 1024 set int state mpls-tunnel0 up ip route add 192.168.3.0/24 table 1 via mpls-tunnel0 out-label 1023 Thanks, xyxue ________________________________ From: Neale Ranns (nranns)<mailto:nra...@cisco.com> Date: 2017-05-31 15:02 To: 薛欣颖<mailto:xy...@fiberhome.com>; vpp-dev<mailto:vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, Can you please give me the full configs in each case. Thanks, neale From: 薛欣颖 <xy...@fiberhome.com> Date: Wednesday, 31 May 2017 at 06:56 To: "Neale Ranns (nranns)" <nra...@cisco.com>, vpp-dev <vpp-dev@lists.fd.io> Subject: Re: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi neale, Sorry for not replying to your email in time. 192.168.2.20 ------192.168.3.20 VPP2----VPP1 A brief description of the problem: When vpp without MPLS the ping packet from CE to CE is ok. When vpp configured MPLS the ping packet from CE to CE is failed ,the assertion occured at the meantime.The assertion is shown below： /home/vpp/build-data/../src/vnet/ip/ip4_forward.c:2635 (ip4_rewrite_inline) assertion `ip0->checksum == ip4_header_checksum (ip0)' fails Aborted /home/vpp/build-data/../src/vnet/ip/ip4_forward.c:2497 (ip4_rewrite_inline) assertion `ip1->checksum == ip4_header_checksum (ip1)' fails Aborted Thanks, xyxue ________________________________ From: Neale Ranns (nranns)<mailto:nra...@cisco.com> Date: 2017-05-27 18:25 To: 薛欣颖<mailto:xy...@fiberhome.com>; vpp-dev<mailto:vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, One issue at a time please ☺ let’s start with getting L3VPN to work correctly. Please describe what the 3 flows are that we you discussing; - Fade flow - Ip4 flow - Mpls flow Describe, as in what headers they have, addressing etc. The IP chksum will change from CE->CE since the IP TTL decrements. /neale
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
