On 19 November 2015 at 04:21, Mikhail Bagrov <mbag...@cloudlinux.com> wrote:
> Hi. I'm trying to implement the VTEP Emulator from > https://github.com/openvswitch/ovs/blob/master/vtep/README.ovs-vtep.md > I've built OVS from source on Centos7. > > When I run 'ovs-vsctl add-port br0 p0', I get an error about the > unexisting device, so, to avoid it I run 'brctl addbr p0' before. > The p0 needs to exist before hand. i..e it needs to be a valid network interface. It can either be a tap device attached to a VM, or a OVS internal interface (created via ovs-vsctl add-port br0 p0 -- set interface p0 type=intenal) or a physical network device (like 'eth1', 'eth2' etc via which you expect the traffic to come from via VLANs and which you want to ramp into logical networks). Once you get the above cleared out, let me know if you hit any other issues. (I haven't read the remainder of your email). Also start your emulator (ovs-vtep) only after the above is resolved. > > When I want to bind a logical switch to any of my bridge ports, I get an > error. I've even added a spare physical port to br0, just to try, but this > fails too. > [root@ovs11 ovs]# ovs-vsctl show > e27227fb-c93b-4ab6-ac39-574374a8211b > Bridge "br0" > Port "eth2" > Interface "eth2" > Port "p1" > Interface "p1" > Port "br0" > Interface "br0" > type: internal > Port "p0" > Interface "p0" > [root@ovs11 ovs]# vtep-ctl bind-ls br0 eth2 0 ls0 > vtep-ctl: no port named eth2 > [root@ovs11 ovs]# vtep-ctl bind-ls br0 p0 0 ls0 > vtep-ctl: no port named p0 > > While I have no problems in logs or running commands in verbose(-v) mode. > May I have a more repeatable manual to try NVC? Thanks in advance. > > -- > Regards, Mikhail Bagrov > DevOps at Kuberdock > > > _______________________________________________ > discuss mailing list > discuss@openvswitch.org > http://openvswitch.org/mailman/listinfo/discuss > >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
