- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Win2K AS Cluster - Shared Disk Access Problem
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
тАО12-14-2000 04:00 PM
тАО12-14-2000 04:00 PM
Win2K AS Cluster - Shared Disk Access Problem
When both nodes are finally up and running, everything seems to be OK with the cluster. Have I missed a particular hardware configuration step specific to the CL380 / CL1850 or perhaps I've missed something during the config of W2K AS and Cluster Services?
Please...any help or suggestions...
--Ryan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-17-2000 04:00 PM
тАО12-17-2000 04:00 PM
Re: Win2K AS Cluster - Shared Disk Access Problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-01-2001 04:00 PM
тАО01-01-2001 04:00 PM
Re: Win2K AS Cluster - Shared Disk Access Problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-01-2001 04:00 PM
тАО01-01-2001 04:00 PM
Re: Win2K AS Cluster - Shared Disk Access Problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-02-2001 04:00 PM
тАО01-02-2001 04:00 PM
Re: Win2K AS Cluster - Shared Disk Access Problem
1) Run SmartStart on Node 1 to configure it and load the System Configuration Utility,
2) Load Windows NT Enterprise Edition, Service Pack 3, and the Support Software for Windows NT a.k.a. NT SSD.
3) Install the CR3500 Configuration Utility into the new Windows NT installation from the [CD-ROM drive letter]:\CR3500\ENG directory of the SmartStart CD.
4) Run the CR3500 Configuration Utility from the Compaq System Tools folder and configure the array as desired.
5) Run Disk Administrator, create volumes out of the logical drives, and be sure to format them NTFS and assign drive letters to them. NTFS is the only file system supported for the shared storage.
6) Install and configure Microsoft Cluster Server.
For Node 2:
1) Run SmartStart on Node 1 to configure it and load the System Configuration Utility.
2) On this node, change the Ultra2 SCSI Adapter ID from ID 7 to ID 6
3) Load Windows NT Enterprise Edition, Service Pack 3, and the Support Software for Windows NT a.k.a. NT SSD
4)Run Disk Administrator to set the drive letter to match the drive letter for the shared storage area which was created on Node 1
5) Install and configure Microsoft Cluster Server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2001 04:00 PM
тАО01-11-2001 04:00 PM
Re: Win2K AS Cluster - Shared Disk Access Problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-15-2001 04:00 PM
тАО01-15-2001 04:00 PM
Re: Win2K AS Cluster - Shared Disk Access Problem
I tried to follow the Instructions supplied by Compaq for setting up Cluster services for Windows 2000 on the Cl380 but as I have found and obviously some of you this doesn't actually work as stated.
I have set the SCSI IDs on both nodes to be different.
Has anyone actually resolved the issue?
I'm still trying to figure out how to get it working but so far no luck.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-16-2001 04:00 PM
тАО01-16-2001 04:00 PM
Re: Win2K AS Cluster - Shared Disk Access Problem
It took 68 steps to get this working as it should ..
Grace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-04-2001 04:00 PM
тАО02-04-2001 04:00 PM
Re: Win2K AS Cluster - Shared Disk Access Problem
So we just took it out and what a surprise the Node2 was working fine. So we created the cluster and so on...
Is it an option ??
Henning
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2001 04:00 PM
тАО04-04-2001 04:00 PM
Re: Win2K AS Cluster - Shared Disk Access Problem
I've setup 3 of these clusters now, with Win2K SP1, and had no problems. Only thing (as others have mentioned) is to make sure the SCSI ID's are setup correctly on your nodes... setup one of them to connect to the array via ID 7, and the other node to connect via ID 6.
Since the smartstart setup goes by so quick, you may forget to do this on the second one before it gets into the Win2K detection phase... so what I do is set the ID to 6 on the first node I setup, so then I don't have to worry about changing it on the second node, which I just leave at id 7.
Never had a problem doing it that way.