1841
From: Chris Evans [mailto:[email protected]] Sent: donderdag 3 februari 2011 20:03 To: Rens Cc: Pshem Kowalczyk; [email protected] Subject: Re: RE: [c-nsp] rate-limit 2 subinterfaces with shared bandwidth What platform is this? It might limit what you can do. High level you could do an egress service policy using h-qos policy matching source interface or apply ingress policies to your ingress interfaces matching the traffic to a qos-group.. Hth If you need an example let me know.. On Feb 3, 2011 1:26 PM, "Rens" <[email protected]> wrote: > Maybe I didn't explain myself very well but, here is what I want to do: > > > > Fa0/0 = WAN at 10 Mbps > > > > Fa0/1.100 & Fa0/1.101 currently rate-limited each at 8 Mbps > > > > rate-limit input 8192000 1536000 2048000 conform-action transmit > exceed-action drop > > rate-limit output 8192000 1536000 2048000 conform-action transmit > exceed-action drop > > > > But Fa0/1.100 & Fa0/1.101 should never go over 8 Mbps together so they won't > saturate my 10 Mbps WAN and always have 2 Mbps left > > > > > > From: Chris Evans [mailto:[email protected]] > Sent: woensdag 2 februari 2011 23:01 > To: Pshem Kowalczyk > Cc: [email protected]; Rens > Subject: Re: [c-nsp] rate-limit 2 subinterfaces with shared bandwidth > > > > This is commonly know has h-qos. Not all platforms support it However.. > > On Feb 2, 2011 4:59 PM, "Pshem Kowalczyk" <[email protected]> wrote: >> Hi, >> >> On 3 February 2011 05:45, Rens <[email protected]> wrote: >>> Hi, >>> I have 2 subinterfaces (Fa0/1.100 & Fa0/1.200) >>> Here are the things I would like: >>> 1) rate limit both to 8 Mbps >>> 2) never use over 8 Mbps together >>> 3) the first subinterface should always have 4 Mbps needed >>> Is this possible? >> >> Depending on your hardware/software you might be able to create a >> parent policy attached to the physical interface (Fa0/1) that >> classifies traffic based on vlan id (match vlan). Another option to >> try (only in inbound direction) is to match on interface (match >> input-interface). You might also try attaching one policy to the >> physical interface and another to the subinterfaces. >> >> kind regards >> Pshem >> >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
