NSX-T 3.0 - Install and Configure

[Music] install and configure nsx t3 for vmware and so to configure this head over to beamwidth.com downloads click on nsxt data center scroll down to the flavor of nsx you want enterprise plus in our case and the top option here which is the nsx manager we'll start with the manager of a download it's about 11 gig it will take some time so just save that somewhere where you have space we're just going to download the nsx edge as well for a later video you require this if you can install the edge onto sort of bare metal boxes and to purpose this video we will be deploying edge from the appliances virtual machines so just download that to my download folder so that'll take some time so i'll just speed up the video at this point once that's downloaded head over to vcenter client right click on the data center or um cluster in which to deploy this and open the ova file and then click upload files browse to the ova file which we just downloaded there's our there's our manager appliance so open that so click next give it a meaningful name i think i'll be too long for ib center so we're going to call this the nsx manager uh you can have multiple managers in a cluster for this instance we're just going to have a single manager node so we just call this test lab nsx manager uh i'm happy with the cluster click next sasha's validating the levy gig file so once that's complete uh just review the detail files see the disk sizes it will take up 300 gig thick provisioned and we're going to go for the medium install which is 6 cpus 24 giga memory so look at the sizing guide we put this on our vsan data store select the networks to deploy onto we've got distributed network here so pg management click next here we just set the the root passwords um for the appliance so we just need to enter that and confirm it we also have the passwords to put in for the cli admin and for the cli audit so go through them you can ignore the rest um so enter in your host name just ensure we don't put underscore in there they won't be allowed so what role do we want so we go just for the nsx manager today it won't be on a cloud environment so put your um default gateway in there followed by the um the ip address of the management and then the subnet mask two four five two four two four five scroll down and we got dns lists so this is our dns server this is um our domain controller which is acting as dns um the domain name in here test lab.local put in your ntp server um i like to enable the ssh just for troubleshooting purposes for now i can show you some some commands later on so confirm on that click ok let that import so we should see an inventory now the test lab has a has appeared so we'll just speed up the video here in the lab environment that took around 15-20 minutes so once that's complete we just need to go ahead and then power that on all right just uh placements with vsan so okay there so that's powering on let's open up the the console they go through its first initialization that does take some time to boot up and get an ip it took about five minutes for me we'll just speed this up so right so head over to your um web page google and firefox works better with this and put in your domain name log on using the password you had you entered it into the appliance accept the ula agreement and continue that it's up to you if you want to go with a customer experience all right so this is our first site of the manager uh first we just need to add in our vcenter so over to system fabric and compute managers so we just click add we're just going to add in our vcenter so that my v center in this case vcsa 7 followed by the fully qualified domain name or ip address in that case so the logo name for the vcenter itself so administrator vsphere.local and then our password if you have a certificate you can add it here enable trust you can ignore for now um later videos there's a support for upcoming features so we should see this in progress um when when that's imported it should say successful it can take a minute or two okay so it's registered now in our um manager window connection status is now up so head over to transport zones we need to add um two zones so first is going to be our um overlay network zone this is effectively where the transport nodes communicate with each other so we call this prod overlay transport zone we need to add that into a switch so this would be our nsx switch so meaningful name that corresponds to the transport zone so overlay ndbs okay that we need to add one more transport zone this transport zone is going to be for our vlans this is communication outside outside the environment up using the uplinks so we call this uh prod vlan tz again this goes into its own switch so prod vlan the mean full name uh nvds uh and select traffic type ensure you have vlan here if you're using the vlan transport zone click add say successfully created now we can head over to our network and we need to add some address pools these address pools are going to be used for our vtep which the the nose communicate over so for this address paul we're going to call this vtep ip pull and then add your subnets click add subnet we're going to use a range so just type in your ip range here so we're going to use what between 151 up until 170. add item or hit enter making sure that that accepts in there address sitter that's our network address followed by our gateway ip so click add once that's successfully in there click apply and then save so once that initializes successful okay so now we can head over and add our transport nodes so it's default is standalone so changes to vcenter managed so in our case it would be the vcsa7 uh we've installed these under the cluster one so select cluster a1 or the clustering which even you wish to put the uh nsx nodes on and then click configure so we're going to create our transport node profile so effectively this profile will be applied to all transport nodes that sit within this profile so these are going to sit on our esxi hosts so we call this esxi tn profile i'm happy then yes give it a meaningful name so this would be the profiles for our overlay ndv and vds select our transport zone which is our overlay here select our host network host profile here and then uplink these are just defaults but you can amend them lldp and we just set that to disabled for now so ip management we're just going to select ippo we just created so we just search for that it's our vtep there here's our team in policies so active standby mode so we just need to add in the physical nick we can use for this uplink so in my case we're going to use the vm nik one press add or enter and apply that so there's our profile created which are applied to these two nsx nodes and any other node we wish to add in using that profile so this would take about 5-10 minutes so we'll just speed through the video at this point it's never applied now i just need to add our network segments we're going to start off with three segments so we can have our web segment connected to the overlay transport zone we need to set our subnet this effectively becomes the gateway for machines in that segment click no i'm just going to create another one here we'll call this our app segment these are just effectively host switches as they were in previous versions so this is going to be the gateway for our machines in this app network so click save no we don't want to configure anymore add one last segment and this in our instance is going to be the db segment we don't want to connect any gateways to this um add the transport zone it's going to be going over the overlay finally our subnet gateway for this network click save and no we don't want to make any more changes so they're up and they're successful so we should see them in vcenter so okay there knows a better chance to have the have the um profiles applied so head over to vcenter so we just need to add in the new segments into our app machines so like any other virtual machine you head over to the edit mode and select the network which she's going to go to and our segments are now visible in here so add that into our app segment i'm just going to um add that into that segment just going to disconnect the previous nic which is no longer required so their machines are now connected to our segments on the nsx so now we open the console to one of the machines we should be able to test them connectivity between all the subnets we've not created any routing yet so it should be able to communicate with the machines in its own subnet so that one works so that's pinging post the web one from webo2 so we just need to add in our edge transport node she needs to give it a valid name so nsx01 it's going to be our fully qualified domain name and we have some t-shirt size in here we'll go medium in this case so just adding your password i like to enable ssh to do some troubleshoot testing select our vcenter this is where it's going to be deployed to and we're statically assigned some ip addresses here and then choose the interface in which your wedge servers are going to go out using so then the domain name they're going to be on followed by the dns server and then lastly your ntp server so once complete click next and then the edge switch name they're going to be on so rkcs are going to be on the overlay nvds switch they're going to be on the transport zone that we created earlier so part of the overlay network and our uplink profile we're going to use the default one here so the single nic uplink profile and for the ip we're going to use our static pool again that we created earlier so there's enough addresses in there right so again we need to select our interface so we're going to use our edge up links that we have so we need to add another switch this switch is going to be for the vlan network so keep it meaningful name so it's going to be on our vlan transport zone uh selector uplink profile again so it's going to be our single nic in this case and then select that interface which your um edges are going to go out on you may have different knicks for these two switches for our 11 bro we're going to use the same nick okay so that's going to deploy that's a few gigs that's going to take some time so um i'll let that run through i'll speed up the video at this point so we're going to create a second edge here for the purpose of clustering you can add a single node into a cluster and we're going to use two edge nodes so we're going to call this one nsx edge.02 it's the same process as before um we're going to use medium again so just put our password for this edge node so the same as before so so so so so so so after hitting refresh we can see that both modes are now successful i didn't add a switch to the last node but you can see how easy it is just to edit we can just add in the vlan switch again add in our uplink profile same as and before we can just save that well that looks like it's good to go so now we can just add in our edge cluster where these two nodes are going to sit in so we're going to call this one edge cluster one and we're just adding our two new edge nodes and then click add and our cluster is now complete now we can head over and create our tears at one gateway so we call i want d1 uh gw one we can't link this to tears we've not created that um you can just have a single tier network and just have tier zero uh we're gonna have two tiers and we could create our tier one first so route advertisements we need to add static routes and connected um segments so add that so now we need to edit our segments and we're going to attach these to the new tier one gateway this is how all the vms will should be to communicate using that gateway address we said so just save that that's the wax web segment uh attached to the tier one gateway now so this is our east west traffic so let's do the other two so edit this one connected gateway tier one gateway and then we need to save that and then edit our db segment add this one also to the t1 gateway and save close edit in right so they're all added into the tier one gateway now so let's head back over to my vcenter client um go to one of the machines in this segment so we're in app one at the moment so let's see if we can hear one of the ping one of the db machines yeah that's one of the web servers this is the db machine and this is the other appo zappo one by this test from the dba one server so ping one of the web servers that's coming back and that's another db server let's see the app server so they're all different subnets they're communicating via the tier one gateway and they can root through so that's successful all right we need to add another segment here this is for the tier 0 gateway so our up links are effectively going to be added into this segment and select our transport zone so because it's going outside we select the vlan transport zone this came out using vlan 0 so we can save that click no we don't want to configure that anymore we want to add another segment for the other uplink so we've got resilience there so again with t zero gw dash zero one up link two uh changes to the transport zone vlan vlan 0 and then save that so we now have uplinks 1 and 2 which the tier 0 gateway can communicate through so let's add our new tier 0 gateway so click add gateway tier 0 and give it a meaningful name [Music] so we call ours tier 0 gw 0 1 and these have to add to a cluster so this is why we added our cluster earlier on so add this to our edge cluster click save and then click yes we will admin this we need to add in our interfaces uh to re root redistribution first so let's set that click add root redistribution give it a name then we need to set we need to set our redistribution so we want to enable static routes connected interfacing segments for tier 0 and click connected internet interface segments for our tier one subnets it should also select everything else just apply that add and click apply let's save that right select our interfaces so we add in the two interfaces that we created earlier so this would be our t0 gateway uplink one just leave it as external and put in an ip address for this uplink so this is the route it will go out through to the external routers and so add this to the segment uplinks that we created earlier and we add this to edge node 1 save that and now we just need to add the second interface going out to the other uplink so again this would be tier zero gateway and then up link two add in the the ip address they can communicate with a router and we're going to add this to that link 2 segment and this is going to go out using the edge 2 server so save that right so refresh they're both successful now so we can just click close so our tier one zero tier zero gateway is now effectively connected to our edge cluster there we have two uplinks we now need to set our bgp so ours is 100 and make sure you set the bgp neighbors as well so go over and click neighbors uh we need to add our neighbor these are going to be our external routers so in our case 192.168 and our autonomous system number is 200. so the source address in which it's going through so this is the up link so it's going to be uplink one so we can save that add in our second neighbor so this would be the ip address of the second router and then the source address is going to go out through the second app link and click save so we can click refresh that becomes successful click close so save that so our tier zero gateway is now complete we do need to link these two together so you do that from the tier one gateway so over to tier one gateway click edit um link tier zero gateway select rt zero um and then click save so it's as simple as connecting the two gateways together that way so save that close editing and they are now linked together so that was um install and configure nsx t3 for the data center i hope that was useful in later videos we'll be looking at vrf lite latin vpn um distributed firewalls so there's a lot to get through so hit that subscribe button uh whereas i hopefully upload these videos soon and you'll be informed so thank you

Channel: Bluewire Solutions

Views: 9,572

Rating: 5 out of 5

Keywords: nsx, nsx-t, vmware, vcp

Id: 6S3cuN4h2qE

Length: 32min 29sec (1949 seconds)

Published: Mon Jul 27 2020