New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ovs-vsctl add-port fail #110
Comments
Does a network device named "test-test" exist? |
When i use version 1.11.0, command ovs-vsctl add-port .... if the port doesn't exist,it will create the port and then add to bridge. Ref:http://openvswitch.org/support/dist-docs-2.5/ovs-vsctl.8.html |
ovs-vsctl did create the port and add it to the bridge. |
Hello, I have a similar issue going with ovs 2.5 on Linux version 4.2 (running on a VM) root@cep-VirtualBox:/usr/src/ovs/ovs-2.5.0# ovs-vsctl add-port br0 ovs-p0 -- set interface ovs-p0 external-ids:iface-id="p0" Any pointers whatsoever will be helpful. |
so does i meet that problem, i use ovs2.6.1 and dpdk 16.11.2
are you solve this problem? @Fangfenghua @Ad0vith |
The port‘s name should be a exist interface use |
I am seeing the same issues. I tried with ovs-vsctl add-port br0 -- set Interface type=dpdk options:dpdk-devargs=0000:00:09.0 With this, I am seeing the same issue. Please let me know, if anyone has resolved this issue. I am using dpdk 16.07.2 with ovs 2.6.1 Thanks |
Arbitrary port names for DPDK ports was only introduced in OVS 2.7. For OVS 2.6 the DPDK port name must be "dpdkn" where n corresponds to the dpdk port as it was added to the userspace driver. Also for 2.6 you should not include the devargs argument for the bus slot function. You should add the port with the following command instead ovs-vsctl add-port br0 dpdk0 -- set Interface dpdk0 type=dpdk To add a second port use ovs-vsctl add-port br0 dpdk1 -- set Interface dpdk1 type=dpdk Further details can be found in the OVS 2.6 Docs. https://github.com/openvswitch/ovs/blob/branch-2.6/INSTALL.DPDK.md#33-setup-ovs |
Thanks for the information. Here is the hw info for the ports ../dpdk-stable-16.07.2/tools/dpdk-devbind.py --status Network devices using DPDK-compatible driver0000:00:09.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused= How does each port map to corresponding port (Ex: how does dpdk0 map to 0000:00:09.0) Thanks |
I believe they map in the order they appear in status above. So in this case dpdk0 correspond to 00:09.0. You can confirm this by adding and removing the devices from the igb_uio driver in different orders and testing with ovs-dpdk each time. However, this method is quite unwieldy in practice, I would encourage you to move to OVS 2.7 at the very least as 2.6 is quite old & support for DPDK was still only experimental at this point in OVS. |
Why it shows Port does not contain a column whose name matches "set"
|
when i execute ovs-vsctl add-port got a error:
[root@mesos-slave ~]# ovs-vsctl add-br br-test
[root@mesos-slave ~]# ovs-vsctl add-port br-test test-test
ovs-vsctl: Error detected while setting up 'test-test'. See ovs-vswitchd log for details.
[root@mesos-slave ~]#
*_vi /var/log/openvswitch/ovs-vswitchd.log
*_2016-03-15T02:37:14.455Z|00001|ofproto_dpif_upcall(handler10)|INFO|received packet on unassociated datapath port 0
2016-03-15T02:37:14.463Z|00023|bridge|INFO|bridge br-test: added interface br-test on port 65534
2016-03-15T02:37:14.463Z|00024|bridge|INFO|bridge br-test: using datapath ID 00005a871bb49b4b
2016-03-15T02:37:14.463Z|00025|connmgr|INFO|br-test: added service controller "punix:/var/run/openvswitch/br-test.mgmt"
2016-03-15T02:37:24.003Z|00026|bridge|WARN|could not open network device test-test (No such device)
*ENV *
root@mesos-slave ~]# uname -a
Linux mesos-slave 3.10.0-327.10.1.el7.x86_64 #1 SMP Tue Feb 16 17:03:50 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[root@mesos-slave ~]# ovs-vsctl -V
ovs-vsctl (Open vSwitch) 2.4.0
Compiled Oct 7 2015 18:01:06
DB Schema 7.12.1
[root@mesos-slave
The text was updated successfully, but these errors were encountered: