Earlier I was getting an error "The domain status of Virtual Connect Manager is not OK Update will not continue" while performing firmware upgrade of my Virtual Connect wherein one of my VC module had a hardware error after which the respective VC module was replaced. Now after replacement the new VC module had firmware version 4.62 while the existing VC module had firmware version 4.61 which is why they both failed to synch. In such cases it is very much expected that synch between both the Interconnect module will fail and will show as "Incompatible".
So in this article I will share the steps to fix such situation wherein both the VC interconnect modules are running with different firmware version and fix "The domain status of Virtual Connect Manager is not OK Update will not continue" error message.
Below is the screenshot of the Interconnect Module on my VC GUI
Now while attempting to upgrade the VC firmware using vcsu-1.12 I was getting below error
ERROR: The signature verification of specified package has failed
To overcome this problem I downloaded vcsu-1.14 which fixed the above problem but the original issue i.e. "The domain status of Virtual Connect Manager is not OK Update will not continue" still exists wherein we get below output while attempting to upgrade/downgrade the VC firmware
Stacking Connection: Failed Stacking Redundancy: No Redundancy The domain status of Virtual Connect Manager is not OK Update will not continue.
OR
-------------------------------------------------------------------- ERROR: Fatal error. One or more modules is preventing VCSU from continuing. Correct the conditions listed above and retry. ----------------------------------------------------------------------
How to fix "The domain status of Virtual Connect Manager is not OK update will not continue"?
To overcome this error "The domain status of Virtual Connect Manager is not OK Update will not continue", you have to perform FW update using "health" option in the vcsu instead of "version"
Let us start with the firmware update. You can download VCSU from HPE Official Page for Linux or Windows depending upon your environment.
Install VCSU rpm, since I am running this from Linux environment I have used rpm file
# rpm -Uvh vcsu-1.14.0.i686.rpm warning: vcsu-1.14.0.i686.rpm: Header V3 RSA/SHA256 Signature, key ID 61f75573: NOKEY Preparing... ################################# [100%] Updating / installing... 1:vcsu-1.14.0-11 ################################# [100%]
Get the VC firmware bin file to perform the FW update from the official HPE page
Execute vcsu from the terminal
# vcsu ------------------------------------------------------------------------------- HPE BladeSystem c-Class Virtual Connect Support Utility Version 1.14.0 (Build 11) Build Date: Oct 10 2018 21:08:42 Copyright (C) 2006-2018 Hewlett Packard Enterprise Development LP All Rights Reserved ------------------------------------------------------------------------------- Please enter action ("help" for list): update Please enter Onboard Administrator IP Address: 10.43.140.21 Please enter Onboard Administrator Username: HPadmin Please enter Onboard Administrator Password: *********** Please enter firmware package location: /tmp/vc/usr/lib/i386-linux-gnu/firmware-vceth-4.62-1.1/vcfwall462.bin Please enter Configuration backup password (Optional): Please enter Force Update options if any (eg: version,health): health Please enter VC-Enet module activation order if any (eg: parallel or odd-even or serial or manual. Default: odd-even): Please enter VC-FC module activation order if any (eg: parallel or odd-even or serial or manual. Default: serial): Please enter the time (in minutes) to wait between activating or rebooting VC-Enet modules (max 60 mins. Default: 0 mins): Please enter the time (in minutes) to wait between activating or rebooting VC-FC modules (max 60 mins. Default: 0 mins): The target configuration is integrated into a Virtual Connect Domain. Please enter the Virtual Connect Domain administrative user credentials to continue. User Name: HPadmin Password: *********** Force Health option is specified. Attempting to upgrade unhealthy modules. The following modules will be updated: =============================================================================== Enclosure Bay Module Current Version New Version =============================================================================== CZ3133RFBS 1 HP VC FlexFabric 4.61 4.62 10Gb/24-Port 2017-08-08T01:27:48Z 2018-01-26T07:07:32Z Module ------------------------------------------------------------------------------- The following modules will NOT be updated: ============================================================================ Enclosure Bay Module Current Version Status ============================================================================ CZ3133RFBS 2 HP VC FlexFabric 4.62 No update needed 10Gb/24-Port 2018-01-26T07:07:32Z Module ---------------------------------------------------------------------------- During the update process, modules being updated will be temporarily unavailable. In addition, the update process should NOT be interrupted by removing or resetting modules, or by closing the application. Interrupting the update or the modules being updated may cause the modules to not be updated properly. Please verify the above report before continuing. Would you like to continue with this update? [YES/NO]: YES The following modules were updated successfully: ======================================================================= Enclosure Bay Module New Version ======================================================================= CZ3133RFBS 1 HP VC FlexFabric 4.62 2018-01-26T07:07:32Z 10Gb/24-Port Module ----------------------------------------------------------------------- Total execution time: 00:20:18 VCSU log file is available at the following location: /root/vcsu-10181.log Press Return/Enter to exit...
So as you see our FW update has completed successfully.
Lastly I hope the steps from the article to perform firmware update on VC running with different version and fix "The domain status of Virtual Connect Manager is not OK Update will not continue" error was helpful. So, let me know your suggestions and feedback using the comment section.
Perfect saved me from rebuilding the domain!