Windows Server 2xxx "Microsoft network adapter multiplexor" MTU (Jumbo Frame) setting Missing?

Question

All:

Why does the logical meta-interface "Microsoft network adapter multiplexor" feature a MTU (Jumbo Frame) setting via the GUI?

It can be defined in PowerShell using "set-netipinterface" and similar commands.

Imagine a scenario:

* where there are two NIC Teams, LACP or failover, defined using the same pair of underlying physical interfaces.

* Two interfaces are having two different VLAN Tags (or untagged)

* One VLAN is routed and must be set to MTU 1500 (lets assume that Layer3 routers don't support jumbo frames)

* One VLAN is bridged only and can support MTU jumbo 9000 bytes

* The switchport MTU is set to 9000

* The switchport mode is set to VLAN Trunk

* The underlying interfaces must have Jumbo Frames enabled and set to MTU set to 9000

* The Layer3 interface (Microsoft network adapter multiplexor) for routed VLAN must be set to 1500 Bytes

* The Layer3 interface (Microsoft network adapter multiplexor) for switched VLAN must set to 9000 bytes

This is very command and standard practice in VMWare, FreeBSD, and GNU/Linux. Yet in Windows Server this simple configuration escapes us and/or one has to do it via PowerShell?

~BAS

Answer 1

Supporting screenshots: