Upgrade Failure

Nvidia (Mellanox) SN3700: How to verify image integrity before activating

Q: Where can I find the Nvidia (Mellanox) official documentation?

https://docs.nvidia.com/networking/ — search the product family + feature name.

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance

Vendor	Nvidia (Mellanox)
Operating system	Cumulus Linux / NVOS / SONiC
Category	Upgrade Failure
Skill level	Intermediate to advanced
DIY-able?	Yes with CLI access; some scenarios need Nvidia Enterprise Support + RMA.

Upgrade work on a Nvidia (Mellanox) fleet is mostly about discipline. Cumulus Linux / NVOS / SONiC gives you the commands; the failure mode is almost always operator error. wrong image for the platform, integrity not checked, no rollback plan. The SN3700 family is no exception.

I always do a one-box pilot before a fleet roll. onie-nos-install /home/cumulus/cumulus-linux-5.x.img on a single representative unit, then 24 hours of soak, then the rest of the fleet in waves. Skipping the soak has bitten me twice.

Nvidia Enterprise Support will want the exact build string and the upgrade method (CLI vs controller-driven) on every case, so keep that recorded for the change ticket.

What this guide covers

Verify image integrity before activating on a Nvidia (Mellanox) SN3700 (Cumulus Linux / NVOS / SONiC).

Step-by-step

Copy the image to local flash.
Run the vendor checksum / md5 command.
Compare against the checksum published on the vendor portal.
If mismatched, the image is corrupt, re-download.

CLI / commands

# Boot recovery prompt: ONIE:/ #

# Verify image
nv show system

# Upgrade
onie-nos-install /home/cumulus/cumulus-linux-5.x.img

# Save / commit
nv config save

# Rollback
nv config patch (revert to last apply)

Recovery options

Boot loader recovery (ONIE:/ #)
Rollback to the previous image with nv config patch (revert to last apply)
Force failover to a known-good standby (HA platforms)

Frequently asked questions

Will this work on my specific Cumulus Linux / NVOS / SONiC version?

The procedure reflects current Cumulus Linux / NVOS / SONiC behaviour. Older releases may need minor syntax adjustments: use the CLI help (? or tab-completion) to verify.

Should I open a Nvidia Enterprise Support case immediately?

Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your support entitlement is active first.

Where can I find the Nvidia (Mellanox) official documentation?

https://docs.nvidia.com/networking/, search the product family + feature name.

Is this procedure safe in production?

Test in a lab or maintenance window first. Capture pre-change state so you can roll back.

All Nvidia (Mellanox) fix guides → /nvidia/
All vendor guides → /vendors/

Related guides worth a look while you sort this one out:

References

Nvidia (Mellanox) support portal: https://enterprise-support.nvidia.com/
Nvidia (Mellanox) knowledge base: https://docs.nvidia.com/networking/
Nvidia (Mellanox) security advisories: https://www.nvidia.com/en-us/security/
Open a case: https://enterprise-support.nvidia.com/s/createcase

Reference material, not professional advice. Validate against your specific Cumulus Linux / NVOS / SONiC version and test in a non-production environment before applying.

What changed recently?

Fault diagnosis on a Nvidia device goes faster when you map the symptom to a recent change:

Did firmware update in the last 7 days?
Did the network (router, ISP, VPN) change?
Was the device moved physically?
Did paired devices (phone, hub, app) update?
Were any accessories swapped in or out?

The answer narrows the root cause to a manageable subset.

Before you start

A few things to confirm so the Nvidia device fix goes cleanly:

Latest firmware downloaded if you're going to update.
Warranty + support contract status checked. opening sealed parts may void it.
Backup of current configuration (where applicable) taken.
Spare parts on hand if you anticipate replacement.
Adequate workspace, lighting, and time, rushing causes regressions.

Verification checklist

After applying the fix on your Nvidia device, confirm:

The original symptom is no longer reproducible.
Related features (status LEDs, app sync, paired accessories) still work.
The device responds to a soft reboot without the fault returning.
Any error codes that were on display have cleared.
Documentation (your service log, the brand companion app) reflects the change.

When to call Nvidia support instead

Escalate if:

The same symptom returns within 24 hours of a clean fix.
You see physical damage (burn marks, swollen battery, cracked PCB).
The device is in warranty and a hardware replacement is the cheaper outcome.
Repair requires specialised tools you don't own (alignment jigs, calibration software).
Following the official path keeps the warranty intact, which matters more than the time spent.