BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

Is Virtual Connect-FC incompatible with Virtual Connect Manager upgrade ?

chuckk281
Trusted Contributor

Is Virtual Connect-FC incompatible with Virtual Connect Manager upgrade ?

Jose had a question when upgrading Virtual Connect Manager:

 

**************************

 

VC modules are VC Flex-10  and VC-8Gb 20port FC module.

After power up and configuration, the VC-FC show "incompatible".  Looking at logs, we should upgrade VC-FC firmware to 1.41 (from current 1.40).

 

System log shows:

2010-09-16T18:35:54-04:00 VCEXTW2030017Z vcmd: [FC:enc0:iobay3:4010:Info] FC Module state OK : Component fully operational
2010-09-16T18:35:55-04:00 VCEXTW2030017Z vcmd: [FC:enc0:iobay3:4014:Major] FC Module state INCOMPATIBLE : Component does not match configuration
2010-09-16T18:35:55-04:00 VCEXTW2030017Z vcmd: [ENET:enc0:iobay3:3014:Major] Enet Module state INCOMPATIBLE : Firmware mismatch: Current: [1.40], Supported: [1.41]. Module will be marked as INCOMPATIBLE.
2010-09-16T18:35:55-04:00 VCEXTW2030017Z vcmd: [FC:enc0:iobay4:4010:Info] FC Module state OK : Component fully operational
2010-09-16T18:35:55-04:00 VCEXTW2030017Z vcmd: [FC:enc0:iobay4:4014:Major] FC Module state INCOMPATIBLE : Component does not match configuration
2010-09-16T18:35:55-04:00 VCEXTW2030017Z vcmd: [ENET:enc0:iobay4:3014:Major] Enet Module state INCOMPATIBLE : Firmware mismatch: Current: [1.40], Supported: [1.41]. Module will be marked as INCOMPATIBLE.
2010-09-16T18:35:57-04:00 VCEXTW2030017Z vcmd: [SVR:enc0:dev1:5004:Info] Server power on

 

 

Searching for support/software downloads for the VC-FC module leads me to the VCM upgrade bundle for 3.10 already installed.

 

What are we missing ?

 

********************************

 

Vincent joined the conversation:

 

**************************

Most likely the VC upgrade from 2.33 to 3.10 failed to upgrade the VC-FC modules for some reason. If you still have the VCSU logs from that upgrade, check them out. Anyway, you can retry the upgrade, VCSU will detect the Flex-10 modules are already on 3.10 but it should offer to upgrade the VC-FC modules. Do a VCSU healthcheck first.

 

**********************************

 

Have you seen this issue? Any suggestions or comments?

3 REPLIES
UncleDr
Occasional Visitor

Re: Is Virtual Connect-FC incompatible with Virtual Connect Manager upgrade ?

Have same problem.

 

Here is VCSU 1.5.1 log (fw2.33 or 3.10 - no difference):

[Thu Sep 23 19:01:36 2010] (7532)[VcsuInit.cpp:240] : Main Thread ID: 3852
[Thu Sep 23 19:01:36 2010] (7532)[VcsuInit.cpp:444] : VCSU Library Version: 1.5.1.9
[Thu Sep 23 19:01:36 2010] (7532)[VcsuWin.cpp:105] : Found group membership: User
[Thu Sep 23 19:01:36 2010] (7532)[VcsuWin.cpp:105] : Found group membership: Admin
[Thu Sep 23 19:01:36 2010] (7532)[VcsuWin.cpp:109] : Matched Administrators
[Thu Sep 23 19:01:36 2010] (7532)[VcsuInit.cpp:347] : Administrator or Power User privilege available
[Thu Sep 23 19:01:36 2010] (7532)[VcsuInit.cpp:296] : Got data port 35768
[Thu Sep 23 19:01:36 2010] (7532)[VcsuInit.cpp:309] : Port 35768 not in use. Passing it up.
[Thu Sep 23 19:01:36 2010] (7532)[OaWrap.cpp:758] : Given oaip = 10.132.0.241
[Thu Sep 23 19:01:37 2010] (7532)[OaWrap.cpp:772] : oa1 ip = 10.132.0.241
[Thu Sep 23 19:01:37 2010] (7532)[VcsuCore.cpp:182] : OA Version: 3.11
[Thu Sep 23 19:01:37 2010] (7532)[OaWrap.cpp:359] : get_OAStatus::Enclosure ROLE=4
[Thu Sep 23 19:01:44 2010] (7532)[OaWrap.cpp:505] : User added successfully
[Thu Sep 23 19:01:52 2010] (7532)[OaWrap.cpp:591] : User has been successfully given access to all bay
[Thu Sep 23 19:01:53 2010] (7532)[OaWrap.cpp:359] : get_OAStatus::Enclosure ROLE=4
[Thu Sep 23 19:01:53 2010] (7532)[VcsuCore.cpp:413] : Enclosure name: BladeSystem c7000 Enclosure G2, type = 0
[Thu Sep 23 19:01:54 2010] (7532)[VcsuCore.cpp:2169] : Bay 1 is Okay
[Thu Sep 23 19:01:55 2010] (7532)[VcsuCore.cpp:642] : cli_compatibility = 1.20;1.30;2.00
[Thu Sep 23 19:01:56 2010] (7532)[VcsuCore.cpp:2169] : Bay 2 is Okay
[Thu Sep 23 19:01:58 2010] (7532)[VcsuCore.cpp:642] : cli_compatibility = 1.20;1.30;2.00
[Thu Sep 23 19:01:59 2010] (7532)[VcsuCore.cpp:2169] : Bay 3 is Okay
[Thu Sep 23 19:02:00 2010] (7532)[VcsuCore.cpp:579] : bay->version = 1.40 7.12.4.06
[Thu Sep 23 19:02:00 2010] (7532)[LocalIp.cpp:78] : connect failed. System may not be up or invalid IP address
[Thu Sep 23 19:02:00 2010] (7532)[VcsuCore.cpp:1023] : fillFcTrayInfo failed
[Thu Sep 23 19:02:00 2010] (7532)[VcsuCore.cpp:1095] : fw_getTrayInfo failed for bay 3 
[Thu Sep 23 19:02:01 2010] (7532)[VcsuCore.cpp:2143] : Module not present in bay 4
[Thu Sep 23 19:02:01 2010] (7532)[VcsuCore.cpp:2143] : Module not present in bay 5
[Thu Sep 23 19:02:02 2010] (7532)[VcsuCore.cpp:2143] : Module not present in bay 6
[Thu Sep 23 19:02:02 2010] (7532)[VcsuCore.cpp:2143] : Module not present in bay 7
[Thu Sep 23 19:02:03 2010] (7532)[VcsuCore.cpp:2143] : Module not present in bay 8
[Thu Sep 23 19:02:16 2010] (7532)[OaWrap.cpp:359] : get_OAStatus::Enclosure ROLE=4
[Thu Sep 23 19:02:17 2010] (7532)[VcsuCore.cpp:413] : Enclosure name: BladeSystem c7000 Enclosure G2, type = 0
[Thu Sep 23 19:02:17 2010] (7532)[VcsuCore.cpp:2169] : Bay 1 is Okay
[Thu Sep 23 19:02:19 2010] (7532)[VcsuCore.cpp:642] : cli_compatibility = 1.20;1.30;2.00
[Thu Sep 23 19:02:20 2010] (7532)[VcsuCore.cpp:2169] : Bay 2 is Okay
[Thu Sep 23 19:02:21 2010] (7532)[VcsuCore.cpp:642] : cli_compatibility = 1.20;1.30;2.00
[Thu Sep 23 19:02:23 2010] (7532)[VcsuCore.cpp:2169] : Bay 3 is Okay
[Thu Sep 23 19:02:24 2010] (7532)[VcsuCore.cpp:579] : bay->version = 1.40 7.12.4.06
[Thu Sep 23 19:02:24 2010] (7532)[LocalIp.cpp:78] : connect failed. System may not be up or invalid IP address
[Thu Sep 23 19:02:24 2010] (7532)[VcsuCore.cpp:1023] : fillFcTrayInfo failed
[Thu Sep 23 19:02:24 2010] (7532)[VcsuCore.cpp:1095] : fw_getTrayInfo failed for bay 3 
[Thu Sep 23 19:02:24 2010] (7532)[VcsuCore.cpp:2143] : Module not present in bay 4
[Thu Sep 23 19:02:25 2010] (7532)[VcsuCore.cpp:2143] : Module not present in bay 5
[Thu Sep 23 19:02:25 2010] (7532)[VcsuCore.cpp:2143] : Module not present in bay 6
[Thu Sep 23 19:02:26 2010] (7532)[VcsuCore.cpp:2143] : Module not present in bay 7
[Thu Sep 23 19:02:26 2010] (7532)[VcsuCore.cpp:2143] : Module not present in bay 8
[Thu Sep 23 19:02:27 2010] (7532)[VcsuCore.cpp:1166] : Domain configuration is present
[Thu Sep 23 19:02:27 2010] (7532)[VcsuCore.cpp:1180] : This is primary enclosure
[Thu Sep 23 19:02:28 2010] (7532)[VcsuInit.cpp:731] : VCM user authenticated successfully
[Thu Sep 23 19:02:32 2010] (7532)[VcsuCore.cpp:3706] : File D:\vcfwall310.bin exists, overwriting..
[Thu Sep 23 19:02:32 2010] (7532)[VcsuFirmware.cpp:559] : Verifying package signature...
[Thu Sep 23 19:02:33 2010] (7532)[VcsuFirmware.cpp:577] : Extracting package 
[Thu Sep 23 19:02:33 2010] (7532)[Extract.cpp:142] : Extracting tar from D:\vcfwall310.bin
[Thu Sep 23 19:02:51 2010] (7532)[Extract.cpp:193] : Done extracting tar from D:\vcfwall310.bin
[Thu Sep 23 19:02:51 2010] (7532)[Extract.cpp:31] : Extracting PackageDesc.xml from VCpackage.tar
[Thu Sep 23 19:02:51 2010] (7532)[Extract.cpp:121] : Done extracting PackageDesc.xml from VCpackage.tar
[Thu Sep 23 19:02:51 2010] (7532)[Extract.cpp:31] : Extracting vcenet.img from VCpackage.tar
[Thu Sep 23 19:02:57 2010] (7532)[Extract.cpp:121] : Done extracting vcenet.img from VCpackage.tar
[Thu Sep 23 19:02:57 2010] (7532)[Extract.cpp:31] : Extracting vcfc.img from VCpackage.tar
[Thu Sep 23 19:03:03 2010] (7532)[Extract.cpp:121] : Done extracting vcfc.img from VCpackage.tar
[Thu Sep 23 19:03:03 2010] (7532)[Extract.cpp:31] : Extracting vcfc2.img from VCpackage.tar
[Thu Sep 23 19:03:08 2010] (7532)[Extract.cpp:121] : Done extracting vcfc2.img from VCpackage.tar
[Thu Sep 23 19:03:08 2010] (7532)[Extract.cpp:142] : Extracting tar from vcfc2.img
[Thu Sep 23 19:03:14 2010] (7532)[Extract.cpp:193] : Done extracting tar from vcfc2.img
[Thu Sep 23 19:03:14 2010] (7532)[Extract.cpp:238] : Extracting all files from vcfc2\vcfc2.tgz
[Thu Sep 23 19:03:21 2010] (7532)[Extract.cpp:339] : Reached end of file
[Thu Sep 23 19:03:21 2010] (7532)[Extract.cpp:359] : Done extracting all files from vcfc2\vcfc2.tgz
[Thu Sep 23 19:03:21 2010] (7532)[VcsuFirmware.cpp:589] : Parsing package information 
[Thu Sep 23 19:03:21 2010] (7532)[Extract.cpp:31] : Extracting PackageDesc.xml from VCpackage.tar
[Thu Sep 23 19:03:21 2010] (7532)[Extract.cpp:121] : Done extracting PackageDesc.xml from VCpackage.tar
[Thu Sep 23 19:03:21 2010] (7532)[Extract.cpp:31] : Extracting ReleaseNotes.txt from VCpackage.tar
[Thu Sep 23 19:03:21 2010] (7532)[Extract.cpp:121] : Done extracting ReleaseNotes.txt from VCpackage.tar
[Thu Sep 23 19:03:21 2010] (7532)[VcsuFirmware.cpp:254] : failed xml_getChild_ByName for SoftResetThreshold

[Thu Sep 23 19:03:21 2010] (7532)[VcsuFirmware.cpp:288] : Information for module type VC-ENETFCOE is not available in this package
[Thu Sep 23 19:03:21 2010] (7532)[VcsuFirmware.cpp:481] : xml_get_module_Info VC-ENETFCOE failed for PackageDesc.xml
[Thu Sep 23 19:03:21 2010] (7532)[VcsuFirmware.cpp:613] : ReleaseNotes.htm saved in current directory
[Thu Sep 23 19:03:21 2010] (7532)[VcsuCore.cpp:2164] : contactOk is FALSE for bay 3
[Thu Sep 23 19:03:45 2010] (7532)[OaWrap.cpp:739] : User successfully deleted

 Tomorrow will try to use VCSU 1.4.1

HP help would be nice in this thread...

gunelius
Occasional Advisor

Re: Is Virtual Connect-FC incompatible with Virtual Connect Manager upgrade ?

I ran into an almost identical issue on my VC-FC modules in one of my enclosures.  OA was seeing them as firmware 1.41, but VC was reporting them as an earlier revision (1.40) and their VC status was "Incompatible".  I contacted HP and the since it appeared that VCM wasn't seeing the FC modules correctly, the technician had me use Tools, Reset Virtual Connect Manager and then everything was okay.  The next time I logged into VCM, the modules reported their proper firmware revision and didn't show any error.

 

Cheers,

 

Scott

UncleDr
Occasional Visitor

Re: Is Virtual Connect-FC incompatible with Virtual Connect Manager upgrade ?

Still have the problem with my  Virtual Connect 8Gb 20-port Fibre Channel

 

This module is not redundant (the only one FC module in enclosure), may it cause the problem?

 

Here is VCSU 1.4.1 log:

 

008316 (0) vcsu.cpp[8971] 
=== log file fwupdate.log opened at Wed Nov 24 07:17:36 2010

008316 (0) vcsu.cpp[8972] === running version 1.4.1.55 built on Jul 30 2009 at 16:27:09
008316 (0) vcsu.cpp[1481] 
008316 (0) vcsu.cpp[466] ------------------------------------------------------------------------------
008316 (0) vcsu.cpp[1483]  HP BladeSystem c-Class Virtual Connect Support Utility
008316 (0) vcsu.cpp[1484]  Version 1.4.1 (Build 55)
008316 (0) vcsu.cpp[1485]  Build Date: Jul 30 2009 16:27:09
008316 (0) vcsu.cpp[1486]  Copyright (C) 2007-2009 Hewlett-Packard Development Company, L.P.
008316 (0) vcsu.cpp[1487]  All Rights Reserved
008316 (0) vcsu.cpp[466] ------------------------------------------------------------------------------
008316 (0) vcsu.cpp[1489] 
008316 (0) vcsu.cpp[1618] Main Thread ID: 8316
008316 (0) vcsu-win.cpp[103] Found group membership: User
008316 (0) vcsu-win.cpp[103] Found group membership: Admin
008316 (0) vcsu-win.cpp[107] Matched Administrators
008316 (0) vcsu.cpp[1626] Administrator or Power User privilege available
008316 (0) ftp.cpp[849] Got data port 12096
008316 (0) ftp.cpp[862] Port 12096 not in use. Passing it up.
008316 (0) vcsu.cpp[1798] Initializing, 0% complete...
008316 (0) vcsu.cpp[1812] 
Initializing, 10% complete...
008316 (0) oawrap.cpp[630] Given oaip = 10.132.0.241
008316 (1) oawrap.cpp[644] oa1 ip = 10.132.0.241
008316 (1) vcsu.cpp[8419] OA Version: 3.10
008316 (1) vcsu.cpp[1822] 
Initializing, 20% complete...
008316 (1) oawrap.cpp[300]  get_OAStatus::Enclosure ROLE=4
008316 (1) vcsu.cpp[1832] 
Initializing, 28% complete...
008316 (2) oawrap.cpp[390]  User already exists
008316 (4) oawrap.cpp[613] User successfully deleted
008316 (9) oawrap.cpp[416]  User added successfully
008316 (14) oawrap.cpp[497]  User has been successfully given access to all bay
008316 (14) vcsu.cpp[1842] 
Initializing, 36% complete...
008316 (15) vcsu.cpp[1852] 
Initializing, 44% complete...
008316 (15) oawrap.cpp[300]  get_OAStatus::Enclosure ROLE=4
008316 (16) vcsu.cpp[1435] Enclosure name: BladeSystem c7000 Enclosure G2, type = 0
008316 (16) vcsu.cpp[6046] Bay 1 is Okay
008316 (19) vcsu.cpp[6046] Bay 2 is Okay
008316 (22) vcsu.cpp[6046] Bay 3 is Okay
008316 (24) vcsu.cpp[6020] Module not present in bay 4
008316 (24) vcsu.cpp[6020] Module not present in bay 5
008316 (24) vcsu.cpp[6020] Module not present in bay 6
008316 (24) vcsu.cpp[6020] Module not present in bay 7
008316 (25) vcsu.cpp[6020] Module not present in bay 8
008316 (25) vcsu.cpp[11081] Domain configuration is present
008316 (25) vcsu.cpp[11093] This is primary enclosure
008316 (25) vcsu.cpp[1435] Enclosure name: BladeSystem c7000 Enclosure G2, type = 0
008316 (25) vcsu.cpp[1996] 
Initializing, 52% complete...
008316 (26) vcsu.cpp[6046] Bay 1 is Okay
008316 (29) vcsu.cpp[6046] Bay 2 is Okay
008316 (32) vcsu.cpp[6046] Bay 3 is Okay
008316 (33) vcsu.cpp[6020] Module not present in bay 4
008316 (33) vcsu.cpp[6020] Module not present in bay 5
008316 (34) vcsu.cpp[6020] Module not present in bay 6
008316 (34) vcsu.cpp[6020] Module not present in bay 7
008316 (34) vcsu.cpp[6020] Module not present in bay 8
008316 (34) vcsu.cpp[2006] 
Initializing, 60% complete...
008316 (35) vcsu.cpp[2141] 
Initializing, 68% complete...
008316 (37) vcsu.cpp[2292] 
Initializing, 76% complete...
008316 (37) vcsu.cpp[2558] 
Initializing, 84% complete...
008316 (38) extract.cpp[185] Extracting tar from D:\blades\vcfwe1f234.bin
008316 (48) extract.cpp[228] Done extracting tar from D:\blades\vcfwe1f234.bin
008316 (48) extract.cpp[72] Extracting PackageDesc.xml from VCpackage.tar
008316 (48) extract.cpp[173] Done extracting PackageDesc.xml from VCpackage.tar
008316 (48) extract.cpp[72] Extracting vcenet.img from VCpackage.tar
008316 (53) extract.cpp[173] Done extracting vcenet.img from VCpackage.tar
008316 (53) extract.cpp[72] Extracting vcfc.img from VCpackage.tar
008316 (58) extract.cpp[173] Done extracting vcfc.img from VCpackage.tar
008316 (58) vcsu.cpp[2801] 
Initializing, 92% complete...
008316 (58) xml.cpp[31]  Image type = 1
008316 (58) xml.cpp[32]  revision = 2.34
008316 (58) xml.cpp[33]  BuildId = 2010-09-09T04:34:45Z
008316 (58) xml.cpp[34] Supported hardware types(4): 
008316 (58) xml.cpp[38] 399593-B21
008316 (58) xml.cpp[38] 399593-B22
008316 (58) xml.cpp[38] 447047-B21
008316 (58) xml.cpp[38] 455880-B21
008316 (58) xml.cpp[31]  Image type = 2
008316 (58) xml.cpp[32]  revision = 1.41
008316 (58) xml.cpp[33]  BuildId = 7.12.4.11
008316 (58) xml.cpp[34] Supported hardware types(3): 
008316 (58) xml.cpp[38] 409513-B21
008316 (58) xml.cpp[38] 409513-B22
008316 (58) xml.cpp[38] 572018-B21
008316 (58) xml.cpp[306]  Information for module type VC-FC2 is not available in this package
008316 (58) vcsu.cpp[8652] xml_get_module_Info VC-FC2 failed for PackageDesc.xml
008316 (58) vcsu.cpp[6046] Bay 3 is Okay
008316 (58) vcsu.cpp[10240] Current firmware revision on 1.400000 of Omaha module in bay: 3 supports generated FTP port feature.
008316 (58) vcsu.cpp[2903] 
Initializing, 100% complete...
008316 (61) vcsu.cpp[2905] 
                                                                             

008316 (61) vcsu.cpp[489] 
008316 (61) vcsu.cpp[1099] Package supports the hardware 572018-B21
008316 (61) vcsu.cpp[1108] Application supports the hardware 572018-B21
008316 (61) CommandOutput.cpp[218] 
008316 (61) CommandOutput.cpp[218] The following modules will be updated:
008316 (61) CommandOutput.cpp[218] 
008316 (61) CommandOutput.cpp[218] ===================================================================
008316 (61) CommandOutput.cpp[218] Enclosure   Bay  Module           Current Version  New Version     
008316 (61) CommandOutput.cpp[218] ===================================================================
008316 (61) CommandOutput.cpp[218] GB8020VR2M  3    HP VC 8Gb        1.40 7.12.4.06   1.41 7.12.4.11  
008316 (61) CommandOutput.cpp[218]                  20-Port FC                                        
008316 (61) CommandOutput.cpp[218]                  Module                                            
008316 (61) CommandOutput.cpp[218] -------------------------------------------------------------------
008316 (61) vcsu.cpp[1099] Package supports the hardware 572018-B21
008316 (61) vcsu.cpp[1108] Application supports the hardware 572018-B21
008316 (61) vcsu.cpp[745] 
008316 (61) vcsu.cpp[746] Please verify the above report before continuing.
008316 (61) vcsu.cpp[751] 
008316 (61) vcsu.cpp[752] Enclosure is configured for Virtual Connect.
008316 (61) vcsu.cpp[753] VC Domain operations will be unavailable during the firmware update process.
008316 (61) vcsu.cpp[756] 
008316 (61) vcsu.cpp[758] During the update process, modules being updated will be temporarily
008316 (61) vcsu.cpp[759] unavailable. In addition, the update process should NOT be interrupted by
008316 (61) vcsu.cpp[760] removing or resetting modules, or by closing the application. Interrupting
008316 (61) vcsu.cpp[761] the update or the modules being updated may cause the modules to not be updated
008316 (61) vcsu.cpp[762] properly.
008316 (61) vcsu.cpp[763] 
008316 (61) vcsu.cpp[869] Total estimated time for updates: 9-19 minutes
008316 (61) vcsu.cpp[870] 
008316 (61) vcsu.cpp[893] Would you like to continue with this update? [YES/NO]: 
008316 (65) vcsu.cpp[2951] All FC modules support new FTP feature. Starting FTP on port 12096
008316 (65) vcsu.cpp[2971] Launching FTP Server...
008316 (65) vcsu.cpp[2973] FTP Server launched on Thread ID: 2652
002652 (65) ftp.cpp[178] Got a parameter to runftpd.
002652 (65) ftp.cpp[179] Enabling new FTP feature is enabled.
002652 (65) ftp.cpp[180] Generated port for FTP server is: 12096
008316 (65) vcsu.cpp[10142] 
                                                                             

008316 (65) vcsu.cpp[10143] Saving Virtual Connect configuration...
008316 (69) vcdownload.cpp[1342] Download succeeded
008316 (69) vcdownload.cpp[1264] Got file name in response of: ..\vcConfig-mosc7000-01_vc_domain-20101124
008316 (69) vcsu.cpp[3123] bayNum = 3
008316 (69) vcsu.cpp[3137] Primary VCM module is in Bay 1
009472 (69) vcsu.cpp[6046] Bay 3 is Okay
009472 (69) fc_update.cpp[255] cmd id = 0
008316 (70) vcsu.cpp[3266] 
                                                                             

008316 (70) vcsu.cpp[3267] Update Progress: 5% completed
009472 (72) fc_update.cpp[144] Setting new ftp information for FC module on bay 3
009472 (72) fc_update.cpp[367]  Previous command_id = 0x14 
009472 (72) vcsu.cpp[9009] cmd id = 21, bay = 3
009472 (72) fc_update.cpp[255] cmd id = 21
008316 (72) vcsu.cpp[3266] 
                                                                             

008316 (72) vcsu.cpp[3267] Update Progress: 50% completed
009472 (73) fc_update.cpp[588] cmd id = 0x15,timeout = 300 for bay 3
009472 (73) vcsu.cpp[9032] exec command failed for ACTIVATE_FIRMWARE on bay 3
009472 (73) vcsu.cpp[9033] Status returned = 16
009472 (73) vcsu.cpp[9351] fc_sendFirmware on bay 3 failed
009472 (73) vcsu.cpp[5773] Firmware update failed on enclosure GB8020VR2M bay 3. Firmware Version: 1.41
008316 (73) vcsu.cpp[3315] 
                                                                             

008316 (73) vcsu.cpp[3316] Activate Progress: 0% completed
008316 (73) vcsu.cpp[3653] Activation order is ODD EVEN
008316 (73) vcsu.cpp[3657] Activation for single bay
008316 (73) vcsu.cpp[4772] 
                                                                             

008316 (73) vcsu.cpp[4773] Activate Progress: 50% completed
008316 (85) vcsu.cpp[4825] 
                                                                             

008316 (85) vcsu.cpp[4826] Activate Progress: 50% completed
008316 (85) vcsu.cpp[4964] Activating VC-FC modules...
008316 (85) vcsu.cpp[5006] Skipping module activation (Bay 3)
008316 (85) vcsu.cpp[5041] Activating VC-FC modules completed
008316 (85) vcsu.cpp[5327] 
                                                                             

008316 (85) vcsu.cpp[5329] Activate Progress: 100% completed
008316 (85) vcsu.cpp[5338] 
                                                                             

008316 (85) vcsu.cpp[5339] 
008316 (85) vcsu.cpp[466] ------------------------------------------------------------------------------
008316 (85) vcsu.cpp[5342]  FIRMWARE UPDATE STATUS SUMMARY
008316 (85) vcsu.cpp[466] ------------------------------------------------------------------------------
008316 (85) vcsu.cpp[5484] 
008316 (85) vcsu.cpp[5485] The following modules were not successful:
008316 (85) CommandOutput.cpp[218] ======================================================================
008316 (85) CommandOutput.cpp[218] Enclosure   Bay  Module                       Status                  
008316 (85) CommandOutput.cpp[218] ======================================================================
008316 (85) CommandOutput.cpp[218] GB8020VR2M  3    HP VC 8Gb 20-Port FC Module  Firmware update failed  
008316 (85) vcsu.cpp[5558] 
008316 (85) vcsu.cpp[466] ------------------------------------------------------------------------------
008316 (85) vcsu.cpp[3010] SUCCESS: All firmware update operations completed successfully
008316 (85) vcsu.cpp[3013] 
008316 (85) vcsu.cpp[3020] Total execution time: 00:00:16
008316 (87) oawrap.cpp[613] User successfully deleted

 

Hope to find solution...