Ed,
sudo vpp api-segment { prefix vpp1 } unix { cli-listen /run/vpp/cli.vpp1.sock }
+
vppctl -s /run/vpp/cli.vpp1.sock
works indeed, but then
sudo vpp api-segment { prefix vpp2 } unix { cli-listen /run/vpp/cli.vpp2.sock }
does not start.
But anyway I was able to run vpp in docker and don’t need this feature anymore.
Thanks,
Marek
From: Ed Warnicke [mailto:[email protected]]
Sent: 7 września 2017 15:39
To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)
<[email protected]>
Cc: Dave Wallace <[email protected]>; [email protected]
Subject: Re: [vpp-dev] Running CLI against named vpp instance
Marek,
I don't think you have a local issue. I think what is happening is that the
instructions for running multiple vpps has changed.
With the advent of the new C vppctl, which is using a different method:
sudo vpp api-segment { prefix vpp1 } unix { cli-listen /run/vpp/cli.vpp1.sock }
(In the example above I arbitrarily chose the cli-listen socket name... you can
pick whatever you want as long as its unique among the set of vpps you are
running).
Then to address it with vppctl you'd use:
vppctl -s /run/vpp/cli.vpp1.sock
essentially -s is replacing -p.
Please note, the above is based on Wallace's excellent description in this
thread, I have not yet tried it, and would be grateful if you would do so and
tell me if it works :)
Ed
On Thu, Sep 7, 2017 at 1:00 AM, Marek Gradzki -X (mgradzki - PANTHEON
TECHNOLOGIES at Cisco) <[email protected]<mailto:[email protected]>> wrote:
Dave, Ed
with 17.07 I was able to run two vpp instances and connect CLI to them as
described here:
https://wiki.fd.io/view/VPP/Progressive_VPP_Tutorial#Action:_Run_vpp
So one needed just to specify prefix when starting vpp and vppctl.
There was no need to do any other configuration changes.
With current master (both build locally or using most recent ub16 packages)
it does not work for me.
I also tired explicitly specifying cfg files with different sockets,
Api segments + corresponding vppctl parameters (-p, -s)
+ some combinations.
It is possible I have some local issue,
so I would be grateful if you could share config that works for you.
Thanks,
Marek
From: Dave Wallace [mailto:[email protected]<mailto:[email protected]>]
Sent: 6 września 2017 18:07
To: Ed Warnicke <[email protected]<mailto:[email protected]>>
Cc: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)
<[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>
Subject: Re: [vpp-dev] Running CLI against named vpp instance
Ed,
vppctl already has a command line arg (-s) which allows the user to specify a
specific socket pathname which must be the same as the "cli-listen <pathname>"
configuration in a given vpp instance. Adding a naming convention to both vpp
and vppctl is going to over-complicate the matter.
Thanks,
-daw-
On 09/06/2017 11:01 AM, Ed Warnicke wrote:
Dave,
I think we would need to be sure that different vpp instances have different
cli-listen socket files, and that vppctl has a mechanism to address them easily.
I'd suggest a pattern like
"unix { cli-listen /run/vpp.cli-${prefix}.sock"
and
vppctl -p ${prefix}
to be in line with current usage.
Ed
On Wed, Sep 6, 2017 at 7:50 AM, Dave Wallace
<[email protected]<mailto:[email protected]>> wrote:
Marek,
Please check the vpp startup configuration (/etc/vpp/startup.conf) to ensure
that "unix { cli-listen /run/vpp/cli.sock }" is present. This is the default
socket used by the 'c' implementation of vppctl.
I'm going to fix the error message to output the socket file name to make this
easier to debug.
Thanks,
-daw-
On 09/06/2017 05:55 AM, Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at
Cisco) wrote:
Dave,
please find replies inline.
From: Dave Wallace [mailto:[email protected]]
Sent: 5 września 2017 16:41
To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)
<[email protected]><mailto:[email protected]>;
[email protected]<mailto:[email protected]>
Subject: Re: [vpp-dev] Running CLI against named vpp instance
Marek,
What is the uid/gid of /dev/shm/vpe-api ?
root/vpp
Is the user a member of the vpp group?
yes
Does your VPP workspace include the patch c900ccc34 "Enabled gid vpp in
startup.conf to allow non-root vppctl access" ?
yes (I’ve built master with HEAD @ 809bc74, also tested corresponding package
from nexus)
Thanks,
-daw-
On 09/05/2017 06:08 AM, Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at
Cisco) wrote:
Hi,
I am having problems with running CLI against named vpp instance (g809bc74):
sudo vpp api-segment { prefix vpp0 }
sudo vppctl -p vpp0 show int
clib_socket_init: connect: Connection refused
But ps shows vpp process is running.
It worked with 17.07.
Is it no longer supported or I need some additional configuration?
Regards,
Marek
_______________________________________________
vpp-dev mailing list
[email protected]<mailto:[email protected]>
https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________
vpp-dev mailing list
[email protected]<mailto:[email protected]>
https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________
vpp-dev mailing list
[email protected]
https://lists.fd.io/mailman/listinfo/vpp-dev
