What Neo can do with SonicWall
- Report each client’s firewalls with their status, firmware, and licences that expire soon, across every tenant
- Schedule a firmware upgrade or a restart for a maintenance window, and report the result
- Read VPN tunnel and WAN link status for an alert
- Return a firewall’s access rules and NAT policies, and change them with a commit in NSM
- Read security and traffic data for a review
Your SonicWall tenants are mapped to clients
Neo matches each MySonicWall tenant that has NSM to a client in your PSA and keeps the mapping on the SonicWall card’s Organization Mapping tab, refreshed on each PSA metadata sync. With the mapping, an agent works in the right client’s tenant. Matching starts with the name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the long tail. A name match, or one you confirm, is handed straight to your agents. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it. Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right client by hand. A mapping you set by hand survives every later sync. If you keep all your clients in one NSM tenant, as device groups, there is nothing per client to map. Agents then work in that one tenant and find the client’s firewalls by device group.Next steps
Connect SonicWall
Generate a MySonicWall API key and save it in Neo.
