[j-nsp] Difference in "MX204" and "MX204-HW-BASE"?

Wed Jan 10 17:32:05 EST 2024

Goodnight

As far as I saw, the MX480 and MPC7 are not in EOL.

However, even if it is, and the customer has an active COR or ND type contract, the customer has the right to install recent versions of JUNOS (obviously as long as they are supported by the platform), such as 22.

If 22 complains to the customer about license, the ideal would be to have a way to generate this HASH by the juniper license portal.

Otherwise, every time a commit is made, a WARNING comes and that is very annoying.

The installed base of MX480 and MPC7 with active support is still very high in the world.

At.te

Giuliano

From: Catalin Dominte <catalin.dominte at nocsult.net>
Sent: Wednesday, January 10, 2024 7:26 PM
To: Giuliano C. Medalha <giuliano at wztech.com.br>; Gert Doering <gert at greenie.muc.de>; Richard McGovern <rmcgovern at juniper.net>
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] Difference in "MX204" and "MX204-HW-BASE"?

Good Evening,

>>> For example. If you bought an MX480/MPC7 ago with -IR and -R ... the JUNOS 22 will ask you to install the hash of a license to >>>enforce the table's software (bgp, gre, etc). However, we still haven't figured out how to generate an old MX480 or MX204 license >>> for the new standard that JUNIPER is requiring in the JUNOS 22...

>>> I think they forgot about that... somehow... and it will need to be resolved.

Unless they EOL the entire lot and therefore the problem is gone. 😊. Computer says no 😊.

Catalin Dominte

From: juniper-nsp <juniper-nsp-bounces at puck.nether.net<mailto:juniper-nsp-bounces at puck.nether.net>> on behalf of Giuliano C. Medalha via juniper-nsp <juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net>>
Date: Wednesday, 10 January 2024 at 21:50
To: Gert Doering <gert at greenie.muc.de<mailto:gert at greenie.muc.de>>, Richard McGovern <rmcgovern at juniper.net<mailto:rmcgovern at juniper.net>>
Cc: juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net> <juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net>>
Subject: Re: [j-nsp] Difference in "MX204" and "MX204-HW-BASE"?
Good evening guys, how are you ?

If I can contribute a little.

Looking from a timeline standpoint... the MX204 passed:

- MX204 with -IR and R licenses ( which were perpetual )

- MX204-P-BASE ( Which was the transition box from -IR and -R to Flex License )

- MX204-HW-BASE ( Advanced and Premium Flex Licenses with 3 years or Perpetual )

Now on the JUNOS 22, Juniper starts requesting that the licenses hashes be installed in the box. However, from my point of view, the portal for generating router licenses is not yet prepared to take an -IR or -R license and generate it in the way that version 22 understands.

For example. If you bought an MX480/MPC7 ago with -IR and -R ... the JUNOS 22 will ask you to install the hash of a license to enforce the table's software (bgp, gre, etc). However, we still haven't figured out how to generate an old MX480 or MX204 license for the new standard that JUNIPER is requiring in the JUNOS 22...

I think they forgot about that... somehow... and it will need to be resolved.

At.te

Giuliano

-----Original Message-----
From: juniper-nsp <juniper-nsp-bounces at puck.nether.net<mailto:juniper-nsp-bounces at puck.nether.net>> On Behalf Of Gert Doering via juniper-nsp
Sent: Wednesday, January 10, 2024 6:46 PM
To: Richard McGovern <rmcgovern at juniper.net<mailto:rmcgovern at juniper.net>>
Cc: juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net>
Subject: Re: [j-nsp] Difference in "MX204" and "MX204-HW-BASE"?

Hi,

On Wed, Jan 10, 2024 at 09:41:41PM +0000, Richard McGovern via juniper-nsp wrote:
> Now, unknown to me (they don?t tell SEs any of this info either) there
> could have been ?hard? enforcement added in some newer SW release ? RN
> should point this out (stop laughing please!!!). Juniper internal have
> discussed implementing ?hard? enforcement over the years, and with
> potential change in product management (just happens) that view may
> change. Can?t tell you yah or nah on hard enforcement.

If you do not have enough magenta coloured ink, no BGP for you...

gert
--
Gert Doering - Munich, Germany                             gert at greenie.muc.de<mailto:gert at greenie.muc.de>

IMPORTANTE:
As informações deste e-mail e o conteúdo dos eventuais documentos anexos são confidenciais e para conhecimento exclusivo do destinatário. Se o leitor desta mensagem não for o seu destinatário, fica desde já notificado de que não poderá divulgar, distribuir ou, sob qualquer forma, dar conhecimento a terceiros das informações e do conteúdo dos documentos anexos. Neste caso, favor comunicar imediatamente o remetente, respondendo este e-mail ou telefonando ao mesmo, e em seguida apague-o.

CONFIDENTIALITY NOTICE:
The information transmitted in this email message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any review, transmission, dissemination or other use of this information is prohibited. If you have received this communication in error, please notify the sender immediately and delete the material from any computer, including any copies.
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net<mailto:juniper-nsp at puck.nether.net>
https://puck.nether.net/mailman/listinfo/juniper-nsp

IMPORTANTE:
As informações deste e-mail e o conteúdo dos eventuais documentos anexos são confidenciais e para conhecimento exclusivo do destinatário. Se o leitor desta mensagem não for o seu destinatário, fica desde já notificado de que não poderá divulgar, distribuir ou, sob qualquer forma, dar conhecimento a terceiros das informações e do conteúdo dos documentos anexos. Neste caso, favor comunicar imediatamente o remetente, respondendo este e-mail ou telefonando ao mesmo, e em seguida apague-o.

CONFIDENTIALITY NOTICE:
The information transmitted in this email message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any review, transmission, dissemination or other use of this information is prohibited. If you have received this communication in error, please notify the sender immediately and delete the material from any computer, including any copies.