An administrator successfully adds a Nutanix cluster to the NDB control plane but cannot provision a database server VM. The provisioning wizard does not display any available networks.
NDB profiles are scoped by database engine and deployment type. A Network Profile identifies the VLAN and related network settings that NDB can use when creating a database server VM. Merely registering the Nutanix cluster does not create a usable engine-specific Network Profile. If the provisioning wizard for a particular engine displays no networks, the most likely missing object is the Network Profile created under that database engine. DHCP or static addressing is a configuration choice inside the profile; neither is universally required, so the absence of one addressing mode does not explain an empty list by itself. A database HA component profile would be relevant only to the corresponding HA topology, not ordinary engine provisioning. Therefore, the administrator must create or make available a Network Profile for the specific database engine. Nutanix documents this engine-specific workflow under NDB Profiles.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit