Terminology Legacy / MQC FRTS???

dara111983 · ‎09-04-2008

In case of FRTS when we apply the shaping parameters, for the specific traffic-class and this class is called under the #map-class frame-relay _______ .

What is the terminology used for this tech, it comes under legacy FRTS/MQC-based FRTS??

Sample config:

----------------------------------

class-map TEST

match protocol http

policy-map TEST

class TEST

class class-default

shape average 1024000

shape adaptive 512000

int se1/0

service-policy out TEST

----------------------------------

class-map TEST

match protocol http

policy-map TEST

class TEST

class class-default

shape average 1024000

shape adaptive 512000

map-class frame TEST1

service-policy output TEST

int se0/1

frame-realy interface-dlci 402

class TEST1

----------------------------------

what is the terminology used for them, since both are achieving the same?

Thanks,

Dara

Giuseppe Larosa · ‎09-05-2008

Hello Dara,

the first example is Modular QoS based.

In the second one you are using legacy FRTS just to reference to a service-policy that is again Modular QoS.

This second example could be defined an hybrid legacy FRTS/Modular QoS.

I think in the second example you would need frame-rel traffic-shaping command under se0/1 but this is a detail.

Hope to help

Giuseppe

dara111983 · ‎09-05-2008

Hi,

The router says is terming the second one as GTS.

!

class-map match-all BGP

match protocol HTTP

!

policy-map SHAPE

class HTTP

class class-default

shape average 1000000

shape adaptive 512000

!

R2(config-if)#do sh run int se 2/0

Building configuration...

Current configuration : 546 bytes

!

interface Serial2/0

description FRSW

ip address 10.10.24.2 255.255.255.0

encapsulation frame-relay

serial restart-delay 0

no dce-terminal-timing-enable

no clns route-cache

frame-relay class FRTS

frame-relay map ip 10.10.24.4 204 broadcast

no frame-relay inverse-arp

end

R2(config-if)#frame traffic-shaping

Generic traffic shaping commands must be removed before enabling frame-relay

traffic shaping.

AS you can see the interface level frame-relay traffic-shaping isn't accepted when we configure this.

Giuseppe Larosa · ‎09-06-2008

Hello Dara,

so the second example could be regarded as a GTS case.

Actually, GTS was available for non FR interfaces with commands like traffic-shape given in interface config mode.

This is interesting I had never used this variation on FR interfaces : or legacy FRTS or Modular QoS.

Best Regards

Giuseppe