Hello,
The FC in JUNOS is the same as qos-group in CSCO IOS - invisible
internal-only field which travels along with packet content across the
switch, but is never inserted in the actual packet. The FC has
significance for choosing output scheduling, RED drop, marking.
Of course there are
Alexander Arseniev wrote:
Hello,
The FC in JUNOS is the same as qos-group in CSCO IOS - invisible
internal-only field which travels along with packet content across the
switch, but is never inserted in the actual packet. The FC has
significance for choosing output scheduling, RED drop,
On (2015-06-25 12:59 +0200), Mark Tinka wrote:
Hey Mark,
For example, a lack of H-QoS on the MX80 or MX104 is not a show-stopper
for us if we are using it as a peering/border router. As an edge router
MX80 and MX104 fully support HQoS. Only limitation is that QX can only be used
for MIC
You meant: In MX80/104, where fabric should sit, you have 4 integrated 10GE
ports.
25 june 2015 @ 13:10, Saku Ytti s...@ytti.fi wrote :
Only difference is, that MPC 'wastes' 50% of capacity for fabric, and
MX104/MX80 spend this capacity for additional ports. (In MX80 where fabric
should
On 25/Jun/15 09:20, Alexander Arseniev wrote:
Hello,
The FC in JUNOS is the same as qos-group in CSCO IOS - invisible
internal-only field which travels along with packet content across the
switch, but is never inserted in the actual packet. The FC has
significance for choosing output
On 24 June 2015 at 21:05, Saku Ytti s...@ytti.fi wrote:
On 24 June 2015 at 22:29, Dan Peachey d...@illusionnetworks.com wrote:
Hey,
I thought the weights were determined by the %? The weights are then used
to schedule the queues appropriately. Even if the queues are in excess,
they
On 25/Jun/15 13:10, Saku Ytti wrote:
MX80 and MX104 fully support HQoS. Only limitation is that QX can only be used
for MIC ports, so you cannot do per-VLAN subrate services on chassis ports.
Sorry I wasn't clear - I meant this as an example, not literally...
Mark.
On 24/Jun/15 15:58, Phil Rosenthal wrote:
Obviously this list came from someone with a biased viewpoint of
nothing but problems with Juniper -- A Competitor. Consider that there
are also positives. For example, In Software, most people here would
rank JunOS Cisco IOS Brocade Arista
On (2015-06-25 13:14 +0200), Olivier Benghozi wrote:
Hey Olivier,
You meant: In MX80/104, where fabric should sit, you have 4 integrated 10GE
ports.
This is common misconception. People think the chassis ports are magical,
because they don't support QX QoS. But the chassis ports are actually
On (2015-06-25 13:57 +), Jackson, William wrote:
Hey Willliam,
mtu 2000;
encapsulation flexible-ethernet-services;
unit 1750 {
encapsulation vlan-ccc;
vlan-id 1750;
}
}
Add output vlan swap above.
--
++ytti
Hi Dan,
Seems odd to me that this needs to be done. Documentation I've read appears
to suggest that in PIR mode (no guaranteed-rate set) the per-queue
guarantee/transmit rate is calculated from the shaper rate and when a queue
exceeds it's guaranteed rate it is in excess, but this doesn't
On 25 June 2015 at 15:48, Marcin Wojcik mail.network.b...@gmail.com wrote:
Hi Dan,
Seems odd to me that this needs to be done. Documentation I've read
appears
to suggest that in PIR mode (no guaranteed-rate set) the per-queue
guarantee/transmit rate is calculated from the shaper rate and
Hi Saku,
Well, it's what I can read in Juniper MX Series, O'Reilly, by Harry Reynolds
Douglas Richard Hanks Jr.
Chapter 1, section MX80: in lieu of a switch fabric, each MX80 comes with four
fixed 10GE ports.
Olivier
25 juin 2015 @ 15:35, Saku Ytti s...@ytti.fi wrote :
On (2015-06-25
That comment does not directly state it's in fabric side, the
implication can be made, but it's not true. There is no external PHY,
it's exactly like 4x10GE MIC, hence it must connect on WAN side.
On 25 June 2015 at 19:07, Olivier Benghozi olivier.bengh...@wifirst.fr wrote:
Hi Saku,
Well,
Alexander,
There is one thing (two, actually :-) I cannot understand, please bear
with me. Does your fixed port classifier change the way frames are
processed in the switch (queue assignment etc) or is this
classification purely a marker?
After you assign a forwarding-class with the first
15 matches
Mail list logo
