[vpp-dev] Rearrangement of graph nodes

Hi, >From this page https://wiki.fd.io/view/VPP/What_is_VPP%3F There is an option to create a plugin to rearrange graph nodes. I want to write a plugin that builds graph nodes from a file, for example graph.txt: dpdk-input-->ethernet-input->change-mac I would like to know from your opinion that

Re: [vpp-dev] FD.io Jenkins Maintenance: 2017-09-07 @ 0415 UTC (9:15am PDT)

Change is complete. The new nodes appear to be spinning up successfully. We'll be monitoring jobs throughout the day. Please report issues via IRC fdio-infra. Thank you, Vanessa On 09/07/2017 11:18 AM, Vanessa Valderrama wrote: > > Starting change now. > > > On 09/07/2017 10:51 AM, Vanessa

Re: [vpp-dev] FD.io Jenkins Maintenance: 2017-09-07 @ 0415 UTC (9:15am PDT)

Starting change now. On 09/07/2017 10:51 AM, Vanessa Valderrama wrote: > > What: > > LF is switching VPP jobs to use new Jenkins nodes with dedicated core > instances > > When: > > 2017-09-07 @ 0415 UTC (9:15am PDT) > > Impact: > > No restart is required for this change. Once the change is made

[vpp-dev] FD.io Jenkins Maintenance: 2017-09-07 @ 0415 UTC (9:15am PDT)

What: LF is switching VPP jobs to use new Jenkins nodes with dedicated core instances When: 2017-09-07 @ 0415 UTC (9:15am PDT) Impact: No restart is required for this change. Once the change is made new instances will spin up on the new nodes. Why: Various FD.io projects have been

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

Re: [vpp-dev] physmem rework patch

On 7 Sep 2017, at 14:46, Billy McFall > wrote: To test, do we need to change anything else with our setup, like remove 80-vpp.conf? yes, it should work even without that file. If I have HugePages_Total set to 8192 via grub, and 80-vpp.conf is

Re: [vpp-dev] physmem rework patch

To test, do we need to change anything else with our setup, like remove 80-vpp.conf? If I have HugePages_Total set to 8192 via grub, and 80-vpp.conf is set to the default of 1024, my system should stay at 8192 (provided there is enough free hugepages), correct? Thanks, Billy On Thu, Sep 7, 2017

Re: [vpp-dev] Query for IPSec support on VPP

Hi Mukesh, I think the problem is that we do not have fib entry for 1.1.1.1 network. I guess there are different ways to fix the issue, I did the following (already updated interface name to match your config): set ip arp GigabitEthernet0/8/0 2.2.2.254 be:ef:00:00:00:02 ip route add

[vpp-dev] physmem rework patch

Dear vpp-devers, As I mentioned on the last community call, there is patch which significantly changes the way how VPP is allocating wired memory, including the dpdk hugepages. Patch is available here and it is passing verify jobs: https://gerrit.fd.io/r/#/c/7701/ With this change, VPP is

Re: [vpp-dev] Query for IPSec support on VPP

Hi Sergio, Just to inform this issue is seen in tunnel mode on VPP core as well. That means issue is seen only on tunnel mode both with DPDK and w/o DPDK. Thanks Mukesh On 07/09/17, 2:35 PM, "Mukesh Yadav (mukyadav)" wrote: HI, I haven’t tested tunnel mode w/o

Re: [vpp-dev] Regarding vxlan_tool.py in SFC vNF

Hi Hongjun, Sometime back, we are discussing about VPP in the place of vxlan_tool.py. Now, I am able to load nsh-plugin in VPP 17.04. To simplify things, I put only one VM in SFC. I am trying to execute the following commands in the SFC VM, which were suggested by you sometime back: vppctl show

Re: [vpp-dev] Query for IPSec support on VPP

HI, I haven’t tested tunnel mode w/o DPDK. With transport mode, I see it works fine both with VPP core and DPDK and follows path post decryption dpdk-esp-decrypt -> dpdk-esp-decrypt-post ->ip4-input-> ip4-lookup-> ip4-local and further follow icmp path. I see this problem only with tunnel

Re: [vpp-dev] Query for IPSec support on VPP

Hi Mukesh, On 07/09/2017 08:48, Mukesh Yadav (mukyadav) wrote: HI Sergio, As I mentioned that transport mode is working now. Next I tried tunnel mode. Here I can see successfully packet decryption. But later inner packet gets dropped. Outer IPSec packet is like 172.28.128.4 ->

Re: [vpp-dev] Running CLI against named vpp instance

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.

Re: [vpp-dev] Query for IPSec support on VPP

HI Sergio, As I mentioned that transport mode is working now. Next I tried tunnel mode. Here I can see successfully packet decryption. But later inner packet gets dropped. Outer IPSec packet is like 172.28.128.4 -> 172.28.128.5 Inner packet is 1.1.1.1 -> 2.2.2.2 I have added 2.2.2.2 on same

Re: [vpp-dev] Running CLI against named vpp instance

Dave, my startup conf is the same as src/vpp/conf/startup.conf, cli-listen /run/vpp/cli.sock is present. Marek From: Dave Wallace [mailto:dwallac...@gmail.com] Sent: 6 września 2017 16:51 To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) ;