search

vmware / ansible-for-nsxt

Ansible delivers simple IT automation that ends repetitive tasks and frees up DevOps teams for more strategic work. This project is to enable this automation for NSX-T installation.
Other
171 stars 145 forks source link

Edge Node not completely configured when attached with LS/Segments and not DVPortGroup #258

Open ysi opened 4 years ago

ysi commented 4 years ago

Hi,

I'm using the module nsxt_transport_nodes for deploying edge node on NSX-T 2.5. This module works fine when the edge node is attached to a Distributes Switch on DVPortGroup. But in my case, the edge node is attached on Transport node, so on a N-VDS and on Segments (even management and data). Opaque network are correctly configured and see on the vCenter (network-oxxx). With my playbook correctly filled, the VM start to be deployed. Once the VM start, network interfaces are not connected and seems to be attached on a "new" network with the same name but not the same ID (network-yyy and not a opaque network). So on NSX, the deployement is stuck. I must re-attached manually on vcenter the vm edge with the right opaque network and restart the VM, for the process to be done.

Is the attachement of a Edge Node on LS/Segments interface working ? If so how to do that ?

vmsysadm commented 4 years ago

Any update on this? I'm having the same issue - deploying Edge node with data interfaces connected to NSX-T 2.5.1 logical segments fails to connect the Edge VM vnics.

madhukark commented 4 years ago

Hello @ysi, @vmsysadm,

The behavior you see where a duplicate network is formed is known. Its an underlying platform issue and we are investigating it. In the meanwhile, please use the Logical Switch UUID while deploying the Edge VMs.

So for example, on NSX-T if your Segment is "edge-data-segment", you can get the logical switch UUID by looking at the object in Advanced Networking Tab. Use this UUID in the Ansible module payload to create the Edge VM.