Hi nagp, A FIB walk that consumes 100% CPU is usually indicative of a cycle/loop in the FIB undirected graph. Cycles in routing should not form permanently, i.e. the routing protocols will eventually converge away from the loop, but they can form temporarily. Use; ‘sh fib walk’ to see the objects/nodes in the graph that are being visited in the walk. This will give you output like:
Brief History (last 128 walks): … [@6]: path-list:12 visits:1 duration:0.00 completed:85.06 sync, reason:evaluate, … you can then see in detail with; ‘sb fib <TYPE> <INSTANCE>’ e.g. ‘sh fib path-list 12’ ‘sh fib entry 19’ if no cycle exists let me know. If one does exist, please debug from the from a routing perspective. Regards, /neale From: <vpp-dev-boun...@lists.fd.io> on behalf of Nagaprabhanjan Bellaru <nagp.li...@gmail.com> Date: Monday, 10 April 2017 at 09:04 To: vpp-dev <vpp-dev@lists.fd.io> Subject: [vpp-dev] fib-walk is consuming 100% CPU.. There are a few routes in FIB, but fib-walk takes up 100% CPU. "show run" shows fib-wak process running perpetually. Is there anything that we can do to get around this? Thanks, -nagp
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
