HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

virtual connect degraded after a failed firmware update

 
SOLVED
Go to solution
aliet
Occasional Visitor

virtual connect degraded after a failed firmware update

Hi,


I tried to update the firmware on both my Flex10 Virtual Connect managers from 3.15 to 3.18 and the second from 2.33 to 3.18 since they were failing because of version mismatch . I used vcsu version 1.6.0 after some time the update failed. Now I can't log into the 2nd VC(2.33->3.18) the module shows as Degraded because Device is reporting an internal degraded status, it doesn't have ip configured but shows everything else as OK, the led in the back is ambar reporting a failure, oa display ok the module

If there is another way to completly reflash   a virtual connect without ip capability because of  a firmware corrupted.

I don't understand why this happened since vcsu reported it was not going to update the vc, something was wrong and now the second vc seems to have corrupted the firmware, I guess.

At this point I need a completly reflash of the vc.

 

I will thank's any help, here the log wich shows vc was not going to update

 

[Wed Aug 24 15:56:50 2011] The following modules will be updated:
[Wed Aug 24 15:56:50 2011]
[Wed Aug 24 15:56:50 2011] ===================================================================
[Wed Aug 24 15:56:50 2011] Enclosure   Bay  Module           Current Version  New Version    
[Wed Aug 24 15:56:50 2011] ===================================================================
[Wed Aug 24 15:56:50 2011] GB8823R382  3    HP Virtual       1.40 7.12.4.06   1.41 7.12.4.11 
[Wed Aug 24 15:56:50 2011]                  Connect 4Gb FC                                   
[Wed Aug 24 15:56:50 2011]                  Module                                           
[Wed Aug 24 15:56:50 2011] -------------------------------------------------------------------
[Wed Aug 24 15:56:50 2011] GB8823R382  4    HP Virtual       1.30 7.12.0.14   1.41 7.12.4.11 
[Wed Aug 24 15:56:50 2011]                  Connect 4Gb FC                                   
[Wed Aug 24 15:56:50 2011]                  Module                                           
[Wed Aug 24 15:56:50 2011] -------------------------------------------------------------------
[Wed Aug 24 15:56:50 2011]
[Wed Aug 24 15:56:50 2011] The following modules will NOT be updated:
[Wed Aug 24 15:56:50 2011]
[Wed Aug 24 15:56:50 2011] ==============================================================================
[Wed Aug 24 15:56:50 2011] Enclosure   Bay  Module           Current Version       Status               
[Wed Aug 24 15:56:50 2011] ==============================================================================
[Wed Aug 24 15:56:50 2011] GB8823R382  1    HP VC Flex-10    3.15                  Stale configuration  
[Wed Aug 24 15:56:50 2011]                  Enet Module      2010-10-09T07:18:16Z  in VCM               
[Wed Aug 24 15:56:50 2011] ------------------------------------------------------------------------------
[Wed Aug 24 15:56:50 2011] GB8823R382  2    HP VC Flex-10    Unknown               Unable to setup      
[Wed Aug 24 15:56:50 2011]                  Enet Module                            command session      
[Wed Aug 24 15:56:50 2011] ------------------------------------------------------------------------------

1 REPLY
aliet
Occasional Visitor
Solution

Re: virtual connect degraded after a failed firmware update

 

I finally fixed this issue following this post:

 

http://h30499.www3.hp.com/t5/HP-BladeSystem/Replacement-of-a-virtual-connect-with-different-firmware-version/td-p/4787764

 

wich suggets

-> put your new VC in the bay 5 or 6(might be other enclosure as well)(Used bay 6)
-> address it in the EIPBA tab
-> reboot the new VC
-> wait for it to "answer" ping from your workstation
-> flash it with VCSU 1.5.2(latest one) with the FW you want(I used 1.6.0)
-> remove its address from EIPBA tab
-> replace VC in bay 2 with the new one

This fixed the virtual connect state, so it can boot with the old firmware, after that I updated the vc with 3.18, just one thing to notice, even with 3.18 I had for a few minutes the No communication error in the vc in bay 2, after some minutes worked again, not sure about this.

best regards