I cannot ping my ESX servers after I plugged in all nics to SAN switches.

I have CAT6 cable from my dedicated SAN switches going to three ESX/i servers that each have 8 nic ports. On the ESX server, I have one nic going to one switch and the next to the second switch (crossing them back and forth to both SAN Switches. I have all eight nics plugged in from all three esx servers. Now, when I had my esx servers connected to a little 5 port switch that connects into my LAN, I could ping the esx servers. Now when their connected to my switchs, which is going to my SAN, I can not ping my esx servers.

My SAN is all functioning and storage was all allocated and configured, I just cant get to ESX server ever since I connected all nics (8) from each esx server to SAN switchs?

Thanks,

nimdatx

Thanks,

nimdatx
LVL 1
Jaime CamposAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
coolsport00Commented:
SAN Switches are not network switches. They are used to connect your host(s) to your SAN. You need your host NICs to be plugged into your network/core switch. SAN switches are connected to via HBAs, not NICs.

Regards,
~coolsport00
0
 
bgoeringCommented:
Did you set up nic teaming/load balancing on esx and ether channel in the switch?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
markzzCommented:
nimdatx
You need to make a logical separation with regard to networking.
If you have 8 NIC's on each host I'd suggest
2 NIC's for your Service Console/vMotion activities (Connected to your conventional Network, therefore routable)
2 NIC's for Storage IP (Connected to your Storage Switches, non routable)
2NIC's for VM Guest traffic (Connected to your conventional Network and routable)

The other 2 are spare of bind them as you see fit.
0
 
Jaime CamposAuthor Commented:
ESX/Server 1

VM1 - Unidentify Network
VM2 - Unidentify Network
VM3 - Good

Did I setup my nics incorrecly? Please see pic.
 ESX Server nics
0
 
Jaime CamposAuthor Commented:
ESX 2

All VMs seem to have an IP address, heres the pic.

 ESX2 Nics
0
 
bgoeringCommented:
It appears that you have 4 iSCSI on 4 different networks - all routed through the same vswitch. I don't see any VLANs configured. What is your subnet mask for those networks?
0
 
coolsport00Commented:
My initial assumption was he was using FC SAN...oops. :P

But even so, you still don't connect all 8 to the SAN switch, correct "bgoering"?

~coolsport00
0
 
bgoeringCommented:
I am not sure what he means by "SAN" switch, for iSCSI it is just a network switch that you are using for iSCSI connections. Nothing says it can't be used for other purposes also. But it looks like he has a number of subnets going on (assuming a mask of 255.255.255.0) and they would typically be segregated by VLANS. If the mask is say, 255.255.0.0, it should work the way he has it with no VLANs.

I am guessing that he is using the wide subnet mask because it was indicated that it all worked going through a 5 port switch. And now he has replaced that 5 port with two independent switches (deduced from crosslinked)

@nimdatx: if this is all one flat layer two network you also need to make sure the switches are linked to each other. If not please provide more detailed information if my assumptions above are incorrect.

@coolsport00: My first look I thought FC also, but then saw CAT 6 cables...

0
 
coolsport00Commented:
Yeah, that's what kinda confused me, as well (CAT6 cables). Gotcha now :)
0
 
Jaime CamposAuthor Commented:
iSCSI - VMotion & IP Storage Ports

iSCSI4
VLAN: None (0)
IP Adress: 192.168.133.1
SM: 255.255.255.0

iSCSI3
VLAN: None (0)
IP Address: 192.168.132.1
SM: 255.255.255.0

iSCSI2
VLAN: None (0)
IP Address: 192.168.131.2
SM: 255.255.255.0

iSCSI1
VLAN: None (0)
IP Address: 192.168.130.2
255.255.255.0

Management Network - VMotion & IP Storage Ports

Management Networks
VLAN: None (0)
IP Address: 192.168.1.175
SM: 255.255.255.0

VMotion - VMotion & IT Storage Ports

VMotion
VLAN: None (0)
IP Address: 192.168.134.2
SM: 255.255.255.0
0
 
Jaime CamposAuthor Commented:
You r correct about the "SAN Switches" as they do work with other devices. I'm thinking since in my environment they are dedicated to SAN storage (MD3000i) that they r "SAN Switches. Your right, sorry to confuse you guys.

I believe I'm usinga  layer 2 Network, but I do not have both dedicated switches connected together. The SAN, however is connected to an existing switch on the LAN.

I'm sorry, I dont have time to do a visio drawing but I'll do a real quick drawing. It's easier for to explain if I draw it out.
0
 
Jaime CamposAuthor Commented:
Quick-drawing.pdf

Thanks,

nimdatx
0
 
Jaime CamposAuthor Commented:
Did my time run out? Should I start a new comment? I'm right at the finish line guys. I appreciate all your help guys.
0
 
bgoeringCommented:
OK, I am guessing you are running a bunch of subnets over a single layer 2 network - while it MAY work, you aren't really getting any benefit from doing it that way. It appears from your drawing that the switches are crosslinked through your LAN switch.

What make and model are all three switches? I expect that the problem is that you have no ether channel configured from your switches to the esx servers. Go into the vswitch properties under nics and move three of them down to standby status (or just unplug three of the nics) and see if it works better -- if that solves it you need to do some additional setup on your switches.
0
 
bgoeringCommented:
BTW - I will be leaving in 20 minutes or so and it may be late before I get back on, but coolsport00 if he is still available may be able to assist you setting up your ether channel if that is what is needed.
0
 
bgoeringCommented:
Maybe I am not real clear on the issue. You say you cannot ping your esx servers -- are you trying to ping the iSCSI ports or the Console port? What are you trying to ping from? What is the ip and subnet mask of whatever you are trying to ping from? Do you have a router in there somewhere?

Basically if you have a workstation at 192.168.1.x 255.255.255.0 and you can get to the console, but not the iSCSI ports that may be normal. As I assume this is a flat layer 2 network try adding secondary ips to your workstation for the other networks and then see if you can ping iSCSI ports. Can you ping your storage?
0
 
Jaime CamposAuthor Commented:
The two ISCSI switches are Powerconnect 5424 and my LAN switches are 2724. When I unplug certain nics on ESX Serers the link on VMs all work. So I imagine your solution is correct.
0
 
Jaime CamposAuthor Commented:
I can ping
ESX Host 1 - 192.168.1.170 - Pings successful
VM1 - 192.168.1.171 - Doesnt ping ip address
VM2 - 192.168.1.172 - Doesnt ping ip successful
VM3 - 192.168.1.173 - Pings successful

I am pinging fron the same subnet - My IP is 192.168.1.24 - 255.255.255.0
I can not ping storage from my LAN.

THANKS SO MUCH for the help.
0
 
bgoeringCommented:
OK, then you need to configure etherchannel on your switches. I am pretty much out of time today (and more familier with Cisco stuff anyway) so you may want to remove Windows 2008 from the zones and add networking. Might pick up a Dell switch expert quicker that way :)

I will check in tomorrow and if still not solved will help you to set up an etherchannel. Do you have a router in your network?
0
 
bgoeringCommented:
yes - wherever you have a nic team you will need switch configuration to go with it.
0
 
Jaime CamposAuthor Commented:
Yes a Adtran 5000. No problem. Thanks so much. I'm calling dell and getting the remote tech to help. When he initialed, he went super fast and wouldn't explain much. I alos didn't have all my cables in plugged into ESX servers. I was left in the dust by the time he exited the remote session. I'm trying bgoering, and my install  of our new EMR version is scheduled for Monday.

THANKS SO MUCH, I really appreciate your time and I wouldn't be asking so many questions if I had more time to research. This project is real close on completing. All I need is to get this issue resolved, transfer my data from old fileserver, transfer DHCP and test. :-)

nimdatx
0
 
coolsport00Commented:
Gosh...sorry was unavailable; left work and just got home...so where are we at "nimdatx"? Are you gonna call Dell?
0
 
Jaime CamposAuthor Commented:
I'm waiting for a callback from Dell's remote assistence team. No call back yet. The reason I decided to call Dell is because the first rep had remoted and made his configuration changes to get me up, but the whole thing was so disorganize that I wasn't prepaired with all my cables. So, he just got it connected and diconnected. I've been trying to contact the same guy, but no response. I contacted my account manager and supposely they are to call me back asap.

Meanwhile, I disabled the vmnic5 on ESX Server #1 (see 1st pic) and my VMs were able to obtain an IP address. I'm reading on nic teaming and vswitches, not sure what is the best way to setup all my nics for the best performance for users connection into our EMR Application, which will be on the SAN.

I have nic (o) on each server, which is the first nic I used to run network configuration when installing ESX/i on the server going to my LAN Switch and my ESX servers work. I initially had nic (o) on ESX server going to both my powerconnect 5424 switches, which are directly connect to SAN Storage. I want to make sure that I setup my vnics/vswitches to satisfy performance and backup.

Thanks,

nimdatx
0
 
coolsport00Connect With a Mentor Commented:
When you have time "nimdatx"...here is the iSCSI SAN Config Guide:
http://www.vmware.com/pdf/vsphere4/r41/vsp_41_iscsi_san_cfg.pdf, which might stear you in the right direction. Ch. 2 begins on Config'ing your initiators. Hopefully this Guide, along with "bgoering's" ether-channel KB will finalize things for you. Keep us posted.

Regards,
~coolsport00
0
 
Jaime CamposAuthor Commented:
Thanks so much.

Last question I have a hard time getting a solution for migrating my data. Once I'm ready to use robocopy (gui version) and I transfer to my new fileserver, what is the best way to re map users drives to the new data drive location, which will be on a differant name and ip address.

For example; everyone is mapped to \\192.168.1.2\Share name and now they will have to be redirected to \\192.168.1.172\New share name. What would you do to ensure all users were pointed to the new fileserver? From my understanding I can change the new DC ip address and name to the old DC ip, however since they are DC, it's not that simple and may be risky. What do you suggest?
0
 
coolsport00Commented:
I don't have an easy answer for you there "nimdatx". What we use for our shares?...DFS. So, whether I change the IP or name of our fileserver, all I have to do is modify the DFS share on my DFS server. Hmm....well, how are you mapping everyone now? We use login scripting...

~coolsport00
0
 
bgoeringCommented:
You would probably be better off making a new question in appropriate zones for your mapping drives question - this is getting a bit off topic ....
0
 
Jaime CamposAuthor Commented:
Thank you so much
0
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.

All Courses

From novice to tech pro — start learning today.