Skip to main content
Triggr manages the firewalls in Network Security Manager (NSM): tenants, devices, commits, templates, group actions, firmware, backups, licences and VPN topologies. To work on a firewall directly, use SonicWall; for Cloud Secure Edge, use SonicWall CSE.

​
Set up SonicWall

1

Generate a MySonicWall API key

Sign in to MySonicWall as the user Triggr should act as, go to My Workspace | User Groups > User list and click Generate My API Key. Enter a Description, leave Source IP Address blank, set Validity (one year at most) and click Confirm. Copy the key before you close the window.If Generate My API Key is missing, raise a Customer Service Request with SonicWall. See SonicWall’s guide to generating a key.
2

Find your NSM region

Open NSM from MySonicWall and note the host, such as nsm-uswest.sonicwall.com or nsm-eucentral.sonicwall.com.

​
Connect it in Triggr

1

Open the configuration

Go to Integrations > SonicWall NSM and click Configure on the Base Configuration card.
The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.
2

Enter the endpoint and sign-in

Enter the NSM Endpoint URL with https:// and no path: your region’s host, such as https://nsm-uswest.sonicwall.com, or your NSM server’s public address with its port if it isn’t 443. For cloud NSM, enter the MySonicWall API Key and leave the rest blank; for NSM On-Prem, enter NSM Admin Username and NSM Admin Password instead. Click Save Configuration.
The SonicWall NSM configuration window with NSM Endpoint URL, MySonicWall API Key, MySonicWall API URL (optional), NSM Admin Password, Tenant (optional), NSM Tenant ID (optional), NSM Tenant Serial (optional) and NSM Admin Username fields, an Allow insecure TLS switch under Advanced, and a Save Configuration button.
If MySonicWall API Key has a value, Triggr uses it and ignores the username and password.

​
Set up each client

Per-client integrations never fall back to the Base Configuration, so click Configure on each client’s row and fill in a complete configuration. With cloud NSM, use the same key and NSM Endpoint URL for every client and set NSM Tenant ID (optional) to the client’s tenant: run Get Cloud Tenants (MySonicWall) to list the tenants the key reaches, each one’s productGroupID being its tenant ID.
The Per-Client Configuration card listing Acme Corp and Globex, each Not Configured with Admin Consent Not Required and a Configure button.
NSM holds changes as pending until they’re committed: Create Commit commits and deploys, and Create Commit with Approval waits for Approve Commit. Most firewall actions take the firewall’s serial number from List Devices for Tenant.

​
Troubleshooting

The configuration the workflow used has neither a MySonicWall API Key nor both NSM Admin Username and NSM Admin Password. If the workflow ran for a client, check that client’s configuration.
Enter the right tenant’s ID, from the list in the error, in NSM Tenant ID (optional).
The NSM Tenant ID (optional) or NSM Tenant Serial (optional) isn’t one the key reaches. Check it against Get Cloud Tenants (MySonicWall) and the MySonicWall user’s tenant access.
NSM isn’t active on that MySonicWall tenant. Check in MySonicWall that the tenant has NSM and its firewalls are managed through it.
Configure the client on the Per-Client Configuration card.
Check the key was pasted in full and hasn’t expired or been revoked. If the error mentions IPBLOCKED, generate a key with Source IP Address blank, or ask SonicWall Support to allow Triggr’s IP addresses.
NSM refused the sign-in. With cloud NSM, check NSM Endpoint URL is your tenant’s region and the MySonicWall user has access to the tenant in NSM.
Check the username and password, that two-factor authentication is off, that NSM Endpoint URL is the public address with its port, and that NSM’s certificate matches the hostname.