Monthly Archives: April 2010

Installation of Dell Equallogic SRA for VMware SRM

I had this problem a little while ago.

When I clicked on “configure” next to “Array Managers”, and then press “add”, I got the box to enter the details of the local SAN.

I then entered the details in the VC window but got an error saying “Error occurred: XML document is empty.”

The solution is to install Java. It doesn’t come with either SRM or the SRA, so you need to go to Oracles website and download and install it separately. All should then work!

Advertisements

1 Comment

Filed under Equallogic, SRM, VMware

Volume move stalls on Dell Equallogic storage

If you have ever tried to move a volume out off a storage device and had it stall (just sit there at say 20% for hours), it could be an incorrect kernel flag. This can happen if the volume is being replicated, and basically it means that the kernel is still being replicated, so the page cannot be moved.

The solution is to reboot the array. Hoepfully though you can get all your other volumes off the array first minimizing the impact, then reboot the array and all should be fine.

This will be fixed in an upcoming firmware update.

Leave a comment

Filed under Equallogic

Recovering a lost partition table on a VMFS volume

ESX 3.x
To recreate the partition table:
Log in to the ESX host service console.
Type esxcfg-vmhbadevs -q and press Enter to get a list of Linux devices and their VMkernel name.
Type fdisk -l /dev/sdX and press Enter to confirm that the partition is no longer here.
Recreate the partition table:
Start fdisk with the command fdisk /dev/sdX and press Enter.
Create the partition:
Press n and press Enter to create a new partition.
Press p and press Enter to select that this is a primary partition.
Press 1 and press Enter to make the first partition.
Press Enter to keep the default value.
Press Enter again to keep the default value.

Change the partition to type fb (VMFS):
Press t and press Enter.
Press 1 and press Enter.
Enter fb and press Enter.

Align the partition to sector 128. Do not execute the realign procedure if the volume was originally created from the ESX command line or if the volume was upgraded from an ESX 2.x as the starting sector is 63, which is the default when using fdisk.

If the VMFS volume was originally created using VMware Infrastructure Client, the beginning of the partition was set to sector 128 and the alignment is required to match the beginning of the partition to where the volume used to be.

Note: Looking at other VMFS partitions with fdisk -lu in the same environment reveals if the current practice is to align the partition start to block 128 or not.

Type x and press Enter to move to expert mode.
Type b and press Enter to change the beginning of the partition.
Type 1 and press Enter to select the first partition.
Type 128 and press Enter to move to the block 128 the beginning of the partition.

Type w and press Enter to save.

Note: This exits fdisk and returns you to the command prompt.
Type vmkfstools -V and press Enter to discover the VMFS.
If the VMFS datastore is still not showing up, see A VMFS volume is not available and vmkernel reports displays the error: Device size mismatch (1003133).

Note: This procedure may not work on VMFS volumes that are participating in a spanned set (extents). Contact VMware Technical Support and work with them to resolve the issue.

ESX 4.x
Log in to the ESX host service console.
Run the command:

esxcfg-scsidevs -c

The output appears similar to:

Device UID Device Type Console Device Size Plugin Display Name
mpx.vmhba0:C0:T0:L0 Direct-Access /dev/sdb 139890MB NMP Local ServeRA Disk (mpx.vmhba0:C0:T0:L0)
mpx.vmhba3:C0:T0:L0 CD-ROM /dev/sr0 0MB NMP Local HL-DT-ST CD-ROM (mpx.vmhba3:C0:T0:L0)
naa.5005076c02045649 Enclosure Svc Dev/vmfs/devices/genscsi/naa.5005076c02045649 0MB NMP Local IBM Enclosure Svc Dev (naa.5005076c02045649)
naa.600601606a20160084afee93bce8de11 Direct-Access /dev/sdf 153600MB NMP DGC Fibre Channel Disk (naa.600601606a20160084afee93bce8de11)
naa.60060160b4111600624c5b749c7edd11 Direct-Access /dev/sda 153600MB NMP DGC Fibre Channel Disk
(naa.60060160b4111600624c5b749c7edd11)
naa.6090a038f0cd4e5bdaa8248e6856d4fe Direct-Access /dev/sde 256005MB NMP EQLOGIC iSCSI Disk
(naa.6090a038f0cd4e5bdaa8248e6856d4fe)
naa.6090a038f0cd6e5165a344460000909b Direct-Access /dev/sdd 153600MB NMP EQLOGIC iSCSI Disk
(naa.6090a038f0cd6e5165a344460000909b)

Identify the disk in question, and make note of the value under the Console Device column.
Run the command:

fdisk -l

Where is the value recorded in step 2.

The output appears similar to:

Disk /dev/sde: 268.4 GB, 268440698880 bytes
255 heads, 63 sectors/track, 32636 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sde1 1 32636 262148606 fb VMware VMFS

Start fdisk with the command following command and press Enter.

fdisk /dev/sdX
Create the partition:
Press n and press Enter to create a new partition.
Press p and press Enter to select that this is a primary partition.
Press 1 and press Enter to make the first partition.
Press Enter to keep the default value.
Press Enter again to keep the default value.
Change the partition to type fb (VMFS):
Press t and press Enter.
Press 1 and press Enter.
Enter fb and press Enter.

Align the partition to sector 128.

Caution: Do not execute the realign procedure if the volume was originally created from the ESX command line or if the volume was upgraded from ESX 2.x as the starting sector is 63, which is the default when using fdisk.If the VMFS volume was originally created using VMware Infrastructure Client, the beginning of the partition was set to sector 128 and the alignment is required to match the beginning of the partition to where the volume used to be.

Note: Looking at other VMFS partitions with fdisk -lu in the same environment reveals if the current practice is to align the partition start to block 128 or not.

Type x and press Enter to move to expert mode.
Type b and press Enter to change the beginning of the partition.
Type 1 and press Enter to select the first partition.
Type 128 and press Enter to move to the block 128 the beginning of the partition.
Type w and press Enter to save.

Note: This exits fdisk and returns you to the command prompt.

Run vmkfstools -V and press Enter to discover the VMFS.
Note: This procedure may not work on VMFS volumes that are participating in a spanned set (extents). Contact VMware Technical Support and work with them to resolve the issue.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002281

Pretty useful if your VMFS volume goes missing after a reboot!

Leave a comment

Filed under VMware

Unpresenting a LUN containing a datastore from ESX 4.x and ESXi 4.x

To unpresent a LUN containing a datastore from an ESX 4 host:

1. Ensure that there is no I/O operations being done to the LUN.

The best method of doing this is:

· Ensure there are no virtual machines running on a datastore located on the LUN in question.

· Ensure there are no 3rd party scripts or utilities running on service console which could access the LUN in question.

2. Log into the ESX host as a root user via the console or via SSH.

For more ESX information, see Unable to connect to an ESX host using Secure Shell (SSH) (1003807).For more ESXi information, see vSphere Command-Line Interface Documentation.

3. To list the existing claimrules, run the command:

esxcli corestorage claimrule list

The output appears similar to:

0 runtime transport NMP transport=usb
1 runtime transport NMP transport=sata
2 runtime transport NMP transport=ide
3 runtime transport NMP transport=block
4 runtime transport NMP transport=unknown
101 runtime vendor MASK_PATH vendor=DELL model=Universal Xport
101 file vendor MASK_PATH vendor=DELL model=Universal Xport
65535 runtime vendor NMP vendor=* model=*

4. Run the command:

esxcli corestorage claimrule add –rule 192 -t location -A –C –T –L -P MASK_PATH

For more information about the adapter, target, and LUN values, see Identifying disks when working with VMware ESX (1014953).

Note: The number used in the –rule 192 portion can be any number between 101 and 200 that does not conflict with a pre-existing rule number from step 3.

5. To list the existing claimrules, run the command:

esxcli corestorage claimrule list

The output appears similar to:

Rule Class Type Plugin Matches
0 runtime transport NMP transport=usb
1 runtime transport NMP transport=sata
2 runtime transport NMP transport=ide
3 runtime transport NMP transport=block
4 runtime transport NMP transport=unknown
101 runtime vendor MASK_PATH vendor=DELL model=Universal Xport
101 file vendor MASK_PATH vendor=DELL model=Universal Xport
192 file location MASK_PATH adapter=vmhba33 channel=0 target=0 lun=25
65535 runtime vendor NMP vendor=* model=*

Note: In the above example, the line beginning with 192 indicates that Adapter 33, Channel 0, Target 0, and LUN 25 has been masked from the ESX host.

6. To reload the claim rules, run the command:

esxcli corestorage claimrule load

7. Run the command:

esxcli corestorage claiming reclaim -d

The field represents the LUN being unpresented. This attempts to unclaim all paths to a device and runs the loaded claimrules on each of the paths unclaimed to attempt to reclaim them. For more information about the NAA identifier, see Identifying disks when working with VMware ESX (1014953).

8. Repeat steps 1 to 7 for any host which also has visibility to the LUN in question.

9. Unpresent the LUN using the suggested method from your storage array vendor.

10. Perform a rescan on all of the ESX hosts which had visibility to the LUN in question.

11. To remove the rule from the ESX host, run the command:

esxcli corestorage claimrule delete –rule 192

Note: Refer to the rule number created in step 4.

12. Run the following command to list the existing claimrules. Compare with the output from step 5.

esxcli corestorage claimrule list

Note: The rule created in step 4 is no longer visible.

13. To reload the claim rules, run the command:

esxcli corestorage claimrule load

14. Repeat steps 11 and 13 on all of the ESX hosts that also have visibility to the LUN in question.

Note: The operation must be done using the VMware ESX service console or the vSphere command line.This operation cannot be done using the Manage Paths dialog within the vSphere Client.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1015084

Leave a comment

Filed under VMware

iSCSI via CLI

iscsicli provides a command line interface for the Microsoft iSCSI initator.

It is executed by running c:\iscsicli and once running, you can press ? to bring up the help screen.

The most useful commands will probably be:

iscsicli AddTarget

iscsicli RemoveTarget

iscsicli PersistentLoginTarget

<Key

iscsicli ListPersistentTargets

iscsicli RemovePersistentTarget

iscsicli Ping

[Request Count] [Request Size] [Request
Timeout]

And also these:

iscsicli QLoginTarget [CHAP Username] [CHAP Password]

iscsicli QAddTarget

iscsicli QAddTargetPortal
[CHAP Username] [CHAP Password]

iscsicli QAddConnection

[CHAP Username] [CHAP Password]

iscsicli BindPersistentVolumes

iscsicli BindPersistentDevices

More info here:
http://social.technet.microsoft.com/Forums/en-US/winservercore/thread/85ebf386-adeb-4721-a752-c0b936f2a692/

http://www.microsoft.com/WindowsServer2003/technologies/storage/iscsi/default.mspx

Leave a comment

Filed under Equallogic, VMware