Avaya G430 Manual page 486

IPSec VPN
Configuring an ISAKMP peer-group
Configuring crypto maps
Configuring crypto lists
Access control lists
Configuring global parameters
Assigning a crypto list to an interface
VPN peer coordination
Before commencing IPSec VPN configuration, you must resolve jointly with your VPN peer the
basic parameters so that IPSec VPN can be set up symmetrically in the two peers. If the IPSec
VPN configuration in the two peers does not match, no VPN is created.
Note:
If you will be defining a peer-group which maintains a list of redundant peers, each of the
peers in the group must be configured to match the Branch Gateway.
The basic parameters include:
• The IKE phase 1 parameters (as defined in the ISAKMP policy, see
policies
• The IKE phase 2 parameters (as defined in the transform-set, see
sets on page 488)
• The ISAKMP peer parameters (see
• Which packets should be secured (as defined in the crypto list, see
lists on page 495)
• The peer addresses. For each peer, the local address entered in the crypto list (see
Configuring crypto lists
peer (see
• NAT Traversal, if your installation includes one or more NAT devices between the local
and remote VPN peers. See
See Configuring IPSec VPN logging
configuration in both peers so as to pinpoint the problem in case of a mismatch between the
two peers.
Configuring ISAKMP policies
About this task
An ISAKMP policy defines the IKE phase 1 parameters.
Note:
You can configure up to 40 ISAKMP policies.
486 Administering Avaya G430 Branch Gateway
on page 493
on page 495
on page 498
on page 499
on page 486)
on page 495) should match the ISAKMP peer address in the other
Configuring ISAKMP peer information
Configuring global parameters
Comments? infodev@avaya.com
on page 492
on page 500
Configuring ISAKMP peer information
on page 489).
on page 503 for information on how to view IPSec VPN
Configuring ISAKMP
Configuring transform-
on page 489)
Configuring crypto
on page 499.
October 2013