RE: MQC equivalent FRTS policy

From: Nathan Richie <nathanr_at_boice.net>
Date: Sat, 3 Oct 2009 08:50:27 -0400

I would think you would need to create a tag based upon the EXP bit and apply it inbound on the MPLS interface. Then create your policing based upon the tag and apply it through a service-policy outbound on your FRTS. Remember for FRTS, you need to create a "map-class frame-relay" map.

This is just my thoughts. I have not tested it so I am not sure that it would work, so if I am incorrect, please let me know.

Regards,

Nathan Richie

-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of petdsouz_at_cisco.com
Sent: Saturday, October 03, 2009 12:58 AM
To: ccielab_at_groupstudy.com
Subject: MQC equivalent FRTS policy

I need some help with converting a MQC based policy to be configured over a FR
sub-interface. The MQC policy is as below.

!
ip access-list extended udp_voice
 permit udp any any range 16384 32767
!
!
!
class-map match-all match-voice
  match mpls experimental topmost 4
class-map match-all match-data
  match mpls experimental topmost 3
class-map match-all voice
  match access-group name udp_voice
!
policy-map core-qos
 class match-voice
    priority 640
 class match-data
    bandwidth 1000
policy-map from_BB2
 class voice
   police cir 640000
    conform-action set-mpls-exp-imposition-transmit 4
    exceed-action drop
 class class-default
   police cir 1000000
    conform-action set-mpls-exp-imposition-transmit 3
    exceed-action drop
!

Requirement:
1. Priority queue for voice 640Kbps
2. Rest - Guaranteed BW - 1Mbps

Not sure how this can be achieved using FRTS. I've tried the following.

a. When I tried applying the above policy directly over a FR DLCI
sub-interface, it threw back a CBWFQ support error.
b. I tried apply the policy under a map-class, comes up with a message. Invalid
Policy. class-default...

Platform : 7200
IOS : 12.0.25S

Blogs and organic groups at http://www.ccie.net
Received on Sat Oct 03 2009 - 08:50:27 ART

This archive was generated by hypermail 2.2.0 : Sun Nov 01 2009 - 07:50:59 ART