A Q3400-RA NVOS upgrade may involve more than replacing the operating system image. The process can also include CPLD, BIOS, BMC, FPGA, ERoT, or other platform firmware components. This guide explains what can be confirmed from public NVOS documentation, why Q3400-RA CPLD files may require support access, and what information to prepare before opening an upgrade request.
What the Q3400-RA NVOS Upgrade Includes
The Q3400-RA is an NVIDIA Quantum XDR InfiniBand switch managed through NVOS. Depending on the target release and supplied package, an upgrade may affect both the operating system and platform firmware.
| Component | Why it may matter | What to confirm |
|---|---|---|
| NVOS | Provides the switch operating system and management functions. | Current image, target image, installation method, and reboot behavior. |
| CPLD | Controls platform-level hardware functions and may be required by the target release. | Exact image, hardware revision, version mapping, and power-cycle requirement. |
| BIOS | May be included in a broader platform firmware update. | Whether the target NVOS package requires a BIOS update. |
| BMC, FPGA, or ERoT | May be part of the approved system firmware sequence. | Required component order and post-upgrade verification method. |
The correct process depends on the exact Q3400-RA system configuration, hardware revision, current firmware state, and target NVOS release. A procedure for another Quantum switch should not be treated as a direct substitute.
Send the exact model, firmware versions, and target NVOS release.
Why the CPLD Firmware May Not Be Publicly Downloadable
CPLD firmware is closely tied to the switch platform. A file that appears to have the correct component name may still be unsuitable for a specific hardware revision or system configuration.
For this reason, a Q3400-RA CPLD image may be supplied as part of a larger firmware bundle or made available only through an approved NVIDIA support process. The file may not appear as a separate public download.
- The CPLD image may be packaged with other platform firmware.
- The package may require unpacking before installation.
- The correct image may depend on the hardware revision.
- The upgrade may require a defined sequence and power cycle.
- The file may be provided after the system details are reviewed.
If the NVOS upgrade guide requires a CPLD update but no approved Q3400-RA file is available, open the appropriate NVIDIA support request. Do not download or install a CPLD image from an unofficial repository.
The support response for the Q3400-RA CPLD question was to open an SF ticket. This should be understood as case-specific support guidance, not as a public guarantee that every Q3400-RA firmware component is available through the same channel.
How to Verify NVOS and CPLD Version Mapping
Do not assume that one CPLD version applies to every NVOS release. The correct combination may depend on the current firmware state, hardware revision, target version, and contents of the approved firmware bundle.
Collect the current versions first
Save the output together with the device model, OPN, serial number, hardware revision, and target NVOS release. These details allow support to check whether the proposed CPLD image belongs to the correct platform and upgrade path.
Ask for a complete mapping, not only a file
A useful support response should identify the approved NVOS image, CPLD image, component order, reboot or power-cycle requirement, and post-upgrade verification method.
- Confirm the approved target NVOS version.
- Confirm whether CPLD must be updated before NVOS.
- Confirm the exact CPLD image or firmware bundle.
- Confirm whether BIOS, BMC, FPGA, or ERoT updates are also required.
- Confirm the rollback and recovery procedure.
- Confirm the expected impact on the InfiniBand fabric.
The general component-installation and verification process is described in the NVIDIA NVOS upgrade documentation. Use the Q3400-RA-specific package and support instructions when they differ from the general example.
Pre-Upgrade Checklist for Q3400-RA
Complete the following checks before scheduling the maintenance window.
Confirm the hardware identity
- Exact Q3400-RA model and OPN
- Serial number and hardware revision
- Current NVOS version
- Current CPLD, BIOS, and BMC versions
- Power and cooling configuration
- UFM or other fabric-management environment
Check the system state
Review the switch for existing alarms, management instability, or fabric errors. An upgrade should not be used to mask an unexplained hardware problem.
Prepare access and recovery
- Back up the current switch configuration.
- Keep console or out-of-band access available.
- Record the current NVOS image and firmware versions.
- Confirm available storage for the firmware files.
- Define the maintenance window and escalation contact.
- Prepare a rollback or recovery procedure.
Review the fabric impact
An NVOS upgrade may make the switch unavailable while the image and firmware are being installed. Confirm redundant paths, connected HCAs, UFM dependencies, fabric-management requirements, and expected service impact before proceeding.
Recommended NVOS and CPLD Upgrade Sequence
The exact sequence must come from the approved Q3400-RA firmware package or NVIDIA Support. A general workflow may include the following stages:
- Confirm the hardware identity and current firmware versions.
- Obtain the approved NVOS and platform firmware package.
- Unpack the firmware bundle if required.
- Install the approved CPLD and other required platform components.
- Install the NVOS system image.
- Reboot or power-cycle the system as instructed.
- Verify all firmware versions after startup.
- Confirm management and InfiniBand fabric recovery.
CPLD component command format
The following commands show the general NVOS command structure. The URL and file name are placeholders and must be replaced only with values supplied for the exact Q3400-RA system.
Some firmware packages require the CPLD bundle to be unpacked before installation. If the supplied instructions include a burn file, refresh file, or separate power-cycle step, follow that sequence exactly.
NVOS installation command format
Do not use these commands with an unverified file. The command structure is general; the approved image, component order, reboot method, and recovery instructions are platform- and release-dependent.
Verify Firmware After the Upgrade
A switch that boots successfully is not necessarily fully upgraded. Verify the NVOS image and every required platform component separately.
- The intended NVOS image is current and active.
- The CPLD version matches the approved target.
- BIOS, BMC, FPGA, and other required components show the expected versions.
- No new hardware or platform alarms are present.
- Management access is stable.
- Connected links and fabric-management services are operational.
- The InfiniBand fabric has recovered as expected.
Keep the post-upgrade output with the support case, firmware package identifier, and maintenance record. This information is useful if the system requires additional troubleshooting or a later rollback.
Frequently Asked Questions
nv show platform firmware and compare the reported CPLD version with the approved target version.Final Takeaway
A Q3400-RA CPLD update should be treated as a platform-specific firmware operation, not as a generic download-and-install task. Confirm the hardware revision, current firmware state, target NVOS release, approved CPLD image, upgrade order, and recovery process before making changes.
For a wider comparison of compatible systems, review the Q3400 Series only as a product-family reference. Do not use another model's firmware file or version mapping for the Q3400-RA without confirmation.
If you need to check a specific system before opening an upgrade request, submit your Q3400-RA firmware details, including the exact OPN, hardware revision, current NVOS version, and CPLD version.