A city prepares to load an AI fabric and must check leaf and spine software currency. What Domain 4 confirmation is required?
Select an answer to reveal the explanation.
Short Explanation
Before you load the city AI fabric, verify that leaf and spine firmware and software versions match the municipal standard; forwarding traffic alone does not establish currency. This validation helps ensure the participating switches meet the approved image requirements.
Full Explanation
Before a city loads an AI fabric, Domain 4 requires confirmation that leaf and spine firmware and software versions match the municipal standard—not merely that packets forward. Verifying the approved versions before load helps prevent mixed-image rows that lack required features, bug fixes, congestion control, or telemetry for GPU collectives. Skipping version checks because ports forward traffic is insufficient: outdated images may still switch frames while missing capabilities the AI fabric design assumes. Assuming factory-installed images are already current and compliant ignores that shipping defaults can lag the approved train used by peer rows. Checking only front-panel LED colors validates power and status indications, not software currency. Switch firmware and software confirmation is a validation gate before production load for city AI capacity. Caveat: maintenance windows may stage rolling upgrades after go-live for existing fabrics, but loading a new or revalidated city fabric still requires approved versions on participating switches. Practical check: inventory leaf and spine version strings against the city’s approved AI fabric image list, remediate outliers, re-confirm after upgrades, and attach the inventory to the load-ready package.