- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Virtual Connect Domain failure
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-24-2011 11:42 AM
тАО02-24-2011 11:42 AM
Re: Virtual Connect Domain failure
The first thing I'd like to do is rule out an issue that can cause VCM to display no communication with Virtual Connect modules that occurs when DNS is enabled in the Onboard Administrtor under Enclosure Settings > Enclosure Bay IP Addressing > Interconnect Bays. If EBIPA is used to assign an IP address, make sure there is no DNS information entered. If there is, remove it and update by hitting the Apply button at the lower right. (This is if you use EBIPA to assign IP address. If you use an external DHCP server, then we would want to remove the DNS info there.)
The symptoms for the DNS issue is VCM reporting no communication for one or more VC modules and stacking links showing failed.
After i replied with this fixed it i got this in return.
Glad to hear that took care of it. There is a customer advisory on this issue, c02720395, but I don't believe it's availble on our website yet. There will be a future firmware fix, but for now the workaround is to remove the DNS information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2011 12:26 AM
тАО03-02-2011 12:26 AM
Re: Virtual Connect Domain failure
This DNS issue as described in the document c02720395 is resolved in VC FW 3.17 that is our next targeted release of VC FW.
Cheers, Jeroen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2011 08:11 AM
тАО03-02-2011 08:11 AM
Re: Virtual Connect Domain failure
We've what HP's advisory has asked and cleared the DNS records for our interconnect cards IPs. We run a DHCP not EBIPA. Also we temporarily set DNS not to update the IP scope. We are still experiencing the No communication error. Has anyone tried something else that resolved this issue? I am new to blade systems and am even having a hard time getting an HP engineer to resolve the issue.
Any advise or a "try this it worked for me" would be greatly appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2011 03:10 PM
тАО03-02-2011 03:10 PM
Re: Virtual Connect Domain failure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2011 03:18 PM
тАО03-02-2011 03:18 PM
Re: Virtual Connect Domain failure
Since you use DHCP, this might not help, but I would do it anyway.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2011 04:23 PM
тАО03-02-2011 04:23 PM
Re: Virtual Connect Domain failure
Is there a release date for VC FW 3.17?
Anyones input is greatly appreciated.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2011 03:57 AM
тАО03-03-2011 03:57 AM
Re: Virtual Connect Domain failure
... looking forward to weird new bugs in 3.17..........
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2011 10:58 AM
тАО03-04-2011 10:58 AM
Re: Virtual Connect Domain failure
I have the exact same problem, brand new C7000 with two VC Eth modules.
All latest FW.
Have also tried to remove DNS entry, without any luck!
We have not put the enclousure in production yet, so I also tried to delete the domain and recreate it, still not work.
Also tried to flush the FW on VC again.
I have open a case with HP, but the response arent wery quick, the only solution from HP so far are the workaround with DNS...
Erik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2011 11:05 AM
тАО03-04-2011 11:05 AM
Re: Virtual Connect Domain failure
We don't have a formal release date yet although we are working on updated schedule to push it out within a month from now or sooner.
Erik, feel free to post your CaseID so I can lookup the status for your case.
A updated Customer Advisory with the same URL: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c02720395 should be available very soon.
Cheers, Jeroen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2011 11:12 AM
тАО03-04-2011 11:12 AM
Re: Virtual Connect Domain failure
Thanck you for quick response!
My case number with HP are: 4626776895.
Thancks