Thanks, Richard. Any particular reason why I would be better off using
12.3R12?
On Wed, Oct 16, 2019 at 5:53 PM Richard McGovern
wrote:
> No. For legacy EX switches, for which EX4500/EX4550 fall into, 15.1 is
> last release. At the same time, I think you might have best results using
>
--- Begin Message ---
No. For legacy EX switches, for which EX4500/EX4550 fall into, 15.1 is last
release. At the same time, I think you might have best results using
12.3R12-S[latest] instead. Both 12.3 and 15.1 will be maintained for life of
legacy EX switches.
HTH, Rich
Richard McGovern
--- Begin Message ---
> On Mar 5, 2019, at 02:04, Job Snijders wrote:
>
> On Thu, Feb 28, 2019 at 04:17:19PM +0300, Alexandre Snarskii wrote:
>> Somewhat stupid question: while experimenting with rpki, I found that
>> while rfc8097 declares origin validation state as extended community
>>
--- Begin Message ---
Marcin,
> On Oct 9, 2019, at 07:26, Marcin Głuc wrote:
> I was wondering is there a way to export family flow routes (from
> inetflow.0) to non flowspec BGP speaker?
> For example tag Flowspec route with community and advertise this route with
> different community to
Response to old thread and referencing my new thread…
“[j-nsp] telemetry analytics - mx960 - npu packet rate concerns”
My JTI/OpenNTI systems seems to be continuing to run nicely. I use it when I
really need to know some details.
In the new thread I mentioned above, I was curious
Is it possible (and recommended) to run anything newer than 15.1 on EX4550
(which is what the JTAC-recommended version currently is).
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
6 matches
Mail list logo