> Saku Ytti > Sent: Sunday, April 12, 2020 9:44 AM > > On Sun, 12 Apr 2020 at 03:53, Mark Tinka <mark.ti...@seacom.mu> wrote: > > > On 11/Apr/20 08:04, Nick Schmalenberger via juniper-nsp wrote: > > > I had the same issue with first trying to export over fxp0, then > > > > We just export flows in-band. Just seems simpler, and has been > > reliable for close to 10 years. > > in-band is right, Trio can export the flow itself, you will kill your performance > if you do non-revenue port export. > > In my mind JNPR non-revenue ports have no use-case. They are dangerous > with no utility. Cisco is much better here, as they offer true OOB non- > revenue ports. JNPR non-revenue port is a convenient way to quickly break a > lot of your network at the same time, as they entirely fate-share the control- > plane. Cisco has non-revenue ports with their own isolated management- > plane, so state of your control-plane will not impact the management-plane > vice versa.
Hey, Can you expand on the above please? Say comparing RE/RSP management port on ASR9k and MX, adam _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
