New Server wont connect to SAN, HBA showing no IP

[RonTurner]

I am setting up a new server, a Dell R730.

Running ESXi 6.5 U2, server setup appears ok but I am not able to connect to the SAN, the HBA is not showing the IP address.

Under Dynamic Discovery I put in the IP address's I assigned to the iSCSI switches on the software adapter.

How do I populate the static discovery tab? is it supposed to pull from the SAN/Compellent?

Thanks!!!

[daphnissov]

You're talking about iSCSI here so there are various pieces in play. In order to get the full picture, we need details of how you've configured your iSCSI vmkernel port, vSwitches, general networking, and how this is connected to your array.

[sean0brien]

Can you try to vmkping from the iSCSI VMkernels to the iSCSI target IP?  Also, make sure that they're in the same IP Subnet / Broadcast domain

# vmkping -I vmkX x.x.x.x

VMware Knowledge Base

Once the dynamic discovery has made contact with the SAN, the SAN will then will relay all available targets to the initiator filling the static discovery tab.

[RonTurner]

Thanks, I tried pinging the iCSI Fault Domains on the SAN from the Host (ESXiA), they didn't respond but I can ping the SAN itself so it appears the iCSI isn't talking.

I do have the correct Subnet etc. This is a new Dell r730 that is replacing our old Super Micro Server.

Also cannot ping the host iSCSI from the SAN in the secure console.

[sean0brien]

Ok that's interesting.  The next thing I'm wondering is... Are you using port binding on the software iSCSI adapter and do you have a separate subnet for iSCSI?

There may be a problem if you don't use prot binding and iSCSI is on the same subnet as let say management.  In this scenario, because the management vmkernel was created before the iSCSI, it will be reflected as that in the esxi routing table and all iSCSI egress traffic will go out the management vmkernel.  To avoid this binding specific iSCSI vmkernels to the initiator would be the answer.

Multi-homing on ESXi/ESX (2010877)

https://kb.vmware.com/s/article/2010877

Port binding should be used when you have a multi-homed ESXi host that has multiple vmkernels for iSCSI traffic on the same subnet.

A few things to keep in mind when configuring port binding

• All iSCSI targets should be on the same subnet as the iSCSI vmkernels
• All the vmkernels must me on the same subnet and broadcast domain

Considerations for using software iSCSI port binding in ESX/ESXi (2038869)

https://kb.vmware.com/s/article/2038869/​

Sean @ vclueless.com

[RonTurner]

Yes I do have Port Binding on the software adapter set up & the iSCSI Sub Nets are not the same as the companies Sub Net.

255.255.254.0 for our Network & 255.255.255.0 for the iSCSI

It is picking up the gateway etc, everything except the iSCSI on the SAN.

The other host works fine. Its going through 2x Dell 3024 stacked switches which are 1GB, the new Server has 10GB but it appears to auto negotiate ok & is showing connected at 1GB & lights on the switch are ok. I can ping everything from the new server except of course the iSCSI on the Compellent/SAN.

I did try the vmkping from the other host & it works fine.

IP/Subnet all appears ok. I just have the Management/vMotion & the 2x iSCSI vmk's setup. They also appear to be ok. Pretty much same settings as the old Super Micro Server.

The Physical Adapters all show up @ 1GB, I have those all on Auto Negotiate because the Server is 10 GB Base T going in the 1GB Dell 3024, getting the new 10GB switch next week so wanting to hook on this switch to migrate from the ESXiB which at the moment is hosting all of our VM's.

[sean0brien]

Thanks for the detailed response!  Just a question on the first line

"Yes I do have Port Binding on the software adapter set up & the iSCSI Sub Nets are not the same as the companies Sub Net."

Do you have multiple subnets for iSCSI ?  Probably just the way I'm reading it, but best to make sure!

Just out of curiosity, can we check if the ESX(new) iSCSI vmks are able to reach ESX(old) iSCSI vmks? 

Sean @ vclueless.com

[RonTurner]

No just the one subnet for the iSCSI, I am unable to ping the other hosts ISCSI VMK's, VMWare support it may be the NIC drivers ..... I had them on the phone, they said the config was ok, just not able to see the iSCSI