I am trying to implement priority queuing (LLQ) on a pair of 10GE links between a 4507 with Sup6E and a 4948 which are configured as an etherchannel. I am unable to configure a priority queue on the 4507. I am running into the following issues:
I want to have a priority queue for voice traffic and specify minimum bandwidth for a critical application. If I configure a class with the priority command it will not let me use the bandwidth command on another class unless the priority class is policed. If I try it without the police command I get the message "bandwidth kbps/percent command cannot co-exist with strict priority in the same policy-map ". If I add a police statement to the priority class then I don't get this error.
When I try to apply the resulting service-policy to the physical interface it says "% A service-policy with non-queuing actions should be attached to the port-channel associated with this physical port" and does not add the command to the config.
If I try to associate the same policy-map to the port-channel rather than the physical interface it says "% A service-policy with queuing actions can be attached in output direction only on physical ports" and does not add the command to the config.
All of the other interfaces on the 4500 are working OK. The trunks have auto qos voip trust configured and access ports are marking the critical application traffic.
The 4507 is running 12.2(44)SG1 EnterpriseK9. I don't have the luxury to upgrade blindly to fix the problem unless I can identify a specific bug that is causing the problem. Can anyone help?
Re: 4500 Sup6E priority queue on port-channel member
I did some further testing. The problem is related to the police command being needed for a priority queue but not being supported on a port-channel member, even if the port-channel and interafaces are shutdown. If I removed the police and priority commands from the class and configured bandwidth instead then I was able to apply the policy to the physical interface in the port-channel. If I then tried to change the applied policy to add the police command I got:
police command is not supported for this interface The interface does not support the specified policy configuration and/or parameter values.
I tried different police options and none of them worked while the policy was applied to the interface.
I then removed the 10GE interfaces from the port-channel and was able to apply the service policy to them, even with the police and policy commands. I was then able to configure the ports back into the port-channel. Unfortunately when I did this the interfaces were suspended and did not come up.
It therefore appears that it is not possible to have a priority queue on a port-channel on the 4500 Sup6E running this image.
could you help me please regarding upper question. In your example on portchannel configuration you have policy
SUP6E-EGRESS-POLICER which polices priority traffic to 3Gbps, right ?
Does that give 3Gig to priority traffic comparing to 20Gig (which is portchannel capacity) meaning 1.5Gig on each port or does that give 3Gig for priority traffic on each interface (3Gig on one, 3 Gig on other).
Question is basically what is this cir parameter, when you have portchannel bundle, based on ? Physical interface bandwidth or bundle bandwidth) ?
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...