Guest

Preview Tool

Cisco Bug: CSCvu44586 - Request vManage QoS Local only push custom created names in configuration

Last Modified

Jun 04, 2020

Products (1)

  • Cisco SD-WAN

Known Affected Releases

20.1

Description (partial)

Symptom:
For the configuration that is pushed from the vManage for QoS, we currently push both the default (QueueX) and the custom created class names.   For cEdges, the default class names are what is places in the policy map.  For vEdges, the qos-scheduler uses the default names. 

This is an enhancement request to have vManage only push the custom class names, rather than both to make the configuration more intuitive.

Current configuration pushed from QoS Local Policy from vManage:
class-map match-any Queue0
   match qos-group 0
  !
  class-map match-any Queue1
   match qos-group 1
  !
  class-map match-any Queue2
   match qos-group 2
  !
  class-map match-any Queue3
   match qos-group 3
  !
  class-map match-any Queue4
   match qos-group 4
  !
  class-map match-any Queue5
   match qos-group 5
  !
  class-map match-any Queue6
   match qos-group 6
  !
  class-map match-any bulk
   match qos-group 1
  !
  class-map match-any control
   match qos-group 0
  !
  class-map match-any critical
   match qos-group 2
  !
  class-map match-any cs1-af11
   match qos-group 4
  !
  class-map match-any cs2-cs6
   match qos-group 5
  !
  class-map match-any cs4-af41
   match qos-group 6
  !
  class-map match-any default
   match qos-group 3
  !
  policy-map Exelon_Repro
   class Queue0
    priority level 1
    police rate percent 10
    !
   !
   class Queue1
    bandwidth remaining ratio 20
    random-detect precedence-based
   !
   class class-default
    bandwidth remaining ratio 25
    random-detect precedence-based
   !
   class Queue3
    bandwidth remaining ratio 15
    random-detect precedence-based
   !
   class Queue4
    bandwidth remaining ratio 5
    random-detect precedence-based
   !
   class Queue5
    bandwidth remaining ratio 5
    random-detect precedence-based
   !
   class Queue6
    bandwidth remaining ratio 20
    random-detect precedence-based
   !
  !
  policy
  class-map
    class Queue0 queue 0
    class Queue1 queue 1
    class Queue2 queue 2
    class Queue3 queue 3
    class Queue4 queue 4
    class Queue5 queue 5
    class Queue6 queue 6
    class bulk queue 1
    class control queue 0
    class critical queue 2
    class cs1-af11 queue 4
    class cs2-cs6 queue 5
    class cs4-af41 queue 6
    class default queue 3
   !

Conditions:
vManage on 20.1.1
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.