Secure SD-WAN 7.1 Online Help

Home
Secure SD-WAN Engine configuration
You can create and modify Engines, IPS engines, Layer 2 Engines, Master Engines and Virtual Secure SD-WAN Engines. You can configure the Secure SD-WAN Engine properties, activate optional features, and configure advanced Secure SD-WAN Engine settings.
Network interface configuration
The network interface configuration for Secure SD-WAN Engines is stored on the Management Server in the properties of Single Engine, Engine Cluster, Single IPS, IPS Cluster, Single Layer 2 Engine, Layer 2 Engine Cluster, Master Secure SD-WAN Engine, and Virtual Engine elements.
Examples of interface configurations
Examples of interface configurations for Secure SD-WAN Engines in different roles are described in the following sections.
Examples of IPS engine interface configuration
These examples illustrate some common uses for IPS engines and general steps for how each example is configured.

Latest online help
Link to the latest FlexEdge Secure SD-WAN online documentation.
About this Help
This online help was created for Forcepoint FlexEdge Secure SD-WAN, version 7.1.0.
Introduction to the Forcepoint FlexEdge Secure SD-WAN solution
Before setting up Forcepoint FlexEdge Secure SD-WAN, it is useful to know what the different components do and what engine roles are available.
Deployment
Before you can set up the system and start configuring elements, you must consider how the different SMC components should be positioned and deployed.
Setting up
After deploying the SMC components, you are ready to start using the Management Client and carrying out some of the first configuration tasks.
Monitoring
You can use the SMC to monitor system components and third-party devices. You can also view and filter logs, and create Reports from them.
Controlling Secure SD-WAN Engines
You can command and set options for engines through the Management Client or on the engine command line. You can also stop traffic manually.
SMC configuration
SD-WAN Manager configuration allows you to customize how the SMC components work.
Secure SD-WAN Engine configuration
You can create and modify Engines, IPS engines, Layer 2 Engines, Master Engines and Virtual Secure SD-WAN Engines. You can configure the Secure SD-WAN Engine properties, activate optional features, and configure advanced Secure SD-WAN Engine settings.
- Creating and modifying Secure SD-WAN Engines
  Secure SD-WAN Engine elements contain the configuration information that is directly related to the Engines, IPS engines, and Layer 2 Engines. The configuration information includes interface definitions, cluster mode selection, tester settings, and other options specific to the Secure SD-WAN Engine.
- Creating and modifying Master Engine and Virtual Engine elements
  Virtual Engines are logically separate Secure SD-WAN Engines that run as virtual instances on a physical Secure SD-WAN appliance. A Master Engine is a physical appliance that provides resources for Virtual Engines.
- Network interface configuration
  The network interface configuration for Secure SD-WAN Engines is stored on the Management Server in the properties of Single Engine, Engine Cluster, Single IPS, IPS Cluster, Single Layer 2 Engine, Layer 2 Engine Cluster, Master Secure SD-WAN Engine, and Virtual Engine elements.
  - Network interfaces for Secure SD-WAN Engines
    The network interface configuration stored on the Management Server contains most of the settings for network interfaces.
  - Configuring interfaces for Engines
    The interface configuration process consists of several general steps.
  - Configuring interfaces for IPS engines
    The interface configuration for Single IPS engines and IPS Clusters consists of several main steps.
  - Configuring interfaces for Layer 2 Engines
    The interface configuration for Single Layer 2 Engines and Layer 2 Engine Clusters consists of several main steps.
  - Configuring interfaces for Master Engines
    Master Engines can have two types of interfaces: interfaces for the Master Engine's own traffic, and interfaces that are used by the Virtual Engines hosted on the Master Engine.
  - Configuring interfaces for Virtual Engines
    Physical interfaces in the properties of a Virtual Engine represent interfaces allocated to the Virtual Engine in the Master Engine.
  - Add manual ARP entries to Secure SD-WAN Engines
    You can add manual ARP entries for IPv4 and neighbor discover entries for IPv6 in the Engine Editor.
  - Examples of interface configurations
    Examples of interface configurations for Secure SD-WAN Engines in different roles are described in the following sections.
    - Examples of Single Engine interface configuration
      These examples illustrate common configurations for a Single Engine and general overviews of the steps for how each example is configured.
    - Examples of Engine Cluster interface configuration
      These examples illustrate the configuration of a Engine Cluster with general steps for how each example is configured.
    - Examples of IPS engine interface configuration
      These examples illustrate some common uses for IPS engines and general steps for how each example is configured.
      - Example: IPS Capture Interface configuration with SPAN
        An example of using SPAN ports on switches to duplicate packets for inspection.
      - Example: IPS Capture Interface configuration with TAP
        An example of using a network TAP device to forward packets for inspection.
      - Example: IPS Inline Interface configuration
        An example of deploying a Single IPS in the traffic path.
      - Example: IPS Cluster serial inline deployment
        This scenario shows an example of an IPS Cluster in a serial inline deployment.
    - Examples of Layer 2 Engine interface configuration
      These examples illustrate some common uses for Layer 2 Engines and general steps for how each example is configured.
- Connecting Secure SD-WAN Engines to the SMC
  To maintain the security of your system, the Secure SD-WAN Engines establish an authenticated and encrypted connection with Log Servers and Management Servers.
- Element-based network address translation (NAT)
  Element-based NAT allows you to define NAT addresses in the properties of an element. The NAT definitions define how engines translate network IP addresses.
- Configuring the Secure SD-WAN Engine tester
  The Secure SD-WAN Engine tester runs various checks on the Secure SD-WAN Engine and initiates responses based on the success or failure of these tests.
- Engine permissions
  You can set permissions to control the administration of the engines.
- DNS Relay
  DNS relay allows the engine to provide DNS services for clients in internal networks.
- Setting up SNMP for Secure SD-WAN Engines
  SNMP is a standard protocol that different equipment can use to send network management-related information to each other. You can configure Secure SD-WAN Engines to send SNMP traps to external equipment.
- Setting up LLDP for Secure SD-WAN Engines
  Network devices can use the Link Layer Discovery Protocol (LLDP) to advertise their identity, capabilities, and neighbors on a local area network.
- Alias element translations for Secure SD-WAN Engines
  Alias elements can be used to represent other network elements in configurations. The value an Alias takes in a configuration can be different on each Secure SD-WAN Engine where the Alias is used.
- Add-on features for Secure SD-WAN Engines
  There are several add-on features that you can use on Engines, IPS engines, Layer 2 Engines, Virtual Engines, Virtual IPS engines, and Virtual Layer 2 Engines.
- Advanced Secure SD-WAN Engine settings
  Advanced settings cover various system parameters related to different features.
Routing
Use the Management Client to configure static or dynamic routing, and use a Multi-Link configuration to manage and distribute inbound and outbound connections.
Traffic inspection policies
Policies are key elements that contain rules for allowing or blocking network traffic and inspecting the content of traffic.
Users and authentication
User accounts are stored in internal databases or external directory servers. You can use Secure SD-WAN in the Engine/VPN role or external authentication servers to authenticate users.
Virtual private networks
Secure SD-WAN supports both policy-based and route-based VPN tunnels between VPN gateways. For full remote access, Secure SD-WAN supports both IPsec and SSL VPN tunnels for VPN clients.
Maintenance and upgrades
Maintenance includes procedures that you do not typically need to do frequently.
Troubleshooting
Troubleshooting helps you resolve common problems in the Secure SD-WAN and SMC.
Appendices

Examples of IPS engine interface configuration

These examples illustrate some common uses for IPS engines and general steps for how each example is configured.

Example: IPS Capture Interface configuration with SPAN
An example of using SPAN ports on switches to duplicate packets for inspection.
Example: IPS Capture Interface configuration with TAP
An example of using a network TAP device to forward packets for inspection.
Example: IPS Inline Interface configuration
An example of deploying a Single IPS in the traffic path.
Example: IPS Cluster serial inline deployment
This scenario shows an example of an IPS Cluster in a serial inline deployment.

Copyright © 2024 Forcepoint LLC