— Exhibit –-
— Exhibit —
An NSX administrator creates the NSX network in the exhibit:
What destination IP address will Host-A use when sending a VXLAN frame to Host-B?
A.
The IP address of one of Host-B’s new vmkernel ports created during host configuration.
B.
The IP address of Host-B’s management vmkernel port, which is also the VTEP IP address.
C.
The IP address of Host-B’s NSX Controller. The NSX Controller forwards the VXLAN frame to
Host-B.
D.
The IP address Host-B provided to Host-A during VXLAN tunnel setup negotiations.
This answer is typically puting you in confusion. Answer B looks good. Communication with VXLAN frames is done between the VTEP’s. But the management VMkernel port is not the VTEP address:
NSX manager deploys the NSX controllers. A subsequent action after deploying the controllers is preparing the vSphere clusters for VXLAN. Host preparation will install the network VIBs onto hosts in the cluster. These are Distributed Firewall, LDR and VXLAN host kernel components. After this an administrator will create VTEP VMkernel interfaces for each host in the cluster. The individual host VMK interfaces can be allocated IP’s from a pool that can be set up.
I just don’t see how there is enough information to answer this one. I’m pouring over the design guide on page 34 which seems applicable, but I’m still not sure. Also…is the Management network in this graphic the same as the physical transport network?
ESXi HostA should get the VTEP IP address for HostB via the control plane, send the frame over to VTEP on HostB, and the VTEP on HostB decapsulates it and delivers the original frame to VM-B.
I suppose once the NSX host kernel components are installed on the cluster members, yeah, a NEW vmk is created specifically for that use. So A is a valid answer.
With that logic, the management VMK is NOT the VTEP…so B is out.
One of the NSX Controllers may not be on Host-B…so C is most likely out.
It’s the source Host VTEP that will do the identifying of HostB’s VTEP IP, so D is out.
Page 13 on the design guide seems to be applicable to this question:
http://www.vmware.com/files/pdf/products/nsx/vmw-nsx-network-virtualization-design-guide.pdf?src=vmw_so_vex_dcaul_99
I would agree with “A”. I think they are questioning more on knowing when the VTEP vmkernal is created, IE during “host configuration” when you add the cluster to NSX.
In NSX controller view,
show control-cluster logical-switch connection-table 20000 < check which host is connected
show control-cluster logical-switches vtep-table 20000 < check how host is connected
show control-cluster logical-switches mac-table 20000 < check which host has what VM mac.
1. All VTEP interface are register with the VNI the moment they are part of the transport network.
2. Mac address or ARP is generate update the moment VM appears on host.
In that sense B C D is most likely not possible.
B = VXLAN cannot be install onto management vmk. it uses VXLAN stack only.
C = Controller dont forward VXLAN frame
D = Since all host already register with controller on creation hence no VXLAN tunnel neg will happen.