Manage network virtualization
Map an NSX-T connection to a vCenter resource handler, import its logical routers and transport zones, and make them available to environments
2 minute read
CMP integrates with NSX-T Data Center through two NSX-T concepts: transport zones and logical routers. Once a connection exists, import those objects, make them available to environments, and then add network build items to a blueprint.
| Field | Description |
|---|---|
| Name | A name for this connection. |
| Protocol | HTTP or HTTPS. Defaults to HTTPS. |
| IP/Hostname | The IP address or hostname of the NSX-T manager. |
| Port | Defaults to 443. |
| Account username | An account authorized to run commands on the NSX-T manager. |
| Password | The password for that account. It is stored securely. If the password vault feature is enabled, this field offers Locally Stored or Vault Managed. Select Vault Managed to read the secret from a configured vault provider. See Use password vaults. |
| SSL Verification | Select this to verify the certificate when CMP connects. Add the certificate under Admin > SSL Root Certificates first, or the connection will fail. See SSL root certificates. |
CMP tests the connection before saving and does not create it if NSX-T cannot be reached with the details you entered, so a saved connection is a working one.
Creating the connection opens its detail page. From there, import the NSX-T objects CMP needs and decide which environments can use them, and then put the network build items on a blueprint so a network deploys when the blueprint is ordered.
Map an NSX-T connection to a vCenter resource handler, import its logical routers and transport zones, and make them available to environments
Add a network build item to a blueprint so that ordering it creates an NSX-T network and attaches the new servers to it