Configuring object tracking

Last Updated : Mar 26, 2020 |

Procedure

  1. Configure RTRs to monitor remote devices and learn if their state is up or down.

    Each RTR has a state:

    • inactive. Not running

    • up. The remote device is considered up

    • down. The remote device is considered down

  2. Configure object trackers to track the states of RTRs.

    Each object tracker calculates its own state as either up or down based on the states of the elements it is tracking. Whenever the state of an object tracker changes, it notifies the applications registered with it.

    An object tracker calculates its own state as follows:

    • For an object tracker tracking a single RTR:

      • If the state of the RTR is up, the state of the object tracker is up.

      • If the state of the RTR is inactive or down, the state of the object tracker is down.

    A track list applies a configurable formula (using a Boolean or a Threshold calculation) to the states of the objects comprising the list, and the result (up/down) is the state of the track list. For example, if the configured formula is the Boolean AND argument, then the state of the list is up if the state of all its objects is up, and down if the state of one or more of its objects is down.

    Note:

    You can register either a VPN tunnel or an interface with an object tracker. For more information see the definition of the keepalive-track command in the Avaya Branch Gateway G450 CLI Reference.

    You cannot configure both DHCP Client and object tracking on the same WAN FastEthernet interface. You can however, configure tracking on the DHCP client default route.