<html><body><div id="zimbraEditorContainer" style="font-family: arial,helvetica,sans-serif; font-size: 10pt; color: #000000" class="6"><div>Totally agree.</div><div><br></div><div data-marker="__SIG_PRE__">Perhaps another Elon Musk to streamline and scale chip manufacturing.<br><br>Regards <br>Paschal Masha | Engineering <br>Skype ID: paschal.masha <br></div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"Mark Tinka" <mark@tinka.africa><br><b>To: </b>"nanog" <nanog@nanog.org><br><b>Sent: </b>Tuesday, June 14, 2022 4:41:14 PM<br><b>Subject: </b>DMARC ViolationDKIM ViolationSerious Juniper Hardware EoL Announcements<br></div><div><br></div><div data-marker="__QUOTED_TEXT__"><font face="Tahoma">So Juniper have gone ahead and announced the EoL
of some key devices that, IMHO, are nowhere near past their prime:<br>
<br>
- MX204 (to be replaced by the MX304)<br>
- MX10003 (to be replaced by the MX304)<br>
- PTX1000 (to be replaced by the PTX10001)<br>
<br>
Re: the PTX1000, I know it is a component issue that Juniper have
mentioned is the reason for EoL'ing this. We bought a fair bit in
the past 2 years, and technically, there is nothing wrong with
them. We are going ahead with the PTX10001 as a replacement,
because it works technically and otherwise.<br>
<br>
Having both the MX10003 and MX304 in the same portfolio did not
make any sense to me, and I did challenge Juniper on this over the
past several weeks as to what their strategy for both platforms
is. I guess we now have an answer :-\. Pity - we started buying
the MX10003 last year, but I have no problem with the MX304 as
long as the price continues to work.<br>
<br>
The MX204 is pure shocker! Unless the MX304 will come with a
license-based approach to run at MX204 pricing, that is Juniper
shooting themselves in the foot.<br>
<br>
This chip shortage issue is, I think, being used as a crutch to
take the p*ss.<br>
<br>
Mark.<br>
</font><br></div></div>
<br>
<html><body bgcolor=#FFFFFF lang=EN-US link=#339933 text=#000000 vlink=#996600><img src=http://zuku.co.ke/es/sig_img.jpg></body></html>
<br>
</body></html>