[dpdk-users] Port Link Down Error while ruining Dpdk ipsec-secgw application

DPDK usage discussions
 help / color / mirror / Atom feed

From: satyavalli rama <satyavalli.rama@gmail.com>
To: Anoob Joseph <anoobj@marvell.com>,
	dev@dpdk.org, dev-request@dpdk.org,  dev@openvswitch.org,
	users@dpdk.org, users-request@dpdk.org
Subject: [dpdk-users] Port Link Down Error while ruining Dpdk ipsec-secgw application
Date: Sat, 26 Sep 2020 14:25:02 +0530	[thread overview]
Message-ID: <CAECt3bNgisVFOHs39rPSP4T4gBu_Yp_7-4Qr2Fc0dm8M5jrdGg@mail.gmail.com> (raw)
In-Reply-To: <CAECt3bM_3kuRfw2rqq+WbJt7RV=ehn-ZuSZj+WWExXiS8MxCfQ@mail.gmail.com>

Hi Anoob and DPDK Dev Team,

Please guide us resolve the issue..

While running the ipsec-secgw application the ports are getting down and it
is throwing

------>Port Link Down Error

We are doing the below steps:

Since we don't have IXGBE driver in the virtual machines. we used SRIOV to
import the IXGBE NIC's (Virtual function) from host(Physical function).
We refered the below link for SRIOV:
https://software.intel.com/content/www/us/en/develop/articles/configure-sr-iov-network-virtual-functions-in-linux-kvm.html

This the info after importing IXGBE NIC's into virtual machine:
-----------> ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP mode DEFAULT group default qlen 1000
    link/ether 52:54:00:bd:f7:ce brd ff:ff:ff:ff:ff:ff
3: ens9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP mode DEFAULT group default qlen 1000
    link/ether 52:54:00:e5:35:b5 brd ff:ff:ff:ff:ff:ff
4: ens12: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP mode DEFAULT group default qlen 1000
    link/ether 52:54:00:14:ce:7c brd ff:ff:ff:ff:ff:ff
5: ens13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP mode DEFAULT group default qlen 1000
    link/ether 52:54:00:d0:73:4c brd ff:ff:ff:ff:ff:ff

6: ens3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
    link/ether 96:42:49:cd:9c:61 brd ff:ff:ff:ff:ff:ff
 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
7: ens11: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
    link/ether 3e:f5:92:ef:9e:16 brd ff:ff:ff:ff:ff:ff
 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


8: ens10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP mode DEFAULT group default qlen 1000
    link/ether 52:54:00:51:ee:74 brd ff:ff:ff:ff:ff:ff
9: ens14: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP mode DEFAULT group default qlen 1000
    link/ether 52:54:00:da:08:cb brd ff:ff:ff:ff:ff:ff
10: ens15: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP mode DEFAULT group default qlen 1000
    link/ether 52:54:00:31:7c:6f brd ff:ff:ff:ff:ff:ff

------>While we are running the ipsec-secgw application. We are getting
following error:

IPSEC: No IPv6 SP Inbound rule specified
IPSEC: No IPv6 SP Outbound rule specified
Creating IPv4 Routing Table (RT) context with 1024 max routes
LPM: Adding route 192.168.122.0/24 (1)

Checking link
status..........................................................................................done
Port 0 Link Down
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Port 1 Link Down
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
IPSEC: entering main loop on lcore 0
IPSEC:  -- lcoreid=0 portid=0 rxqueueid=0
IPSEC:  -- lcoreid=0 portid=1 rxqueueid=0

Please find the attachment which contain console logs.

Thanks and Regards

     prev parent reply	other threads:[~2020-09-26  8:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d61d4da786594548953efcc0503c6647@tcs.com>
     [not found] ` <2a9c8f5b288d4917806cba6ecefb6ee7@tcs.com>
     [not found]   ` <459eaf8c52084858b4bc16145336255c@tcs.com>
2020-09-21  7:54     ` [dpdk-users] (no subject) satyavalli rama
2020-09-22 10:06       ` [dpdk-users] IPSEC: No IPv6 SP Inbound rule specified satyavalli rama
2020-09-22 10:25         ` [dpdk-users] [dpdk-dev] " Ananyev, Konstantin
2020-09-22 10:31           ` [dpdk-users] Port 0 Link Down eerror satyavalli rama
2020-09-26  8:55       ` satyavalli rama [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAECt3bNgisVFOHs39rPSP4T4gBu_Yp_7-4Qr2Fc0dm8M5jrdGg@mail.gmail.com \
    --to=satyavalli.rama@gmail.com \
    --cc=anoobj@marvell.com \
    --cc=dev-request@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=dev@openvswitch.org \
    --cc=users-request@dpdk.org \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Be sure your reply has a Subject: header at the top and a blank line before the message body.

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).