Secure workloads running on Windows Server 2016 bare metal servers.

You can provide connectivity and security to applications or workloads between:
  • Physical workloads (bare metal server) and virtual workloads
  • Virtual workloads and physical workloads (bare metal server)
  • Physical workloads (bare metal server) and physical workloads (bare metal server)
The workloads can be on overlay or VLAN-backed networks and the workloads must not be outside of the perimeter of a Windows Server 2016 bare metal server. As part of the configuration, the NSX Agent is installed on the bare metal host. Network connectivity between the application IP address of the Windows bare metal server, NSX Agent and NSX Manager needs to be established before applying DFW rules to protect workloads.

Apply DFW rules to secure ingress and egress traffic flowing through the L2 and L3 networks between workloads on a Windows Server 2016 bare metal server and virtual or physical workloads.

A couple of use cases where ingress and egress trafffic is filtered at the Windows bare metal server.

Traffic between Virtual and Physical Bare Metal Workloads

Traffic between Physical Bare Metal Workloads

Before you apply DFW rules to the Windows bare metal workloads, integrate NSX-T on the Windows Server using Ansible scripts. To install and integrate NSX-T on a Windows bare metal server, refer to the Secure Workloads on Windows Server 2016 Bare Metal Server topic in the NSX-T Data Center Installation Guide.