Multi-pathing in 2016 Server with HP6000

-
Multi-pathing in 2016 Server with HP6000

I came across a situation today where the software vendor recommend Server 2016 for one of their software upgrade projects.  As the SysAdmin I had to setup the storage fabric.  After getting the SAN zone configured on the Nexus 5K's and presented a test lun from the HP6000 array to the new 2016 server.  Once this was done, the server seen 8 drives of the same size.  OK, no biggie I just gotta grab the HPE MPIO DSM Manager software and away we will go.  However, I quickly discovered that there is no software developed for 2016, nor is 2016 on the compatibility list.

So I was able to take my first adventure down the path of Windows 2016's native MPIO software.  I realize the mpclaim.exe software came out much earlier but this was the first time I've had to personally use it.

So to get the system to multipath, I found that it was pretty simple with this tool.

 First see if the system detects that a multipath device can be found.

mpclaim.exe -e

"Target H/W Identifier   "   Bus Type     MPIO-ed      ALUA Support
-------------------------------------------------------------------------------
"HP      HSV400          "   Fibre        YES          ALUA Not Supported


Next you can simply run the following command to have it attempt to auto configure the devices for multipathing.  In my case it worked w/o a flaw.

mpclaim.exe -r -i -a

(-r = reboot, -i = add multipath, -a add devices)


Next you can set the load balancing policy with the following command.

mpclaim.exe -l -t "HP      HSV400          " 2

(-l = loadbalancing, -t= target device, "2" is the loadbalacing option for RR)


Show the results with the following command:

mpclaim.exe -s -t

"Target H/W Identifier   "   LB Policy
-------------------------------------------------------------------------------
"HP      HSV400          "   RR


Comments

Post a Comment

Popular posts from this blog

Integrate Choco with SCCM

-
Image
Integrating Choco with SCCM Choco is well known and recently I've written on how to integrate choco with puppet as the control mechanism.  Today, I've explored how to do this with SCCM configuration manager.  This article assumes you have a working SCCM environment.  My lab environment was set up using Oracle's personal use virtual box and evaluation software provided by Microsoft's eval center and a Fedora host system.  (Let me know if you would like to know more about my setup) The reason I'm writing about this is to keep 3rd party software up to date leveraging choco packages as well as develop a standard deployment model for all software. High level steps: Create choco installer application in sccm. Create notepad++ installer and uninstaller applications in sccm. Upgrade notepad++ with supersedence Deploy non standard package (Comming soon) So to dig in, first we need to install choco on our SCCM clients.  In this test, I'm using SCCM appl
Read more

Windows 11 22H2 production setup!

-
Image
Windows 11 22H2 production setup! I recently started to deploy windows 11 and to my chagrin found many applications that didn't align to the business needs such as recommended apps, tiktok, instagram etc, as well as other apps like Microsoft Teams, and Onedrive.  So this is a short blog and shout out to the resources I found to help tame this beast Microsoft released. Customize the start menu for the default profile to remove suggested apps for all users Uninstall bloatware for all users Customized Start Menu Log in as an admin account and customize the start menu they way you would like. Windows 11 stores the customized configuration under the users profile folder: c:\users\%user%\appdata\local\packages\Microsoft.Windows.StartMenuExperienceHost_%randomized%\localstate\start2.bin Copy this start2.bin file to somewhere on the network.  Like the sysvol domain controller. I wrote the script below to account for the randomization as the folder path is unique per windows install, but co
Read more

Automate Server Patching with Puppet (Part 2)

-
Image
In the first blog post I made about this, I showed how to patch windows 3rd party software like, notpad++, windirstat and other software utilizing puppet and chocoloatey on windows.  However, the next part of the solution was to deploy windows patches as the name suggests.  This part of the equation was a bit more challenging, but well worth the effort. For help setting up puppet and chocolatey refer to the previous blog post .  When patching windows security patches, most of them are not on the chocolatey website ready to go, so I choose to build my own repository of patches using a internal NuGet server.  Getting NuGet up and running requires Visual Studio.  In my case I utilized the community edtion (Free).  During the install you have to pick which components you want to install.  See below: Once you get visual studio prepare, your ready to head over to the microsoft project site and build the package on your own IIS instance.  I wont go into much detail here, I didn'
Read more