- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Restart of OA blows up Virtual Connect
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
тАО04-15-2009 12:51 PM
тАО04-15-2009 12:51 PM
Restart of OA blows up Virtual Connect
Whenever I reset my OA my VC ethernet gets kicked off the network for 30 seconds and sometimes my VC San gets disconnected. The only way to get the SAN back is to restart all the VC modules.
This is not cool.. anyone else ever have this happen? I have two OA's
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-16-2009 12:09 AM
тАО04-16-2009 12:09 AM
Re: Restart of OA blows up Virtual Connect
Do you have compatible firmware levels for your OA, BIOS, ILO and VC Eth/SAN
http://h18004.www1.hp.com/products/blades/components/c-class.html#tab3_content
Check Compatability TAB!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-16-2009 11:15 AM
тАО04-16-2009 11:15 AM
Re: Restart of OA blows up Virtual Connect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-16-2009 03:04 PM
тАО04-16-2009 03:04 PM
Re: Restart of OA blows up Virtual Connect
I upgraded all blades to 11/08, then upgraded VC with auto update to 2.01. I didnt loose any servers as my TS session stayed up but my event log spammed with outages. I was testing a few things with teaming and updates.
I then upgraded the OA's to 2.41 and lost the VC manager totally and couldnt ping any of the VC's either. I had to reset everything.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-17-2009 10:23 AM
тАО04-17-2009 10:23 AM
Re: Restart of OA blows up Virtual Connect
Out of curiosity, what method are you using to reset the OA?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-17-2009 10:57 AM
тАО04-17-2009 10:57 AM
Re: Restart of OA blows up Virtual Connect
When I reset the OA i just hit the virtual reset button
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2009 07:12 AM
тАО04-20-2009 07:12 AM
Re: Restart of OA blows up Virtual Connect
I have since set this registry setting to help alleviate brief SAN outages:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk]
"TimeOutValue"=dword:00000078
Have not had the oppertunity to verify this helps yet.
Nelson
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-30-2009 03:25 AM
тАО04-30-2009 03:25 AM
Re: Restart of OA blows up Virtual Connect
We can pretty much repeat on demand by simply failing active to standby.
Only difference is the resulting problem.
So far we have seen -
New active OA fails to identify the first blade in the enclosure (comes up unknown and can only be brought back to life with a reset from the command line). Other blades fine.
Loss of san (as described above - reset all fc cards to fix)
Loss of OA - that's to say the active to standby fails to complete. Only way to resolve is to reseat original active OA.
We are looking into possible problems being network related as the later issue seems to flood the network.
Calls being raised with HP, will post results.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-30-2009 04:08 AM
тАО04-30-2009 04:08 AM
Re: Restart of OA blows up Virtual Connect
That fixed my issues. After I did this I was unable to reproduce the problems.
I also lost SAN and caused a network flood.
I had a case open with support but a post sales engineer actually suggested I do this. I told support what I had to do to fix the issue.
During the network flood my entire enclosure was powered down for a while. This could have also played a part in my problems being fixed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-30-2009 04:34 AM
тАО04-30-2009 04:34 AM
Re: Restart of OA blows up Virtual Connect
Will give it a try. There's nowt in the 2.02 fw note to suggest a fix for this but there you go.
Been testing all morning and am not convinced the san is actually disappearing. Servers that are boot from san don't seem to be affected.
Connectivity through the OA and VC manager is obviously hampered by the network flooding across the management lan. In all but one of our enclosures this recovers after a while.