Service Manual

Field Description
Local DCBx Status: DCBx Max Version Supported Highest DCBx version supported in Control TLVs.
Local DCBx Status: Sequence Number Sequence number transmitted in Control TLVs.
Local DCBx Status: Acknowledgment Number Acknowledgement number transmitted in Control TLVs.
Local DCBx Status: Protocol State Current operational state of DCBx protocol: ACK or IN-SYNC.
Peer DCBx Status: DCBx Operational Version DCBx version advertised in Control TLVs received from peer
device.
Peer DCBx Status: DCBx Max Version Supported Highest DCBx version supported in Control TLVs received from
peer device.
Peer DCBx Status: Sequence Number Sequence number transmitted in Control TLVs received from
peer device.
Peer DCBx Status: Acknowledgment Number Acknowledgement number transmitted in Control TLVs received
from peer device.
Total DCBx Frames transmitted Number of DCBx frames sent from local port.
Total DCBx Frames received Number of DCBx frames received from remote peer port.
Total DCBx Frame errors Number of DCBx frames with errors received.
Total DCBx Frames unrecognized Number of unrecognizable DCBx frames received.
Generation of PFC for a Priority for Untagged Packets
In order to generate PFC for a particular priority for untagged packets, and conguring PFC for that priority, you should nd the
queue number associated with priority from TABLE 1 and Associate a DCB map to forward the matched DSCP packet to that queue.
PFC frames gets generated with PFC priority associated with the queue when the queue gets congested.
Operations on Untagged Packets
The below is example for enabling PFC for priority 2 for tagged packets. Priority (Packet Dot1p) 2 will be mapped to PG6 on
PRIO2PG setting. All other Priorities for which PFC is not enabled are mapped to default PG – PG7.
Classication rules on ingress (Ingress FP CAM region) matches incoming packet-dot1p and assigns an internal priority (to select
queue as per Table 1 and Table 2).
The internal Priority assigned for the packet by Ingress FP is used by the memory management unit (MMU) to assign the packet to
right queue by indexing the internal-priority to queue map table (TABLE 1) in hardware.
PRIO2COS setting for honoring the PFC protocol packets from the Peer switches is as per above Packet-Dot1p->queue table (Table
2).
The packets that come in with packet-dot1p 2 alone will be assigned to PG6 on ingress.
The packets that come in with packet-dot1p 2 alone will use Q1 (as per dot1p to Queue classication – Table 2) on the egress port.
• When Peer sends a PFC message for Priority 2, based on above PRIO2COS table (TABLE 2), Queue 1 is halted.
• Queue 1 starts buering the packets with Dot1p 2. This causes PG6 buer counter to increase on the ingress, since P-dot1p 2 is
mapped to PG6.
• As the PG6 watermark threshold is reached, PFC will be generated for dot1p 2.
Data Center Bridging (DCB)
241