Missed CCing list in the earlier email. Looks like the fix is present in 2.6.0. I will plan on upgrading
On Thu, Dec 15, 2016 at 10:30 AM, Vijay Sampath < vsamp...@pluribusnetworks.com> wrote: > Thanks a lot Nick. We are using ovs version 2.5.90. I assume the feature > is not available here, as I don't see I get an error when issuing the > command. > > # ovs-vsctl set int eth0 mtu_request=9216 > ovs-vsctl: Interface does not contain a column whose name matches > "mtu_request" > > # ovs-vsctl -V > ovs-vsctl (Open vSwitch) 2.5.90 > DB Schema 7.13.0 > > Which version should I use? > > Thanks, > > Vijay > > On Thu, Dec 15, 2016 at 6:45 AM, nickcooper-zhangtonghao < > n...@opencloud.tech> wrote: > >> Hi Vijay, >> The section “How can I configure the bridge internal interface MTU? “ >> and the ovs-vswitchd manpage may help you. >> https://github.com/openvswitch/ovs/blob/master/Documentation >> /faq/issues.rst >> >> >> Thanks. >> Nick >> >> On Dec 15, 2016, at 7:31 AM, Vijay Sampath via discuss < >> ovs-discuss@openvswitch.org> wrote: >> >> I have read articles online that an OVS bridge defaults to the MTU of the >> port that has the lowest configured MTU value. I wanted to confirm if this >> is in fact true. Is it not possible that the bridge has ports belonging to >> different segments (say segmented by vlan) and is not then possible that >> ports in each of these segments have a different configured MTU value? >> >> Thanks, >> >> Vijay >> >> >> >
_______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
