Creating virtual NIC on different IP subnet

Hi,
I have VMware ESXi running with one Win2K8 DC and two windows 2K8 as virtual machines on an HP Proliant DL380 server w/ two physical NICs. One of the physical NIC is connected to the physical switch but the other one's not. I am planning to build a SQL cluster on a single VMware ESXi host.
I have my public NICs on virtual machines (one DC and two nodes) connected on one ip subnet and can ping one another with no problem.

But, I'm having trouble getting the second virtual NIC added on a different subnet for heartbeat traffic. I added a new virtual switch and the NIC, but it shows as disconnected on VMware configuration screen. I even the newly added virtual NIC on the two VMs with IPs from the same private IP subnet, but they don't ping.

Do I have to physically connect the second NIC to a physical switch? What shall I do to create second private LAN and use it as cluster's private network?

Sorry, I'm new to VMware and trying things out in the LAB right now.

Any assistance would be much appreciated!
Thanks,
Sharad
raisharadAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Paul SolovyovskySenior IT AdvisorCommented:
Add a second vswitch and add a nic to it.  Attach a second virtual nic from each node of the cluster( windows boxes) to this vswitch after creating a virtual machine portal group on it
0
raisharadAuthor Commented:
Ok, I think this is what I'm not getting. I did add a vswitch (vswitch2) and added NICs (secondary NICs from those two Win2K8 Nodes) to it. On the Host's Configuration tab, the NIC shows up as disconnected (red X) on the new switch.

Do I have to group these NICs on the new switch somehow simulating a crossover connection? But, how?
Thanks,
0
Paul SolovyovskySenior IT AdvisorCommented:
Is the physical nic connected to the network (it needs to be).  If the heartbeat is just between the 2 windows nodes you can setup the vswitch without any nics and it will act as just a layer 2 switch.  

On the windows nodes make sure you have a second nic on each guest OS and also make sure that when you edit properties that it's connected (check box)
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

msmamjiCommented:
If you just need to have a heartbeat network, then you don't have to necessarily have the second VSwitch mapped to a physical NIC. Have a look at the following thread.
http://www.experts-exchange.com/Software/Virtualization/Q_25122061.html
Since you have both VMs on the same single ESX host  then follow the first comment on the thread.

Regards,
shahid
0
raisharadAuthor Commented:
The link looks like it has the right info for my effort of doing the same thing.
I will try and let you all know.

Thanks a million for the link,.
I googled many ways, but that link never came up...
0
raisharadAuthor Commented:
I've screen captured my VLAN configuration and attached it here. Can you tell where I am going wrong with my VLAN configuration?
You can clearly see red X on the 2nd VLAN.

Much appreciated!
Thanks,
0
raisharadAuthor Commented:
Here is the attachment
VLAN-VMware.jpg
0
msmamjiCommented:
your virtual switch vSwitch1 should not be bound to vmnic1. It shouldn't be assigned to any NIC at all.

Regards,
Shahid
0
raisharadAuthor Commented:
I did that too and the followings after I posted the above posting:

1. Created new VSwitch w/o binding any physical NIC to it.
2. Added 3rd NICs individually on two nodes (disabled previous heartbeat NICs)
3. Added new NICs to this new switch
4. Assigned 10.0.0.0 IP addresses to this new subnet
5. Tried to ping each other, can't (I can however ping these addresses locallly on each node)

I can still however ping 192.168.0.0; public network.

stumped!
Thanks for working with me on this...
0
Paul SolovyovskySenior IT AdvisorCommented:
Take a look at the bindings on virtual nic, disable ipv6.  Just for giggles attache the vmnic1 to a standalone switch port without being on your production vlan/subnet
0
raisharadAuthor Commented:
Ok, I will disable IP6 on these NICs and also attach vmnic1 to a physical switch and see if that brings up the down status to up.

I will update the case as soon as I get a chance to apply these new changes to my lab setup.
Thanks a lot,
0
raisharadAuthor Commented:
Tried everything, but couldn't simulate the heartbeat VLAN function on VMWare ESXi single host system. Even tried connecting the second vmnic1 to a physical switch, no help.

Is it even possible to create secondary virtual LAN on vmware?
Thanks,
0
raisharadAuthor Commented:
I think this is my issue: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1008451

When I try to trace route to second node on the 2nd ip subnet, it fails even on the first hop! While, this is not a problem with the public IP subnet. When I type route print, I can see 10.0.0.0 network having the correct interface as its Gateway, yet it doesn't know how to use that interface and get through. I'm dumbfounded by not knowing it it's a VMware issue (very new on this) of not supporting something like this or a network routing issue. If any of you have experienced this already and know a solution, please, please let me know.

In the mean time, I will try adding static routes in the box and see. Glad my networking skills will come in handy here.

I will post my findings,
Thanks,
0
raisharadAuthor Commented:
I'm increasing the point value...
0
msmamjiCommented:
I will try to help with the primary problme and this should work.
Set up one vSwitch with a port group, which has no assigned NIC and connect the two VMs to the vSwitch with this port group.
What the VMs IP config in this setup? for both NICs? for both VMs?
Regards,
Shahid
0
rvivek_2002Commented:
If you want two VMs inside an ESX host to talk to each other , ther is no need of connecting it to a physical NIC.

 1. On the VMs create second NIC (on each VM)
2. Create a Vswitch (No Physical NIC to be attached)
3. Create a Vrtual Machien prort group (assign a  suitable name like Private)
4. Associate the Second NIC of the VMs to the Private port group.
5. If the VMs have IP ddresses on the second NIC from same subnet  they should ping each other.
0
raisharadAuthor Commented:
oops, I'm sorry I couldn't get back to these two new comments any earlier. Reason, 'cuz I couldn't play with my system as planned over this weekend.

However, I think I have tried the last method as suggested by rvivek_2002, but I will give it a try and post the result.

Thanks,
0
raisharadAuthor Commented:
Tried both methods, none worked. Now, I even lost the ability to ping between nodes on public IP. My ip assignments are:

Public Net: Node1: 192.168.1.22/24; Node2: 192.168.1.24/24
Private Net: Node1: 10.10.10.10/8; Node2: 10.10.10.11/8
Thanks,
0
raisharadAuthor Commented:
http://www.vmware.com/pdf/esx3_vlan_wp.pdf
As per this, I would need a physical switch and segment it in two separate VLANs. Create two ISL trunk ports and tag them with individual VLAN in VMware.

Is this the missing link? Did you guys always presumed that I had a physical switch with corresponding VLANs? Please let me know if this "is" the required setup...

Thanks,
0
msmamjiCommented:
Can you post the screen capture of your n/w config once again, the state in which it is now
0
raisharadAuthor Commented:
As soon as I could get my hands on it.
Thanks,
0
raisharadAuthor Commented:
here is the new screen shot of my VMWare Networking:
Thanks,
VLAN-VMware.jpg
0
msmamjiCommented:
If you say you have lost connectivity to even the public NIC by removing the adapter from vSwitch2, I sernse that you might have mixed the NICs assigned to the VMs. Meaning that, Inside one or both VMs, you might have assigned public n/w IP address assigned to private NIC (attached to vSwitch2) and/or have assigned private n/w IP address assigned to public NIC (attached to vSwitch1).
Check to make sure.

Regards,
Shahid
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
raisharadAuthor Commented:
I couldn't get the heartbeat network on my VM installaiton work ever. I followed every suggestion precisely, but it never worked.

I would however, like to distribute points based on the different level of suggestions provided by each expert... These suggestions did help me learn somrthing about VMWare.

Thanks,
Sharad
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
Apple Software

From novice to tech pro — start learning today.