Nvidia (Mellanox) SN2100: How to zero-touch provisioning

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

What this guide covers

How to zero-touch provisioning for Nvidia (Mellanox) SN2100 (Cumulus Linux / NVOS / SONiC).

Step-by-step

1. Choose the automation surface: vendor controller, API, or CLI scripting.
2. Verify reachability + credentials from your automation host.
3. Test the change on a single device + maintenance window.
4. Roll out in waves of 10-20 devices to limit blast radius.
5. Pre-collect baseline, push the change, post-collect; diff.
6. Roll back any device whose post-check fails.

Sample CLI invocation

# Manual baseline
nv show system
nv show platform inventory
nv show interface

# Push change (via vendor CLI)
nv config (NVUE)
nv set interface swp1 ip address 10.0.0.1/24
nv config apply
nv config save

# Verify
nv show interface

Best practices

• Always test on a single device or sandbox before fleet rollout.
• Keep configurations in version control (Git).
• Use AAA + RBAC for the automation account; never embed credentials in code.
• Build pre/post-change validation into your pipeline.

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.

Related guides

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

Related fixes

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

• Nvidia (Mellanox) SN2010: How to zero-touch provisioning
• Nvidia (Mellanox) SN2410: How to zero-touch provisioning
• Nvidia (Mellanox) SN2100 all ports dead: Diagnose & Fix
• Nvidia (Mellanox) SN2100: How to back up configs nightly to a Git repo
• Nvidia (Mellanox) SN2100: How to deploy with a Python script (paramiko / netmiko / native API)
• Nvidia (Mellanox) SN2100: How to deploy with Ansible

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.

Common patterns we see

When this symptom shows up on a Nvidia device, three patterns repeat:

1. Recent firmware update changed behavior, the symptom started within a week of an OTA push. Rollback or wait for the hotfix. 2. Environmental trigger: temperature, humidity, line voltage, network changes. Look at what changed in the environment. 3. Cumulative wear, components like batteries, gaskets, fans degrade over time. Replace the consumable rather than chasing a software fix.

Knowing which pattern applies saves time on the wrong fix.

Safety + preconditions

Before any work on a Nvidia device:

• Unplug from mains for any internal-access procedure.
• Discharge stored energy (capacitors in PSUs, residual battery charge) per manufacturer guidance.
• Use ESD-safe handling for boards and modules. no carpet, no wool sleeves.
• Avoid moisture; never apply liquids near vents or connectors.
• If you smell smoke, see scorch marks, or feel uneven heat, stop and escalate.

Quick verification

Before you walk away from a Nvidia device fix, run through:

1. Reproduce the original trigger, does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + firmware version.

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.

More frequently asked questions

Will the procedure work on the international variant?

Some features and firmware paths are region-locked. Check the model spec sheet to confirm your variant supports the menu option referenced. If you're outside the US/EU, look for the regional support portal.

Can I roll this back if something breaks?

Yes for software-level changes (firmware rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.

Are there safer alternatives for non-technical users?

Yes: the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.

What if my model isn't exactly the same revision?

Cross-check the model code on the rating plate against the manufacturer support page. Major firmware generations sometimes shift the menu path; the option is usually under a similarly-named section.

Why is this happening on a brand-new unit?

Out-of-box defects do occur. If you've owned the device under 30 days and the symptom persists after a factory reset, escalate to the seller for replacement under DOA terms before opening a manufacturer support case.