{"id":426,"date":"2020-05-12T15:45:38","date_gmt":"2020-05-12T20:45:38","guid":{"rendered":"http:\/\/loudacloud.com\/?p=426"},"modified":"2020-05-12T18:26:59","modified_gmt":"2020-05-12T23:26:59","slug":"nsx-t-3-0-deployment-for-tkg-step06","status":"publish","type":"post","link":"https:\/\/loudacloud.com\/?p=426","title":{"rendered":"NSX-T 3.0 Deployment for TKG ~ Step06"},"content":{"rendered":"\n

Recommended Audience<\/strong>: Anybody with an Infrastructure, networking, vSphere, and NSX -V background.
What to expect from this post:<\/strong> Prepping the NSX-T environment for configuring \u201cworkload management\u201d in vSphere7 with Kubernetes.<\/p>\n\n\n\n

NSX-T Implementation Order > Create an IP Address pool for NSX Edge Node TEPs > Install NSX-T Edge Node > Create an NSX-T Edge Cluster<\/strong>
Here are the high-level implementation steps that we\u2019re going to follow to deploy and configure NSX-T Manager, so we can make it ready for configuring \u201cWorkload Management\u201d on vSphere 7.0 to enable Tanzu Kubernetes Grid.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Create an IP Address pool for NSX Edge Node TEPs<\/strong><\/strong>
IP Address Pools are used to assign IP addresses to tunnel endpoints (TEPs) on various Transport Nodes (as we’ve seen earlier in step03) and NSX Edge Nodes. * Based on the recommendation to create separate IP Address pools between Transport and NSX Edge Nodes, I’m creating another IP Address Pool for NSX Edge Nodes.<\/p>\n\n\n\n

Click on Networking (top-menu) > click on IP Address Pools (left-menu) > click on “ADD IP ADDRESS POOL” > Provide a name, description > Click on Set under Subnets.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

From the Add Subnet drop-down menu, select IP Ranges > Provide an IP Range, CIDR, Gateway IP, DNS Servers, and DNS Suffix, as outlined in the screenshot below and click Add and click Apply.<\/p>\n\n\n\n

\"This<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure><\/div>\n\n\n\n

Click on Save and make sure that Status displays “Success”<\/p>\n\n\n\n

Install NSX-T Edge Node<\/strong>
NSX Edges are vSphere appliances that provide pools of resources to host distributed routing and other services. Particularly, they provide dynamic routing and other services such as NAT, load balancing, VPN, etc. For details refer to the NSX-T Architecture post.<\/p>\n\n\n\n

Click on System (top-menu) > expand Fabric (left-menu) > click on Nodes (left-menu) > click Edge Transport Nodes at the top > add a new edge node by clicking on “+ADD EDGE VM” button > provide a name, hostname\/FQDN, and select small for form factor and click Next > under Credentials, provide a password for admin\/root\/audit accounts and click Next > under Configure Deployment, provide the compute manager attached in step02, select the cluster to which you would like to deploy VMs and Containers, respective datastore and click Next > under Configure Node Settings, select DHCP or static and provide all the appropriate network details, select the management interface to which the VM is connected to and click Next > Under Configure NSX, add two-node switches, one for VLAN and the other for Overlay (as Edge Node will be connected to both the types of networks) as outlined in the screenshots below and click Finish.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

Now, you should see that it will start deploying an Edge Node both on NSX GUI and vSphere Client.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

When the deployment is completed, make sure that the Configuration State is success and the Node Status is up.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Create an NSX-T Edge Cluster<\/strong><\/strong>
NSX Edge Cluster is used for NSX Edge Node redundancy and will always make sure that at least one Edge node is available. It supports up to 10 NSX Eges and a maximum of 160 vSphere Clusters. As outlined the NSX-T Architecture post, and edge cluster is a required component, especially when configuring any of the services such as NAT, load balancing, VPN, etc. through a Service Router (SR).<\/p>\n\n\n\n

Click on System (top-menu) > expand Fabric (left-menu) > click on Nodes (left-menu) > click Edge Clusters at the top > add a new cluster by clicking on “+ADD” button > give a name, select the default edge cluster profile, under Transport Nodes, select the nsx-t-edge01 from Available and move to Selected and click ADD as outlined in the screenshot below.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

That concludes this post and let’s move onto part07<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Recommended Audience: Anybody with an Infrastructure, networking, vSphere, and NSX -V background.What to expect from this post: Prepping the NSX-T environment for configuring \u201cworkload management\u201d in vSphere7 with Kubernetes. NSX-T Implementation Order > Create an IP Address pool for NSX Edge Node TEPs > Install NSX-T Edge Node > Create an NSX-T Edge ClusterHere are the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[9,7,8,4,3],"tags":[10],"class_list":["post-426","post","type-post","status-publish","format-standard","hentry","category-lab","category-nsx","category-sdn","category-tkg","category-vmware-tanzu","tag-nsx-t"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/loudacloud.com\/index.php?rest_route=\/wp\/v2\/posts\/426","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/loudacloud.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/loudacloud.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/loudacloud.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/loudacloud.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=426"}],"version-history":[{"count":5,"href":"https:\/\/loudacloud.com\/index.php?rest_route=\/wp\/v2\/posts\/426\/revisions"}],"predecessor-version":[{"id":481,"href":"https:\/\/loudacloud.com\/index.php?rest_route=\/wp\/v2\/posts\/426\/revisions\/481"}],"wp:attachment":[{"href":"https:\/\/loudacloud.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=426"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/loudacloud.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=426"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/loudacloud.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=426"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}