Hi, if the interface configuration on the FlexFabric (Comware) included:
flow-control receive enable
then it means that Rx-mode generic flow control was enabled (by using the flow-control receive enable command): with this Rx-mode generic flow control enabled, that switch interface can receive flow control frames from connected peer (provided that that peer has flow control enabled) but it cannot send flow control frames. It means:
- When congestion occurs, the interface cannot send flow control frames to its peer.
- When the interface receives a flow control frame from its peer, it suspends sending packets to its peer.
To handle unidirectional traffic congestion on a link, configure the flow-control receive enable command at one end and the flow-control command at the other end.
The corresponding setting on ArubaOS-CX based switches should be:
flow-control rx
As example, considering an HPE Nimble peer device connected to an ArubaOS-CX based switch (or VSX):
interface 1/1/13
description Nimble Data Path A
no shutdown
mtu 9198
flow-control rx
no routing
vlan access 110
interface 1/1/14
description Nimble Data Path B
no shutdown
mtu 9198
flow-control rx
no routing
vlan access 110
Have a look here.
-------------------------------------------