https://community.hpe.com/t5/bladesystem-general/problem-with-virtual-connect/m-p/4558106#M8691 Erick,<BR /><BR />Couple of things:<BR /><BR />First, VC firmware upgrades via the GUI are not very reliable. There is a firmware upgrade utility which is much more reliable.<BR />The utility is called "Virtual Connect Support Utility" (VCSU) and is generally more reliable.<BR /><BR />The second thing is, (and I know this is not a popular suggestion, however it usually works.), shutdown your servers, and remove/replace the VC FC module from the enclosure. Wait ~10 seconds when you remove it, and then re-insert it. <BR /><BR />You will see that it disappears from your OA display, and the OA log will record the removal and replacement.<BR /><BR />If you wait a couple of minutes, the OA should rediscover the FC module. <BR /><BR />This usually works, however there are no guarantees. (However since it is not working right now, what do you have to lose?)<BR /><BR />Hope this helps,<BR /><BR />Dave. Tue, 05 Jan 2010 13:34:04 GMT The Brit 2010-01-05T13:34:04Z https://community.hpe.com/t5/bladesystem-general/problem-with-virtual-connect/m-p/4558105#M8690 I had no problem errors on any device it seams that all the upgrade process was transparent as i did the update by "GUI" (virtual connect)also the update for OA was by GUI<BR /><BR />The blades upgrade was with firmwarecd<BR /><BR />the currently firmware versions i have <BR /><BR />Device Model ProLiant BL460c G1 I15 <BR />ROM Version 07/10/2009 <BR />ilo model iLO2<BR />iLO Firmware Version 1.77 Apr 23 2009<BR />Power Management Controller Version 0.5<BR /><BR />OA ver. 2.51<BR />virtual connect 2.10<BR /><BR />Bay Device Model Firmware Version <BR /><BR />1 HP 1/10Gb VC-Enet Module 2.10 <BR />2 HP 1/10Gb VC-Enet Module 2.10 <BR />3 HP 4Gb VC-FC Module 1.32 <BR /><BR /><BR /><BR />i had before <BR /><BR />ilo blabes 1.70 <BR />OA 2.32 <BR />virtual connect 1.31 <BR /><BR />iam copying you error messages of VC logs<BR /><BR />2009-12-22T10:23:54-06:00 VCETW280200PL vcmd: [FC:enc0:iobay3:4019:Major] FC Module state NO_COMM : Cannot communicate with component<BR />2009-12-22T10:23:55-06:00 VCETW280200PL vcmd: [FC:enc0:iobay3:4004:Info] FC Module power on<BR />2009-12-22T10:24:10-06:00 VCETW280200PL vcmd: [FC:enc0:iobay3:4011:Warning] FC Module state UNKNOWN : Component operational state cannot be determine<BR /><BR /><BR />the problem is that the VC ethernet can't administer with the VC of FC neither<BR />can with OA manage so I can't manage my SAN Mon, 04 Jan 2010 20:40:17 GMT https://community.hpe.com/t5/bladesystem-general/problem-with-virtual-connect/m-p/4558105#M8690 Erick Flores Rivas 2010-01-04T20:40:17Z https://community.hpe.com/t5/bladesystem-general/problem-with-virtual-connect/m-p/4558106#M8691 Erick,<BR /><BR />Couple of things:<BR /><BR />First, VC firmware upgrades via the GUI are not very reliable. There is a firmware upgrade utility which is much more reliable.<BR />The utility is called "Virtual Connect Support Utility" (VCSU) and is generally more reliable.<BR /><BR />The second thing is, (and I know this is not a popular suggestion, however it usually works.), shutdown your servers, and remove/replace the VC FC module from the enclosure. Wait ~10 seconds when you remove it, and then re-insert it. <BR /><BR />You will see that it disappears from your OA display, and the OA log will record the removal and replacement.<BR /><BR />If you wait a couple of minutes, the OA should rediscover the FC module. <BR /><BR />This usually works, however there are no guarantees. (However since it is not working right now, what do you have to lose?)<BR /><BR />Hope this helps,<BR /><BR />Dave. Tue, 05 Jan 2010 13:34:04 GMT https://community.hpe.com/t5/bladesystem-general/problem-with-virtual-connect/m-p/4558106#M8691 The Brit 2010-01-05T13:34:04Z