MIR, CIR on dynamic queues in case of PPPoE

Did some one try to set different MIR CIR values using Radius in case of PPPoE? Both radius attributes such as “Mikrotik-Rate-Limit”, “Rate-Limit”, “WISPr-Bandwidth-Max-Up”, “WISPr-Bandwidth-Max-Down” and “Ascend-Data-Rate” always creates dynamic queue with same values on “limit-at=” and “max-limit=”.

Your great experience and advise will be highly appreciated.

http://wiki.mikrotik.com/wiki/Manual:RADIUS_Client

Mikrotik-Rate-Limit > - Datarate limitation for clients. > Format is: rx-rate[/tx-rate] [rx-burst-rate[/tx-burst-rate] [rx-burst-threshold[/tx-burst-threshold] [rx-burst-time[/tx-burst-time] [priority] [rx-rate-min[/tx-rate-min]]]] > from the point of view of the router (so “rx” is client upload, and “tx” is client download). All rates should be numbers with optional ‘k’ (1,000s) or ‘M’ (1,000,000s). If tx-rate is not specified, rx-rate is as tx-rate too. Same goes for tx-burst-rate and tx-burst-threshold and tx-burst-time. If both rx-burst-threshold and tx-burst-threshold are not specified (but burst-rate is specified), rx-rate and tx-rate is used as burst thresholds. If both rx-burst-time and tx-burst-time are not specified, 1s is used as default. Priority takes values 1..8, where 1 implies the highest priority, but 8 - the lowest. If rx-rate-min and tx-rate-min are not specified rx-rate and tx-rate values are used. The rx-rate-min and tx-rate-min values can not exceed rx-rate and tx-rate values.

Thanks Chupaka. But it doesn`t work. Actually my idea is to set total rate for PPPoE customers. As I know ROS has 2 option to complete this task.
First one is to set it on /queue tree. Mark packets first and then using this mark, add rule in queue tree. But if active customers more than 800, queue tree starts to add huge delays on customer traffic. Contacted to support and MT support agrees “currently HTB Global is slow on CCR, we have plans for improvements”.
Second option: Newer ROS has new feature that able to configure Parent queue in PPP profile section.

/ppp profile
add name=testing local-address=Pool1 remote-address=Pool2 parent-queue=Testing

Using this feature, dynamic simple queues creat under configured Parent queue. But actual traffic exceeds the max-limitation of this Parent queue. I think because dynamic queue creates with limit-at value. Limit-at is guaranteed rate. That`s the issue. For example:
Parent queue: Max-limit=10M/10M
Customer1: limit-at=5M/5M
Customer2: limit-at=5M/5M
Customer3: limit-at=5M/5M
Parent queue can not limit at 10Mbps. Parent queue passes over 15Mbps of traffic. I would like to find a way to create dynamic queue only with value “max-limit” without “limit-at” value.

if it’s documented - it should work. write to support@