In How to traffic shape frame-relay? part 1 , i have mentioned four types of QoS mechanism that can be applied to frame-relay interface. Lets have a look at the other two methods that can be used with frame-relay networks.
MQC Frame-Relay Traffic shaping
In here, we see the efforts put into introducing the MQC style for traffic shaping. but with this method, you nest the MQC into a map-class. Yes, it doesn’t look pretty, and seems slightly confusing. But let’s have an example, and this will ease our understanding of the topic.
shape average 256000 2560 0
shape adaptive 128000
map-class frame-relay TEST_DLCI
service-policy output SHAPE
interface Serial 0/0.1
frame-relay interface-dlci 101
This example lengthy as it seems, but it is still straight forward. we have defined shaping in MCQ style, then impliemented that into map-class. lastly, this map-class was configured inside the interface-dlci.
Class Based Generic Traffic Shaping
This is the last method out of the four methods that can be used for FRTS. It is similar to the legacy GTS. In this, you have the advantage to match the class based of frame-relay dlci. Lets see an example and that should show us the details.
match fr-dlci 123
shape average 256000
service-policy output SHAPE_123
One of the main issues of this method is that adaptive shaping can’t be used, nor voice-adaptive fragmentation.
all of the four methods have their advantage and disadvantage to them. from the simplest, to more complicated ones. The situations/requirment will be the deciding factor on which method use for FRTS.