[j-nsp] Going Juniper

[Alexandre Guimaraes]

Hello everyone!

Last notice that I have about Junos fusion, some features doesn’t work in to satellite ports, like ethernet ccc.

Did you guys that use, can confirm that, or all features are available?

att
Alexandre

Em 11 de abr de 2018, à(s) 08:11, Ola Thoresen <ola at nytt.no> escreveu:

> On 11. april 2018 12:51, Saku Ytti wrote:
> 
>> On 11 April 2018 at 13:43, Ola Thoresen <ola at nytt.no> wrote:
>> 
>> 
>>> We have recently started playing with MX204 and Junos Fusion, and that makes
>>> a really nice setup.
>>> With either EX4300 (for 1G) or QFX5100 (for 10G), you get a lot of ports and
>>> a great routing engine for a "decent" cost.
>> I have strong dislike to satellite solutions. I'd rather even run L2
>> backhaul than satellite. There tends to be all kind of catches and
>> esoteric differences between 'native' port and satellite port, and
>> those are not documented anywhere, probably not even known to vendor,
>> and you just stumble on them as you go. As well as you have to carry
>> the increased bug surface of the vendor's proprietary host<->satellite
>> code.
>> 
>> Granted at least JNPR offering allows you to run same device as pure
>> L2, with Cisco offering it is satellite-only box, cannot be used as
>> L2.
> 
> I know what you mean, but I must say that this time it seems like they have more or less managed to do it right.  They use pretty standard protocols for everything, it is just "packaged" so you don't need to think about it.
> 
> But as you say, you can easily use the exact same hardware in a regular L2 setup, the thing you gain from the satellite setup is central management of only the routers, which can be a time and management saver.
> 
> /Ola (T)
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp