This is a known bug that was resolved in later releases. On that version you either manually deploy the Edge VM or choose any VSS/VDS portgroup and after the VM is deployed manually change the VMs connection to an N-VDS segment in vCenter.
It is the intra tier link and I do not see any auto created segment to use as intratier.
I don't understand which segment I have to choose
I just got confused by your last message.
Your first post was about not being able to choose N-VDS segment to connect to the Edge VM's N-VDS uplink. This is the bug I mentioned in version 2.4. If this is your problem and I understand you have a fully collapsed cluster, with Edge VMs connected to the N-VDS of NSX-T prepared hosts. To do this you have to create the appropriate VLAN backed segments on the host N-VDS and connect the Edge VM vnics to these segments. Since this cannot be done in NSX-T UI, just select any VSS/VDS PortGroup and manually edit the Edge VM properties to connect to the right segments.
What you mention in your second post is intra tier link. This is something totally different and is just a segment that NSX-T creates to interconnect Tier-0 and Tier-1 routers. This by default uses the 100.64. subnet and cannot be seen in the NSX-T UI a normal segment.
Take a careful look at the Reference Design Guide, as it should have the answers you need.
Hi and thanks,
I was reffering to Intra-Tier Transit Link: Internal link between the DR and SR, using a transit logical switch. as described here: VMware NSX-T: Distributed Routing & Centralized Routing
Anyway I understand, as you said, the bug that doesen't show me n N-VDS segment the deploy edge wizard.