Filter
Top Products
Managing Policy Enforcement Points
148 EncrypTight User Guide
network sets in Layer 3 IP policies. L2 PEPs can be used in Layer 2 Ethernet policies. You can sort the
list of PEPs by type or name by clicking the column header (SG or Name).
When ETEMS communicates with a PEP, it verifies that its hardware and software configuration is valid.
PEPs that ETEMS has not yet communicated with are marked with a ? symbol beside the IP or L2
designation. In the previous example, PEP 2, PEP 5, and ESG PEP 1 have not yet had any
communications from ETEMS. Once you refresh the status or push configurations from ETEMS, the ?
symbol disappears. The first time you attempt to use a PEP with the ? symbol, the following warning
appears.
Related topics:
● “Adding a New PEP in ETEMS” on page 148
● “Adding a New PEP Using ETPM” on page 150
Adding a New PEP in ETEMS
It is recommended that you add all new PEPs in the ETEMS Appliance Manager because you can only
push configurations to the PEPs in ETEMS. All appliances used as EncrypTight PEPs must have the
configuration settings described in Table 39.
Table 39 EncrypTight PEP configuration
Configuration Description
Network interfaces On the Interfaces tab, configure the PEP’s management, local, and
remote ports.
If the PEP and the ETKMS are on different subnets, specify a
default gateway for the management port that the PEP can use for
communication with the ETKMS and the management workstation
hosting ETPM.