Exploring Wi-Fi 7 Access Points and Wireless Innovations

my name is Dave Benham I am a product manager on The Cisco Wireless team and uh I'm going to talk some highlights of some really cool things we've been doing lately uh then M say Kim will come up and dive into some even cooler things in the second half of the presentation so we're going to talk about some new APS we're going to talk about some test results that my friend Jim flck and I did in our RF lab and any locate which is our uh AP Auto location umbrella term and then Ultra reliable Wireless back haul so let's Dive Right In at the show we announced a new uh pair of access points so these are entry level access points the CW 9172 I and H and that is the internal Omni and the hospitality or wall plate version these are direct replacements for the 9162 that level of access point um get into some details I've highlighted the differences between the two and green on this slide uh the coolest thing about these APS to me is that they are fully functional the radios are fully functional on 30 watts of power so there are some things that shut off we turn off the USB port on the I we don't allow Poe out on the H because there's no more Poe to spare but on 30 Watts radio is fully functional they are uh very capable APS for for their size you can see they are each six spatial streams and the cw9 172i you can select whether you want triband or a more robust dual band AP so it can be 2x two on all three bands or it can be 2 by two on two4 and 4x4 on 5 GHz you have that option doesn't have that option on the hospitality AP so to show you a bit more detail on the the power and what shuts off if you if you draw the power down I've created a couple charts again you can see at the the poe+ level the radi are the exact same as the upoe level so you're able to uh get full radio functionality and then it shows the various things that states things as we uh draw the power back uh what what shuts off or degrades of course these APS use our Global use AP operation technology or process I should say that we introduced with Wi-Fi 7 we also call it Guapo and what this is is ah yes yes naturally the aps are handsome so uh these are uh single PID devices we don't have a skew for Europe and a skew for United States or a skew for moroi mode and a skew for Catalyst or controller based mode one skew for all the things and I will dive into a little bit about what that looks like so because we did one skew there's a process that needs to happen when you power these things on the first time to determine what the heck they are what country am I in what should I be am I cloud-based am I controller based and that process takes a little bit of time to to go through the first boot only once the first boot is complete stays in that mode until you reset it or change it um there's no country code configured by default it it deres that automatically through a whole number of ways including GPS and neighboring access points Cloud connectivity Etc there are of course ways to deal with that if you don't have you're completely air gapped we can absolutely take care of it but most customers will do it automatically this is what the process yeah go ahead so if you were for example wanting to deploy this at a a m office you would recommended you ship it to yourself centrally configure it and then ship it to the team or would it be could you remotely the best part about it is you have the option to do either uh you could stage it and then clear the country code and ship it to the remote location in another country and it will ReDiscover the country code but save the configuration when it gets there okay or you could ship it over there and configure the whole thing you could use plugin play uh the beauty of it is it will figure itself out regardless uh you don't generally uh want to leave a country code configured and ship it to another country but we let you just reset only the country code or both you can reset the config as well of course cool so this is what the process looks like just real briefly uh you may have seen this slide before but when it boots it needs to determine whether it is moroi or cloud-based versus controller based and that process starts by checking the moroi cloud looking for whether it's been claimed in a network things like that if it doesn't see itself in the cloud it will then start to discover controllers via the existing means you're familiar with for controller based APS there's a way to shortcut this as well to to speed things up but uh you get that part it it figures out it's country code it figures out its mode day one operation it stays that way every time you reboot it it doesn't do that Discovery again it remembers that it has this country code and this mode you can convert between the two you no longer have to open a tack case to convert from moroi back to Catalyst you can do it either way as many times as you want and then of course you can factory reset it and if you factory reset it it goes back to the beginning and starts that Discovery process again so I just want to reiterate if you do nothing treat it just like an older access point it will function it will get there it just takes longer might take 15 minutes the first time it boots to figure all this stuff out and then it will proceed with the normal boot but you can use some DHCP option 43 values new values to kick it one way or the other whether you want it to be controller or cloud-based the options are there I also want to cover some stress test results my friend friend Jim and I went to Richfield Ohio and uh ran some tests with Wi-Fi 7 uh to see if we could break mlo basically we wanted to see what happened when we really loaded some APS down and if you did things poorly or incorrectly uh or if your environment dictates that you have some Channel overlap and that sort of thing so we wanted to see how bad we could break it um this is the the overlay of the or the overview of the uh test play out we had 20 Windows laptops in four groups of five and we were pushing traffic to them with ex Chariot and each of them receiv received two flows and I'll give you the aggregate flow uh data here in a second but we were pushing them as hard as we could these were dualband clients or triband but using two bands five and six gahz clients and the aps of course were five and six GHz as well they were placed about 15 M apart through a wall kind of a typical spacing and then we also SPAC the clients out you can see the blue rectangles on the map are the tables we had the the laptops on so the first test is all radios on separate channels basically the correct way to deploy Wi-Fi nothing overlapping uh we got about 2.8 gig of of average overall throughput that's the complete amount to all clients now you might think that seems pretty low for 20 clients when you're at Wi-Fi 7 but we were literally doing bidirectional Full Throttle traffic to 20 clients at once on two APS I think that's a pretty impressive number considering what was going on mean everything screaming at each other at the same time in both directions uh latency stayed pretty low around 65 milliseconds looked really good so then we started to break things in various ways we put the 5 gigz radios on the same channel with the same primaries right not ideal right uh you can see that the throughput didn't change whole lot the latency just about doubled but the throughput is still pretty good most of the data is happening on 6 GHz in this I mean in this demo that's clients seem to prefer 6 GHz for High throughput stuff uh so it didn't affect it a whole lot so we decided to keep breaking stuff then we flip the primary so same channel but on different primar so the aps can't really see each other they can't coordinate back off anything they're just stepping on each other that hurt it really bad you can see the throughput went down to 1.2 gig and almost 400 milliseconds of latency so big difference there when when you have a full conflict on 5 gig and we decided to play with the 6 gz side so we put 5 GHz back on separate channels the way it should be and we split 6 GHz you can see throughput came up a little bit latency got a little bit better but it's still pretty rough and that's interesting uh because 5 GHz when we put them on the same channel it was still pretty good so thinking maybe management traffic might be on one band versus data on the other that sort of thing every client behaves a little bit differently but this is just some food for thought uh from was mimicking an actual deployment so lastly we put five gig on separate channels again and we misalign the 6 gig primary so this is the worst case scenario for 6 GHz uh same channel but different primaries throughput came up up a little bit 1.6 but the latency got even worse almost 600 millisecond of latency so just wanted to share some scenarios it's not often that any of us are able to really sit down and kind of lab test to compare uh results from one to another with with consistent surroundings so it was fun wanted to make sure to uh to show it now I want to talk about any locate and uh I've spoke about this before at field days but I want to give you kind of a high level of what it is and talk about the cool stuff we're doing so any locate is an umbrella term for our Advanced location Technologies as well as the AP autoloc function that we have and what it boils down to is the accuracy of AP positions on maps is the fundamental basis for all things location services if your APS aren't placed properly on maps you don't get good location accuracy period nothing will fix your accuracy if your APS are not well placed so the AP autoloc function will autop place APS on maps we've been doing this for a couple years now works pretty well we we've been doing it with fine timing measurement on the Wi-Fi radios and it measures the inter AP distance with FTM between the APS and then computes kind of a matrix of uh locations of APS and the heat map I'm sorry and the heat map also yeah yeah the heat map can can benefit from it as well um primarily we're trying to figure out exactly where the aps are if you rely on heat maps to show your R of coverage they'll of course be more accurate as well we also offer this same technology for client location so you can do FTM with clients but we wanted to step it up take it to the next level with ultra wideband so we have Ultra wideband radios integrated into our 9176 and our 9178 and that's my feeble attempt at an x-ray animation so you may not be familiar with ultra wideband because it has nothing to do with Wi-Fi but it's a short- range highfrequency technology it exists in iPhones and other Android phones for searching for tags and things you've probably seen it it's very very accurate submeter accuracy way less than submeter in a lot of cases um and we we're integrating it to kind of make the existing use cases better and explore new use cases as well so the first use case is that it enhances AP autoloc that we just talked about we're offering this technology between APS so we're combining the results from FTM which were already pretty good and also using WB to get that submeter accuracy so it has made a substantial Improvement in the location accuracy the aps there's that area of certainty or uncertainty that you see sometimes when you're looking at the GPS on your phone you're in a basement it'll be very big shrink down that area gets smaller with uh with these these Technologies combined this is an example of what it might look like for uh AP accuracy with FTM alone so these circles are not coverage areas these are areas of certainty for for the location uh pretty large circles kind of shifted around and this is the AP would be in the center of the circle but I'm trying to depict the difference um this is what it looks like with ultra wideband so much much smaller Circle much more accurate consistent results we're seeing about 95% results better than 2 m accuracy and quite a bit better than one meter accuracy as well and that's a big improvement from FTM and pull me offline I'd be happy to share uh some more details on it I also want to do a bit of a public service announcement because I get this question a lot for our AP autoloc you can absolutely preview before committing you do not have to accept the results so don't I guess don't be scared to run AP autoloc it isn't going to ruin your existing map or locations you can simply run it and it will preview the data and then you can say yes I'll save it or cancel it and this is an all three platforms so it's in beta right now in Catalyst Center but it's public on moroi as well as spaces so all three give you the ability to preview before commit so don't be afraid to to test it out these are the platforms and access points that are supported I won't read through all of them but it's supported on a lot of APs going back a few Generations uh and like I mentioned all of our platforms if you want to test it on Catalyst Center please reach out to me and I can turn it on it's a controlled beta at the moment but I can absolutely turn it on for anyone that wants to test it so the last topic I want to talk about is uwb or Ultra reliable Wireless back haul you ever wish that wireless could just be better essentially lower latency less loss during roaming uh more resilient more redundant Etc you can't do that with Wi-Fi alone today we're working on it but can't get there completely with just Wi-Fi there are some fundamental challenges with the way that Wi-Fi works for example the break before Make nature of the ram it has to disconnect from the current AP before it connects to the next AP you're going to get packet loss in that scenario just naturally that's how it works depending on what you're doing that may or may not affect the application but you'll get some packet loss and you can only connect to one AP at a time of course that's what we're used to so that means can't really be redundant now mlo helps with that you can do two connections or three connections to the same AP potentially different clients handle that differently but it's not a true redundant solution now some of the upcoming Wireless standards May address this when though probably not the initial release uh things are improving but at a slower rate and these are real problems that need to be solved today and we can solve them so we solve them with ultra reliable Wireless back hle which has been around for a while now we've uh 5 years since we acquired fluid mesh the technology has been there but it has always been kind of a separate thing uh it's a points point to point supports pointto point point to multipoint Mesh mobile all the things uh that you would expect for wireless back hle to to uh work um and clients connect through a Cisco so think of it like a on a fork truck in a warehouse or an AG in a in a manufacturing facility there'd be a like a 9165 or some small Cisco AP on that acting as sort of a workg group Bridge would familiar terms to us it would connect to ur WB and the primary benefits of UR WB over Wi-Fi are that it is zero loss roaming true zero loss roaming no packets lost uh the latency is better because the back end is different this is non-wifi uh it it operates on 80211 F but the the whole communication's non- Wi-Fi and uh multipath allows a device to connect to multiple APS at the same time redundantly and send the same traffic two places and it gets joined on the back end so if anything fails you don't lose a frame now that's not the way it's typically deployed but if you have that need it absolutely supports it you can even have two APS on the vehicle connecting to two APS on the infrastructure completely redundant from end to end separate power everything if you want to how many paths are supported two two paths yeah yeah two paths so up until now this is always been a separate infrastructure like I mentioned you had to deploy different APS in this mode uh it's it's been completely separate some of the use cases are manufacturing AGS like I mentioned mining real fast moving things like uh high-speed trains Etc and a typical design would have been 9167 on the ceiling and 9165 on the vehicles that's that's kind of the most common way to deploy it and you're probably thinking why are we talking about this if we've been doing it for 5 years and the reason is because we now offer it integrated into our APS at the same time as Wi-Fi so you can choose one radio and put it in Ur WB mode and have the rest of them doing Wi-Fi so if you have a dual f 5 gig AP one of the five gigs in curb one of the five in Wi-Fi and you lose nothing on the Wi-Fi side you don't need to dual boot to same image for both in the wlc all the same and uh it can be enabled per per radio or via a radio profile in the 9800 and even the vehicle end of it is managed in the W that's an ask that some of our work grou Bridge customers have had for a decade at this point is that they want that mobile end to be manageable and now it is in the wlc and other platforms to come we are still offering the traditional way if you want to deploy this without a wlc or without the rest of the Enterprise Wi-Fi infrastructure uh but the cool thing we're talking about is joining it today and this is an example of what it might look like on on an AP split up the radios one of the fives With Ur WB and one with Wi-Fi so you can service Wi-Fi clients and curb clients or curb devices at the same time these are the aps we are planning to support this may change but this is the the current planned list of supporting this uh mid mid is of this year uh there's a lot of APs on this list again just like with the AP autoloc we went back quite a ways a few generations of APs to to support this uh and there's a a wide breath of access points uh as as well different styles different use case APS I want to show you a video demo a short video demo of what this technology can do this is the demo environment I won't go through it in detail but we have basically a vehicle with two 9165 on it one of them is connected via Wi-Fi and one of them is connected via Ur WB those 9165 have raspberry pies behind them that are generating traffic we we did some stuff in Python made a UDP traffic flow scenario so that we could very accurately show packet loss latency Etc uh they are connecting to 9178 on the ceiling and back to a wlc and a 9167 as the traffic concentrator for the UR WB pretty standard lab setup but uh let's get to the video so the way that we are instrumenting this of course I love grafana you guys know so I threw some stats in grafana uh the left half of this is ur WB the right half is Wi-Fi and we've got on the top chart the uh latency both immediate and average and then in the bottom chart we have Jitter the difference in latency from the last frame as well as packet loss and this will this is live data when we start the video you'll see that uh that it's changing and then along the top I have some tiles that identify the state or the health of things uh in focus on the packet loss one because that's what is is going to be interesting for uh for this time through uh and then we've got some stats in the middle Center at the top there that's a three-minute comparison showing the health of the connections between each other so let me start with the video that's the hallway 9178 access point and uh that's my buddy Chris Williams that is uh pushing a vehicle around in our office We've Got Ur WB on one side and uh Wi-Fi on the other so moving along it's going to roam here shortly if you pay attention to where it says hallway CW 9178 on both sides that's the currently connected access point and that's going to change real soon for both of them and on the left side for curb just roamed nothing changed no packet loss latency didn't change it was like it never happened it roam between the right side also is roaming now it you'll see the AP change momentarily but it lost 51 packets now these packets are UDP frames being every 50 milliseconds so it's an extreme test you wouldn't see 51 pings drop via a simple Wi-Fi Ram but uh we're trying to show you basically how long the outage is as it roams and this is 11R by the way this is not artificially trying to make Wi-Fi look worse we gave it the best scenario on both sides uh so we keep moving back and forth you see another roam there more packet loss on Wi-Fi nothing on Ur WB uh this continues on for a bit back and forth and trust me there's never any packet loss on the UR WB side uh yeah it's it's impressive to see the difference between the two when you're really looking at something like a streaming video or anything where data is is sensitive to packet loss so that is all I had I'm going to turn it over to m Kim it's going to dive he's going to dive into some uh awesome things that we've been working on all right you go M say thank you thank you Dave I'm hoping to have dead Wi-Fi as my home Wi-Fi isn't that great yeah so uh today I brought couple of AI iteration that we have done lately from the last tech field day to uh this uh February and then uh we indeed we made a couple of I mean amazing progression such as the uh generic availability of intelligent capture I've been presenting couple times but it was all about beta lab PC and now it's a fully functional available to everybody about that I will'll also talk about some of the uh monitoring and visibility Improvement for the infrastructure there something that the uh Mar user has not been fully appreciated on the uh some of the abstraction that we have done in the mar dashboard sometime like if you don't see a light then uh everything is green right so we decided to expose everything what's coming under the hood under the scene so now you have a full transparency of the device monitoring in the in this case infrastructure so third case that I want to cover is the uh the AI RM the what happened from past especially from the uh the efficacy of the AI RM which hasn't been covered in the prior topic so let's start from the intelligent capture so what it is and what we trying to do so let's assume the some of the day-to-day operation and uh we all probably know that only time that the net or demain is trying to take a look on the Wi-Fi dashboard is some of the VP and the VIP is having a bad day in the morning so uh it always reported in the uh delayed fashion hey I have some bad things happened my webx my uh my zoom my meeting with my board members in besta when sou hey check out what's happened in Amsterdam right so then the guy sitting in the maybe France or other theater other the continent found that there's a no expert in country level so okay what to do next right okay and looks like this is not the first time happened few times but I really couldn't do much properly and then I still have to figure it out whether it's a network issue or client issue basic 101 of the Wi-Fi trouble shooting so let's get some packet capture right this is a natural progression Next Step so uh to get a packet capture what we have to do let's start from the uh let's just bring my old LP card and try to get some uh hook up my wire shark and then I suddenly bump into a couple of interesting challenges here right first of all I need to know the which AP was serving that client and what was a channel for that part I need to know that which is specific 5 gig Channel they have to looking into and obviously we are living in the high density world there's a multiple AP multiple channel so they okay yeah probably we have to use a channel bonding up to three then realize that that these packets are all encrypted I mean problem was my WebEx meeting problem it wasn't really clear that it was a connectivity problem or application problem but data is encrypted anyway so probably have to take the multiple package capture from The Wire and wireless right and then client might be moved between the 2.5

because of that we enable it especially with the six gig right 5 gig two 2.45 and6 ml right multi Bender PK multi Bender trouble shooting is new Norm with the Wi-Fi 7 how we going to troubleshoot that how we going to take a packet capture right this super challenging I at the moment with the third party tool we probably need to figure out what to do right what about the uh using AP as a packet capture devices given that this is remote EMB bment I don't have anyone onite with a packet capture tool so let's convert AP into s mode pricus mode which is pretty much what we can do today but if we do that what we found is it's all about RX I cently correlate with a specific failure event with a p probably I need use my own brain to make some chronological correlation I need some expert to look at that right what about the packet itself can we get every packet sometime it doesn't right uh C mode AP is sitting on the other side of a corner while the failure is happening the other end right so there's a distance limitation and sometime I need to get are both wired and wireless which is impossible to get the wired because of the packet failure happen on the one AP while the pricus mode AP sitting on the other side we can't get the wired and wir package capture either what about the uh dashboard looks like many Benders kind of approaching hey I have this amazing dashboard tool that you can easily trigger and packet captures and do that lot of things looks like a great idea but the uh what has been the I mean existing tools EXP ience that the network Benders offered there was some debate about whether we should store the pcap historically or not espe important in Europe all this privacy matter but that's probably more compliance not a real technology limit but sometime I do not get the full packet because of the packet capture through the dashboard it take a lot of a backend complexity sometime the many vendors and implementation do not have a full data so in the CCO cases when you designed the inity capture first in the in Catalyst Center four five years ago we had to build a special Mode called the full data packet capture because a regular mode we won't be able to get the full data packet and sometime packet comes in the different order if I get the management Frame data frame let's say that you have uh I mean the block request and Pa in out of order fashion and your pack up is no use right you have to get the proper time stamp and this is a little bit interesting topic I will explain later why this become one of the most common Le discovered scenario espe when to try to capture from the dashboard size limit Wi-Fi 7 m at least uh this one seems to be most advanced topic because of a lot of a vendor try to monetize by adding additional functionality but it doesn't come without their own cavia so let's come back with the uh traditional scenario so this this is a traditional inline package capture so inline means that we are capturing from the data plane of the AP which is great we can get all the data decrypted nice looks like working fine but there's one cavier because of the uh in the design and architecture of AP there's a two split head there's a data plane side main OS you can imagine the host APD wpon those things are all SE on here but there is a Wi-Fi modem does all these low and I mean low layer operation beon proving control frame all happen generated by modem it never go back to data plate so if you try to make take a packet capture often that you miss this whole pieces and you ended up you only got partial packet capture and this is a big problem in the Wi-Fi 7 because of the more and more devices are relying on the uh the the control frame action frame imagine that you are troubleshooting AAR 11 U which is using aqp action frame which all entirely generate from the AP modem not on the main OS so all these problems comes into the way that our package capture has been partially useful but not fully functional what about the uh pricus mode PR promic mode seems like a answer for many cases because I don't need to worry about like a missing packet partial packet but at the same time it's just RX only there's no TX so I only can approach it from the S party view is uh not too different from the uh just having a lpk uh adapter on site but other than that I still have to deal with all the problem that I had in the S party toolway so how we can solve this problem how can move forward right that's why the inter capture comes in I think I've shown this the slide so uh I think that really the visualization let's move on I did that the key point is the internal architecture how we made that happen how Cisco was able to solve all this problem to be honest in the couple of pages that when I leased out the challenge it was only partial it took like it took me 10 minutes to reach down all the problem that we have because there's are so many of limitation that we have in today's packet capture system so what we have done at this time is we redesigned the entire packet capture from ground up at the AP and Hardware level so first of all when you get the uh when you get the package capture the Wii modem itself always replicate the exact outbound the over the air traffic to the packet capture module so it happen all the time so every time we take a packet capture that's why we are able to get the probing and the the uh the the control frame and the the bonting all the time because we are replicating all the time and then of course the data being comes in in order and now the interesting part is how we can make this scalable because simply amount of the management frame and all the data traffic can be overwhelmed that's why we are able to increase or design the special buff so Cisco intelligent capture buff what unique about is we have the uh end number of the link buffer and being equal to client count and how many client we can support for single AP 1,200 a humongous number of concurrent client support and then we have a 1,200 ring buffer so thanks to the new AP Wi-Fi 60 and 7 we just able to get so much of Hardware capacity and now the even the intelligent functionality is fully leveraging uh these inherit Hardware strengths into the product and put together as a solution and uh what it does as a end result I can get a full packet anytime every time time and we don't even even need to do any of a prep work because a system will always automatically capture store and upload to the cloud so there are a lot more exciting architecture from the behind the scene is the cloud layer but I didn't go that too much because uh it might be most interesting but I probably wouldn't cover any second topic so I'll just uh stop that and then uh this is what we have added from the last time uh we didn't show the uh the packet analyzer and back in the last time so now we have a packet analyzer embedded extended with a Wii protocol so uh approach way took was uh because we are gathering the millions and millions of file every day the we were able to kind of a sorting top 10 failure cases and in each top 10 cases we were able to build a special puzzle and the user was able to easily identify which package is the source of the problem what cause and why it cause and all these things available from dashboard with just one click I have a question on the previous slides yep you're copying a wire shark effectively to the that could have privacy data from customers that didn't agree to that yes that's a potential data leak of sensitive data yes so uh that's why that this functionality when we ship it we ship it in disabled fashion so there was a customers comment on the Community page ameran community that why you enabled by default if this is so useful you shouldn't enable disa by default that was the one of concern I need to have a expit end user consent to enable it and then then and another part is uh we are developing the new mechanism of store the packet in their own local private accessory bucket what we call the pyob bring your own bucket so bring your own bucket I think the same question was made by the uh the the Sam the other day we haven't built that yet but that's part of the curon r A2 plan and probably this summer next tech field day we'll be able to update the boob plan yep thank you all right let's get into kick demo I have one last question for the last thing let's say I have a problem with roaming and clients moving so I could fire this up not for a single AP I could fire this up for the let's say all Cisco life yeah absolutely whole Cisco all the AP we have then a comparison function as well where I can let's say follow the client moving from different points so uh right now they when client fail to Rome we actually capture a packet from two different AP and then the first AP roam from AP send the packet to the R 2 AP so when the packet gets sent to a cloud it just sent as a one packet so you you don't need to kind of Stitch the two different p and try to okay where from what which AP to which AP you don't need to worry about it single care failur with a roaming failure we'll have a boss okay yeah and according to that because this is troubleshooting when you have WiFi problems M and I want to go uh a step before that to show more client analytics out of the uh note itself um is there an upgrade yep so uh that's what we called as a single client troubleshooting workflow which are actively working on in fact I have some slide maybe the uh Tony is a PM for that project single client experiences so we'll be able to Tony will be able to show it next time next tech field day which actually combine the Wess and wir are all put together in the historical manner so what I'm saying is if you look at the traditional timeline of a Mara right it only show one aspect which is a wireless timeline it doesn't show any wire timeline it doesn't show me any correlation with the switch capabilities or wind failures or application problem and I have to have it with a contextual manner in the chronological owner right I need to go back to yesterday go back to last week and see what happened on that particular moment with the twit and application that's all putting together and that will replace the current 360 pages of the Mori and that will be a brand new yes Tony no okay okay plus um I mean you doing a great job H with with with great state-of-the-art access points and and Hardware but clients rule the Wi-Fi world right correct and troubleshooting Wi-Fi is going from down to top yep so you need more information more client analytics to do better troubleshooting out of taking a 100% 100% I think you are setting the stages for for me in fact Cisco is the only vendor who is getting Gathering or actually getting because they are sending us the propor information of the client connection failure from their supplicant directly over the L2 from the each modem each client to the Cisco AP The bendor Who agreed to sending and actually sending to us right now is Apple all the Apple devices iOS Mac iPad everything every Samsung devices all the a series I mean the the the what's Ser S Series they all sending the propriety suppliant Arrow code to a Cisco AP and the zra we're sending Intel they're sending it the only thing is hey why you demoing us we actually have it already in the DNA Center I probably would have shown it this time but it has been available for quite some time yeah maybe maybe more extra information out of the client before we go troubleshooting and sure capture yeah yeah absolutely I took a note and actually that's indeed one of the project I'm working on so uh looking forward to uh so meet you again next time hopefully yeah that what we call the client analytic project and uh there's some some big thing is actually happening right now uh all right uh Tello I got only five minutes so let me go real real quick because I have a lot to cover today let's get into uh intered capture here so a typical client of overw pages and I know that how to get into detail there's some failures going on authentication failur so uh let's get into the any of let's say the temporary refusal which is super difficult to troubleshoot it in the most of cases right and then uh in such cases a device had been uh Disconnected by AP a few times and let's find out what happened goes to timeline and just filter with the packet capture yeah well you have a package right it said that the client failed during the association and then here just click the view packet capture then now you have a familiar wire shock View and then it also pre-filtered with the colored with a proper I mean the the filtering right we have a e messaging going on so it seems like overall looking okay but uh there is a there is a deauthentication happen from the client uh so I mean from the AP and the AP was not able to handle this client connection properly so then that's why that we have a packet captures enabled with a timeline so now we can work with a device maker to uh continue further deer that why we are getting this messages but in these cases it happen once out of the thousands of authentication cases but probably not so much of a I mean the super duper amazing but the uh when you have a 3 second of disconnection for certain on plan time now you have a full data to uh looking into and deep down uh Del into further that's the key idea here uh let me get into our next topic here I I know that I'm kind of a rushing here but a lot to cover uh I want to start with the basic sometime the ciso saying that uh the I mean the Simplicity is a really rule but no I need to have every single bit of information because that's the whole point of assurance right and 99% time I don't need to look at this but when things go south when AP suddenly got rebooted I need to know why AP got rebooted how was why was there any M happened was there any CP hogging process happened what is my device the trending view of rebooting and uptime condition device up time is a number one requested feature by every customer and we are providing a additional context of the reboot reason so none of this has been available from Ira the past few years and uh I we realize that every Enterprise require this type of information as the most basic found foundational info and now everything is available customer can build their own dashboard uh using the API M grafana support that uh yeah let me uh just quick let me let me cover one just one last because my time is up I will just cover one part we got we got a lot of these things going on but I will skip that I will I just want to cover one thing the whole airm story I mean we've been heard enough right okay I mean yeah it's good so what how much is good how you can convince me right all these things look at slide well so uh what we have done was uh building the AI RM into the measurable I mean the statistic any success has to be measurable right so what is my Wi-Fi performance look like how's my Wi-Fi schore look like which was done by Javier 2018 we use the same algorithm now we can see a before afterward view of the how my network behave how's my channel changes Channel changes often become a big source of the UN unplanned disconnection and now the channel change being measured monitored and now see that how Channel changes I mean contained afterm what is my core Channel interference which is number one reason of the bad Wi-Fi and now I can see my core Channel interference Trend before afterwards not only that we can compare it with the global am man fion so this actually measured with the p with a very CH pick does the it's not done by the industry we CH picked by Network density we have a metric called the network deny metric so NDM and we took the same NDM and based on the similarly I mean distributed AP we know that which how my network behave compared to the similarly dance AP in the same Tri metric it's all about RF yes but but uh these are R RRM insights what about armm insights AI armm adaptive radio met ah adaptive radio metric so uh we are working on the building the ARF house metric as a separate dashb and then uh right now our has dashboard is scheduled in the coming months not this time so uh stay tuned and we'll be able to update that on the next tech Field Day update

2025-02-27 18:38

Other news