ESXi and iSCSI datastore

Hi,

i have an ESXi running on 4.0 i want to add an Synology DS212 on an iSCSI connection.

this is what i did:
i uses an unused networkcard and created by "networking" a new virtual switch and added "VMkernel" i added an IP adress on the card 192.168.0.50
then i go to the Synology drive. there i also created an iSCSI Lun. the Synolog has also an IP 192.168.0.100
When the LUN is setup i did go to storage adapters and clicked on the "proporties" of the iSCSI Software adapter. Next i go to Static recovery and added the IP 192.168.0.100 and port 3260 and my iSCSI target name. Filled in the correct CHAP credentials and press ok.

when i do a rescan of the HBA he do not find any iSCSI connection.

Hardware:
i have 4 networkcards.

2 are connected to the network and are running the VM's
1 is connected directly to the Synology NAS (for iscsi)
1 is not used/connected

strange is that when i connect the Synology on the local lan of my network the connectoin works. but when i add the Synology directly on a free networkcard of my server nothing works.

what am i missing?
LVL 1
Rik Van LierCEOAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

coolsport00Commented:
Did you 'enable' the Software iSCSI HBA? (Config tab -> Storage Adapters -> iSCSI Software Adapter, then Properties link, then Configure button, then check 'Enable').

~coolsport00
0
Rik Van LierCEOAuthor Commented:
yes i did enabled that option.
0
coolsport00Commented:
Hmm..ok; well, just to make sure CHAP is not getting in our way, how about disabling it on both ends (ESXi host and SAN) just so we can get the 'standard' connection to work, first. Disable CHAP, rescan HBAs, then see if your LUN shows up...
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Have a look at this video...

Video Tutorial - Adding iSCSI storage to a VMware vSphere ESX/ESXi 4.x host server

http://andysworld.org.uk/2011/06/24/new-hd-video-adding-iscsi-storage-to-a-vmware-vsphere-esxesxi-4x-host-server/
0
Rik Van LierCEOAuthor Commented:
this video is not helping. so far i know what to do.

the nas is connected to a seperate networkcard. does the networkcard and the nas need the same ip? or a different?

and disabling the CHAP also did not solve the problem

0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Is the NAS on the same physical network, and same IP network as the iSCSI Software Initiator, ESXi VMKernel? (ESXi server?)

can you use ping and vmkping on the ESXi console to check you can ping the iSCSI NAS?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
On the Synology DS212 unit,. do you have to add the ESXi iSCSI Initiator Name to the LUN you have created?
0
Rik Van LierCEOAuthor Commented:
2 networkcards are connected in the datacenter to the cisco switch provided by the datacenter.
on this networkcards i have al my vmware's running. i have created a "VM Network" and a "VM Kernel" on this VM Kernel i have assigned an ip: 192.168.0.2 -> i use this to connect to the vSphere Client

then i have a 3rd networkcard on my server and that card has 1 networkcable directly to the networkport of my nas. in vSphere i gave that networkconnection also a "VM Kernel" and an ip adres: 192.168.0.50. On my NAS i have configured the networkcard with 192.168.0.100

is that enough information?
0
Rik Van LierCEOAuthor Commented:
yes i have created a initiatorname and entered that in vsphere
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Check at the ESXi console if you can ping the NAS, and also use vmkping the NAS.

Does the crossover cable work?

You will be able to confirm by using the above ping commands.
0
Rik Van LierCEOAuthor Commented:
with the esxi console you mean the ALT-F2 option?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Correct, at the shell.
0
Rik Van LierCEOAuthor Commented:
ping 192.168.0.50 = 100% packet loss
ping 192.168.0.100 = failed (host is down)

vmkping 192.168.0.50 = failed (host is down)
vmkping 192.168.0.100 = failed (host is down)

0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
okay, no traffic is reaching your NAS.

this is a physical fault, did you state a cable connects NAS direct to Server?

Is this a crossover cable?
0
Rik Van LierCEOAuthor Commented:
no idea, i have bought a networkcable at a hardware store. retail packaging.

and yes the server and nas are connected directly by cable
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
okay, you cannot use a standard network cable to connect two network devices e.g. Server to SAN, there must be a twist, what we refer to a crossover cable, which are not so common.

0
Rik Van LierCEOAuthor Commented:
can you provide me with a layout of creating that cable? so i will create one and drive to the datacenter.
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:


 crossover.jpg
0
coolsport00Commented:
Ha...you know how many yrs it's been since I created a crossover @hanccocka!?? :P hahaha
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
@coolsport00: we don't make any cables, we purchase them! But many years ago, two now "FAMOUS" Microsoft Employees, that I managed as Junior Analysts, were responsible for a ethernet rollout, made all the cables, and made them all WRONG!!!

They made crossovers from the switches to the ethernet sockets!!!!
0
coolsport00Commented:
Oh, I know..we purchase them, as well. It was fun making them.....uhh.....for a little while...very little while. HAHAHA...nice!
0
Rik Van LierCEOAuthor Commented:
does the cable has the same layout on both sides? i guess not?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
no, that why we call it crossover or twisted, as the cables, wies do not go 1 to 1 eyc
0
Rik Van LierCEOAuthor Commented:
are you still available within 1 hour?

i will drive to datacenter and test. if not succesfull we can work from there
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
should be around.
0
Rik Van LierCEOAuthor Commented:
ok i am here but no result
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
with new crossover cable?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
why have you not connected the NAS to the switch?

why connecting it direct? (Gigabit network cards maynot support crossover!)
0
Rik Van LierCEOAuthor Commented:
yes stil same issue when pinging also

and when i connect the nas to the datacenter switch it works directly
0
Rik Van LierCEOAuthor Commented:
because in the datacenter we have a 100mbit connection and not gigabit. and also the whole rack is using that switch so it will have performance issues
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
so you can ping, when connected to switch?

but not when directly connected?

do the lights come in both NICs, on NAS and NIC in server
0
Rik Van LierCEOAuthor Commented:
yes it does. on all scenario's
0
Rik Van LierCEOAuthor Commented:
does my ip on my server nic must be the same ip as on my synology?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
they must be different IP addresses.
0
Rik Van LierCEOAuthor Commented:
and the nic does not need a vm network only a vmkernel is ok
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
correct, iSCSI traffic goes via the VMKernel.

But something is wriong physically, if you cannot ping or vmping the NAS.

and you can ping, when it's connected to switch, but not directly to server?

it could be NIC negioation, servers and NAS are not really designed to be connected directly.
0
Rik Van LierCEOAuthor Commented:
could it be dns?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
No, DNS is not involved in iSCSI.
0
Rik Van LierCEOAuthor Commented:
ok i did not get this to work.. any other ideas?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
with a direct cable?
0
Rik Van LierCEOAuthor Commented:
yep, when connected to the mail datacenter switch it does work

if i can trust you, you can take a look at my vsphere
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I'm afraid it's against EE rules for me to connect to you remotely.

Okay, this leads to possible issues

1. cross over cable is not correct.
2. NAS server does not support cross over cable.
3. Server NIC does not support cross over cable.
4. NIC Speed and Duplex settings mismatch.

Does the NIC in the server state connected?
0
wullieb1Commented:
I'm going to throw in something

Are the 2 machines connected on the same physical IP range???

I.E one server is 192.168.0.10/255.255.255.0 and the other is 192.168.0.11/255.255.255.0

From what i can see the NAS is working when you connect it to the LAN using a port on the switch but it won't connect when you plug directly into the server.

What is your ESX host network configuration???

Does the NIC card that you are plugging the crossover cable into have an IP address???
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Rik Van LierCEOAuthor Commented:
yes that did the trick. i added an different ip range in the nas and the direct networkcard. this works directly...
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.