Damjan is right. However, vpp is willing to start a binary API messages over 
sockets server.



With a strong warning that not every api works when vpp_api_test runs over 
sockets, here's how to make it play:



# vpp unix { interactive cli-listen /run/vpp/cli-vpp1.sock } api-segment { 
prefix vpp1 } socksvr { socket-name /run/vpp/api_1.sock }



and



# vpp_api_test socket-name /run/vpp/api_1.sock chroot prefix vpp1

# show_version



Or some such...



HTH... Dave



-----Original Message-----
From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Damjan Marion
Sent: Thursday, May 10, 2018 9:48 AM
To: Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) <pmi...@cisco.com>
Cc: vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] vpp_api_test via socket file





You cannot use  CLI socket with VAT. They are completely different things.



--

Damjan



> On 10 May 2018, at 14:58, Peter Mikus 
> <pmi...@cisco.com<mailto:pmi...@cisco.com>> wrote:

>

> Hello,

>

> I am trying to override api-segment prefix as well as override cli-listen 
> socket file [1].

> However I am not able to connect to VPP via vpp_api_test over the socket file.

>

> Is this expected behavior? How to connect to vpp via vpp_api_test over custom 
> socket file?

>

> I am aiming for controlling more than one VPP instance (that is why prefix) 
> via vpp_api_test. Is that possible?

>

> Thank you.

>

> My startup.conf

>

>     unix

>     {

>         cli-listen /run/vpp/cli-vpp1.sock

>         log /tmp/vpe.log

>         nodaemon

>     }

>     api-segment

>     {

>         prefix vpp1

>     }

>     cpu

>     {

>         corelist-workers 2

>         main-core 1

>     }

>     dpdk

>     {

>         dev 0000:07:00.0

>     }

>

> 1) Connecting to vppctl works:

>

> $ sudo vppctl -s /run/vpp/cli-vpp1.sock sh ver vpp v18.04-release

> built by root on f10ad4364e3e at Wed Apr 25 16:06:03 UTC 2018

>

>

> 2) Connecting to vpp_api_test does not work

>

> $ sudo vpp_api_test socket-name /run/vpp/cli-vpp1.sock

> clib_socket_init: connect (fd 3, '/run/vpp/cli-vpp1.sock'): Protocol

> wrong type for socket

> WARNING: socket connection failed

>

> [1] https://wiki.fd.io/view/VPP/Progressive_VPP_Tutorial

> [2]

> https://wiki.fd.io/view/VPP/Command-line_Arguments#.22api-trace.22_par

> ameters

>

> Peter Mikus

>

>








Reply via email to