Policy-Based Routing; Managing Policy Lists - Avaya G250 Administration

Configuring policy
QoS lists have the following parts:
Rule list — a list of filtering rules and actions for the G250/G350 to take when a packet
●
matches the rule. Match actions on this list are pointers to the composite operation table.
Actions (composite operation table) — a table that describes actions to be performed
●
when a packet matches a rule. The table includes pre-defined actions such as permit and
deny. You can configure more complex rules. Refer to
DSCP map — a table that contains DSCP code points and match action pairs. Match
●
actions are pointers to the composite operation table. Refer to

Policy-based routing

You can use policy-based routing to determine the routing path a packet takes based on the
type of packet or the packet's source or destination IP addresses or DSCP field. This enables
you to route different types of traffic over different routes or interfaces. For example, you use
policy-based routing to route voice traffic over a WAN interface and data traffic over the Internet.
Policy-based routing is implemented by means of policy-based routing (PBR) lists. PBR lists are
similar in many respects to access control lists and QoS lists. However, since there are also
some key differences, policy-based routing is explained in a separate chapter. Refer to
Configuring policy-based routing

Managing policy lists

You can manage policy lists on the Avaya G250/G350 Media Gateway with CLI commands. You
can also manage policy lists throughout your network with Avaya QoS Manager. Avaya QoS
Manager is part of Avaya Integrated Management.
illustrates the operation of policy lists on the Avaya G250/G350 Media Gateway:
444 Administration for the Avaya G250 and Avaya G350 Media Gateways
on page 465.
Figure 47: Policy lists
Composite operations
DSCP table on page
on page 445
on page 457.
460.