about traffic shaping

[historicalswimming]

Could you please  give me the simplest configuration  to  shape  all outgoing traffic  in cisco iou GNS3 to 20 mpbs ?

[Joseph W. Doherty]

For what device running what IOS?

[M02@rt37]

Hello @historicalswimming,

Basic config to adapt following your equipement and you case:

interface GigabitEthernet0/0
description LAN interface
ip address 192.168.1.1 255.255.255.0

interface GigabitEthernet0/1
description WAN interface
ip address 100.0.0.1 255.255.255.0
service-policy output SHAPE-TRAFFIC

class-map match-any TRAFFIC
match any

policy-map SHAPE-TRAFFIC
class TRAFFIC
shape average 20000000

--Class-map match any traffic, the service-policy is applied directly to the WAN interface (GigabitEthernet0/1). This ensures that all outgoing traffic on the WAN interface will be shaped to a rate of 20 Mbps.

[Joseph W. Doherty]

What M02@rt37 describes would be one way to shape all interface traffic to 20Mbps.

But is it the "simplest" approach?  I believe not.

Possibly a simpler CBWFQ policy would be to drop the class-map TRAFFIC, and within the policy-map, use class "class-default" instead.

However, even using CBWFQ assumes your GNS3 device supports it (which it likely does).  However, if you truly want the "simplest" shaping, before CBWFQ, there was interface GTS (generic traffic shaping).  I recall (?), though the later IOS versions have stopped supporting this, but often IOS being used with GNS3 is an older version.

Definitely, both traffic shaping features were available on many IOS versions, and I would usually recommend using the CBWFQ version, if available, but if you truly want "simplest", I suggest GTS is that.

[paul driver]

Hello
You could apply a simple Hqos policy to traffic shape to 20MB

access-list 1 permit any
class-map  all_traffic_cm
match access-group 1

policy_map child_pm
class all_traffic_cm
fair-queue

policy_map parent_pm
class class-default
shape average 20mb
service-policy child_pm

int x/x
description WAN
service-policy output parent_pm

[Joseph W. Doherty]

Ah, @paul driver reply appears to have been posted while I was composing my prior reply.

Basically, what I wrote in my prior reply, also applies to Paul too.

I.e. For the "simplest configuration" CBWFQ approach, likely:

policy-map SimpleShaper
class class-default
shape average 20000000

interface x
service-policy output SimpleShaper

Possibly the "simplest configuration":

interface x
traffic-shape rate 20000000

If you factor in other considerations, for using a shaper, beyond it being the "simplest configuration", then what both Paul and M02@rt37 have shown, should be considered.  For example, Paul's example of using a child policy.