Create an Acceptance Plan for a Mixed-Generation AI Fabric
Independent editorial analysis of third-party public reports. No SwitchInfra implementation or performance claim.
Create an Acceptance Plan for a Mixed-Generation AI Fabric
Create an Acceptance Plan for a Mixed-Generation AI Fabric
Overview
This is a hypothetical engineering scenario, informed by official interconnect documentation and historical deployment practice. It is not a customer success story or an assertion that a proposed bill of materials has been validated.
The scenario
An operator wants to add new compute nodes while retaining part of an existing fabric. The project contains several link types: older endpoints, newer switch ports, breakout connections and management links. The immediate objective is to produce a supported port map and a repeatable acceptance record.
Start with the retained equipment
Inventory the existing devices and firmware before selecting replacements or expansion parts. Record the exact ports available, their configured mode and the route each cable must take. Identify links that must remain unchanged during installation. Then create a link schedule for the expansion. Each row should define both endpoints, the intended protocol and rate, the proposed order code and the evidence supporting that combination. NVIDIA’s LinkX overview explains the broad interconnect categories, while the applicable product and release documentation must resolve the actual pairings. LinkX documentation
Classify uncertainty before procurement
Place each link in one of three groups: documented and ready for validation; awaiting an exact-part clarification; or dependent on an engineering-sample component. Do not treat these groups as interchangeable commercial options. For example, the versioned ConnectX-9 compatibility list distinguishes lifecycle phases and protocol support. An InfiniBand-only row should not become an Ethernet recommendation just because a related module supports both. Compatibility and lifecycle evidence If a connector description conflicts across official pages, pause that pairing and request clarification. An adapter, fiber or breakout should not be improvised to bridge the uncertainty.
Validate a representative slice
Before a wider rollout, test the proposed combination on a small slice that uses the actual endpoints and software. Check recognition, negotiated mode, sustained traffic and error behavior. For split links, exercise all branches together and confirm the intended port mapping. Repeat under the expected thermal conditions and with competing traffic where relevant. Agree the acceptable result in advance. A link-up screenshot alone does not establish the performance or stability needed for production.
Hand over a controlled expansion package
The final package should include the approved port map, exact bill of materials, open exceptions, installation sequence, rollback steps and test results. Preserve which components were actually tested so future changes can be assessed against a known baseline. This solution delivers an engineering decision process. It makes no claim that an unspecified new cable, prototype optic or alternate switch has already succeeded in another organization’s cluster. Sources checked: 10 October 2026. This article discusses third-party evidence or an explicitly labeled engineering scenario; it does not establish a reseller’s delivery history, current stock or exact-SKU deployment.