- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- problem with virtual connect
BladeSystem - General
1752808
Members
6288
Online
108789
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2010 12:40 PM
01-04-2010 12:40 PM
problem with virtual connect
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
The blades upgrade was with firmwarecd
the currently firmware versions i have
Device Model ProLiant BL460c G1 I15
ROM Version 07/10/2009
ilo model iLO2
iLO Firmware Version 1.77 Apr 23 2009
Power Management Controller Version 0.5
OA ver. 2.51
virtual connect 2.10
Bay Device Model Firmware Version
1 HP 1/10Gb VC-Enet Module 2.10
2 HP 1/10Gb VC-Enet Module 2.10
3 HP 4Gb VC-FC Module 1.32
i had before
ilo blabes 1.70
OA 2.32
virtual connect 1.31
iam copying you error messages of VC logs
2009-12-22T10:23:54-06:00 VCETW280200PL vcmd: [FC:enc0:iobay3:4019:Major] FC Module state NO_COMM : Cannot communicate with component
2009-12-22T10:23:55-06:00 VCETW280200PL vcmd: [FC:enc0:iobay3:4004:Info] FC Module power on
2009-12-22T10:24:10-06:00 VCETW280200PL vcmd: [FC:enc0:iobay3:4011:Warning] FC Module state UNKNOWN : Component operational state cannot be determine
the problem is that the VC ethernet can't administer with the VC of FC neither
can with OA manage so I can't manage my SAN
The blades upgrade was with firmwarecd
the currently firmware versions i have
Device Model ProLiant BL460c G1 I15
ROM Version 07/10/2009
ilo model iLO2
iLO Firmware Version 1.77 Apr 23 2009
Power Management Controller Version 0.5
OA ver. 2.51
virtual connect 2.10
Bay Device Model Firmware Version
1 HP 1/10Gb VC-Enet Module 2.10
2 HP 1/10Gb VC-Enet Module 2.10
3 HP 4Gb VC-FC Module 1.32
i had before
ilo blabes 1.70
OA 2.32
virtual connect 1.31
iam copying you error messages of VC logs
2009-12-22T10:23:54-06:00 VCETW280200PL vcmd: [FC:enc0:iobay3:4019:Major] FC Module state NO_COMM : Cannot communicate with component
2009-12-22T10:23:55-06:00 VCETW280200PL vcmd: [FC:enc0:iobay3:4004:Info] FC Module power on
2009-12-22T10:24:10-06:00 VCETW280200PL vcmd: [FC:enc0:iobay3:4011:Warning] FC Module state UNKNOWN : Component operational state cannot be determine
the problem is that the VC ethernet can't administer with the VC of FC neither
can with OA manage so I can't manage my SAN
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2010 05:34 AM
01-05-2010 05:34 AM
Re: problem with virtual connect
Erick,
Couple of things:
First, VC firmware upgrades via the GUI are not very reliable. There is a firmware upgrade utility which is much more reliable.
The utility is called "Virtual Connect Support Utility" (VCSU) and is generally more reliable.
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.
You will see that it disappears from your OA display, and the OA log will record the removal and replacement.
If you wait a couple of minutes, the OA should rediscover the FC module.
This usually works, however there are no guarantees. (However since it is not working right now, what do you have to lose?)
Hope this helps,
Dave.
Couple of things:
First, VC firmware upgrades via the GUI are not very reliable. There is a firmware upgrade utility which is much more reliable.
The utility is called "Virtual Connect Support Utility" (VCSU) and is generally more reliable.
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.
You will see that it disappears from your OA display, and the OA log will record the removal and replacement.
If you wait a couple of minutes, the OA should rediscover the FC module.
This usually works, however there are no guarantees. (However since it is not working right now, what do you have to lose?)
Hope this helps,
Dave.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP