This counter records the number of frames dropped on transmit at this flow point because the flow point itself was in a blocked state. A nonzero count strongly signals to the admin that this flow point has been administratively or protectively blocked, which would explain a complete or partial outage of the service riding on it. For example, if a customer's flow point was blocked as part of a loop-protection action, the admin would see cmFlowPointStatsFdTxFb incrementing for the duration of the block and use that to confirm the block, not a separate fault, is the cause of the outage.