Two virtual machines are attempting to communicate. The VMs are on different NSX Logical
Switches on separate physical hosts. What NSX component is responsible for facilitating
communication between these VMs?
A.
NSX Manager
B.
Distributed Logical Router
C.
An NSX Controller
D.
The Edge Service Gateway
Answer is B I think. NSX controller helps if ESX1 on which VM1 resides doesn’t know how to get to VM2 on ESX2 (in that case ESX1 sends a control message to NSX controller asking for required info).
That being said, truly, the component that helps logical switch1 talk to switch2 is DLR. That’s the guy who is going to route the packet. Disagree?
NSX DLR is a virtual machine and not a component.
Answer is C.
NSX DLR is a service not a component, but you are right the answer is C
Vmware training module 3.4 explains all the NSX components. The NSX Controller receives the updated routing tables and switch configuration information to be distributed to the hosts. The DLR is the NSX component that creates the routes from one host to another host (this scenario). Answer is B
Read thru the VXLAN Deployment
The NSX Manager is responsible for deploying the NSX Controller instances, and preparing the vSphere clusters for VXLAN. The ESXi hosts will provide network information to the NSX Controller using the User World Agent, allowing the NSX Controller to maintain network-state information, which will be cached locally.
http://www.educationalcentre.co.uk/revision-notes-vmware-network-virtualization-fundamentals-course/
The Question above is “. What NSX component is controlling this communication”
Answer should be The NSX Manager
agree/disagree?
I think B is the answer
I’d go with C NSX Controller
Also from Module 3.4:
NSX Manager – seen at same level as vCenter on the Management Plane (NO)
Distributed Logical Router – Performs east-west “in-kernal” routing (No)
An NSX Controller – Distributes routing and switching configuration and updates to the hosts (Most likely)
The Edge Service Gateway- North-south routing between private and external networks (NO)
The answer is B.
The DLR is unique because it enables each vSphere hypervisor host to perform L3 routing between virtual and physical subnets in the kernel at line rate. The DLR is configured and managed like one logical router chassis, where each hypervisor host is like a logical line card. Because of that the DLR works well as the “device” handling the East-West traffic in your virtual network. You know, the traffic between virtual machines, the traffic between virtual and physical machines, all of that backend traffic that makes your application work. We want this traffic to have low latency and high throughput, so it just makes sense to do this as close to the workload as possible, hence the DLR.
https://blogs.vmware.com/networkvirtualization/2013/11/distributed-virtual-and-physical-routing-in-vmware-nsx-for-vsphere.html#.V47Qovm7hBc
C