VPP IPsec responder on ESXI VM RHEL 7.6
Is there a limitation on the number of num-tx-queues and num-rx-queues we can
associate with vmxnet3? I have 12 worker threads running but when i try to
associate more than 4 num-rx-queues i get error saying "vmxnet3 failed to
activate dev error 1"
Yes it works fine with num-rx-queues 4 and below.
vpp# sh threads
ID Name Type LWP Sched Policy (Priority) lcore Core Socket State
0 vpp_main 2726 other (0) 1 0 0
1 vpp_wk_0 workers 2730 other (0) 2 0 4
2 vpp_wk_1 workers 2731 other (0) 3 0 6
3 vpp_wk_2 workers 2732 other (0) 4 0 8
4 vpp_wk_
[Edited Message Follows]
VPP IPsec responder on ESXI VM RHEL 7.6
Is there a limitation on the number of num-tx-queues and num-rx-queues we can
associate with vmxnet3? I have 12 worker threads running but when i try to
associate more than 4 num-rx-queues i get error saying "vmxnet3 failed to
ac
Route Injection VPP IPSec: " Routing traffic through ipsec0 interface on the
VPP responder "
*Setup Details:* StrongSwan IPsec client initiator which establishes 250 IPSec
tunnels with the VPP head-end responder.
*Case # Only one IPSec tunnel:*
ipip0 (ipsec00) interface and its straight forward
Folks,
I am seeing packet congestion drop errors "esp4-encrypt-tun-handoff". What
could be the reason for this and how can i debug this further?
124 ikev2 IKEv2 packets processed
31 ikev2 IKE_SA_INIT retransmit
31 ip4-
[Edited Message Follows]
Folks,
I am seeing packet congestion drop errors "esp4-encrypt-tun-handoff". What
could be the reason for this and how can i debug this further?
124 ikev2 IKEv2 packets processed
31 ikev2 IKE_SA_INIT retr
[Edited Message Follows]
Route Injection VPP IPSec: " Routing traffic through ipsec0 interface on the
VPP responder "
*Setup Details:* StrongSwan IPsec client initiator which establishes 250 IPSec
tunnels with the VPP head-end responder.
*Case # Only one IPSec tunnel:*
ipip0 (ipsec00) interfac
