Typical Application - Tracking The Dhcp Client Default Route - Avaya G250 Administration

Configuring WAN interfaces
When the WAN Fast Ethernet is up, policy-based routing routes this traffic via the WAN Fast
Ethernet interface. When the track list defined in the previous typical application is down,
policy-based routing routes this traffic through the Serial interface 2/1:1. When the track list is
up again, the traffic is again routed through the WAN Fast Ethernet interface.
! Create PBR list 801. This list routes traffic from IP address
! 149.49.42.1 to IP address 149.49.43.1 according to next hop list 10.
!
ip pbr-list 801
name "list #801"
ip-rule 10
exit
!
! Assign PBR list 801 to interface Vlan 1.
!
interface Vlan 1
icc-vlan
ip pbr-group 801
ip address 149.49.42.254
exit
!
! Configure next hop list 10 with interface FastEthernet 10/2 as the
! first next hop, and interface Serial 2/1:1 as the second next hop.
!
ip next-hop-list 10
next-hop-interface 5 FastEthernet 10/2
next-hop-interface 10 Serial 2/1:1
exit
Typical application – tracking the DHCP client default route
This typical application demonstrates a case where a user configures DHCP client on the
device to enable cable modem connection to the WAN Fast Ethernet interface. The user wishes
to know whether the DHCP client default route can be used for routing decisions, i.e., whether
traffic can be routed over this default route. To do so, the user activates tracking to monitor the
remote HQ peer. When the object tracker is up, the DHCP default route may be used. When the
object tracker is down, the DHCP default route is not used for routing and traffic is routed to
alternate routes.
270 Administration for the Avaya G250 and Avaya G350 Media Gateways
next-hop list 10
source-ip host 149.49.42.1
destination-ip host 149.49.43.1
exit
255.255.255.0