I have an check that I run before I run performance tests which sends a
ping along all of the paths that I run perf testing on. It runs `ping -q -c
1 -s 1472 -M do ` from every source to every destination running an
iperf server It passes. I've set the MTU on all our network devices to
Just for ki
MTU? Big drops in performance numbers are usually because of packet
fragmentation. Keep the MTU of your packet origin to, say 1450 and retry?
On 31 July 2018 at 12:01, Carl Baldwin wrote:
> My apologies. I failed to include the ovs version number that I'm using. It
> is 2.7.3. Is there anything
My apologies. I failed to include the ovs version number that I'm using. It
is 2.7.3. Is there anything else I could check that maybe I'm not thinking
of?
Carl
On Tue, Jul 31, 2018 at 11:01 AM Ben Pfaff wrote:
> On Mon, Jul 30, 2018 at 02:02:16PM -0600, Carl Baldwin wrote:
> > I recently tried
On Mon, Jul 30, 2018 at 02:02:16PM -0600, Carl Baldwin wrote:
> I recently tried pushing MPLS labels using OVS in a lab.
>
> Before adding MPLS push to the mix, I had four hosts: two pairs, each
> connected to a different set of TOR switches running VRRP. OVS (using
> kernel datapath) had a flow t
I recently tried pushing MPLS labels using OVS in a lab.
Before adding MPLS push to the mix, I had four hosts: two pairs, each
connected to a different set of TOR switches running VRRP. OVS (using
kernel datapath) had a flow to write the VRRP mac address and output to a
bond port. The bond is a Li
