What you do there is to specify smtp traffic to belong to the class SMTP. Then you define a policy that does shape the traffic in this class to 25% of the interface bandwidth and apply it to the DLCI 100 with the help of a FR class.
You can monitor the outcome by "show policy interface Serial0/0.100". Adjust the config to your interface naming, DLCI number and bandwidth.
Martin - tried this and had some difficulties. Defined the policy fine but had an issue mapping it to an interface. Also, from the posts below, I also need to understand the frame-relay cir 64000 line in the config. I am assuming that this is total available bandwidth on the circuit....in this case 64K ? For a 3T bundle we would be talking roughly 4600K?
Perhaps if I posted my config it would help. Appreciate your input.
The problem I encountered was with the sub-interface. I'm not quite sure what the line class DLCIshape accomplishes and what command was issued that resulted in that line being added to the sub-interface. Everything else was pretty straightforward.
I also had a question regarding the bandwidth parameter which I see now is total bandwidth of the bundle expressed in bytes..correct?
in addition to Martin´s post, and if you want to read up a little more on Frame Relay Traffic Shaping, you might want to have a look at the link below, which is (I think) a really good and fairly easy to understand explanation of the technology:
Just a quick question. Wouldn't configuring a CIR of 64k in the map-class effectively shape SMTP to 25% of that (resulting in shaping SMTP @ 16k) ? When configured this way, I believe it will use the configured CIR as opposed to the total bandwidth available on the MFR bundle. Could be wrong.
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...