Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

catalyst 4500 sup 7E qos etherchannel

Has anyone been able to configure successfully?  I followed the example and broke customers uplink as a result for about 12 minutes and the ommand wasn't on once it came back. Obviously hesitant to put it on again. Just to mention you cannot police and queue on the same policy for either the physical interfaces that make up the etherchannel or on the port channel interface.  This is what the doci indicates is the way to do it.

policy-map p1

class voice

police cir   30000000

policy-map p2

class voice

priority

int port-channel1

service-policy output p1

ing gig1/1

channel-group 1

service-policy output p2

as always thanks

1 REPLY
Cisco Employee

catalyst 4500 sup 7E qos etherchannel

Hello,

Is this the config that broke connectivity for 12 min? Not quite sure why it would cause an outage.

I believe you are referring to a known software limitation:

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsq67430

The Sup6-E and Sup7-E divide policies into "queueing" and "non-queuing"

actions. On an etherchannel, the queueing actions must be applied to the

port-channel interface and the non-queueing actions must be applied to

the physical member interfaces.  In other words, you'll need to create

two different service policies and apply one to the port-channel

interface and the other to the physical member interface.

Example queueing actions within a policy-map: priority, bandwidth,

bandwidth remaining, dbl

Example on-queueing action within a policy-map (policing and marking):

set dscp, set ip prec, set qos, police

Fabienne

LAN-Switching TAC

827
Views
0
Helpful
1
Replies