If you look in MDSM at the host mappings tab of the virtual disk it will list out the host that can access the virtual disk. if you need to change it so that you can add a second host to access it then you will need to follow the steps listed on page 56 of the Administrator guide. http://downloads.dell.com/manuals/common/md32xx_md36xx_administrator%20guide_en%20us.pdf
Please let us know if you have any other questions.
- offline the MD3k disks in disk management on both servers
- remove the disks from the hosts in MDSM
- rescan device manager to make the servers recognize the disks are no longer there
- rescan disk management to ensure the OS doesn't still try to hold on to the disks
- if rescanning device manager and/or disk management locks up said application, consider rebooting the server(s)
- use MDSM to move the servers into the host group and map the disks to the host group
- don't forget to also create/pick a Quorum disks for the hyper-v cluster (unless you're going to use a share for the Quorum) and assign this to the host group as well
- have both servers rescan device manager to find the disks
- have both servers rescan disk management to find the disks
- NEVER bring the disks online on both servers at the same time as this will corrupt the data/file system (may not happen immediately, but it could be seconds, minutes, hours or days, but it will corrupt to have a SAN shared disks in Windows when the disk isn't a clustered resource.
- I usually bring the disks online on one server, verify all looks ok, then offline them again, and bring them online on the other server to verify it can see them as well. Then you build your cluster and add these disks as cluster resources
DELL-Sam L
Moderator
•
7.8K Posts
0
December 6th, 2017 08:00
Hello kshingler1,
If you look in MDSM at the host mappings tab of the virtual disk it will list out the host that can access the virtual disk. if you need to change it so that you can add a second host to access it then you will need to follow the steps listed on page 56 of the Administrator guide. http://downloads.dell.com/manuals/common/md32xx_md36xx_administrator%20guide_en%20us.pdf
Please let us know if you have any other questions.
Dev Mgr
4 Operator
•
9.3K Posts
0
December 6th, 2017 16:00
In short:
- Create a host group
- add both hyper-v hosts to the host group
- map the LUNs/virtual disks to the host group (not the individual hosts)
kshingler1
2 Posts
0
December 7th, 2017 13:00
That makes sense. Do I need to drop all connections before I make those changes?
I'm going to create a new volume to test from each host.
Dev Mgr
4 Operator
•
9.3K Posts
0
December 9th, 2017 19:00
Your best bet is these steps:
- offline the MD3k disks in disk management on both servers
- remove the disks from the hosts in MDSM
- rescan device manager to make the servers recognize the disks are no longer there
- rescan disk management to ensure the OS doesn't still try to hold on to the disks
- if rescanning device manager and/or disk management locks up said application, consider rebooting the server(s)
- use MDSM to move the servers into the host group and map the disks to the host group
- don't forget to also create/pick a Quorum disks for the hyper-v cluster (unless you're going to use a share for the Quorum) and assign this to the host group as well
- have both servers rescan device manager to find the disks
- have both servers rescan disk management to find the disks
- NEVER bring the disks online on both servers at the same time as this will corrupt the data/file system (may not happen immediately, but it could be seconds, minutes, hours or days, but it will corrupt to have a SAN shared disks in Windows when the disk isn't a clustered resource.
- I usually bring the disks online on one server, verify all looks ok, then offline them again, and bring them online on the other server to verify it can see them as well. Then you build your cluster and add these disks as cluster resources