Had the same problem after upgrading a HyperV node from R2 to All looks fine on the blades, this way – until a volume is created in Disk Management – exactly like you do – no drive letter, mpio correctly configured. Why did I do that? And we have at least 6 more months of warranty left! Hope that explains it a bit more Did you create this in Hyper-V Manager?

Uploader: Gardazuru
Date Added: 18 January 2015
File Size: 18.90 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 70769
Price: Free* [*Free Regsitration Required]

Office Office Exchange Server.

You can just email me at info georgealmeida. This is not relative to the iSCSI configuration but I thought it was important to understand what you are viewing in the image below. How I wish that I had your issue! Hi Spudney, Glad to hear that you have resolved the issue and thanks for sharing your solution in the forum. Did you create this in Hyper-V Manager?

Configure iSCSI on Windows Server 2012 R2

Wednesday, March mpko, 2: Take a read through the MSA best practices guide. I want to ask how can I directly attached the MSA to the server.

However, I’m confused as to what HBA you would use on one of your blades. I fully admit that it is overkill but I had the NICs so why not? The first thing you will do when you are ready to configure the MSA msx to run the Configuration Wizard. Monday, July 25, 8: Spudney, thanks for your response! By continuing to browse this site, you agree to this use.


Best of luck Derrick. You say you’ve created a VM on Blade1.

Thursday, January 9, 1: If the CSV isn’t created in Failover Cluster Manager, then the 2nd Blade will not see the file properly at all – it would suspect corruption of the disk. Good luck and please let me know if you have any other questions.

Can I clarify one thing please? So what are we looking at? Your time and efforts are highly appreciated. Edited by Nostra systems Monday, March 10, 9: Sign up using Email and Password. The W Boxes are as per HP’s recommendations.

Server R2 – HP P G3 MSA – MPIO

Edited by Fleetinfo Saturday, March 15, 3: And we have at least 6 more months of warranty left! I’ve tried, many times, to delete the virtual volume and re-map it to the server but it is always the same. Hi Derrick Your setup is pretty much the same as mine except you have a BladeCentre setup and SAS switches in between where I have direct connections between the HBAs and controllors, is everything uptodate firmware wise and driver wise?


Sorry for the delay in getting back in touch re this solution. Glad to hear that you have resolved the issue and thanks for sharing your solution in the forum. We’ve only got five months of HP support for the P anyway, so we gave up on them and just went with what we have. Yes, it is OK to do this but it is probably overkill. Resources for IT Professionals. As for teaming the storage iscsi NICs.

Rather disconcertingly, although the Pm is listed in the HP Technical white paper: