3. The third step is to configure a track list object tracker which tracks the states of
object trackers 1 and 2, and calculates its own state using a boolean or threshold
calculation.
In this case, a Boolean OR argument is used. This means that the track list is up if
either
object tracker 1
or
object tracker 2 is up. For example:
Gxxx-001(config)# track 10 list boolean or
Gxxx-001(config-track list 10)# description “track list rtr-5 and rtr-6”
Done!
Gxxx-001(config-track list 10)# object 1
Done!
Gxxx-001(config-track list 10)# object 2
Done!
Gxxx-001(config-track list 10)# exit
Typical object tracking applications
• Trigger the failover mechanism for VPN. See
Typical application – VPN failover using
• Trigger the failover mechanism for interfaces. See
Typical application – backup for the
on page 293, and
Typical application – interface backup via
on page 294.
• Track the state of a route: a static route, a PBR next hop, or the DHCP client default route.
For an example of how to track the DHCP client default route, see
tracking the DHCP client default route
on page 296.
Related topics:
Typical application – VPN failover using object tracking
on page 292
Typical application – backup for the WAN FastEthernet interface
on page 293
Typical application – interface backup using policy-based routing
on page 294
Typical application – tracking the DHCP client default route
on page 296
Typical application – VPN failover using object tracking
In this application, the Branch Gateway is connected to a remote site through an IPSec VPN
tunnel. The remote site can be reached through two or more VPN gateways that can back
each other up, such as a main gateway and a backup gateway. Object tracking can monitor
the state of the current VPN connection, by monitoring one or more hosts that reside within
the remote site's network. If the current connection is lost, the Branch Gateway can failover to
a backup gateway, and attempt to establish a VPN connection to it.
A typical application of this type is described in full in
page 542.
WAN interfaces
292 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 ...