Error: "400 Bad Request - VC 'NONE' network "<network_name>" not present in vCenter" when attempting to register a vCenter using the Cloud Director API

Products

• VMware Cloud Director

Issue/Introduction

• Attempting to register a vCenter with Cloud Director using the Cloud Director API as per the documentation, VMware Cloud Director API - POST-RegisterVimServer.
• Supplying a portgroup name for the optional vcNoneNetwork in the RegisterVimServerParams during the registration attempt.

Environment

VMware Cloud Director 10.6

Cause

This issue occurs if the portgroup name for the optional vcNoneNetwork parameter is part of a distributed switch which is located under a folder in vSphere and the distributed switch is not located at the root Datacenter level.

Resolution

This is a known issue affecting Cloud Director.

To workaround the issue register the vCenter without customising the vcNoneNetwork.

Alternatively if a custom portgroup must be used, provide a portgroup from a distributed switch located at the root Datacenter level and not under a folder in vSphere.