Re: [PVE-User] OVS Internal ports all in state unknown

2018-09-17 Thread Brian Sidebotham
Thanks for the responses to an essentially off-topic post. Best Regards, --- Brian Sidebotham On Fri, 14 Sep 2018 at 19:07, Josh Knight wrote: > This looks to be expected. The operational state is provided by the > kernel/driver for the interface. For these virtual interfaces, it's j

Re: [PVE-User] OVS Internal ports all in state unknown

2018-09-14 Thread Josh Knight
This looks to be expected. The operational state is provided by the kernel/driver for the interface. For these virtual interfaces, it's just not being reported, probably because they can't actually go down. This is common and not specific to proxmox. The openvswitch and tun drivers must not be re

Re: [PVE-User] OVS Internal ports all in state unknown

2018-09-14 Thread dORSY
this is not proxmox relatedthose are not phisical ifs so there is no link up or down on them On Fri, Sep 14, 2018 at 16:42, Brian Sidebotham wrote: Hi Guys, We are using Openvswitch networking and we have a physical 1G management network and two 10G physical links bonded. The physical i

[PVE-User] OVS Internal ports all in state unknown

2018-09-14 Thread Brian Sidebotham
Hi Guys, We are using Openvswitch networking and we have a physical 1G management network and two 10G physical links bonded. The physical interfaces show a state of UP when doing "ip a". However for the OVS bond, bridges and internal ports we get a state of" UNKNOWN". Is this expected? Everythin