Fabric Manager Users Guide, Version 6.1, Revision A - QLogic

1–Overview of the QLogic Fabric Manager Suite
Congestion Control Architecture
SM Configuration
BM Configuration
The following SM specific parameters are excluded:
TrapLogSuppressTriggerInterval, SmPerfDebug, SaPerfDebug, DebugDor,
DebugVf, DebugJm, DebugLidAssign, LoopTestOn, LoopTestPackets,
LoopTestFastMode, LID, DynamicPortAlloc, SaRmppChecksum
Also all MLIDShared, CongestionControl, and AdaptiveRouting parameters are
ignored when the given section is not enabled.
The following BM specific parameters are excluded:
DebugFlag
PM Configuration
The following PM specific parameters are excluded:
ThresholdsExceededMsgLimit (entire section), SweepErrorsLogThreshold
FE Configuration
The following FE specific parameters are excluded:
TcpPort
Congestion Control Architecture
The objective of InfiniBand Congestion Control Architecture (CCA) is to reduce
the propagation of fabric congestion during oversubscription scenarios such as
many-to-one traffic. By configuring CCA-specific switch and channel adapter
parameters, the fabric can throttle the packet transmit rate on the sending hosts,
thereby preventing the spread of congestion through the fabric. Refer to
InfiniBand Architecture Specification Volume 1, Release 1.2.1, Annex A10, for a
complete description of Congestion Control.
QLogic's implementation of CCA differs from the InfiniBand Trade Association
(IBTA) specification in three ways:
1. QLogic's approach to fabric congestion is wholistic in nature and addresses
congestion through a combination of features: Adaptive routing, dispersive
routing and CCA.
2. The QLogic Adaptive Routing and Dispersive routing features are designed
to optimize and balance traffic in the core ISLs of the fabric.
3. The QLogic CCA implementation in the QLogic Fabric Manager is focused
on preventing the spread of congestion into the core fabric from over
subscribed Host Channel Adapters (receivers of many to one traffic).
IB0054608-01 B 1-9