dmz? nsx? multiple interfaces on a vm that needs external and internal communication

[rastickland]

        there is a request in my org to have a vm (in the dmz or not) that has both internal interfaces to the network as well as public / external internet access.   The discussion internally has been straight forward as to that it needs to be done, but the question(s) has been as to best do it.   the push internally has been to go virtual with this but we have not implemented nsx yet and i am asking if the "protections" offered by nsx would be sufficient for something like this?    thoughts?

[Sreec · Accepted solution]

For sure this is achievable. Going via the traditional way , we will have DMZ specific F/W and DC F/W for ingress and egress traffic ,assuming you have a similar connectivity model from the servers to those segments , NSX can certainly protect your workloads. How you implement the F/W and Routing is purely a design choice.

[rastickland]

i talked to my NSX dealer yesterday and we talked about the DMZ anywhere solution and i think that is something looks very promising as well.  Thank you for the reply!