As with other Juniper Networks virtual appliances, Policy Enforcer requires either a VMware ESX server version 4.0 or later or a VMware ESXi server version 4.0 or later that can support a virtual machine with the following configuration:
1 CPU
8-GB RAM
120-GB disk space
If you are not familiar with using VMware ESX or EXSi servers, see VMware Documentation and select the appropriate VMware vSphere version.
To deploy and configure the Policy Enforcer with OVA files, perform the following tasks:
Note: Do not change the name of the Policy Enforcer virtual machine image file that you download from the Juniper Networks support site. If you change the name of the image file, the creation of the Policy Enforcer virtual machine can fail.
It may take a few minutes to deploy your virtual machine. Once deployed, its name appears in the left side of the vSphere Client.
The welcome page appears.
The End User License Agreement (EULA) window appears.
The Network configuration page appears. See Figure 82.
Figure 82: Defining the Basic Network Configuration Settings
Option | Description |
---|---|
Hostname | Enter the hostname for the Policy Enforcer virtual machine; for example, pe.juniper.net. |
IP address | Enter the IP address for the Policy Enforcer virtual machine. Note: Make note of this IP address as you’ll need it in a later step. |
Network mask | Enter the netmask for the Policy Enforcer virtual machine. |
Default gateway | Enter the IP address of the default gateway that connects your internal network to external networks. |
Primary DNS server | Enter the IP address of your primary system registered to join the Domain Name System (DNS). |
Secondary DNS server | Enter the IP address of a secondary DNS server. Policy Enforcer uses this address only when the primary DNS server is unavailable. |
Skip DNS servers check | Select this check box if you do not want to check basic network settings. By default, the system will ping the gateway to ensure it receives a response indicating your settings are correct. |
Your network settings are applied. A progress window indicates the status.
When the system is finished updating your network settings, an NTP server window appears and prompts you to configure the NTP server list. See Figure 83.
Figure 83: Prompt for Configuring the NTP Servers
Figure 84: Configuring the NTP Servers
The Customer Information page appears. See Figure 85.
Figure 85: Entering Customer Information
The Root password change page appears. See Figure 86.
Figure 86: Changing the Root Password
Password restrictions are listed in the screen.
Note: Make note of this password as you’ll need it in a later step.
If you forget your password, see CentOS root password reset instructions.
The Juniper Networks Policy Enforcer page appears. See Figure 87.
Figure 87: Reviewing and Changing Your Configuration Settings.
Option | Description |
---|---|
Review configuration and finish setup | Lets you review the configuration settings you defined one last time before applying them to the Policy Enforcer virtual machine. We recommend that you do not change your configuration settings after Policy Enforcer is set up within Security Director. |
Change... | Select a setting to update its value. |
Troubleshooting menu | Lets you ping the default gateway and custom IP address and lets you perform a DNS lookup to verify that your settings are correct. |
The Review configuration page appears. See Figure 88.
Figure 88: Reviewing Your Configuration Settings
When you click Finish setup, the configuration settings are applied to the Policy Enforcer virtual machine. A status page indicates the progress.
When done, the Setup Complete page appears.
Note: Each time you log in to the Policy Enforcer virtual machine, you are given the option to review or change any of these settings.
© 2018 Juniper Networks, Inc. All rights reserved