Hi Xxyue, Can you please be more specific about what is working and was is not. Does the ping we were debugging previously now work? What is this ‘bi-directional flow’ you speak of, if it is not the ping.
Those asserts could be related to: https://gerrit.fd.io/r/#/c/6883/ I saw them, whilst debugging the original problem. I you sure you patched and recompiled the DEBUG version of VPP on both ‘PE’s’? Thanks, neale From: 薛欣颖 <xy...@fiberhome.com> Date: Saturday, 27 May 2017 at 06:33 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 result :flow is ok. But when have bi-directional flow ,the assertion will appear: That is the assertion: DBGvpp# 0: /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 192.168.2.20 ------192.168.3.20 VPP2----VPP1 The trace is shown below: VPP1 Packet 4 01:06:37:616042: af-packet-input af_packet: hw_if_index 2 next-index 4 tpacket2_hdr: status 0x1 len 132 snaplen 132 mac 66 net 80 sec 0xff9 nsec 0x34b682dc vlan 0 01:06:37:616604: ethernet-input MPLS: 0e:1a:0d:00:50:43 -> 00:03:7f:ff:ff:fe 01:06:37:616765: mpls-input MPLS: next mpls-lookup[1] label 1024 ttl 255 01:06:37:616898: mpls-lookup MPLS: next [8], lookup fib index 0, LB index 34 hash 0 label 1024 eos 0 01:06:37:617032: lookup-mpls-dst fib-index:0 hdr:[1023:254:0:eos] load-balance:33 01:06:37:617097: ip4-mpls-label-disposition disp:0 01:06:37:617139: lookup-ip4-dst fib-index:1 addr:192.168.3.20 load-balance:35 01:06:37:617255: ip4-rewrite tx_sw_if_index 1 dpo-idx 6 : ipv4 via 192.168.3.20 host-eth0: 00109400000400037fffffff0800 flow hash: 0x00000000 00000000: 00109400000400037fffffff080045c0006e8e070000fdfda752c0a80214c0a8 00000020: 03140000000000000000000000000000000000000000000000000000 01:06:37:617323: host-eth0-output host-eth0 IP4: 00:03:7f:ff:ff:ff -> 00:10:94:00:00:04 unknown 253: 192.168.2.20 -> 192.168.3.20 tos 0xc0, ttl 253, length 110, checksum 0xa752 fragment id 0x8e07 VPP2 Packet 3 01:02:34:895149: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x5 len 124 snaplen 124 mac 66 net 80 sec 0x1054 nsec 0x11097ff5 vlan 0 01:02:34:895471: ethernet-input IP4: 00:10:94:00:00:03 -> 00:50:43:00:02:02 01:02:34:895533: ip4-input unknown 253: 192.168.2.20 -> 192.168.3.20 tos 0xc0, ttl 255, length 110, checksum 0xa169 fragment id 0x91f0 01:02:34:895586: ip4-lookup fib 1 dpo-idx 3 flow hash: 0x00000000 unknown 253: 192.168.2.20 -> 192.168.3.20 tos 0xc0, ttl 255, length 110, checksum 0xa169 fragment id 0x91f0 01:02:34:895643: ip4-mpls-label-imposition mpls-header:[1023:254:0:eos] 01:02:34:895695: mpls-midchain adj-idx 7 : mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@3]: dpo-load-balance: [proto:mpls index:33 buckets:1 uRPF:-1 to:[0:0] via:[37340:4266490]] [0] [@8]: mpls-label:[0]:[1024:255:0:neos] [@2]: mpls via 2.1.1.1 host-eth1: 00037ffffffe0e1a0d0050438847 flow hash: 0x00000000 01:02:34:895726: adj-midchain-tx adj-midchain:[7]:mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@3]: dpo-load-balance: [proto:mpls index:33 buckets:1 uRPF:-1 to:[0:0] via:[37340:4266490]] [0] [@8]: mpls-label:[0]:[1024:255:0:neos] [@2]: mpls via 2.1.1.1 host-eth1: 00037ffffffe0e1a0d0050438847 01:02:34:895767: mpls-label-imposition mpls-header:[1024:255:0:neos] 01:02:34:895814: mpls-output adj-idx 6 : mpls via 2.1.1.1 host-eth1: 00037ffffffe0e1a0d0050438847 flow hash: 0x00000000 00000000: 0000000000000000000000000000000000000000000000000000000000000000 00000020: 00000000000000000000000000000000000000000000000000000000 01:02:34:895851: host-eth1-output host-eth1 MPLS: 0e:1a:0d:00:50:43 -> 00:03:7f:ff:ff:fe label 1024 exp 0, s 0, ttl 255 Thanks, xyxue
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
