SonicOS 7.1 System
- SonicOS 7.1
- About SonicOS
- Interfaces
- About Interfaces
- Interface Settings IPv4
- Adding Virtual Interfaces
- Configuring Routed Mode
- Enabling Bandwidth Management on an Interface
- Configuring Interfaces in Transparent IP Mode (Splice L3 Subnet)
- Configuring Wireless Interfaces
- Configuring WAN Interfaces
- Configuring Tunnel Interfaces
- Configuring VPN Tunnel Interfaces
- Configuring Link Aggregation and Port Redundancy
- Configuring One Arm Mode
- Configuring an IPS Sniffer Mode Appliance
- Configuring Security Services (Unified Threat Management)
- Configuring Wire and Tap Mode
- Layer 2 Bridged Mode
- Key Features of SonicOS Layer 2 Bridged Mode
- Key Concepts to Configuring L2 Bridged Mode and Transparent Mode
- Comparing L2 Bridged Mode to Transparent Mode
- Comparison of L2 Bridged Mode to Transparent Mode
- Benefits of Transparent Mode over L2 Bridged Mode
- ARP in Transparent Mode
- VLAN Support in Transparent Mode
- Multiple Subnets in Transparent Mode
- Non-IPv4 Traffic in Transparent Mode
- ARP in L2 Bridged Mode
- VLAN Support in L2 Bridged Mode
- L2 Bridge IP Packet Path
- Multiple Subnets in L2 Bridged Mode
- Non-IPv4 Traffic in L2 Bridged Mode
- L2 Bridge Path Determination
- L2 Bridge Interface Zone Selection
- Sample Topologies
- Configuring Network Interfaces and Activating L2B Mode
- Configuring Layer 2 Bridged Mode
- Asymmetric Routing
- Configuring Interfaces for IPv6
- 31-Bit Network Settings
- PPPoE Unnumbered Interface Support
- Failover & LB
- Neighbor Discovery
- ARP
- MAC IP Anti-Spoof
- Web Proxy
- PortShield Groups
- SonicOS Support of X-Series Switches
- About the X-Series Solution
- Performance Requirements
- Key Features Supported with X-Series Switches
- PortShield Functionality and X-Series Switches
- PoE/PoE+ and SFP/SFP+ Support
- X-Series Solution and SonicPoints
- Managing Extended Switches using GMS
- Extended Switch Global Parameters
- About Links
- Logging and Syslog Support
- Supported Topologies
- Port Graphics
- Port Configuration
- External Switch Configuration
- External Switch Diagnostics
- Configuring PortShield Groups
- SonicOS Support of X-Series Switches
- PoE Settings
- VLAN Translation
- IP Helper
- Dynamic Routing
- DHCP Server
- Configuring a DHCP Server
- Configuring Advanced Options
- Configuring DHCP Option Objects
- Configuring DHCP Option Groups
- Configuring a Trusted DHCP Relay Agent Address Group (IPv4 Only)
- Enabling Trusted DHCP Relay Agents
- Configuring IPv4 DHCP Servers for Dynamic Ranges
- Configuring IPv6 DHCP Servers for Dynamic Ranges
- Configuring IPv4 DHCP Static Ranges
- Configuring IPv6 DHCP Static Ranges
- Configuring DHCP Generic Options for DHCP Lease Scopes
- DHCP and IPv6
- Multicast
- Network Monitor
- AWS Configuration
- SonicWall Support
Enabling Bandwidth Management on an Interface
Bandwidth Management (BWM) allows you to guarantee minimum bandwidth and prioritize traffic. BWM is enabled in Firewall Settings > Bandwidth Management. By controlling the amount of bandwidth to an application or user, you can prevent a small number of applications or users from consuming all available bandwidth. Balancing the bandwidth allocated to different network traffic and then assigning priorities to traffic improves network performance.
Various types of bandwidth management can be enabled:
- Advanced—Enables you to configure maximum egress and ingress bandwidth limitations per interface, by configuring bandwidth objects, access rules, and application policies.
- Global—Allows you to enable BWM settings globally and apply them to any interfaces.
- Global Enh—Similar to Global, but uses a first-come, first-served queue and does not limit the number of packets processed.
- None (default)—Disables BWM.
For more information about configuring bandwidth management and the effect of the various BWM types, see the SonicOS administration documentation, available at https://www.sonicwall.com/support/technical-documentation.
SonicOS can apply bandwidth management to both egress (outbound) and ingress (inbound) traffic on any interfaces. Outbound bandwidth management is done using Class-based Queuing. Inbound Bandwidth Management is done by implementing an ACK delay algorithm that uses TCP’s intrinsic behavior to control the traffic.
Class-based Queuing (CBQ) provides guaranteed and maximum bandwidth Quality of Service (QoS) for the firewall. Every packet destined to the interface is queued in the corresponding priority queue. The scheduler then dequeues the packets and transmits them on the link depending on the guaranteed bandwidth for the flow and the available link bandwidth.
The options described in this section are only available if Bandwidth Management is enabled in Firewall Settings > Bandwidth Management.
To enable or disable ingress and egress BWM
- Navigate to NETWORK | System > Interfaces.
- Click the Edit icon of an interface. The Edit Interface dialog displays.
- If this is an unassigned interface, configure the interface according to the sections contained in Configuring Interfaces.
-
On the Advanced screen, scroll to Bandwidth Management.
Advanced Settings might differ, depending on the firewall model and the type of zone selected.
-
Enable Bandwidth Management for this interface.
-
To limit outgoing traffic to a maximum bandwidth on the interface, select Enable Interface Egress Bandwidth Limitation. This option is not selected by default.
Specify the maximum bandwidth, in kbps, in the Maximum Interface Egress Bandwidth (kbps) field. The minimum is 20 Kbps, the maximum is 1000000, and the default is 384.000000.
-
To limit incoming traffic to a maximum bandwidth on the interface, select Enable Interface Ingress Bandwidth Limitation. This option is not selected by default.
Specify the maximum bandwidth, in kbps, in the Maximum Interface Ingress Bandwidth (kbps) field. The minimum is 20 Kbps, the maximum is 1000000, and the default is 384.000000.
When either of these options are:
- Selected, the maximum available egress BWM is defined, but as advanced BWM is policy-based, the limitation is not enforced unless there is a corresponding Access Rule or App Rule.
- Not selected, no bandwidth limitation is set at the interface level, but traffic can still be shaped using other options.
-
-
Optionally, select Enable Default 802.1p tagging to tag information passing through this interface with 802.1p priority information for Quality of Service (QoS) management. This option is not selected by default.
Packets sent through this interface are tagged with VLAN id=0 and carry 802.1p priority information. To make use of this priority information, devices connected to this interface should support priority frames. QoS management is controlled with access rules established on POLICY | Rules and Policies > Access Rules.
- Click OK.
Was This Article Helpful?
Help us to improve our support portal