Avaya G430, Manual

Page: 591 / 696

Note:
You can also perform this step before defining PBR lists and rules.
Enter
ip next-hop-list
, followed by the number of the list, to define a next hop
list. In the next hop list context, use the following commands to define the next hops
in the list:
• Enter
next-hop-ip
, followed by the index number of the entry in the next
hop list, to define an IP address as a next hop. You can optionally apply
tracking to monitor the route.
• Enter
next-hop-interface
, followed by the index number of the entry in
the next hop list, to define an interface as a next hop. You can optionally apply
tracking to monitor the route.
You can also use the
name
command to assign a name to the next hop list.
Note:
You cannot use a FastEthernet Interface as an entry on a next hop list unless the
interface was previously configured to use
PPPoE
encapsulation, or was
configured as a DHCP client. See Configuring PPPoE on page 252, and DHCP
client configuration on page 204.
A next hop list can include the value NULL0. When the next hop is NULL0, the
Branch Gateway drops the packet. However, you cannot apply tracking to
NULL0.
The following example creates next hop list 1, named “Data to HQ”, with the
following entries:
• The first entry is the FastEthernet 10/2 interface. Object tracker 3 is applied to
monitor the route. For details about configuring the object tracker see Object
tracking on page 282.
• The second entry is IP address 172.16.1.221. This is the IP address of the
external Layer 3 router connected to the Branch Gateway.
• The third entry is NULL0, which means the packet is dropped
Gxxx-001(super)# ip next-hop-list 1
Gxxx-001(super-next hop list 1)#name “Data_to_HQ”
Done!
Gxxx-001(super-next hop list 1)#next-hop-interface 1 FastEthernet 10/2
track 3
Done!
Gxxx-001(super-next hop list 1)#next-hop-ip 2 172.16.1.221
Done!
Gxxx-001(super-next hop list 1)#next-hop-interface 3 Null0
Done!
Gxxx-001(super-next hop list 1)#
For additional details about next hop lists, see Next hop lists on page 594.
Policy-based routing
Administering Avaya G430 Branch Gateway October 2013 591