There is no limit to the number of labels that can be specified. /neale
From: <[email protected]> on behalf of "Neale Ranns (nranns)" <[email protected]> Date: Monday, 14 August 2017 at 18:03 To: Алексей Болдырев <[email protected]>, Michael Borokhovich <[email protected]>, "[email protected]" <[email protected]> Subject: Re: [vpp-dev] MPLS labels question On master branch the CLI has changed subtlety to allow one to specify multiple output-labels: 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-labels 222 333 note the change from ‘out-label’ to ‘out-labels’. In older versions passing multiple out-labels is only possible via the API. /neale From: <[email protected]> on behalf of Алексей Болдырев <[email protected]> Date: Monday, 14 August 2017 at 17:08 To: Michael Borokhovich <[email protected]>, "[email protected]" <[email protected]> Subject: Re: [vpp-dev] MPLS labels question А как можно навесить несколько меток на маршрут? 14.08.2017, 18:58, "Michael Borokhovich" <[email protected]>: 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 [email protected]<mailto:[email protected]> https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________ vpp-dev mailing list [email protected] https://lists.fd.io/mailman/listinfo/vpp-dev
