iSCSI connection issue

bntech
bntech used Ask the Experts™
on
I have a HP MSA 2012i Storage device, and (3) ESX servers.
I had a pre-existing volume on the HP MSA that is seen by all three servers without issues.
VMDKS are running on this just fine.

I created a new volume and rescan the VHBAs and tried to "add new disk" under storage like normal, but nothing populates.
I know the esx servers can see the MSA, as it saw and created the first volume without issue.
Also CHAP is not enabled. and on the new volume, all esx host have permissions to this.
I looked in the /var/logs/ and found the following,
Need help getting this new volume connected to the esx servers.

iscsid: connection failed for discovery (err=interrupted system call)
iscsid: connection to discovery address x.x.x.x failed
iscsid: connection login retries (reopen_max) 5 exceeded
iscsid: login failed: iqn................. default x.x.x.x,3260,2,conn=0 reason:00080000
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Paul SolovyovskySenior IT Advisor
Top Expert 2008

Commented:
Make sure the LUNs are zoned propperly on the MSA, this is usually the cause.  You have to allow the iqn (intiator) to access the new LUN on the MSA.  I have seen this many times and that's usually the case

Author

Commented:
There is a place in volume management that allows you do volume mappings. I had already added the 3 esx servers iqn to this lun mapping but this did not work. its almost like i tried to many times and now nothing shows up.

This did orginally show up when i was creating the disk, but it wouldnt add becuase it couldnt find partition. which makes since --- since the msa was still initialize the disk, and creating volume.
But now that it has the volume and mappings -- nothing shows up in the add disk

I rescanned the vmhbas to no avail.
Can you try to many times where vmware will not show any more?
Paul SolovyovskySenior IT Advisor
Top Expert 2008

Commented:
Make sure you don't have residual stuff ont the MSA.  If you tell me the MSA model I can help.  Also it may be a good idea to delete the LUN and recreate it.

Once you recreate it provide screenshot with ACL view

Author

Commented:
its a MSA 2012i
I already tried recreating vdisk, and volume with same results. I also deleted the volume and assigned a different LUN and that didnt work either.

Commented:
Disregard I figured it out. --- I changed RAID controller owner to A from B and it worked.
Top Expert 2014

Commented:
So you've got a single controller MSA2012i? Nice feature they've got of automatically making the non-existant B controller owner of every second vDisk you create.
Paul SolovyovskySenior IT Advisor
Top Expert 2008

Commented:
That's what you get for virtual IOPS

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial