A parks computer-vision fabric must update Spectrum-X PFC and ECN settings. How should operators make the change?
Select an answer to reveal the explanation.
Short Explanation
You shouldn’t set PFC and ECN through one-off CLI edits on each switch. Revise the NVUE template, push the Spectrum-X QoS change, and keep the story auditable.
Full Explanation
A parks computer-vision fabric updating Spectrum-X PFC and ECN settings must change QoS through the same template-driven path used for other municipal Spectrum baselines. An NVUE template revision that updates PFC and ECN keeps congestion-management settings versioned, reviewable, and consistently applied across parks CV leafs that carry RoCE traffic for vision inference and training. Direct switch CLI edits that set PFC and ECN per port recreate drift and erase change history precisely when QoS tuning needs auditability for civic operations. Pushing an InfiniBand UFM policy that programs PFC and ECN still targets IB fabric management rather than Spectrum-X Ethernet QoS control, so it does not reliably configure parks CV leafs. A What Just Happened rule that captures PFC and ECN events only observes congestion; it does not configure PFC and ECN, and leaves parks CV operators without the actual QoS change during lossless tuning. Exam caveat: PFC and ECN must remain end-to-end coherent with host and peer leaf settings; a template that sets only one side can worsen lossless behavior under load. Operational check: revise the NVUE template for PFC/ECN, review the diff in git, apply to a parks staging leaf, confirm WJH/congestion counters and RoCE test traffic behave as expected, then roll out to production CV leafs.