Secure SD-WAN 7.1.x Online Help

Home
Troubleshooting
Troubleshooting helps you resolve common problems in the Secure SD-WAN and SMC.
Troubleshooting Secure SD-WAN Engine operation
There are several common errors and problems that are directly related to the operation of Engines, IPS engines, and Layer 2 Engines.

About this Help
This online help was created for Forcepoint FlexEdge Secure SD-WAN, version 7.1.x.
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.
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.
- General troubleshooting tips
  General troubleshooting tips help you troubleshoot situations that are not covered by more specific troubleshooting topics.
- Troubleshooting Administrator accounts and passwords
  There are several common problems and solutions related to Administrator accounts and passwords.
- Messages for troubleshooting
  Some common alert and log messages that you might see in the Logs view are useful for troubleshooting.
- Troubleshooting Secure SD-WAN Engine operation
  There are several common errors and problems that are directly related to the operation of Engines, IPS engines, and Layer 2 Engines.
  - Troubleshoot Secure SD-WAN Engines that do not go or stay online
    There are several possible causes and solutions when you command a node online, but it does not go online or turns itself offline shortly after going online.
  - Troubleshoot errors when commanding Secure SD-WAN Engines
    There are several possible causes and solutions when you try to command an engine using the Management Client and receive an error.
  - Troubleshoot heartbeat and synchronization errors
    There are several possible causes and solutions when you receive alerts regarding the heartbeat connection between the nodes in a cluster.
  - Troubleshoot contact between Secure SD-WAN Engines and the Management Server
    Sometimes, the engine cannot establish initial contact to the Management Server, or all subsequent attempts to command the engine through the Management Client fail. There are several possible causes and solutions for these failures.
- Troubleshooting licenses
  Licenses are a proof of purchase used for ensuring that your organization is a legal license holder of the software.
- Troubleshooting logging
  There are some common problems you might encounter when viewing logs or performing tasks related to the log files.
- Troubleshooting the Management Client
  There are several general problems that you might encounter when using the Management Client.
- Troubleshooting NAT
  There are some common problems you might encounter with NAT.
- Troubleshooting policies
  There are some common problems you might encounter when working with policies and the rules that they contain.
- Troubleshooting reporting
  There are some common problems that you might encounter when generating reports from raw statistical and log data stored on the Log Server.
- Troubleshooting upgrades
  There are some common problems that you might encounter when upgrading SMC components.
- Troubleshooting VPNs
  There are some common problems that you might encounter when creating and managing VPNs.
Appendices

Troubleshooting Secure SD-WAN Engine operation

There are several common errors and problems that are directly related to the operation of Engines, IPS engines, and Layer 2 Engines.

Troubleshoot Secure SD-WAN Engines that do not go or stay online
There are several possible causes and solutions when you command a node online, but it does not go online or turns itself offline shortly after going online.
Troubleshoot errors when commanding Secure SD-WAN Engines
There are several possible causes and solutions when you try to command an engine using the Management Client and receive an error.
Troubleshoot heartbeat and synchronization errors
There are several possible causes and solutions when you receive alerts regarding the heartbeat connection between the nodes in a cluster.
Troubleshoot contact between Secure SD-WAN Engines and the Management Server
Sometimes, the engine cannot establish initial contact to the Management Server, or all subsequent attempts to command the engine through the Management Client fail. There are several possible causes and solutions for these failures.

Copyright © 2024 Forcepoint LLC