Unclear what you're trying to accomplish. When shaping for frame-relay, it makes sense to shape all traffic but it also sometimes makes sense to prioritize traffic within the shaper, such as routing protocol packets. Further, in theory, it also makes sense to insure critical packets, again such as routing protocol packets, don't become DE marked.
In practice, I would suggest first shaping all traffic at either end-to-end minimum port speed or at CIR; either with FQ. Next, prioritize traffic as you desire within the shaped rate. Beyond that it can get rather complex and, I believe, may require cooperation of the frame-relay vendor and/or "very smart" network equipement.
Thanks for your reply. well all i am trying to do is shape all traffic which includes mpls, and IP traffic . but i want to exclude my routing protocol traffic from this shaping. my routing protocol is RIP.
Yes it's clear what you want to do, still unclear why. Your routing protocol traffic, e.g. RIP, within the shaper, can be prioritized, or have guaranteed bandwidth, vs. other traffic. On the frame-relay's physical interface, you just shape non-RIP traffic, but then you need to insure doesn't use bandwidth needed by RIP.
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...