On Tue, Jul 21, 2015 at 04:52:01PM -0300, Flavio Leitner wrote:
> On Tue, Jul 21, 2015 at 11:38:01AM -0700, Ben Pfaff wrote:
> > On Fri, Jul 17, 2015 at 01:56:21PM -0300, Flavio Leitner wrote:
> > > When ifdown isn't executed (system didn't shut down properly),
> > > the interfaces remain in the op
On Tue, Jul 21, 2015 at 11:38:01AM -0700, Ben Pfaff wrote:
> On Fri, Jul 17, 2015 at 01:56:21PM -0300, Flavio Leitner wrote:
> > When ifdown isn't executed (system didn't shut down properly),
> > the interfaces remain in the openvswitch's database. For the
> > internal ports or devices that are av
On Fri, Jul 17, 2015 at 01:56:21PM -0300, Flavio Leitner wrote:
> When ifdown isn't executed (system didn't shut down properly),
> the interfaces remain in the openvswitch's database. For the
> internal ports or devices that are available when openvswitch
> service starts that's not an issue.
>
>
On Fri, 17 Jul 2015 13:56:21 -0300, Flavio Leitner wrote:
> When ifdown isn't executed (system didn't shut down properly),
> the interfaces remain in the openvswitch's database. For the
> internal ports or devices that are available when openvswitch
> service starts that's not an issue.
>
> Howev
When ifdown isn't executed (system didn't shut down properly),
the interfaces remain in the openvswitch's database. For the
internal ports or devices that are available when openvswitch
service starts that's not an issue.
However, ovs-vsctl won't do anything for devices created later
(Linux vlan
