Tuesday, 30 April 2013

Configuring ISCSI port binding on vSphere using CLI




Configuring Port Binding on vSphere 5.0 Using CLI


Run the following commands from the vSphere 5.0 host CLI to bind the VMkernel network adapter to the  iSCSI adapter:

esxcli iscsi networkportal add --nic vmk0 --adapter vmhbaXX
esxcli iscsi networkportal add --nic vmk1 --adapter vmhbaXX


Where vmk0 and vmk1 are the VMkernel network adapters compatible with iSCSI port binding requirements.  You can get the list of VMkernel network adapters connected to  all vSwitches by using  the command   

esxcfg-vmknic –l


vmhbaXX  is the software iSCSI adapter vmhba ID. You can verify the binding details by using the  following command: 


esxcli iscsi networkportal list --adapter vmhbaXX.


Then rescan the software iSCSI adapter to verify that multiple paths are available for iSCSI LUNs.



Configuring Port Binding on vSphere 4.x Using CLI


To enable vmknic-based multipathing for software iSCSI, run the following CLI commands:

esxcli swiscsi nic add --nic vmk0 --adapter vmhbaXX
esxcli swiscsi nic add --nic vmk1 --adapter vmhbaXX


Where  vmk0 and  vmk1 are the VMkernel network adapters  compatible with iSCSI port binding requirements. You can get the list of VMkernel network  adapters connected to all vSwitches by using the command 

esxcfg-vmknic -l.


vmhbaXX is the software iSCSI adapter vmhba ID.  After configuring port binding, you can verify the binding details by using the following command: 


esxcli swiscsi nic list --adapter vmhbaXX. 


Then rescan the software iSCSI adapter to verify that multiple paths are available for iSCSI LUNs.



http://www.vmware.com/files/pdf/techpaper/vmware-multipathing-configuration-software-iSCSI-port-binding.pdf

Monday, 29 April 2013

Unable to find the system volume, reconfiguration is not possible, VMWARE P2V error

Applies to Windows Vista, 7, Server 2008, Server 2008 R2

To resolve this issue:
  1. Import the virtual machine to vCenter Server.
  2. Boot the virtual machine from the correct Microsoft Windows installation media (Correct architecture and version of the OS).
  3. Select the appropriate keyboard layout and language options and click Next.
  4. Click Repair your computer.
  5. Select the operating system to be repaired and click Next.
  6. Click the Command Prompt.
  7. Type bcdedit and press Enter.
  8. Under the Windows Boot Manager title with the identifier set to {bootmgr}, you may see that the device is set to bootSimilarly, under the Windows Boot Loader with the identifier set to {default}, you may see that the device and osdevice are set to boot. These items should be set properly for your environment. Usually these appear as partition=C:In some cases the {default} identifier may have them set to partition=D:.

    Run these commands to correct the configuration:

    Note: bcdedit is located in the following path, c:\windows\system32
    bcdedit /set {bootmgr} device partition=C:

    bcdedit /set {default} device partition=C:

    bcdedit /set {default} osdevice partition=C:
  9. Type exit at the command prompt and select Shutdown.
  10. Try to reconfigure using VMware converter. The reconfigure should now complete successfully. If it fails again, repeat Steps 1 to 7 and then run these commands to set the default device to partition=D::

    bcdedit /set {bootmgr} device partition=C:

    bcdedit /set {default} device partition=D:

    bcdedit /set {default} osdevice partition=D:

Saturday, 27 April 2013

How to disable firewall command line?

To Disable:
netsh firewall set opmode disable

To Enable:
netsh firewall set opmode enable

How to clear preferred IP address

How to clear preferred IP address?

Step 1. Goto Start, Run, CMD to open a command prompt.
Step 2. Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Step 3. Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log
Step 4. Reboot the machine.

Thursday, 4 April 2013

Disk extended in Computer Management not showing in My Computer

If you come across a Virtual Machine running out of space and you are about to provision more space and extend it make note that extending disk from Computer Management may increase the disk space on Computer Management window but also check from My Computer to ensure disk is actually extended.

If you come across this problem where disks showing in My Computer window are not extending after a refresh then do following:
  • Allocate more space to the VM
  • run Re-Scan from Disk Management
  • use Diskpart to extend as shown in the screenshot below