Say I have an ESXi (5.0) host that runs a Linux distribution which hosts iSCSI targets, which contain the images for other VMs which the host will run. When it's used, I'll start the host first, then the iSCSI server, and then refresh all storage targets/HBAs in order to see the provided shares as online. I know it's a strange puzzle-box solution, but I was told to implement it.
I have a small VMware cluster that is exhibiting some strange behavior - the NICs in my iSCSI ports are needing to be switched periodically when my hosts have been down. Why is this occurring?
This has been happening since version 4.0 ESX. We are currently on 5.0 ESXi.
I'm using the inbuilt iSCSI software initiator utilizing a single vSwitch. Two physical NICs. Two VMKernel ports.
I have enabled Jumbo Frames (9000) in ESXi for all my vmNICs, vmKernels, vSwitches, iSCSI Bindings etc - basically anywhere in ESXi where it has an MTU settings I have put 9000 in it. The ports on the switches (Dell PowerConnects) are all set for Jumbo Frames. I have a Dell MD3200i with 2 controllers, each with 4 ports for iSCSI.
Using iSCSI On Ubuntu 9.04 (Initiator And Target)
Let me start by saying I am somewhat of a Vmware novice, I know just enought to manage and create servers at a basic level from the vSphere client.
I have a VMWare server, ESX 4.0 connected over iSCSI to a SAN. The SAN is being used as storage for both RDMs and VMFS volumes.
The SAN has died and I ordered a new one.
I created an iSCSI volume in Openfiler.
Volume name Volume description Volume size File system type File system size FS used space FS free space Delete Properties Snapshots
backup Backup Storage 3717536 MB iSCSI Not applicable Not applicable Not applicable In use Edit Create
When I create the partition in VMware, it sets the size of the partition to 1.55TB even t
I don't know if I'm missing something but when I'm mounting additional iSCSI volumes to a said server to add additional storage to a server I'm not seeing a way to mount the volume after running a discovery command.
The reasoning I want to be able to do this is that we're running an application that would require downtime everytime we add additional iSCSI volumes to this server.
This question is a follow-on from Dedicated NIC or dedicated port for iSCSI?
Excluding the hardware iSCSI initiator point that was made in the accepted answer to the above question, it seems that using separate port(s) on a multi-port NIC for iSCSI is pretty much going to meet the recommendation of using "seperate NICs" for iSCSI traffic.
I'm in the process of planning a small iSCSI installation
I work for a small state college. We currently have 4 ESXi hosts (all made by Dell), 2 EqualLogic SANs (PS4000 and PS4100) and a bunch of old HP Procurve switches. The current setup is very far from being redundant and fast so we want to improve it. I read several threads but get even more confused.
The Procurve Switches are 2824.
Email this page
