qppb-policy ip-precedence

Function

The qppb-policy ip-precedence command applies a QPPB local policy to an interface.

The undo qppb-policy ip-precedence command cancels the configuration.

By default, no QPPB local policy is applied to an interface.

Format

qppb-policy ip-precedence destination

qppb-policy ip-precedence source

undo qppb-policy [ ip-precedence ]

Parameters

Parameter	Description	Value
source	Indicates source-based QPPB.	-
destination	Indicates destination-based QPPB.	-

Parameter

Description

Value

source

Indicates source-based QPPB.

destination

Indicates destination-based QPPB.

Views

100GE interface view, 10G LAN interface view, 10G WAN interface view, 400GE interface view, 40GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
qos	write

Usage Guidelines

Usage Scenario

You can run this command to configure QPPB to be based on routing policies.

On a large and complex network, a large number of complex traffic classification operations are required, and routes cannot be classified based on the community attribute, ACL, IP prefix, or AS_Path. When a network topology keeps changing, configuring or changing routing policies is difficult or even impossible to implement.

QPPB is introduced to reduce the configuration workload. In QPPB, the sender of the BGP routes can set attributes for the BGP route to pre-classify routes. This simplifies the policy modification on the route receiver. To meet the requirements, you only need to configure the BGP routing policy.

QPPB is applicable to both IBGP and EBGP and can be configured in an AS or between different ASs.

Prerequisites

Basic BGP functions have been configured and BGP peers have been set up before QPPB is configured.

Configuration Impact

QPPB configured on the inbound interface is valid for all the packets that meet the matching rules.

Precautions

BGP routes in QPPB refer to only BGP routes on the public network.

This command applies to VLAN-type dot1q sub-interfaces, dot1q VLAN tag termination sub-interfaces, and QinQ VLAN tag termination sub-interfaces.

In a QPPB application scenario, if only the remark dscp command is run, the command takes effect for both IPv4 and IPv6 packets. If both the remark dscp and remark ipv6 dscp commands are run, the remark dscp command takes effect for IPv4 packets whereas the remark ipv6 dscp command takes effect for IPv6 packets.

Example

# Enable QPPB on an interface, bind a QoS local ID to a traffic behavior in a QPPB local policy, and implement destination-based QPPB.

<HUAWEI> system-view
[~HUAWEI] interface GigabitEthernet 0/1/32
[~HUAWEI-GigabitEthernet0/1/32] qppb-policy ip-precedence destination