Re: [j-nsp] Subrate speed on GigE requiring CoS / Policer configuration
After more research I found that I need to do traffic shaping and hierarchical CoS.. The unfortunate part is that with the MX you need the enhanced queuing cards and for the M series you need at least an IQ2 pic to do these features.. All fine and dandy except for the cost, the Juniper solution costs about 4 to 5x as much as compared to using an ASR1K solution. We do not have the J series as a buyable platform currently and I'm not going to take the effort to research, test and certify it when I have other choices already.. I have to sit back and think that Juniper is getting their A$$es handed to them right due to the cost of their products. On Wed, Oct 6, 2010 at 12:12 AM, Chris Evans wrote: > I'm still researching hardware selection right now but it looks like I need > at minimum iq2 pics to support hierarchical cos. I think those are rather > expensive which would push me to the Cisco asr1k series.. bums me out I have > to get special high end hardware on juniper boxes to support this featur > when almost every Cisco platform supports this on base hardware. > > It looks like I would need the enhanced queueing cards for our headend mx > devices. > > Guess I'll be looking at alternative platforms or trying to come up with > another answer. > On Oct 5, 2010 11:44 PM, "Dale Shaw" > > > wrote: > ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Subrate speed on GigE requiring CoS / Policer configuration
I'm still researching hardware selection right now but it looks like I need at minimum iq2 pics to support hierarchical cos. I think those are rather expensive which would push me to the Cisco asr1k series.. bums me out I have to get special high end hardware on juniper boxes to support this featur when almost every Cisco platform supports this on base hardware. It looks like I would need the enhanced queueing cards for our headend mx devices. Guess I'll be looking at alternative platforms or trying to come up with another answer. On Oct 5, 2010 11:44 PM, "Dale Shaw" > wrote: ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Subrate speed on GigE requiring CoS / Policer configuration
Hi Chris, On Wed, Oct 6, 2010 at 1:44 PM, Chris Evans wrote: > As this is a lab we want to limit the bandwidth that comes out of > the LAB to 15megabits, but using GigE for the physical connection on an m7i. I have no hands-on experience with M-series but is there any reason you can't use traffic shaping to limit the transmit rate? ('set interfaces ... shaping-rate 15m') It can't be tuned as much as the equivalent function in IOS but unless you're trying to interoperate with a particularly aggressive intermediate device, it should do the job. We use it instead of egress policers on J and SRX, and we use it in conjunction with schedulers, including a priority queue for voice. My understanding is that it (the shaper) should introduce back pressure/congestion when the interface reaches the specified transmit rate. Cheers, Dale ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Subrate speed on GigE requiring CoS / Policer configuration
Looks like Hierarchical CoS is what I'm looking for. http://www.juniper.net/techpubs/software/junos/junos91/swconfig-cos/introduction-to-hierarchical-schedulers.html#id-sec-sched-ex On Tue, Oct 5, 2010 at 10:44 PM, Chris Evans wrote: > I'm struggling to come up with a solution for my requirement.. Essentially > we are building a lab using GRE to link two sites over our enterprise > network. As this is a lab we want to limit the bandwidth that comes out of > the LAB to 15megabits, but using GigE for the physical connection on an m7i. > Essentially my first thought was implement a policer on the egress interface > limiting the maximum aggregate traffic to 15Mb, then implement a scheduler > on the GRE interface. I need to prioritize certain traffic leaving the lab > so I also want to use a scheduler to make sure that the voice traffic has > priority and has a 2Mb of traffic for example. > > I want to limit my EF traffic to 2Mb, AF to 2Mb, NC to 500Kb and best > effort to 10.5Mb under signs of congestion within that 15Mb CIR. > > 1st issue.. It appears that you cannot implement schedulers on GRE > interfaces, as this isn't possible the next thought was to implement a > scheduler on the egress GigE using the copy TOS to header feature on the GRE > interface. Is certain hardware required to be able to do this? EIQ2 pic for > example? > > 2nd issue..As I'm trying to do a CIR of 15mb, I don't believe a scheduler > will work as the interface really is GigE there are no signs of congestion, > so the scheduler doesn't kick in. I've tried the extra parameters under the > transmit rate to use exact, rate-limit, etc.. nothing do what I expect it to > do. I'm not sure if the scheduler limiters are always active or only in > signs of congestion. > > > I've made it work by breaking out and creating individual policers per > forwarding class, however this isn't as sexy as I have to hard limit each > forwarding class within the aggregate 15Mb CIR. Thus it denies me the > possibility of the bandwidth being dynamic across all 4 forwarding classes. > > Is this configuration even possible with Juniper devices? > > Thanks > > Chris > ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] Subrate speed on GigE requiring CoS / Policer configuration
I'm struggling to come up with a solution for my requirement.. Essentially we are building a lab using GRE to link two sites over our enterprise network. As this is a lab we want to limit the bandwidth that comes out of the LAB to 15megabits, but using GigE for the physical connection on an m7i. Essentially my first thought was implement a policer on the egress interface limiting the maximum aggregate traffic to 15Mb, then implement a scheduler on the GRE interface. I need to prioritize certain traffic leaving the lab so I also want to use a scheduler to make sure that the voice traffic has priority and has a 2Mb of traffic for example. I want to limit my EF traffic to 2Mb, AF to 2Mb, NC to 500Kb and best effort to 10.5Mb under signs of congestion within that 15Mb CIR. 1st issue.. It appears that you cannot implement schedulers on GRE interfaces, as this isn't possible the next thought was to implement a scheduler on the egress GigE using the copy TOS to header feature on the GRE interface. Is certain hardware required to be able to do this? EIQ2 pic for example? 2nd issue..As I'm trying to do a CIR of 15mb, I don't believe a scheduler will work as the interface really is GigE there are no signs of congestion, so the scheduler doesn't kick in. I've tried the extra parameters under the transmit rate to use exact, rate-limit, etc.. nothing do what I expect it to do. I'm not sure if the scheduler limiters are always active or only in signs of congestion. I've made it work by breaking out and creating individual policers per forwarding class, however this isn't as sexy as I have to hard limit each forwarding class within the aggregate 15Mb CIR. Thus it denies me the possibility of the bandwidth being dynamic across all 4 forwarding classes. Is this configuration even possible with Juniper devices? Thanks Chris ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp