5.1

Option Action
Host Name
Type the host name of the DHCP client virtual machine.
IP Address
Type the address to which to bind the MAC address of the selected virtual
machine.
Domain Name
Type the domain name of the DNS server.
Primary Name Server
If you did not select Auto Configure DNS, type the Primary Nameserver
for the DNS service. You must enter the IP address of a DNS server for
hostname-to-IP address resolution.
Secondary Name Server
If you did not select Auto Configure DNS, type the Secondary
Nameserver for the DNS service. You must enter the IP address of a DNS
server for hostname-to-IP address resolution.
Default Gateway
Type the default gateway address. If you do not specify the default gateway
IP address, the internal interface of the vShield Edge instance is taken as the
default gateway.
Lease Time
If you did not select Lease never expires, select whether to lease the address
to the client for the default time (1 day), or type a value in seconds.
9 Click Add.
10 Click Publish Changes.
What to do next
Verify that the DHCP service is enabled. The DHCP Service Status above the DHCP Pools panel must be set
to Enabled.
Managing VPN Services
vShield Edge modules support site-to-site IPSec VPN between a vShield Edge instance and remote sites.
vShield Edge modules also support SSL VPN-Plus to allow remote users to access private corporate
applications.
1 IPSec VPN Overview on page 80
vShield Edge modules support site-to-site IPSec VPN between a vShield Edge instance and remote sites.
2 SSL VPN-Plus Overview on page 103
With SSL VPN-Plus, remote users can connect securely to private networks behind a vShield Edge
gateway. Remote users can access servers and applications in the private networks.
IPSec VPN Overview
vShield Edge modules support site-to-site IPSec VPN between a vShield Edge instance and remote sites.
vShield Edge supports certificate authentication, preshared key mode, IP unicast traffic, and no dynamic
routing protocol between the vShield Edge instance and remote VPN routers. Behind each remote VPN router,
you can configure multiple subnets to connect to the internal network behind a vShield Edge through IPSec
tunnels. These subnets and the internal network behind a vShield Edge must have address ranges that do not
overlap.
You can deploy a vShield Edge agent behind a NAT device. In this deployment, the NAT device translates the
VPN address of a vShield Edge instance to a publicly accessible address facing the Internet. Remote VPN
routers use this public address to access the vShield Edge instance.
You can place remote VPN routers behind a NAT device as well. You must provide the VPN native address
and the VPN Gateway ID to set up the tunnel. On both ends, static one-to-one NAT is required for the VPN
address.
You can have a maximum of 64 tunnels across a maximum of 10 sites.
vShield Administration Guide
80 VMware, Inc.