Managing appliances

Administrator Help | Forcepoint Email Security | Version 8.4.x

Before you add an appliance to the Email Security module, you should have already installed and configured a Forcepoint appliance. Interface information includes IP address, subnet mask, default gateway, and up to 3 DNS server IP addresses. See the Forcepoint Appliance Getting Started Guide for more details about setting up and configuring an appliance.

Forcepoint Email Security may be deployed as a virtual appliance. See the Forcepoint appliance Getting Started Guide for complete information about deploying and configuring a virtual appliance.


	Note You can configure a primary, secondary, and tertiary DNS server, with the secondary and tertiary servers being optional entries. When it starts, the email appliance polls each DNS server to determine which has the lowest latency level. That server is selected as the "primary" server for DNS queries, regardless of its designation. The other servers may be used for subsequent queries based on the network connection status of the primary server.

If you change either the appliance hostname or C interface IP address on the appliance, you must make the same change in the Settings > General > Email Appliances page. The Email Security module does not detect this change automatically.

Email traffic is usually routed through dedicated appliance interfaces (E1/E2). However, if you want to route traffic through the C interface (for example, to transfer log data to a SIEM server), you need to define a route using the appliance CLI. You should note that you need to stop and restart email security services on the appliance each time you add or delete a route on the appliance.