<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font face="Tahoma">I've, generally, always been wary about these
"satellite" systems since Cisco introduced them with the ASR9000v
back in 2012.<br>
<br>
My whole thing is it being a closed system that requires the same
vendor hardware from start to finish. Back then, wiring things up
redundantly where all ports are in action was not possible, not
sure where things stand now but I guess there are solutions to
that.<br>
<br>
Ultimately, I didn't want to be in a position where I am no longer
satisfied with the solution, but my only recourse is to either
lose the investment or continue with the same vendor just to save
face.<br>
<br>
Recently, we had to vote with our feet as Juniper behaved badly on
their EX4550's and EX4600's. So we are now switching to Arista,
including getting rid of the old gear as it can't scale anymore.
If we had gone this satellite route, we'd have fewer options to
maneuver.<br>
<br>
The vendors love to push these systems because they say it will
simplify your life - and in essence, it probably will - but this
is a proper lock-in of note, and no vendor hates that.<br>
<br>
Mark.<br>
</font><br>
<div class="moz-cite-prefix">On 17/Dec/18 20:26, Matt Erculiani
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHk8tanADrw7gLgD+FxgDzJrJmeZzmP4aw6dv=1_RwDbtB8jMQ@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Fusion has made a lot more sense since Juniper changed the
licensing model from every switch AND the MX to just the MX.</div>
<div><br>
</div>
We've deployed it in some of our sites. It is very cool from a
forwarding plane perspective, but from a control plane
standpoint it's very...meh. For example, you can't get SNMP oids
for light levels or even read them right from the CLI. You have
to log into the satellite switch like you would log into an FPC
just to get light levels. That's probably the dumbest thing
we've dealt with though. I've also heard you can have them do
local L2 forwarding, which can be nice for latency and
conserving uplink bandwidth, but we don't do any L2 that way so
I wouldn't know the implications. From what we can tell though,
it does give you Trio L3 performance and features with a MUCH
cheaper port cost which is exactly what we were looking for, the
extended reach of the chassis was just a fantastic bonus.
<div><br>
</div>
<div>We also REALLY like that we can have one pair of MX dists
for a whole data center with hundreds of thousands of square
feet of raised floor and deploy QFX5100 or EX4300 switches in
every pod and haul back over just a few pairs of fiber. Saves
a lot of time because all that's required to turn up a new
connection is a cross connect in the pod. It also allows us to
offer copper ports very far away from the MX device, which
would normally require media converters.</div>
<div><br>
</div>
<div>We've wanted to experiment with doing this over dark fiber
in the metro as well, but we want to feel out any kinks
locally before we add additional failure modes.</div>
<div><br>
</div>
<div>Very interested in hearing about other's experiences with
Fusion, good, bad, and ugly.<br>
<div>
<div><br>
</div>
<div>-Matt</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Mon, Dec 17, 2018 at 12:08 PM Mehmet Akcin
<<a href="mailto:mehmet@akcin.net" moz-do-not-send="true">mehmet@akcin.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto">Hey there</div>
<div dir="auto"><br>
</div>
<div dir="auto">Any ISP using Juniper Fusion Provider Edge? </div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div><a
href="https://www.juniper.net/documentation/en_US/junos/information-products/pathway-pages/junos-fusion/junos-fusion.html"
target="_blank" moz-do-not-send="true">https://www.juniper.net/documentation/en_US/junos/information-products/pathway-pages/junos-fusion/junos-fusion.html</a></div>
<br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">I am trying to chat with an engineer besides
Juniper engineers to understand how buggy (or not) this is
to go on production for a medium size ISP.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Any feedback good/bad appreciated. </div>
-- <br>
<div dir="ltr"
class="gmail-m_-3463922157267493963gmail_signature">Mehmet<br>
+1-424-298-1903</div>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>