County health discovery finds a BlueField-3 still on factory firmware during rack acceptance. What should operators do?
Select an answer to reveal the explanation.
Short Explanation
Factory BF3 firmware is a hold, not a green light—keep that county health node out of production until versions match the approved levels.
Full Explanation
County health discovery that finds a BlueField-3 still on factory firmware during rack acceptance means the node is not production-ready for the AI fabric. Holding the node out of production until BlueField-3 firmware and software match the approved levels protects the cluster from unvalidated DPU state and incomplete offload capability. Placing the node in production queues immediately imports factory skew into scheduling and can strand jobs that assume DOCA-aligned behavior. Documenting the factory level as equivalent to the approved image without checking falsifies the acceptance record and creates support debt. Disabling DPU health checks to clear the acceptance blocker removes the control instead of remediating the version gap. Domain 4 expects exclusion and remediation when BF3 levels fail confirmation during rack acceptance. Caveat: some racks may stage DPU updates in a maintenance VLAN before host OS bring-up; the constant is that production placement waits on approved levels, not paperwork equivalence. Operational check: quarantine the county health node, update BF3 firmware/software to the approved train, re-query versions, run basic DPU health, then clear it for production queues only after the matrix matches.