Core dump:
root@server1-38:~# cat _usr_bin_vpp.0.crash
ProblemType: Crash
Architecture: amd64
Date: Thu Oct 17 11:15:11 2019
DistroRelease: Ubuntu 18.04
ExecutablePath: /usr/bin/vpp
ExecutableTimestamp: 1566409810
ProcCmdline: /usr/bin/vpp -c /etc/vpp/startup.conf
ProcCwd: /
ProcEnviron:
LANG=en_U
Hi Dear VPP guys,
I would like to do some investigation about AVX512 instruction
support in VPP, I saw there are already some implementations but AVX2 is still
the default option. Could anybody tell me how to enable AVX512 in VPP?
Appreciate for your kindly help in advance.
Rega
Hi Balaji,
I checked the docs and tried to set the handler engine. Since there’s no
example for the command, I’m not sure if I’m setting the right value for
‘cipher’ here. I tried with different values, but it just returns error msg
like this:
vpp# set crypto handler aes-128-cbc engine
failed t
Looking at the docs, I think you need to set one using the:
set crypto handler cipher [cipher2 cipher3 …] engine
Not sure, what’s the default behavior.
--
Regards,
Balaji.
From: on behalf of "Ying, Ruoyu"
Date: Thursday, October 17, 2019 at 6:03 PM
To: "Neale Ranns (nranns)" , "vpp-dev@lists.
Attaching the version information also. And I install VPP through apt.
vpp# sh version
vpp v19.08.1-release built by root on a0e0f3d06c53 at Wed Sep 18 18:14:09 UTC
2019
Best Regards,
Ruoyu
From: vpp-dev@lists.fd.io On Behalf Of Ying, Ruoyu
Sent: Friday, October 18, 2019 9:03 AM
To: nra...@cis
Hi Neale,
Thanks for replying. I think you’ve pointed out the root cause. The cmds
provides the response like this:
vpp# show crypto engine
No crypto engines registered
vpp# show ipsec backend
IPsec AH backends available:
Name Index Active
crypto engin
This looks like a DPDK issue, but I’ll let Damjan be the judge of that.
To see if this is a config issues, could you simplify your startup config by
- removing “workers 0” from the two nics and adding “num-rx-queues 2” to the
nics or to the default stanza, if you’re running with 2 workers
- comm
I tried disabling autoneg on R740 side. It is not allowed too. If vpp
cannot allow two nics to be successfully added to the same vpp instance, it
seems to be a bug. Is it something which can be easily spotted in the code
base?
It is also not possible to enforce symmetricity on internet. The other
If I only put one phy nic, i.e., eth0, to vpp, 'sh hardware' shows it is
up. If I put both eth0 and eth1 in vpp, eth0 is always down. It seems
something is wrong with the nic or vpp does not support this type of
hardware?
We tried enabling autoneg on R230. It is not allowed. To avoid asymmetric
se
It plays a role if it is asymmetric at both ends. You could enable it at both
ends and check.
On Oct 17, 2019, at 3:15 PM, Chuan Han wrote:
I rebooted the r230 machine and found the phy nic corresponding to eth has
autoneg off.
root@esdn-relay:~/gnxi/perf_testing/r230# ethtool enp6s0f1
Sett
When two interfaces are in the linux, ping works.
On R740, we have
root@esdn-lab:~/gnxi/perf_testing/r740/vpp# ip a s eno3
4: eno3: mtu 1500 qdisc mq state UP group
default qlen 1000
link/ether 24:6e:96:b4:b2:06 brd ff:ff:ff:ff:ff:ff
inet 10.10.10.11/24 scope global eno3
valid_lft
Hi Chuan,
As Balaji said, probably it’s worth making sure the cable between the eth0 nics
is fine and that eth0 on R230 works as expected. For instance, you could double
check your setup by switching to linux drivers and trying a ping between the
two boxes.
Regarding “sh int”, it only shows
Does vpp have some special requirements on nic types and cabling?
On Thu, Oct 17, 2019 at 3:08 PM Balaji Venkatraman (balajiv) <
bala...@cisco.com> wrote:
> Hi Chuan,
>
> I got the eth0 and eth1 mixed up. My bad.
>
> Are these fiber or copper links? You may want to check if the cable is ok.
> Als
I rebooted the r230 machine and found the phy nic corresponding to eth has
autoneg off.
root@esdn-relay:~/gnxi/perf_testing/r230# ethtool enp6s0f1
Settings for enp6s0f1:
Supported ports: [ FIBRE ]
Supported link modes: 1baseT/Full
Supported pause frame use: Symmetric
Hi Chuan,
I got the eth0 and eth1 mixed up. My bad.
Are these fiber or copper links? You may want to check if the cable is ok.
Also, please make sure you have crossover cable(if RJ) between the servers.
Thanks!
--
Regards,
Balaji.
From: Chuan Han
Date: Thursday, October 17, 2019 at 2:41 PM
To:
Restarting ixia controller does not help. We ended up with both ixia ports
having '!'.
We are not sure how ixia port plays a role here. eth0 interfaces are the
interfaces connecting two servers, not to ixia.
On Thu, Oct 17, 2019 at 11:26 AM Balaji Venkatraman (balajiv) <
bala...@cisco.com> wrote:
We are pleased to announce the Call for Participation for the FOSDEM
2020 Software Defined Networking devroom!
Important dates:
Nov 24th 2019 Submission deadline for talk proposals
Dec 15th 2019 Announcement of the final schedule
Feb 1st 2019 Software Defined Networking devroom
Hi Chuan,
Could you please try to reset the ixia controller connected to port 4?
I have seen issues with ‘!’ on ixia. Given the carrier on eth0 is down, I
suspect the ixia port.
--
Regards,
Balaji.
From: Chuan Han
Date: Thursday, October 17, 2019 at 11:09 AM
To: "Balaji Venkatraman (balajiv)"
Yes. It is unidirectional stream from port 1 to port 4.
Another engineer, Nambi, configured ixia. What he showed me yesterday is
that xia port connected to port 1 is green and good. ixia port connected to
port 4 is green but has a red exclamation mark, which means ping does not
work.
We also foun
*What:*
LF will be performing standard system maintenance and a Jenkins migration
* *Jenkins*
o Migrate to two new SSD volumes
o OS updates
o Jenkins upgrade to 2.190.1
o Plugin upgrades
* *Nexus *
o OS updates
o Nexus upgrade to 2.14.15-01
* *Jira *
Hi Chuan,
I assume u have unidirectional stream ? ixia->1->2->3->4->ixia?
vpp# sh int
Name IdxState MTU (L3/IP4/IP6/MPLS)
Counter Count
eth0 2 up 9000/0/0/0 rx packets
30925
On R230, we have the following. Not sure why eth0 is down. I used the same
setup for L3 routing measurement. Everything worked fine.
vpp# sh hardware-interfaces eth0
NameIdx Link Hardware
eth0 2down eth0
Link speed: unknown
Et
> On 17 Oct 2019, at 09:59, Chuan Han wrote:
>
> It seems R740 vpp works fine. All packets coming from port 1 go to port 2.
>
> vpp# sh int
> Name IdxState MTU (L3/IP4/IP6/MPLS)
> Counter Count
> eth0 2 up
That will work.
Looking into the fixup function, all that's used from the session is the
ergress interface. So only that needs to be 'pushed'. I suspect using the whole
session was a convenience for the orignal author, whoever that might have been
...
/neale
On 17/10/2019 18:38, "Benoit Gan
It seems R740 vpp works fine. All packets coming from port 1 go to port 2.
vpp# sh int
Name IdxState MTU (L3/IP4/IP6/MPLS)
Counter Count
eth0 2 up 9000/0/0/0 tx
packets 30895
> I think your analysis is spot on. Thank you!
> How you're a VPP PPPoE expert __ do you have some suggestions on a fix?
Shouldn't the usual solution of storing the index in the pool instead of the
pointer itself be enough?
Ie, use session_id as fixup_data, and use it in pppoe_fixup() to retrieve
Hi,
Currently we only support setting of local ips for builtin applications, like
the one you’ve built lower. VCL and the message queue api currently do not
support this.
I guess we could add a VPPCOM_ATTR_SET_LCL_ADDR set attribute option and pass
that over the api. But before that, could yo
Hi Raj,
I think your analysis is spot on. Thank you!
How you're a VPP PPPoE expert __ do you have some suggestions on a fix?
/neale
On 17/10/2019 16:18, "vpp-dev@lists.fd.io on behalf of Raj"
wrote:
Hello all,
I could do some more analysis of this issue and I think I have
i
In the Hoststack app, I use write the flowing function to set local addr to
connect remote socket server
>
> clib_error_t * vnet_connect_uri_with_local_addr(vlib_main_t *vm,
> vnet_connect_args_t
> *a, ip46_address_t *local_addr) { session_endpoint_cfg_t sep =
> SESSION_ENDPOINT_CFG_NULL; int r
Hello all,
I could do some more analysis of this issue and I think I have
identified what could be wrong here.
During pppoe session creation time frame, as we mentioned earlier, the
below function will get invoked from pppoe_update_adj()
adj_nbr_midchain_update_rewrite(adj_index_t
adj_index,adj_
Hi Ruoyo,
Possiblly because your loaded crypto engine/backend does not support the
requested algorithms. Please provide :
show crypto engine
show ipsec backend
also whenever asking for assistance:
sh version
Thanks,
neale
From: on behalf of "Ying, Ruoyu"
Date: Thursday 17 October 2019
All of the docs have moved to the main fd.io site: See
https://fd.io/documentation/ and more specifically
https://fd.io/docs/vpp/master/.
Eventually, one would expect that search results will improve. It's possible
that we could plant a "301 Moved Permanently" page on readthedocs.
I'll ask Joh
Hi Ruoyu,
Could you please post the ipsec error message on create?
SA create usually indicates an issue with hardware. You might want to try if
rebooting the instance resolves it?
--
Regards,
Balaji.
From: on behalf of "Ying, Ruoyu"
Date: Thursday, October 17, 2019 at 1:51 AM
To: "vpp-dev@lis
Hi,
I tried to use vpp to enable IPSec in my environment. And when I tried to
create a SA, I always got an error for that.
Detailed configs look like this:
Interface details:
vpp# show int
Name IdxState MTU
(L3/IP4/IP6/MPLS) Counter
Hi, I got VPP crashed when trying to add more nsh map.
My case is this:
client -> router1 (vpp, 192.168.1.34) -> node1 (vpp, 192.168.1.37) -> ...
-> node2 (vpp, 192.168.1.40) -> ...
node1/2 work as nodes of a nfv cluster, ,and router1 has two vxlan-gpe tunnels
with node1/2:
vpp# show vxlan-gpe
35 matches
Mail list logo
