cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
10662
Views
24
Helpful
16
Replies

Unable to apply QoS service-policy output to EtherChannel on Cisco 4500 Switch

jeetkulkarni
Level 1
Level 1

Hi,

We are trying to apply QoS policy in our campus. Some of the interfaces are bundled in ether channel and I cannot apply service-policy output <service policy name> to the interface. The command looks like it applied okay but when I go to verify on show policy-map interface portchannel"X" I do not see any class-maps from the output policy. Input policy applies okay. Any obvious reasons this is happening.

Below is the software version of the switch

Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch  Software (cat4500e                                                                                      -UNIVERSALK9-M), Version 03.06.03.E RELEASE SOFTWARE (fc3)

show etherchannel summary
Flags:  D - down        P - bundled in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      f - failed to allocate aggregator

        M - not in use, minimum links not met
        u - unsuitable for bundling
        w - waiting to be aggregated
        d - default port


Number of channel-groups in use: 2
Number of aggregators:           2

Group  Port-channel  Protocol    Ports
------+-------------+-----------+-----------------------------------------------
2      Po2(SU)         PAgP      Gi1/32(P)   Gi1/35(P)
3      Po3(SU)          -        Gi1/47(P)   Gi1/48(P)   Gi7/8(P)
                                 Gi7/38(P)   Gi7/42(P)   Gi7/44(P)

1 Accepted Solution

Accepted Solutions

Hello,

you cannot configure any queuing on port channel interfaces. Queuing needs to be applied to the physical members of the port channel. Only policing and marking can be applied to the port channel interface. Typically, you would need two policies, one for policing and marking, which you would apply to the port channel interface, and one for anything related to queuing, which you would apply to the channel members.

Here is an example:

policy-map CIR_CLASS_A
 class CLASS_A
  police cir 500m

policy-map P_B_Q_CLASS_A_B
 class CLASS_A
  priority
class CLASS_B
 bandwidth remaining percent 30
  queue-limit 8192

interface PortChannel1
 service-policy output CIR_CLASS_A

interface GigabitEthernet1/1
 channel-group 1
 service-policy output P_B_Q_CLASS_A_B

interface GigabitEthernet1/2
 channel-group 1
 service-policy output P_B_Q_CLASS_A_B

View solution in original post

16 Replies 16

Hello,

you cannot configure any queuing on port channel interfaces. Queuing needs to be applied to the physical members of the port channel. Only policing and marking can be applied to the port channel interface. Typically, you would need two policies, one for policing and marking, which you would apply to the port channel interface, and one for anything related to queuing, which you would apply to the channel members.

Here is an example:

policy-map CIR_CLASS_A
 class CLASS_A
  police cir 500m

policy-map P_B_Q_CLASS_A_B
 class CLASS_A
  priority
class CLASS_B
 bandwidth remaining percent 30
  queue-limit 8192

interface PortChannel1
 service-policy output CIR_CLASS_A

interface GigabitEthernet1/1
 channel-group 1
 service-policy output P_B_Q_CLASS_A_B

interface GigabitEthernet1/2
 channel-group 1
 service-policy output P_B_Q_CLASS_A_B

Just to add to that , you need to take the physical interfaces out of the port-channel before you can apply the service command and then put it back into the port-channel , that's the workaround for pos

Hi Mark,

I tried that it allows me to add the service policy after i remove it from the channel group (no channel-group xx mode desirable

But after that it does not allow me to add it back to the channel group. Any ideas? 

Thanks again for all the help.

hmm odd that's exactly how we did it on our 4500s :) , have you tried shutting the interfaces altogether and try again as below its working for us but higher image so it does work  but were using lacp , couldn't see how that makes a diff though , this is specified in the docs somewhere too , that's how we found it got it working

#sh ver | i SPA
System image file is "bootflash:cat4500e-universalk9.SPA.03.06.06.E.152-2.E6.bin"
#sh run int po11
Building configuration...

Current configuration : 181 bytes
!
interface Port-channel11
 description description L2 E11 -  XHD-ACC1-12C1 To XHD-DIST1-DC1
 switchport
 switchport mode trunk
 flowcontrol receive on
 ip dhcp snooping trust
end

#sh run int te5/1
Building configuration...

Current configuration : 208 bytes
!
interface TenGigabitEthernet5/1
 description *To xxxxxxxxxxxxx(Ten1/1) Port-channel11
 switchport mode trunk
 channel-group 11 mode active
 service-policy output EGRESS-QUEUING
 ip dhcp snooping trust
end


Group  Port-channel  Protocol    Ports
------+-------------+-----------+-----------------------------------------------
11     Po11(SU)        LACP      Te5/1(P)    Te5/2(P)

Thanks again.


I have tried interface after interface.


1. Shutdown the interface

2. Remove it from Ether channel group

3. Apply service policy and I get this error/output

- (config-if)#channel-group 2 mode desirable
GigabitEthernet1/32 is not added to port channel
4. I tried no shut and apply the command, same output.

Any ideas :|

Hello,

odd indeed. Try the 'interface-range' command instead of individual interfaces...

Hi

Just re-read the original post , you cant do that show policy-map interface portchannel x... it must be the physical interface you check when its applied not the PO

if the command is taken please check can you see the output on the physical interface , there is no policy output on a 4500 on logical interface

as well just seen another post to show its definitely possible  as we have it on ours and Rolf has it on his 4500 on this post , on how to alter the service policy without dropping the po

ket us know how your getting on , maybe your hittin some weird ios issue if its not happening

https://supportforums.cisco.com/discussion/13291791/disable-qos-consistency-check-c4ksup7-etherchannel

Thanks Mark. Not sure if this is a bug.

I tried creating a new port channel with 2 new ports in range but cannot apply the policy on the range too.

nzaklnet1(config)#int range g1/6-7
nzaklnet1(config-if-range)#service-policy output Output-Policy
nzaklnet1(config-if-range)#channel-group 4 mode desirable
GigabitEthernet1/6 is not added to port channel
% Range command terminated because it failed on GigabitEthernet1/6
nzaklnet1(config-if-range)#channel-group 4 mode auto
GigabitEthernet1/6 is not added to port channel
% Range command terminated because it failed on GigabitEthernet1/6

Have asked the same on the other question thread.

Have you tried removing the service policy, adding the ports to the channel, then adding the service policy to the port channel instead?

Some things have to be applied to the port channel and not the individual ethernet ports.

-Mike

Thanks again Malone.

I think I may be close to the solution. Below link explains the etherchannel configuration on QoS.

http://www.ciscopress.com/articles/article.asp?p=2159353&seqNum=4

I think I have to rewrite the QoS policy.

(For EtherChannel interfaces configured on Catalyst 4500-E Supervisor 6-E/7-E switches, the ingress QoS policies (including classification, marking, and/or policing policies) are applied via MQC service-policy statements (in the ingress direction using the input keyword) configured on the logical Port-Channel interface. Trust statements are not required, as these supervisors implicitly trust by default. Additionally, these supervisors support egress marking and/or policing policies to be similarly applied via MQC service-policy statements (in the egress direction using the output keyword) on the logical Port-Channel interface.)

Have you got any solution with MQC service-policy setup? Just trying to find some guidance around that.

Hi

all our 4500s are just access switches we have fairly large setup in regions so I didn't do full layer 3 MQC custom specific policy but we do have policy's In place as its auto qos , we just turned on auto qos at layer 2 and it created the policy maps for us as that's all we needed , we only do major tweaks on our full routers facing mpls etc for custom MQC , we just tested this though packet captures after we enabled it and everything we needed was being marked correctly

so its all auto but just to show you this is what's generated , its basic enough mainly to ensure voice video is prioritised in case the local network comes under stress

we set this only on layer 2 ports to generate this below .... auto qos voip trust

we apply it to all layer 2 ports and the port-channel outbound only

interface Port-channel11
 description 
 switchport
 switchport mode trunk
 flowcontrol receive on
 ip dhcp snooping trust


!
interface TenGigabitEthernet5/1
 description 
 switchport mode trunk
 channel-group 11 mode active
 service-policy output EGRESS-QUEUING
 ip dhcp snooping trust

class-map match-all MULTIMEDIA-STREAMING-QUEUE
 match dscp af31  af32  af33
class-map match-any CONTROL-MGMT-QUEUE
 match dscp cs7
 match dscp cs6
 match dscp cs3
 match dscp cs2
class-map match-all AutoQos-VoIP-Control-Dscp26
 match dscp af31
class-map match-all TRANSACTIONAL-DATA-QUEUE
 match dscp af21  af22  af23
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 SCAVENGER-QUEUE
 match dscp cs1
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 MULTIMEDIA-CONFERENCING-QUEUE
 match dscp af41  af42  af43
class-map match-all BULK-DATA-QUEUE
 match dscp af11  af12  af13
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-any PRIORITY-QUEUE
 match dscp ef
 match dscp cs5
 match dscp cs4
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 EGRESS-QUEUING
 class PRIORITY-QUEUE
  priority
 class CONTROL-MGMT-QUEUE
  bandwidth remaining percent 10
 class MULTIMEDIA-CONFERENCING-QUEUE
  bandwidth remaining percent 10
 class MULTIMEDIA-STREAMING-QUEUE
  bandwidth remaining percent 10
 class TRANSACTIONAL-DATA-QUEUE
  bandwidth remaining percent 10
    dbl
 class BULK-DATA-QUEUE
  bandwidth remaining percent 4
    dbl
 class SCAVENGER-QUEUE
  bandwidth remaining percent 1
 class class-default
  bandwidth remaining percent 25
    dbl
policy-map AutoQos-VoIP-Input-CiscoPhone-Cos-Policy
 class AutoQos-VoIP-Bearer-Cos
  set qos-group 46
 class AutoQos-VoIP-Control-Cos
  set qos-group 24
 class class-default
  set dscp default
  set cos 0
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
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
!

access port


interface GigabitEthernet1/48
 description
 switchport access vlan 36
 switchport mode access
 switchport nonegotiate
 auto qos voip trust
 spanning-tree portfast
 spanning-tree bpduguard enable
 service-policy input AutoQos-VoIP-Input-Cos-Policy
 service-policy output AutoQos-VoIP-Output-Policy
 ip dhcp snooping limit rate 7

we run all our tech stuff though TAC too most of the time as best practice checks too , we have had no issues with this setup ,and its on a lot of 45s globally

Thanks Matthew. I figured out by George's response above.

Only policing and marking can be applied to the port channel interface and queuing on physical interface.

I was able to apply the service-policy by creating a new policy all together for port channel interface.

Thanks for your support and guidance.

Thanks George, sorry did not read your answer carefully at first.

I got the 2nd part working as I was able to apply the output policy after removing the policing and marking. However I cannot get the policy to work on port channel interface. My policy looks like one below.

Policy Map Output-Policy_PortChannel_virtualin
Class  Output-Priority-Queue
priority
police cir percent 30
conform-action transmit
exceed-action drop

Can the above not be applied to PortChannel Interface?

Review Cisco Networking products for a $25 gift card