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
Configuring Network Monitor Policies
To add a new Network Monitor policy
- Navigate to NETWORK | System > Network Monitor.
-
Click +Add. The Add New Network Monitor Policy dialog displays.
- Enter a meaningful name in the Name field.
- Select an address object from Probe Target.
-
From Probe Type, select:
- Ping (ICMP) - Explicit Route (default); go to Step 7.
- TCP - Explicit Route; the Port field and other options become available.
- Enter the port number of the explicit route in the Port field.
-
Enter the interval between probes in the Probe hosts every … seconds field. The minimum is 1 second, the maximum is 3600 seconds, and the default is 3 seconds.
The probe interval must be greater than the reply timeout.
- Enter the maximum delay for a response in the Reply time out … seconds field. The minimum is 1 second, the maximum is 60 seconds, and the default is 1 second.
- Enter the maximum number of missed intervals before the performance probe is set to the DOWN state in the Probe state is set to DOWN after … missed intervals field. The minimum number is 1, the maximum is 100, and the default is 3.
- Enter the maximum number of successful intervals before the performance probe is set to the UP state in the Probe state is set to UP after … successful intervals field. The minimum number is 1, the maximum is 100, and the default is 1.
- If you selected TCP - Explicit Route for Probe Type, the RST Response Counts As Miss option becomes available. Select the option to count RST responses as missed intervals. This option is not selected by default.
- Enable or disable if you would like to force a response from all hosts with the All Host Must Respond option.
- Enable or Disable RST Response Counts As Miss (for Probe Types of TCP – Explicit Route), whether RST responses count as misses.
- Optionally, enter a comment in the Comment field.
- Click ADD.
-
Repeat Step 3 through Step 14 to add more probes.
- Click Close.
Was This Article Helpful?
Help us to improve our support portal