Configuring Destination-Based QPPB

Usage Scenario

QPPB is applicable to both IBGP and EBGP and can be configured for one or more ASs.

As shown in Figure 1, traffic is transmitted from provider B (AS 200) and provider C (AS 300) to provider D (AS 400) through provider A (AS 100). Providers B and C function as BGP route senders and provider A functions as a BGP route receiver. Based on the traffic control policies that are signed between providers A and D, provider A needs to limit the rate of the traffic sent to provider D.

Providers B and C advertise BGP routes carrying the community attribute to provider A. After receiving the BGP routes, provider A matches the routes with the community list, ACL list, or AS_Path list, and associates QoS policy IDs with QoS behaviors for the routes. Destination-based QPPB is enabled on the provider A interface that allows traffic to pass through. Therefore, QPPB local policies are applied to all traffic that passes through provider A.

Destination-based QPPB is applicable to both incoming and outgoing traffic on a device.

Figure 1 Networking diagram for destination-based QPPB configuration

Pre-configuration Tasks

Before configuring QPPB, complete the following tasks:

• Configure basic BGP functions.

• Configure local network routes advertised by BGP.

• Configure interfaces for setting up a BGP connection.