Friday, January 15, 2016

ME3600 policy-maps - queue limit - leaf level

Platform supports three level hierarchy - Port, VLAN and Class.
Class is the leaf level.
Queuing is done only at the leaf level.
You need to attach your policy to the port level policy so that it can be a two level policy.

Three Level Class-default Policy Example:

policy-map leaf
class class-default
queue-limit xxxxx bytes
policy-map logical
class class-default
service-policy leaf
policy-map root
class class-default
service-policy logical
Invalid Queue-Limit Policy Configuration Example:
This case "class-default" is being considered as the port level.
Following QOS policy configuration failed because the configuration check assumes user is trying to apply the queue-limit at the vlan level which is not supported.
policy-map child-1
class class-default
  queue-limit 256 packets
!
policy-map VLAN-OUT
class class-default       <<< Class default is being assumed at the port level , Child policy at the second level
  shape average 5000000
  service-policy child-1
!
interface GigabitEthernet0/5
switchport trunk allowed vlan none
switchport mode trunk
!
service instance 2 ethernet
  encapsulation dot1q 60
  rewrite ingress tag pop 1 symmetric
  bridge-domain 60
3600-HL-2-N(config)#interface GigabitEthernet0/5
3600-HL-2-N(config-if-srv)#service-policy output VLAN-OUT
QOS: queue-limit command not supported in non-leaf classes
QoS: Policy attachment failed for policymap VLAN-OUT
*Feb 13 09:55:28.700: %QOSMGR-3-QLIMIT_LEVEL_ERROR: Qlimit command not supported in non-leaf classes

No comments:

Post a Comment