Hi Xyxue,
Thanks, that helps.
Can I also see:
1) The ‘sh trace’ (with the patch applied)
2) ‘sh ip fib index 1<PREFIX>’ 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: 0e1a0d00504300037ffffffe8847
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]: dpo-load-balance: [proto:ip4 index:33 buckets:1 uRPF:35
to:[143537:16147757]]
[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:34 buckets:1 uRPF:-1
to:[0:0] via:[143537:16721905]]
[0] [@8]: mpls-label:[1]:[1024:255:0:neos]
[@1]: mpls via 2.1.1.1 host-eth1: 00037ffffffe0e1a0d0050438847
DBGvpp#
-----------------------------------------------------------
VPP1 show error ：
DBGvpp# show error
Count Node Reason
114 ethernet-input l3 mac mismatch
3 ip4-glean address overflow drops
213 ip4-glean ARP requests sent
15 ip4-input ip4 length > l2 length
95199 ip4-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
Count Node Reason
1345 mpls-input MPLS input packets
decapsulated
2664 mpls-output MPLS output packets
encapsulated
1345 mpls-lookup MPLS input packets
decapsulated
685 ip4-input ip4 adjacency drop
10 ip4-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)<mailto:nra...@cisco.com>
Date: 2017-05-25 15:00
To: 薛欣颖<mailto:xy...@fiberhome.com>; vpp-dev<mailto:vpp-dev@lists.fd.io>
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 <LABEL>’, for both of the labels you are
popping
3) Please collect ‘sh ip fib index 1 <PREFIX>’ 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 0xffff)
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: 00037ffffffe0e1a0d0050438847
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: 0x00000000
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
