date:20170915

Re: [ovs-discuss] error: "could not open network device dpdk0 (Address family not supported by protocol)"

2017-09-15 Thread O'Reilly, Darragh


try binding to the uio_pci_generic driver.

Regards,
Darragh.

From: Ranjith Kumar D [mailto:ranjith.ku...@radisys.com]
Sent: 15 September 2017 07:59
To: O'Reilly, Darragh ; disc...@openvswitch.org
Subject: RE: [ovs-discuss] error: "could not open network device dpdk0 (Address 
family not supported by protocol)"

Hi Darragh,

Thank you for your suggestion, I tried followed step 5 from the link which you 
shared and also  enabled PMD CPU mask. However VM still hangs while starting 
OVS daemon(ovs-vswitchd --dpdk -c 0x1 -n 4 -- unix:$DB_SOCK --pidfile -detach).

Regards,
Ranjith

From: O'Reilly, Darragh [mailto:darragh.orei...@hpe.com]
Sent: Thursday, September 14, 2017 9:02 PM
To: Ranjith Kumar D 
mailto:ranjith.ku...@radisys.com>>; 
disc...@openvswitch.org
Subject: RE: [ovs-discuss] error: "could not open network device dpdk0 (Address 
family not supported by protocol)"


Maybe you need to set the pmd-cpu-mask. I don't know what it defaults to. I 
think this will place a PMD on the fourth core
ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0x8

Then make sure ovs-vswitchd is stopped and try starting it like step 5 in 
https://github.com/openvswitch/ovs/blob/branch-2.4/INSTALL.DPDK.md

Regards,
Darragh.

From: 
ovs-discuss-boun...@openvswitch.org 
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of Ranjith Kumar D
Sent: 14 September 2017 14:29
To: disc...@openvswitch.org
Subject: [ovs-discuss] error: "could not open network device dpdk0 (Address 
family not supported by protocol)"

Hello All,

I have installed OVS 2.4.0 in a Virtual machine with DPDK 2.0,  I am getting 
below error when I add DPDK port in OVS bridge.

error: "could not open network device dpdk0 (Address family not supported by 
protocol)"

d68d0789-5e61-47d4-ad2d-838c183b0e41
Bridge pdn-br
Port "dpdk0"
Interface "dpdk0"
type: dpdk
error: "could not open network device dpdk0 (Address family not 
supported by protocol)"
Port pdn-br
Interface pdn-br
type: internal

DPDK NIC status:

ubuntu@mysite-vpgwu-slice1-25:~/dpdk-2.0.0/tools$
 ./dpdk_nic_bind.py --s

Network devices using DPDK-compatible driver

:00:03.0 'Virtio network device' drv=igb_uio unused=

Network devices using kernel driver
===
:00:04.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
:00:05.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
:00:06.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
:00:07.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio

Other network devices
=


Huge Page:( cat /proc/meminfo)

HugePages_Total:   1
HugePages_Free:1
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:1048576 kB
DirectMap4k:   51068 kB
DirectMap2M: 3094528 kB
DirectMap1G: 7340032 kB


The below are steps which I followed to configure OVS


1.  config_file="/etc/depmod.d/openvswitch.conf"

2.  for module in datapath/linux/*.ko; do   modname="$(basename 
${module})";   echo "override ${modname%.ko} * extra" >> "$config_file";   echo 
"override ${modname%.ko} * weak-updates" >> "$config_file";   done



3.  depmod -a

4.  /sbin/modprobe openvswitch

5.  /sbin/lsmod



6.  mkdir -p /usr/local/etc/openvswitch

7.  ovsdb-tool create /usr/local/etc/openvswitch/conf.db 
vswitchd/vswitch.ovsschema

8.  ovsdb-server --remote=punix:/usr/local/var/run/openvswitch/db.sock  
--remote=db:Open_vSwitch,Open_vSwitch,manager_options   
   --private-key=db:Open_vSwitch,SSL,private_key  
--certificate=db:Open_vSwitch,SSL,certificate  
--bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert  --pidfile 
-detach

9.  ovs-vsctl --no-wait init

10.   ovs-vswitchd --pidfile -detach

11.   ovs-vsctl add-br pdn-br

12.   ovs-vsctl set bridge pdn-br datapath_type=netdev

13.   ovs-vsctl add-port pdn-br dpdk0 -- set Interface dpdk0 type=dpdk

The VM had hang when I follow below steps instead of above step 10


1.  export DB_SOCK=/usr/local/var/run/openvswitch/db.sock

2.  ovs-vswitchd --dpdk -c 0x1 -n 4 -- unix:$DB_SOCK --pidfile -detach


Output VM hang console:

root@mysite-vpgwu-slice1-25:/home/ubuntu# ovs-vswitchd --dpdk -c 0x1 -n 4 -- 
unix:$DB_SOCK --pidfile -detach

2017-09-14T21:32:31Z|1|dpdk|INFO|No -vhost_sock_dir provided - defaulting 
to /usr/local/var/run/openvswitch

EAL: Detected lcore 0 as core 0 on socket 0

EAL: Detected lcore 1 as core 0 on socket 0

EAL: Detected lcore 2 as core 0 on socket 0

EAL: Detected lcore 3 as core 0 on socket 0

EAL: Support maximum 128 logical core(s) by configuration.

EAL: Detected 4 lcore(s

[ovs-discuss] LACP bond faulty, partner state: activity timeout

2017-09-15 Thread Elias Abacioglu

Hi,

I'm running Open vSwitch on some nodes and trying to get a LACP bond to
work.
But it's not working fully.
The partner state looks like this:
*partner state: activity timeout aggregation synchronized collecting
distributing*

I have other nodes where it is working and it looks like this:
*partner state: activity aggregation synchronized collecting distributing*

And the HW switch(Dell FTOS) the nodes are connected to are setup correctly
AFAIK.


Here is how my setup looks like:
I've cut the output a bit to reduce clutter.
```
$ sudo ovs-appctl bond/show
 bond0 
bond_mode: balance-tcp
bond may use recirculation: yes, Recirc-ID : 1
bond-hash-basis: 0
updelay: 0 ms
downdelay: 0 ms
next rebalance: 9480 ms
lacp_status: negotiated

slave p1p1: enabled
may_enable: true

slave p1p2: enabled
active slave
may_enable: true
```

```
  $ sudo ovs-appctl lacp/show
   bond0 
  status: active negotiated
  aggregation key: 1
  lacp_time: fast

  slave: p1p1: current attached
  port_id: 2
  may_enable: true

  actor port_id: 2
  actor key: 1
  actor state: activity timeout aggregation synchronized collecting
distributing

   partner port_id: 132
  partner key: 38
  partner state: activity timeout aggregation synchronized collecting
distributing

  slave: p1p2: current attached
  port_id: 1
  may_enable: true

  actor port_id: 1
  actor key: 1
  actor state: activity timeout aggregation synchronized collecting
distributing

  partner port_id: 196
  partner key: 38
  partner state: activity timeout aggregation synchronized collecting
distributing
```

FTOS config
```
lacp ungroup member-independent port-channel 38
!
interface TenGigabitEthernet 0/2
 description vm09
 no ip address
!
 port-channel-protocol LACP
  port-channel 38 mode active
 no shutdown
!
interface TenGigabitEthernet 1/2
 description vm09
 no ip address
!
 port-channel-protocol LACP
  port-channel 38 mode active
 no shutdown
!
interface Port-channel 38
 description vm09
 no ip address
 portmode hybrid
 switchport
 no shutdown
!
```

Where do I go from here, how can I figure out what's wrong?


Any help is appreciated.

/Elias
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] error: "could not open network device dpdk0 (Address family not supported by protocol)"

2017-09-15 Thread Ranjith Kumar D

Hi Darragh,


No luck, still the same issue. I tried one more experiments by testing PMD 
command line(sudo ./testpmd -c 0xF -n 4 -- -i --portmask=0x1 --nb-cores=2
) by following below link steps, VM hangs.

http://dpdk.readthedocs.io/en/v16.04/testpmd_app_ug/build_app.html
However, PMD command line work  without any issue with DPDK 17.0.1.

Regards,
Ranjith

From: O'Reilly, Darragh [mailto:darragh.orei...@hpe.com]
Sent: Friday, September 15, 2017 3:17 PM
To: Ranjith Kumar D ; disc...@openvswitch.org
Subject: RE: [ovs-discuss] error: "could not open network device dpdk0 (Address 
family not supported by protocol)"


try binding to the uio_pci_generic driver.

Regards,
Darragh.

From: Ranjith Kumar D [mailto:ranjith.ku...@radisys.com]
Sent: 15 September 2017 07:59
To: O'Reilly, Darragh 
mailto:darragh.orei...@hpe.com>>; 
disc...@openvswitch.org
Subject: RE: [ovs-discuss] error: "could not open network device dpdk0 (Address 
family not supported by protocol)"

Hi Darragh,

Thank you for your suggestion, I tried followed step 5 from the link which you 
shared and also  enabled PMD CPU mask. However VM still hangs while starting 
OVS daemon(ovs-vswitchd --dpdk -c 0x1 -n 4 -- unix:$DB_SOCK --pidfile -detach).

Regards,
Ranjith

From: O'Reilly, Darragh [mailto:darragh.orei...@hpe.com]
Sent: Thursday, September 14, 2017 9:02 PM
To: Ranjith Kumar D 
mailto:ranjith.ku...@radisys.com>>; 
disc...@openvswitch.org
Subject: RE: [ovs-discuss] error: "could not open network device dpdk0 (Address 
family not supported by protocol)"


Maybe you need to set the pmd-cpu-mask. I don't know what it defaults to. I 
think this will place a PMD on the fourth core
ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0x8

Then make sure ovs-vswitchd is stopped and try starting it like step 5 in 
https://github.com/openvswitch/ovs/blob/branch-2.4/INSTALL.DPDK.md

Regards,
Darragh.

From: 
ovs-discuss-boun...@openvswitch.org 
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of Ranjith Kumar D
Sent: 14 September 2017 14:29
To: disc...@openvswitch.org
Subject: [ovs-discuss] error: "could not open network device dpdk0 (Address 
family not supported by protocol)"

Hello All,

I have installed OVS 2.4.0 in a Virtual machine with DPDK 2.0,  I am getting 
below error when I add DPDK port in OVS bridge.

error: "could not open network device dpdk0 (Address family not supported by 
protocol)"

d68d0789-5e61-47d4-ad2d-838c183b0e41
Bridge pdn-br
Port "dpdk0"
Interface "dpdk0"
type: dpdk
error: "could not open network device dpdk0 (Address family not 
supported by protocol)"
Port pdn-br
Interface pdn-br
type: internal

DPDK NIC status:

ubuntu@mysite-vpgwu-slice1-25:~/dpdk-2.0.0/tools$
 ./dpdk_nic_bind.py --s

Network devices using DPDK-compatible driver

:00:03.0 'Virtio network device' drv=igb_uio unused=

Network devices using kernel driver
===
:00:04.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
:00:05.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
:00:06.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
:00:07.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio

Other network devices
=


Huge Page:( cat /proc/meminfo)

HugePages_Total:   1
HugePages_Free:1
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:1048576 kB
DirectMap4k:   51068 kB
DirectMap2M: 3094528 kB
DirectMap1G: 7340032 kB


The below are steps which I followed to configure OVS


1. config_file="/etc/depmod.d/openvswitch.conf"

2. for module in datapath/linux/*.ko; do   modname="$(basename ${module})"; 
  echo "override ${modname%.ko} * extra" >> "$config_file";   echo "override 
${modname%.ko} * weak-updates" >> "$config_file";   done



3. depmod -a

4. /sbin/modprobe openvswitch

5. /sbin/lsmod



6. mkdir -p /usr/local/etc/openvswitch

7. ovsdb-tool create /usr/local/etc/openvswitch/conf.db 
vswitchd/vswitch.ovsschema

8. ovsdb-server --remote=punix:/usr/local/var/run/openvswitch/db.sock   
   --remote=db:Open_vSwitch,Open_vSwitch,manager_options
  --private-key=db:Open_vSwitch,SSL,private_key  
--certificate=db:Open_vSwitch,SSL,certificate  
--bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert  --pidfile 
-detach

9. ovs-vsctl --no-wait init

10.  ovs-vswitchd --pidfile -detach

11.  ovs-vsctl add-br pdn-br

12.  ovs-vsctl set bridge pdn-br datapath_type=netdev

13.  ovs-vsctl add-port pdn-br dpdk0 -- set Interface dpdk0 type=dpdk

The VM had hang when I follow below steps inst

Re: [ovs-discuss] error: "could not open network device dpdk0 (Address family not supported by protocol)"

2017-09-15 Thread O'Reilly, Darragh

Hi Ranjith,

I checked my notes from when I was learning ovs-dpdk 2.4 on kvm vms, and I was 
using e1000 emulated nics. Maybe try those.

Regards,
Darragh.

From: Ranjith Kumar D [mailto:ranjith.ku...@radisys.com]
Sent: 15 September 2017 13:02
To: O'Reilly, Darragh ; disc...@openvswitch.org
Subject: RE: [ovs-discuss] error: "could not open network device dpdk0 (Address 
family not supported by protocol)"

Hi Darragh,


No luck, still the same issue. I tried one more experiments by testing PMD 
command line(sudo ./testpmd -c 0xF -n 4 -- -i --portmask=0x1 --nb-cores=2
) by following below link steps, VM hangs.

http://dpdk.readthedocs.io/en/v16.04/testpmd_app_ug/build_app.html

However, PMD command line work  without any issue with DPDK 17.0.1.

Regards,
Ranjith

From: O'Reilly, Darragh [mailto:darragh.orei...@hpe.com]
Sent: Friday, September 15, 2017 3:17 PM
To: Ranjith Kumar D 
mailto:ranjith.ku...@radisys.com>>; 
disc...@openvswitch.org
Subject: RE: [ovs-discuss] error: "could not open network device dpdk0 (Address 
family not supported by protocol)"


try binding to the uio_pci_generic driver.

Regards,
Darragh.

From: Ranjith Kumar D [mailto:ranjith.ku...@radisys.com]
Sent: 15 September 2017 07:59
To: O'Reilly, Darragh 
mailto:darragh.orei...@hpe.com>>; 
disc...@openvswitch.org
Subject: RE: [ovs-discuss] error: "could not open network device dpdk0 (Address 
family not supported by protocol)"

Hi Darragh,

Thank you for your suggestion, I tried followed step 5 from the link which you 
shared and also  enabled PMD CPU mask. However VM still hangs while starting 
OVS daemon(ovs-vswitchd --dpdk -c 0x1 -n 4 -- unix:$DB_SOCK --pidfile -detach).

Regards,
Ranjith

From: O'Reilly, Darragh [mailto:darragh.orei...@hpe.com]
Sent: Thursday, September 14, 2017 9:02 PM
To: Ranjith Kumar D 
mailto:ranjith.ku...@radisys.com>>; 
disc...@openvswitch.org
Subject: RE: [ovs-discuss] error: "could not open network device dpdk0 (Address 
family not supported by protocol)"


Maybe you need to set the pmd-cpu-mask. I don't know what it defaults to. I 
think this will place a PMD on the fourth core
ovs-vsctl set Open_vSwitch . other_config:pmd-cpu-mask=0x8

Then make sure ovs-vswitchd is stopped and try starting it like step 5 in 
https://github.com/openvswitch/ovs/blob/branch-2.4/INSTALL.DPDK.md

Regards,
Darragh.

From: 
ovs-discuss-boun...@openvswitch.org 
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of Ranjith Kumar D
Sent: 14 September 2017 14:29
To: disc...@openvswitch.org
Subject: [ovs-discuss] error: "could not open network device dpdk0 (Address 
family not supported by protocol)"

Hello All,

I have installed OVS 2.4.0 in a Virtual machine with DPDK 2.0,  I am getting 
below error when I add DPDK port in OVS bridge.

error: "could not open network device dpdk0 (Address family not supported by 
protocol)"

d68d0789-5e61-47d4-ad2d-838c183b0e41
Bridge pdn-br
Port "dpdk0"
Interface "dpdk0"
type: dpdk
error: "could not open network device dpdk0 (Address family not 
supported by protocol)"
Port pdn-br
Interface pdn-br
type: internal

DPDK NIC status:

ubuntu@mysite-vpgwu-slice1-25:~/dpdk-2.0.0/tools$
 ./dpdk_nic_bind.py --s

Network devices using DPDK-compatible driver

:00:03.0 'Virtio network device' drv=igb_uio unused=

Network devices using kernel driver
===
:00:04.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
:00:05.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
:00:06.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
:00:07.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio

Other network devices
=


Huge Page:( cat /proc/meminfo)

HugePages_Total:   1
HugePages_Free:1
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:1048576 kB
DirectMap4k:   51068 kB
DirectMap2M: 3094528 kB
DirectMap1G: 7340032 kB


The below are steps which I followed to configure OVS


1.  config_file="/etc/depmod.d/openvswitch.conf"

2.  for module in datapath/linux/*.ko; do   modname="$(basename 
${module})";   echo "override ${modname%.ko} * extra" >> "$config_file";   echo 
"override ${modname%.ko} * weak-updates" >> "$config_file";   done



3.  depmod -a

4.  /sbin/modprobe openvswitch

5.  /sbin/lsmod



6.  mkdir -p /usr/local/etc/openvswitch

7.  ovsdb-tool create /usr/local/etc/openvswitch/conf.db 
vswitchd/vswitch.ovsschema

8.  ovsdb-server --remote=punix:/usr/local/var/run/openvswitch/db.sock  
--remote=db:Open_vSwitch,Open_vSwitch,manager_options

[ovs-discuss] Open vSwitch Fall 2017 Conference: Call for Participation and Registration

2017-09-15 Thread Ben Pfaff

[Sorry about the repost]

The Open vSwitch project, a Linux Foundation Collaborative Project,
will host its fourth annual conference focused on Open vSwitch and OVN
on November 16 and 17, 2017, at Club Auto Sport in San Jose,
California.

We are seeking long and short ("lightning") talks on topics related to
Open vSwitch and OVN.  We expect long talks to last 20 minutes with an
additional 5 minutes for questions, and short talks to last 5 minutes.

Topics that may be considered, among others, include:

 * The future of Open vSwitch (e.g., P4 and eBPF).

 * NAT, DPI, and stateful processing with Open vSwitch. 

 * Deploying and using OVN.

 * Testing and scaling OVN.

 * NIC acceleration of Open vSwitch.

 * Using Open vSwitch to realize NFV and service chaining.

 * Porting Open vSwitch to new operating systems, hypervisors,
   or container systems.

 * Integrating Open vSwitch into larger systems.

 * Troubleshooting and debugging Open vSwitch installations.

 * Open vSwitch development and testing practices.

 * Performance measurements or approaches to improving
   performance.

 * End-user or service provider experiences with Open vSwitch.

 * Hardware ports of Open vSwitch (existing, in progress, or
   speculative).

 * The relationship between OpenFlow and Open vSwitch.

 * Using, developing, or administering OpenFlow controllers in
   conjunction with Open vSwitch.

 * Comparisons to other implementations of features found in
   Open vSwitch (e.g. other OpenFlow implementations, other
   software switches, etc.).

 * Increasing the size and diversity of the Open vSwitch user
   and developer base.

 * Tutorials and walkthroughs of use cases.

 * Demos.

Talks will be recorded and made available online.


How to propose a talk
-

This year, we are soliciting proposals for full talks and short
("lightning") talks in a single round.  If you request a full talk, we
will also consider it for a lightning talk in the event that we cannot
accept it as a full talk.

We will also accept proposals for panel discussions.  Please submit
them as full talks and make it clear in the description that it is a
panel.

Please submit proposals to to the following URL by September 29:

https://goo.gl/forms/erjZIQICXVjfUh863

Speakers will be notified of acceptance by October 6.

Speakers should plan to attend the event in person.  Travel to and
accommodations in San Jose are the responsibility of attendees.


How to attend
-

To partially cover expenses, we expect to charge $200 for
registration.  We offer complimentary registration to speakers,
students, academics, and anyone for whom the registration fee is
burdensome.  Please contact us if you need any help obtaining a
complimentary registration.

To register, visit https://www.regonline.com/openvswitch2017.


Related Event: DPDK Summit
--

The Open vSwitch conference, on Nov. 16-17, follows the DPDK North
America Summit on Nov. 14-15, in the same venue.  The CFP for the DPDK
Summit is open until Oct. 4:
http://events.linuxfoundation.org/events/dpdk-north-america-summit/program/cfp


Important URLs
--

CFP: https://goo.gl/forms/erjZIQICXVjfUh863
general: https://events.linuxfoundation.org/events/open-vswitch-fall-event
registration: https://www.regonline.com/openvswitch2017


More information


To reach the organizers, email ovs...@openvswitch.org.  For general
discussion of the conference, please use the ovs-discuss mailing list
at disc...@openvswitch.org.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] error: "could not open network device dpdk0 (Address family not supported by protocol)"

[ovs-discuss] LACP bond faulty, partner state: activity timeout

Re: [ovs-discuss] error: "could not open network device dpdk0 (Address family not supported by protocol)"

Re: [ovs-discuss] error: "could not open network device dpdk0 (Address family not supported by protocol)"

[ovs-discuss] Open vSwitch Fall 2017 Conference: Call for Participation and Registration

5 matches

Site Navigation

Mail list logo

Footer information