Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Xyxue,
L3VPN should work directly from master branch. So yes, clone from
https://gerrit.fd.io/r/vpp.
In my opinion, the best way to try out a gerrit patch is to:
git review –d
for example to get the L2VPN code it’s;
git review –d 6861
this will create a new branch it your git repro. Saves you managing various
patch files.
Regards,
neale
From: 薛欣颖 <xy...@fiberhome.com>
Date: Friday, 2 June 2017 at 07:20
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,
These patches you upload have something conflict with the master branch.I
can't add all the patches.
Can I use' git clone https://gerrit.fd.io/r/vpp 'to get the vpp code with your
pathes?
Thanks,
xyxue
From: Neale Ranns (nranns)<mailto:nra...@cisco.com>
Date: 2017-05-31 18:09
To: 薛欣颖<mailto:xy...@fiberhome.com>; vpp-dev<mailto:vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Xyxue,
The MPLS config works for me with:
DBGvpp# sh version
vpp v17.07-rc0~314-g79ea7ec built by vagrant on localhost at Wed May 31
00:46:42 PDT 2017
which is master branch from a few hours ago.
Regards,
neale
Packet 1
00:09:02:603978: af-packet-input
af_packet: hw_if_index 1 next-index 4
tpacket2_hdr:
status 0x2001 len 98 snaplen 98 mac 66 net 80
sec 0x592e95b3 nsec 0x8466a6e vlan 0 vlan_tpid 0
00:09:02:604038: ethernet-input
IP4: 3a:4c:48:ed:59:c3 -> 02:fe:1a:e1:c5:4c
00:09:02:604054: ip4-input
ICMP: 192.168.2.20 -> 192.168.3.20
tos 0x00, ttl 64, length 84, checksum 0x26b8
fragment id 0x8d78, flags DONT_FRAGMENT
ICMP echo_request checksum 0x1c3e
00:09:02:604062: ip4-lookup
fib 1 dpo-idx 3 flow hash: 0x
ICMP: 192.168.2.20 -> 192.168.3.20
tos 0x00, ttl 64, length 84, checksum 0x26b8
fragment id 0x8d78, flags DONT_FRAGMENT
ICMP echo_request checksum 0x1c3e
00:09:02:604072: ip4-mpls-label-imposition
mpls-header:[33:63:0:eos]
00:09:02:604081: mpls-midchain
adj-idx 5 : mpls via 0.0.0.0 mpls-tunnel0:
stacked-on:
[@5]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0]
via:[43:3784]]
[0] [@6]: mpls-label:[1]:[34:255:0:neos]
[@1]: mpls via 2.1.1.2 host-vcore-link-1:
02feb30a3b6f02fe4eafc6638847 flow hash: 0x
00:09:02:604088: adj-midchain-tx
adj-midchain:[5]:mpls via 0.0.0.0 mpls-tunnel0:
stacked-on:
[@5]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0]
via:[43:3784]]
[0] [@6]: mpls-label:[1]:[34:255:0:neos]
[@1]: mpls via 2.1.1.2 host-vcore-link-1: 02feb30a3b6f02fe4eafc6638847
00:09:02:604096: mpls-label-imposition
mpls-header:[34:255:0:neos]
00:09:02:604100: mpls-output
adj-idx 4 : mpls via 2.1.1.2 host-vcore-link-1: 02feb30a3b6f02fe4eafc6638847
flow hash: 0x
:
0020:
00:09:02:604102: host-vcore-link-1-output
host-vcore-link-1
MPLS: 02:fe:4e:af:c6:63 -> 02:fe:b3:0a:3b:6f
label 34 exp 0, s 0, ttl 255
Packet 2
00:09:02:604968: af-packet-input
af_packet: hw_if_index 2 next-index 4
tpacket2_hdr:
status 0x2001 len 106 snaplen 106 mac 66 net 80
sec 0x592e95b3 nsec 0x84c97da vlan 0 vlan_tpid 0
00:09:02:604978: ethernet-input
MPLS: 02:fe:b3:0a:3b:6f -> 02:fe:4e:af:c6:63
00:09:02:604987: mpls-input
MPLS: next mpls-lookup[1] label 1024 ttl 255
00:09:02:604993: mpls-lookup
MPLS: next [8], lookup fib index 0, LB index 34 hash 0 label 1024 eos 0
00:09:02:605000: lookup-mpls-dst
fib-index:0 hdr:[1023:63:0:eos] load-balance:33
00:09:02:605005: ip4-mpls-label-disposition
disp:0
00:09:02:605008: lookup-ip4-dst
fib-index:1 addr:192.168.2.20 load-balance:35
00:09:02:605014: ip4-rewrite
tx_sw_if_index 1 dpo-idx 6 : ipv4 via 192.168.2.20 host-vce-link-1:
3a4c48ed59c302fe1ae1c54c0800 flow hash: 0x
: 3a4c48ed59c302fe1ae1c54c08004554e9fd3e010c33c0a80314c0a8
0020: 0214243e07d20010b3952e59311e02001011
00:09:02:605018: host-vce-link-1-output
host-vce-link-1
IP4: 02:fe:1a:e1:c5:4c -> 3a:4c:48:ed:59:c3
ICMP: 192.168.3.20 -> 192.168.2.20
tos 0x00, ttl 62, length 84, checksum 0x0c33
fragment id 0xe9fd
ICMP echo_reply checksum 0x243e
From: 薛欣颖 <xy...@fiberhome.com>
Date: Wednesday, 31 May 2017 at 08:40
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 without MPLS:
###VPP1
create host-interface name eth0
create host-interface name eth1
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-
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Neale,
These patches you upload have something conflict with the master branch.I
can't add all the patches.
Can I use' git clone https://gerrit.fd.io/r/vpp 'to get the vpp code with your
pathes?
Thanks,
xyxue
From: Neale Ranns (nranns)
Date: 2017-05-31 18:09
To: 薛欣颖; vpp-dev
Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Xyxue,
The MPLS config works for me with:
DBGvpp# sh version
vpp v17.07-rc0~314-g79ea7ec built by vagrant on localhost at Wed May 31
00:46:42 PDT 2017
which is master branch from a few hours ago.
Regards,
neale
Packet 1
00:09:02:603978: af-packet-input
af_packet: hw_if_index 1 next-index 4
tpacket2_hdr:
status 0x2001 len 98 snaplen 98 mac 66 net 80
sec 0x592e95b3 nsec 0x8466a6e vlan 0 vlan_tpid 0
00:09:02:604038: ethernet-input
IP4: 3a:4c:48:ed:59:c3 -> 02:fe:1a:e1:c5:4c
00:09:02:604054: ip4-input
ICMP: 192.168.2.20 -> 192.168.3.20
tos 0x00, ttl 64, length 84, checksum 0x26b8
fragment id 0x8d78, flags DONT_FRAGMENT
ICMP echo_request checksum 0x1c3e
00:09:02:604062: ip4-lookup
fib 1 dpo-idx 3 flow hash: 0x
ICMP: 192.168.2.20 -> 192.168.3.20
tos 0x00, ttl 64, length 84, checksum 0x26b8
fragment id 0x8d78, flags DONT_FRAGMENT
ICMP echo_request checksum 0x1c3e
00:09:02:604072: ip4-mpls-label-imposition
mpls-header:[33:63:0:eos]
00:09:02:604081: mpls-midchain
adj-idx 5 : mpls via 0.0.0.0 mpls-tunnel0:
stacked-on:
[@5]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0]
via:[43:3784]]
[0] [@6]: mpls-label:[1]:[34:255:0:neos]
[@1]: mpls via 2.1.1.2 host-vcore-link-1:
02feb30a3b6f02fe4eafc6638847 flow hash: 0x
00:09:02:604088: adj-midchain-tx
adj-midchain:[5]:mpls via 0.0.0.0 mpls-tunnel0:
stacked-on:
[@5]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0]
via:[43:3784]]
[0] [@6]: mpls-label:[1]:[34:255:0:neos]
[@1]: mpls via 2.1.1.2 host-vcore-link-1: 02feb30a3b6f02fe4eafc6638847
00:09:02:604096: mpls-label-imposition
mpls-header:[34:255:0:neos]
00:09:02:604100: mpls-output
adj-idx 4 : mpls via 2.1.1.2 host-vcore-link-1: 02feb30a3b6f02fe4eafc6638847
flow hash: 0x
:
0020:
00:09:02:604102: host-vcore-link-1-output
host-vcore-link-1
MPLS: 02:fe:4e:af:c6:63 -> 02:fe:b3:0a:3b:6f
label 34 exp 0, s 0, ttl 255
Packet 2
00:09:02:604968: af-packet-input
af_packet: hw_if_index 2 next-index 4
tpacket2_hdr:
status 0x2001 len 106 snaplen 106 mac 66 net 80
sec 0x592e95b3 nsec 0x84c97da vlan 0 vlan_tpid 0
00:09:02:604978: ethernet-input
MPLS: 02:fe:b3:0a:3b:6f -> 02:fe:4e:af:c6:63
00:09:02:604987: mpls-input
MPLS: next mpls-lookup[1] label 1024 ttl 255
00:09:02:604993: mpls-lookup
MPLS: next [8], lookup fib index 0, LB index 34 hash 0 label 1024 eos 0
00:09:02:605000: lookup-mpls-dst
fib-index:0 hdr:[1023:63:0:eos] load-balance:33
00:09:02:605005: ip4-mpls-label-disposition
disp:0
00:09:02:605008: lookup-ip4-dst
fib-index:1 addr:192.168.2.20 load-balance:35
00:09:02:605014: ip4-rewrite
tx_sw_if_index 1 dpo-idx 6 : ipv4 via 192.168.2.20 host-vce-link-1:
3a4c48ed59c302fe1ae1c54c0800 flow hash: 0x
: 3a4c48ed59c302fe1ae1c54c08004554e9fd3e010c33c0a80314c0a8
0020: 0214243e07d20010b3952e59311e02001011
00:09:02:605018: host-vce-link-1-output
host-vce-link-1
IP4: 02:fe:1a:e1:c5:4c -> 3a:4c:48:ed:59:c3
ICMP: 192.168.3.20 -> 192.168.2.20
tos 0x00, ttl 62, length 84, checksum 0x0c33
fragment id 0xe9fd
ICMP echo_reply checksum 0x243e
From: 薛欣颖 <xy...@fiberhome.com>
Date: Wednesday, 31 May 2017 at 08:40
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 without MPLS:
###VPP1
create host-interface name eth0
create host-interface name eth1
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
ip route add 192.168.2.0/24 via 2.1.1.2
VPP2
create host-interface name eth0
create host-interface name eth1
set int state host-eth1 up
set int state host-eth0 up
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
ip route add 192.168.3.0/24 via 2.1.1.1
The configuration with MPLS:
PE1
create host-interface name eth0
create host-inter
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Neale,
The configuration without MPLS:
###VPP1
create host-interface name eth0
create host-interface name eth1
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
ip route add 192.168.2.0/24 via 2.1.1.2
VPP2
create host-interface name eth0
create host-interface name eth1
set int state host-eth1 up
set int state host-eth0 up
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
ip route add 192.168.3.0/24 via 2.1.1.1
The configuration with MPLS:
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)
Date: 2017-05-31 15:19
To: 薛欣颖; vpp-dev
Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED
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)
Date: 2017-05-31 15:02
To: 薛欣颖; vpp-dev
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 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 VPP2VPP1
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
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)
Date: 2017-05-31 15:02
To: 薛欣颖; vpp-dev
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 VPP2VPP1
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)
Date: 2017-05-27 18:25
To: 薛欣颖; vpp-dev
Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Xyxue,
One issue at a time please J 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
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 VPP2VPP1 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
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 VPP2VPP1 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) Date: 2017-05-27 18:25 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, One issue at a time please J 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
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 From: 薛欣颖 <xy...@fiberhome.com> Date: Saturday, 27 May 2017 at 11:07 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 ping we were debugging now work.'Bi-directional flow 'is the fade flow send by tester. I'm sure I patched and recompiled the DEBUG version of VPP on both ‘PE’s’. The phenomenon :When there is ip4 flow ,nothing wrong with it.when there is mpls flow ,the checksum come out is not the same as the checksum get into vpp2 .Does the mpls change it? In VPLS the flow was dropped in L2. The configuration and trace is shown below: MPLS L2VPN VPLS 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 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-eth1 2.1.1.1/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.2 host-eth1 out-label 34 out-label 33 set int state mpls-tunnel0 up set interface l2 bridge mpls-tunnel0 1 set interface l2 bridge host-eth0 1 mpls local-label add eos 1023 l2-input-on mpls-tunnel0 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 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-eth1 2.1.1.2/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.1 host-eth1 out-label 1024 out-label 1023 set int state mpls-tunnel0 up set interface l2 bridge mpls-tunnel0 1 set interface l2 bridge host-eth0 1 mpls local-label add eos 33 l2-input-on mpls-tunnel0 mpls local-label add non-eos 34 mpls-lookup-in-table 0 DBGvpp# show trace --- Start of thread 0 vpp_main --- Packet 1 00:04:36:289191: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x9 len 76 snaplen 76 mac 66 net 80 sec 0x2736 nsec 0xb5544e1 vlan 0 00:04:36:291446: ethernet-input IP4: 00:50:43:00:02:02 -> 2c:53:4a:02:91:db 00:04:36:291525: l2-input l2-input: sw_if_index 1 dst 2c:53:4a:02:91:db src 00:50:43:00:02:02 00:04:36:291582: l2-learn l2-learn: sw_if_index 1 dst 2c:53:4a:02:91:db src 00:50:43:00:02:02 bd_index 1 00:04:36:291643: l2-fwd l2-fwd: sw_if_index 1 dst 2c:53:4a:02:91:db src 00:50:43:00:02:02 bd_index 1 00:04:36:291673: error-drop l2-fwd: Reflection Drop Is the configuration correctly? VPWS :Unable to send and receive messages continuously.Sometimes there is no flow receive or send. The configuration and trace is shown below: VPP1 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up 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-eth1 2.1.1.1/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.2 host-eth1 out-label 34 out-label 33 set int state mpls-tunnel0 up set interface l2 xconnect host-eth0 mpls-tunnel0 set interface l2 xconnectmpls-tunnel0 host-eth0 mpls local-label add eos 1023 l2-input-on mpls-tunnel0 mpls local-label add non-eos 1024 mpls-lookup-in-table 0 VPP2 create host-interface name eth0 create host-interface name eth1 set int state host-eth1 up set int state host-eth0 up 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-eth1 2.1.1.2/24 set interface mpls host-eth1 enable mpls tunnel l2-only via 2.1.1.1 host-eth1 out-label 1024 out-label 1023 set int state mpls-tunnel0 up set interface l2 xconnect host-eth0 mpls-tunnel0 set interface l2 xconnectmpls-tunnel0 host-eth0 mpls local-label add eos 33 l2-input-on mpls-tunnel0 mpls local-label add non-eos 34 mpls-lookup-in-table 0 从VPP1VPP2的流量时断时续的.不能正常持续的收发报文 show trace VPP1 Packet 3 00:03:05:985952: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x1 len 124 snaplen 124 mac 66 net 80 sec 0x5b1f nsec 0x35349da1 vlan 0 00:03:05:986527: ethernet-input IP4: 00:10:94:00:00:04 -> 00:03:7f:ff:ff:ff 00:03:05:986683: l2-input l2-input: sw_if_index 1 dst 00:03:7f:ff:ff:ff src 00:10:94:00:00:04 00:03:05:986805: l2-output l2-output: sw_if_index 3 dst 00:03:7f:ff:ff:ff
Re: [vpp-dev] MPLS L3VPN PING FAILED
987162: ethernet-mpls-label-imposition mpls-header:[33:255:0:eos] 00:03:05:987207: mpls-output adj-idx 2 : mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 flow hash: 0xb78171c6 : 0020: 00:03:05:987385: host-eth1-output host-eth1 MPLS: 00:03:7f:ff:ff:fe -> 0e:1a:0d:00:50:43 label 34 exp 0, s 0, ttl 255 - VPP2 Packet 6 00:07:14:455621: af-packet-input af_packet: hw_if_index 2 next-index 4 tpacket2_hdr: status 0x1 len 146 snaplen 146 mac 66 net 80 sec 0x24ba nsec 0x7299553 vlan 0 00:07:14:455772: ethernet-input MPLS: 00:03:7f:ff:ff:fe -> 0e:1a:0d:00:50:43 00:07:14:455928: mpls-input MPLS: next mpls-lookup[1] label 34 ttl 255 00:07:14:456060: mpls-lookup MPLS: next [7], lookup fib index 0, LB index 23 hash 0 label 34 eos 0 00:07:14:456177: lookup-mpls-dst fib-index:0 hdr:[33:255:0:eos] load-balance:21 00:07:14:456251: interface-dpo-l2 sw_if_index:3 00:07:14:456289: l2-input l2-input: sw_if_index 3 dst 00:03:7f:ff:ff:ff src 00:10:94:00:00:04 00:07:14:456468: l2-output l2-output: sw_if_index 1 dst 00:03:7f:ff:ff:ff src 00:10:94:00:00:04 data 08 00 45 c0 00 6e 0b 24 00 00 ff fd 00:07:14:456511: host-eth0-output host-eth0 IP4: 00:10:94:00:00:04 -> 00:03:7f:ff:ff:ff unknown 253: 192.168.3.20 -> 192.168.2.20 tos 0xc0, ttl 255, length 110, checksum 0x2836 fragment id 0x0b24 Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-27 17:11 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED 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 VPP2VPP1 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: 0010940400037fff0800 flow hash: 0x : 0010940400037fff080045c0006e8e07fdfda752c0a80214c0a8 0020: 0314 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: 0x unknown
Re: [vpp-dev] MPLS L3VPN PING FAILED
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 VPP2VPP1 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: 0010940400037fff0800 flow hash: 0x : 0010940400037fff080045c0006e8e07fdfda752c0a80214c0a8 0020: 0314 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: 0x 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: 00037ffe0e1a0d0050438847 flow hash: 0x 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: 00037ffe0e1a0d0050438847 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: 00037ffe0e1a0d0050438847 flow hash: 0x : 0020: 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
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 VPP2VPP1 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: 0010940400037fff0800 flow hash: 0x : 0010940400037fff080045c0006e8e07fdfda752c0a80214c0a8 0020: 0314 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: 0x 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: 00037ffe0e1a0d0050438847 flow hash: 0x 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: 00037ffe0e1a0d0050438847 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: 00037ffe0e1a0d0050438847 flow hash: 0x : 0020: 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
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Xyxue, I found a bug where the lookup DPO for MPLS is not popping the label. The buffer pointer is thus 4 bytes off, and so the IPv4 lookup is done on the source not destination address. Please patch both VPPs with: https://gerrit.fd.io/r/#/c/6883/ thanks, neale From: 薛欣颖 <xy...@fiberhome.com> Date: Friday, 26 May 2017 at 10:26 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, Each of the two VPP is connected to a CE. I'm pinging to and from the CE. Thanks, xyxue From: Neale Ranns (nranns)<mailto:nra...@cisco.com> Date: 2017-05-26 17:07 To: 薛欣颖<mailto:xy...@fiberhome.com>; vpp-dev<mailto:vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, So the addresses you are pinging to and from are not owned by the VPPs. Are you issuing the ping command on a VPP or on the device that owns the address.? /neale From: 薛欣颖 <xy...@fiberhome.com> Date: Friday, 26 May 2017 at 08:43 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, Is this correct in trace: 00:18:57:702675: lookup-ip4-dst fib-index:1 addr:192.168.2.20 load-balance:31 192.168.2.20 is src ip not the dst ip. It seems that lack of pop a label . That is the infomation about it: VPP1: show mplsfib DBGvpp# sh ip fib index 1 192.168.2.20 ipv4-VRF:1, fib_index:1, flow hash:[src dst sport dport proto ] locks:2 192.168.2.0/24 fib:1 index:26 locks:2 src:CLI refs:1 flags:attached,import, index:31 locks:2 flags:shared, uPRF-list:32 len:1 itfs:[3, ] index:31 pl-index:31 ip4 weight=1 attached: oper-flags:resolved, mpls-tunnel0 Extensions: path:31 labels:33 forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:30 buckets:1 uRPF:32 to:[264:30096]] [0] [@10]: mpls-label:[3]:[33:255:0:eos] [@2]: 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:[264:31152]] [0] [@6]: mpls-label:[1]:[34:255:0:neos] [@2]: mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 DBGvpp# DBGvpp# sh ip fib index 1 192.168.3.20 ipv4-VRF:1, fib_index:1, flow hash:[src dst sport dport proto ] locks:2 192.168.3.20/32 fib:1 index:30 locks:2 src:adjacency cover:12 refs:1 flags:attached, index:35 locks:2 uPRF-list:35 len:1 itfs:[1, ] index:35 pl-index:35 ip4 weight=1 attached-nexthop: oper-flags:resolved, 192.168.3.20 host-eth0 [@0]: ipv4 via 192.168.3.20 host-eth0: 0010940400037fff0800 Extensions: path:35 adj-flags:refines-cover forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:35 buckets:1 uRPF:35 to:[0:0]] [0] [@5]: ipv4 via 192.168.3.20 host-eth0: 0010940400037fff0800 DBGvpp# -- vpp2 : show mplsfib DBGvpp# sh ip fib index 1 192.168.2.20 ipv4-VRF:1, fib_index 1, flow hash: src dst sport dport proto 192.168.2.20/32 fib:1 index:31 locks:2 src:adjacency cover:12 refs:1 flags:attached, index:36 locks:2 uPRF-list:36 len:1 itfs:[1, ] index:36 pl-index:36 ipv4 weight=1 attached-nexthop: oper-flags:resolved, 192.168.2.20 host-eth0 [@0]: ipv4 via 192.168.2.20 host-eth0: 001094030050430002020800 Extensions: path:36 adj-flags:refines-cover forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:34 buckets:1 uRPF:36 to:[0:0]] [0] [@5]: ipv4 via 192.168.2.20 host-eth0: 001094030050430002020800 DBGvpp# sh ip fib index 1 192.168.3.20 ipv4-VRF:1, fib_index 1, flow hash: src dst sport dport proto 192.168.3.0/24 fib:1 index:29 locks:2 src:CLI refs:1 flags:attached,import, index:34 locks:2 flags:shared, uPRF-list:35 len:1 itfs:[3, ] index:34 pl-index:34 ipv4 weight=1 attached: oper-flags:resolved, mpls-tunnel0 Extensions: path:34 labels:1023 forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:33 buckets:1 uRPF:35 to:[448:49280]] [0] [@11]: mpls-label:[3]:[1023:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@5]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0] via:[448:51072]] [0] [@8]: mpls-label:[0]:[1024:255:0:neos] [@2]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 DBGvpp# --- VPP1 show int addr DBGvpp# show int addr host-eth0 (up): 192.168.3.1/24 table 1 host-eth1 (up): 2.1.1.1/24 local0 (dn): mpls-tunnel0 (up): DBGvpp#
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi neale, Each of the two VPP is connected to a CE. I'm pinging to and from the CE. Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-26 17:07 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, So the addresses you are pinging to and from are not owned by the VPPs. Are you issuing the ping command on a VPP or on the device that owns the address.? /neale From: 薛欣颖 <xy...@fiberhome.com> Date: Friday, 26 May 2017 at 08:43 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, Is this correct in trace: 00:18:57:702675: lookup-ip4-dst fib-index:1 addr:192.168.2.20 load-balance:31 192.168.2.20 is src ip not the dst ip. It seems that lack of pop a label . That is the infomation about it: VPP1: show mplsfib DBGvpp# sh ip fib index 1 192.168.2.20 ipv4-VRF:1, fib_index:1, flow hash:[src dst sport dport proto ] locks:2 192.168.2.0/24 fib:1 index:26 locks:2 src:CLI refs:1 flags:attached,import, index:31 locks:2 flags:shared, uPRF-list:32 len:1 itfs:[3, ] index:31 pl-index:31 ip4 weight=1 attached: oper-flags:resolved, mpls-tunnel0 Extensions: path:31 labels:33 forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:30 buckets:1 uRPF:32 to:[264:30096]] [0] [@10]: mpls-label:[3]:[33:255:0:eos] [@2]: 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:[264:31152]] [0] [@6]: mpls-label:[1]:[34:255:0:neos] [@2]: mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 DBGvpp# DBGvpp# sh ip fib index 1 192.168.3.20 ipv4-VRF:1, fib_index:1, flow hash:[src dst sport dport proto ] locks:2 192.168.3.20/32 fib:1 index:30 locks:2 src:adjacency cover:12 refs:1 flags:attached, index:35 locks:2 uPRF-list:35 len:1 itfs:[1, ] index:35 pl-index:35 ip4 weight=1 attached-nexthop: oper-flags:resolved, 192.168.3.20 host-eth0 [@0]: ipv4 via 192.168.3.20 host-eth0: 0010940400037fff0800 Extensions: path:35 adj-flags:refines-cover forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:35 buckets:1 uRPF:35 to:[0:0]] [0] [@5]: ipv4 via 192.168.3.20 host-eth0: 0010940400037fff0800 DBGvpp# -- vpp2 : show mplsfib DBGvpp# sh ip fib index 1 192.168.2.20 ipv4-VRF:1, fib_index 1, flow hash: src dst sport dport proto 192.168.2.20/32 fib:1 index:31 locks:2 src:adjacency cover:12 refs:1 flags:attached, index:36 locks:2 uPRF-list:36 len:1 itfs:[1, ] index:36 pl-index:36 ipv4 weight=1 attached-nexthop: oper-flags:resolved, 192.168.2.20 host-eth0 [@0]: ipv4 via 192.168.2.20 host-eth0: 001094030050430002020800 Extensions: path:36 adj-flags:refines-cover forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:34 buckets:1 uRPF:36 to:[0:0]] [0] [@5]: ipv4 via 192.168.2.20 host-eth0: 001094030050430002020800 DBGvpp# sh ip fib index 1 192.168.3.20 ipv4-VRF:1, fib_index 1, flow hash: src dst sport dport proto 192.168.3.0/24 fib:1 index:29 locks:2 src:CLI refs:1 flags:attached,import, index:34 locks:2 flags:shared, uPRF-list:35 len:1 itfs:[3, ] index:34 pl-index:34 ipv4 weight=1 attached: oper-flags:resolved, mpls-tunnel0 Extensions: path:34 labels:1023 forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:33 buckets:1 uRPF:35 to:[448:49280]] [0] [@11]: mpls-label:[3]:[1023:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@5]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0] via:[448:51072]] [0] [@8]: mpls-label:[0]:[1024:255:0:neos] [@2]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 DBGvpp# --- VPP1 show int addr DBGvpp# show int addr host-eth0 (up): 192.168.3.1/24 table 1 host-eth1 (up): 2.1.1.1/24 local0 (dn): mpls-tunnel0 (up): DBGvpp# - VPP2 show int addr DBGvpp# show int addr host-eth0 (up): 192.168.2.1/24 table 1 host-eth1 (up): 2.1.1.2/24 local0 (dn): mpls-tunnel0 (up): DBGvpp# Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-26 15:22 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, If these are the addresses you are pinging to and from: VPP2 ->vpp1 sip： 192.168.2.20 -- dip：192.168.3.20 Then let’s see how they are reachable on each device; sh ip fib index 1 192.168.2.20 sh ip fib index 1 192.168.3.20 on both VPP instances. And
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Xyxue, So the addresses you are pinging to and from are not owned by the VPPs. Are you issuing the ping command on a VPP or on the device that owns the address.? /neale From: 薛欣颖 <xy...@fiberhome.com> Date: Friday, 26 May 2017 at 08:43 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, Is this correct in trace: 00:18:57:702675: lookup-ip4-dst fib-index:1 addr:192.168.2.20 load-balance:31 192.168.2.20 is src ip not the dst ip. It seems that lack of pop a label . That is the infomation about it: VPP1: show mplsfib DBGvpp# sh ip fib index 1 192.168.2.20 ipv4-VRF:1, fib_index:1, flow hash:[src dst sport dport proto ] locks:2 192.168.2.0/24 fib:1 index:26 locks:2 src:CLI refs:1 flags:attached,import, index:31 locks:2 flags:shared, uPRF-list:32 len:1 itfs:[3, ] index:31 pl-index:31 ip4 weight=1 attached: oper-flags:resolved, mpls-tunnel0 Extensions: path:31 labels:33 forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:30 buckets:1 uRPF:32 to:[264:30096]] [0] [@10]: mpls-label:[3]:[33:255:0:eos] [@2]: 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:[264:31152]] [0] [@6]: mpls-label:[1]:[34:255:0:neos] [@2]: mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 DBGvpp# DBGvpp# sh ip fib index 1 192.168.3.20 ipv4-VRF:1, fib_index:1, flow hash:[src dst sport dport proto ] locks:2 192.168.3.20/32 fib:1 index:30 locks:2 src:adjacency cover:12 refs:1 flags:attached, index:35 locks:2 uPRF-list:35 len:1 itfs:[1, ] index:35 pl-index:35 ip4 weight=1 attached-nexthop: oper-flags:resolved, 192.168.3.20 host-eth0 [@0]: ipv4 via 192.168.3.20 host-eth0: 0010940400037fff0800 Extensions: path:35 adj-flags:refines-cover forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:35 buckets:1 uRPF:35 to:[0:0]] [0] [@5]: ipv4 via 192.168.3.20 host-eth0: 0010940400037fff0800 DBGvpp# -- vpp2 : show mplsfib DBGvpp# sh ip fib index 1 192.168.2.20 ipv4-VRF:1, fib_index 1, flow hash: src dst sport dport proto 192.168.2.20/32 fib:1 index:31 locks:2 src:adjacency cover:12 refs:1 flags:attached, index:36 locks:2 uPRF-list:36 len:1 itfs:[1, ] index:36 pl-index:36 ipv4 weight=1 attached-nexthop: oper-flags:resolved, 192.168.2.20 host-eth0 [@0]: ipv4 via 192.168.2.20 host-eth0: 001094030050430002020800 Extensions: path:36 adj-flags:refines-cover forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:34 buckets:1 uRPF:36 to:[0:0]] [0] [@5]: ipv4 via 192.168.2.20 host-eth0: 001094030050430002020800 DBGvpp# sh ip fib index 1 192.168.3.20 ipv4-VRF:1, fib_index 1, flow hash: src dst sport dport proto 192.168.3.0/24 fib:1 index:29 locks:2 src:CLI refs:1 flags:attached,import, index:34 locks:2 flags:shared, uPRF-list:35 len:1 itfs:[3, ] index:34 pl-index:34 ipv4 weight=1 attached: oper-flags:resolved, mpls-tunnel0 Extensions: path:34 labels:1023 forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:33 buckets:1 uRPF:35 to:[448:49280]] [0] [@11]: mpls-label:[3]:[1023:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@5]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0] via:[448:51072]] [0] [@8]: mpls-label:[0]:[1024:255:0:neos] [@2]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 DBGvpp# --- VPP1 show int addr DBGvpp# show int addr host-eth0 (up): 192.168.3.1/24 table 1 host-eth1 (up): 2.1.1.1/24 local0 (dn): mpls-tunnel0 (up): DBGvpp# - VPP2 show int addr DBGvpp# show int addr host-eth0 (up): 192.168.2.1/24 table 1 host-eth1 (up): 2.1.1.2/24 local0 (dn): mpls-tunnel0 (up): DBGvpp# Thanks, xyxue From: Neale Ranns (nranns)<mailto:nra...@cisco.com> Date: 2017-05-26 15:22 To: 薛欣颖<mailto:xy...@fiberhome.com>; vpp-dev<mailto:vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, If these are the addresses you are pinging to and from: VPP2 ->vpp1 sip： 192.168.2.20 -- dip：192.168.3.20 Then let’s see how they are reachable on each device; sh ip fib index 1 192.168.2.20 sh ip fib index 1 192.168.3.20 on both VPP instances. And also: sh int addr on both. Sp we see VPP’s local addresses. Thanks, neale From: 薛欣颖 <xy...@fiberhome.com> Date
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi neale, Is this correct in trace: 00:18:57:702675: lookup-ip4-dst fib-index:1 addr:192.168.2.20 load-balance:31 192.168.2.20 is src ip not the dst ip. It seems that lack of pop a label . That is the infomation about it: VPP1: show mplsfib DBGvpp# sh ip fib index 1 192.168.2.20 ipv4-VRF:1, fib_index:1, flow hash:[src dst sport dport proto ] locks:2 192.168.2.0/24 fib:1 index:26 locks:2 src:CLI refs:1 flags:attached,import, index:31 locks:2 flags:shared, uPRF-list:32 len:1 itfs:[3, ] index:31 pl-index:31 ip4 weight=1 attached: oper-flags:resolved, mpls-tunnel0 Extensions: path:31 labels:33 forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:30 buckets:1 uRPF:32 to:[264:30096]] [0] [@10]: mpls-label:[3]:[33:255:0:eos] [@2]: 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:[264:31152]] [0] [@6]: mpls-label:[1]:[34:255:0:neos] [@2]: mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 DBGvpp# DBGvpp# sh ip fib index 1 192.168.3.20 ipv4-VRF:1, fib_index:1, flow hash:[src dst sport dport proto ] locks:2 192.168.3.20/32 fib:1 index:30 locks:2 src:adjacency cover:12 refs:1 flags:attached, index:35 locks:2 uPRF-list:35 len:1 itfs:[1, ] index:35 pl-index:35 ip4 weight=1 attached-nexthop: oper-flags:resolved, 192.168.3.20 host-eth0 [@0]: ipv4 via 192.168.3.20 host-eth0: 0010940400037fff0800 Extensions: path:35 adj-flags:refines-cover forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:35 buckets:1 uRPF:35 to:[0:0]] [0] [@5]: ipv4 via 192.168.3.20 host-eth0: 0010940400037fff0800 DBGvpp# -- vpp2 : show mplsfib DBGvpp# sh ip fib index 1 192.168.2.20 ipv4-VRF:1, fib_index 1, flow hash: src dst sport dport proto 192.168.2.20/32 fib:1 index:31 locks:2 src:adjacency cover:12 refs:1 flags:attached, index:36 locks:2 uPRF-list:36 len:1 itfs:[1, ] index:36 pl-index:36 ipv4 weight=1 attached-nexthop: oper-flags:resolved, 192.168.2.20 host-eth0 [@0]: ipv4 via 192.168.2.20 host-eth0: 001094030050430002020800 Extensions: path:36 adj-flags:refines-cover forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:34 buckets:1 uRPF:36 to:[0:0]] [0] [@5]: ipv4 via 192.168.2.20 host-eth0: 001094030050430002020800 DBGvpp# sh ip fib index 1 192.168.3.20 ipv4-VRF:1, fib_index 1, flow hash: src dst sport dport proto 192.168.3.0/24 fib:1 index:29 locks:2 src:CLI refs:1 flags:attached,import, index:34 locks:2 flags:shared, uPRF-list:35 len:1 itfs:[3, ] index:34 pl-index:34 ipv4 weight=1 attached: oper-flags:resolved, mpls-tunnel0 Extensions: path:34 labels:1023 forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:33 buckets:1 uRPF:35 to:[448:49280]] [0] [@11]: mpls-label:[3]:[1023:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@5]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0] via:[448:51072]] [0] [@8]: mpls-label:[0]:[1024:255:0:neos] [@2]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 DBGvpp# --- VPP1 show int addr DBGvpp# show int addr host-eth0 (up): 192.168.3.1/24 table 1 host-eth1 (up): 2.1.1.1/24 local0 (dn): mpls-tunnel0 (up): DBGvpp# - VPP2 show int addr DBGvpp# show int addr host-eth0 (up): 192.168.2.1/24 table 1 host-eth1 (up): 2.1.1.2/24 local0 (dn): mpls-tunnel0 (up): DBGvpp# Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-26 15:22 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, If these are the addresses you are pinging to and from: VPP2 ->vpp1 sip： 192.168.2.20 -- dip：192.168.3.20 Then let’s see how they are reachable on each device; sh ip fib index 1 192.168.2.20 sh ip fib index 1 192.168.3.20 on both VPP instances. And also: sh int addr on both. Sp we see VPP’s local addresses. Thanks, neale From: 薛欣颖 <xy...@fiberhome.com> Date: Friday, 26 May 2017 at 03:26 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， That is the infomation about it: VPP2 ->vpp1 sip： 192.168.2.20 -- dip：192.168.3.20 VPP1 show trace （RX） Packet 1 00:18:57:701485: 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 0x5a7 nsec 0x211a6b95 vlan 0 00:18:57:70
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Xyxue, If these are the addresses you are pinging to and from: VPP2 ->vpp1 sip： 192.168.2.20 -- dip：192.168.3.20 Then let’s see how they are reachable on each device; sh ip fib index 1 192.168.2.20 sh ip fib index 1 192.168.3.20 on both VPP instances. And also: sh int addr on both. Sp we see VPP’s local addresses. Thanks, neale From: 薛欣颖 <xy...@fiberhome.com> Date: Friday, 26 May 2017 at 03:26 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， That is the infomation about it: VPP2 ->vpp1 sip： 192.168.2.20 -- dip：192.168.3.20 VPP1 show trace （RX） Packet 1 00:18:57:701485: 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 0x5a7 nsec 0x211a6b95 vlan 0 00:18:57:702142: ethernet-input MPLS: 0e:1a:0d:00:50:43 -> 00:03:7f:ff:ff:fe 00:18:57:702305: mpls-input MPLS: next mpls-lookup[1] label 1024 ttl 255 00:18:57:702436: mpls-lookup MPLS: next [8], lookup fib index 0, LB index 34 hash 0 label 1024 eos 0 00:18:57:702569: lookup-mpls-dst fib-index:0 hdr:[1023:254:0:eos] load-balance:33 00:18:57:702629: ip4-mpls-label-disposition disp:0 00:18:57:702675: lookup-ip4-dst fib-index:1 addr:192.168.2.20 load-balance:31 00:18:57:702795: ip4-mpls-label-imposition mpls-header:[33:82:0:eos] 00:18:57:702851: mpls-midchain adj-idx 5 : mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@3]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0] via:[171485:19898930]] [0] [@6]: mpls-label:[1]:[34:255:0:neos] [@1]: mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 flow hash: 0x 00:18:57:702982: adj-midchain-tx adj-midchain:[5]:mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@3]: dpo-load-balance: [proto:mpls index:32 buckets:1 uRPF:-1 to:[0:0] via:[171485:19898930]] [0] [@6]: mpls-label:[1]:[34:255:0:neos] [@1]: mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 00:18:57:703067: mpls-label-imposition mpls-header:[34:255:0:neos] 00:18:57:703110: mpls-output adj-idx 4 : mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 flow hash: 0x : 0020: 00:18:57:703192: host-eth1-output host-eth1 MPLS: 00:03:7f:ff:ff:fe -> 0e:1a:0d:00:50:43 label 34 exp 0, s 0, ttl 255 - VPP2 show trace （tx） DBGvpp# show trace --- Start of thread 0 vpp_main --- Packet 1 00:21:48:468740: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x1 len 124 snaplen 124 mac 66 net 80 sec 0x66a nsec 0x13c20c2d vlan 0 00:21:48:471028: ethernet-input IP4: 00:10:94:00:00:03 -> 00:50:43:00:02:02 00:21:48:471147: ip4-input unknown 253: 192.168.2.20 -> 192.168.3.20 tos 0xc0, ttl 255, length 110, checksum 0x8fde fragment id 0xa37b 00:21:48:471269: ip4-lookup fib 1 dpo-idx 3 flow hash: 0x unknown 253: 192.168.2.20 -> 192.168.3.20 tos 0xc0, ttl 255, length 110, checksum 0x8fde fragment id 0xa37b 00:21:48:471339: ip4-mpls-label-imposition mpls-header:[1023:254:0:eos] 00:21:48:471386: mpls-midchain adj-idx 5 : mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@3]: dpo-load-balance: [proto:mpls index:34 buckets:1 uRPF:-1 to:[0:0] via:[191878:22337288]] [0] [@8]: mpls-label:[1]:[1024:255:0:neos] [@1]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 flow hash: 0x 00:21:48:471415: adj-midchain-tx adj-midchain:[5]:mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@3]: dpo-load-balance: [proto:mpls index:34 buckets:1 uRPF:-1 to:[0:0] via:[191878:22337288]] [0] [@8]: mpls-label:[1]:[1024:255:0:neos] [@1]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 00:21:48:471454: mpls-label-imposition mpls-header:[1024:255:0:neos] 00:21:48:471501: mpls-output adj-idx 4 : mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 flow hash: 0x : 0020: 00:21:48:471535: 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 - VPP1 show mpls fib DBGvpp# sh ip fib index 1 192.168.3.20 ipv4-VRF:1, fib_index:1, flow hash:[src dst sport dport proto ] locks:2 192.168.3.20/32 fib:1 index:30 locks:2 src:adjacency cover:12 refs:1 flags:attached, index:35 locks:2 uPRF-list:35 len:1 itfs:[1, ] index:35 pl-index:35
Re: [vpp-dev] MPLS L3VPN PING FAILED
9:05 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, Thanks, that helps. Can I also see: 1) The ‘sh trace’ (with the patch applied) 2) ‘sh ip fib index 1’ where this time PREFIX is the address the RX packets should match. Thanks, neale From: 薛欣颖 <xy...@fiberhome.com> Date: Thursday, 25 May 2017 at 11:52 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, That is the infomation about it: MPLS configuration： VPP1: FTN mpls tunnel add via 2.1.1.2 host-eth1 out-label 34 set int state mpls-tunnel0 up ILM 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 VPP2 ILM mpls local-label add eos 33 ip4-lookup-in-table 1 mpls local-label add non-eos 34 mpls-lookup-in-table 0 FTN 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 - VPP1 mpls fib info: DBGvpp# sh mpls fib 33 MPLS-VRF:0, fib_index 0 DBGvpp# sh mpls fib 34 MPLS-VRF:0, fib_index 0 DBGvpp# sh mpls fib 1023 MPLS-VRF:0, fib_index 0 1023:eos/21 fib:0 index:29 locks:2 src:CLI refs:1 index:34 locks:2 flags:shared, uPRF-list:33 len:0 itfs:[] index:34 pl-index:34 ipv4 weight=1 deag: oper-flags:resolved, [@0]: dst-address,unicast lookup in ipv4-VRF:1 forwarding: mpls-eos-chain [@0]: dpo-load-balance: [proto:mpls index:34 buckets:1 uRPF:33 to:[28634:3306044]] [0] [@7]: mpls-disposition:[0]:[ip4] [@1]: dst-address,unicast lookup in ipv4-VRF:1 DBGvpp# sh mpls fib 1024 MPLS-VRF:0, fib_index 0 1024:neos/21 fib:0 index:30 locks:2 src:CLI refs:1 index:35 locks:2 flags:shared, uPRF-list:35 len:0 itfs:[] index:35 pl-index:35 MPLS weight=1 deag: oper-flags:resolved, [@0]: dst-address,unicast lookup in MPLS-VRF:0 forwarding: mpls-neos-chain [@0]: dpo-load-balance: [proto:mpls index:35 buckets:1 uRPF:35 to:[29133:3480258]] [0] [@8]: dst-address,unicast lookup in MPLS-VRF:0 --- VPP2:show mpls fib ： DBGvpp# show mpls fib 33 MPLS-VRF:0, fib_index 0 33:eos/21 fib:0 index:27 locks:2 src:CLI refs:1 index:31 locks:2 flags:shared, uPRF-list:31 len:0 itfs:[] index:31 pl-index:31 ipv4 weight=1 deag: oper-flags:resolved, [@0]: dst-address,unicast lookup in ipv4-VRF:1 forwarding: mpls-eos-chain [@0]: dpo-load-balance: [proto:mpls index:30 buckets:1 uRPF:31 to:[100039:11561273]] [0] [@6]: mpls-disposition:[0]:[ip4] [@1]: dst-address,unicast lookup in ipv4-VRF:1 DBGvpp# show mpls fib 34 MPLS-VRF:0, fib_index 0 34:neos/21 fib:0 index:28 locks:2 src:CLI refs:1 index:32 locks:2 flags:shared, uPRF-list:32 len:0 itfs:[] index:32 pl-index:32 MPLS weight=1 deag: oper-flags:resolved, [@0]: dst-address,unicast lookup in MPLS-VRF:0 forwarding: mpls-neos-chain [@0]: dpo-load-balance: [proto:mpls index:31 buckets:1 uRPF:32 to:[100520:12018915]] [0] [@7]: dst-address,unicast lookup in MPLS-VRF:0 DBGvpp# show mpls fib 1024 MPLS-VRF:0, fib_index 0 DBGvpp# show mpls fib 1023 MPLS-VRF:0, fib_index 0 DBGvpp# --- VPP1 show ip fib index 1 DBGvpp# show ip fib index 1 192.168.2.0 ipv4-VRF:1, fib_index 1, flow hash: src dst sport dport proto 192.168.2.0/24 fib:1 index:28 locks:2 src:CLI refs:1 flags:attached,import, index:33 locks:2 flags:shared, uPRF-list:34 len:1 itfs:[3, ] index:33 pl-index:33 ipv4 weight=1 attached: oper-flags:resolved, mpls-tunnel0 Extensions: path:33 labels:33 forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:32 buckets:1 uRPF:34 to:[130199:14584513]] [0] [@11]: mpls-label:[3]:[33:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@5]: dpo-load-balance: [proto:mpls index:33 buckets:1 uRPF:-1 to:[0:0] via:[130199:15105309]] [0] [@6]: mpls-label:[1]:[34:255:0:neos] [@1]: mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 DBGvpp# VPP2 show ip fib index 1 DBGvpp# show ip fib index 1 192.168.3.0 ipv4-VRF:1, fib_index 1, flow hash: src dst sport dport proto 192.168.3.0/24 fib:1 index:29 locks:2 src:CLI refs:1 flags:attached,import, index:34 locks:2 flags:shared, uPRF-list:35 len:1 itfs:[3, ] index:34 pl-index:34 ipv4 weight=1 attached: oper-flags:resolved, mpls-tunnel0
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Xyxue, Thanks, that helps. Can I also see: 1) The ‘sh trace’ (with the patch applied) 2) ‘sh ip fib index 1’ where this time PREFIX is the address the RX packets should match. Thanks, neale From: 薛欣颖 <xy...@fiberhome.com> Date: Thursday, 25 May 2017 at 11:52 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, That is the infomation about it: MPLS configuration： VPP1: FTN mpls tunnel add via 2.1.1.2 host-eth1 out-label 34 set int state mpls-tunnel0 up ILM 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 VPP2 ILM mpls local-label add eos 33 ip4-lookup-in-table 1 mpls local-label add non-eos 34 mpls-lookup-in-table 0 FTN 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 - VPP1 mpls fib info: DBGvpp# sh mpls fib 33 MPLS-VRF:0, fib_index 0 DBGvpp# sh mpls fib 34 MPLS-VRF:0, fib_index 0 DBGvpp# sh mpls fib 1023 MPLS-VRF:0, fib_index 0 1023:eos/21 fib:0 index:29 locks:2 src:CLI refs:1 index:34 locks:2 flags:shared, uPRF-list:33 len:0 itfs:[] index:34 pl-index:34 ipv4 weight=1 deag: oper-flags:resolved, [@0]: dst-address,unicast lookup in ipv4-VRF:1 forwarding: mpls-eos-chain [@0]: dpo-load-balance: [proto:mpls index:34 buckets:1 uRPF:33 to:[28634:3306044]] [0] [@7]: mpls-disposition:[0]:[ip4] [@1]: dst-address,unicast lookup in ipv4-VRF:1 DBGvpp# sh mpls fib 1024 MPLS-VRF:0, fib_index 0 1024:neos/21 fib:0 index:30 locks:2 src:CLI refs:1 index:35 locks:2 flags:shared, uPRF-list:35 len:0 itfs:[] index:35 pl-index:35 MPLS weight=1 deag: oper-flags:resolved, [@0]: dst-address,unicast lookup in MPLS-VRF:0 forwarding: mpls-neos-chain [@0]: dpo-load-balance: [proto:mpls index:35 buckets:1 uRPF:35 to:[29133:3480258]] [0] [@8]: dst-address,unicast lookup in MPLS-VRF:0 --- VPP2:show mpls fib ： DBGvpp# show mpls fib 33 MPLS-VRF:0, fib_index 0 33:eos/21 fib:0 index:27 locks:2 src:CLI refs:1 index:31 locks:2 flags:shared, uPRF-list:31 len:0 itfs:[] index:31 pl-index:31 ipv4 weight=1 deag: oper-flags:resolved, [@0]: dst-address,unicast lookup in ipv4-VRF:1 forwarding: mpls-eos-chain [@0]: dpo-load-balance: [proto:mpls index:30 buckets:1 uRPF:31 to:[100039:11561273]] [0] [@6]: mpls-disposition:[0]:[ip4] [@1]: dst-address,unicast lookup in ipv4-VRF:1 DBGvpp# show mpls fib 34 MPLS-VRF:0, fib_index 0 34:neos/21 fib:0 index:28 locks:2 src:CLI refs:1 index:32 locks:2 flags:shared, uPRF-list:32 len:0 itfs:[] index:32 pl-index:32 MPLS weight=1 deag: oper-flags:resolved, [@0]: dst-address,unicast lookup in MPLS-VRF:0 forwarding: mpls-neos-chain [@0]: dpo-load-balance: [proto:mpls index:31 buckets:1 uRPF:32 to:[100520:12018915]] [0] [@7]: dst-address,unicast lookup in MPLS-VRF:0 DBGvpp# show mpls fib 1024 MPLS-VRF:0, fib_index 0 DBGvpp# show mpls fib 1023 MPLS-VRF:0, fib_index 0 DBGvpp# --- VPP1 show ip fib index 1 DBGvpp# show ip fib index 1 192.168.2.0 ipv4-VRF:1, fib_index 1, flow hash: src dst sport dport proto 192.168.2.0/24 fib:1 index:28 locks:2 src:CLI refs:1 flags:attached,import, index:33 locks:2 flags:shared, uPRF-list:34 len:1 itfs:[3, ] index:33 pl-index:33 ipv4 weight=1 attached: oper-flags:resolved, mpls-tunnel0 Extensions: path:33 labels:33 forwarding: unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:32 buckets:1 uRPF:34 to:[130199:14584513]] [0] [@11]: mpls-label:[3]:[33:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@5]: dpo-load-balance: [proto:mpls index:33 buckets:1 uRPF:-1 to:[0:0] via:[130199:15105309]] [0] [@6]: mpls-label:[1]:[34:255:0:neos] [@1]: mpls via 2.1.1.2 host-eth1: 0e1a0d00504300037ffe8847 DBGvpp# VPP2 show ip fib index 1 DBGvpp# show ip fib index 1 192.168.3.0 ipv4-VRF:1, fib_index 1, flow hash: src dst sport dport proto 192.168.3.0/24 fib:1 index:29 locks:2 src:CLI refs:1 flags:attached,import, index:34 locks:2 flags:shared, uPRF-list:35 len:1 itfs:[3, ] index:34 pl-index:34 ipv4 weight=1 attached: oper-flags:resolved, mpls-tunnel0 Extensions: path:34 labels:1023 forwarding: unicast-ip4-chain [@0]:
Re: [vpp-dev] MPLS L3VPN PING FAILED
: 00037ffe0e1a0d0050438847 DBGvpp# --- VPP1 show error ： DBGvpp# show error CountNode Reason 114 ethernet-input l3 mac mismatch 3ip4-glean address overflow drops 213ip4-glean ARP requests sent 15ip4-input ip4 length > l2 length 95199ip4-input ip4 adjacency drop 190519 mpls-lookup MPLS input packets decapsulated 381270 mpls-output MPLS output packets encapsulated 190519 mpls-input MPLS input packets decapsulated DBGvpp# VPP2 show error： DBGvpp# show error CountNode Reason 1345 mpls-input MPLS input packets decapsulated 2664 mpls-output MPLS output packets encapsulated 1345 mpls-lookup MPLS input packets decapsulated 685ip4-input ip4 adjacency drop 10ip4-glean ARP requests sent 5 ethernet-input l3 mac mismatch DBGvpp# Bidirectional flow,Messages can already go out of the interface and encapsulate the corresponding two tags,but droped at the other end equipment. Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-25 15:00 To: 薛欣颖; vpp-dev Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, A few things please: 1) A Chris mentions on another thread, please add https://gerrit.fd.io/r/#/c/6865 so we see a better trace 2) Please collect ‘sh mpls fib ’, for both of the labels you are popping 3) Please collect ‘sh ip fib index 1 ’ for the prefix you expect the decapped packet to match. Thanks, neale From: 薛欣颖 <xy...@fiberhome.com> Date: Thursday, 25 May 2017 at 06:36 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 ping still failed .Here is the specific information： DBGvpp# show trace CLIB unknown format `%#' x label 0 eos 1024 17:23:38:439098: lookup-mpls-dst fib-index:0 hdr:[1023:85:0:eos] load-balance:29 17:23:38:439159: ip4-mpls-label-disposition disp:0 17:23:38:439198: lookup-ip4-dst fib-index:1 addr:63.1.94.231 load-balance:9 17:23:38:439325: ip4-drop IP6_HOP_BY_HOP_OPTIONS: 85.93.65.0 -> 63.1.94.231 version 0, header length 0 tos 0x3f, ttl 69, length 61781, checksum 0x0054 (should be 0x) fragment id 0x0002 offset 35320, flags CONGESTION 17:23:38:439391: error-drop ip4-input: ip4 adjacency drop By the way , I didn't build tunnels. Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-24 18:18 To: 薛欣颖; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, The lookup was performed in FIB index 1– you must have used ‘set int ip table host-XXX YYY’ - but the route you added is in the default table. If you want the routes in the same table as the interface do; Ip route add table YYY 192.168.3.0/24 via mpls-tunnel0 out-label 1023 Regards, Neale p.s. are you really constructing the L3VPN from a [full] mesh of MPLS tunnels, or is it LDP in the core? From: <vpp-dev-boun...@lists.fd.io> on behalf of 薛欣颖 <xy...@fiberhome.com> Date: Wednesday, 24 May 2017 at 09:09 To: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io> Subject: [vpp-dev] MPLS L3VPN PING FAILED Hi guys, I have the following configuration: 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 via mpls-tunnel0 out-label 1023 Ping from CE to PE ,and the PE drop it. That is the fib : 192.168.3.0/24 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:34 buckets:1 uRPF:36 to:[15:1260]] [0] [@11]: mpls-label:[3]:[1023:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@5]: dpo-load-balance: [proto:mpls index:35 buckets:1 uRPF:-1 to:[0:0] via:[15:1320]] [0] [@8]: mpls-label:[1]:[1024:255:0:neos] [@1]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 The following is the trace info: 00:17:54:791606: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x1 len 98 snaplen 98 mac 66 net 80 sec 0x16645 nsec 0x34a33284 vlan 0 00:17:54:791899: ethernet-input IP4: 2c:53:4a:02:91:95 -> 00:50:43:00:02:02 00:17:54:791956: ip4-input ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Xyxue, A few things please: 1) A Chris mentions on another thread, please add https://gerrit.fd.io/r/#/c/6865 so we see a better trace 2) Please collect ‘sh mpls fib ’, for both of the labels you are popping 3) Please collect ‘sh ip fib index 1 ’ for the prefix you expect the decapped packet to match. Thanks, neale From: 薛欣颖 <xy...@fiberhome.com> Date: Thursday, 25 May 2017 at 06:36 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 ping still failed .Here is the specific information： DBGvpp# show trace CLIB unknown format `%#' x label 0 eos 1024 17:23:38:439098: lookup-mpls-dst fib-index:0 hdr:[1023:85:0:eos] load-balance:29 17:23:38:439159: ip4-mpls-label-disposition disp:0 17:23:38:439198: lookup-ip4-dst fib-index:1 addr:63.1.94.231 load-balance:9 17:23:38:439325: ip4-drop IP6_HOP_BY_HOP_OPTIONS: 85.93.65.0 -> 63.1.94.231 version 0, header length 0 tos 0x3f, ttl 69, length 61781, checksum 0x0054 (should be 0x) fragment id 0x0002 offset 35320, flags CONGESTION 17:23:38:439391: error-drop ip4-input: ip4 adjacency drop By the way , I didn't build tunnels. Thanks, xyxue From: Neale Ranns (nranns)<mailto:nra...@cisco.com> Date: 2017-05-24 18:18 To: 薛欣颖<mailto:xy...@fiberhome.com>; vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, The lookup was performed in FIB index 1– you must have used ‘set int ip table host-XXX YYY’ - but the route you added is in the default table. If you want the routes in the same table as the interface do; Ip route add table YYY 192.168.3.0/24 via mpls-tunnel0 out-label 1023 Regards, Neale p.s. are you really constructing the L3VPN from a [full] mesh of MPLS tunnels, or is it LDP in the core? From: <vpp-dev-boun...@lists.fd.io> on behalf of 薛欣颖 <xy...@fiberhome.com> Date: Wednesday, 24 May 2017 at 09:09 To: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io> Subject: [vpp-dev] MPLS L3VPN PING FAILED Hi guys, I have the following configuration: 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 via mpls-tunnel0 out-label 1023 Ping from CE to PE ,and the PE drop it. That is the fib : 192.168.3.0/24 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:34 buckets:1 uRPF:36 to:[15:1260]] [0] [@11]: mpls-label:[3]:[1023:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@5]: dpo-load-balance: [proto:mpls index:35 buckets:1 uRPF:-1 to:[0:0] via:[15:1320]] [0] [@8]: mpls-label:[1]:[1024:255:0:neos] [@1]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 The following is the trace info: 00:17:54:791606: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x1 len 98 snaplen 98 mac 66 net 80 sec 0x16645 nsec 0x34a33284 vlan 0 00:17:54:791899: ethernet-input IP4: 2c:53:4a:02:91:95 -> 00:50:43:00:02:02 00:17:54:791956: ip4-input ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886 fragment id 0xabbe, flags DONT_FRAGMENT ICMP echo_request checksum 0xae6a 00:17:54:792005: ip4-lookup fib 1 dpo-idx 1 flow hash: 0x ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886 fragment id 0xabbe, flags DONT_FRAGMENT ICMP echo_request checksum 0xae6a 00:17:54:792062: ip4-drop ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886 fragment id 0xabbe, flags DONT_FRAGMENT ICMP echo_request checksum 0xae6a 00:17:54:792110: error-drop ip4-input: ip4 adjacency drop How can I solve the problem? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
Re: [vpp-dev] MPLS L3VPN PING FAILED
Hi Neale, The ping still failed .Here is the specific information： DBGvpp# show trace CLIB unknown format `%#' x label 0 eos 1024 17:23:38:439098: lookup-mpls-dst fib-index:0 hdr:[1023:85:0:eos] load-balance:29 17:23:38:439159: ip4-mpls-label-disposition disp:0 17:23:38:439198: lookup-ip4-dst fib-index:1 addr:63.1.94.231 load-balance:9 17:23:38:439325: ip4-drop IP6_HOP_BY_HOP_OPTIONS: 85.93.65.0 -> 63.1.94.231 version 0, header length 0 tos 0x3f, ttl 69, length 61781, checksum 0x0054 (should be 0x) fragment id 0x0002 offset 35320, flags CONGESTION 17:23:38:439391: error-drop ip4-input: ip4 adjacency drop By the way , I didn't build tunnels. Thanks, xyxue From: Neale Ranns (nranns) Date: 2017-05-24 18:18 To: 薛欣颖; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] MPLS L3VPN PING FAILED Hi Xyxue, The lookup was performed in FIB index 1– you must have used ‘set int ip table host-XXX YYY’ - but the route you added is in the default table. If you want the routes in the same table as the interface do; Ip route add table YYY 192.168.3.0/24 via mpls-tunnel0 out-label 1023 Regards, Neale p.s. are you really constructing the L3VPN from a [full] mesh of MPLS tunnels, or is it LDP in the core? From: <vpp-dev-boun...@lists.fd.io> on behalf of 薛欣颖 <xy...@fiberhome.com> Date: Wednesday, 24 May 2017 at 09:09 To: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io> Subject: [vpp-dev] MPLS L3VPN PING FAILED Hi guys, I have the following configuration: 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 via mpls-tunnel0 out-label 1023 Ping from CE to PE ,and the PE drop it. That is the fib : 192.168.3.0/24 unicast-ip4-chain [@0]: dpo-load-balance: [proto:ip4 index:34 buckets:1 uRPF:36 to:[15:1260]] [0] [@11]: mpls-label:[3]:[1023:255:0:eos] [@2]: mpls via 0.0.0.0 mpls-tunnel0: stacked-on: [@5]: dpo-load-balance: [proto:mpls index:35 buckets:1 uRPF:-1 to:[0:0] via:[15:1320]] [0] [@8]: mpls-label:[1]:[1024:255:0:neos] [@1]: mpls via 2.1.1.1 host-eth1: 00037ffe0e1a0d0050438847 The following is the trace info: 00:17:54:791606: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x1 len 98 snaplen 98 mac 66 net 80 sec 0x16645 nsec 0x34a33284 vlan 0 00:17:54:791899: ethernet-input IP4: 2c:53:4a:02:91:95 -> 00:50:43:00:02:02 00:17:54:791956: ip4-input ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886 fragment id 0xabbe, flags DONT_FRAGMENT ICMP echo_request checksum 0xae6a 00:17:54:792005: ip4-lookup fib 1 dpo-idx 1 flow hash: 0x ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886 fragment id 0xabbe, flags DONT_FRAGMENT ICMP echo_request checksum 0xae6a 00:17:54:792062: ip4-drop ICMP: 192.168.2.10 -> 192.168.3.10 tos 0x00, ttl 64, length 84, checksum 0x0886 fragment id 0xabbe, flags DONT_FRAGMENT ICMP echo_request checksum 0xae6a 00:17:54:792110: error-drop ip4-input: ip4 adjacency drop How can I solve the problem? Thanks, xyxue ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
