Hi Neale， After referring to your example, I modified my configuration. And the two layer label SR MPLS works well. But when configure ten layer label, the bottom label is different from the configuration.
vpp1 configuration: create host-interface name eth4 mac 00:0c:29:4d:af:b5 create host-interface name eth2 mac 00:0c:29:4d:af:a1 set interface state host-eth2 up set interface state host-eth4 up set interface ip address host-eth2 14.1.1.1/24 set interface ip address host-eth4 21.1.1.1/24 mpls table add 0 set interface mpls host-eth2 enable sr mpls policy add bsid 999 next 210 next 209 next 208 next 207 next 206 next 205 next 204 next 203 next 202 next 201 // encap 10 layer label sr mpls steer l3 23.1.1.0/24 via sr policy bsid 999 mpls local-label add non-eos 210 via 14.1.1.2 host-eth2 out-label 211 Actually, the bottom is 16416 (the value configured is 201). The ttl is 63 and others is 255. The trace info and message info is shown below: 00:31:47:618725: af-packet-input af_packet: hw_if_index 1 next-index 4 tpacket2_hdr: status 0x20000001 len 78 snaplen 78 mac 66 net 80 sec 0x5a1fb1aa nsec 0x22ae91a9 vlan 0 00:31:47:618752: ethernet-input IP4: 00:00:00:66:00:55 -> 00:0c:29:4d:af:b5 00:31:47:618815: ip4-input ICMP: 21.1.1.5 -> 23.1.1.5 tos 0x00, ttl 64, length 64, checksum 0x4cb1 fragment id 0x0001 ICMP echo_request checksum 0x5f5d 00:31:47:618823: ip4-lookup fib 0 dpo-idx 34 flow hash: 0x00000000 ICMP: 21.1.1.5 -> 23.1.1.5 tos 0x00, ttl 64, length 64, checksum 0x4cb1 fragment id 0x0001 ICMP echo_request checksum 0x5f5d 00:31:47:618833: ip4-load-balance fib 0 dpo-idx 34 flow hash: 0x00000000 ICMP: 21.1.1.5 -> 23.1.1.5 tos 0x00, ttl 64, length 64, checksum 0x4cb1 fragment id 0x0001 ICMP echo_request checksum 0x5f5d 00:31:47:618837: ip4-mpls-label-imposition mpls-header:[16416:63:0:eos] 00:31:47:618844: mpls-label-imposition mpls-header:[211:255:0:neos] 00:31:47:618846: mpls-output adj-idx 3 : mpls via 14.1.1.2 host-eth2: 000c290fe2a8000c294dafa18847 flow hash: 0x00000000 00000000: 0000000000000000000000000000000000000000000000000000000000000000 00000020: 00000000000000000000000000000000000000000000000000000000 00:31:47:618853: host-eth2-output host-eth2 MPLS: 00:0c:29:4d:af:a1 -> 00:0c:29:0f:e2:a8 label 211 exp 0, s 0, ttl 255 Thanks for your help. Thanks,Xyxue From: Neale Ranns (nranns) Date: 2017-11-29 16:37 To: 薛欣颖; Pablo Camarillo (pcamaril); vpp-dev Subject: Re: [vpp-dev] SR MPLS not effective Hi Xyxue, Here’s a hastily assembled guide on how I would do it; https://wiki.fd.io/view/VPP/Segment_Routing_for_MPLS I’ve not verified the configs myself. If you use it, please let me know any errors you find. Regards, neale From: 薛欣颖 <xy...@fiberhome.com> Date: Wednesday, 29 November 2017 at 08:13 To: "Neale Ranns (nranns)" <nra...@cisco.com>, "Pablo Camarillo (pcamaril)" <pcama...@cisco.com>, vpp-dev <vpp-dev@lists.fd.io> Subject: Re: Re: [vpp-dev] SR MPLS not effective After add the 'mpls local-label add non-eos 33 mpls-lookup-in-table 0 ' on P, the mistake still exist.
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
