<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Network virtualization on CloudBolt Documentation</title>
		<link>https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/networks/network-virtualization/</link>
		<description>Recent content in Network virtualization on CloudBolt Documentation</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<atom:link href="https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/networks/network-virtualization/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Manage network virtualization</title>
				<link>https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/networks/network-virtualization/manage/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/networks/network-virtualization/manage/</guid>
				<description>&lt;p&gt;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.&lt;/p&gt;&#xA;&lt;h2 id=&#34;map-a-resource-handler&#34;&gt;Map a resource handler&lt;/h2&gt;&#xA;&lt;p&gt;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 &lt;a href=&#34;https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/resource-handlers/vmware-vcenter/&#34;&gt;vCenter resource handlers&lt;/a&gt;, so you need at least one before this step produces any output.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Configure network build items on blueprints</title>
				<link>https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/networks/network-virtualization/blueprint-build-items/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/networks/network-virtualization/blueprint-build-items/</guid>
				<description>&lt;p&gt;With a network build item, the blueprint carries the network alongside the servers, and both are created when someone orders it.&lt;/p&gt;&#xA;&lt;h2 id=&#34;before-you-start&#34;&gt;Before you start&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Connect an NSX-T manager and map it to a vCenter resource handler. See &lt;a href=&#34;https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/networks/network-virtualization/&#34;&gt;Network virtualization&lt;/a&gt; and &lt;a href=&#34;https://docs.cloudbolt.io/docs/cmp/configure/infrastructure/networks/network-virtualization/manage/&#34;&gt;Manage network virtualization&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Give the blueprint a resource type. A blueprint with a resource type of &lt;strong&gt;None&lt;/strong&gt; cannot carry a network build item.&lt;/li&gt;&#xA;&lt;li&gt;Add at least one server build item.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;div class=&#34;alert alert-info&#34; role=&#34;alert&#34;&gt;&#xA;&lt;p&gt;The &lt;strong&gt;Network&lt;/strong&gt; button appears on the &lt;strong&gt;Build&lt;/strong&gt; tab only once an NSX-T mapping has a resource handler attached. If you cannot see it, check the mapping.&lt;/p&gt;&#xA;&lt;/div&gt;</description>
			</item>
	</channel>
</rss>
