We confirmed that RE0 and RE1 had a BIOS mismatch so we advised the customer to perform a BIOS upgrade to 30.07 (The current version was 30.05) so it could match the Master RE BIOS version. Once done, both REs reported the same alarm even though their BIOS was on the same version.
{master}
root@router> show chassis alarms
2 alarms currently active
Alarm time Class Description
2024-01-16 12:56:38 -05 Minor VMHost RE 1 Secure BIOS Version Mismatch
2024-01-16 10:04:36 -05 Minor VMHost RE 0 Secure BIOS Version Mismatch
root@router> show system firmware
Part Type Tag Current Available Status
version version
Routing Engine 0 RE BIOS 0 0.30.7-P 00.30.7 OK
Routing Engine 0 RE FPGA 1 41.0.0 41.0 OK
Routing Engine 0 RE SSD1 6 12050 12050 OK
Routing Engine 0 RE SSD2 6 12050 12050 OK
Routing Engine 0 RE i40e-NVM 7 7.0 0 OK
Routing Engine 1 0 0.30.7 0 OK
{backup}
Routing Engine 0 0 0.0.0 0 OK
Routing Engine 1 RE BIOS 0 0.30.7-P 00.30.7 OK
Routing Engine 1 RE FPGA 1 41.0.0 41.0 OK
Routing Engine 1 RE SSD1 6 12050 12050 OK
Routing Engine 1 RE SSD2 6 12050 12050 OK
Routing Engine 1 RE i40e-NVM 7 7.0 0 OK
To fix this problem we had to perform the BIOS upgrade twice per RE.
root@router> request system firmware upgrade re bios
Perform indicated firmware upgrade ? [yes,no] (no) yes
Firmware upgrade initiated, use "show system firmware" to monitor status.
After upgrade, reboot using "request vmhost reboot" for BIOS to take effect
Routing Engine 0 RE BIOS 0 0.30.7-P 00.30.7 UPGRADED SUCCESSFULLY
Routing Engine 1 0 0.0.0 0 OK
root@router> request vmhost reboot re0
Reboot the vmhost ? [yes,no] (no) yes
re0:
--------------------------------------------------------------------------
*** FINAL System shutdown message from root@router ***
System going down IMMEDIATELY
{master} root@TAC_TACP1_JMX2020-RE0> show chassis alarms No alarms currently active