Information About Link Level Flow Control; Link Level Flow Control On Interfaces - Cisco Nexus 9000 Series Configuration Manual

Nx-os quality of service configuration, release 7.x
Hide thumbs Also See for Nexus 9000 Series:
Table of Contents

Advertisement

Information About Link Level Flow Control

• Enabling link level flow control requires a part of the buffer to be reserved. This reduces the available
• Data Center Bridging Exchange Protocol (DCBX) is not supported.
• Configuration time quanta of the pause frames is not supported.
• On each Ethernet interface, the switch can enable either PFC or LLFC, but not both.
• Only pure CoS-based classification of traffic classes is supported.
• Setting of pause threshold values is restricted.
• Configuring Link Level Flow Control on the interfaces will flap the interfaces which results in a
• When a no-drop QoS group is configured, you must ensure that packets received on ports that do not
• Only a no-drop QoS group is capable of generating link level pause frames.
• Weighted Random Early Detection (WRED) should not be enabled on a no-drop class because it can
• It is recommended to use default buffer sizes for no-drop classes because if the buffer size is specified
• It is recommended to change the LLFC configuration when there is no traffic, otherwise packets already
• Beginning with NX-OS 7.0(3)I1(2), link level flow control and PFC are supported on Cisco Nexus 9300
• 3232C does not support a combination of cut-through and LLFC enabled ports. Cut-through and LLFC
Information About Link Level Flow Control

Link Level Flow Control on Interfaces

When link level flow control is configured the system changes the interface state to Down if the specified
interface is in UP state and then applies the flow control configuration. After the configuration is successfully
applied to the interface, the system restores the interface to the UP state.
Cisco Nexus 9000 Series NX-OS Quality of Service Configuration Guide, Release 7.x
140
shared buffer space.
Note
When both PFC and LLFC are enabled, LLFC is selected.
momentary traffic loss.
have flow control send-on configured are not classified to a no-drop QoS group.
cause egress queue drops.
through CLI, it will allocate the same buffer size for all ports irrespective of the link speed, and MTU
size.
in the MMU of the system may not get the expected treatment.
platform switches and line cards that contain the ALE (Application Leaf Engine).
are mutually exclusive and will work without the presence of the other feature. Post 9.3(8) release, on a
cut-through enabled switch, if LLFC is enabled on a port, that port will operate in store and forward
mode.
Configuring Link Level Flow Control

Advertisement

Table of Contents
loading

Table of Contents