Cisco 9800 WLC- Base config and Redundancy

hello and welcome to sg tech forum in this video i'm going to talk about cisco uh 9800 wlc and i have done a previous video where we we saw the high level overview of wlc what are the different form factors and the navigation form right so you know uh more about this product and uh and then how it is different from aros now if you receive this product right and you want to use it so this video is focused on that in this video i have received a pair of catalyst 9800 wlan controllers and the agenda for this video is apply the base config so that the controller is available or accessible remotely at the same time we configure high availability or redundancy between these two controllers so that when we apply the ssid or wlan profile we have the controller available as a ha for my aps um and and ready to roll in production so on this diagram you can see i have two 9800 controllers i named them primary and secondary and they are connected using a redundancy port so it these are hardware controller that means it comes as a hardware appliance and it has a built-in port for redundancy so i have connected them back to back and just like any other controller there is a lag or ether channel going from my controller to my uh distribution environment or the wired environment and similar for the second one and and then we have the gateway and other things configured in the wired network which i'm not showing it here okay so once you receive and you power it up basically what you are going to get is uh just like any other switch since this is ios xc um any other cisco switch it will ask you do you want to enter into initial configuration dialog mode you can say yes and then you can configure it like all this ntp server wlan profile ssid and all so it will prompt you basically right just like in air os when you reset system you have to configure some minimum parameters but i don't want to configure in that way right i want a flexibility to apply templates and site tag and profile on my own so i'm terminating the initial configuration mode and coming a terminator to install and i'll just configure it very minimal confidence config like a host name username password apply um enable login vty lines so that i can telnet it further and just connect the ports for ether channel uh and other things and an ip address for for the management that is it so you can see i'm not our base config template here is the host name username you configure your name server domain name because you want to access it remotely right so these things are important needed vtp mode we are going to set as a transparent i'm going to enables tcp keep alive ends but the most important thing is configure the vlan and the and the ip address so this is my wireless management interface and these are the physical ports they are connected to switch so i'm using four physical ports and configured a ether channel on them other things very minimal so i enable ssh version 2 and underline console login synchronous so that it doesn't trouble my input and similar configuration at the other side just the ip address change okay so let me log into the box itself so here we have the box and this is my secondary box okay so i have just terminated auto install and hence this is this so let me login there is no password nothing and let me just put terminal length 0 and let's look at the out of box config first so you can see i have some self-signed certificates here other than that the blank interfaces and some uh wireless ap related default configuration so we have lot of default things which you can use or you can customize but this part wireless part we will touch base in follow following videos so this is a if you look at the config you and you're working with cisco devices this will look very much familiar uh to you the first part the first part is nothing but just like a regular switch and then you have a later part which is related to the wireless config and that's how a wireless controller looks like so let's go ahead and configure and i have the base configuration ready so let me apply the first configuration and i'm going to simply paste it okay exit service i didn't get this syntax right so let me just check okay tcp keep alive in and tcp keep live out because i don't want my devices to keep the tcp connections open if they are not in use and let's configure this secondary one so here what you want to say is dash in dash out and very similar configuration i have already configured my switches so my ether channel should come up immediately okay i got those wrong again let me check service all right so config applied and let's see if the lags are up so you can see my port channel 3 is up and all three ports are in participating and i'm going to do the same thing here so either channel summary and once we do summary i should you should see that this is available now let's see if the devices are available for uh remote access uh because right now i'm connected as a console so in your environment if you have the console remote console server you can connect the console port to the console server and access console remotely or if you don't have that flexibility or if it is a lab scenario you can simply connect your laptop to the console port and use some terminal program to access the console but console is all not really convenient right so you want to enable telnet so that your users can log in remotely and that's what i did so now let me just do a write and exit out of it before i exit sure run int vlan 10 and same thing here 10 okay and let me verify our username and password so not a very secret password cisco one two three okay so i'm going to exit from the console and try to log in [Music] try to log in remotely so i'm going to say ssh sdn tech at 10 199 189.29 okay yes and when it is asking me for the password all right so this is available for remote and same thing i'm going to terminate this connection here let me restart the session because my control server somewhere and the break sequence is not working so i have to restart session with the attack 30 this one is 30 and you can see it is asking further so my primary and secondary both are available right now since it is available i should be able to access this using a browser so 29 is my primary so let me put 29. connection will not be private because it's not using a certificate and i'm going to use the same username and password and take tech and try to login you can see the web ui is loading and this is here so you can see configuration setup wizard and it is asking you to configure a few things but if you are not ready then what you can do you can just disable this via cli and how to do that you just have to set the country code on the device itself so to set the country code what you want to do you want to say ap you want to set ap country but you cannot set a ap country directly so first you have to disable um [Music] are you sure want to continue yes and i'm going to shut down five gigahertz also just because i want to set the country so now i'm going to say ap country and you can see i have iap country usa us okay country code is us i'm going to say yes changing country code could research a channel and that's why i have shut down those things and now let's bring the shutdown back so i'm going to say no ap dot 11. okay all right and now let's go back to our web ui and you can see since we have set up the country code the web ui will be available without the first time login page so you see here i am a it's loading and right now no access point nothing is configured but my ui is available right the next task is to go ahead and configure the redundancy right so for that you have user admins so before we discuss that let me show you something that what is a redundancy right so let's talk about redundancy and what are the things needed so redundancy configuration or sso you need a cheaper which is same kind of like hardware controller you cannot configure redundancy or h between 9880 and 9840 or 9880 and and a cloud controller both controller must be running the same software uh in order to form a cha and there are some link latency rp link latency and minimum bandwidth if it is going via a switch in my case i have connected it directly but if it is if it is going via some switch or something then you need extra configuration uh you have to ensure that you have enough latency all right now let's go ahead and configure redundancy between them so i am logged into the my primary box and to configure redundancy what do you need you need couple of extra ip addresses so keep those ip addresses handy then go to administration devices under devices you have general stp ftp and other things but we are interested in redundancy so you click on redundancy then you can see redundancy configuration is disabled and you can verify the same thing on a device also so this is close for some reason let me login again show redundancy or we can just simply so you can see that is non-redundant because when uh it's disabled right now and we have only one uh active which is itself so now you can toggle the button and then you say the local ip address so this is the ip address you need additional to your wire to to your wireless management so this is for redundancy purpose only so i'm going to say 21 in my network and 240 remote ip is 26. i can keep keep a live timer or another things default but active chassis priority so higher the priority uh the greater the precedence so i want this uh controller to be active all primary all the time that's why i'm going to increase the priority to two and simply say save okay priority may result in configuration change new search provider you want to continue yes and this will reload my system so i'm going to simply start the reload yes and let it reload let's go ahead and access the second one uh okay so we may have to do the first skip the first time setup again let's see what it loads since we are logging it at the first time so just like just as expected just like primary it is also coming in configuration setup wizard so we have to set up the country code here as well so let me log into 30 since telnet is available what we can do we can simply go to this four shot yes is by default and i'm going to say five gigahertz shut yes by default and then we are going to set ap country code us when by default is yes then let's bring back 5 gigahertz and 2.4 gigahertz so you have to do this exercise on both the controllers and simply right now so now if you refresh this you can see that we can bypass day zero so let's configure redundancy here as well administration devices redundancy enable local ip 46 just opposite to what we did in primary we are just putting the reversing the ip address and we'll keep the chassis priority as one we don't want to increase it and apply so this is applied let's go ahead and reboot this one as well okay my prompt is not available for some reason maybe the configuration is getting applied but let's check what is the state for the second one okay oh do you wish to push okay i thought it's already booting okay so the active unit this will reload the whole stack yes please go ahead and reload okay configuration connection 22 is broken pipe let's see so let me pause the videos while my stacks are loading and once they come back we will verify the redundancy status thank you okay so finally uh the router reloaded uh sorry controller reloaded both the controllers and now i have web ui back for my primary controller you can see i can refresh i can get the dashboard back again because the device is back and if i do the same for my secondary controller earlier it was loading but now it it won't so the ui won't be available for h a pair now here let's verify the um redundancy what we just configured so administration devices redundancy is how you configure right but to monitor it or to verify let's go to monitor system and then finally we have tab called redundancy within redundancy you can see i have this chassis as active because it has priority 2 and this is my ip address this is the remote one that's the remote ip address image version and the device up time this is the active chassis and then peer status is stand by heart these are the switch over details so if any switch over happens you can see the details here but i will not uh if i want i can manually run a switch over but this will increase the length of this video so i am not going to do that all the redundancy related information you can find it here under monitor system and redundancy all right so let's go and verify the same thing from the device perspective so let's log into primary and i'm going to say show redundancy and here you can see the same details what we were looking in the ui so you have active and then this slot 2 is stand by heart and if i try to log into the standby you can see that the console won't be available anymore okay [Music] like i say you can see standby console is disabled so it's not available but if you want we can do a switch over redundancy switch over and i don't remember the command immediately but you can do it so you can say redundancy force switch over and it will fall off to the secondary one but we are not going to do that because that will increase the length of the video and if you do any switch over whether manually or a system it happened automatically because of system crash you will see all the switchover details here so now our device is actually ready for wireless lan configuration and that i'm going to show you in different video very quickly if you come back to dashboard you can watch primary and secondary cpu utilization and other details from here so you can see now since we have redundancy available i have this drop down becomes active and i can select standby and i can see the cpu and memory utilization for my standby as well from the primary ui so this this is all for now and in future video we will go ahead and configure uh the controller and let ap join this controller thank you

Channel: SDN TechForum

Views: 5,378

Keywords: Networking, sdntechforum, monitoring, cisco

Id: sff26rgzY_I

Length: 24min 46sec (1486 seconds)

Published: Thu Oct 01 2020