Note:
Do not specify an ambiguous ISAKMP peer. In other words, do not configure an
FQDN that translates to an IP address which is already associated with another
ISAKMP peer.
For example:
Gxxx-001# crypto isakmp peer address 149.49.70.1
Gxxx-001(config-peer:149.49.70.1)#
Gxxx-001# crypto isakmp peer fqdn vpn.lnd.ny.avaya.com
Gxxx-001(config-peer:vpn.lnd.ny.avaya.com)#
2. Use the
description
command to enter a description for the peer.
For example:
Gxxx-001(config-peer:149.49.70.1)# description “New York office”
Done!
3. Specify an ISAKMP policy to be used with the peer, using the
isakmp policy
command.
Important:
isakmp policy
is a mandatory command.
For example:
Gxxx-001(config-peer:149.49.70.1)# isakmp-policy 1
Done!
4. Enter the preshared key for peer authentication using the
pre-shared-key
command.
Important:
pre-shared-key
is a mandatory command.
For example:
Gxxx-001(config-peer:149.49.70.1)# pre-shared-key GNpi1odGNBrB5z4GJL
Done!
Alternatively, you can obtain a cryptographic-grade random key from the Branch
Gateway with the
suggest-key
command, and then enter it using the
pre-
shared-key
command. The suggested key-length can vary from 8 to 127
alphanumeric characters, or from 8 to 64 bytes represented in hexadecimal
notation. The default length is 32 characters.
For example:
Gxxx-001(config-peer:149.49.70.1)# suggest-key 24
The suggest key: yjsYIz9ikcwaq0FUPTF3CIrw
Gxxx-001(config-peer:149.49.70.1) pre-shared-key yjsYIz9ikcwaq0FUPTF3CIrw
Done!
IPSec VPN
490 Administering Avaya G430 Branch Gateway
October 2013
Summary of Contents for G430
Page 1: ...Administering Avaya G430 Branch Gateway Release 6 3 03 603228 Issue 5 October 2013 ...
Page 12: ...12 Administering Avaya G430 Branch Gateway October 2013 ...
Page 246: ...VoIP QoS 246 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...
Page 556: ...IPSec VPN 556 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...