Drag and Drop Question Match each Data Center Bridging (DCB) protocol component with its description. Answer:

Question

Exhibit

Answer Area

Explanation

DCB Protocol Components - Match Explanation

Overview of DCB

Data Center Bridging (DCB) is a suite of IEEE 802.1 extensions that enhance Ethernet for lossless, low-latency data center networking (supporting workloads like storage - iSCSI, FCoE - and RDMA/RoCE).

Correct Arrangement & Technical Reasoning

1. DCBX - Data Center Bridging Exchange

Role: The negotiation/discovery protocol for DCB.

• Built on top of LLDP (Link Layer Discovery Protocol)
• Allows directly connected peers (switches, NICs) to advertise, negotiate, and synchronize DCB capabilities and configurations
• It is the carrier that delivers ETS, PFC, and APP settings between devices
• Why it's first: DCBX is the foundational signaling mechanism - without it, the other three protocols have no way to be negotiated between endpoints

2. ETS - Enhanced Transmission Selection (IEEE 802.1Qaz)

Role: Bandwidth allocation and traffic scheduling.

• Groups traffic into classes and assigns minimum guaranteed bandwidth percentages to each
• Works alongside a scheduler (e.g., strict priority or weighted round-robin)
• Why it's second: ETS defines the resource sharing policy - it sets the stage for how bandwidth is divided before flow control (PFC) is applied per class

3. PFC - Priority Flow Control (IEEE 802.1Qbb)

Role: Per-priority, lossless flow control.

• Extends 802.3x PAUSE frames to operate on individual priority queues (0–7) rather than the entire link
• Allows a receiver to pause only specific priorities, keeping other traffic flowing
• Critical for lossless transport of storage and RDMA traffic
• Why it's third: PFC acts on the priority classes that ETS has defined - it depends on the traffic class structure ETS establishes

4. APP - Application Priority (APP TLV within DCBX)

Role: Maps applications/protocols to priority classes.

• Carried as a TLV (Type-Length-Value) inside DCBX messages
• Associates specific application protocols (e.g., FCoE = priority 3, iSCSI = priority 4) with a traffic class priority
• Why it's last: APP is the policy layer - it tells endpoints which priority queue a specific application's traffic should use, consuming the infrastructure defined by ETS and PFC

Common Mistakes & Misconceptions

Memory Aid

DCBX discovers → ETS shares bandwidth → PFC prevents loss → APP assigns apps

Each layer builds on the previous: discover → allocate → protect → assign.

No community discussion yet for this question.