4500/4900 Cannot apply Autoqos Policy to etherchannel member

Unanswered Question
Mar 8th, 2010

I have two 4900M Cisco switches connected together with two 10Gb (CX-4) links in an etherchannel.

The network will have an Avaya VoIP solution running over it.

Only needing basic QoS so I have implemented the Auto Qos feaure as the policy it generates is more than satisfactory for the limited environment of this network.

This is the default (auto generated policy)

class-map match-all AutoQos-VoIP-Control-Dscp26

match dscp af31

class-map match-all AutoQos-VoIP-Control-Dscp24

match dscp cs3

class-map match-all AutoQos-VoIP-Bearer-Cos

match cos 5

class-map match-all AutoQos-VoIP-Control-QosGroup24

match qos-group 24

class-map match-all AutoQos-VoIP-Control-QosGroup26

match qos-group 26

class-map match-all AutoQos-VoIP-Bearer-QosGroup

match qos-group 46

class-map match-all AutoQos-VoIP-Bearer-Dscp

match dscp ef

class-map match-all AutoQos-VoIP-Control-Cos

match cos 3

!

!

policy-map AutoQos-VoIP-Input-Dscp-Policy

class AutoQos-VoIP-Bearer-Dscp

set qos-group 46

class AutoQos-VoIP-Control-Dscp26

set qos-group 26

class AutoQos-VoIP-Control-Dscp24

set qos-group 24

policy-map AutoQos-VoIP-Input-Cos-Policy

class AutoQos-VoIP-Bearer-Cos

set qos-group 46

class AutoQos-VoIP-Control-Cos

set qos-group 24

policy-map AutoQos-VoIP-Output-Policy

class AutoQos-VoIP-Bearer-QosGroup

set dscp ef

set cos 5

priority

police cir percent 33

class AutoQos-VoIP-Control-QosGroup26

set dscp af31

set cos 3

bandwidth remaining percent 5

class AutoQos-VoIP-Control-QosGroup24

set dscp cs3

set cos 3

bandwidth remaining percent 5

class class-default

dbl

It allows both the AutoQos-VoIP-Input-Cos-Policy and AutoQos-VoIP-Output-Policy policies to be applied to any interface, however when attempting to apply this to one of the two TenGigabit interfaces which are members of the Etherchannel between the switches it refuses to apply the Output policy saying "non-queing policies must be applied to the virtual port", trying to apply the exact same policy to the Etherchannel it again refuses saying "queing policies must be applied to the physical interface"

Looks like it's going around in circles!

Admittedly the way the network has been designed there will actually be very light usage of the 20Gb link however I know it's somthing the customer will pick up on!

Any ideas?

Tony

I have this problem too.
1 vote
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Jon Marshall Mon, 03/08/2010 - 12:58

Tony

Which IOS version are you running. There are known issues with applying auto-qos to an etherchannel with the workaround being to apply the QOS configuration manually ie. you need to configure the QOS policy and then apply it.

Jon

aiwapro09 Tue, 11/30/2010 - 10:48

Was this resolved?

I have the issue.  I attempted to follow the workaround, and it gave an error as well.  There was another thread about this, https://cisco-support2.uat3.hosted.jivesoftware.com/thread/2008852?decorator=print&displayFullThread=true#2008852 , and I have the same problem as that person did.

Here is what I get trying to enter the commands:

router(config-if)# service-policy input AutoQos-VoIP-Input-Cos-Policy

% A service-policy with non-queuing actions should be attached to the port-channel associated with this physical port.

router(config-if)# service-policy output AutoQos-VoIP-Output-Policy

% A service-policy with non-queuing actions should be attached to the port-channel associated with this physical port.

router(config-if)# interface Port-channel1

router(config-if)# service-policy input AutoQos-VoIP-Input-Cos-Policy

router(config-if)# service-policy output AutoQos-VoIP-Output-Policy

% A service-policy with queuing actions can be attached in output direction only on physical ports.

Actions

This Discussion

Related Content