- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual Connect: Not configured for Virtual Conne...
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
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
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
тАО02-25-2008 02:36 PM
тАО02-25-2008 02:36 PM
Virtual Connect: Not configured for Virtual Connect
Anyone else seen this or have a fix?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2008 02:20 PM
тАО02-26-2008 02:20 PM
Re: Virtual Connect: Not configured for Virtual Connect
it may be a sync issue since you mention that servers are functioning correctly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2008 02:29 PM
тАО02-26-2008 02:29 PM
Re: Virtual Connect: Not configured for Virtual Connect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2008 02:33 PM
тАО02-26-2008 02:33 PM
Re: Virtual Connect: Not configured for Virtual Connect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2008 02:38 PM
тАО02-26-2008 02:38 PM
Re: Virtual Connect: Not configured for Virtual Connect
Under Hardware Overview I see the enclosure and all of the status symbols are green checks w/ OK beside them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-26-2008 06:30 PM
тАО02-26-2008 06:30 PM
Re: Virtual Connect: Not configured for Virtual Connect
When I logon to the Virtual connect manager it has a critical error that says "the domain is incapable managing its contained VC components." There is a device named Unknown with a severity Failed and device type of enclosure. All the other statuses are Unknown.
When I connect via SSH and issue a show status command it says every module status is Unknown and "The OA reported an Unknown module state or Virtual Connect has lost communication to the OA".
I thought my stacking links were the problem so I removed those, that didn't help. I have reset the OA and Virtual Connect too.
I called HP and opened a ticket. When they call me back I will post a reply here if we haven't figured it out first.
Scott
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-27-2008 04:39 PM
тАО02-27-2008 04:39 PM
Re: Virtual Connect: Not configured for Virtual Connect
Therefore, I had to take drastic measures; I powered down all the blades and then deleted the Virtual Connect domain. This removed all the Virtual connect configuration and put it back in the default state. I then reconfigured Virtual Connect, imported the enclousre, etc, and all is working again.
Luckily, this was a new install otherwise this would have been highly disruptive.
I would be interested to hear if someone else fixes this without having to reconfigure.
Scott
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-28-2008 12:48 AM
тАО02-28-2008 12:48 AM
Re: Virtual Connect: Not configured for Virtual Connect
I too have had the same problem with the Virtual Connect showing "Not configured for Virtual Connect". Here's what I did to get round the issue.
Having checked all the configuration to be correct, I tried resetting the Virtual Connect Module (be warned all servers will loose connectivity). Once the module came back up, next to all devices was a warning saying comething like 'Server Profile Pending'.
At this point none of the servers had any connectivity. I shut down the servers one by one and then turned them back on again and hey presto, problem solved, profile applied...
Not sure why this has happened and an explanation be good, all I can think is that an earlier change to server profiles has not applied correctly and caused some sort of corrution or other.
Hope this helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2008 11:05 AM - last edited on тАО02-05-2024 07:00 AM by Sunitha_Mod
тАО03-14-2008 11:05 AM - last edited on тАО02-05-2024 07:00 AM by Sunitha_Mod
Re: Virtual Connect: Not configured for Virtual Connect
The Prfile pending issue is fixed in 2.13 OA firmware. This is taken from the download page for 2.13
Fixed an issue where the Onboard Administrator could clear the Virtual Connect parameters from one or more servers following the sequence of events described below. This issue caused a "Profile Pending" condition, detected and reported by Virtual Connect Manager, that required affected servers to be powered off to clear the problem.
The Onboard Administrator is rebooted, power-cycled, or failed over followed by any of these events:
The Virtual Connect Manager (executing on a Virtual Connect Ethernet module in I/O bay 1 or 2) failed over
The Virtual Connect Manager changed IP addresses (due to a change in network connection, DHCP server, or Enclosure Bay IP Addressing setting)
The Virtual Connect Manager was used to change the Virtual Connect Domain Name value
Please update to 2.13 OA FW found here: https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_efec2f7f471345a3a9d1819dcb
[Moderator edit: Updated the link]