MINT MTU

[Aviv_Kedem]

Generic question about MINT MTU.
Default MTU is 1500 and in most cases is not meet the netwotk's MTU.
Is always recommended in L2/L3 adoption to set the MTU suitable for the network?
Or just only adjust it when there is some issues ?

[Aviv_Kedem]

I need the official answer for the question.
Thanks

[Aviv_Kedem]

Thanks

[Ondrej_Lepa]

Hi Aviv,

you might be right - testing that in Lab I see that adoption / configuration push could be quite higher
ROUTER#service pktcap on bridge filter mint and host 88.88.88.88

7 9:21:18.149772 UDP: 88.88.88.88 > 192.168.7.205 ports 24576 > 24576, data length 72, DSCP 0| RDP/STREAM 4D.87.1A.F0/58143 > 12.34.04.07/11 adoption/config, AF, seq 55626, ack 8144, win 10, data 0
6 9:21:18.149758 UDP: 88.88.88.88 > 192.168.7.205 ports 24576 > 24576, data length 877, DSCP 0| RDP/STREAM 4D.87.1A.F0/58143 > 12.34.04.07/11 adoption/config, AP, seq 55625, ack 8144, win 10, data 805MTU of 504 is very low value - this could cause general problems to MINT communication. I'd stay with formula
Highest DF PING MTU - 100 bytes = WAN crossing MINT MTURegards,
Ondrej

[Aviv_Kedem]

Thanks for your reply.
Just yesterday I saw some AP failed to adopt to VC because of maximum MTU of 504.
But allowed MTU size can be configured only between 900-1500, and in this condition is caused adoption to fail at all. So this is some extreme situation but it caused Me to think about MTU size.