To do so, use the keepalive-track command. For more information on object
trackers, see
Object tracking on page 282.
For example:
Gxxx-001(config-peer:149.49.70.1)# keepalive-track 5
Done!
Note:
DPD and object tracking can coexist and augment each other. However, object
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.
10. Specify whether to enable continuous-channel IKE phase 1, with the continuous-
channel command.
The default setting is no continuous-channel that disables continuous-channel
IKE phase 1. For more information on continuous-channel see
Continuous
channel on page 512.
For example:
Gxxx-001(config-peer:149.49.70.1)# continuous-channel
Done!
11. Exit the peer context with the exit command.
For example:
Gxxx-001(config-peer:149.49.70.1)# exit
Gxxx-001#
Configuring an ISAKMP peer-group
About this task
An ISAKMP peer-group maintains an ordered list of redundant peers. The purpose of the peer-
group is to provide a backup in the case of remote peer failure. At any point in time, only one
peer is active and acting as the remote peer. If the active peer is presumed dead, the next peer
in the peer-group becomes the active remote peer. For a full explanation of the redundancy
mechanism see
Introduction to the failover mechanism on page 529.
Note:
You can define up to 50 peer-groups.
Note:
A peer configured as initiate mode none cannot be a member of a peer-group.
IPSec VPN
492 Administering Avaya G430 Branch Gateway October 2013
Comments? infodev@avaya.com
To Next Page
Loading...
