7606 Traffic Shaping

[dtom]

I am new to Qos so please bare with me...

I am trying to setup traffic shaping on a outgoing port.  Here is my configuration:

!

policy-map 50MBPS-SHAPER

  class class-default

    shape average 45000000 180000 0

policy-map 500MBPS-SHAPER

  class class-default

    shape average 450000000 1800000 0

policy-map 100MBPS-SHAPER

  class class-default

    shape average 90000000 360000 0

policy-map 1000MBPS-SHAPER

  class class-default

    shape average 900000000 3600000 0

!

!

!

interface TenGigabitEthernet4/7

description Outbound Port

bandwidth 10000000

no ip address

!

interface TenGigabitEthernet4/7.30

description Outbound Port - Pri

encapsulation dot1Q 2030

ip address 10.0.17.25 255.255.255.248

service-policy output 50MBPS-SHAPER  <------

!

When I try to add the service-policy to int TenG4/7.30 I get the following error message:

service-policy output 50MBPS-SHAPER

shape average command is not supported in output direction for this interface

Configuration failed!

What do I need to do here?

[amabdelh]

Can you provide the exact command that you used?

Sent from Cisco Technical Support iPhone App

[Steve Fuller]

Hi,

What is the module type that this interface is part of? Given that there's at least seven 10GE interfaces I'm suspecting it's a 10GE switching module e.g., WS-X6708-10GE, and if that's the case then I'm afraid shaping is not supported on this module type.

When you use regular switching modules in the Cisco 7600 series they use PFC QoS and shaping is not supported with PFC QoS. As per the Configuring PFC QoS in the software configuration guide:

Overview of Policers

Policing allows you to rate limit incoming and outgoing traffic so that it adheres to the traffic forwarding rules defined by the QoS configuration. Sometimes these configured rules for how traffic should be forwarded through the system are referred to as a contract. If the traffic does not adhere to this contract, it is marked down to a lower DSCP value or dropped.

Policing does not buffer out-of-profile packets. As a result, policing does not affect transmission delay. In contrast, traffic shaping works by buffering out-of-profile traffic, which moderates the traffic bursts. (PFC QoS does not support shaping.)

The PFC supports both ingress and egress PFC QoS, which includes ingress and egress policing. Traffic shaping is supported on some WAN modules.

If you want to do egress shaping then you need to use an interface of an Optical Services Module (OSM) or Shared Port Adapter.

Regards

[paul driver]

Hello

Alhough i have not checked for this device you may be able to use mls qos SRR

Which you can even shape or share bw on the interface

Res
Paul

Sent from Cisco Technical Support Android App

[Steve Fuller]

Hi,

Paul is correct that Shaped Round Robin will allow shaping, and it is supported on the Cisco 7600 with certain WS-X67xx series line modules and supervisor engines.

I've taken the following from section 6.5.4 Shaped Round Robin of the Understanding Quality of Service on the Catalyst 6500 Switch white paper:

SRR is a recent addition to the scheduling capabilities of the Catalyst 6500 family. SRR is currently available only on egress and only on the WS-X6708, the WS-X6716, the uplink ports of the Supervisor 32 and Sup720-10GE. SRR is different to WRR in that the SRR algorithm provides a way to shape outbound traffic to a stated rate. In some respects, it is similar to a policer except that traffic in excess of the rate will be buffered rather than dropped as with a policer.

SRR is configured by adding the keyword shape to the queue configuration and can only be configured if the priority queue is not used (no COS is associated with the priority queue).

I referenced the Catalyst 6500 above as it's a better description of SRR than I could find for the Cisco 7600 and it shows an example of the wrr-queue shape comand you'll need to use. The PFC QoS link I referenced in my previous post mentions SRR support for the WS-X6708-10GE module in 12.2SR so you should be OK to use this.

What I'm not sure of though is whether it will do what you need. What SRR will do is allow you to shape each queue to a specific rate or percentage of the interface bandwidth. As the interface has multiple egress queues (1P7Q8T on the WS-X6708-10GE) with each taking different classes of traffic, I think that if you want the 10GE interface shaped to some lower bandwidth you'll need to understand the traffic volume that's likely to hit each of the queues, or have all the traffic mapped to a single queue.

A couple of points to note though:

• there are restrictions in that SRR is not supported on interfaces if you're using the strict priority queue. As I think the default will have CoS 5 mapped to the strict priority queue, then you'll need to re-map your CoS values with the wrr-queue cos-map interface command before you can apply the wrr-queue shape command to the interface.
• If you change the cos-map for the Ten 4/7 interface, it will also be changed for all other interfaces that share the same port ASIC

Regards

[Rps-Cheers]

Hello，
Did you have resloved this issue?i have this problem too.