On Tuesday 26 January 2010 07:15:59 pm Sean Clarke wrote:
> R Cards do QOS, but not per unit .. only per port.
>
> Firewalling per unit will also wor, i.e. policing
Yes, just as I thought... thanks for the clarification.
Cheers,
Mark.
signature.asc
Description: This is a digitally signed mes
On 1/26/10 12:06 PM, Mark Tinka wrote:
Really? The -R cards won't do QoS? I haven't tried the -R
cards, but was thinking of giving them a shot!
Documentation suggests they'll do QoS, but not as deep as
the -R-Q models.
Cheers,
Mark.
R Cards do QOS, but not per unit .. only per port.
Fire
On Tuesday 26 January 2010 05:32:24 pm Richard A Steenbergen
wrote:
> You don't need -Q cards to do per-subinterface policing,
> just cos AFAIK.
Really? The -R cards won't do QoS? I haven't tried the -R
cards, but was thinking of giving them a shot!
Documentation suggests they'll do QoS, but
On Tue, Jan 26, 2010 at 11:35:48AM +0300, Cyrill Malevanov wrote:
>
> On Jan 25, 2010, at 5:12 AM, David Coulson wrote:
>
> > I am trying to configure input rate limiting on an ae0 unit on a MX240
> > unning 9.4R2.9... Everything I have tried so far has had no effect on
> > interface input rate
On Jan 25, 2010, at 5:12 AM, David Coulson wrote:
> I am trying to configure input rate limiting on an ae0 unit on a MX240 unning
> 9.4R2.9... Everything I have tried so far has had no effect on interface
> input rates.
>
> * policier with firewall filter applied to interface
> * input-traffic
I am trying to configure input rate limiting on an ae0 unit on a MX240
unning 9.4R2.9... Everything I have tried so far has had no effect on
interface input rates.
* policier with firewall filter applied to interface
* input-traffic-control-profile with a shaping-rate on the
interface/unit wit
6 matches
Mail list logo
