SonicOS 7.0 Rules and Policies for Policy mode
- SonicOS 7.0 Rules and Policies
- Settings
- Security Policy
- NAT Policy
- About NAT in SonicOS
- About NAT Load Balancing
- About NAT64
- About FQDN-based NAT
- About Source MAC Address Override
- Viewing NAT Policy Entries
- Adding or Editing NAT or NAT64 Rule Policies
- Deleting NAT Policies
- Creating NAT Rule Policies: Examples
- Creating a One-to-One NAT Policy for Inbound Traffic
- Creating a One-to-One NAT Policy for Outbound Traffic
- Inbound Port Address Translation via One-to-One NAT Policy
- Inbound Port Address Translation via WAN IP Address
- Creating a Many-to-One NAT Policy
- Creating a Many-to-Many NAT Policy
- Creating a NAT Load Balancing Policy for Two Web Servers
- Routing
- Decryption Policy
- DoS Policy
- DNS Policy
- Endpoint Policy
- Shadow
- SonicWall Support
Caveats
- Only two health-check mechanisms (ICMP ping and TCP socket open)
- No higher-layer persistence mechanisms (Sticky IP only)
- No “sorry-server” mechanism if all servers in group are not responding
- No “round robin with persistence” mechanism
- No “weighted round robin” mechanism
- No method for detecting if resource is strained
While there is no limit to the number of internal resources that the SonicWall network security appliance can load-balance to and there is no limit to the number of hosts it can monitor, abnormally large load-balancing groups (25+ resources) might impact performance.
Was This Article Helpful?
Help us to improve our support portal