Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Need some help in VMware NSX to route between two vSwitch in single ESXi server for different Subnet ?
People,
Using VMware NSX v6, can anyone here please assist me what is the steps that I can use to route traffic between two different vSwitch which contains VM with different IP subnet in a single ESXi server ?
The idea is to eliminate the physical router appliance so that all routing and firewalling can be done virtually in vSphere environment.
Thanks.
Using VMware NSX v6, can anyone here please assist me what is the steps that I can use to route traffic between two different vSwitch which contains VM with different IP subnet in a single ESXi server ?
The idea is to eliminate the physical router appliance so that all routing and firewalling can be done virtually in vSphere environment.
Thanks.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
A physical router adds vlans and interfaces but nsx calls them segments. The VMware blog explains it well
https://blogs.vmware.com/networkvirtualization/2014/07/getting-started-vmware-nsx-part-ii-building-virtual-networks.html
https://blogs.vmware.com/networkvirtualization/2014/07/getting-started-vmware-nsx-part-ii-building-virtual-networks.html
Thanks Aaron,
So does this means I can deploy NSX in each of my ESXi servers and then expect it to route between two vSwitch / vDS ?
If yes, I need some guide to do that.
So does this means I can deploy NSX in each of my ESXi servers and then expect it to route between two vSwitch / vDS ?
If yes, I need some guide to do that.
Why not just add another vnic to the VM? While you can do what you are asking, You may want to consider not just duplicating your physical setup but redesigning based on the virtual capabilities open you.
Hi Aaron,
So if I add another vNIC to each and every VM (like exchange heartbeat network) what's the default gateway ?
So if I add another vNIC to each and every VM (like exchange heartbeat network) what's the default gateway ?
The default gateway is what the nic uses to get out of its subnet, so to other subnets on your lan, or the Internet.
So the default gateway stays on the nic that already gives you access to the Internet.
So the default gateway stays on the nic that already gives you access to the Internet.
Hm...,
That's bit confusing.
Because the existing gateway vNIC1 in my test VM is already set to 192.168.1.1
I cannot set the other vNIC2 I the same VM to the same 192.168.1.1 ?
That's bit confusing.
Because the existing gateway vNIC1 in my test VM is already set to 192.168.1.1
I cannot set the other vNIC2 I the same VM to the same 192.168.1.1 ?
Gheist, I used to play & test around Vyatta but it is not free anymore.
Is there any Windows server equivalent ?
Is there any Windows server equivalent ?
Back to your original question, nsx can totally do this. The blog post goes through it pretty well and the basic concept of a virtual router is the same as a physical router.
Give it access to both subnets, be the gateway.
Give it access to both subnets, be the gateway.
Aaron, quick question.
so in the real world, when using NSX Virtual Appliance, does that means the physical appliance will be just Layer 3 switch connected to the modem / FIbre Channel aggregator ?
so in the real world, when using NSX Virtual Appliance, does that means the physical appliance will be just Layer 3 switch connected to the modem / FIbre Channel aggregator ?
Is there any other options without using NSX perhaps ?
Because I feel that NSX is to overkill for this purpose.
Because I feel that NSX is to overkill for this purpose.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial