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

[Michael Hare]

Richard just reports the news, and at risk of keeping this thread a live, I thought I'd give our real word experiences.

I've upgraded both newer "licensed based" mx204s and perpetual pre-sku-change mx204's to 22.4.  I can attest regardless I had no problems with BGP or anything else.  All of my chassis, licensed or not, claim to be missing licenses based on the output of 'show system license'.   For all of my chassis, there are/were  no chassis alarm indicating a problem, nor did I receive any syslogs indicating a missing license.

So calling the enforcement soft seems to be an understatement; I had to go out of my way to find out JunOS things I'm breaking the rules.  

We had purchased the activation codes for the licensed based mx204s that I sat on until 22.4, so I went through the Agile licensing portal hoops and applied a license to the ones that "I know" require a license per their new model

The whole process makes me wonder if I made a mistake and we're one step away from being locked out of our network.  Not a great experience.  I will probably follow Richard's advice and ask our SE what's supposed to happen "show system license" wise to my legacy mx204s.

-Michael

> -----Original Message-----
> From: juniper-nsp <juniper-nsp-bounces at puck.nether.net> On Behalf Of
> Richard McGovern via juniper-nsp
> Sent: Wednesday, January 10, 2024 4:03 PM
> To: EXT - giuliano at wztech.com.br <giuliano at wztech.com.br>; Gert Doering
> <gert at greenie.muc.de>
> Cc: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] Difference in "MX204" and "MX204-HW-BASE"?
> 
> Agree sort of. The SW should know if model was MX204 or MX204-P-BASE/
> MX204-HW-BASE. So it should know if need to enforce a license or not. The
> problem is that some MX204-P-BASE were sold as -IR or -R, etc. and some
> sold with Flex - Transition period.
> 
> There is no way for SW to know by which method a MX204-P-BASE was sold.
> So no way to know to enforce or not. That is one reason for "soft"
> enforcement. Customer (and Juniper Sales) can then determine which method
> was used, and get the customer a valid perpetual license at $0 so customer is
> good to go forever.
> 
> Now whether this approach is actually occurring, I don't know. I service my
> customer base like above on an as needed basis.
> 
> FYI only, Rich
> 
> Richard McGovern
> Sr Sales Engineer, Juniper Networks
> 978-618-3342
> 
> I'd rather be lucky than good, as I know I am not good
> I don't make the news, I just report it
> 
> 
> 
> 
> Juniper Business Use Only
> From: Giuliano C. Medalha <giuliano at wztech.com.br>
> Date: Wednesday, January 10, 2024 at 4:49 PM
> To: Gert Doering <gert at greenie.muc.de>, Richard McGovern
> <rmcgovern at juniper.net>
> Cc: juniper-nsp at puck.nether.net <juniper-nsp at puck.nether.net>
> Subject: RE: [j-nsp] Difference in "MX204" and "MX204-HW-BASE"?
> [External Email. Be cautious of content]
> 
> 
> 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> On Behalf Of Gert
> Doering via juniper-nsp
> Sent: Wednesday, January 10, 2024 6:46 PM
> To: Richard McGovern <rmcgovern at juniper.net>
> Cc: 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
> 
> WZTECH is registered trademark of WZTECH NETWORKS.
> Copyright © 2023 WZTECH NETWORKS. All Rights Reserved.
> 
> 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
> https://puck.nether.net/mailman/listinfo/juniper-nsp