Hi Ben, I have a related question. I do the following in order to have a bridge br with ports 0.br, 1.br... and later add existing interfaces to such ports:
ovs-vsctl add-br br ovs-vsctl add-port br 0.br ovs-vsctl --id=@ifce create interface name=eth1 -- set port 0.br interface=@ifce When I execute the "ovs-vsctl add-port' command above I get an error saying that 0.br doesn't correspond to any interface: *ovs-vsctl: Error detected while setting up '0.switch5': could not open network device 0.switch5 (No such device).* Can I pass an argument to "ovs-vsctl add-port" to tell OVS that 0.br is just a switch port and not a real existing interface? ______ On 15 January 2018 at 20:19, Ben Pfaff <[email protected]> wrote: > On Mon, Jan 15, 2018 at 09:50:52AM -0800, Fred Licht wrote: > > Is it possible to have an OVS port ‘name’ differ from the interface > name? > > > > Bridge ovs-ha-sw > > Port ovs-ha-sw > > Interface ovs-ha-sw > > type: internal > > Port "bond1" > > Interface "bond1" > > > > To have the effect of: > > > > Bridge ovs-ha-sw > > Port ovs-ha-sw > > Interface ovs-ha-sw > > type: internal > > Port “east-west" > > Interface "bond1" > > You can do it, but since port names are immutable it has to happen at > the time you add the port. For example: > > blp@sigabrt:~/nicira/ovs/tutorial(0)$ ovs-vsctl add-br br0 > blp@sigabrt:~/nicira/ovs/tutorial(0)$ ovs-vsctl add-port br0 p0 -- set > port p0 name=asdf > blp@sigabrt:~/nicira/ovs/tutorial(0)$ ovs-vsctl show > 8b75cccb-f1eb-4e75-ac67-57ebac4e8432 > Bridge "br0" > Port "br0" > Interface "br0" > type: internal > Port asdf > Interface "p0" > blp@sigabrt:~/nicira/ovs/tutorial(0)$ > _______________________________________________ > discuss mailing list > [email protected] > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss >
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
