Cisco Wireless Innovations with Ankur Bhasin

you money the my name is Uncle machine and I am a software developer manager in enterprise networking group and today I'm going to talk about next generation wireless controller which will reinvent the wireless network so let me introduce you to catalyst 9800 wireless controller which also represents catalyst access expansion to wireless so built from grounds up for intent-based networking catalyst 9800 is part of DNA center architecture now DNA Center architecture is built on three pillars automation policy and assurance now Network automation translate your business intent into network policy and network assurance can capture the actionable insights back to the DNA Center and gives you a granular visibility of your network so 98:8 comes in different form factors hardware appliance a virtual machine running on private or a public cloud and also gets with a software package and buried on catalyst 9300 switching platform and i'm going to touch base all of these flavors later in my slides catalyst 9800 will support all wave one and wave two indoor access points and outdoor access points and whenever 11a X gets introduced catalyst 9800 will also support the same so now let us quickly look at the wireless architecture for 9800 so it catalyst 9800 brings together the decade of Cisco RF excellence with all the innovative features what we have done on the most deployed air OS controller which includes client link intelligent captures clean air married together with the most modern and modular operating system which is Cisco IOS XE which provides high availability programmability and scaling so when both brought together we built this 9800 controller from grounds up with confidence for intent based networking and can be deployed anywhere so 9800 provides the most flexible management options for an example 9800 catalyst controller can be managed from DNA Center we also managed from Cisco prime and integrated very simple web UI the CLI also which is training as an IO sexy CL eyes but because it is powered from iOS XE which is open and programmable architecture it can be also managed from net convent yang models so DNA Center will be able to manage it with net convent yang model you can also use standard base interoperability tools like puppet or NC Bell to manage catalyst 9800 controller because it has a net content yang models and not only that a custom development which means that every single CLI which is present on catalyst 9800 for configuring it is also can have a corresponding net content yang model which means you can use day 0 to day 1 to day n network provisioning using a programmable interfaces so now 9800 controller as I said it is powered by iOS sexy we built it on three pillars of network excellence always on secure and deploy anywhere now let us understand why always-on is so critical so take an example of our health care customers a minute of a downtime can result in to roughly $3,000 so what about if they have to plan an upgrade and do that upgrade multiple times in a year and on multiple site may cause them hundreds and thousands of dollars so what we are introducing with always-on is a seamless software update with hot patching which means a network administrator can do a hot patch on to the controller and also a ap service pack on to an access point and can have a seamless software update with no network downtime so i'm not updating aps and then waiting in from the combat exactly random fry I'm not rebooting controllers and flipping them back and forward exactly doing any of that anymore exactly and I'm gonna touch details about major code upgrades not just minor iteration even and that's the second thing which I was about to talk we are introducing intelligent RF base rolling ap upgrades where even if you are upgrading the entire base image of a controller and an access points you can upgrade it with the Hitler with zero downtime leave you decoupled ap version from controller version yes and I'm gonna touch bit a little bit more about always-on and go a little bit deep dive on there now what we are doing is security so security being on top of the mind more and more traffic is getting encrypted right so it is very important to detect a malware into an encrypted traffic before even can bring down the network so we are introducing encrypted traffic analytics on our 9800 controller also which means any traffic which goes to the wireless LAN controller in a centralized Wireless deployment we can implement ET on their traffic you can implement what encrypted traffic analytic are so which means that we can I will go touch base deep on to the ETA in next couple of my slides and within automated macro and micro segmentation with software-defined access we can also have security applied add an access layer itself and then deploy anywhere we also understand that customers are looking for a flexibility where they can deploy the way they want and can also expand the wireless network so we are giving an option to deploy it on trend on private and public cloud and also as a software package on an embedded switch so now let's go little bit deep dive on the three network pillars of excellence as I was talking before always-on secure and deploy anywhere so what we are doing in always-on so now always-on for an unplanned and planned outages so we all are aware of unplanned outages where a device on network interrupts can happen in the network if that happens we have state will switch over where ap and client database is synced from active to standby controller and there is no downtime when the network failures or a device failure happened and then we will also support n plus 1 high availability but what we are doing more on top of it with power of our sexy we are doing an infrastructure updates which means a software maintenance updates can be given onto the controller and can also be applied to an access point without even rebooting the controllers and then with software image upgrades as I said if you want to upgrade the tire controller image or an access points we can do it with intelligent rolling ap upgrades based on an RF and I'm going to show you how it will happen so first let's look at unplanned events so as I said unplanned even means something can happen on to your network which means your AP and client database has been synced when your AP and client databases sync the states are also synced now that results in always-on network where ap continues to stay up and running you're always on services which is voice video and data services stays up because we have synced the database and gifting the state and always-on client where users and client will always stays connected if any downtime happens in your network now in case if any downtime happen on the device we still because we have synced the database again ap then client will always stays up so this is what we call as active and standby state we'll switch over now this is what we are introducing new with catalyst 9800 controller as I was discussing seamless software based updates on the infrastructure so what's going to happen today in today's wireless network in case let's say you hit some issue on your controller what happens is you go to the tak tak Rich's house to engineering and then we come up with a new engineering image or maybe a mr image and then customer plans for an upgrade they upgrade the entire controller and all the access point get up image from the controller and that brings a downtime into your network now what we are doing is we are doing this off of the hot patching we will give you a patches and patches can be applied on to the controller once you apply a patch on to the controller the base image never gets upgraded the access point never gets upgraded and network and always stays up what we are doing on on top of it is we are introducing an AP service pack so let's take an example of you have a wave one access point or you have a wave two access points and you are hitting some issue on your wave one access point today what we do is we upgrade the entire controller and again all the APS get upgraded with ap service pack you will get a pack on to the controller controller intelligently will be able to find this service for which AP models and we push that service pack on to the access point which means only that access point which need that pack will get update and rest of the access point and the controller will not get upgraded so it will be a seamless software update on to the controller or on to the nexus point and on top what we are introducing is ap device Mac so for an example today you want to introduce a new access point on to the network what do we do we upgrade the again the entire controller and the access point and get upgraded and then only new AP models can join the controller with an AP device patch you will be able to put that back onto the controller and any new AP models which gets introduced for an example tomorrow 11a x will be able to join the controller without upgrading your controller and without upgrading the rest of the access point in the network now could you also use that to increase backwards compatibility by backward compatibility means that go back to and join the old image no no old ApS joining new controller I mean we retire we have that huge matrix of access points controllers and software version yes would this allow you to maintain much more backwards compatibility with older access points through the new software revs that's right so we will start supporting only 11 wave one and wave 2 access point with this controller which means older AP which is 11a and will not be supported on catalyst 9800 but more and more new ap which comes in you can just make it join the controller without waiting for the new software image or upgrading the entire controller on an access point I have a question here because I'm an old call manager guy and this looks like what we used to do with phone software loads where we can issue a firmware update for a phone and not it has to be independent of call manager's platform itself but I also know that that was a huge pain in the neck when it came time to do things like controller upgrades because then we had to be on specific firm revisions for the access or for the phones before we could do those upgrades are you guys learning anything from the communications manager bu about how to prevent those kinds of problems because I can think of a couple of wireless people that will be watching this thinking to themselves I just got out of this mess with with call manager now I'm getting right back into it with wireless so what we are doing it is right for an example a new AP model has to join your controller right and let's say let me take an example you are running sixteen dot ten software version on your controller and the rest of the access point now a new AP model which comes in is supported in sixteen dot eleven right so what we will do is we will have n minus two image which will support the new AP models or the next MD release which means that even without going to sixteen dot eleven on your controller and an access point you can load us in AP device back onto the controller and new AP models which is supposed to be supported in sixteen dot eleven will be able to join an existing sixteen dot n controller will not give you sixteen dot eleven features but will be able to give you all sixteen dot ten features can join a controller and be used exactly so if you don't necessarily get all the features I get that but that that's a struggle I mean I agree with Ryan that that's a pain with customers that have a thousand access points and have the budget to replace half of them and you're running you know this model in this model and you have to choose a happy middle and then they weird stuff happens that's that's a real pain exactly yeah so this will solve that exactly and that will solve it on top of it that whenever you introduce new AP models many times it happens right you have not planned for your network upgrade you are just introducing a new AP model and you want them to join once it joins it's giving you a 16 or ten features and then you plant a network upgrade you can do an intelligent RF based little rolling ap upgrades which will again bring no downtime into your network and still be able to get you sixteen dot 11 and all the new features but till that time you are able to make a new AP model joint without planning a forceful upgrade into your network sort of sort of a library Ron Tom's question there with the device packs is that going to be specific to that new AP model or like the call manager scenario where a device pack actually contains firmware for the entire breadth of endpoints and you may inadvertently also upgrade some devices that you didn't mean to no no so even though let me give an example of a hot patch for the controller ap service pack for an existing AP and an AP device pack for the new AP models will be for those particular issues and access point they be models and when you load it onto the controller controller intelligently find it out from that pack this is for what kind of AP models or what kind of AP which is having a problem so only those ApS will get that update automatically so now let's talk about if you plan to upgrade the entire controller image or the entire access point how you can do it with an intelligent RF based rolling ap upgrade there is no manual intervention needed so let me take an example off you have two controllers here one running version X and you have another controller which is n plus one which you can upgrade it to version X plus one all your access point have joined version X on controller which is your primary controller serving the clients everything is good till here now what you plan is you plan an upgrade so before you plan an upgrade you can define how many percentage of access point you want to get upgraded in your network by default we are picking 15% you can move to 5% to 25% if you want to be more aggressive once you do that automatically based on an RF the access point will intelligently find it out which access point let's say a five percent or a 15% access point which are those access point in your network should be upgraded and then those access point will also find the neighbors access point which will be safe so I know this is an access point which is getting upgraded it will define all the safe neighbor lives next to them and it can start steering the clients onto those neighboring APs and automatically start moving the access point back to the or not back it should start going to the n plus one controller so slowly access point will keep moving get reloaded and come up with a new image and we have already steered the client to the neighboring AP which are safe and slowly all the access point will move back move to the new controller and get upgraded to n plus one version with no downtime in your network we already do this with mobility groups down just like this so what's the advantage today no so today what you do it is when you have a mobility group today if you want to upgrade your access point how do you define which access point has to move so there is no manual intervention needed yeah so what innovation we did it is based on an RF we have a complete RF neighbor relationship which access point observing how many clients which are the neighboring AP which are safe for an example I will start picking up an access point which has no client force oh I say yeah that's definitely manual there and it's exactly what we do this is all automated for an incision so so access point will automatically find out I have no clients or a minimum number of client I will pick that access point find out the neighbors which are safe to me and I can start steering the clients automatically to those neighbors when I have no client on my access point I will start moving my access point to the controller and now the first controller will be intelligent finding out that access point has gone get upgraded and then only I will start the next access point so the mobility messages are exchanged when the AP is on the new controller are completely ready and are able to take the new clients and then only I will start moving the rest of the access point slowly back to the new controller to get upgraded them previous clients are coming back to the old access points right yes so for the clients what matters is right which is the access point which can serve me once that clients are steered to the access point which are safe and I move my access point to the new controller getting it upgraded these act clients will stay on to that access point and when these access point get upgraded and if my client feels that I am getting a better signal and power level from these access point client automatically can roam back to this access point just curious about a nexus point doesn't see the upgrade this of what we have also done it is for an example let's say you define 15% of an access point should get upgraded let's take an example hundred a point in your network and only 15 access points are moving unless and until those 15 access point get upgraded on to the new controller it will keep RIA tempting ok and it gives two or three extra attempts when the access point get upgraded our mobility act message is sent back to the primary controller that all the access points are upgraded and ready to serve the client and then the remaining 15 percent starts moving and then you will upgrade your previous controller which was a primary back 2x plus one version and now both the controllers are running the same version now it depends on you if you want to move your access point back to the primary controller I'll leave it on to the secondary controller which is already serving the APS inclined but in case if you decide to move your access point back to the primary controller again in a same fashion of that RF intelligence access one will slowly move back to the primary controller with effective no time on to the clients and an ax and your network now let's talk about security security as I said top of the mind right and more and more traffic is getting encrypted we are introducing encrypted traffic analytics on catalyst 9800 virus controller ETA was already present on all nine case switching platform where we used to do it at an access layer now we have introduced the same thing on 9800 wireless controller so as you know there are three kinds of deployment in wireless network a centralized wireless traffic where the wireless traffic goes back to 9800 controller that is where you can apply ETA it will look at all the encrypted traffic and attach a metadata and send it in a net flow telemetry to the stealthWatch cloud and a stealthWatch cloud will be able to find that if there is any malware with a algorithm or a machine learning running on to the stealthWatch and give you enhanced visibility it will give shortened time to response before even a malware hits and bring your network down now SD access on 9800 so you all must be knowing that SD axis which we call it as a fabric which was already present on our existing arrow is controller so what are we doing noon with 9800 SD axis so as I said 9800 controller is based on iOS XE now the entire network stack your routers your switches and your wireless controller supports the same OS which means customer need not worry about certifying a separate OS for your wireless in separate ways for switch and separate for switches and routers once you certify your base OS image the same image runs on all the platforms with a switch a router and a viola so you get the same consistent experience on the switches on the router as well as the wireless controllers and now you can get to multi-site wireless maverick by that what I mean is you can deploy a hardware appliance or a virtual appliance on the bigger side and get the fabric and on the distributed sides you can apply Wireless with a software package on the 9300 air OS going away now so investment on air OS will continue and you will keep innovating features on top of it once we know that our next generation wireless controller is adapted in this field and then always the new platform which comes in take a year or two to get adapted and that is very where we plan and decide at that time what do what is our strategy for arrow is controller but as a long term yes but I hope today the arrow investment will continue what will make sure that every hardware I'm sorry for the existing controller yes what exists what's what's a parity like so the entire feature which is present on our arrow is controller till 8.8 release which has just gone on to the CCO will also be available from the fillet of first day of launch ok so I remember when there was another wireless controller based on you know iOS XE and that was a problem 57 60 could and that was missing a lot of features and that's not the case now though exactly now if you notice right we don't care about the GUI or anything like that I mean I care about it but what I mean is as far as the feel absolutely so if you notice 57 60 right it was a platform which was supporting a converge access as an architecture converge access of one of the architecture which was supported by two platform 57 60 and 38 50 yeah so we have three major architectures in wireless a centralized wireless very peas in a local mode you have a flex connect architecture and you have a fabric so we are continuing our architecture on the new platforms so there is no change in an architecture converge access or the complete different architecture which was missing a feature parity a complex MCM a tunnel but our architecture remains the same a centralized Wireless flex connect fabric on a next-generation platform with feature parity with the management as I said from the web UI from cisco prying from DNA center and scale and I'm gonna touch base on the different flavors you will be able to realize what all we are doing on our platforms in different form factor I think one of the things was that at the time it was really helpful to have something that was mid mid range you know how like when you have cars you have like a economy car you know some company then they make one for the mid market then the expensive luxury car it was good to have something that accommodated a few hundred ApS and whatever that was a thousand APs and then you can get the 8500 and a few but there was a cost associated with that yeah so you can sell that to a medium-sized business you know is that gonna be an issue where I have to sell a customer the entire fabric and huge controllers I mean I don't know how this is gonna play out exactly and let me touch base with you all the form factors what we are gonna introduce the 9,800 you will be able to realize the different scale okay we are bringing up with different platforms so as I said SD axis now will be present everywhere with wireless running on the switch while it's running on a private cloud and while it's running on an appliance in areas we used to only support it on an appliance but now the virtual form factor and we will also run the software package 9800 on a switch where you can enable wireless for SD access so quickly to show you deploy anywhere now this is a flexibility what we will be providing to our customers you have a various options to pick and choose from starting from switch where you can run 9800 catalyst software package for embedded wireless you can go up to 200 AP than 4,000 clients you can deploy on a private and public cloud that means the same virtual same software which is running on a 9k as a catalyst 9800 package and on an appliance will also be run on a private cloud on KVM ESXi and also on Cisco NCS and also will be available on AWS marketplace and I am again going to touch base a little bit detail about what we are doing on private and public cloud and then we can go up to 2000 access point on an appliance 9800 43,000 access point on a private cloud and if you want to further expand network to 6,000 APs 64,000 client you can go to private cloud on vieni fxi and also on 90 880 which is our next generation bigger platform and all the feature is the same on each platform like it is now exactly so what we did is we did a feature consistency what we also did is deployment consistency which means the centralized the Flex connect and also a fabric will be supported on all the form factors if the architecture allows for that what an example on 1990 300 switching platform we will only support fabric enable wireless but features remains the same yeah so now let me quickly go through the various form factors to show you what all we are introducing with catalyst 9800 catalyst 9800 wireless controller will introduce an appliance to show you how that plants look like a front panel this is 90 880 industry's first modular wireless controller with hundred giegi uplink so if you notice here there is a modular uplink which can have different uplink interfaces a one gig eat 10 gig e 40 gig in 100 GB we are also introducing with a fixed 8 10 gig fiber-optic modules where you can get 80 GB piece of throughput and a dual power supply and can support up to 6000 APs and 64,000 Wireless clients a smaller version of it which will support 2000 ap than 32,000 Wireless clients and up to 40 GB piece of throughput it again has four fixed interfaces for 410 gig interfaces it can go to 40 Gbps we are also integrating for a recipe which will be a fiber port also before we used to have an RP for active and standby neighbor ship only on an Ethernet we are also introducing in our PI interface for fiber up links exactly the same thing yes but now you can extend using a fiber connectivity in case if you don't have internet on your data centers yeah okay now let's quickly discuss what we are doing for the cloud so the same software image which is running on an appliance will also be running on a private cloud my private cloud I mean is that you can install it on an ESX I on a KVM or as an NFC is on Cisco NCS it will be supported from DNA Center for automation and assurance and can scale up to 6,000 APs and 64,000 Wireless clients even on your virtual machine and we will support all the deployment model which includes centralized wireless flex connect and fabric so lot of innovation we did it on our virtual footprint and in arrow as we never used to support this bigger scale and different deployment modes but there were next generation catalyst 9800 for the private cloud we will support all the deployment modes scale up to 6000 APs and 64,000 Wireless line and you can also use this virtual controller as a guest anchor controller you network about multi-tenancy so multi-tenancy can be multi tendencies in a roadmap which we are planning to introduce but today you can do it with a site tag concept the way we have an AP group concept on our arrow is controller on next generation controller we are coming up with more modular configuration the way we have MQ cqs based configuration you will also have a modular configuration where you can configure site tags a policy tag map those together to an access point and you can still do multi-tenancy what we are doing for the public cloud is we will also have the same software catalyst 9800 available on AWS marketplace you can go and search for catalyst 9800 wireless controller you will be able to find a 9800 controller listed on the marketplace you will be able to instantiate your virtual machine onto the cloud it will support up to thousand access point and 10,000 Wireless line and will only support flex connect local switching and the reason for that is when traffic enters the cloud you don't have to pay but when traffic exits the cloud you have to pay for that so the architecture which makes sense is flex connect local switching where your data traffic locally stays in your branches or your head office only the control plane is managed from the controller sitting it on to the cloud so your image management your config management can be done for them controller sitting in AWS and your ApS are sitting on your branches or is it missing compared to local you know that kind of thing missing features all the features which we have on a local mode other than an ETA for an example ETA we are doing it on a controller because traffic had to hit the controller but ETA can be done on an access layer so it if you have 90 300 very ap's are connected on tonight so now coming to a last flavour where 9800 as a software package can be installed on 9300 so what we are doing is if you have a fabric deployment and you have a border node you can enable wireless on top of it and once enable wireless on top of it the fabric edges ap can be connected and join your controller which is now running as a software package embedded on 9300 based OS image and then for a smaller branches you can have catalyst 9800 can deploy fabric in a box and a piece can be directly connected to it so a complete scalable distributed fabric SDA solution with catalyst 9800 as a software package running on to the 9300 switch depending on the campus fabric that is coming right yes so this is getting launched as a part of our 1610 release multi-site fabric is already supported you need to have an extra hardware appliance to support a wireless now with catalyst 9800 software package you can install it on the existing 9300 switch and wireless functionality will be enabled onto the switch itself it supports up to 200 access point and 4000 client per wireless controller which is running on a switch and if you have two border nodes you can enable wireless on both and can go up to 480 then 8000 client in that branch so just give me two minutes just want to show something laughs which is how you can interoperate a build with the existing air OS controller in your network so we also understand that you may not be able to upgrade the entire network with one shot but if you have an existing air OS controller and the catalyst 9800 you can interoperate now with your air OS can be upgraded to 8.8 mr2 and you can have a seamless roaming between applet Network deployed on catalyst 9800 and a network deployed on arrow is controller and the last thing before I end is even if you have a guest anchor solution and your air OS which is one of your anchor point is running your network as a guest anchor you can have upgrade to 8.8 mr2 and you will be able to form a guest anchor tunnel from the 9800 also from your existing air OS controller which means if some of your sites have aro s can form a tunnel to the guest anchor running 9,800 and some of 9,800 in some of your sites can form a tunnel to your existing errors controller and you can get guest anchor interoperability and the last thing before I end is a config migration now what happens to your arrow S configurations because now we are moving to our sexy the CLI format will be different so what we did is with the three different management tools for an example DNA Center you have already discovered catalyst 9,800 you have a sorry your arrow s controller you have already done a design and policy you just discovered catalyst 9800 all the configurations in the design and the policy what you did will also be get pushed to your 9800 without touching the network without redesigning the network we are giving a prime infrastructure where you can discover and use your existing templates and configure 9800 without changing arises existing templates which has configured arrow s and the last thing is integrated web UI we are integrating a tool on the web UI where you click on it import your arrow S configuration it will export your configuration which can go on 9800 you click on apply and the config gets applied onto the controller so very seamless migration from an existing arrow s to catalyst 9800 controllers with this thank you so very much in case if you have any questions maybe I can answer those I have lots of questions sure you said that your gonna have an API that does Netcom and yang are we gonna have full access to that API or is it only for configuration no you will have a full access for an opera data as well as the config data so you will be able to configure which means you can provision and you can also read even if you don't have a management tool using a net content yang model so even opera data is available and exposed out ok but we don't just have like a restful JSON API so we have a plan to introduce a rest conv interface also but yes the JSON interface is also present ok all right and will the API have 100 percent or greater feature pair with the CLI exactly and just to give you an example the we have deployed the catalyst 9800 in our existing live network in our building 18 and the entire configuration was done using the net convent yang model okay what new or existing features on this platform are gonna require DNA Center so there is no mandate to have a DNA Center to manage your catalyst 9800 controller but if you want to deploy fabric which is SDA you always recommend to use DNA centers so only for a fabric you need to have a DNA Center but without fabric if you want to deploy a centralized wireless network or a flex connect you can use it without DNA Centauri the prying or of mui or integrated there's not gonna be any any featured checkbox is that if i don't have DNA so now it's not gonna work okay all the features are present on to the catalyst 9800 without DNA center also alright and i assume that it's i/o sexy so all of these wireless services are running containerized inside we ever gonna see a kubernetes pod where we can just deploy that ok can you come again me the question a kubernetes pod or something like that containerized instead of deploying a VM to AWS can we have our hybrid cloud and deploy our services yes sir so what we did it with cactus 9800 the entire software module is very modular it's not running in a container but for an example the are enemies running on are a manager or a mobility is running on a mobility manager so they are independent modules but they are not the containers into an annual saxxy ok so although they are modular they don't depend on each other for an example we have a process where something happens on your honor and mobility will not be impacted something happens under mobility your guest anchor will not be impacted so it's very modular but they are not yet container ok and were there any lessons learned from converge access that were carried over and and addressed directly with us so if you notice right the converge axis again I said was an architecture it was not a platform it was supported on two platforms it was lacking features it was lacking manageability it was lacking an architecture where you can have a seamless transition we'll like a lot of stability - with catalyst 9800 if you notice we have a feature parity with the latest release which we just launched on arrow s we have a manageability story where we are manageable from DNA Center Prime web UI open any programmable interfaces and as I showed you the innovations what we did for always-on and secure and deploy anywhere the flexibility of deploying a software on either an appliance or a virtual machine and the scale if you notice the converge axis was not able to scale and we are scaling up to 6000 APs and 64,000 kline even on a virtual machine and on top of it the stability we have deployed from last six months this catalyst 9800 controller in the entire building with no backup SSID on the air OS controller which means if your network goes down you go home so the entire building is running on the catalyst 9800 controller and we did multiple EF T's with our customers in production network maybe we have got a very good feedback and this I mean this is a complete rewrite there's no this is an arrow s ported over it's been from crowns up with confidence everything is written from the scratch using all the features which were available on iOS XE and taking all the excellence what we already have in Aero s

Channel: Tech Field Day

Views: 4,004

Rating: 4.9148936 out of 5

Keywords: Tech Field Day, TFD, Networking Field Day, NFD, Networking Field Day 19, NFD19, Cisco, Automation, Security, IOS, IOS-XE, Office, Wireless, Airespace, AirOS, Access Point, AP

Id: 8VpLM9YqUN0

Length: 36min 52sec (2212 seconds)

Published: Tue Nov 13 2018