Swarup, LISP-GPE has its own CLI to enable/disable which until now [1] returned status 0 even if no input was provided. Therefore, the CLI parser, after finishing executing the first command, actually tried to execute lisp_gpe_enable_disable_command_fn and returned successfully.
Should be fixed now. Thanks, Florin [1] https://gerrit.fd.io/r/#/c/9694/ <https://gerrit.fd.io/r/#/c/9694/> > On Dec 1, 2017, at 11:21 AM, swarup <swarupn...@gmail.com> wrote: > > Hi, > > Some strange behavior with the word "gpe". We can add this word at the end of > many commands, it'll not throw any parsing error, but add anything else it'll > give parsing error. > > Some example: > > vpp# show vxlan tunnel ? > show vxlan tunnel show vxlan tunnel > vpp# show vxlan tunnel gpe ---> No parse error > No vxlan tunnels configured... > vpp# show vxlan tunnel abc > No vxlan tunnels configured... > unknown input `abc' ---> parse error > vpp# > vpp# show oam > Fib Src Dst Last Heard State > vpp# show oam gpe ---> No parse error > Fib Src Dst Last Heard State > vpp# show oam ? > show oam show oam > vpp# show oam abc > Fib Src Dst Last Heard State > unknown input `abc' ---> parse error > vpp#vpp# show one statistics details > No statistics found. > vpp# show one statistics details gpe > No statistics found. > vpp# show one statistics details abc > No statistics found. > unknown input `abc' > vpp# show one statistics details vxlan > No statistics found. > unknown input `vxlan' > vpp# > > Sorry if this is not a problem at all.. > > Regards, > > Swarup > > _______________________________________________ > vpp-dev mailing list > vpp-dev@lists.fd.io > https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
