I found the solution to this issue. It turns out the 'no-validate' requirement becomes a hidden command after invoking 'in-service-upgrade'. From the master RE, issue the following upgrade commands with active GRES between redundant RE's, of course.
{master}
root@R1_RE0>request vmhost software in-service-upgrade /var/tmp/<package-name> no-validate | reboot
I tested and reproduced this operation several times successfully in the MX-Series systems using vmhost REs.
------------------------------
David Pascarella
Sr. Networking Specialist
L3Harris Corporation
------------------------------
Original Message:
Sent: 01-17-2024 10:48
From: DAVID PASCARELLA
Subject: How to do ISSU on MX480 with VMHOST REs?
We have an MX480 with redundant RE-S-2X00x6 running Junos 21.4R2-S2.5. For field upgrades, we are testing ISSU and there seems to be a dilemma. With these RE's being vmhost versions, the required upgrade command is 'request vmhost software add <package-name> no-validate reboot'.
However when attempting ISSU, the required command is 'request vmhost software in-service-upgrade <package-name> reboot' and there isn't a 'no-validate' option available. The upgrade fails with an error stating no-validate is required, of course. All required sync and NSR features are deactivated/disabled in advance per Junos documentation.
Is ISSU supported with vmhost REs? If so, what is the process to complete it successfully in a production router?
Thank you,
------------------------------
David Pascarella
Sr. Networking Specialist
L3Harris Corporation
------------------------------