[QOS-R5.0]: Not able to set qos queue scheduling

Bug #1770316 reported by Pulkit Tandon on 2018-05-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R5.0
Fix Committed
High
Kiran
Trunk
Fix Committed
High
Kiran

Bug Description

Not able to set scheduling parameters using qosmap utility.
Vrouter giving an error:

[root@nodei38 /]# qosmap --get-queue enp4s0f1
vRouter: DCB 22 failed with error 5632
vRouter: Unknown DCBX mode 0

[root@nodei38 /]# qosmap --set-queue enp4s0f1 --dcbx ieee --bw 5,10,15,20,20,15,10,5 --strict 01010101
NOTE: Bandwidth specification does not work with strict priority
Priority Operation
Interface: enp4s0f1
DCBX: IEEE
DCB State: Disabled

                               P0 P1 P2 P3 P4 P5 P6 P7
Traffic Class: 0 1 2 3 4 5 6 7

                              TC0 TC1 TC2 TC3 TC4 TC5 TC6 TC7
Priority Group: 0 1 2 3 4 5 6 7

                              PG0 PG1 PG2 PG3 PG4 PG5 PG6 PG7
Priority Group Bandwidth: 5 0 15 0 20 0 10 0
Strictness: 0 1 0 1 0 1 0 1
vRouter: DCB 23 failed with error 5888
vRouter: Set DCBX failed (Req/Resp: 9/5888)

Also, on DCB enable on the interface, not able see it as "on"
```
[root@nodei38 /]# dcbtool gc enp4s0f1 dcb
Command: Get Config
Feature: DCB State
Port: enp4s0f1
Status: Successful
DCB State: off
[root@nodei38 /]#
[root@nodei38 /]# dcbtool sc enp4s0f1 dcb on
Command: Set Config
Feature: DCB State
Port: enp4s0f1
Status: Successful
[root@nodei38 /]#
[root@nodei38 /]# dcbtool gc enp4s0f1 dcb
Command: Get Config
Feature: DCB State
Port: enp4s0f1
Status: Successful
DCB State: off
[root@nodei38 /]#

```

Tags: qos Edit Tag help
Kumar Harsh (hkumar) wrote :

Bandwidth specification does not work with strict priority (not supported by vrouter)

Need to look into 2nd part of bug .

Review in progress for https://review.opencontrail.org/45151
Submitter: Kiran (<email address hidden>)

Review in progress for https://review.opencontrail.org/45178
Submitter: Kiran (<email address hidden>)

Reviewed: https://review.opencontrail.org/45151
Committed: http://github.com/Juniper/contrail-vrouter/commit/7c12561690e621b419933feaf03f1f61f40c192b
Submitter: Zuul v3 CI (<email address hidden>)
Branch: master

commit 7c12561690e621b419933feaf03f1f61f40c192b
Author: Kiran Kasim <email address hidden>
Date: Tue Jul 31 17:45:06 2018 -0700

Fix for qosmap not working

While refractoring vrouter-utils/ library for *nix and windows, due to
incorrect offset calculation of nlmsghdr when parsing OS specific nl
replies, qosmap was not working. Fixing the same.

Change-Id: Idae686f3082d912ff5411dd4e0f693e675c2d821
Closes-Bug: 1770316

OpenContrail Admin (ci-admin-f) wrote :

Reviewed: https://review.opencontrail.org/45178
Committed: http://github.com/Juniper/contrail-vrouter/commit/159f1700422f53e94d2c99986b7993f8543ff87b
Submitter: Zuul v3 CI (<email address hidden>)
Branch: R5.0

commit 159f1700422f53e94d2c99986b7993f8543ff87b
Author: Kiran Kasim <email address hidden>
Date: Tue Jul 31 17:45:06 2018 -0700

Fix for qosmap not working

While refractoring vrouter-utils/ library for *nix and windows, due to
incorrect offset calculation of nlmsghdr when parsing OS specific nl
replies, qosmap was not working. Fixing the same.

Change-Id: Idae686f3082d912ff5411dd4e0f693e675c2d821
Closes-Bug: 1770316

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers