Hi Justin,
Functionally, from your perspective, there’s no difference. They’re just two
options you have to exercise the debug cli. It’s up to you to decide which
works best for what you’re trying to achieve.
And 0 is just a shorthand for local host.
Florin
> On Oct 5, 2017, at 10:46 AM, Justin Iurman <justin.iur...@ulg.ac.be> wrote:
>
> Florin,
>
> Thanks for that. What's the difference between my technique and yours using
> telnet ? Also, what does the 0 correspond to ? Is it an instance index or
> something else ?
>
> Justin
>
>> Le 5 oct. 2017 à 17:23, Florin Coras <fcoras.li...@gmail.com> a écrit :
>>
>> Justin,
>>
>> That looks about right. The other option would be to use telnet. So instead
>> of
>> “cli-listen /run/vpp/cli.vpp1.sock” do something like “cli-listen
>> localhost:5002” and then telnet 0 5002
>>
>> Florin
>>
>>> On Oct 5, 2017, at 1:18 AM, Justin Iurman <justin.iur...@ulg.ac.be> wrote:
>>>
>>> Hi Florin,
>>>
>>> In fact, that's what I was already trying. Anyway, I found a way to make it
>>> work but I'm still not sure that's the right/best way to do so.
>>>
>>> # vpp1 instance
>>> sudo vpp unix { log /tmp/vpp1.log full-coredump cli-listen
>>> /run/vpp/cli.vpp1.sock } api-segment { prefix vpp1 } api-trace { on }
>>> plugins { plugin dpdk_plugin.so { disable } }
>>>
>>> # vpp2 instance
>>> sudo vpp unix { log /tmp/vpp2.log full-coredump cli-listen
>>> /run/vpp/cli.vpp2.sock } api-segment { prefix vpp2 } api-trace { on }
>>> plugins { plugin dpdk_plugin.so { disable } }
>>>
>>> # vppctl vpp1
>>> sudo vppctl -s /run/vpp/cli.vpp1.sock <cmd>
>>>
>>> # vppctl vpp2
>>> sudo vppctl -s /run/vpp/cli.vpp2.sock <cmd>
>>>
>>> Since I build a dynamic topology, I won't use startup config files. That's
>>> why i'm using parameters in command line. Commands above work good, as it
>>> mimics the behavior I had with VPP-lite. But again, is it the right/best
>>> way to do so ? Or would there be anything better suited ?
>>>
>>> Justin
>>>
>>> ----- Mail original -----
>>> De: "Florin Coras" <fcoras.li...@gmail.com>
>>> À: "Justin Iurman" <justin.iur...@ulg.ac.be>
>>> Cc: vpp-dev@lists.fd.io
>>> Envoyé: Mercredi 4 Octobre 2017 18:32:27
>>> Objet: Re: [vpp-dev] Running multiple instances of VPP as it was allowed
>>> with VPP-lite
>>>
>>> Hi Justin,
>>>
>>> Try api-segment {prefix <fill-in-name>}
>>>
>>> Florin
>>>
>>>> On Oct 4, 2017, at 9:23 AM, Justin Iurman <justin.iur...@ulg.ac.be> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> Is it still possible to run multiple instances of VPP, just like it was
>>>> done with VPP-lite (see here:
>>>> https://wiki.fd.io/view/VPP/Progressive_VPP_Tutorial) before merging it ?
>>>>
>>>> Actually, my problem is the following. I need to run several instances of
>>>> VPP (eg. vpp1, vpp2, vpp3, etc) to simulate a topology. But, for some
>>>> reason, I'm not able to make it work as expected. I've already disabled
>>>> DPDK plugin to run in "lite" mode. Could it be a configuration issue ? VPP
>>>> startup.conf:
>>>>
>>>> unix {
>>>> nodaemon
>>>> log /tmp/vpp.log
>>>> full-coredump
>>>> cli-listen /run/vpp/cli.sock
>>>> gid vpp
>>>> }
>>>>
>>>> api-trace {
>>>> on
>>>> }
>>>>
>>>> api-segment {
>>>> gid vpp
>>>> }
>>>>
>>>> plugins {
>>>> plugin dpdk_plugin.so { disable }
>>>> }
>>>>
>>>> I tried to compare both VPP and VPP-lite. A first observation showed that
>>>> VPP is installed as a service, which is not the case for VPP-lite. I've
>>>> also compared both config files. Here is VPP-lite startup.conf:
>>>>
>>>> unix {
>>>> nodaemon
>>>> log /tmp/vpp.log
>>>> full-coredump
>>>> }
>>>>
>>>> api-trace {
>>>> on
>>>> }
>>>>
>>>> api-segment {
>>>> gid vpp
>>>> }
>>>>
>>>> Currently, here is how I try to mimic VPP-lite behavior with VPP:
>>>>
>>>> sudo vpp api-segment { prefix vpp1 } unix { cli-listen
>>>> /run/vpp/cli.vpp1.sock }
>>>> sudo vppctl -s /run/vpp/cli.vpp1.sock
>>>>
>>>> It works for one instance, but not for more, even if it does not throw any
>>>> error. Do you have any idea on how to proceed or what is wrong here ?
>>>>
>>>> Thanks !
>>>>
>>>> Justin
>>>> _______________________________________________
>>>> 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
