- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Virtual connect Errors
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
05-27-2011 08:41 AM
05-27-2011 08:41 AM
Virtual connect Errors
Further looking at the Hardware Overview, Interconnect Bay there are (?) next to HP-B Series 8/12c San Switch Bladesystem c-class.
next clicking on the Device mentioned above Overall Status reports Unknown and the Hardware status reports Unknown.
There are no changes made to the C7000 except adding two more blades.
What could have caused the issues and what needs to be done clear the Alerts...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2011 01:15 PM
05-28-2011 01:15 PM
Re: Virtual connect Errors
If my post was useful, clik on my KUDOS! "White Star" !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2011 10:43 AM
05-31-2011 10:43 AM
Re: Virtual connect Errors
It would probably help if you could cut and paste a section of the VC Error Log into notepad (or similar), and post it here.
As pointed out by Bart, these SAN switch modules are NOT Virtual Connect and cannot be configured via VC. You can still use them, but you must configure them exactly as you would an external SAN switch. (and note, the REAL HBA port WWIDs will by used by the storage subsystem to present storage.)
You will not be able to take advantage of the Virtual WWID's used by VC.
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2011 08:54 AM
12-09-2011 08:54 AM
Re: Virtual connect Errors
I am experiencing this issue, also, and would like to see a solution. I understand the Brocade SAN switches are not managed by VCM but I'd like to see the error go away if only for a clean Domain Status.
I have other Brocade SAN modules in the same VC domain that show a hardware status of OK and therefore and Overall Status of OK. I have one Brocade SAN module with the Hardware Status of Unknown.
Any help in determining how VCM detects the hardware status of modules and changing the Unknown status to OK would be much appreciated.
I'm running v3.18 (recently upgraded from 3.15).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2011 09:46 PM
12-18-2011 09:46 PM