Unsolved
This post is more than 5 years old
16 Posts
0
19087
March 19th, 2008 19:00
Modular disk Storage Manager not detecting all connected hosts
I have a pair of server (PE6950) each with 2 SAS controllers in them that I'm trying to setup as a cluster. I've set up the disks in my MD3000 as I want them, and now I'm trying to setup 'Host Access' in MDSM.
MDSM sees one of the hosts, and all 4 HBA ports in it correctly, but does NOT see the other host at all.
Device Manager reports both boxes as using SAS 5/E driver version 1.24.4.0, dated 10/08/07. I'm kinda stumped as to why MDSM doesn't see the 'missing' host. I've tried MDSM from both an In Band, and an Out of Band connection with the same results.
Checking from the card BIOS, both cards appear to see the MD3000 -
Can anyone offer any troubleshooting hints ?



Dev Mgr
4 Operator
•
9.3K Posts
0
March 20th, 2008 11:00
This isn't possible I suspect.
In a cluster SAS cabling should be:
- server 1 to left side controller in-0 and right side controller in-0 (whether this is from 2 HBAs (each just using 1 port) or both ports on a single HBA doesn't matter)
- server 2 to left side controller in-1 and right side controller in-1
- the out ports are for adding an MD1000 for extra drive slots
So MDSM should never see 4 HBA ports on a single server (unless you're only connecting a single server and are using all 4 ports for that one server).
I'd suggest:
- go to modify and then modify topology
- remove the host you see
- restart all MDSM related services (or just reboot the server) on both servers
- go to configure and configure host automatically
- let it add both hosts (you can use "view details" to verify it sees 2 WorldWideIdentifiers (WWI's/look like MAC addresses) per host)
- modify both host to set them for Windows clustering mode
- now create a hostgroup and put only a single host in it (the host you want to start your cluster on)
- assign virtual disks to the host group
- let the server rescan for hardware changes in device manager
- go to disk management and verify you can see all the disks
- partition and format the disks if you haven't already (drive letter Q for the Quorum disk (1GB is fine for this))
- start up the cluster wizard and set up the 1-node cluster
- now add the 2nd host to the hostgroup (under modify topology)
- let this host scan for hardware changes in the device manager
- verify the host can see the disks (they'll be unreadable, but that's because the cluster already has a lock on the disks, so that's expected and normal)
- in the cluster admin add this 2nd node (select to run the minimal check as it sometimes stops you from joining due to not being able to see all disks, which is due to the cluster blocking access to the disks (on minimal you'll get a yellow bang about skipping drive letter collision testing, but assuming you made sure there were no conflicting drive letters on the 2 servers that's fine))
Dell-Jeff G
156 Posts
0
March 20th, 2008 12:00
You may also want to reference Dell's cluster docs for the MD3000 at this link<ADMIN NOTE: Broken link has been removed from this post by Dell>.