SonicWall: How to enable NETCONF or vendor API over SSH

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

What this guide covers

How to enable NETCONF or vendor API over SSH on SonicWall devices (SonicOS).

Recommendation

Modern automation needs API access. Enable NETCONF / vendor API only over SSH or TLS.

CLI / commands

# Entered from: configure
configure
  interface X0
    ip-address 10.0.0.1 netmask 255.255.255.0
  exit
commit

# Save / commit
commit

Verify

• Test from a non-admin workstation.
• Confirm fallback works if AAA or external service is down.
• Document the change in your CMDB / change-control.

Frequently asked questions

Will this work on my specific SonicOS version?

The procedure reflects current SonicOS behaviour. Older releases may need minor syntax adjustments, use the CLI help (? or tab-completion) to verify.

Should I open a SonicWall 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 SonicWall official documentation?

https://www.sonicwall.com/support/knowledge-base/: 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 SonicWall fix guides → /sonicwall/
• All vendor guides → /vendors/

Related fixes

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

• SonicWall: How to enable control-plane policing / rate-limiting
• SonicWall: How to enable HTTPS-only management
• SonicWall: How to enable management ACL to lock down access
• SonicWall: How to replace Telnet with SSH
• SonicWall: How to configure logging to a central SIEM
• SonicWall: How to disable unused services and protocols

References

• SonicWall support portal: https://www.sonicwall.com/support
• SonicWall knowledge base: https://www.sonicwall.com/support/knowledge-base/
• SonicWall security advisories: https://psirt.global.sonicwall.com
• Open a case: https://www.mysonicwall.com

Reference material, not professional advice. Validate against your specific SonicOS version and test in a non-production environment before applying.

What changed recently?

Fault diagnosis on a SonicWall: 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.

Safety + preconditions

Before any work on a SonicWall: 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.

Verification checklist

After applying the fix on your SonicWall: 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.

Escalation guide

For a SonicWall: device, the right escalation depends on impact:

• Cosmetic / minor: log a ticket via the SonicWall: app or web portal. Response 1-3 business days.
• Mid-impact: phone support. Have your serial number ready.
• Critical (production down, safety issue): in-person dealer / TAC visit. Bring proof of purchase.
• Out of warranty: third-party repair shop with manufacturer-certified technicians.

More frequently asked questions

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.

What if the fix returns after a reboot?

Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent firmware update (rollback).

How often should I run preventive checks?

Quarterly for most consumer devices; monthly for production / commercial devices. Set a calendar reminder so the device stays healthy between issues.

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.

Does this affect other devices on my network?

Generally no. The procedure is local to this device. Network-side changes (firmware updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.