{"id":933,"date":"2021-09-30T22:28:55","date_gmt":"2021-09-30T20:28:55","guid":{"rendered":"http:\/\/hentati.org\/?p=933"},"modified":"2021-12-27T18:00:58","modified_gmt":"2021-12-27T17:00:58","slug":"create-uplink-profile-transport-node-profile-configure-host-transport-node","status":"publish","type":"post","link":"https:\/\/hentati.org\/index.php\/2021\/09\/30\/create-uplink-profile-transport-node-profile-configure-host-transport-node\/","title":{"rendered":"Step4: Create Uplink Profile, Transport Node Profile & Configure Host Transport Node"},"content":{"rendered":"

Link for all Steps :<\/strong> 10 Steps to Deploy NSX-T<\/a><\/span><\/p>\n

(Previous Step) Step 3 : <\/strong>Create IP Pools & Transport Zones<\/a><\/span><\/p>\n

In this article, we will continue with the creation of uplink profile,<\/span><\/p>\n

Uplink Profile :<\/strong><\/span><\/p>\n

An uplink profile defines the policies for the links from hypervisor hosts to the logical switches (segments) or from NSX Edge nodes to top-of-rack switches i.e. teaming policies, active\/standby links, VLAN ID and the MTU setting.<\/span><\/p>\n

There are four pre-defined Uplink Profiles, which satisfies most use cases. This blog focuses on to create a bespoke uplink profile e.g. multi-tep uplink profile which will be utilised later in the series for the compute ESXi hosts.<\/span><\/p>\n

1. Click -> System ->Fabric\u00a0 -> Profiles -> Uplink Profiles -> Add Profile:<\/span><\/p>\n

\"\"<\/span><\/p>\n

2. Specify the name, select Teaming Policy as\u00a0Load balance source<\/em>\u00a0and both\u00a0uplink-1,uplink-2<\/em>\u00a0as \u201cActive Uplinks\u201d:<\/span><\/p>\n

\"\"<\/span><\/p>\n

 <\/p>\n

\"\"<\/span><\/p>\n

\n
\n
\n

The screenshot below shows the new uplink policy created successfully:<\/span><\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"\"<\/span><\/p>\n

Transport Node Profile :<\/strong><\/span><\/p>\n

Transport node profile clubs an IP Pool, Transport Zone(s) and Uplink profile (discussed and created in the previous steps) in a single configuration profile that is applied to the Transport nodes e.g. hypervisors. It defines the network configuration of a transport node with N-VDS configuration, IP assignment and uplink to physical NIC mapping.<\/span><\/p>\n

\n
\n
\n

3. Click -> System ->Fabric -> Profiles -> Transport Node Profiles:<\/span><\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"\"<\/span><\/p>\n

4. Specify the Name, select the \u201cOverlay\u201d Transport Zone created previously, Click N-VDS as shown in the screenshot below:<\/span><\/p>\n

\"\"<\/span><\/p>\n

5. Select the N-VDS, the default NIOC Profile, Uplink profile created, LLDP Profile, IP Assignment , IP Pool also created , Select vmnic2 and vmnic3 (the physical NIC not in used), Click Add PNIC as shown in the screenshot below:<\/span><\/p>\n

\"\"<\/span><\/p>\n

This concludes this step of creating a new Transport Node Profile successfully.<\/span><\/p>\n

\"\"<\/span><\/p>\n

When a hypervisor host is prepared to function with NSX-T Data Center, the host is known as \u201cFabric Node\u201d which carries the overlay traffic. All fabric nodes have NSX-T Data Center modules installed and are registered with the NSX-T Data Center management plane.<\/span><\/p>\n

For a hypervisor host or a bare metal server to be part of the NSX-T Data Center overlay, it must first be added to the NSX-T Data Center fabric.<\/span><\/p>\n

6. System -> Fabric -> Nodes -> Host Transport Nodes -> Select the Site A\u2019s vCenter Server, as shown in the screenshot below<\/span><\/p>\n

\n
\n
\n

7. Select the compute cluster and click \u201cConfigure NSX\u201d:<\/span><\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"\"<\/span><\/p>\n

8. Select Transport-node-A<\/em> as Deployment Profile -> Click Save as shown in the screenshot below:<\/span><\/p>\n

\"\"<\/span><\/p>\n

\n
\n
\n

9. Give it a few minutes, and the Configuration State<\/em>\u00a0and\u00a0Node Status<\/em>\u00a0will show\u00a0Success<\/em>\u00a0and\u00a0Up<\/em>:<\/span><\/p>\n<\/div>\n<\/div>\n<\/div>\n

\"\"<\/span><\/p>\n

To verify configuration, we can check on overview:<\/span><\/p>\n

\"\"<\/span><\/p>\n

Also by Physical Adapters<\/span><\/p>\n

\"\"<\/span><\/p>\n

To visualize the N-VDS from vCenter Server \u2013 Logon to the vCenter -> Click \u201cHosts and Clusters\u201d -> Select Host -> Click Configure -> Expand Networking -> Click Virtual switches:<\/span><\/p>\n

\"\"<\/span><\/p>\n

 <\/p>\n

The TEP IPs can also be identified by logging on to the esxi host and running the command below:<\/span><\/p>\n

esxcli network ip interface ipv4 get<\/em><\/span><\/p>\n

Run the following command to perform a ping test using the TEP interface:<\/span><\/p>\n

vmkping ++netstack=vxlan 172.16.100.X<\/em><\/span><\/p>\n

 <\/p>\n

Note<\/strong>: Even though the overlay encapsulation used in NSX-T is GENEVE, the esxi command is still the same using the stack vxlan.<\/span><\/p>\n

 <\/p>\n

This concludes this step of configuring Host Transport Node successfully.<\/span><\/p>\n

(Next Step) Step 5 : <\/strong>Configure Edge Transport Node, Deploy NSX-T Edge VM & Create NSX Edge Cluster<\/a><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Link for all Steps : 10 Steps to Deploy NSX-T (Previous Step) Step 3 : Create IP Pools & Transport Zones In this article, we will continue with the creation …<\/p>\n","protected":false},"author":1,"featured_media":1147,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[10],"tags":[],"_links":{"self":[{"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/posts\/933"}],"collection":[{"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/comments?post=933"}],"version-history":[{"count":6,"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/posts\/933\/revisions"}],"predecessor-version":[{"id":1112,"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/posts\/933\/revisions\/1112"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/media\/1147"}],"wp:attachment":[{"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/media?parent=933"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/categories?post=933"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/hentati.org\/index.php\/wp-json\/wp\/v2\/tags?post=933"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}