To contact Coraid support directly, email email@example.com.
The Coraid EtherDrive Host Bus Adapter and driver for VMware ESXi enable your server with AoE technology to deliver affordable, fast EtherDrive SAN solutions for your virtualization environment. Enabling ESXi hosts to work natively with EtherDrive storage is a highly effective way to take full advantage of VMware vSphere features including vMotion and VMFS. Coraid EtherDrive SAN products deliver Fibre Channel speeds at Ethernet prices in an easily scalable, reliable, and simply elegant solution.
PCIe HBA with (2) RJ-45 GbE ports
PCIe HBA with (2) RJ-45 10G Base-T ports
PCIe HBA with (2) CX-4 10 GbE ports
PCIe HBA with (2) SFP+ 10 GbE ports
Mezzanine HBAs for HP, IBM and Dell Blade Servers
Before Coraid EtherDrive SAN storage can be used with an ESXi host, one or more LUNs must be configured on the EtherDrive SAN storage appliance or through the EtherDrive VSX storage virtualization appliance. The SRX Admin Guide and VSX Admin Guide should both be used as the complete reference for EtherDrive SAN appliance configuration.
To setup a LUN on an EtherDrive Storage Appliance, follow these sample steps:
At this point, LUN 1.0 is online and visible to any EtherDrive HBA on the same Layer 2 network.
The Coraid EtherDrive HBA utilizes a PCIe interface within the ESXi Host. A full set of documentation on the ESXi HBA options and drivers is located at http://support.coraid.com/esx.
When the HBA has been physically installed in the ESXi host, the software driver must be installed for ESXi to recognize and utilize the card. You can download the software driver from http://support.coraid.com/support/esx. You can also access the software driver directly from the ESXi console using the wget command.
From the console on the ESXi host, install the EtherDrive HBA driver.
If the user is logged in to the ESXi host directly, enter:
esxcli software vib install –d file:///etherdrive-hba-esxi5-x.x.x-Rx.zip
If using the vSphere CLI, enter:
esxcli -u root -s hostname software vib install -d file:///etherdrive-hba-esxi5-x.x.x-Rx.zip
Reboot the ESXi hostby typing reboot at the Console OS command prompt.
Claiming a LUN
The EtherDrive HBA sees all EtherDrive LUNs that are available on the SAN. To allow the ESXi host visibility of the LUN, it must be "claimed". Only LUNs that have been claimed by an ESXi host are presented to ESXi and assigned a SCSI ID. When a LUN is claimed by an ESXi host, all other hosts in the ESXi cluster view it as claimed and also obtain a SCSI ID for access to this shared storage device. The act of claiming is only required by one ESXi host.
Note: One of the changes between ESXi 4.x and 5.x is in the VMFS File System. If a datastore was created on an ESXi 4.x system, that datastore and the LUN are considered "legacy" LUNs. See instructions for claiming Legacy LUNs on an ESXi 5.x, see Claiming a legacy LUN.
esxcli ethdrv claim -t targetid
Where targetid is shelf number.LUN number. For example, with shelf 1, LUN 0, the command is:
esxcli ethdrv claim -t 1.0
Claiming a Legacy LUN
Because of the maximum 2TB LUN capacity limit in VMFS 3 and the SCSI-2 LUN capacity limitations included, a legacy LUN is presented as one or more 2TB SCSI devices which each use a unique 8-byte NAA for identification. As part of the legacy claim function, the EtherDrive HBA automatically presents a Coraid LUN greater than 2TB to the ESXi host as multiple LUNs segmented at 2TB boundaries.
In the example below, the 9TB LUN (1.0) is legacy claimed and presented to the ESXi server as two 4TB LUNs and one 1TB LUN.
For example, run the command:
[root@remo ~]# cat /proc/ethdrv/devices
vmhba2:C0:T0:L1 1.0 2.0TB
vmhba2:C0:T0:L2 1.0 2.0TB
vmhba2:C0:T0:L3 1.0 2.0TB
The result of this legacy claim is (4) 2TB LUNs and (1) additional ~1TB LUN. If desired, the segmented LUNs can be reassembled into a single datastore by using the Extend Datastore feature.
To use the ESXi CLI to claim a legacy LUN:
Repeat the claim command for each Legacy LUN/datastore that needs to be recognized on an ESXi 5.0 host.
vSphere assigns a name to each LUN available to the ESXi host. LUN names can be changed from the vSphere-assigned LUN names to reflect EtherDrive shelf.slot names. Renaming the LUNs to reflect the EtherDrive shelf.slot mapping is recommended to maintain DataStore to LUN mappings and organization.
~ # cat /proc/ethdrv/devicesFor example:
vmhba2:C0:T3:L0 26.0 8000.000GB
vmhba2:C0:T8:L0 28.1 2199.023GB
vmhba2:C0:T8:L1 28.1 2199.023GB
The Runtime Name vmhba2:C0:T2:L0 is assigned to LUN 26.0.
In this example, it is Local Coraid Disk (naa.600100408f7239d9f03fa00700000000).
Right-click the LUN and click Rename.
Name the LUN with the shelf:LUN:Extent number used by the EtherDrive SAN.
In this case, it is EtherDrive 26.0.
Creating a datastore on the EtherDrive SAN follows the same steps as configuring any SCSI storage.
Follow the Add Storage Wizard to select Disk/LUN and the datastore options for storage initialization.
Based on VMware KB 1031322