# Import and manage existing networks

> Bring known networks into Cloud Management Platform (CMP), then determine how servers on each get addresses

---

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

---

CMP imports networks defined in your virtualization platform or cloud account; it does not create them.

## Import networks

Networks are imported from the resource handler that provides them.

1. Go to **Admin** > **Resource Handlers** and open the handler.
1. Select the **Networks** tab and select **Import Networks**.
1. Select the networks you want and confirm.

CMP lists only networks it has not already imported, so run the import again to pick up new ones.

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


The **Import Networks** button appears only for technologies that support importing. MetalSoft does not offer it. Google Cloud Platform imports networks from a project's **Networks** tab instead.
</div>


## Review and edit a network

Go to **Admin** > **Networks** to see every network CMP holds, listed with its resource handler, gateway IP, addressing schema, and whether it has an IP pool. Select a name to open it.

The **Overview** tab contains the settings a server needs to connect: gateway, netmask, DNS 1, DNS 2, DNS domain, and the addressing schema, plus fields specific to the technology, such as VLAN or dvSwitch on a VMware network. Select **Edit** to change them.

An IPAM refuses to register a host whose domain it does not recognize, so the DNS domain must match what the IPAM expects. See [IP address management (IPAM)](/docs/cmp/configure/infrastructure/networks/ipam/).

## Choose how addresses are assigned

A network's **Addressing Schema** decides how a server on it gets an IP address. Edit it on the **Overview** tab.

| Option | What happens |
| --- | --- |
| DHCP only | The server uses DHCP, and the static addressing settings are ignored. This is the default. |
| Static only | The server is configured from the gateway, netmask, and DNS settings, and whoever orders it is asked for the IP address. |
| User defined | The person ordering chooses between DHCP and entering a static address. |

CMP can configure addressing only on a server with guest operating system tools installed, such as VMware Tools on a vCenter VM.

CMP consults the addressing schema last: an IPAM mapping or an IP range on the network overrides it. See [Where a server's address comes from](/docs/cmp/configure/infrastructure/networks/#where-a-servers-address-comes-from). If a network is not behaving as its **Addressing Schema** suggests, check the **IPAM Network** value and the **IP Pool** tab.

## Related

- [IP ranges](/docs/cmp/configure/infrastructure/networks/ipam/ip-ranges/): Assign addresses from a range held on the network.
- [IP address management (IPAM)](/docs/cmp/configure/infrastructure/networks/ipam/): Hand address allocation to an external IPAM.
- [Resource handlers](/docs/cmp/configure/infrastructure/resource-handlers/): Where networks are imported from.