Related Documentation
- QFX Series
- Configuring CoS PFC (Congestion Notification Profiles)
- Example: Configuring Two or More Lossless FCoE IEEE 802.1p Priorities on Different FCoE Transit Switch Interfaces
- Example: Configuring Two or More Lossless FCoE Priorities on the Same FCoE Transit Switch Interface
- Example: Configuring Lossless FCoE Traffic When the Converged Ethernet Network Does Not Use IEEE 802.1p Priority 3 for FCoE Traffic (FCoE Transit Switch)
- Example: Configuring Lossless IEEE 802.1p Priorities on Ethernet Interfaces for Multiple Applications (FCoE and iSCSI)
- Understanding CoS Flow Control (Ethernet PAUSE and PFC)
- Understanding CoS IEEE 802.1p Priorities for Lossless Traffic Flows
mru
Syntax
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 12.3 for the QFX Series.
Description
Configure the maximum receive unit (MRU) of the interface in bytes (incoming packet sizes must be less than or equal to the MRU, or the packets are dropped). The system uses the MRU and the cable length to calculate the amount of buffer headroom reserved to support priority-based flow control (PFC). The lower the MRU and the shorter the cable length, the less headroom buffer space is required for PFC.
![]() | Note: You can also set a maximum transmission unit (MTU) value (the largest packet size the interface sends) for interfaces by including the mtu statement at the [edit interfaces interface-name] hierarchy level. |
Default
For priority 3 traffic, the default MRU value is 2500 bytes.
For priority 4 traffic, the default MRU value is 9612 bytes.
Options
mru-value—Value of the maximum packet receive unit size in bytes (generally from 1500 to 9216 bytes, but there is no configuration restriction).
Required Privilege Level
interfaces—To view this statement in the
configuration.
interface-control—To add this
statement to the configuration.
Related Documentation
- QFX Series
- Configuring CoS PFC (Congestion Notification Profiles)
- Example: Configuring Two or More Lossless FCoE IEEE 802.1p Priorities on Different FCoE Transit Switch Interfaces
- Example: Configuring Two or More Lossless FCoE Priorities on the Same FCoE Transit Switch Interface
- Example: Configuring Lossless FCoE Traffic When the Converged Ethernet Network Does Not Use IEEE 802.1p Priority 3 for FCoE Traffic (FCoE Transit Switch)
- Example: Configuring Lossless IEEE 802.1p Priorities on Ethernet Interfaces for Multiple Applications (FCoE and iSCSI)
- Understanding CoS Flow Control (Ethernet PAUSE and PFC)
- Understanding CoS IEEE 802.1p Priorities for Lossless Traffic Flows


