PBR rule criteria
The rule criteria for PBR rules are largely the same as the rule criteria for other policy list rules.
Refer to Policy lists rule criteria on page 569 for an explanation of the rule criteria, including
explanations and examples of the commands used to set the criteria.
Unlike other policy lists, PBR lists do not use composite operations. Thus, there is no
composite-operation command in the context of a PBR rule. Instead, PBR lists use next
hop lists. For an explanation of next hop lists, see Next hop lists on page 594.
Enter next-hop list, followed by the list number of a next hop list, to specify a next hop list
for the Branch Gateway to apply to packets that match the rule. You can specify Destination
Based Routing instead of a next hop list, in which case the Branch Gateway applies
destination-based routing to a packet when the packet matches the rule.
If the next hop list specified in the rule does not exist, the Branch Gateway applies destination-
based routing to packets that match the rule.
Next hop lists
PBR rules include a next hop list. When the rule matches a packet, the Branch Gateway routes
the packet according to the specified next hop list.
Each next hop list can include up to 20 entries. An entry in a next hop list can be either an IP
address or an interface. The Branch Gateway attempts to route the packet to the first available
destination on the next hop list. If every destination on the list is unavailable, the Branch
Gateway routes the packet according to destination-based routing.
Related topics:
Modifying next hop lists on page 594
Modifying next hop lists
Procedure
1. To modify a next hop list, you must enter the context of the next hop list.
To enter a next hop list context, enter ip next-hop-list followed by the number
of the list you want to edit.
For example, to modify next hop list 1, enter ip next-hop-list 1.
2. To show the next hops in an existing list, enter the context of the next hop list and
enter show next-hop.
Policy-based routing
594 Administering Avaya G430 Branch Gateway October 2013
Comments? infodev@avaya.com
To Next Page
Loading...
