Hi Jeff,
Thank you very mush for sharing this information. Do you know in what
publicly available release it's going to be fixed? Knowing PR number
would be the best but I guess it may be internal-only.
Kind regards,
Andrey
Litterick, Jeff (BIT) via juniper-nsp писал(а) 2023-06-08 18:03:
No, that is not quite right. We have 2 chassis of MX304 in Production
today and 1 spare all with Redundant REs You do not need all the
ports filled in a port group. I know since we mixed in some 40G and
40G is ONLY supported on the bottom row of ports so we have a mix and
had to break stuff out leaving empty ports because of that limitation,
and it is running just fine. But you do have to be careful which
type of optics get plugged into which ports. IE Port 0/2 vs Port 1/3
in a grouping if you are not using 100G optics.
The big issue we ran into is if you have redundant REs then there is a
super bad bug that after 6 hours (1 of our 3 would lock up after
reboot quickly and the other 2 would take a very long time) to 8 days
will lock the entire chassis up solid where we had to pull the REs
physical out to reboot them. It is fixed now, but they had to
manually poke new firmware into the ASICs on each RE when they were in
a half-powered state, Was a very complex procedure with tech support
and the MX304 engineering team. It took about 3 hours to do all 3
MX304s one RE at a time. We have not seen an update with this
built-in yet. (We just did this back at the end of April)
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
