Hp p2000 g3 windows 2012
Вопрос
I just have a quick query, I know this isnt a HP forum but my kit is pretty much widely used in the industry, can someone please let me know if there is a DSM for Server 2012 R2 MPIO for use with a HP P2000 G3 SAS Storgae appliance?
HP have said its built into to Windows Server 2012 R2 via adding the feature MPIO as normal and then use the windows «add sas support» within MPIO then reboot, is this true as I have seen a P2000 G3 SAS with a DSM listed as » HP P2000 G3″ within MPIO on Server 2008 R2 so a manufacturer one must exist which I presume would work under Server 2012 R2, as when you add the windows native MPIO support for SAS it shows up as MSF******** etc not HP P2000 G3 with MPIO at the top of the DSM list on the first tab
Anyone know the answer to this?
Ответы
Hi Guys I found the answer myself, hope this helps others!
** Just so you know
HP recommends that you use the Windows Server «DSM» for a HP P2000 G3 for Server 2008/R2 & 2012/R2 MPIO setup (Source: direct from HP support)
The vendor specific DSM was only ever required to be used with Server 2003/R2 as its built into Windows Server versions of later releases.
To configure MPIO with SAS connectivity using Server 2012 R2 and a HP P2000 G3 SAS SAN
Configure SAN to present/map LUN1 to both HBA’s in host (Read/Write) through web browser based “Storage Management Utility” (connect to IP of storage controller from host) (Firefox is best to use)
Then on Server 2012 R2 Host:
1. Connect up your storage to your Host HBA’s using your SAS cables
2. Test and see in Disk Management that you can see two paths (2 separate listings for the LUN/Disk) to the LUN1
3. Add MPIO feature through Server Manager and reboot
4. After reboot run this command from an elevated command prompt «mpclaim -n -i -a» then reboot again (This grabs both paths and combines them into one redundant path)
5. Now after the second reboot check Disk Management again and you will notice that only one path/disk is listed offline
6. Bring disk online and initialise and create volume (Obviously only do this once on Host1 if its a clustered setup)
Все ответы
Hi Guys I found the answer myself, hope this helps others!
** Just so you know
HP recommends that you use the Windows Server «DSM» for a HP P2000 G3 for Server 2008/R2 & 2012/R2 MPIO setup (Source: direct from HP support)
The vendor specific DSM was only ever required to be used with Server 2003/R2 as its built into Windows Server versions of later releases.
To configure MPIO with SAS connectivity using Server 2012 R2 and a HP P2000 G3 SAS SAN
Configure SAN to present/map LUN1 to both HBA’s in host (Read/Write) through web browser based “Storage Management Utility” (connect to IP of storage controller from host) (Firefox is best to use)
Then on Server 2012 R2 Host:
1. Connect up your storage to your Host HBA’s using your SAS cables
2. Test and see in Disk Management that you can see two paths (2 separate listings for the LUN/Disk) to the LUN1
3. Add MPIO feature through Server Manager and reboot
4. After reboot run this command from an elevated command prompt «mpclaim -n -i -a» then reboot again (This grabs both paths and combines them into one redundant path)
5. Now after the second reboot check Disk Management again and you will notice that only one path/disk is listed offline
6. Bring disk online and initialise and create volume (Obviously only do this once on Host1 if its a clustered setup)
Glad to hear that you have resolved the issue and thanks for sharing your solution in the forum. This will help others who face the same scenario resolve the issue quickly. Your time and efforts are highly appreciated.
Hi, Spudney / Justin.
I’ve got the same set up as the OP (storage wise), only I connect the storage via 2x HP 6Gb SAS BL Switches in Active/Passive mode. All mapped correctly in the SMU and a separate zone in the BL Switch management console.
Whilst I can see disks appearing in Disk Manager, if I try to map the LUN to the 2nd blade (they are identical BL460c G7s) I end up with one of the hosts returning a BSOD circular restart , and Bad Pool Header issues etc. It really is a pain — despite working with HP for nearly 6 months, we’re no nearer fixing it. I was beginning to think that it would never work — but when I saw your post, I had a resurgence of optimism — I’m not the only one with a P2000 G3 SAS and wanting to use Hyper-V / MS Failover Clustering! Thanks for giving me a bit of hope!
With kind regards
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?
When you say you map the lun to the second blade what exactly do u mean?
Hiya, Spudney.
Sorry about the delay — was jumping through HP hoops on Thursday & Friday. :o(
You’re correct — it is pretty much the same. Everything is bang up to date, firmware wise (well, it’s all dated February 2014, but that’s up to date in this game!)
When you map LUNs in the P2000 SMU, using the DA method you use, you will put a tick in the box for particular Volume, name it with the LUN id (e.g. in my case I have 3 volumes, LUN 20, 21 & 22 — for CSVWitness, CSV1 & CSV2 volumes) — You would allocate which of the ports would serve these LUNs (A1,A2,B1,B2 for example) — with a BL Switch setup like mine, you use the BL 6G SAS Switch Management Console to accomplish the same thing, creating Blade Zone Groups, allocating blades as members etc — originally we had all the blade ports as members of the same BLZoneGroup, since all machines were in a larger cluster using W2008R2 — that didn’t give us what we needed, however.
The two blades are now in their own Zone Group, and they are connected to Ports A4,B4 on the SMU. — this is pretty much the same as you doing the direct mapping.
In order to search for the disks on one blade, we actually create an explicit mapping via 2 paths for that volume (LUN) in the SMU — on the Blade’s OS then, we use Disk Management to ensure this is visible. Then we create the mapping to the second server in the same way.
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.
Unfortunately, this never survives a reboot — sometimes not even that long. The BSOD cycle starts with BAD_POOL_HEADER & «Unable to write to read only memory» (issues). Remove the explicit mapping ticks in the SMU, and eventually the server will start ok.
Really gets frustrating — the HP 2nd Line Techs and their HP MS Specialists are trawling through HPS reports & Kernel Dumps now — this has dragged on for months with no success. I’m just happier knowing someone who has a similar set up.
Hp p2000 g3 windows 2012
Frage
I just have a quick query, I know this isnt a HP forum but my kit is pretty much widely used in the industry, can someone please let me know if there is a DSM for Server 2012 R2 MPIO for use with a HP P2000 G3 SAS Storgae appliance?
HP have said its built into to Windows Server 2012 R2 via adding the feature MPIO as normal and then use the windows «add sas support» within MPIO then reboot, is this true as I have seen a P2000 G3 SAS with a DSM listed as » HP P2000 G3″ within MPIO on Server 2008 R2 so a manufacturer one must exist which I presume would work under Server 2012 R2, as when you add the windows native MPIO support for SAS it shows up as MSF******** etc not HP P2000 G3 with MPIO at the top of the DSM list on the first tab
Anyone know the answer to this?
Antworten
Hi Guys I found the answer myself, hope this helps others!
** Just so you know
HP recommends that you use the Windows Server «DSM» for a HP P2000 G3 for Server 2008/R2 & 2012/R2 MPIO setup (Source: direct from HP support)
The vendor specific DSM was only ever required to be used with Server 2003/R2 as its built into Windows Server versions of later releases.
To configure MPIO with SAS connectivity using Server 2012 R2 and a HP P2000 G3 SAS SAN
Configure SAN to present/map LUN1 to both HBA’s in host (Read/Write) through web browser based “Storage Management Utility” (connect to IP of storage controller from host) (Firefox is best to use)
Then on Server 2012 R2 Host:
1. Connect up your storage to your Host HBA’s using your SAS cables
2. Test and see in Disk Management that you can see two paths (2 separate listings for the LUN/Disk) to the LUN1
3. Add MPIO feature through Server Manager and reboot
4. After reboot run this command from an elevated command prompt «mpclaim -n -i -a» then reboot again (This grabs both paths and combines them into one redundant path)
5. Now after the second reboot check Disk Management again and you will notice that only one path/disk is listed offline
6. Bring disk online and initialise and create volume (Obviously only do this once on Host1 if its a clustered setup)
Alle Antworten
Hi Guys I found the answer myself, hope this helps others!
** Just so you know
HP recommends that you use the Windows Server «DSM» for a HP P2000 G3 for Server 2008/R2 & 2012/R2 MPIO setup (Source: direct from HP support)
The vendor specific DSM was only ever required to be used with Server 2003/R2 as its built into Windows Server versions of later releases.
To configure MPIO with SAS connectivity using Server 2012 R2 and a HP P2000 G3 SAS SAN
Configure SAN to present/map LUN1 to both HBA’s in host (Read/Write) through web browser based “Storage Management Utility” (connect to IP of storage controller from host) (Firefox is best to use)
Then on Server 2012 R2 Host:
1. Connect up your storage to your Host HBA’s using your SAS cables
2. Test and see in Disk Management that you can see two paths (2 separate listings for the LUN/Disk) to the LUN1
3. Add MPIO feature through Server Manager and reboot
4. After reboot run this command from an elevated command prompt «mpclaim -n -i -a» then reboot again (This grabs both paths and combines them into one redundant path)
5. Now after the second reboot check Disk Management again and you will notice that only one path/disk is listed offline
6. Bring disk online and initialise and create volume (Obviously only do this once on Host1 if its a clustered setup)
Glad to hear that you have resolved the issue and thanks for sharing your solution in the forum. This will help others who face the same scenario resolve the issue quickly. Your time and efforts are highly appreciated.
Hi, Spudney / Justin.
I’ve got the same set up as the OP (storage wise), only I connect the storage via 2x HP 6Gb SAS BL Switches in Active/Passive mode. All mapped correctly in the SMU and a separate zone in the BL Switch management console.
Whilst I can see disks appearing in Disk Manager, if I try to map the LUN to the 2nd blade (they are identical BL460c G7s) I end up with one of the hosts returning a BSOD circular restart , and Bad Pool Header issues etc. It really is a pain — despite working with HP for nearly 6 months, we’re no nearer fixing it. I was beginning to think that it would never work — but when I saw your post, I had a resurgence of optimism — I’m not the only one with a P2000 G3 SAS and wanting to use Hyper-V / MS Failover Clustering! Thanks for giving me a bit of hope!
With kind regards
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?
When you say you map the lun to the second blade what exactly do u mean?
Hiya, Spudney.
Sorry about the delay — was jumping through HP hoops on Thursday & Friday. :o(
You’re correct — it is pretty much the same. Everything is bang up to date, firmware wise (well, it’s all dated February 2014, but that’s up to date in this game!)
When you map LUNs in the P2000 SMU, using the DA method you use, you will put a tick in the box for particular Volume, name it with the LUN id (e.g. in my case I have 3 volumes, LUN 20, 21 & 22 — for CSVWitness, CSV1 & CSV2 volumes) — You would allocate which of the ports would serve these LUNs (A1,A2,B1,B2 for example) — with a BL Switch setup like mine, you use the BL 6G SAS Switch Management Console to accomplish the same thing, creating Blade Zone Groups, allocating blades as members etc — originally we had all the blade ports as members of the same BLZoneGroup, since all machines were in a larger cluster using W2008R2 — that didn’t give us what we needed, however.
The two blades are now in their own Zone Group, and they are connected to Ports A4,B4 on the SMU. — this is pretty much the same as you doing the direct mapping.
In order to search for the disks on one blade, we actually create an explicit mapping via 2 paths for that volume (LUN) in the SMU — on the Blade’s OS then, we use Disk Management to ensure this is visible. Then we create the mapping to the second server in the same way.
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.
Unfortunately, this never survives a reboot — sometimes not even that long. The BSOD cycle starts with BAD_POOL_HEADER & «Unable to write to read only memory» (issues). Remove the explicit mapping ticks in the SMU, and eventually the server will start ok.
Really gets frustrating — the HP 2nd Line Techs and their HP MS Specialists are trawling through HPS reports & Kernel Dumps now — this has dragged on for months with no success. I’m just happier knowing someone who has a similar set up.
