I'm not sure if your question was answered, but I thought I'd explain a little more about how flowcontrol works with the Nexus so you know where the best practices are coming from.
Flowcontrol Receive (Rx) is when another device sends US pause frames. There are two protocols we support to do this: 802.3x and Priority Flow Control. Flowcontrol Transmit (Tx) is when WE send pause frames out.
A pause frame is a communication sent by a switch to tell the link on the other end to slow down sending traffic, because we can't handle it, or somewhere downstream can't handle it. Its always a good thing to have, because without it we or the other switch will drop frames and in storage environments the retransmits that result can be disastrous.
So on to your question,
What action does the Nexus switch take in response to receiving these pause frames?
The action depends on what we have configured.
If we don't have Flow Control Rx turned on, we will drop the packet and take no action, after ticking the counter to show we received it. If we do have Flow Control Rx turned on, we will receive pause frames and send traffic to your NIC slower If we have Flow Control Tx turned on, we will also have the ability to send pause frames to you and inform you if you are sending data too fast for the target to receieve (assuming the target communicates to us that it needs the traffic to be slowed, and assuming we have flowcontrol enabled on all interfaces in the path to the target).
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...
Cisco Documents are usually accurate, but when it came to the document
on Cisco APIC Signature-Based Transactions it was slightly off the mark.
This document is for those novices to API like me who cant seem to
figure out how to go about performing signat...