- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- Re: Lefthand upgrade 8.5>9.0 results in Windows 20...
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
08-25-2011 01:04 AM
08-25-2011 01:04 AM
I`ve have done a upgrade of Lefthand SanIq 8.5 > 9.0
During this upgrade several windows 2008r cluster nodes randomly crashed.
After booting the HP DSM favorite targets ip-adresse where changed into other NIC adresses(LAN and/or Cluster NIC)
Anyone have had the same problem?
I have followed the best practise guide of HP with configuringHP DSM on my servers. Are there additional windows settings to do?
How can I prevent mix-up of iscsi favorites and prevent reboot/crash of windows 2008 cluster nodes during future upgrades.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2011 12:25 AM
08-30-2011 12:25 AM
Re: Lefthand upgrade 8.5>9.0 results in Windows 2008r2 cluster node crashes
I have posted a support case for this strange issue at HP Storage support.
They have ellevated the case already....
to be continued.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2011 04:17 AM
09-08-2011 04:17 AM
SolutionHi there,
Hp advises to bring the 12 node cluster back top 10 nodes and applie the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
MaxRequestHoldTime too 600 seconds(eq 10 minutes)
See also the time out doc from HP, this is an old document and is still usable also for windows 2008 R2
..
This is the reaction of L2 HP:
Below are the analysis from the L-2 engineer
- No errors reported during the upgrade to point any hardware failures
- I see volumes going unavailable during the time of upgrade. This is important as it can cause Nodes crash. I suspect initiator and disk timeout settings may not be appropriate from hosts. Customer to confirm this
- The nodes reboot time is too close 8-10 minutes gap so I suspect there would be occasions where more than 1 node were not synced and led to this. Recommendation is to have fewer nodes in cluster , 12 nodes are present in this cluster where issue was reported , I would recommend less than 10 nodes if feasible . NOTE : Customer did not report issue with other clusters with fewer nodes
- The Best practices guide clearly tells to bring nodes offline during upgrade or atleast have minimal work load. I suspect the load wouldn’t be very less as it was Thursday morning .