GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Windows 2000 Adv cluster on MSA 1000. Strange prob...
HPE EVA Storage
1855136
Members
5219
Online
104109
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
Discussions
Forums
Discussions
back
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
12-11-2003 07:26 PM
12-11-2003 07:26 PM
Windows 2000 Adv cluster on MSA 1000. Strange problem
HP MSA 1000. Two cluster nodes. Only two cluster nodes are attached to this device.
The problem is that:
1. Sometimes, nodeB will hang. Windows 2000 Kernel mode works. Therefore, the failover doesn't happen to nodeA.
2. We have no way, but reset the computer.
3. After we reset the computer, nodeA tried to take the SAP group on the nodeB. During the failover stage, all the disks are not connected. In the cluster log, error 1167 is reported.
We have to reboot nodeA again.
I have asked MS and HP to check this problem. MS thought that it was a SAN configuration or hardware issue. HP checked the hardware. They said no problem. This issue has happened several times. I don't want to solve NodeB hang issue. Cluster should be able to provide fault-toleance abliity. How do you think this problem? Can we enable the log at the switch level to check? I suspect that the switch embeded in MSA 1000 is reset when this behavior occurs.
In the event log on nodeA, we can see the event 9, 11, and 15 when nodeA tried to take the group SAP.
Thanks,
Sam
The problem is that:
1. Sometimes, nodeB will hang. Windows 2000 Kernel mode works. Therefore, the failover doesn't happen to nodeA.
2. We have no way, but reset the computer.
3. After we reset the computer, nodeA tried to take the SAP group on the nodeB. During the failover stage, all the disks are not connected. In the cluster log, error 1167 is reported.
We have to reboot nodeA again.
I have asked MS and HP to check this problem. MS thought that it was a SAN configuration or hardware issue. HP checked the hardware. They said no problem. This issue has happened several times. I don't want to solve NodeB hang issue. Cluster should be able to provide fault-toleance abliity. How do you think this problem? Can we enable the log at the switch level to check? I suspect that the switch embeded in MSA 1000 is reset when this behavior occurs.
In the event log on nodeA, we can see the event 9, 11, and 15 when nodeA tried to take the group SAP.
Thanks,
Sam
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2003 05:01 AM
12-17-2003 05:01 AM
Re: Windows 2000 Adv cluster on MSA 1000. Strange problem
Check you dependencies and make sure network name and storage sets are correct. Check you your perferred owner as well.. You need to check each resource don't just look at the groups...
Yabba Dabba Doo
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP