[vpp-dev] Error when trying to test ipsec gre, and packet can not be decrypted.

2018-01-31 Thread 唐伟

Hi guys,

My configuration about ipsec gre is shown below:
Vpp1:
create host-interface name eth2 mac 00:0c:29:f2:15:8b
set interface state host-eth2 up
set interface ip address host-eth2 10.0.0.1/24
create host-interface name eth1 mac 00:0c:29:f2:15:81
set interface state host-eth1 up
set interface ip address host-eth1 20.0.0.1/24
ipsec sa add 10 spi 1001 esp crypto-alg aes-cbc-128 crypto-key 
4a506a794f574265564551694d653768 integ-alg sha1-96 integ-key 
4339314b55523947594d6d3547666b45764e6a58
ipsec sa add 20 spi 1002 esp crypto-alg aes-cbc-128 crypto-key 
5a506a794f574265564551694d653768 integ-alg sha1-96 integ-key 
5339314b55523947594d6d3547666b45764e6a58
create ipsec gre tunnel src 10.0.0.1 dst 10.0.0.2 local-sa 10 remote-sa 20
set interface ip address ipsec-gre0 100.1.1.1/24
set interface state ipsec-gre0 up
ip route add 21.0.0.2/24 via ip4-address 100.1.1.2 interface ipsec-gre0 

vpp2:
create host-interface name eth2 mac 00:0c:29:e0:87:dd 
set interface state host-eth2 up
set interface ip address host-eth2 10.0.0.2/24
create host-interface name eth3 mac 00:0c:29:e0:87:e7
set interface state host-eth3 up
set interface ip address host-eth3 21.0.0.2/24
ipsec sa add 10 spi 1001 esp crypto-alg aes-cbc-128 crypto-key 
4a506a794f574265564551694d653768 integ-alg sha1-96 integ-key 
4339314b55523947594d6d3547666b45764e6a58
ipsec sa add 20 spi 1002 esp crypto-alg aes-cbc-128 crypto-key 
5a506a794f574265564551694d653768 integ-alg sha1-96 integ-key 
5339314b55523947594d6d3547666b45764e6a58
create ipsec gre tunnel src 10.0.0.2 dst 10.0.0.1 local-sa 20 remote-sa 10
set interface ip address ipsec-gre0 100.1.1.2/24
set interface state ipsec-gre0 up
ip route add 20.0.0.1/24 via ip4-address 100.1.1.1 interface ipsec-gre0


The trace:

Packet 3

00:03:19:325858: af-packet-input
  af_packet: hw_if_index 1 next-index 4
tpacket2_hdr:
  status 0x2001 len 166 snaplen 166 mac 66 net 80
  sec 0x5a72b5ef nsec 0x1a6aa25c vlan 0
00:03:19:325878: ethernet-input
  IP4: 00:0c:29:e0:87:dd -> 00:0c:29:f2:15:8b
00:03:19:325894: ip4-input
  IPSEC_ESP: 10.0.0.2 -> 10.0.0.1
tos 0x00, ttl 253, length 152, checksum 0xa931
fragment id 0x
00:03:19:325899: ip4-lookup
  fib 0 dpo-idx 6 flow hash: 0x
  IPSEC_ESP: 10.0.0.2 -> 10.0.0.1
tos 0x00, ttl 253, length 152, checksum 0xa931
fragment id 0x
00:03:19:325909: ip4-local
IPSEC_ESP: 10.0.0.2 -> 10.0.0.1 

   
  tos 0x00, ttl 253, length 152, checksum 0xa931
  fragment id 0x
00:03:19:325913: ip4-punt
IPSEC_ESP: 10.0.0.2 -> 10.0.0.1
  tos 0x00, ttl 253, length 152, checksum 0xa931
  fragment id 0x
00:03:19:325920: error-punt
  ip4-input: unknown ip protocol

Packet 4

  
 How can I solve the problem?
 
 Thanks,
 Wtang


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] adding large number of route prefixes

2018-01-31 Thread Konrad Gutkowski

Hi,

While testing ipv4 routing I found that vpp crashes when supplied with  
large sets of prefixes, the exact point when vpp goes down changes  
depending on prefix set and vpp version tested.


Tried 17.10 and 18.01, first consistently crashes at around 1m (though  
tested only with sequential /24 and /32 prefixes), for the latter it  
depends on the set, for sequential it's around 390k, while public bgp  
table does crash pretty randomly around 100-300k, (my file has around 750k  
routes).


For 17.10, adding less than 1m prefixes works for both scenarios and  
continues working - adding and deleting it multiple times does not cause  
any stability issues.

It doesn't seem dependent on heap-size parameter value.

I used both cli "ip route add count" as well as modified router plugin to  
pull the table from netlink.

Any suggestions are welcome.

--
Konrad Gutkowski
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev


Re: [vpp-dev] VXLAN Tunnel IF Names

2018-01-31 Thread John Lo (loj)
Hi Jon,

All VPP tunnel creation uses the mechanism of returning a sw_if_index of the 
created tunnel. The name of the tunnel is then followed by a number being the 
instance or index to the tunnel struct vector. Thus, the first VXLAN tunnel 
created is called vxlan_tunnel0 followed by vxlan_tunnel1, etc. The number is 
incrementing unless tunnels are deleted and created again where a newly created 
tunnel will reuse the last deleted tunnel, hence its name. If all previously 
deleted tunnels are used up, then the tunnel name number will start 
incrementing again.  I am not sure if it is feasible to follow this behavior to 
“predict” tunnel name.

BTW, GRE tunnels are created and named the same way. You added TEB (transparent 
ethernet bridging) support to GRE. Have you not been using it and bothered by 
how to predict name of created GRE tunnels?

It is not a good idea to tie tunnel name to VNI as it is not a unique ID to 
identify VXLAN tunnels. It is quite common for existence of multiple VXLAN 
tunnels with the same VNI with different remote end point IP addresses. A 
bridge domain (BD) may have multiple VXLAN tunnels with the same VNI to several 
remote servers where the same overlay network exist. It is quite common to use 
the ID for BD or VLAN as the VNI for all its VXLAN tunnels to make it easier to 
track their usage.

I suppose it is feasible to provide another set of VXLAN tunnel create/delete 
API to allow caller to specify instance or number of the tunnel, similar to 
what you did for loopback interface.  One complication for the new API is that, 
upon VXLAN tunnel deletion, the interface created for the tunnel is not really 
deleted by the current code but put into a reuse pool. When more tunnels are 
created, any interface from reuse pool with its existing interface name will be 
used for the new tunnel, before new interfaces are created. If a interface is 
reused upon tunnel creation, its interface name may not match the specified 
tunnel instance/number of the new tunnel creation API.  One way to overcome 
this may be to not keep interface in reused pool on tunnel deletion. Thus, 
tunnel creation would always create new interface.  For backward compatibility, 
I suppose we can keep the tunnel create/delete API as is so interfaces of 
deleted tunnels are kept for reuse. The new API will then always create/delete 
interface on tunnel create/delete.  This would put a restriction that user 
should not mix the usage of new or old APIs.

Regards,
John

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Jon Loeliger
Sent: Wednesday, January 31, 2018 3:13 PM
To: vpp-dev 
Subject: [vpp-dev] VXLAN Tunnel IF Names

Hey Developers,

I've turned my attention to the wondrous world of VXLANs!
And with that, I stare into the Vast VXLAN API Abyss...

My first question, as usual, involves the SW IF that is created
by the vxlan tunnel create API call.   The IF has a name that
is once-again unknowable by the User who creates the tunnel
unless direct inspection takes place.

Can we somehow invert the naming responsibility here so that
the API states either the name or the unique integer used to
form the the SW IF tunnel name?  Or perhaps it can be formed
using the VNI number?

Inspecting the reply return value isn't good enough; we need to
be able to know, in advance, what the tunnel SW IF name will be.
This is, again, the same naming problem we've had in the past
with Loopback IFs, bridges, and recently memif socket names.

If directly using the VNI won't work, I can work up a patch to
allow user numbering in the style of, say, bridges, if that would
be helpful.

Thanks,
jdl

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] VXLAN Tunnel IF Names

2018-01-31 Thread Jon Loeliger
Hey Developers,

I've turned my attention to the wondrous world of VXLANs!
And with that, I stare into the Vast VXLAN API Abyss...

My first question, as usual, involves the SW IF that is created
by the vxlan tunnel create API call.   The IF has a name that
is once-again unknowable by the User who creates the tunnel
unless direct inspection takes place.

Can we somehow invert the naming responsibility here so that
the API states either the name or the unique integer used to
form the the SW IF tunnel name?  Or perhaps it can be formed
using the VNI number?

Inspecting the reply return value isn't good enough; we need to
be able to know, in advance, what the tunnel SW IF name will be.
This is, again, the same naming problem we've had in the past
with Loopback IFs, bridges, and recently memif socket names.

If directly using the VNI won't work, I can work up a patch to
allow user numbering in the style of, say, bridges, if that would
be helpful.

Thanks,
jdl
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP FD in a linux epoll

2018-01-31 Thread Shashi Kant Singh
Thanks for the clarification !!

From: Florin Coras [mailto:fcoras.li...@gmail.com]
Sent: 31 January 2018 21:51
To: Shashi Kant Singh
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP FD in a linux epoll

Shashi,

No. VCL session ids are not valid Linux fds.

Florin



On Jan 31, 2018, at 3:21 AM, Shashi Kant Singh 
> wrote:

Hi

I have created VPP session and the UDP FD for the same in my client program.

Would it ok to add this FD in a unix epoll (instead of vppcom_epoll_wait) 
already running a thread?

Regards
Shashi

___
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

Re: [vpp-dev] VPP FD in a linux epoll

2018-01-31 Thread Florin Coras
Shashi, 

No. VCL session ids are not valid Linux fds. 

Florin


> On Jan 31, 2018, at 3:21 AM, Shashi Kant Singh  wrote:
> 
> Hi
>  
> I have created VPP session and the UDP FD for the same in my client program.
>  
> Would it ok to add this FD in a unix epoll (instead of vppcom_epoll_wait) 
> already running a thread?
>  
> Regards
> Shashi
>  
> ___
> 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

Re: [vpp-dev] Error when trying to add interface to vpp on ARM server.

2018-01-31 Thread Damjan Marion (damarion)

On 31 Jan 2018, at 10:34, adarsh m via vpp-dev 
> wrote:

Hi,

Pls check i am trying to bring up vpp with interface on ARM server but facing 
issue while doing so,

pls let me know if there is any existing issue or method to correct this issue.


ubuntu@vasily:~$ sudo service vpp status
[sudo] password for ubuntu:
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: enab
   Active: active (running) since Mon 2018-01-29 22:07:02 CST; 19h ago
  Process: 2461 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, status
  Process: 2453 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm /dev/shm/
 Main PID: 2472 (vpp_main)
   CGroup: /system.slice/vpp.service
   └─2472 /usr/bin/vpp -c /etc/vpp/startup.conf

Jan 29 22:07:05 vasily vnet[2472]: dpdk_pool_create: failed to create dpdk_mbuf_
Jan 29 22:07:05 vasily vnet[2472]: dpdk_buffer_pool_create:573: WARNING: Failed
Jan 29 22:07:05 vasily vnet[2472]: unix_physmem_region_iommu_register: ioctl (VF
Jan 29 22:07:05 vasily vnet[2472]: dpdk_pool_create: failed to create dpdk_mbuf_
Jan 29 22:07:05 vasily vnet[2472]: dpdk_buffer_pool_create:573: WARNING: Failed
Jan 29 22:07:05 vasily vnet[2472]: unix_physmem_region_iommu_register: ioctl (VF
Jan 29 22:07:05 vasily vnet[2472]: dpdk_pool_create: failed to create dpdk_mbuf_
Jan 29 22:07:05 vasily vnet[2472]: dpdk_buffer_pool_create:573: WARNING: Failed
Jan 29 22:07:05 vasily vnet[2472]: dpdk_ipsec_process:1011: not enough DPDK cryp
Jan 29 22:07:05 vasily vnet[2472]: dpdk_lib_init:221: DPDK drivers found no port


Looks like hugepages issue. can you show full log? What you pasted above is 
truncated...

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] How to get dns server of dhcp client interface

2018-01-31 Thread Dave Barach (dbarach)
Option 6 (dhcp server) parsing is not implemented. See 
…/src/vnet/dhcp/client.c, switch statement near line 112…

Should be a simple coding task. Feel free to submit a patch.

Worst-case, file a Jira ticket so we don’t forget about it.

Thanks… Dave

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of ???
Sent: Tuesday, January 30, 2018 7:58 PM
To: vpp-dev 
Subject: [vpp-dev] How to get dns server of dhcp client interface

Hi,vpp-dev team,
When I use dhcp client to get a wan ip address for vpp interface,How to get the 
dns server address?
sudo vppctl set dhcp client intfc GigabitEthernet0/a/0
vagrant@localhost:~$ sudo vppctl show dhcp client
[0] GigabitEthernet0/a/0 state DHCP_BOUND addr 10.180.30.193/24 gw 10.180.30.1

Thanks.


Regards,
Jzhchen


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] Error when trying to add interface to vpp on ARM server.

2018-01-31 Thread adarsh m via vpp-dev
Hi,
Pls check i am trying to bring up vpp with interface on ARM server but facing 
issue while doing so,
pls let me know if there is any existing issue or method to correct this issue.

ubuntu@vasily:~$ sudo service vpp status
[sudo] password for ubuntu: 
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: enab
   Active: active (running) since Mon 2018-01-29 22:07:02 CST; 19h ago
  Process: 2461 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, status
  Process: 2453 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm /dev/shm/
 Main PID: 2472 (vpp_main)
   CGroup: /system.slice/vpp.service
   └─2472 /usr/bin/vpp -c /etc/vpp/startup.conf

Jan 29 22:07:05 vasily vnet[2472]: dpdk_pool_create: failed to create dpdk_mbuf_
Jan 29 22:07:05 vasily vnet[2472]: dpdk_buffer_pool_create:573: WARNING: Failed 
Jan 29 22:07:05 vasily vnet[2472]: unix_physmem_region_iommu_register: ioctl (VF
Jan 29 22:07:05 vasily vnet[2472]: dpdk_pool_create: failed to create dpdk_mbuf_
Jan 29 22:07:05 vasily vnet[2472]: dpdk_buffer_pool_create:573: WARNING: Failed 
Jan 29 22:07:05 vasily vnet[2472]: unix_physmem_region_iommu_register: ioctl (VF
Jan 29 22:07:05 vasily vnet[2472]: dpdk_pool_create: failed to create dpdk_mbuf_
Jan 29 22:07:05 vasily vnet[2472]: dpdk_buffer_pool_create:573: WARNING: Failed 
Jan 29 22:07:05 vasily vnet[2472]: dpdk_ipsec_process:1011: not enough DPDK cryp
Jan 29 22:07:05 vasily vnet[2472]: dpdk_lib_init:221: DPDK drivers found no port

Thnaks,Regards,Adarsh M.

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] How to get dns server of dhcp client interface

2018-01-31 Thread 陈敬志
Hi,vpp-dev team,
When I use dhcp client to get a wan ip address for vpp interface,How to get the 
dns server address?
sudo vppctl set dhcp client intfc GigabitEthernet0/a/0
vagrant@localhost:~$ sudo vppctl show dhcp client 
[0] GigabitEthernet0/a/0 state DHCP_BOUND addr 10.180.30.193/24 gw 10.180.30.1

Thanks.


Regards,
Jzhchen

 
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] VPP FD in a linux epoll

2018-01-31 Thread Shashi Kant Singh
Hi

I have created VPP session and the UDP FD for the same in my client program.

Would it ok to add this FD in a unix epoll (instead of vppcom_epoll_wait) 
already running a thread?

Regards
Shashi

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [csit-dev] adding interface to vpp

2018-01-31 Thread Gabriel Ganne
I'm forwarding this to vpp-dev as I think this is a vpp/dpdk question more than 
a csit one.


--

Gabriel Ganne


From: csit-dev-boun...@lists.fd.io  on behalf of 
adarsh m via csit-dev 
Sent: Tuesday, January 30, 2018 2:42:46 PM
To: csit-...@lists.fd.io
Subject: Re: [csit-dev] adding interface to vpp


Hi,

I fixed the issue of adding the vendor_id and device_id in the init.c but still 
the interface is not showing in VPP.

Error after fixing :
---
root1@root1-CN21UPSA:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Tue 2018-01-30 15:18:18 IST; 1min 34s ago
  Process: 12206 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 12202 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 12210 (vpp_main)
   CGroup: /system.slice/vpp.service
   └─12210 /usr/bin/vpp -c /etc/vpp/startup.conf

Jan 30 15:18:18 root1-CN21UPSA /usr/bin/vpp[12210]: load_one_plugin:63: Loaded 
plugin: /usr/lib/vpp_api_test_plugins/gtpu_test_plugin.so
Jan 30 15:18:18 root1-CN21UPSA /usr/bin/vpp[12210]: load_one_plugin:63: Loaded 
plugin: /usr/lib/vpp_api_test_plugins/ioam_pot_test_plugin.so
Jan 30 15:18:18 root1-CN21UPSA vpp[12210]: /usr/bin/vpp[12210]: 
dpdk_config:1243: EAL init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages 
--file-prefix vpp -w :0b:00.1 --master-lcore 0 --socket-mem 102
Jan 30 15:18:18 root1-CN21UPSA /usr/bin/vpp[12210]: dpdk_config:1243: EAL init 
args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w :0b:00.1 
--master-lcore 0 --socket-mem 1024
Jan 30 15:18:18 root1-CN21UPSA vpp[12210]: EAL: No free hugepages reported in 
hugepages-1048576kB
Jan 30 15:18:18 root1-CN21UPSA vpp[12210]: EAL: VFIO support initialized
Jan 30 15:18:18 root1-CN21UPSA vnet[12210]: EAL: VFIO support initialized
Jan 30 15:18:18 root1-CN21UPSA vnet[12210]: unix_physmem_region_iommu_register: 
ioctl (VFIO_IOMMU_MAP_DMA): Invalid argument
Jan 30 15:18:18 root1-CN21UPSA vnet[12210]: dpdk_ipsec_process:1011: not enough 
DPDK crypto resources, default to OpenSSL
Jan 30 15:18:18 root1-CN21UPSA vnet[12210]: dpdk_lib_init:221: DPDK drivers 
found no ports...

root1@root1-CN21UPSA:~$ sudo vppctl show interface
  Name   Idx   State  Counter  Count
local00down
root1@root1-CN21UPSA:~$

---

As per 
http://dpdk.org/doc/quick-start
1> I Extracted the dpdk
2> Enabled pcap (libpcap headers are required).
3> Built libraries and test application (Linux headers may be needed with 
default config).
4> Reserved huge pages memory.
but since the hardware isnt accessible to me i wasn't able to test by running 
poll-mode driver

But after doing this when i start the vpp it'll stay active for a moment and 
stop immediately.

Log :
--
root1@root1-CN21UPSA:~$ sudo service vpp start
root1@root1-CN21UPSA:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: active (running) since Tue 2018-01-30 19:10:09 IST; 6ms ago
  Process: 22689 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
  Process: 22704 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited, 
status=0/SUCCESS)
  Process: 22701 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm 
/dev/shm/vpe-api (code=exited, status=0/SUCCESS)
 Main PID: 22708 (vpp)
   CGroup: /system.slice/vpp.service
   └─22708 /usr/bin/vpp -c /etc/vpp/startup.conf

Jan 30 19:10:09 root1-CN21UPSA systemd[1]: Starting vector packet processing 
engine...
Jan 30 19:10:09 root1-CN21UPSA systemd[1]: Started vector packet processing 
engine.
Jan 30 19:10:09 root1-CN21UPSA vpp[22708]: vlib_plugin_early_init:356: plugin 
path /usr/lib/vpp_plugins
Jan 30 19:10:09 root1-CN21UPSA vpp[22708]: load_one_plugin:184: Loaded plugin: 
acl_plugin.so (Access Control Lists)
root1@root1-CN21UPSA:~$
root1@root1-CN21UPSA:~$ sudo service vpp status
● vpp.service - vector packet processing engine
   Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor preset: 
enabled)
   Active: 

[vpp-dev] vpp io threads

2018-01-31 Thread Shiv Dev
 Hi Team,

  I am trying to see how to distribute traffic between multiple
worker threads
in the absence of RSS. I believe there are I/O threads for handling input
and and dispatching to worker threads.

src/vlib/threads.c: "  /* Initial barrier sync, for both worker and
i/o
threads */

Is there any documentation for I/O threads and binding them to interfaces ?

Regards,
Shiv
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP Crash in stress test when configuring stateful ACL

2018-01-31 Thread Andrew Yourtchenko
Hi Rubina,

Thanks for reporting ! Which version are you on ?

Could you unicast me a decoded traceback from the core file ?

Thanks a lot!

--a

> On 30 Jan 2018, at 09:10, Rubina Bianchi  wrote:
> 
> Hi
> 
> I run a stress test on stateful VPP. After a while it crash and raise an os 
> panic signal.
> I run this test on both single and multicore vpp and every time it happens.
> 
> My Scenario:
> 
> 1.
> VPP:
> Default startup.conf configuration (main and worker on same core)
> Session timeouts are configured as follows:
> vppctl set acl-plugin session timeout udp idle 5
> vppctl set acl-plugin session timeout tcp idle 10
> vppctl set acl-plugin session timeout tcp transient 5
> 2 interface in brdige mode
> add permit + reflect acl rule on both Input & Output of all interfaces
> Trex:
> ./t-rex-64 -f cap2/my_custom_test.yaml --cfg 
> cfg/concurrent_connection_trex_config.yaml -c 8 -m 3000
> 
> 2.
> VPP:
> 1 main core + 1 worker core
> Session timeouts are configured as follows:
> vppctl set acl-plugin session timeout udp idle 5
> vppctl set acl-plugin session timeout tcp idle 10
> vppctl set acl-plugin session timeout tcp transient 5
> 2 interface in brdige mode
> add permit + reflect acl rule on both Input & Output of all interfaces
> Trex:
> ./t-rex-64 -f cap2/my_custom_test.yaml --cfg 
> cfg/concurrent_connection_trex_config.yaml -c 8 -m 3000
> 
> 
> 3.
> VPP:
> 1 main core + 4 worker core
> Session timeouts are configured as follows:
> vppctl set acl-plugin session timeout udp idle 5
> vppctl set acl-plugin session timeout tcp idle 10
> vppctl set acl-plugin session timeout tcp transient 5
> 2 interface in brdige mode
> add permit + reflect acl rule on both Input & Output of all interfaces
> Trex:
> ./t-rex-64 -f cap2/my_custom_test.yaml --cfg 
> cfg/concurrent_connection_trex_config.yaml -c 8 -m 3000
> 
> I also attached my Trex yaml and config files.
> 
> Sent from Outlook
> 
> 
> 
> ___
> 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