cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5142
Views
0
Helpful
1
Replies
Highlighted
Beginner

QOS: egress police command not supported in non-leaf classes

Hello,

I have issue with egress policers on EFP (Service instance).

When configure two egress policers on EFPs (on one physical interface), I received a message:

ME-3600X(config-if-srv)#service-policy output VLAN-50M

QOS: egress police command not supported in non-leaf classes

QoS: Policy attachment failed for policymap VLAN-50M

The configuration looks easy:

policy-map VLAN-50M

class VLAN

  police cir 50000000

   exceed-action drop

class-map match-all VLAN

match protocol ip

interface GigabitEthernet0/11

description TEST

switchport trunk allowed vlan none

switchport mode trunk

mtu 1998

load-interval 30

service instance 199 ethernet

  encapsulation dot1q 199

  rewrite ingress tag pop 1 symmetric

  service-policy output VLAN-50M

  xconnect 82.119.245.231 3291 encapsulation mpls

!

service instance 500 ethernet

  description L2MNG-SWITCHE

  encapsulation dot1q 500

  rewrite ingress tag pop 1 symmetric

  bridge-domain 500

I tried to attach the same policy-map to Service Instance 500, with the messages above mentioned.

I am not sure if this is correct behaviour, and what means term "non-leaf class".

IOS version is 15.2(4)S2 with AdvancedMetroIPAccess.

Best regards,

Josef

1 REPLY 1
Highlighted
Beginner

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

Content for Community-Ad

This widget could not be displayed.