Apparently we have set this to 1400 but the physical nodes have it set to 1500.
Is this OK? Because we are seeing errors on the two gateway nodes o the recieve side of the interface...
Not a lot of errors, but still we get some.. which is annoying.. and a bit strange on a virtual machine...?
#Recommended MTU size on Client Network for virtual Gateway nodes?
craggy ocean
manic surge
generally, i would say it's just easier to use jumbo frames (9000 bytes + header, mostly just set at "9000") on hardware and set 1500 on client vlan interfaces. You avoid a lot of problems with divergent MTU within a network. Having a smaller MTU is going to cause problems for clients and networks that block PMTU discovery and get their frames fragmented
craggy ocean
So you would recommend setting the Client network to 9000 like the Storage and Grid networks?
...and because it's the client initiatiating the connection, they "set" the MTU size of their "choice"? and there is no chance that the SG will respond back in Jumbo frames which the switch/client will have to split up?
manic surge
clients generally are set at 1500...
As a rule-of-thumb: physical interfaces (and the switched networks they're attached to) should just use jumbo frames. You then use vlan interfaces with 1500MTU to make things easier for this standard 1500 byte MTU clients use
you then have the freedom to use a 9000 byte MTU for the grid network, for example
this used to mean a lot more as far as throughput because the net interfaces could push more data per frame, but the differences isn't much on moderate traffic
craggy ocean
we use jumbo for the grid, but for some reason the provisioned gateway nodes is set to 1400 on the client network where the other physical ndoes (and clients) are set to 1500... so mayeb this is why we see errors on these interfaces... it's also recieve traffic so I guess it makes sense... I think we will try to set these to 1500... but a bit strange why the OVF images have set this to 1400 by default then?