* [dpdk-users] (no subject) [not found] ` <459eaf8c52084858b4bc16145336255c@tcs.com> @ 2020-09-21 7:54 ` satyavalli rama 2020-09-22 10:06 ` [dpdk-users] IPSEC: No IPv6 SP Inbound rule specified satyavalli rama 2020-09-26 8:55 ` [dpdk-users] Port Link Down Error while ruining Dpdk ipsec-secgw application satyavalli rama 0 siblings, 2 replies; 5+ messages in thread From: satyavalli rama @ 2020-09-21 7:54 UTC (permalink / raw) To: Anoob Joseph, dev, dev-request, users-request, users Hi Anoob and DPDK Dev Team, ------>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) ------>Below are the steps we've performed.. 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* [dpdk-users] IPSEC: No IPv6 SP Inbound rule specified 2020-09-21 7:54 ` [dpdk-users] (no subject) satyavalli rama @ 2020-09-22 10:06 ` satyavalli rama 2020-09-22 10:25 ` [dpdk-users] [dpdk-dev] " Ananyev, Konstantin 2020-09-26 8:55 ` [dpdk-users] Port Link Down Error while ruining Dpdk ipsec-secgw application satyavalli rama 1 sibling, 1 reply; 5+ messages in thread From: satyavalli rama @ 2020-09-22 10:06 UTC (permalink / raw) To: Anoob Joseph, dev, dev-request, users-request, users Hi Anoob and DPDK Dev Team, > ------>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) > > ------>Below are the steps we've performed.. > > 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 > ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [dpdk-users] [dpdk-dev] IPSEC: No IPv6 SP Inbound rule specified 2020-09-22 10:06 ` [dpdk-users] IPSEC: No IPv6 SP Inbound rule specified satyavalli rama @ 2020-09-22 10:25 ` Ananyev, Konstantin 2020-09-22 10:31 ` [dpdk-users] Port 0 Link Down eerror satyavalli rama 0 siblings, 1 reply; 5+ messages in thread From: Ananyev, Konstantin @ 2020-09-22 10:25 UTC (permalink / raw) To: satyavalli rama, Anoob Joseph, dev, dev-request, users-request, users > Hi Anoob and DPDK Dev Team, > > ------>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 Wonder what makes you think it is an error? It is just a message saying that you don't have SP rules for IPv6.... If you don't plan to process ipv6 traffic that is probably ok. > > Creating IPv4 Routing Table (RT) context with 1024 max routes > > LPM: Adding route 192.168.122.0/24 (1) > > > > ------>Below are the steps we've performed.. > > > > 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 > > ^ permalink raw reply [flat|nested] 5+ messages in thread
* [dpdk-users] Port 0 Link Down eerror 2020-09-22 10:25 ` [dpdk-users] [dpdk-dev] " Ananyev, Konstantin @ 2020-09-22 10:31 ` satyavalli rama 0 siblings, 0 replies; 5+ messages in thread From: satyavalli rama @ 2020-09-22 10:31 UTC (permalink / raw) To: Ananyev, Konstantin; +Cc: Anoob Joseph, dev, dev-request, users-request, users Sorry it was a drafting error Even the nics are up and after binded to Dpdk it is saying 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 On Tue, 22 Sep, 2020, 3:55 pm Ananyev, Konstantin, < konstantin.ananyev@intel.com> wrote: > > > Hi Anoob and DPDK Dev Team, > > > ------>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 > > Wonder what makes you think it is an error? > It is just a message saying that you don't have SP rules for IPv6.... > If you don't plan to process ipv6 traffic that is probably ok. > > > > Creating IPv4 Routing Table (RT) context with 1024 max routes > > > LPM: Adding route 192.168.122.0/24 (1) > > > > > > ------>Below are the steps we've performed.. > > > > > > 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 > > > > ^ permalink raw reply [flat|nested] 5+ messages in thread
* [dpdk-users] Port Link Down Error while ruining Dpdk ipsec-secgw application 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-26 8:55 ` satyavalli rama 1 sibling, 0 replies; 5+ messages in thread From: satyavalli rama @ 2020-09-26 8:55 UTC (permalink / raw) To: Anoob Joseph, dev, dev-request, dev, users, users-request 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2020-09-26 8:55 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[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 ` [dpdk-users] Port Link Down Error while ruining Dpdk ipsec-secgw application satyavalli rama
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).