Restrictions for configuring per-port MTU
Several restrictions apply to configuring per-port MTU on Cisco Catalyst switches. These restrictions vary depending on the platform, interface type, and other configuration conditions.
General restrictions:
-
Per-port MTU cannot be configured on the management port.
-
Do not configure the per-port MTU value while traffic is flowing (e.g., during active data transmission).
Port-channel restrictions:
-
Members of a port channel cannot be configured with a per-port MTU value; they derive their MTU from the port-channel MTU configuration.
-
Per-port MTU can be configured on port-channel interfaces but not on the port-channel members.
Subinterface restrictions:
-
Per-port MTU is not supported on subinterfaces or port-channel subinterfaces.
Layer 2 MTU restrictions:
-
Ingress and egress Layer 2 MTU is derived from per-port MTU. If per-port MTU is not configured, the System MTU is used.
-
On ingress ports configured with Layer 2 MTU, packets that exceed the configured MTU size are dropped.
Platform-specific restrictions:
-
On Cisco Catalyst 9610 Series Supervisor 2 Module, the following restrictions are applicable:
-
If no protocol-specific MTU configuration is present, per-port MTU is used as protocol-specific MTU.
-
If per-port MTU is not configured, System MTU is used as protocol-specific MTU.
-
Feedback