Skip to content

Latest commit

 

History

History
184 lines (122 loc) · 14.8 KB

vpc-bm-vmware-nsx-t-deploy.md

File metadata and controls

184 lines (122 loc) · 14.8 KB
subcollection copyright lastupdated lasttested content-type services account-plan completion-time use-case
solution-tutorials
years
2024
2024-01-05
tutorial
vpc, vmwaresolutions
paid
1h
ApplicationModernization, Vmware

{{site.data.keyword.attribute-definition-list}}

Deploy NSX-T Managers

{: #vpc-bm-vmware-nsx-t-deploy} {: toc-content-type="tutorial"} {: toc-services="vpc, vmwaresolutions"} {: toc-completion-time="1h"}

This tutorial may incur costs. Use the Cost Estimator to generate a cost estimate based on your projected usage.

This tutorial is part of series, and requires that you have completed the related tutorials in the presented order. {: important}

In this tutorial, NSX-T will be deployed on the VMware Cluster. This includes deploying NSX-T managers, adding compute manager and adding host and edge transport nodes. This phase is optional, if you plan to use NSX-T for your Virtual Machine networking. {: shortdesc}

Objectives

{: #vpc-bm-vmware-nsx-t-deploy-objectives}

In the previous tutorial, you deployed required {{site.data.keyword.bm_is_short}} VLAN interfaces. The management IPs were registered to the DNS Service, so that these can be resolved with a name. These IP addresses and FQDNs will be used throughout this tutorial.

In this tutorial, you will first deploy one NSX-T manager on a {{site.data.keyword.bm_is_short}} running VMware ESXi. After the first NSX-T manager has been deployed, you will register the vCenter as a compute manager and you can then deploy the 2nd and 3rd NSX-T managers via the NSX Manager GUI. After the cluster formation, you can configure the NSX-T transport zones and various profiles based on your preference and add the {{site.data.keyword.bm_is_short}} hosts as transport nodes as well as create the edge transport nodes and edge cluster.

Deploying NSX-T in {{site.data.keyword.vpc_short}}{: caption="Figure 1. Deploying NSX-T in {{site.data.keyword.vpc_short}}" caption-side="bottom"}

Before you begin

{: #vpc-bm-vmware-nsx-t-deploy-prereqs}

This tutorial requires:

  • Common prereqs for VMware Deployment tutorials in {{site.data.keyword.vpc_short}}

This tutorial is part of series, and requires that you have completed the related tutorials. Make sure you have successfully completed the required previous steps:

Login with IBM Cloud CLI with username and password, or use the API key. Select your target region and your preferred resource group.

When advised to use Web browser, use the jump machine provisioned in the {{site.data.keyword.vpc_short}} provisioning tutorial. This jump machine has network access to the hosts, the private DNS service and vCenter IP to be provisioned. Use url with FQDN, e.g. https://vcenter.vmware.ibmcloud.local as used in this example. {: note}

Order a vCenter License from IBM Cloud

{: #vpc-bm-vmware-nsx-t-deploy-license}

As a customer on IBM Cloud, you can bring your own license or you can obtain a license from IBM Cloud as a monthly fee.

Use the following steps to order licenses for the VMware products

VMware NSX-T™ Data Center SP license editions available include:

  • NSX Data Center SP Base
  • NSX Data Center SP Professional
  • NSX Data Center SP Advanced
  • NSX Data Center SP Enterprise Plus.
  1. From the {{site.data.keyword.cloud_notm}} Portal > Classic Infrastructure
  2. Click Devices > Managed > VMware Licenses > Order VMware licenses.
  3. Click the drop-down list under Order VMware License. to list the VMware products and number of CPUs for the licenses that you want to order.
  4. List of the VMware products and number of CPUs for the licenses that you want to order. Select NSX Data Center SP Advanced .
  5. Click Continue to order the licenses or you can click Add License to add more licenses.
  6. After you click Continue, you are taken back to the VMware Licenses page, which displays your VMware products and license keys.
  7. Copy the VMware vCenter license key and can be added to the vCenter after the installation.

Review NSX-T installation requirements

{: #vpc-bm-vmware-nsx-t-review} {: step}

Before you start the actual NSX-T deployment, review the following requirements:

  1. Review VMware Solution Architectures for {{site.data.keyword.vpc_short}} for naming and architectural considerations.
  2. Review the NSX Manager installation requirements. See NSX Manager Installation{: external}.
  3. Review and configure the necessary ports and protocols in security groups (if detailed rules are applied). See Ports and Protocols{: external}.
  4. Review the NSX Edge installation requirements. See NSX Edge Installation Requirements{: external}.
  5. Collect the IP addresses and FQDNs for the provisioned {{site.data.keyword.bm_is_full_notm}} VLAN interfaces from the previous tutorial.

Deploy NSX-T managers and for a cluster

{: #vpc-bm-vmware-nsx-t-deploy-deploy} {: step}

Follow the recommended order of procedures to deploy NSX-T on {{site.data.keyword.bm_is_full_notm}} with VMware ESXi.

  1. Install the NSX Manager. Use the VLAN interface IP for the NSX-T manager 1 which was created in the previous tutorial. For more information, see Install NSX Manager and Available Appliances{: external}.
  2. Log in to the newly created NSX Manager using the jump box provisioned earlier. Use e.g. https://nsx-1.vmware.ibmcloud.local as the URL to connect. For more information, see Log In to the Newly Created NSX Manager{: external}.
  3. Configure a compute manager. Add the previously provisioned vCenter as the compute manager. For more information, see Add a Compute Manager{: external}.
  4. Deploy additional NSX Manager nodes (2 and 3) to form a cluster. Use the IP addresses provisioned in the previous tutorial. For more information, see Deploy NSX Manager Nodes to Form a Cluster from the UI{: external}.
  5. Configure a Virtual IP Address for a Cluster. se the IP addresses provisioned in the previous tutorial.For more information, see Configure a Virtual IP Address for a Cluster{: external}.
  6. Create transport zones. For simplicity, you can use the default overlay and VLAN transport zones. For more information, see Create Transport Zones{: external}.

Refer to VMware Solution Architectures for {{site.data.keyword.vpc_short}} for naming and architectural considerations. {: note}

You can order NSX licenses through IBM Cloud Classic portal. {: note}

If you do not have access to VMware customer connect, please contact IBM Cloud Support to download NSX-T images. {: note}

Create uplink profile

{: #vpc-bm-vmware-nsx-t-deploy-transport-nodes-uplink-profile} {: step}

In preparation for the next step, you will need to create a new uplink profile

  1. Create an uplink profile, assigning the TEP vlan id e.g. 400 and assign the active uplink as uplink-1. For more information, see Create an Uplink Profile{: external}

Add host transport nodes

{: #vpc-bm-vmware-nsx-t-deploy-transport-nodes-hosts} {: step}

An NSX Edge Node is a transport node that runs the local control plane daemons and forwarding engines implementing the NSX-T data plane. It runs an instance of the NSX-T virtual switch called the NSX Virtual Distributed Switch, or N-VDS. The Edge Nodes are service appliances dedicated to running centralized network services that cannot be distributed to the hypervisors. An NSX Edge can belong to one overlay transport zone and multiple VLAN transport zones. In this example, the NSX edge belongs to one VLAN transport zone which represents the physical connectivity to provide the uplink access to {{site.data.keyword.vpc_short}}.

Follow the recommended order of procedures to add {{site.data.keyword.bm_is_full_notm}} with VMware ESXi as host transport nodes to NSX-T.

  1. Create host transport nodes. When configuring the host TEP IPs, configure each host individually by using the previously provisioned TEP IPs of the related {{site.data.keyword.bm_is_full_notm}} VLAN interface for TEP. For more information, see Prepare Standalone Hosts as Transport Nodes or Prepare ESXi Cluster Hosts as Transport Nodes{: external}.

When you deploy an NSX-T edge, you can think of it as an empty container. The NSX-T edge does not do anything until you create logical routers, it provides the compute backing for Tier 0 and Tier 1 logical routers. {: important}

Refer to VMware Solution Architectures for {{site.data.keyword.vpc_short}} for naming and architectural considerations. {: note}

Create a segment and port group for NSX-T edge deployment

{: #vpc-bm-vmware-nsx-t-deploy-transport-nodes-prep} {: step}

  1. Create a NSX-T VLAN backed segment for the vlan transport zone using with the VLAN ID, e.g. 400. For more information, see Adding a Segment{: external}
  2. Create a Distributed port group for the overlay transport zine using the VLAN trunk, e.g. 0-4094. For more information, see Configure VLAN Tagging on a Distributed Port Group or Distributed Port{: external}

Add edge transport nodes and create an edge cluster

{: #vpc-bm-vmware-nsx-t-deploy-transport-nodes-edges} {: step}

Edge nodes are grouped in one or several clusters, representing a pool of capacity.

Follow the recommended order of procedures to install edge transport nodes and form an edge cluster for your logical routers.

  1. Install NSX Edges. When configuring the host TEP IPs, configure each host individually by using the previously provisioned TEP IPs of the related {{site.data.keyword.bm_is_full_notm}} VLAN interface for TEP. For more information, see Install an NSX Edge on ESXi Using the vSphere GUI{: external}.
  2. Create an NSX Edge cluster. For more information, see Create an NSX Edge Cluster{: external}.

When installing NSX Edges, create two N-VDSs. One for overlay traffic and one for accessing VPC subnets. {: important}

When configuring uplink for TEP traffic in Edges, create a VLAN based segment for the vlan transport zone using with the VLAN ID, e.g. 400.
{: important}

When you deploy an NSX-T edge cluster, you can think of it as an empty pool of compute resources. The NSX-T edge cluster does not do anything until you create Tier 0 and/or Tier 1 logical routers into it. {: important}

Refer to VMware Solution Architectures for {{site.data.keyword.vpc_short}} for naming and architectural considerations. {: note}

Next steps

{: #vpc-bm-vmware-nsx-t-deploy-next-steps}

The next step in the tutorial series is: