An NSX Administrator has created a segment named WEB-LS from the NSX UI and noticed the segment is not realized on the KVM Transport node.

An NSX Administrator has created a segment named WEB-LS from the NSX UI and noticed the segment is not realized on the KVM Transport node.
What are two possible causes for this issue? (Choose two.)
A. The KVM Transport node has hardware issues and will not realize the WEB-LS Segment.
B. Since the Compute Manager is disconnected in NSX UI, the WEB-LS segment will not be realized on the KVM Transport Node.
C. The virtual machines running on the KVM Transport Node are connected to the WEB-LS segment, but are in Powered Off state.
D. The virtual machines running on the KVM Transport Node are not connected to the VDS.
E. The virtual machines running on the KVM Transport Node are not connected to the WEB-LS Segment.

microsoft-exams

2 thoughts on “An NSX Administrator has created a segment named WEB-LS from the NSX UI and noticed the segment is not realized on the KVM Transport node.

  1. C & E definitely
    * Hardare defects are always a possible cause, but there are better answer options. – disqualifies A
    * KVM hosts are standalone, not managed by Compute Manager – disqualifies B
    * VTEPs from ALL transport nodes are only participating in segments if needed, e.g. by running VMs. No active VMs means no segment is realized/implemented to run. – check C
    * KVM hosts do not use VDS, the use N-VDS (or OVS, specfically) – disqualifies D
    * Virtual machines on KVM hosts need to be attached MANUALLY to the segment, by grepping the interface uuid and assigning a segment port. Without this step, the new segment ist not realized as no VM needs it – check E

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.