VPP does not have MPLS trace-route support. I’d suggest using the packet trace; trace add <INPUT-NODE> 50 show trace
/neale From: Алексей Болдырев <devel-net-ne-vleza...@yandex.ru> Date: Monday, 14 August 2017 at 23:52 To: Michael Borokhovich <michael...@gmail.com>, "Neale Ranns (nranns)" <nra...@cisco.com> Cc: "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] MPLS labels question Скажите пожалуйста, умеет ли vpp отображать процесс в трассировке о надивании и снятии MPLS-меток? Как например тут: traceroute to kernel.org (198.145.29.83), 30 hops max, 60 byte packets 1 10.247.1.1 (10.247.1.1) 0.095 ms 0.127 ms 0.122 ms 2 100.64.0.1 (100.64.0.1) 0.765 ms 0.753 ms 0.893 ms 3 192.168.192.193 (192.168.192.193) 5.333 ms 5.334 ms 5.329 ms 4 192.168.192.1 (192.168.192.1) 4.476 ms * * 5 kiev-r0.w-ix.net (193.106.112.4) 31.109 ms 28.508 ms 28.508 ms 6 * * * 7 10ge1-8.core1.vie1.he.net (184.105.222.25) 61.858 ms 61.844 ms 59.284 ms 8 100ge13-1.core1.par2.he.net (184.105.65.5) 70.435 ms 70.443 ms 70.592 ms 9 100ge14-1.core1.nyc4.he.net (184.105.81.77) 150.720 ms 150.975 ms 151.391 ms 10 100ge14-1.core1.tor1.he.net (184.105.80.10) <MPLS:L=2198,E=0,S=1,T=1> 154.989 ms 155.078 ms 146.024 ms 11 100ge6-1.core1.ywg1.he.net (184.105.64.102) <MPLS:L=2048,E=0,S=1,T=1> 176.754 ms 162.817 ms 168.390 ms 12 100ge10-1.core1.yyc1.he.net (184.105.222.98) <MPLS:L=2486,E=0,S=1,T=1> 180.728 ms 183.503 ms 192.020 ms 13 100ge10-2.core1.yvr1.he.net (184.105.64.113) <MPLS:L=2227,E=0,S=1,T=1> 240.695 ms 239.889 ms 236.867 ms 14 100ge10-2.core1.sea1.he.net (184.105.64.109) 193.678 ms 196.335 ms 196.401 ms 15 100ge14-1.core1.pdx1.he.net (184.105.64.138) 193.324 ms 195.997 ms 196.036 ms 16 infinity-internet-inc.gigabitethernet2-11.core1.pdx1.he.net (64.71.165.18) 195.808 ms 196.093 ms 195.852 ms 17 xe-6-0-0.r-1.linuxfoundation.org (198.145.0.9) 197.070 ms 197.043 ms 197.272 ms 18 fw-1.linuxfoundation.org (198.145.0.11) 196.924 ms 197.011 ms 196.879 ms 19 kernel.org (198.145.29.83) 199.697 ms 197.026 ms 199.542 ms 14.08.2017, 22:37, "Michael Borokhovich" <michael...@gmail.com>: Thanks a lot for the explanation, Neale! I actually need that all incoming traffic with label 222 will go to a specific VRF (table 1). So, as I understand, this can be achieved by: mpls local-label add eos 222 ip4-lookup-in-table 1 And in this case, it seems that I always have to use "add eos". On Mon, Aug 14, 2017 at 1:59 PM, Neale Ranns (nranns) <nra...@cisco.com<mailto:nra...@cisco.com>> wrote: No, not quite. There’s a need to add ‘eos’ if you want the label entry to match against that label AND against the set EOS bit. An MPLS lookup is really a 21 bit match; 20 bits of label value and 1 bit EOS. It only makes sense to send EOS traffic to IP lookup. Sending non-EOS traffic to a IP lookup would not result in something good. If label 222 has been dedicated to 10.100.2.0/24<http://10.100.2.0/24> (i.e. when we the receiver gets traffic with label 222, it must be for 10.100.2.0/24<http://10.100.2.0/24>) then the command you are looking for is; mpls local-label 222 10.100.2.0/24<http://10.100.2.0/24> this does what the API refers to as a ‘bind’. It says, whatever IP does for 10.100.2.0/24<http://10.100.2.0/24>, MPLS should do for label 222. It will add the eos and non-eos entries appropriately. /neale From: Michael Borokhovich <michael...@gmail.com<mailto:michael...@gmail.com>> Date: Monday, 14 August 2017 at 18:20 To: "Neale Ranns (nranns)" <nra...@cisco.com<mailto:nra...@cisco.com>> Cc: "vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>" <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>> Subject: Re: [vpp-dev] MPLS labels question I see.. so there is a need to add the "add eos" to the "mpls local-label" command if I want to send the packet to the IP lookup after popping a single (the only) label. Thanks, Neale! On Mon, Aug 14, 2017 at 1:01 PM, Neale Ranns (nranns) <nra...@cisco.com<mailto:nra...@cisco.com>> wrote: Hi Michael, ‘add’ is the default. It’s necessary to specify ‘eos’ because it I the end-of-stack entry you are adding and the default (i.e. without ‘eos’) is to add the non-end-of-stack entry. Regards, neale From: <vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io>> on behalf of Michael Borokhovich <michael...@gmail.com<mailto:michael...@gmail.com>> Date: Monday, 14 August 2017 at 16:58 To: "vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>" <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>> Subject: [vpp-dev] MPLS labels question Hi, I'm adding a label using the following command: ip route add 10.100.2.0/24<http://10.100.2.0/24> table 1 via 10.100.4.12 GigabitEthernet0/6/0 out-label 222 And on the receiving side poping it with: set interface mpls GigabitEthernet0/6/0 enable mpls local-label 222 ip4-lookup-in-table 1 However, this didn't work until I added "add eos" to the last command, i.e., the following worked: mpls local-label add eos 222 ip4-lookup-in-table 1 Why is it necessary to specify "add eos" at the receiving side? Or maybe my configuration of the sender's side is wrong? Thanks, Michael. , _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
