Avaya G250 Administration page 373

5. If you wish to work in IKE aggressive mode, use the initiate mode aggressive
command.
Note:
Aggressive mode is one of the prerequisites for working with dynamic local peer
Note:
IP addresses. For more information about working with dynamic local peer IP
addresses, see
G350-001(config-peer:149.49.70.1)# initiate mode aggressive
Done!
6. Specify the branch device (G250/G350) by its address or by the FQDN name that identifies
the G250/G350 in the remote peer, using the self-identity command.
G350-001(config-peer:149.49.70.1)# self-identity address
Done!
Or
G350-001(config-peer:149.49.70.1)# self-identity fqdn vpn.avaya.com
Done!
Note:
Specifying self-identity as a name is one of the prerequisites for working with
Note:
dynamic local peer IP addresses. For more information about working with
dynamic local peer IP addresses, see
7. Enable DPD (Dead Peer Detection) keepalives that check whether the remote peer is up
using the keepalive command, followed by the number of seconds between DPD
keepalive probes, and the number of seconds between retries if keepalive fails. The
following example sets DPD keepalive to send probes every 10 seconds, and to send
retries every two seconds if DPD keepalive fails.
G350-001(config-peer:149.49.70.1)# keepalive 10 retry 2
Done!
8. Bind peer status to an object tracker, which can monitor hosts inside the remote peer's
protected network. To do so, use the keepalive-track command. For more information
on object trackers, see
G350-001(config-peer:149.49.70.1)# keepalive-track 5
Done!
Note:
DPD and object tracking can coexist and augment each other. However, object
Note:
tracking does not impose any requirements on the remote peer. You can
therefore use object tracking rather than DPD keepalives if the remote peer does
not support DPD.
Using dynamic local peer IP
Object tracking on page 171.
Configuring a site-to-site IPSec VPN
on page 392.
Using dynamic local peer IP
Issue 1.1 June 2005
on page 392.
373