[Last Call] Learn about multicloud storage options and how to improve your company's cloud strategy. Register Now

x
?
Solved

VMware iSCSi Storage Network Connection Issue

Posted on 2013-11-18
18
Medium Priority
?
886 Views
Last Modified: 2013-11-19
Hi,

I’m having issues with connecting my SAN Storage device to my VMware environment.  The Hosts are having trouble seeing the LUNS on the synology device.  I recently changed my network around with different VLANs and separating the traffic in different ways than what I was doing before.  Before, I did separate the traffic, but I put everything on the 10.5.1.1 /255.255.255.192 sectioning off the network with different VLANs.  I don’t know what I’m doing wrong or why the Hosts wont see the LUNS on the device.  I’ve set this up before, but I’m completely stumped on why its not working.  I’ve recanned the Storage Devices and VMFS Volumes multiple times, Enabled/Disabled the iSCSi target on the device (with a reboot) but still no luck.

Attached is my complete document of what I have set up with screen shots for very easy reference.

Please let me know as soon as you can on what I'm not seeing here.

Thanks!
VMware-iSCSi-Storage-Network-Con.docx
0
Comment
Question by:Lumious
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 8
  • 8
  • 2
18 Comments
 
LVL 123
ID: 39658612
can your ESXi server vmkping your SAN IP Address?

(not ping!)
0
 
LVL 9

Expert Comment

by:dipopo
ID: 39658721
Exactly what I was thinking, can you vmkping the synology from the ESXi hosts, also are you using iSNS on the Synology? it simplifies scanning for iqn's
0
 

Author Comment

by:Lumious
ID: 39659059
Hi,

I will check on both this morning.

Stay tuned.

Thanks
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:Lumious
ID: 39659147
Hi,

I tried to vmkping from Host to Target through Putty and it didn't work.  I tried to vmkping from Windows machine to Target and it didn't work either.  I've attached screenshots showing what I typed in.

iSNS on the Synology device for the 3 LUNS is not enabled.  Should I enable it?  Also when enabling iSNS it also asks for a iSNS Server, do I have to put one in?  What is that actually?

Please let me know when you get a chance.

Thanks
11-19-2013-7-05-47-AM.jpg
11-19-2013-7-02-51-AM.jpg
0
 
LVL 9

Expert Comment

by:dipopo
ID: 39659173
You are only required to vmkping from host to storage interface.

Isns is just a name server that stores own like a DNS server does a records.

The symbology IP address for the storage interface is what you should enter for isns.

If you cannot vmkping from the host, check each part of your network.
0
 
LVL 123
ID: 39659335
Your networking is incorrect, from host to iSCSI SAN, and hence why your LUNs are not connectecting.
0
 

Author Comment

by:Lumious
ID: 39659391
Hi,

Hanccocka:
- Could you explain what you are seeing in a little more detail?

Thanks
0
 
LVL 123
ID: 39659419
10.5.4.87 is your ESXi Host

10.5.3.52 is your SAN.

vmkping, cannot send a ping request to your iSCSI SAN, it's therefore unreachable.

What IP Address does your vmkernel portgroup have, and is it on the same network as your SAN?
0
 

Author Comment

by:Lumious
ID: 39659466
Hi,

See attached for Network details for Hosts and SAN.

Please let me know what you think and any suggestions on how to go about this.

Thanks
11-19-2013-9-43-37-AM.jpg
11-19-2013-9-44-59-AM.jpg
0
 
LVL 123

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 total points
ID: 39659501
the first thing, I've spotted, are you using multi path, which is usually best practice and recommended for iSCSI.

see my EE Article, Step by Step Tutorial Instructions with Screenshots

HOW TO: Add an iSCSI Software Adaptor and Create an iSCSI Multipath Network in VMware vSphere Hypervisor ESXi 5.0

HOW TO: Enable Jumbo Frames on a VMware vSphere Hypervisor (ESXi 5.0) host server using the VMware vSphere Client

IP Addresses look okay, but maybe you VLANs are incorrect. You are using a VLAN 103, is this correct, and also tagged on ESXi, trunk, switches etc
0
 

Author Comment

by:Lumious
ID: 39659566
Hi,

Yes I am using multipath, those articles I actually followed which are great.  Since we verified the IP Addressing, next is verifying the VLANs, tagging, switches, etc...

I've attached an image from my HP ProCurve switch which shows the VLANs.  VLAN 104 is where the ESXi hosts (VM Network and Management Network) are connected to on those ports.  VLAN 103 is where the the iSCSi Network cables are connected into from the Hosts with the "untagged" ports for where the SAN connects in to.

Quick question:  When initiating the iSCSi initiator, it gives it a Name by default.  If that name is changed by clicking configure, will that effect the connection to the LUNS?  See attached image.

Please let me know when you get a chance.

Thanks
HP-ProCurve-VLANS.jpg
11-19-2013-10-16-56-AM.jpg
0
 
LVL 123
ID: 39659578
Name is populated from iSCSI discovery, I would leave as is, and do not change.

okay, if using untagged ports, this network interface should be connected to two physical nics on the switch, and nics connected to SAN.

no tag is required on the SAN or ESXi host.
0
 

Author Comment

by:Lumious
ID: 39659691
Hi,

If the name that the iSCSi discovery populated got changed, would that effect the connection to the LUNS?

There are 2 ports on the HP ProCurve that the the NICs from the SAN are connected to which are untagged.  They are part of VLAN 103 as well.  

The ESXi hosts each have 2 cables that are dedicated for (VM-MGMT Network VLAN 104), (iSCSi Network VLAN 103), and (vMotion Network VLAN 102).  Each of these ports are tagged accordingly to where they are plugged into the HP ProCurve as you can see from the tagging in the previous image of the HP ProCurve Switch.

When you mentioned that "no tag is required on the SAN (which they aren't tagged, they are "Untagged" as you can see from the image) or the ESXi host: The cables that are used from the ESXi Host for the iSCSi, which are plugged into the ports of the HP ProCurve on VLAN 103, are you saying I'm not supposed to tag those?

Please let me know when you get a chance.

Thanks
0
 
LVL 123
ID: 39659703
changing the name is not going to stop vmkping from working.

All looks okay, but clearly VLAN 103 is not working correctly.

you have not tagged the virtual machine portgroups with 103 ?

if you remove all the VLAN 103 info, can you ping the SAN?
0
 

Author Comment

by:Lumious
ID: 39659820
Hi,

Wow....we all missed this one....JUMBO wasn't enabled on the VLAN ports for the HP ProCurve.  I set JUMBO to 9000 on all the NICs in VMware but not on the VLANS.

My LUNS came up right away after making the change on the Switch.

Thanks
0
 
LVL 123
ID: 39659826
Jumbo Frames should only be on your Storage Network, as per my EE Article mentioned earlier!

odd, you should still have been able to ping?

does vmkping still work?
0
 

Author Comment

by:Lumious
ID: 39659838
Hi,

After enabling JUMBO on the VLANS, I was then able to Ping everything and my LUNS came right up on each host in VMware.

Thanks
0
 
LVL 123
ID: 39659865
no problems.
0

Featured Post

[Webinar] Lessons on Recovering from Petya

Skyport is working hard to help customers recover from recent attacks, like the Petya worm. This work has brought to light some important lessons. New malware attacks like this can take down your entire environment. Learn from others mistakes on how to prevent Petya like worms.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The question appears often enough, how do I transfer my data from my old server to the new server while preserving file shares, share permissions, and NTFS permisions.  Here are my tips for handling such a transfer.
Ransomware is a malware that is again in the list of security  concerns. Not only for companies, but also for Government security and  even at personal use. IT departments should be aware and have the right  knowledge to how to fight it.
Teach the user how to edit .vmx files to add advanced configuration options Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:

650 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question