MTU

What this chapter covers

The MTU chapter explains how large a packet or frame can be on a switched network, and what goes wrong when devices disagree.

It matters for a switching engineer because bridges and switches cannot fragment. A size mismatch on a switched path shows up as lost frames with no error message, so you need a method to find it.

The four syllabus topics are the bridge overview, L2MTU, jumbo frames and the potential MTU issues.

After this chapter you should be able to do the following:

• Explain why a bridge drops an oversized frame without any message.
• Read the mtu and l2mtu values and say what each one limits.
• Plan a jumbo frame path, and name every place that needs a change.
• Test a path with a ping of a chosen size and the do not fragment flag.
• Name the usual causes of an MTU fault, such as tags, tunnels and blocked ICMP.

How the topics fit together

The pages move from the rule, to the settings, to the faults.

A bridge forwards frames and drops what is too big. L2MTU and MTU are the two numbers that decide what is too big. Jumbo frames raise those numbers on purpose, and every added tag or tunnel raises the demand without warning.

How to use these pages

Each topic page has the same shape, so you can skim for what you need.

• What it is: the idea in plain words.
• How it works: the mechanism, with diagrams and example commands.
• What to remember for the exam: the facts to memorise.
• Common mistakes: the classic traps.
• Check yourself: three questions to test your understanding.

Practise on a lab with two routers and a switch between them. Change the MTU on one side, send pings with different sizes, and watch where they stop. Seeing a silent drop once makes the theory easy to remember.