# 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

---

Site [llms.txt](/llms.txt)

---

These are the steps from creating an NSX-T connection to using it in a blueprint. Before you start, make sure at least one vCenter resource handler exists. Then work through the sections below in order, because each depends on the last.

## Map a resource handler

NSX-T keeps a list of its connected compute managers. Refreshing the mappings requests that list from NSX-T, and Cloud Management Platform (CMP) displays the vCenter entries. The NSX-T integration supports only [vCenter resource handlers](/docs/cmp/configure/infrastructure/resource-handlers/vmware-vcenter/), so you need at least one before this step produces any output.

1. Open the NSX-T connection and select the **Resource Handlers** tab.
1. Select **Refresh Mappings**, then **Refresh**. Available vCenter entries appear in the **Mapping Reference** column.
1. In the **Resource Handler** column, select the pencil icon, choose the vCenter resource handler, and select **Map**.

To break a mapping, select the X icon next to the handler, then confirm with **Remove**.

<div class="alert alert-warning" role="alert">


A resource handler mapped to NSX-T must not include environments that use NSX-V.
</div>


## Import logical routers

Logical routers move traffic between internal and external networks, such as between a data center and the internet. NSX-T tiers them so several tenants can control their own routing:

- **Tier-0** connects northbound to the physical network and southbound to Tier-1.
- **Tier-1** connects northbound to Tier-0 for public network access, and southbound to logical switches.

At least one logical router must exist in NSX-T before import.

1. Open the NSX-T connection and select the **Logical Routers** tab.
1. Select **Import Logical Routers**, then **Import**. CMP displays findings with name, UUID, and associated environments.
1. In the **Actions** column, select the pencil icon to choose which environments can use the router. Select the X icon to delete it.

## Import transport zones

A transport zone determines which hosts, and, in turn, which VMs, can reach a particular network. It does this by limiting which hosts can see a logical switch. A host can belong to more than one transport zone, but a logical switch belongs to exactly one. CMP imports only overlay transport zones.

At least one transport zone must exist in NSX-T before import.

1. Open the NSX-T connection and select the **Transport Zones** tab.
1. Select **Import Transport Zones**, then **Import**.
1. In the **Actions** column, select the pencil icon to choose which environments can use the zone. Select the X icon to delete it.

## Manage the connection

The **Overview** tab shows the technology, IP address, username, and the environments this connection serves. **Edit Credentials** changes the connection details, retesting on save. **Verify Connection** checks that CMP can still reach NSX-T, which is worth doing after credentials or certificates change at the NSX-T end. **Remove** deletes the connection from CMP and changes nothing in NSX-T.

## Related

- [Network virtualization](/docs/cmp/configure/infrastructure/networks/network-virtualization/): Create the NSX-T connection these steps build on.
- [Configure network build items on blueprints](/docs/cmp/configure/infrastructure/networks/network-virtualization/blueprint-build-items/): Use the imported objects when ordering a blueprint.
- [VMware vCenter](/docs/cmp/configure/infrastructure/resource-handlers/vmware-vcenter/): The resource handler this integration maps to.