Archive

Archive for April, 2015

Setup MPIO for EMC VNX Storage

April 23rd, 2015 Comments off

If you use EMC PowerPath, the process is straightforward from EMC. But in most cases, due to the price of EMC PowerPath, we use Microsoft MPIO instead (Which PowerPath uses under the covers)

If using Microsoft’s MPIO, you can use their mpclaim utility from a command line or their GUI for doing all the setup. The following assumes you are using Microsoft MPIO and an EMC VNX storage array. There are only slight variations for other combinations.

  1. Configure hardware for MPIO.
  2. Install Microsoft MPIO.
  3. From a command prompt, issue the command “mpclaim -h” to see the currect storage devices claimed by MS MPIO. With a VNX you should see something like “Vendor 8Product 16″. Looking at the MPIO Devices tab in the GUI will show the same information.
  4. From a command prompt, issue the command “mpclaim -s -d” and you should see that there are no disk present yet, as you haven’t allowed any.
  5. From a command prompt, issue the command “mpclaim -e” to display the vendor product ID string for the connected storage array. Depending on how your VNX is configured, you will see something like this “DGC VRAID”.  There are exactly five (5) spaces after “DGC” and you must have exactly five spaces in the ID.
  6. Now you can add the multipath support for the speicifc IDs you want. Obviously you will want whatever you saw in the previous step, but in case you plan on using some other configurations, you can add everything from the list from above. From a command prompt enter the command “mpclaim -n -i -d “DGC VRAID”. The “-n” switch suppresses the automatic reboot. Repeat that commnd for each all device IDs desired.
  7. Reboot the system.
  8. From a command prompt, issue the command “mpclaim -s -d” and you should see the disks claimed by MPIO on the node. Again, you can use the GUI for all this, too.
  9. Run Disk Management and activate the new disk

 

Categories: Data Center, Windows

Vsphere snapshot hang – How to (force) kill a VM process

April 16th, 2015 Comments off

I had a frozen VM because the snapshot hang at 95%. I could not do anything to the VM because its process is locked to the host. I couldn’t stop it, couldn’t cancel the task either. To release the lock and force kill it, I had to do the following:
- Restart the management agents
- Force stop the VM
- Consolidate the snapshot (if necessary)
- Restart the VM

1. Restart the management agents
These 2 commands should do

2. Force stop the VM
a. The VMWare way

VM's NAME
World ID: 46664
Process ID: 0
VMX Cartel ID: 46640
UUID: 42 24 e8 f3 28 35 e1 77-dd 56 40 46 d2 a4 16 43
Display Name: plsw-ts2012-fe1
Config File: /vmfs/volumes/5156099e-0e41f131c77b4/VM-NAME/VM-NAME.vmx

Then collect the “Word ID” and run either of these commands

At this point the VM should be stopped and the lock is released. You might need to remove and re-add it. If the VM is still lock, we will need to force stop it the Linux way

~ # ps | grep 52173320
52173320 52173320 vmx /bin/vmx
52173323 52173320 vmx-vthread-4:VM-NAME /bin/vmx
52174736 52173320 vmx-vthread-5:VM-NAME /bin/vmx
52174737 52173320 vmx-mks:VM-NAME /bin/vmx
52174738 52173320 vmx-svga:VM-NAME /bin/vmx
52174741 52173320 vmx-vcpu-0:VM-NAME /bin/vmx

The second column is the master process number . Run this command to kill it

KB 1004340 should provide you with some more methods but these 2 are usually good enough

l>