Re: [j-nsp] JUNIPER POLICER and CoS Shaping Rate
On 04.10.2012 14:30, Duane Grant wrote: network-services all-ethernet; Btw, it's unsupported thing. There are ways to do it per IFL, but I don't have an example handy. Last time i checked build-in ports of MX=80 did not support per unit scheduling. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] JUNIPER POLICER and CoS Shaping Rate
On 10/8/12 4:02 AM, Tima Maryin wrote: On 04.10.2012 14:30, Duane Grant wrote: network-services all-ethernet; Btw, it's unsupported thing. There are ways to do it per IFL, but I don't have an example handy. Last time i checked build-in ports of MX=80 did not support per unit scheduling. That is correct, xe-0/0/0 through xe-0/0/3 are port mode only. It is the MIC interfaces that have per-unit shaping. -- Christopher E. Brown chris.br...@acsalaska.net desk (907) 550-8393 cell (907) 632-8492 IP Engineer - ACS ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] JUNIPER POLICER and CoS Shaping Rate
Hi, MPC/MIC interfaces take all Layer 1 and Layer 2 overhead bytes into account when shaping. egress-shaping-overhead configuartion is an option - you can add/subtract from [-63, +128] bytes. http://www.juniper.net/techpubs/en_US/junos10.2/information-products/topic-collections/config-guide-cos/topic-43439.html Best Regards, Krasi On Thu, Oct 4, 2012 at 5:54 AM, GIULIANO (WZTECH) giuli...@wztech.com.brwrote: People, Some topics where questioned today about how to limit traffic for vlan subscribers using MX5 routers. The main question is related to system architecture related to the main gear (internal machine) to control and limiting packets. Using policers (input or output) or shaping-rate we have quite the same result: miscalculating or error. If we create a rule like the following: set class-of-service interfaces ge-0/0/1 unit 530 shaping-rate 20m The output traffic rates 19.2~ Mbps only (using MRTG and SNMP statistics and graphics). We ever needs to allocate more bandwidth for the subscriber like. set class-of-service interfaces ge-0/0/1 unit 530 shaping-rate 22m To get the correct result ... Using policers generate almost the same result for output traffic. Is this because of system architecture or this is a graphic's mistake ? The burst size limit influence this result ? It must be calculated using what kind of parameter ? For example (same physical interface, same MTU, etc): Interface ge-0/0/0 unit 10 - VLAN 10 - 30 Mbps What is the correct burst ? Interface ge-0/0/0 unit 20 - VLAN 20 - 50 Mbps What is the correct burst ? Interface ge-0/0/0 unit 30 - VLAN 30 - 150 Mbps What is the correct burst ? Interface ge-0/0/0 unit 30 - VLAN 30 - 4 Mbps What is the correct burst ? Does anyone has solved this problems ? Is it possible to get a correct parameter and points to a correct limit for the contracted bandwidth ? Thanks a lot, Giuliano __**_ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/**mailman/listinfo/juniper-nsphttps://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] JUNIPER POLICER and CoS Shaping Rate
On (2012-10-03 23:54 -0300), GIULIANO (WZTECH) wrote: set class-of-service interfaces ge-0/0/1 unit 530 shaping-rate 20m The output traffic rates 19.2~ Mbps only (using MRTG and SNMP statistics and graphics). What do you see on fully congested 100M ethernet, no policers/shapers on MRTG/SNMP? Hint, you don't see 100M. Why? Because we can't count. I've not yet seen system which shows actual wire use in graph, which is only thing we network engineers care about. If your line is 20M and you're sending 1500B (best case). You'll see 19.51Mbps L2 speed (what you are calculating right now) or 18.99 L3 speed. That is without VLAN header. Add one VLAN header and those numbers drop to 19.46Mbps L2 and 18.94Mbps L3. QinQ, MPLS etc, it'll all decrease speed (L2) you're measuring. I know that Juniper MX shaper does the right thing and calculates L1 rate. As does say Cisco ES20. But Cisco ES+ shaper calculates L2 speed, which is extremely bad default, luckily it is configurable. Why is shaper measuring L2 speed bad? Router - Distribution_L2 -100M- Customer If you shape router VLAN to 100M and then prioritize VoIP on it, if router is calculating L2 speed, you'll end up dropping VoIP packets in the physical pipe, which certainly is calculating L1 speed. If you use 'traffic-control-profile', you can manually set overhead accounting, which you need if far-end overhead is different than local interface. -- ++ytti ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] JUNIPER POLICER and CoS Shaping Rate
HI,
I suspect that much of your problem is that the MX boxes by default count
L1 stuff like IFG-preamble (20 bytes in all).
You can adjust the counting overhead for the PIC like so:
grant@mx80a show configuration chassis
fpc 0 {
pic 0 {
traffic-manager {
egress-shaping-overhead -20;
}
}
pic 1 {
traffic-manager {
egress-shaping-overhead -20;
}
}
}
network-services all-ethernet;
There are ways to do it per IFL, but I don't have an example handy.
Hopefully Harry or Doug will chime in.
--Duane
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] JUNIPER POLICER and CoS Shaping Rate
People, Some topics where questioned today about how to limit traffic for vlan subscribers using MX5 routers. The main question is related to system architecture related to the main gear (internal machine) to control and limiting packets. Using policers (input or output) or shaping-rate we have quite the same result: miscalculating or error. If we create a rule like the following: set class-of-service interfaces ge-0/0/1 unit 530 shaping-rate 20m The output traffic rates 19.2~ Mbps only (using MRTG and SNMP statistics and graphics). We ever needs to allocate more bandwidth for the subscriber like. set class-of-service interfaces ge-0/0/1 unit 530 shaping-rate 22m To get the correct result ... Using policers generate almost the same result for output traffic. Is this because of system architecture or this is a graphic's mistake ? The burst size limit influence this result ? It must be calculated using what kind of parameter ? For example (same physical interface, same MTU, etc): Interface ge-0/0/0 unit 10 - VLAN 10 - 30 Mbps What is the correct burst ? Interface ge-0/0/0 unit 20 - VLAN 20 - 50 Mbps What is the correct burst ? Interface ge-0/0/0 unit 30 - VLAN 30 - 150 Mbps What is the correct burst ? Interface ge-0/0/0 unit 30 - VLAN 30 - 4 Mbps What is the correct burst ? Does anyone has solved this problems ? Is it possible to get a correct parameter and points to a correct limit for the contracted bandwidth ? Thanks a lot, Giuliano ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] JUNIPER POLICER and CoS Shaping Rate
The math for burst rate is a little odd. However it seems to average at around 10% of the desired rate. The burstiness (for lack of a better word) provides for a better user experience rather than a hard policer. Will O'Brien On Oct 3, 2012, at 9:55 PM, GIULIANO (WZTECH) giuli...@wztech.com.br wrote: People, Some topics where questioned today about how to limit traffic for vlan subscribers using MX5 routers. The main question is related to system architecture related to the main gear (internal machine) to control and limiting packets. Using policers (input or output) or shaping-rate we have quite the same result: miscalculating or error. If we create a rule like the following: set class-of-service interfaces ge-0/0/1 unit 530 shaping-rate 20m The output traffic rates 19.2~ Mbps only (using MRTG and SNMP statistics and graphics). We ever needs to allocate more bandwidth for the subscriber like. set class-of-service interfaces ge-0/0/1 unit 530 shaping-rate 22m To get the correct result ... Using policers generate almost the same result for output traffic. Is this because of system architecture or this is a graphic's mistake ? The burst size limit influence this result ? It must be calculated using what kind of parameter ? For example (same physical interface, same MTU, etc): Interface ge-0/0/0 unit 10 - VLAN 10 - 30 Mbps What is the correct burst ? Interface ge-0/0/0 unit 20 - VLAN 20 - 50 Mbps What is the correct burst ? Interface ge-0/0/0 unit 30 - VLAN 30 - 150 Mbps What is the correct burst ? Interface ge-0/0/0 unit 30 - VLAN 30 - 4 Mbps What is the correct burst ? Does anyone has solved this problems ? Is it possible to get a correct parameter and points to a correct limit for the contracted bandwidth ? Thanks a lot, Giuliano ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
