Hi All,
I have a query regarding neos mpls fib entry for tunnel interface. I have
observed when we create mpls fib entry with neos bit set for tunnel label
it always sets forwarding as drop ("dpo-drop mpls"). For the eos bit the
issue is not seen the forwarding is set correctly.
Is this expected to have neos mpls fib entry created as drop for mpls
tunnel interface. Is this due to any reason. I am checking on a use case in
which I have to set the tunnel label with both neos and eos fib bit entry
for the lookup and forwarding .
Logs:
CLI:
"mpls local-label add 51999 via l2-input-on mpls-tunnel0"
MPLS FIB:
*51999:neos/21 fib:0 index:35 locks:2*
CLI refs:1 entry-flags:attached, src-flags:added,contributing,active,
path-list:[30] locks:4 flags:shared, uPRF-list:27 len:0 itfs:[]
path:[34] pl-index:30 ethernet weight=1 pref=0 intf-rx:
oper-flags:resolved, cfg-flags:interface-rx,
[@0]: mpls-tunnel0-rx-dpo: ethernet
*forwarding: mpls-neos-chain >>>> NEOS*
* [@0]: dpo-load-balance: [proto:mpls index:40 buckets:1 uRPF:27 to:[0:0]]*
* [0] [@0]: dpo-drop mpls >>>> DROP*
*51999:eos/21 fib:0 index:24 locks:2*
API refs:1 entry-flags:attached, src-flags:added,contributing,active,
path-list:[30] locks:4 flags:shared, uPRF-list:27 len:0 itfs:[]
path:[34] pl-index:30 ethernet weight=1 pref=0 intf-rx:
oper-flags:resolved, cfg-flags:interface-rx,
[@0]: mpls-tunnel0-rx-dpo: ethernet
* forwarding: mpls-eos-chain >>>>>> EOS*
*[@0]: dpo-load-balance: [proto:mpls index:26 buckets:1 uRPF:27
to:[34:1700]]*
* [0] [@6]: mpls-tunnel0-rx-dpo: ethernet >>>> VALID*
Thanks & Regards,
Sreejith
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21821): https://lists.fd.io/g/vpp-dev/message/21821
Mute This Topic: https://lists.fd.io/mt/93241741/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
