Hi Mukesh,
On 30/08/2017 17:41, Mukesh Yadav (mukyadav) wrote:
HI Sergio,
I haven’t done any extra config besides mentioned in two scenario.
1.
dpdk {
socket-mem 1024,1024
num-mbufs 131072
dev 0000:00:08.0
}
/usr/bin/vpp[3844]: dpdk_ipsec_process:239: not enough Cryptodevs, default to
OpenSSL IPsec
2.
dpdk {
socket-mem 1024,1024
num-mbufs 131072
dev 0000:00:08.0
vdev cryptodev_aesni_mb_pmd,socket_id=1
vdev cryptodev_aesni_mb_pmd,socket_id=1
}
I reckon it could be another missed bit in the documentation regarding
the configuration. If Using DPDK 17.08 you might have to do something
like the following instead:
dpdk {
socket-mem 1024,1024
num-mbufs 131072
dev 0000:00:08.0
vdev crypto_aesni_mb0
vdev crypto_aesni_mb1
}
You should set the startup.conf to suit your needs depending on the
numbers of cores to use, the socket (numa node) you are running VPP on, etc.
That is just to say that you are probably fine with default VPP values
for socket-mem and num-mbufs.
Thanks,
Sergio
CRYPTODEV: [crypto_aesni_mb] cryptodev_aesni_mb_create() line 704: failed to
create cryptodev vdev
CRYPTODEV: [crypto_aesni_mb] cryptodev_aesni_mb_create() line 746: driver
cryptodev_aesni_mb_pmd: cryptodev_aesni_create failed
EAL: failed to initialize cryptodev_aesni_mb_pmd device
I am not aware of significance of various paramters mentioned above. Just
trying from reading DPDK documentation.
Will be helpful if you can point me some sample config for DPDK IPSec or any
link which shall have these pointers.
Thanks
Mukesh
On 30/08/17, 9:14 PM, "Sergio Gonzalez Monroy"
<sergio.gonzalez.mon...@intel.com> wrote:
I was just reproducing your steps.
Check that you have created a 'vdev crypto_aeasni_mb0' in
/etc/vpp/startup.conf inside the 'dpdk' section.
Then to check if you have support, you can run:
vppctl show crypto device mapping verbose
Thanks,
Sergio
On 30/08/2017 13:07, Mukesh Yadav (mukyadav) wrote:
>
> HI Sergio,
>
> I am using VPP version 17.10
>
> vpp# show ver
>
> vpp v17.10-rc0~103-g42e6b09 built by vagrant on localhost at Sun Aug
> 27 22:06:20 PDT 2017
>
> I am cloned vpp on my mac machine using below command
>
> git clone https://gerrit.fd.io/r/vpp
>
> Then I have ran vagrant up/vagrant ssh
>
> Referred:
>
https://wiki.fd.io/view/VPP/Pulling,_Building,_Running,_Hacking_and_Pushing_VPP_Code
>
> On vagrant ssh, I have started vpp service.
>
> Note: I have ran scenario mentioned on below links properly.
>
> https://wiki.fd.io/view/VPP/IPSec_and_IKEv2
>
> Only issue is coming when trying to use DPDK.
>
> Once/twice I have ran below as well after vagrant ssh. But haven’t
> made any code changes in VPP Source.
>
> cd /vpp
>
> make wipe-release
>
> make install-dep
>
> make build-release (or make build)
>
> make pkg-deb
>
> sudo dpkg -i /vpp/build-root/*.deb
>
> sudo service vpp start
>
> Thanks
>
> Mukesh
>
> *From: *Sergio Gonzalez Monroy <sergio.gonzalez.mon...@intel.com>
> *Date: *Wednesday, 30 August 2017 at 4:18 PM
> *To: *Mukesh Yadav <mukya...@cisco.com>, "vpp-dev@lists.fd.io"
> <vpp-dev@lists.fd.io>
> *Subject: *Re: [vpp-dev] Query for IPSec support on VPP
>
> Which VPP are you using?
>
> If you are using/installing VPP package (rpm/deb), then it is likely
> that you do not have DPDK SW crypto support.
>
> As a summary, if you want DPDK SW crypto support:
> - VPP package: 17.07.1 (AFAIK not released yet) or newer.
> - From source:
> - 17.04 or 17.07: need to build VPP with DPDK SW crypto support
> make build-release vpp_uses_dpdk_cryptodev_sw=yes
> - 17.07.1 or newer: DPDK SW crypto support built by default
> make build-release
>
> Thanks,
> Sergio
>
> On 30/08/2017 10:57, Mukesh Yadav (mukyadav) wrote:
>
> Thanks Sergio.
>
> I tried below combinations of dpdk config.
>
> dpdk {
>
> socket-mem 1024,1024
>
> num-mbufs 131072
>
> dev 0000:00:08.0
>
> # enable-cryptodev
>
> # vdev cryptodev_aesni_mb_pmd,socket_id=1
>
> # vdev cryptodev_aesni_mb_pmd,socket_id=1
>
> }
>
> I get below error:
>
> /usr/bin/vpp[3844]: dpdk_ipsec_process:239: not enough Cryptodevs,
> default to OpenSSL IPsec
>
> dpdk {
>
> socket-mem 1024,1024
>
> num-mbufs 131072
>
> dev 0000:00:08.0
>
> # enable-cryptodev
>
> vdev cryptodev_aesni_mb_pmd,socket_id=1
>
> vdev cryptodev_aesni_mb_pmd,socket_id=1
>
> }
>
> CRYPTODEV: [crypto_aesni_mb] cryptodev_aesni_mb_create() line 704:
> failed to create cryptodev vdev
>
> CRYPTODEV: [crypto_aesni_mb] cryptodev_aesni_mb_create() line 746:
> driver cryptodev_aesni_mb_pmd: cryptodev_aesni_create failed
>
> EAL: failed to initialize cryptodev_aesni_mb_pmd device
>
> Seems still config is missing something.
>
> Can you point me out any working wiki or document for making IPSec
> work along DPDK in VPP.
>
> Thanks
>
> Mukesh
>
> *From: *Sergio Gonzalez Monroy <sergio.gonzalez.mon...@intel.com>
> <mailto:sergio.gonzalez.mon...@intel.com>
> *Date: *Wednesday, 30 August 2017 at 2:06 PM
> *To: *Mukesh Yadav <mukya...@cisco.com>
> <mailto:mukya...@cisco.com>, "vpp-dev@lists.fd.io"
> <mailto:vpp-dev@lists.fd.io> <vpp-dev@lists.fd.io>
> <mailto:vpp-dev@lists.fd.io>
> *Subject: *Re: [vpp-dev] Query for IPSec support on VPP
>
> Just for reference and clarity, there is no wiki entry for the
> DPDK crypto, only documentation page.
> The wiki page is for general VPP/IPSec/IKEv2.
>
> Thanks,
> Sergio
>
> On 30/08/2017 09:19, Sergio Gonzalez Monroy wrote:
>
> On 29/08/2017 18:25, Mukesh Yadav (mukyadav) wrote:
>
> Thanks Sergio for quick help. Pointers cleared few of
> basic doubts.
>
>
> You are flushing out few left overs from previous releases, so
> thank you.
>
>
>
> I will use below wiki to proceed.
>
> https://docs.fd.io/vpp/17.10/dpdk_crypto_ipsec_doc.html
>
> Since vpp version is 17.10
>
> I added below in /vpp/src/vpp/conf/startup.conf
>
> dpdk {
>
> socket-mem 1024,1024
>
> num-mbufs 131072
>
> dev 0000:00:08.0
>
> enable-cryptodev
>
> vdev cryptodev_aesni_mb_pmd,socket_id=1
>
> vdev cryptodev_aesni_mb_pmd,socket_id=1
>
> }
>
> And did a restart of vpp service using “sudo service vpp
> restart”. It didn’t restarted service.
>
> Till now I was using vanilla config which came with Source
> where dpdk config section was commented.
>
> Next I tried below.
>
> /usr/bin/vpp -c /etc/vpp/startup.conf
>
> I can see logs on command terminal where above command is
ran:
>
> load_one_plugin:63: Loaded plugin:
> /usr/lib/vpp_api_test_plugins/ioam_pot_test_plugin.so
>
> dpdk_config: unknown input `enable-cryptodev vdev
cryptode...'
>
>
> That is my bad. The option is not supported anymore, the doc
> is incorrect.
>
>
>
> In wiki it is mentioned to have config like below:
>
> dpdk {
>
> 2 socket-mem 1024,1024
>
> 3 num-mbufs 131072
>
> 4 dev 0000:81:00.0
>
> 5 dev 0000:81:00.1
>
> 6 enable-cryptodev
>
> 7 dev 0000:85:01.0
>
> 8 dev 0000:85:01.1
>
> 9 vdev cryptodev_aesni_mb_pmd,socket_id=1
>
> 10 vdev cryptodev_aesni_mb_pmd,socket_id=1
>
> 11 }
>
>
> I see the wiki needs update too, at least for the latest VPP
> release.
>
>
>
> It is mandatory to have 4 dev config, or It can work with
> single dev config as I mentioned in my sample config.
>
>
> I reckon it should work with a single port, should entirely
> depend on your config (fib, ipsec-tunnels, etc).
> The example in the wiki was just trying to cover the different
> options with a single configuration.
>
> Thanks,
> Sergio
>
>
>
> Thanks
>
> Mukesh
>
>
>
>
>
> _______________________________________________
>
> vpp-dev mailing list
>
> vpp-dev@lists.fd.io <mailto: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
