MPLS is now supported on IRB on QFX5100:
https://www.juniper.net/documentation/en_US/junos/topics/reference/general/mpls-limitations-qfx-series.html#jd0e57
On Fri, Oct 27, 2017 at 3:50 PM, Andrey Kostin wrote:
> Chris Wopat писал 25.10.2017 13:00:
>
>> On 10/24/2017 05:30
Chris Wopat писал 25.10.2017 13:00:
On 10/24/2017 05:30 PM, Vincent Bernat wrote:
❦ 24 octobre 2017 14:29 -0400, Andrey Kostin :
Straight up saying "don't put public IPs on them" doesn't seem like
the best advice to me. You can certainly do this, we do and it's
fine.
Vincent Bernat писал 24.10.2017 18:30:
❦ 24 octobre 2017 14:29 -0400, Andrey Kostin :
QFX5100 are good as L2 devices for aggregation, we use them in
virtual-chassis. But be careful with planning any L3 services on
them. First, don't put public IPs on them because TCAM for
On 10/24/2017 05:30 PM, Vincent Bernat wrote:
❦ 24 octobre 2017 14:29 -0400, Andrey Kostin :
QFX5100 are good as L2 devices for aggregation, we use them in
virtual-chassis. But be careful with planning any L3 services on
them. First, don't put public IPs on them because
On Wed, Oct 25, 2017 at 8:49 AM, Aaron Gould wrote:
> I let someone else worry about dollars… but sounds like you have a point
>
> You can do mpls l2circuit (martini) in a qfx ? I was under the impression
> the qfx did no mpls at all.
>
>
Cc: mlfre...@mtu.edu; Karl Gerhard; Juniper List
Subject: Re: [j-nsp] Using a QFX5100 without QFabric?
How do you handle 10G port licensing on the 5048? That gets expensive quickly.
I've got about 75 qfx's deployed as PE devices right now because of the 5048
port licenses.
The major
❦ 24 octobre 2017 14:29 -0400, Andrey Kostin :
> QFX5100 are good as L2 devices for aggregation, we use them in
> virtual-chassis. But be careful with planning any L3 services on
> them. First, don't put public IPs on them because TCAM for filters is
> tiny and programmed in
Without ASCII art:
We have P(MX), a P(vMX), a PE1 (QFX5100), and PE2 (QFX5100),
all with ISIS, MPLS, RSVP/LDP, BGP underlay, cluster and multipath.
The (EVPN) broadcast is handled by the P's but once that
discovery is done, the traffic passes between the PE's without
Hi,
We have a stub vrf with Transit on them, the solution is a very
good set of filters on lo0 input.
-
Alain Hebertaheb...@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911
QFX5100 are good as L2 devices for aggregation, we use them in
virtual-chassis. But be careful with planning any L3 services on them.
First, don't put public IPs on them because TCAM for filters is tiny and
programmed in a tricky for understanding way. As a result everything
that doesn't fit
How do you handle 10G port licensing on the 5048? That gets expensive
quickly. I've got about 75 qfx's deployed as PE devices right now because
of the 5048 port licenses.
The major limitation of the qfx as a PE device is that it doesn't support
VPLS. It does however do EVPN over vxlan, which can
Not to change subject too much, but, In case you are wanting to extend your
mpls cloud (I'm assuming your MX core is mpls-enabled) further out into the
aggregation/access edge, you could go with the qfx-5100 cousin... acx5048.
I've been pretty pleased with them.
I've deployed 30 or 40 of these
Karl, we're also looking at QFX5100-48S switches for our aggregation. I
actually have one in place doing aggregation and routing and the only "big"
change I found is the DHCP forwarder config is not remotely similar to the
forwarding-options helpers bootp config we've been using to forward DHCP on
Hello
we're thinking about buying a few QFX5100 as they are incredibly cheap on the
refurbished market - sometimes even cheaper than a much older EX4550.
Are there any caveats when using the QFX5100-48S as a normal aggregation switch
without QFabric? We have a pretty basic setup of Access
14 matches
Mail list logo