When designing a multi-site NSX deployment, which capability requires Enhanced Linked Mode to function?
A.
Creating Universal Transport Zones
B.
Creating Universal Logical Switches
C.
Cross-vCenter vMotion
D.
Registering a Secondary NSX Manager
Explanation:
https://pubs.vmware.com/NSX-62/topic/com.vmware.ICbase/PDF/nsx_62_cross_vc_install.pdf
Right Answer should be C. (A,B& D) are doable without Enhanced Linked Mode
Using Cross-vCenter NSX Without Enhanced Linked Mode
Enhanced Linked Mode is not a prerequisite or requirement for cross-vCenter NSX. Without Enhanced
Linked Mode, you can still create cross-vCenter universal transport zones, universal switches, universal
routers, and universal firewall rules. However, without Enhanced Linked Mode in place, you must log in to
the individual vCenter Servers to access each NSX Manager instance.
https://docs.vmware.com/en/VMware-NSX-for-vSphere/6.2/nsx_62_cross_vc_install.pdf
3
0
You are right, but I don’t understand what is the “vMotion” in C.
0
0
Moving a VM from a vCenter to another vCenter ( Cross vCenter vMotion)
0
0
Its unclear as the answer says : Answer can be C, also d as we cannot manage secondary NSX managers withiut enhanced linke dmode.
https://docs.vmware.com/en/VMware-NSX-for-vSphere/6.2/com.vmware.nsx-cross-vcenter-install.doc/GUID-D2F6476C-6DE5-45B1-9D84-E834E0539A75.html
Enhanced Linked Mode is not a prerequisite or requirement for cross-vCenter NSX. Without Enhanced Linked Mode, you can still create cross-vCenter universal transport zones, universal switches, universal routers, and universal firewall rules. However, without Enhanced Linked Mode in place, you must log in to the individual vCenter Servers to access each NSX Manager instance.
1
0
I think this is a wrongly worded question. Question should read “which capability requires Enhanced Linked Mode to function?” – Then C will fit properly.
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2106952
But when you add “When designing a multi-site NSX deployment,” one cannot say what the expected answer will be with the options given
0
0
Agree, Clearly confusing question. But thinking of option D, you can register and manage the NSX Managers individually (primary and secondary) with out ELM. So its not a right choice. Similarly A & B are also doiable with out ELM. So only option left is C.
0
0
Its absolutely C because multi site nsx deployment its a deep design with 4 major configuration.
But at page 18 on MULTI-SITE OPTIONS AND CROSS – VC NSX DESIGN GUIDE there is only one time remider for enhanced vmotion.
“for live migrations, an enhanced vMotion must be performed to move the workload and its associated storage s ince the live migration is crossing vCenter boundaries and storage is local to vCenter”
0
0
C
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2106952
•When using the vSphere Web Client, both vCenter Server instances must be in Enhanced Linked Mode and must be in the same vCenter Single Sign-On domain so that the source vCenter Server can authenticate to the destination vCenter Server.
0
0
BTW, part of that new 313Q 2V0-642 dumps are available here:
https://drive.google.com/open?id=0B-ob6L_QjGLpbVl3X1hXbUdteHc
Best Regards!
0
0
“C”
http://blog.jgriffiths.org/long-distance-cross-vcenter-vmotion-requirements/
“When initiating the moves in the web client both source and destination vCenter instances must be in Enhanced Linked mode and in the same vCenter Single Sign-On domain (When using API this is not a requirement)”
“https://kb.vmware.com/s/article/2106952?language=en_US”
0
0
I would think D is a better answer as configuring a secondary NSX manager requires enhanced link mode.
Using Cross-vCenter NSX Without Enhanced Linked Mode
Enhanced Linked Mode is not a prerequisite or requirement for cross-vCenter NSX. Without Enhanced Linked Mode, you can still create cross-vCenter universal transport zones, universal switches, universal routers, and universal firewall rules. However, without Enhanced Linked Mode in place, you must log in to the individual vCenter Servers to access each NSX Manager instance.
1
0