qppb-policy inbound

Function

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

The undo qppb-policy inbound command deletes a QPPB local policy.

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

Format

qppb-policy policy-name [ unshared ] { destination | source } inbound

qppb-policy qos-local-id { destination | source } inbound

undo qppb-policy [ { qos-local-id | policy-name [ unshared ] } { destination | source } ] inbound

Parameters

Parameter	Description	Value
policy-name	Specifies the name of a QPPB local policy.	The value is a string of 1 to 31 characters.
unshared	Indicates an unshared flag for a QPPB policy. When a QPPB policy is applied to multiple interfaces, each interface separately uses the QPPB resources.	-
destination	Indicates destination-based QPPB.	-
source	Indicates source-based QPPB.	-
qos-local-id	Specifies the QoS local ID.	-

Views

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

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
qos	write

Usage Guidelines

Usage Scenario

Source-based QPPB and destination-based QPPB can be applied as required.

If source is specified in the command, the source address of routes advertised using BGP is used as the source address of traffic. If destination is specified in the command, the source address of routes advertised using BGP is used as the destination address of traffic.

Prerequisites

A QPPB local policy that defines the binding relationships between BGP routes and traffic behaviors has been configured.

Precautions

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

If both a QPPB policy and a traffic policy are configured on an interface, the QPPB policy takes effect preferentially.

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] qppb local-policy policy1
[*HUAWEI-localpolicy-policy1] quit
[*HUAWEI] interface GigabitEthernet0/1/0
[*HUAWEI-GigabitEthernet0/1/0] qppb-policy policy1 destination inbound