A GPU Network Product Is End-of-Sale. Must the Rack Be Replaced?

Separate ordering, shipment and service milestones

NVIDIA defines End of Sales (EOS) as the last ordering date through its point-of-sale mechanisms; the product and initial support cease being offered for sale afterward. End of Service Life (EOSL) is the last day a service contract is honored, with no formal service or support afterward and no renewal beyond it. End of Life (EOL) describes the wider lifecycle process containing those milestones.

The guide describes five years of service as typical unless otherwise noted. Its overview identifies the guide as non-binding. Establish the applicable product milestone and the customer's actual entitlement instead of calculating a guaranteed service end date from that general description. A product's EOSL does not grant coverage up to that date; an individual entitlement may end earlier.

Also request any applicable final-shipment cutoff. An order deadline answers when a purchase can be placed; a shipment cutoff answers when deliveries end under the applicable notice or order terms. Neither is the customer's service expiry. Keep each milestone attached to its exact product scope and evidence, with missing dates left unresolved.

References: [N1][N5][N4]

Read the ordering part before declaring a family unavailable

NVIDIA's SN4000 ordering page, updated February 23, 2026, lists MSN4600-VS2FC and MSN4600-VS2RC in its legacy EOL table and says those OPNs are no longer available for ordering. The same page separately lists MSN4600-CS2FC and MSN4600-CS2RC as Mass Production entries. Those rows do not establish an interchangeable replacement.

The finding is specific to ordering part numbers, not every SN4600 or SN4000 product. It supplies neither a supplier stock check nor an EOSL or final-shipment date for the customer's units. Match the quoted OPN to the relevant row, then obtain the actual supplier response and product-support evidence needed for the proposed purchase.

References: [N2]

Match the software branch to the actual configuration

NVIDIA's Long-Term Support (LTS) page labels its April 2024 branch Cumulus ONLY and supported through 2027. Its table names releases including Cumulus 5.9.1 and 5.9.4. That is a product-and-release maintenance window, not an extension of hardware ordering or service life. It does not prove that a particular legacy OPN or installed customer stack is supported.

NVIDIA's separate software policy says support depends on applicable runtime and hardware requirements. Obtain the appointed product-support owner's response for the actual hardware, selected software releases and proposed use. Record the scope and period that response covers. A branch heading cannot substitute for that match, and a response for the existing fleet does not automatically cover an expanded or altered configuration.

References: [N3][N4]

Work through six existing switches and two additions

Fictional example LC-08 starts with six installed NVIDIA network switches and a requirement for eight switches throughout a 24-month planning period. Its equipment applicability, supplier responses and coverage windows are invented inputs, with no real fleet, entitlement or product approval represented. The counts describe equipment populations; they establish no topology, port allocation or performance capacity.

The expansion request quotes two MSN4600-VS2FC units, an OPN in the published no-longer-orderable table. There is no supplier-confirmed delivery for that line. A separate fictional offer confirms quantity and delivery for two units of an identified alternative A, without assigning A a real model. That supply response leaves the proposed combined configuration awaiting the appointed product-support owner's response.

Now stipulate that the product-support owner returns confirmation for the combined configuration at the intended location. For each of the six retained units, all required coverage layers are confirmed for [0, 18 months). For each of the two selected additions, all required coverage layers are confirmed for [0, 24 months). Both intervals run from the same fictional start, t0, and exclude their ending point. The required eight-unit operating horizon is [0, 24 months).

These windows are case inputs, not dates calculated from NVIDIA's typical service period or the named Cumulus branch. Aligning their starts makes the comparison explicit: six retained plus two additions meets the eight-unit population, while the coverage available to that whole population still needs comparison with the required horizon.

References: [N2]

Compare retaining, expanding and replacing equipment

Keeping the six existing units means maintaining the stipulated configuration within its confirmed service conditions and period. It creates no automatic switch-removal project and buys none of the two requested additions. The buyer must explicitly defer or otherwise resolve the expansion requirement. Retention for the full 24 months would also need a coverage response beyond the six units' confirmed 18-month window. Any separately identified physical correction can have its own scope; a lifecycle label alone supplies no defect or replacement instruction.

Expanding with alternative A adds two units while retaining six. In LC-08, the returned configuration response supplies the stipulated applicability and coverage windows; the supplier response supplies quantity and delivery. Neither response answers the other's question. The proposed physical package needs installation positions, mounting and handling inputs, site interfaces, affected connections, labels and revised records against the approved selection. Adding two devices can still affect shared connections or existing equipment; the device count does not establish a non-disruptive installation.

Broader replacement would remove the six existing units and install eight selected replacement units for the same stipulated target. It creates a larger change population: the released removals, new installation, affected cabling and records, and handoff of removed assets all need definition. The selected replacement configuration must also have evidence for the required 24-month horizon; eight new units alone cannot establish it. The buyer may compare this path for its operating horizon, capacity or approved network arrangement even while the existing fleet remains supported. Its justification must come from those requirements and the applicable evidence, rather than the stopped ordering of one expansion OPN.

These are purchasing alternatives, not a swap design or field procedure. The customer and its appointed technical, operating and facility owners determine product applicability, system changes and work release. Continued operation beyond confirmed support is not an assumed fourth option.

Compare the same unit population and operating horizon

For the LC-08 expansion, the common confirmed period is the intersection of the coverage windows for all eight required units and all their required layers. The six retained units' [0, 18 months) window overlaps the additions' [0, 24 months) window for [0, 18 months). Thus the evidence covers the entire eight-unit population for the first 18 months. During [18, 24 months), coverage is confirmed for the two additions, while the corresponding response for the six retained units remains unanswered. The available evidence does not establish that those six units are unsupported during that final interval.

An aggregate can hide this exact gap. Six units with 18 months each and two with 24 months each give 6 × 18 + 2 × 24 = 156 device-months. Dividing by eight gives an average of 19.5 months per unit. Neither number supplies 24 months of confirmed coverage for every unit. The additions' longer windows cannot fill the retained units' missing interval; coverage remains attached to its applicable assets, configuration and terms.

Return a precise request: establish all required coverage layers for each of the six retained units during [18, 24 months), or define a supported alternative meeting the same eight-unit, 24-month requirement. Obtain the actual available response rather than assuming renewal or extension. A software branch's later calendar year cannot close the hardware-service question. The unresolved future interval also leaves the separate confirmation for the first 18 months intact.

Compare prices against that same population and horizon. Keeping six leaves the two-unit increment unresolved; expansion provides eight with the stated coverage gap; broader replacement still needs its selected configuration and coverage evidence. For the alternatives intended to deliver eight throughout the full period, compare equipment and software scope, supplier-confirmed material and delivery, physical changes, required checks and the receiving owners' handoff. Keep unanswered costs or lead times visible.

Keep support-role allocation and spare-stock planning with their own decisions. A maintenance entitlement, a boxed spare and a confirmed purchase offer are different inputs. Carry their constraints into the refresh comparison and identify which existing assets each alternative retains, changes or removes. A network-equipment replacement decision does not, by itself, place GPU servers or rack enclosures in the removal population.

Bring the chosen equipment boundary into the physical project

Once the equipment and operating owners have selected the applicable path, identify the retained units, proposed additions or removals, affected connections, material supplier, site restrictions and intended handoff. Establish cable-plant retention separately against the selected interfaces and routes. A device lifecycle finding cannot settle which trunks, terminations or equipment cords remain suitable.

Leviathan's hardware-refresh and physical-remediation service can discuss agreed equipment replacement, recabling, label changes, accessible physical checks and revised installation records. Product-support eligibility, software or network configuration and OEM warranty repair remain with the appointed parties. Any instrument testing needs a separately confirmed scope and criteria.

Use the linked project inquiry with a nonconfidential summary of the existing and proposed equipment, requested physical tasks, site, target window and unresolved inputs. That makes the physical request specific whether the buyer retains the existing fleet, expands it or selects a broader refresh.