★ QoS remark local-precedence setting not working on switch S6520X-54QC-EI

Not involved

The customer tried configuring the QoS on the switch but it did not work.

1. Below is the configuration on the branch core switch.

2. Expected result from this is when 192.168.201.146 transmit data through interface XGE1/0/2, the QOS is applied.

3. Line rate (lr) QoS is working but not policy-type QoS.

#

acl basic 2000

 rule 0 permit source 192.168.201.146 0

#

traffic classifier VC_SL operator and

 if-match acl 2000

#

traffic behavior VC_SL

 remark local-precedence 6

#

qos policy VC_SL

 classifier VC_SL behavior VC_SL

#

interface Ten-GigabitEthernet1/0/2

 port link-mode bridge

 description Maxis router-2

 port access vlan 301

 speed 1000

 duplex full

 storm-constrain broadcast ratio 3 3

 qos lr inbound cir 30720 cbs 35840

 qos lr outbound cir 30720 cbs 35840

 qos apply policy VC_SL inbound

 qos apply policy VC_SL outbound

 qos gts queue 6 cir 1000 cbs 512

 dhcp snooping trust

#

1.       First, use the display qos queue-statistics interface outbound command to check the outbound statistics of the port queue:

[KamparL3-A]dis qos queue-statistics int xge1/0/2 outbound

Interface: Ten-GigabitEthernet1/0/2

 Direction: outbound

 Queue 0

  Forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

  Dropped: 0 packets, 0 bytes

  Current queue length: 0 packets

 Queue 1

  Forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

  Dropped: 0 packets, 0 bytes

  Current queue length: 0 packets

 Queue 2

  Forwarded: 632095724 packets, 44322921880 bytes, 380 pps, 2272720 bps

  Dropped: 7069 packets, 10210714 bytes

  Current queue length: 0 packets

 Queue 3

  Forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

  Dropped: 0 packets, 0 bytes

  Current queue length: 0 packets

 Queue 4

  Forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

  Dropped: 0 packets, 0 bytes

  Current queue length: 0 packets

 Queue 5

  Forwarded: 202572 packets, 30953537 bytes, 0 pps, 0 bps

  Dropped: 0 packets, 0 bytes

  Current queue length: 0 packets

 Queue 6

  Forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

  Dropped: 0 packets, 0 bytes

  Current queue length: 0 packets

 Queue 7

  Forwarded: 0 packets, 0 bytes, 0 pps, 0 bps

  Dropped: 0 packets, 0 bytes

  Current queue length: 0 packets

We found that there is no packet count in queue 6.

2.       Therefore, we suspect that the packets do not enter from the XGE1/0/2 interface, so the traffic remarking configured on this interface does not take effect. Because remark lp only supports the remarking of traffic in the inbound direction.

remark local-precedence

Use remark local-precedence to configure a local precedence marking action in a traffic behavior.

Use undo remark local-precedence to restore the default.

Syntax

remark [ green | red | yellow ] local-precedence local-precedence-value

undo remark [ green | red | yellow ] local-precedence

Default

No local precedence marking action is configured.

Views

Traffic behavior view

Predefined user roles

network-admin

Parameters

green: Specifies green packets.

red: Specifies red packets.

yellow: Specifies yellow packets.

local-precedence-value: Specifies the local precedence to be marked for packets, in the range of 0 to 7.

Usage guidelines

A local precedence marking action takes effect only when the QoS policy is applied to the inbound direction.

Examples

# Configure traffic behavior database to mark matching traffic with local precedence 2.

system-view

[Sysname] traffic behavior database

[Sysname-behavior-database] remark local-precedence 2

3.       Then we checked the flow direction again. According to customer feedback, XGE1/0/23 is the interface where the traffic enters, so the traffic remark on XGE1/0/2 does not take effect.

192.168.201.146 come from interface XGE1/0/23

traffic goes to/from 192.168.18.27 through XGE1/0/2

In this case, the qos policy should be applied to the XGE1/0/23 interface, as follows:

#

interface Ten-GigabitEthernet1/0/23

 qos apply policy VC_SL inbound

#

After applying the qos policy to the incoming interface of the traffic, check the statistical information on the outgoing interface, and you can see that there are packet counts in queue 6:

The streaming result also shows that QOS has taken effect: