SonicOS 7 System
- SonicOS 7.0
- Overview
- 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
Prerequisites for PortShielding X-Series Switches
If the topology has two or more switches, the switches can be cascaded or daisy chained, that is, one switch can be connected to another one that is connected to the appliance.
X-Series switches (excluding X1052/X1052P models) are delivered from the factory in unmanaged mode to avoid unauthorized access to the switch. You need to put the switch into Managed mode by pressing Mode, near the power plug, for at least seven seconds.
X1052/X1052P models delivered from the factory are by default in Managed mode.
During the initial set up of the switch, to ensure the X-Series switch’s IP does not change dynamically when the DHCP server is enabled on the appliance interfaces, choose Static IP instead of Dynamic IP.
For more information on these features, refer to the SonicWall SonicOS X-Series Solution Deployment Guide located on the Support portal at https://www.sonicwall.com/support/technical-documentation/ and select TZ Series in the Select A Product field.
- Apart from the initial IP address, username/password configuration, which can be found on the switch, no other configuration is recommended to be performed on the X-Series switch directly through the switch’s GUI/console. To do so results in the appliance being out-of-sync with the configuration state of the X-Series switch.
- To manage the X-Series switch from the appliance, one of the interfaces of the appliance must be in the same subnet as the X-Series switch. For example, to manage an X-Series switch with a default IP
192.168.2.1
, an interface of the appliance needs to be configured in the192.168.2.0/24
subnet and connected to the X-Series switch. - Ensure the appliance can reach the X-Series switch by pinging the X-Series switch from the appliance before provisioning/managing the switch from the appliance.
- VLAN support:
- Support for VLANs is available on shared and common uplinks. For example, VLANs can be configured under the appliance interface, which is provisioned as the shared uplink for the X-Series switch.
- For details on VLAN support, refer to the SonicWall SonicOS X-Series/ Solution Deployment Guide located on the Support portal at https://www.sonicwall.com/support/technical-documentation/ and select TZ Series in the Select A Product field. Overlapping VLANs cannot exist under appliance interfaces configured as dedicated uplinks. For example, if X3 and X5 are configured for dedicated uplinks, VLAN 100 cannot be present under both X3 and X5. Such a configuration is rejected.
Was This Article Helpful?
Help us to improve our support portal