Posts Tagged iSCSI

Operation failed, diagnostics report: iScsi Adapter in unbound status, adding Static Target can not be done.


Hello,

You might see error in VMWare ESXi when LUN is created in EMC VNX3150 and you grant access to hosts that added to the VNXe3150.

Operation failed, diagnostics report: iScsi Adapter in unbound status, adding Static Target can not be done.

VNXe3150 Error in ESXi
This error is generated because EMC VNXe3150 try’s to add the iSCSI Servers/Targets that configured in the EMC VNX to each ESX that granted access to the LUNs. While the iSCSI Targets already added in the Dynamic/Static iSCSI Targets tab, this error is generated.

I think EMC should introduce some logic into the EMC VNXe3150 SAN Storage to initially check the Host if the iSCSI Targets already added, adding iSCSI targets via EMC should be ignored.

Or, VNXe3150 should loop through the storage pools/LUNs where it finds LUNs already presented to ESX hosts from the same Array, adding iSCSI Targets through EMC VNXe3150 should be ignored. Otherwise this fake error will keep presenting itself.

, , , ,

Leave a comment

(DUP!) Duplicate Ping when you ping VMKernel PortGroup within ESX Host


Hello,

Have you ever encountered a duplicated ping when you try to ping the iSCSI PortGroups or pinging the ESX Host Itself from vCenter?

In my case I have this issue when I try to ping from ESXi5.0 host to an iSCSI Target.

SAN Storage Configuration:

IBM DS3512 with two Controllers, each with 4 iSCSI Ports.

CTRL-1:
Port-3: 10.10.30.1
Port-4: 10.10.40.1
Port-5: 10.10.50.1
Port-6: 10.10.60.1

CTRL-2:
Port-3: 10.10.30.2
Port-4: 10.10.40.2
Port-5: 10.10.50.2
Port-6: 10.10.60.2

When I try to ping each of the iSCSI Ports IP Address, I got

64 bytes from xxx.xxx.xxx.xxx: icmp_seq=4 ttl=128 time=0.xxx ms (DUP!)

ESX iSCSI Configuration:

vSwitch with 4 VMKernels PortGroup for iSCSI.

iSCSI-30 10.10.30.x

iSCSI-40 10.10.40.x

iSCSI-50 10.10.50.x

iSCSI-60 10.10.60.x

By default, vSwitch will take Route Based on the Originating port ID.

I resolved this issue by:

Changing from Route based on the Originating Port ID to Route based on IP Hash. And I set each VMKernel Port active on one nic only instead of two “Default”

VMNIC3 active for iSCSI-30 and iSCSI-40 because this NIC connected to Switch-1 as well as both iSCSI Ports.

VMNIC9 active for iSCSI-50 and iSCSI-60 because this NIC connected to Switch-2 as well as both iSCSI Ports.

(DUP!) has disappeared after doing this :)

, , , , ,

Leave a comment

(DUP!) Duplicate Ping when you ping VMKernel PortGroup within ESX Host


Hello,

Have you ever encountered a duplicated ping when you try to ping the iSCSI PortGroups or pinging the ESX Host Itself from vCenter?

In my case I have this issue when I try to ping from ESXi5.0 host to an iSCSI Target.

SAN Storage Configuration:

IBM DS3512 with two Controllers, each with 4 iSCSI Ports.

CTRL-1:
Port-3: 10.10.30.1
Port-4: 10.10.40.1
Port-5: 10.10.50.1
Port-6: 10.10.60.1

CTRL-2:
Port-3: 10.10.30.2
Port-4: 10.10.40.2
Port-5: 10.10.50.2
Port-6: 10.10.60.2

When I try to ping each of the iSCSI Ports IP Address, I got

64 bytes from xxx.xxx.xxx.xxx: icmp_seq=4 ttl=128 time=0.xxx ms (DUP!)

ESX iSCSI Configuration:

vSwitch with 4 VMKernels PortGroup for iSCSI.

iSCSI-30 10.10.30.x

iSCSI-40 10.10.40.x

iSCSI-50 10.10.50.x

iSCSI-60 10.10.60.x

By default, vSwitch will take Route Based on the Originating port ID.

I resolved this issue by:

Changing from Route based on the Originating Port ID to Route based on IP Hash. And I set each VMKernel Port active on one nic only instead of two “Default”

VMNIC3 active for iSCSI-30 and iSCSI-40 because this NIC connected to Switch-1 as well as both iSCSI Ports.

VMNIC9 active for iSCSI-50 and iSCSI-60 because this NIC connected to Switch-2 as well as both iSCSI Ports.

(DUP!) has disappeared after doing this :)

, , , , ,

Leave a comment

Cannot reach iSCSI target after enabling iSCSI port binding in ESXi5.0


Today I have encountered funny thing which kept me out of control trying to figure it out. In my environment my ESX Servers are connected to EMC AX4-5i and I configured an iSCSI Binding to achieve Round Robin Load Balancing..

I received a new IBM DS3512 and recently put the second controller to reply the EMC SAN Storage. In IBM  Storage manager I configured the host profile and created test LUN and presented to one of the ESX Hosts. I confirm everything is correct, I can ping the targets IP Address and i can ping ESX VMkernel IP Address but when I do a rescan, nothing is added. I was pulling my hair to figure out what is wrong.

It concluded that the previous iSCSI Binding is the issue. After removing both VMKernel PortGroups that binded to the VMHBA41 and did a rescan the IBM iSCSI Target detected and LUN appear.

In vSphere Client:

  1. Click Configuration > Storage Adapters > iSCSI Software Initiator > Properties > Configure.
  2. Select the Network Configuration tab.
  3. Select the vmk which is iSCSI compliant, then click OK.

Or you can use cli in command line;

esxcli iscsi networkportal add -A vmhbaX -n vmkY

Where X is the vmhba device number, and Y is the vmkernel port configured to access iSCSI storage.

, , , , , ,

Leave a comment

IBM DS3500 Multipathing / vSphere MPIO


Below I’m summrizing how I have configured the IBM DS3500 SAN Storage for my DR Site.

Each SCSI port in the IBM DS3500 with different subnet,

  • Port-3 10.10.10.1
  • Port-4 10.10.20.1
  • Port-5 10.10.30.1
  • Port-6 10.10.40.1 /24

 

The Storage Processor Ports are connected to the Dell 2724 switches, 10.x subnet goes into Port-1 in pSwitch1 and subnet 20.x goes into pSwitch1 Port-2, Subnet 30.x goes into pSwitch2 into Port-1 and Subnet 40.x goes into pSwitch2 Port-2.

In the ESX side, one vSwitch attached to two vmnic’s vmnic2 and vmnic3. In this vSwitch  created four VMkernel Portgroups,

  • iSCSI-01 10.10.10.30
  • iSCSI-02 10.10.20.30
  • iSCSI-03 10.10.30.30
  • iSCSI-04 10.10.40.30

If all the nics are active at the same time and try to vmkping to the Storage Processor, (DUP!) Duplicate pings from one of the subnet, then the ping will stop working but it will work for the other Storage Processor.

To overcome this issue is to have the vmnic2 is active for iSCSI-01 and iSCSI-02 and vmnic3 unused for iSCSI-01 and iSCSI-02. The same for the other Portgroups, vmnic3 is Active only for iSCSI-03 and iSCSI-04 and vmnic2 is unused these two Portgroups. After that the ping is steady without (DUP!).

iSCSI Binding is done on the iSCSI adapter to have all the VMkernel Portgroups. esxcli swiscsi nic add -n -d vmk# vmhba33.

After that, all the four paths are appeared, and changed the Storage Path to Round Robin to have them all Active(I/O) at the same time.

Testing were done, by switching off pSwitch1 and connection were alive to the SAN Storage, and the number of paths changed from four to Two. Turned off pSwitch2 and the connection were alive too to the SAN Storage and the number of paths changed from four to two.

As per IBM, they say it’s not the recommended way of having this config and its unsupported  I don’t know the reason why it’s not supported / recommended. The only support method they say as per the IBM engineer who installed this SAN Storage is to have only two paths if only one Controller is installed and cannot put four connections!!! But he surprised of what he has seen from my configuration :). As per him, he said I can use the 8 Paths ONLY if the second controller is installed, which is logically I can’t find any answer for it why is that!!!!

, , , , , , , ,

7 Comments