LingQin
Contributor
Contributor

Physcial world and virutal world communication.

Jump to solution

Could a VM under nsx-t 3.0 communicate with a physical server directly without going through T1/T0?

0 Kudos
1 Solution

Accepted Solutions
p0wertje
Hot Shot
Hot Shot

Hi,

No. Not directly.

Only routed over t1/t0

Or using a bridge

https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.0/nsxt_30_admin.pdf

page 69

Layer 2 Bridging

With layer 2 bridging, you can have a connection to a VLAN-backed port group or a device, such as a gateway, that resides outside of your NSX-T Data Center deployment. A layer 2 bridge is also useful in a migration scenario, in which you need to split a subnet across physical and virtual workloads.

A layer 2 bridge requires an Edge cluster and an Edge Bridge profile. An Edge Bridge profile specifies which Edge cluster to use for bridging and which Edge transport node acts as the primary and backup bridge. When you configure a segment, you can specify an Edge bridge profile to enable layer 2 bridging.

Or use

Configuring Bare Metal Server to Use NSX-T Data Center

But you are limited to some os

Bare Metal Server Requirements

      

Operating System Version CPU Cores Memory
CentOS Linux

7.7, 7.6 (kernel: 3.10.0-957)

4 16 GB
Red Hat Enterprise Linux (RHEL) 7.7

7.6 (kernel: 3.10.0-957)

4 16 GB
Oracle Linux7.7

7.6 (kernel: 3.10.0-957)

416 GB
SUSE Linux Enterprise Server 12 sp3, 12 sp4416 GB
Ubuntu

16.04.2 LTS (kernel: 4.4.0-*)

18.04

4 16 GB
Windows Server2016416 GB

Cheers,
p0wertje | VCIX6-NV | JNCIS-ENT | vExpert
Please kudo helpful posts and mark the thread as solved if solved

View solution in original post

0 Kudos
6 Replies
p0wertje
Hot Shot
Hot Shot

Hi,

No. Not directly.

Only routed over t1/t0

Or using a bridge

https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.0/nsxt_30_admin.pdf

page 69

Layer 2 Bridging

With layer 2 bridging, you can have a connection to a VLAN-backed port group or a device, such as a gateway, that resides outside of your NSX-T Data Center deployment. A layer 2 bridge is also useful in a migration scenario, in which you need to split a subnet across physical and virtual workloads.

A layer 2 bridge requires an Edge cluster and an Edge Bridge profile. An Edge Bridge profile specifies which Edge cluster to use for bridging and which Edge transport node acts as the primary and backup bridge. When you configure a segment, you can specify an Edge bridge profile to enable layer 2 bridging.

Or use

Configuring Bare Metal Server to Use NSX-T Data Center

But you are limited to some os

Bare Metal Server Requirements

      

Operating System Version CPU Cores Memory
CentOS Linux

7.7, 7.6 (kernel: 3.10.0-957)

4 16 GB
Red Hat Enterprise Linux (RHEL) 7.7

7.6 (kernel: 3.10.0-957)

4 16 GB
Oracle Linux7.7

7.6 (kernel: 3.10.0-957)

416 GB
SUSE Linux Enterprise Server 12 sp3, 12 sp4416 GB
Ubuntu

16.04.2 LTS (kernel: 4.4.0-*)

18.04

4 16 GB
Windows Server2016416 GB

Cheers,
p0wertje | VCIX6-NV | JNCIS-ENT | vExpert
Please kudo helpful posts and mark the thread as solved if solved

View solution in original post

0 Kudos
mauricioamorim
VMware Employee
VMware Employee

Well, a VM on a VLAN-backed segment is under NSX-T 3.0 and being on a VLAN can communicate directly to any server using the physical network routing.

If the VM on an overlay segment, then you either have to route (through T1/T0) or bridge and this will go through the edge node. The only way on an overlay to not go through an edge node is installing NSX on the bare metal server so they both are on an overlay segment.

0 Kudos
LingQin
Contributor
Contributor

How to bridge overlay VMs and physical server via edge? my VM is in overlay and my physical server actually is third party appliance which is impossible to install NSX on it.

0 Kudos
mauricioamorim
VMware Employee
VMware Employee

Have you taken a look here: Layer 2 Bridging ?

0 Kudos
LingQin
Contributor
Contributor

Thanks for such detail explanation.

0 Kudos
LingQin
Contributor
Contributor

Thanks for the advice.

0 Kudos