Cisco 9800 CL Controller install on VMWARE - Wireless LAN Controller

[Music] all right so we're going to deploy the brand new 19 cisco 9800 cloud controller on the new version 17 to go in our icelab so we're going to deploy an ovf template i've got the esxi vsphere client sorry the vsphere client open and my esxi server picked up so i'm going to go ahead and browse to my new download here of 17.3 code it is not the recommended release but it's the latest release and we like tested stuff out here so uh we're going to go ahead and click continue and put in our host name uh well let's make a little bit more official and we're gonna choose inventory location we're going to put it in that data center got a lot of options here now there's an option for the high throughput which is the advanced license we're going to go ahead and just do the 1k 10k appliance that's fine but if you look there uh it's got eight gigs ram three uh v-necks all it's the same software no matter how many aps you're supporting it's just more processor more memories uh more processor more memory and it's pretty much the same hard drive space though it doesn't require anything bigger for you know the bigger uh deployment so this one says high throughput 7v cpu eight gigs of ram for example versus four uh vcpu eight gigs of ram and three vnix this one is v cpu eight gigs of ram and then we go up to the three k six v cpus for a regular and if you want high throughput once nine vcp used all right the ram doesn't change but the number of the cpus does so uh we're gonna go ahead and click ok we've got our host that we want to plug in and again this is all labs so it doesn't really matter to us we're gonna throw uh select our data store i'm gonna do thin provisioning it's really not a big appliance right it's it's really not you don't need a lot of hard drive space for the controller other than just to run the very small operating system and then also a little bit of local logs that's it i think a flash storage kind of thing right all right so uh the interfaces here confuses a lot of people okay and i won't lie i was one of them initially so uh we've got i've got a couple interfaces mapped and what i like to do uh what i'm gonna do is come back and switch it because the initial setup thing i've not installed 17 but in 16 it was supposed to be that if we logged in from the console and we set the country code for our access points that way we wouldn't have to go to the wireless setup script that's this gui setup script and for some freaking reason uh that's not the case on the cloud versions if you uh basically didn't configure it from the service port which is the v-neck one then you gotta sit to that day zero set up over and over and over again we don't like that so what we're going to end up doing is i'm going to throw this on our vlan 10 just get an ip address and basically join the network we're going to put this guy actually on a trunk interface on the same physical interface but what i've done is i've created a virtual nic that is tagging vlan 10 already that i'm putting on vlan 1 and then i've got a trunk port that's on a virtual nick but it's a trunk to the switch on this interface gig 2 is our primary interface don't get me wrong this is our out-of-band service port up here and then three is our redundancy port for aha communications we are not doing an aha deployment we're doing standard i'm going to go ahead and choose next and in fact before we turn this guy on i'm gonna remove interface three yeah i'm gonna remove it check it out so we're gonna put in c900 as the host name and then our super secret enable password uh you've got device management service interface configuration i'm going to say dhp we're going to say dhp there and then this will add a rock to the remote network where you want to manage the device from uh you know what let's go back a little bit different here i think what do i want to do here do i want to do php there i don't know [Music] what i'm going to do actually is we're going to create another interface because here's the problem if i set up the service interface on the uh ip scheme that i wanted to use then whenever i go to configure the actual box i'm not going to be able to use the ip space i want to so uh this is pain in the ass but we're gonna do it it's all good all right so here's that v-switch this v-switch basically is connected uh on port 24 of the switch and depending on which interface i use that's trunked now we're gonna go ahead and do uh properties here and i'm gonna add another v-nick okay and we're gonna put this guy on uh v we're gonna put this guy on 50. so we're going to say this is uh p1 w ice l v 50 and next and then finish so what i'm going to do is actually use that just as a temporary staging interface and then we'll apply the actual traffic back here on just the root interface that is tagged vlan all i know fun stuff all right so let's go ahead and do the deployment start taking from the top next next uh g1 wc 9800 next we're going to do this new high throughput that's fine next and the data store we want next then uh all right now i'm gonna choose v50 here and then get two we're gonna put this on the main trunk whoops the main trunk port there that way it's got access to the trunk there we go this will work should work i think it'll work i hope it'll work we'll see if it works all right so gig one i'm gonna do dhp because i've got dhp on vlan 50 that's fine php and uh default route we're just going to do 0.000 that's fine uh username admin super secret password all right and next looks good all right so uh you know that those little setup scripts in vmware just creates a little xml file that's used by the host uh to make certain decisions about its configuration which is pretty nice so we're going to go ahead and uh speed this guy up a bit all right so now that that is done let's go ahead and go under our controller edit virtual machine settings before we turn it on i know it's classic mode and we're just going to delete this interface we don't need it we're not doing an h8 deployment if we decide to do an aja deployment later just add it back configure the aha we're good to go but right now we don't need it we need to pull up our console though and go through the initial console yeah setup uh actually it's gonna pretty much come up should come up with a manager interface on that v950 and then we can kind of configure it from there so we're just going to watch this till we see what ip address it picks up on vlan 50 and then we'll go through day zero provisioning uh to set up the uh the gig to interface and if you don't have an out-of-band service port uh in your topology a lot of people some people do some people don't uh some people like to have all of their devices use out-of-band interfaces for configuration in case that primary uh ether channel bundle fails on physical controllers or basically you're pushing lots of scripts you're doing lots of automation if you if you're using that out-of-band management to configure all your devices it's pretty nice network to have actually you don't have to worry about spanning tree killing your stuff and killing your configs and blocking part of your config pushes and all that but a lot of people again they like to do phased rollouts where they push the code they send another command to do the change and then if something doesn't happen it rolls back there's all kinds of new uh automation features out there so if you're not using that service port for anything useful then configure the box and then you know basically you don't have to have it connected after that but it's gig 2 that by default is going to be your primary interface you could make it whatever you want to be honest it's an ios xe image but the way the setup script runs it's you know i'll show you with me i'll show you what i mean as always chris having fun with what he does and that's the way it should be you should be fun with what you do i'm gonna talk to myself because you guys are not talking back wait are you talking back just kidding all right so let's see if you can get to our here box well we needed chris to see which ip address we're going to get so let's see what we got it does take a little bit to come up these boxes are amazing it's always amazed me how little horsepower like our wireless controllers have and then how much they actually do in a network and they're able to pull it off with just a lot of times very limited resources uh look at this go look at the specs on you know the older boxes right the 3504s or the 2106s if you remember back then um or the 4400s damn that thing was built like a freaking tank if i was ever like going to get shot at i would not mind at all having one of those cisco 4400s in my hands or just around me to protect me because i'm pretty sure that thing would laugh off a 50 cal for sure all right failed to initialize nvram because there's not a startup mofo i yeah this is where i am in my phone right now it's right into my feel of it all right so let's see what ip address we get here guys let's and girls say we got going on so there's that initial booting up right um we got our controller uh pre-installed here so let's go ahead and log in super secret password you'll see kind of what was configured there in the beginning was uh those three interfaces we don't actually need the third one so we're gonna get rid of that pretty quick but uh we installed this with the that one manager interface i was telling you about so basically we've got access to it uh in the lab let me go ahead and open that back up and get this into frame for you i'm using a widescreen monitor so from time to time if it looks like i'm bouncing around a little that's what it is is i'm trying to record in 1080 for you guys but my wide screen is super awesome like four or five k something like that i don't know it's pretty insane i'm just playing it it is uh it is larger though and that's what causes uh issues from time to time so uh yeah all right so we're gonna open up our new c9800 see what happens uh it's gonna be a day zero configuration that we're gonna have to deal with i'm not a big fan of the day zero configuration myself uh i love the new ios xc controllers and all that kind of stuff actually it's not going to be available at that ip yet because we had to remember we had to deploy this in that the other network temporarily just to get it configured on the network i want to get it configured on using the setup script i don't even want to use the setup script and here's the thing normally as long as you go in through the console and you give it an ip address on a vlan and you enable gig 2 and you enable gig 2 to have access to that vlan uh then essentially you get to uh visit this page up whoops what okay we got more work to do let me go ahead and come over here and let's just see what the heck is up so let's do uh ping 10.1.50.1 and let's see show ip route uh okay we are peeing that way let's see what all right so it looks like um i mean there is certificates on here so it looks like the um looks like the device is being silly let's see here uh 10.1.50.103. that's the problem 10.1.50.103 is the ip address so we need to put in the correct ip address and then we'll get over to the correct interface yeah yeah yeah hopefully hopefully that's where we're going all right uh there we go all right so now we're at this new awesome controller interface we're gonna go ahead and choose to log in and there's a day zero setup script there's a day one setup script so cisco loves their little setup scripts uh for these controllers i thought we were gonna get away from this with the whole airspace to ios xe but apparently not um now we set the time zone to central that's fine uh the time is the correct time zone we're gonna go ahead and add a time server here and this is what i meant by the day zero setup script if you notice day zero up in the top uh our radius server we'll go ahead and add that now we choose our management uh interface so we're going to make it vlan 10 i'm going to put this guy on uh our manager interface that we've been using here with our airspace controller at 32 and then we give our management vlan dhp server now you can do this like i said from the cli it is supposed to be that as long as you add a country code for your aps then you skip day zero configuration however there's a bug in this particular code version but that's not the case so we're gonna go ahead and set up this uh wt data uh psk and network type we're gonna go ahead and just use personal that's fine and you know what let's just set up our wt uh data3 um and this time we're going to call it uh yeah we'll call it wt data3 let's do e let's do wt data um to because i kind of want to keep the authentication separate then then the other one then our uh 3504 so we're gonna go ahead and add that we can always change this of course uh once the controller set up in fact that's where i like doing all that so traffic type data invoice there's our virtual ip we're going to generate a certificate for this we want to use a minimum of sha2 if not more so we're going to put in our password there look at our summary and finish really everything that we just did like i said could be done through the cli but uh i've been experiencing with this particular code version and i don't want to sit here and try you know several code versions but even though you give it the uh country code it's still coming up with day zero configuration so uh and the other little caveat is is you really need that service port uh configured for ghp or configured in the wlan to do this initial configuration and then make it uh your management two because of all that uh like i said i tried this once earlier i'm not sure if i'm going to include that part of it with the course although i do like for you guys to see whenever i have problems in the troubleshooting behind it i try to leave a lot of that in so i probably will but essentially uh there because that caveat you really kind of gotta configure both gig one and two uh and they've got to be in different segments or else it won't work okay you can't like uh configure them both for the same ip space just doesn't work like that all right so uh we were logged out and again it may take a minute for everything to be applied as it said but we'll go ahead and log back in here and hopefully hopefully hopefully we don't have to see the day zero anymore there's our dashboard that's what we're looking for yay all right so we have finished the initial setup scripts for this controller we should be able to now reach it again on our uh c9 800 uh wi-fi training.local if not that is just um this is our dns and it's going to that manager interface so it should be reachable here like i said if not we can fix it but it is all right um and let's go ahead and log in there and we are now web ui so uh we're gonna continue this in another video this one's super long and don't

Channel: Chris Avants

Views: 1,679

Keywords: Cisco, 9800-CL, WLC, Wireless LAN Controller, Cisco Controller Setup, Cisco vWLC Setup, Wireless Controller Setup on VMWARE, Cisco 9800 on ESXi

Id: HwVv4u5hK5E

Length: 20min 34sec (1234 seconds)

Published: Thu Oct 01 2020