>From: Dennis Reiter <denny at reiters.org> > >Several of our locations are shaping (or trying to) customer traffic >through Radius using these attributes: > > Ascend-Dsl-CIR-Recv-Limit = 128 , > Ascend-Dsl-CIR-Xmit-Limit = 1168 > >Now, the way these are set up, it leads me to believe that all >the limiting is being done on the TNT, but the person who instigated >this insists that the DSL pipeline is what is doing the limiting. The attribute takes affect on the device using the profile, in this case the TNT. In the case of Ascend DSL gear, these settings can be set on either or both ends, and they needn't even agree--lowest setting in either direction (presumably) wins. So, if you use this attribute on the TNT it will take effect (assuming it works, which I don't know). And, if the DSL Pipe makes it's own settings it will use them. If the Pipe tries to exceed the CIR set at the TNT the TNT should throttle it back--wouldn't be much of a CIR otherwise, would it? Bear in mind, from the docs: Dependencies: The system activates configurable receive data-rate limits only for connections that use CAP-RADSL, SDSL, and unchannelized DS3 cards. If you specify a value for a connection that does not use these cards, the system ignores the settings. -- Peter Lalor ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com Archives: http://www.nexial.com/mailinglists/