We were running NSX-V with endpoint associated to vSphere/vCenter endpoint. We just added NSX-T to the mix, and per instructions, vRA should be able to handle both. It did so correctly with the development vRA and vCenter.
However, when I added the new production NSX-T endpoint and associated it to the the production vSphere/vCenter and vRA did its first data collection, it associated it with the Legacy non-NSX cluster. "Production - GS" is the NSX-T cluster. "Production - NGS" is the NSX-V cluster. "Production - GS - Legacy" is non-NSX.
Now caveat to this was that our NSX-V cluster was always named "Production - NGS". Our Legacy was originally named "Production - GS", but then renamed to "Production - GS - Legacy". Then the new NSX-T cluster was created with name "Production - GS".
Any idea why vRA thinks that the "Production - GS - Legacy" is NSXT and not "Production - GS" as the NSXT cluster? Any idea of where to start looking in order to fix?
Damion Terrell . + (He/Him) + . * . + @ + . * . + .
Core IT Service Specialist * . + * . + . + . + * +
UNM – IT Platforms – VIS + . . . . . . . . .
. + . + * . + * .
* . . + . . . . + . + * + .
“You learn the job of the person above you, * + . + * @
and you teach your job to the person below you..” . * +
We solved the problem by renaming the cluster to something new. The previous name had existed prior. We were then able to clean up and remove all references to the NSX-V cluster. And the new Cluster registered as NSX-T.
Damion Terrell . + (He/Him) + . * . + @ + . * . + .
Core IT Service Specialist * . + * . + . + . + * +
UNM – IT Platforms – VIS + . . . . . . . . .
. + . + * . + * .
* . . + . . . . + . + * + .
“You learn the job of the person above you, * + . + * @
and you teach your job to the person below you..” . * +