Source-Based Transit Provider Selection; Backup; Defining Pbr Lists - Avaya G350 Administration

Configuring policy-based routing

Defining PBR lists

Figure 14: Policy-based routing — Voice/Data Division By DSCP
Router
Headquarters

Source-based transit provider selection

Internet service providers and other organizations can use policy-based routing to route traffic originating
from different sets of users through different Internet connections across policy routers.

Backup

You can utilize policy-based routing to define backup routes for defined classes of traffic. If the first route
on the list fails, the packets can be routed to another hop. When necessary, you can use the NULL
interface to drop packets when the primary next hop fails. For example, voice packets are usually sent
over a WAN interface, and not the Internet. You can configure a PBR list to drop voice packets when the
WAN interface is down.
Defining PBR lists
To create or edit a PBR list, you must enter the context of the list. If the list already exists, you can edit
the list from the list context. If the list does not exist, entering the list context creates the list.
To create or edit a PBR list, type
pre-configured PBR lists.
PBR lists have the following attributes:
•
Name
•
Owner
To define these attributes:
1
Enter the context of the PBR list in which you want to define the attribute.
2
Enter one of the following commands, followed by a text string or integer:
— name — defines a list name (text string). The default value is owner.
— owner — defines a list owner (text string). The default value is list#<listnumber>.
178
T1
ISP
T1
ip pbr-list , followed by a list number in the range 800-899. There are no
Administration of the Avaya G350 Media Gateway
Voice -
DSCP=34,
41,43,44,46
Data -
Default
WAN
xDSL1
ETH
Small Branch
G350
June 2004