<div>
Thanks Aaron,<br />
<br />
So does this means I can deploy NSX in each of my ESXi servers and then expect it to route between two vSwitch / vDS ?<br />
<br />
If yes, I need some guide to do that.
</div>


<div>
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.
</div>


<div>
Hi Aaron,<br />
<br />
So if I add another vNIC to each and every VM (like exchange heartbeat network) what's the default gateway ?
</div>


<div>
Hm...,<br />
That's bit confusing.<br />
<br />
Because the existing gateway vNIC1 in my test VM is already set to 192.168.1.1<br />
<br />
I cannot set the other vNIC2 I the same VM to the same 192.168.1.1 ?
</div>


<div>
Gheist, I used to play &amp;&nbsp;test around Vyatta but it is not free anymore.<br />
<br />
Is there any Windows server equivalent ?
</div>


<div>
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. <br />
<br />
Give it access to both subnets, be the gateway.
</div>


<div>
Aaron, quick question.<br />
<br />
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 ?
</div>


<div>
Plugin the ISP hardware to an Untagged &quot;wan vlan&quot; on a switch, pass the wan vlan to the VM.
</div>


<div>
Is there any other options without using NSX perhaps ?<br />
Because I feel that NSX is to overkill for this purpose.
</div>


<div>
<div class="content wysiwyg-content">
People,<br />
<br />
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 ?<br />
<br />
The idea is to eliminate the physical router appliance so that all routing and firewalling can be done virtually in vSphere environment.<br />
<br />
Thanks.
</div>
</div>


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.

Need some help in VMware NSX to route between two vSwitch in single ESXi server for different Subnet ?

VMware, a software company founded in 1998,  was one of the first commercially successful companies to offer x86 virtualization. The storage company EMC purchased VMware in 1994. Dell Technologies acquired EMC in 2016. VMware’s parent company is now Dell Technologies.

VMware has many software products that run on desktops, Microsoft Windows, Linux, and macOS, which allows the virtualizing of the x86 architecture.  Its enterprise software hypervisor for servers, VMware vSphere Hypervisor (ESXi), is a bare-metal hypervisor that runs directly on the server hardware and does not require an additional underlying operating system.

VMware

A router is a networking device that forwards data packets between computer networks. Routers perform the "traffic directing" functions on the Internet. The most familiar type of routers are home and small office cable or DSL routers that simply pass data, such as web pages, email, IM, and videos between computers and the Internet. More sophisticated routers, such as enterprise routers, connect large business or ISP networks up to the powerful core routers that forward data at high speed along the optical fiber lines of the Internet backbone. Though routers are typically dedicated hardware devices, use of software-based routers has grown increasingly common.

Routers

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.