Which would best describe a workload in Compute Cluster 1 attached to a logical switch port group?
A.
Within Compute Cluster 1, Layer 2 would function, but Layer 3 would fail.
B.
Within Compute Cluster 1, Layer 2 would fail, and Layer 3 would fail.
C.
Within Compute Cluster 1, Layer 2 would fail, but Layer 3 would function.
D.
Within Compute Cluster 1, Layer 2 would function, and Layer 3 would function.
A
3
0
Indeed should be A
2
0
A
This has an interesting side effect: if you didn’t add all clusters of a given DVS to the TZ, those clusters you haven’t added will still have access to that Logical Switch. Let’s have a look at the following diagram:
https://telecomoccasionally.wordpress.com/2014/12/27/nsx-for-vsphere-understanding-transport-zone-scoping/
his means that in out hypothetical case, if we were to create a DLR and connect to it that LS we’ve created earlier, DLR instance would get created on hosts in clusters Comp B and Mgmt / Edge, but not on hosts in cluster Comp A:
https://telecomoccasionally.wordpress.com/2014/12/27/nsx-for-vsphere-understanding-transport-zone-scoping/
4
0
In this example, a logical switch created in the transport zone will also be available to the virtual machines in Compute Cluster 1. The reason being, a logical switch is essentially a port group on the VDS and the Compute Cluster 2 is a member of the transport zone. In this case, VXLAN connectivity will work just fine. However, an issue will arise when the logical switch is connected to a DLR.
Unlike the logical switch, DLR instance is only created by the NSX Manager on each host in the transport zone. This would cause a situation where virtual machines in Compute Cluster 1 can communicate at layer 2, but layer 3 connectivity would be broken.
1
0
What’s more, some new 313Q VMWare 2V0-642 dumps are available here:
https://drive.google.com/open?id=0B-ob6L_QjGLpbVl3X1hXbUdteHc
Best Regards!
0
0