An NSX administrator has created a segment named WEB-LS from the simplified UI and noticed the segment is not realized on the KVM Transport node.
What are two possible causes for this issue? (Choose two.)
An NSX administrator has created a segment named WEB-LS from the simplified UI and noticed the segment is not realized on the KVM Transport node.
What are two possible causes for this issue? (Choose two.)
The issue occurs if the virtual machines running on the KVM Transport Node are connected to the WEB-LS segment but are in a Powered Off state, as networking configurations often require active VM states to propagate settings. Additionally, if the virtual machines are not connected to the WEB-LS segment, Network Segments will not be realized. Ensuring that the VMs are both powered on and properly connected to the segment are necessary steps to troubleshoot this problem.
B & E should be answer!
Its definetly not A. Computer Manager is used only for deployment/configuration phase to help configure ESXi hosts. Its not necessary. We could configure Tarnsport Nodes on the ESXi hosts without Computer Manager. I've never meet with Computer Manager set for KVM host. KVM host always were configured as a stand alone host. The most suite answer is B and E. C also is not good becaouse we actually don't connect VMs with VDS directly. We connect's VMs with segments or other PortGroups. If it would be hardware problem with KVM host then not only one VM will have some problem. So B and E are the most suite for me.
Computer Manager is used only for deployment/configuration phase to help configure ESXi hosts