Hi Neale, Thank you for your reply. I was offline for sometime and could not track it.
We are using VL APIs to program into vpp and I see some error while programming mpls route into default mpls table: Params we pass are as below: mp->_vl_msg_id = htons (VL_API_MPLS_ROUTE_ADD_DEL); mp->context = context; mp->mr_is_multipath =1 ; mp->mr_is_add = fib.is_add; vl_api_mpls_route_add_del_t *mp; /* Allocated all memory and memseted logic ..... ... ... */ mp->mr_route.mr_eos= 1; //mp->mr_route.mr_eos_proto = htonl(0); mp->mr_route.mr_label = htonl(fib.local_label); mp->mr_route.mr_table_id = 0; // MPLS Table ID default is 0 mp->mr_route.mr_n_paths =1; mp->mr_route.mr_paths[0].table_id = ntohl(fib.vrf_id); mp->mr_route.mr_paths[0].type = ntohl(FIB_API_PATH_TYPE_NORMAL); if(fib.is_ipv4) mp->mr_route.mr_paths[0].proto = 0; else mp->mr_route.mr_paths[0].proto = 1; Output from show mpls fib: ==================== 16:eos/21 fib:0 index:174 locks:2 API refs:1 entry-flags:attached, src-flags:added,contributing,active, path-list:[192] locks:2 flags:shared, uPRF-list:212 len:1 itfs:[0, ] path:[300] pl-index:192 ip4 weight=1 pref=0 attached-nexthop: cfg-flags:attached, 1000:0:100:0:5e:3b3f:0:d0fe local0 [@0]: ipv4 via 0.0.208.254 local0: mtu:9000 next:17 flags:[] forwarding: mpls-eos-chain [@0]: dpo-load-balance: [proto:mpls index:177 buckets:1 uRPF:212 to:[0:0]] [0] [@0]: dpo-drop mpls My question is, fib_index is missing and also dpo-drop in forwarding action. What is wrong in params that we pass? vppctl is working fine. I see some gaps in API params filling. Your early reply is much appreciated. Thank you. With Regards Sastry
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20866): https://lists.fd.io/g/vpp-dev/message/20866 Mute This Topic: https://lists.fd.io/mt/87373182/21656 Mute #mpls:https://lists.fd.io/g/vpp-dev/mutehashtag/mpls Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
