hewittscooter
Contributor
Contributor

ESXi not connecting to MSA1510i via iSCSI

Storage works MSA20 with a 1510i controller Basic LUN setup with a Target iqn.1986.com.hp.storage.etc..... target ip address 192.168.0.4. Trying to connect a ESX Server 3i 3.5.0 build-110271 Running on a Proliant DL380 G5 2 built in NICs one vmnic0 is management port on a 10.0.0.x network and I have configured the Vmkernel to vmnic1 to 192.168.0.5. I can see and ping the target and I can also see it from other microsoft boxes using the microsoft iscsi initiator. This is a complete test enviroment. will try anything.

0 Kudos
13 Replies
rlund
Enthusiast
Enthusiast

See

Walks you through adding iSCSI target in ESXi and formatting it

"

Steps to Configure ISCSI Target in VMware ESXi

1. Login to Infrastructure Client

2. Click the Configuration Tab

3. Click Storage Adapters

4. Highlight iSCSI Software Adapter

5. Click Properties

6. Click Configure

7. Check Enable and hit ok

8. Click Dynamic Discovery

9. Click Add

10. Type in the IP Address of the Server or Device that has the ISCSI Target.

11. Click OK

12. Click Close

13. If prompted to rescan of the host, click yes. If not, click rescan and hit ok

14. Click Storage

15. Click Add storage

16. Click next

17. Make sure the lun number is correct and click next

18. At the hard disk is blank, hit next

19. Name the datastore, a new name, ISCSI02 for example.

20. Select 2048 GB Block size 8 MB and make sure Max Cap is check, click next.

21. Click Finish.

"

Also you need to configure your networking as follows.

See Attached Picture.

Basicy, you need to vswitches, one for each network, each with a kernel.

Roger Lund

My Blog:

Roger Lund Minnesota VMUG leader Blogger VMware and IT Evangelist My Blog: http://itblog.rogerlund.net & http://www.vbrainstorm.com
0 Kudos
hewittscooter
Contributor
Contributor

Im good until step 14 and no new storage shows up.

0 Kudos
rlund
Enthusiast
Enthusiast

see attachment and addtional note above.

Roger Lund

My Blog:

Roger Lund Minnesota VMUG leader Blogger VMware and IT Evangelist My Blog: http://itblog.rogerlund.net & http://www.vbrainstorm.com
0 Kudos
hewittscooter
Contributor
Contributor

Here is my networking config. I now have a vswitch and vmkernel on each network. When I set the gateway routing on one it changes on both. I see you have 4 NICS I may need to add a physical NIC?

0 Kudos
rlund
Enthusiast
Enthusiast

Try setting the gateway on the iSCSI network to nothing.

It worked for me.

The gateway on the other network can be blank as well.

Roger Lund

My Blog:

Roger Lund Minnesota VMUG leader Blogger VMware and IT Evangelist My Blog: http://itblog.rogerlund.net & http://www.vbrainstorm.com
0 Kudos
hewittscooter
Contributor
Contributor

No luck.

Is there anything else you need to configure on the target to allow the ESXi to connect?

Also in the iSCSI software adapter config for the vmhba32 when I enter my iqn iSCSI name in, the iSCSI alias never changes it still reflects the name of my ESXi host name.

0 Kudos
rlund
Enthusiast
Enthusiast

All you do is click enable, under dymatic addressing you put in your target IP. ( iSCSI HOST, being your SAN )

Have you tired Accessing your iSCSI host from a windows device, using the Microsoft software?

Roger Lund

My Blog:

Roger Lund Minnesota VMUG leader Blogger VMware and IT Evangelist My Blog: http://itblog.rogerlund.net & http://www.vbrainstorm.com
0 Kudos
hewittscooter
Contributor
Contributor

Yes it works from a microsoft box. I didnt attach to it, but i can see it. it shows up. I will verify that I can attach via MS. thanks for your help so far.

0 Kudos
rlund
Enthusiast
Enthusiast

Here is my iSCSI Initiator Properties

Here is where you click enable. Leave the name alone.

2.gif

and next this is where you put in your iSCSI Host's IP.

3. gif

After a resan, it should show the disk under the iSCSI Software Adapter

4.gif

Roger Lund

My Blog:

Roger Lund Minnesota VMUG leader Blogger VMware and IT Evangelist My Blog: http://itblog.rogerlund.net & http://www.vbrainstorm.com
0 Kudos
hewittscooter
Contributor
Contributor

Okay, just for the heck of it I switched duties of the physical NIC's after that I could not connect to the management port. So my Dl380 has a bad NIC out of the box. Im in the process of borrowing a NIC just to finish my testing. But im sure that is it. Sorry to waste your time the last thing I thought to check was that.

0 Kudos
rlund
Enthusiast
Enthusiast

No Problem, post your results , and let me know if it works.

I'd love to know what you end up running, and performance also.

Roger Lund

My Blog:

Roger Lund Minnesota VMUG leader Blogger VMware and IT Evangelist My Blog: http://itblog.rogerlund.net & http://www.vbrainstorm.com
0 Kudos
hewittscooter
Contributor
Contributor

rlund, thank you for your help. It was the NIC.

We are going to eventually roll this server out with exchange 2007 with each host running different server roles , then snap shots and mailboxes can be stored on the SAN. That is our vision we still have alot of studing and planning to do. Tons of reading and testing in the next few weeks.

Do you have any articles or documentation on virtulizing with exchange 2007. I found some stuff on the vmware site. But like ive said I have just started looking.

0 Kudos
rlund
Enthusiast
Enthusiast

Sorry, it's been one of those weeks.

Here is a start

Message me if your looking for specific's and check out my blog.

Roger Lund

My Blog:

Roger Lund Minnesota VMUG leader Blogger VMware and IT Evangelist My Blog: http://itblog.rogerlund.net & http://www.vbrainstorm.com
0 Kudos