– [Lauren] Imagine that you’re a director
of IT for a major hospital. – [Robb] That’s a big deal. Lots of users,
high expectations. – Yeah. They all depend on you.
The doctors, nurses, patients, visitors, they all want a great network. – A secure network. It’s got to be robust,
ready for anything, especially if it impacts quality of care. – And security has to be high on your
priority list. Lots of people to control. – Yeah, security. It’s not just people.
There’s lighting, there’s A/C, we’ve got medical equipment coming online. – Yeah, is your team ready?
Do you even have the budget? – We are not ready. We spent all our time
troubleshooting. We never even get budget with these new projects that come along. – Yeah, that reminds me. Dr.
Stone called yesterday. Another problem with her conference call. – Oh yeah. No, I know Dr. Stone.
We’ve been troubleshooting that issue for hours and got nothing. – Nothing. How do you know it won’t happen
again, let’s say, with her board of directors call? – Well that’s the big question for
everyone. How can we get out of firefighting mode and in front of
all these network demands? – Well Cisco’s intent based network
provides answers to this and so many other things we thought we would be dealing with
forever. – All new network superpowers for
DNA Center now with DNA assurance. – More than 60 telemetry sources for
real-time analytics, taking that extra step,
closing the feedback loop through automation. – You will never look at your network the
same way again, literally. DNA Center is the only interface you’re
going to need. – And Rob kicks us off with Ronnie Ray,
Cisco’s senior director of product management right now. ♪ [music] ♪ – Well Cisco’s making so many moves when
it comes to intent based networking and change is happening so fast,
so Ronnie Ray, that is why I am so glad to have you here to help us understand how
we’re…what the vision is, and then how we’re executing against the
vision. Is that fair? – [Ronnie] Absolutely, Robb. So in fact,
what Cisco’s launched back in July was intent-based networking.
And if you recall, we talked about software defined access being the
spearhead of the vision, and being able to express intent and make
the network into a single fabric. So we talked a lot about designing.
We talk about policy. We talked about provisioning,
and how automation really translates that business intent into abstract and network
configuration. And then now what we’re adding onto that is the ability to do
telemetry on the network. So really understanding context from the
network, bringing them back into what we call, and at that time when we launched
the DNA Center, and being able to close that loop. So now we have automation and
assurance analytics all working together. – So in my oversimplified view of things,
we’ve really got SD access, which has really turned the complexity of
the network VLANs, and all the different complexities for doing segmentation and
how to implement policy, we’ve simplified that not because it went
away, but we’ve let the machines do more of the work, if you will,
by first kind of creating a virtual switch essentially out of the entire network
through the fabric of SDA. But now DNA Center becomes kind of that
centralized access to absolutely everything.
It feels like DNA, the understanding of what we can do now with DNA Center
becomes really, really important to understanding the genius behind
everything that’s being done. Because it feels like you can do
everything with DNA Center. – No you’re absolutely right. In fact,
this is basically the platform that the network operator now needs to go to to
basically manage the entire network, both as a single fabric,
or even in the transition process. If they have in a traditional networks and
kind of moving to the fabric over time and they’re starting with the building or a
floor, and then kind of expanding around the campus, and then to the
branches, as they go through the transition,
DNA Center manages it all. – And so there’s no more what interface do
I go to for this or how do I actually implement this? Chances are you’re going
to get the high level picture and then you can dive deeper as necessary because we’ve
talked about kind of the provisioning and the design, the deployment and such within
DNA Center. Today we’re going to talk about assurance and kind of taking in some
of this telemetry and the way it’s being crunched into some goodness. But first,
let’s understand why now? Because it feels like we’ve had tools to
be able to understand what our network is doing. But do you think that we’ve
really understood what is happening on our network to the degree we need to? – So what has happened, Robb,
is that the amount of data the network operators have to consume has just
exploded. And in fact what we find is that more than 40% of the time,
they’re just trying to collect data. Forget about how to look at data and how
to analyze data, and therefore actually make changes to the network.
So what we’re doing with DNA Center in fact is because we are getting this
humungous mass of data, and sometimes volumes of data points
across thousands of devices, some being streamed in at real-time with
new telemetry that’s now in the Cisco devices, DNA Center is able to
absolve that, really be able to synthesize that into what’s the right place where the
issue’s actually happening, understand where the right time is in
terms of. For example when a user calls into the network ops,
and then they’re trying to talk about something that happened in the past,
DNA Center is able to replay the network and take it back into the past so that the
network operators has a full view, not just about what’s happening now,
but what happened in an earlier time. And then finally what it also does is it’s
basically the problem resolution process which is it’s giving steps to the network
operators, let’s say, here’s are the steps that you literally
want to take to resolve that problem. And this is 30 years of Cisco expertise
that’s now slowly getting built into the tool. – You said a lot there.
And so I’d like to break some of those down a little bit further to make sure we
got this right. So first it sounds like the notion of context becomes very
important in terms of when we look at this data, it’s not in isolation any
longer. It feels like as a troubleshooter myself, IT operations,
I might be looking at different things and then I myself have to then figure out how
to kind of correlate those things together to…which is great, but sometimes I can’t
move fast enough to be able to do that. It sounds like you’re saying this is being
done for us with the analysis engine or the correlation engine,
or however you would call it there, and then being presented to us in a way
that is more actionable? – You’re absolutely right, Robb.
So if you look at the paradigm of network management,
it was all about that I would collect data, I would probably make it in
reports, and I would put it up and represent it to a network operator to
actually make all the deductions as to what exactly was going on.
Now what we’re doing with DNA Center is basically it is an analytics engine.
So it is correlating insights from all of that data instead of just representing
just data as reports, what we are saying is we can get to the
heart of the issue, which is exactly what the issue is happening by really crunching
through the data, so it’s all machine based. Right now we’re using in a
multidata correlation lots of statistical techniques to kind of get to that,
really that essence of the data, what the insight is.
And so that it becomes immediately actionable. – Okay, so now you mentioned right place,
right time, right action, I believe. So right place, you’re talking about where
we’re getting the data from? – So the right place is about where we’re
getting the data from and where the problem is. So it’s about the breadth.
So we’re looking at router switches, wireless action points.
We’re looking at client users and application data. So crunching through all
of that to say if there’s a problem that is, whether it’s happening now,
whether it happened in the past, whether it might happen in the future,
where is that problem? So finding the right place of the problem,
including even sometimes the location. For example, you might be facing a
wireless issue in a particular building in a particular floor.
So all of that is part of the right place. – So talk about right time for a second,
because as you mentioned wireless, I feel like that is an area ripe for
improvement in terms of…well just feels like wireless has a lot of things that can
go wrong. It’s just the nature of the beast, dealing with radio frequency
in areas that change constantly. When you talk about time,
you mentioned the ability to go back in history. Is this the ability to say
something happened yesterday on wireless and it since has corrected itself as the
system will do, but yet we want to prevent it from happening again.
Are we getting the ability now to be able to go back and say what caused that? – That is exactly what DNA Center does,
Robb. So if you look at the biggest issue for network operators when the user calls
in and says I had this issue in a meeting yesterday. And in this meeting
room, but I really don’t have any contextual information as to how to go and
troubleshoot that. I might have some historical charts that tell me, okay,
that point in time this was happening to a particular metric, but it’s not connected.
So what DNA Center’s doing is creating a connected graph of relationships.
So I could basically dial back the network in time, go back to the time the issue
actually happened, and look at where was the user, what location was it,
which EP or she was connected on? What was the switch,
what applications were being consumed at that point in time?
What is happening in the environment? All of that is connected in almost a
network graph that is maintained over 14 days. So I could in a 14 day
timeframe, and that timeframe will increase as we go forward in the product. – It’s almost like a replay,
or just rewind, or kind of a TiVo for your network to a certain sense.
– It is a TiVo, exactly. – Oh that’s excellent. I like that.
So when you mentioned right action, I’m thinking about the fact that it feels
like we’re making moves toward taking the step further instead of saying we present
all this to you, we’re starting to make, I think what you were calling it guided
remediation? Is that the right terminology? – Absolutely. So this is all about how do
I resolve the problem? And so what we’re doing is we’re taking in
all of our technical marketing engineers, technical experts that run Cisco,
they’ve been writing books. I mean, they’ve been doing Cisco evaluating
designs. They’ve been in our TAC, which is a technical services has been
helping customers. We’re taking that combined knowledge and starting to put it
in the tool so that now almost when you’re trying to find that needle in the
haystack, you almost have a Cisco virtual workforce with you as a network operator
that’s helping you saying, okay, the power be with you because Cisco is
with you, and we’ll help you troubleshoot this very, very quickly. – Okay, Ronnie, thank you so much. Guys,
hold on. We’re going to get more details on DNA Center assurance.
It looks like Lauren is ready in the lab right now. Lauren, why don’t you take us
over? – That’s right, and we are.
But first I want to point out the hardware that actually contains the DNA Center
appliance. We have that right here. Today of course we’re going to concentrate
on assurance. So tell me about assurance, Ramit. – [Ramit] Yeah, so DNA Assurance is the
next space in our intent based journey where we are now actually going to use
context to really provide end to end view, 360 degree view for your entire network,
starting from users all the way to the applications. So for example,
you would know what clients you have, if they’re connected,
what’s the health of the client, what are the health of the network
devices, and you know, with the right information, right place,
and right time in mind. – All right, perfect.
So that builds on our whole intent based network, right?
All the automation built in. I know there are four key points.
I see them up here. Let’s start with network telemetry.
Let’s dive right in, right? – Yeah, so what we are bringing is an
analytics engine which actually consumes data from about 13+ different telemetry
sources. You know, not only just from network sources like router switches,
firewalls, but more importantly contextual sources like DSCP, DNS, you know, radius,
location information. – Lot of information within those things.
That’s awesome. So then complex event processing. What does that mean?
It sounds like a bunch of words that could mean a lot of things. – Absolutely. So this is big data
platform. So as we get this information, we go metadata extraction.
We take it through complex event processing which is set up big data
pipelines which allows us to actually take this data and put in a network graph,
property graph. Think of it as a topology map with the user and device,
and all that information correlated on top of it with once again the location,
and time aspect of it. – Very important things when you’re trying
to troubleshoot, right? – Absolutely. – Or at least maintain even. You know,
it all come in. And I assume then that from that big data we get the analytics
and then we can make these correlated insights,
actually create information out of these things, right? – Yeah, so we actually use statistical
analysis, you know, time series analysis, predictive modeling,
and machine learning algorithms, you know, do identify patterns, right?
And which allows us to then generate insights about what’s happening in your
network, you know? If there’s an issue, how many clients are affected? – That could be a big deal, right?
If it’s one client, maybe it’s just the password issue. If it’s 20,
then maybe there’s something bigger going on.
– More serious, yeah. – Right. All right, so then guided
remediation actions. I mean, that’s the important part, right?
So that’s great. We can identify what’s gone wrong, but how do we fix it? – Yeah, so look. A lot of tools today,
they provide you alarms and, you know, all those alerts. But the goal here is not
only to tell you, you know, what the problem, where the problem is,
but also how to solve it. And we are using, you know,
three decades of Cisco IP, you know, to really help you quickly troubleshoot
the issue and remediate that issue. – I imagine prioritization is a big thing
there too. I mean, I remember getting a million different alerts from a billion
different devices and all that. So this makes it a little easier I
imagine. – Absolutely. So you know,
depending upon the type of the device, you know, if it’s a core device,
then it’s a high priority. If there is a single user affecting,
you know, a lot of users, then all those are bumped up in priority.
What you’re looking at right now is the landing page for DNA Assurance starting
with at the very top, what you have is the map.
And in the map you see these beautiful circles. These actually
represent the sites, and the color represents the health of
those sites. The goal here is try to get to quickly identify the sites which are
having problems. And the size of the circles here represents, you know,
the overall size of that site, like based on the number of devices,
the number of clients. For example, if I click on any one of these sites,
you can see that, here, this site is doing great. You know,
clients as well as network devices. – I like that. – Yeah. And then if you scroll down,
we are also providing, you know, an overall health of your network.
You can see the health of your core devices, access distribution,
you know, routers, wireless. We can see that wireless right now is
about 57% healthy. We’ll double click on that. And then we also provide the
health of the clients, right? You know, distribution between wired and wireless
clients, you know, wired is doing great. Typically it’s always wireless, right?
And obviously you can see that wireless is having some issues. – So the networks, like the core routers,
the network switches, and things like that,
client might be whatever client devices are using the network. – Absolutely. Yeah, these are like you
know, your PC, your phone, your iPad, so on and so forth.
– Okay. – Yeah, and down below,
what we also show are, you know, top 10 global issues.
Now the way we define global issues are any time an issue is affecting, you know,
multiple clients and multiple locations, once again with the appropriate priority,
they’re just bumped up to the top to bring users’ attention to what are some of those
issues, you know, that are affecting my entire network. – That makes sense. Those are the ones you
want to tackle first. – Yeah, so why don’t you take a look at
one of the issues, right, the global issues? It says wireless
clients fail to connect. And as you can see, there are six wireless
clients that are affected by this particular issue. I can see the data
leading up to the issue, you know, so you can see sort of the baseline right
here. And also, you can see all those five clients. So every one of these are
hot links that takes you to the actual user client 360 degree page. – That’s awesome. – And down below, these are the suggested
actions, which really help you to solve the problem. – Very cool. Yeah, let’s dive into some
more use cases. – So now we are in client health.
And you can see very top, what we have is the…we call it the spark
chart, which essentially shows you over time the health of the clients.
I can see right now, you know, my clients are 86% healthy.
They are 26 active clients. So all the clients that I have in my
network are, you know, online there. There are no inactive clients right now.
But then also shows, you know, health of some of those clients are not
that great. We also have distribution, you know, shown between wireless and
wired. Wireless is where we want to double-click. You can,
every one of these charts have second level or third level drill downs.
So if you want to get more information about what are some of those clients which
are having problems so that I can get that information right here. – Makes it a lot easier to chase down
rather than maybe getting on the CLI, saying who’s not connecting,
all that good stuff. – Yeah. And if you scroll down a little
bit more, we can see the client times and onboarding times. So in the wireless
world, one of the key metrics is how long it is taking for my clients to onboard to
wireless network. Here are, you know, we are providing analytics to show you
very quickly, you know, how much time is being taken by, you know,
clients in the network. – My hotel chain could use this,
by the way, because I struggled with that this week. – And so from here, once again you can get
down to the actual details. I can see that hey, look for any one of
these bars, I can see like, you know, the clients which took less than four
seconds, and the relative distribution, that four seconds between your association
AAA, DHCP, so on and so forth. And you can quickly zoom into, you know,
the clients which are the ones which are actually exceeding the 10 seconds
threshold. And I can see that I have one client which is exceeding that threshold.
You can double-click and get more information there… – So if you’re seeing like a AAA problem,
maybe they just don’t know their password, or they’re the right username.
But if it’s a DHCP problem, maybe you need to go check out your DHCP
server, cool. – And then we also have,
we show information regarding the RL signal strength indicator. Once again,
what percentage of my users have good signal strength. That shows a quality of
the connection. And I can see that the majority of them have a good signal
strength, but there are few, about 6.58% of my users are having low
signal strength. And once again, you can go into the details and get more
information regarding that. – So they shouldn’t be streaming Netflix
or something like that. – Yes. And then we have the client table
where you can get, you know, a lot of detailed information.
There are lot of filters. You can just filter based on the clients
which have poor connectivity all the way up to, you know, show me all the clients,
right? I just want to look at the wireless clients. And you can get all the
information, you know, from the user ID, to the host name, to the MAC IP,
the onboarding health, connected health. And if the wireless client,
what SSID is connected on, right? What AP it is currently connected to,
and you know, so on and so forth. – So let’s say, you know,
yesterday I had a problem connecting with, you know whatever, my tablet, or my PC,
whatever, would you be able to troubleshoot that even though I’m like
yesterday at 3:00 p.m. But I’m not there today,
so can you help me out? – I think we have the perfect user for
you. The user’s name is Daphine. – Okay. – We have client 360 and user 360.
The subtle distinction between the two is a user may have multiple devices.
So a device is called a client. And the user is called a user.
So we started with the user 360. But as you can see, the user in this case
has two different devices, so essentially two clients.
Here I can actually look at, get more information regarding these
devices. But the user device or the client that supposedly in this particular case I
can see that was having a problem yesterday just by looking at the,
you know, the health time series chart right at the top. Which think of it as a
DVR. Think of it as a, you know, network time travel.
We’ll get to that in just a second. But let’s just quickly take a look at what
other information we have on this page. – Okay. – Starting with at the very top,
you can see that the system identifies any kind of issues or insights related to
that. I can see that hey, you know, the user, he has been browsing application
exceeded some thresholds. – So like it’s similar to the previous
dashboard that you showed us, but these are no longer global.
These are user issues. – Yeah, client specific, exactly.
This is the logical topology showing, you know, which RSSI and AP it is
connected to and managed by a particular WLC. Then we have information
regarding the application. So in this particular case, you
can see that, you know, we have, it’s split between business relevant,
irrelevant, and default down to the actual throughput and the packet loss, lead,
and jitter information. And at the very bottom,
we show the device information, as well as the RF. Like you know,
what the RSSI or the signal to noise ratio for that client is.
– Yeah, so you can really go deep. – Yes, yes. So why don’t we go back and
take a look at…so the issue the client was having yesterday and troubleshoot what was
happening. So make a note that right now that client currently is connected to an
SSI Corporate-2. So we’re going to go to the top, and we are going to go on the
time series here. And then we’ll go ahead and click somewhere here because this is
where I can see the client was having problem. So as soon as I click,
you’ll notice that the information on the screen kind of refreshed.
So the very first thing I want to bring your attention to is look,
we are looking in the past, like yesterday as if you were there at
that time. So here you can see that the client at that time had a health of one
obviously. They were not able to connect. And then the client was trying to connect
to a different SSID. – It’s guest-2 rather than what was
corporate-2. – Exactly. Guest-2, not corporate-2.
And then at the same time, the system as and when this problem
happened, the system also detected an issue, right? So let’s take a look at
what’s going on. So let’s take a look at the very first issue at the very top,
because that’s essentially coincides with exactly the time the user was having
a problem. So when we click on this, you can see that the client was trying to
guest-2. This was the AP, the band, failed to authenticate due to client site
timeout. Probably the client didn’t put the right username and password,
or didn’t respond back. You can see the appropriate location of
the client on the floor map. You can see once again the data leading up
to that, the number of attempts the client made. And last but not least,
three of the clients which are on that AP, which were kind of having similar issues,
right? And then once again down below, you know, actions in how to solve the
problem. – How do you fix it?
– Exactly. – And I do like that it’s intuitive.
That it stays with the same general schema of following the dashboards,
and following it to those actionable remediation tips. So that’s very cool.
Awesome. So let’s say I have another problem. Let’s say I can’t print,
which actually happened yesterday to me. And I’m not even making that up.
Twenty minutes spent. – Okay so we have an option here called
Path Trace, right? So we’re going to go ahead and run a path trace so I know the
IP address. Let’s say the IP address of the printer is 10.30.120.10.
That’s the printer. Yes, you can see it’s connected to the
network. Port number is 9100. The DCP, and let’s, why don’t we go ahead and also
collect some additional stats, right? So we’ll go ahead and start.
So now you can see that the system, the amount of time it actually takes a
human being to log into the first device, the system actually went to the network,
and identified the exact path for a given flow, right? Down to the actual cap
web tunnel because this client is connected, iPad connected to AP.
The traffic’s going over cap after the WLC, and then, you know,
from there it goes to the printer. But the issue that we see here is that
there are two places where we have ACLs blocking that traffic.
So why don’t we look at one of those interfaces where the ACL is setting and
get more details. So we go in more details. And you can see a lot of
data here related to the stats that we have collected, and voila,
there is the ACL sitting right there blocking that traffic. – Telling me deny. So it’s working as it
should be, but not working for a user obviously.
– Absolutely. – Very cool. So I know that we based a lot
of this, you know, we’re talking about network intuitive.
We’re talking about intent based networking. We need insights.
We need actionable insights. So let’s dive into the insights that we’re
actually using to allow all of this to happen. – Yeah so you know, we have covered
clients and we looked at network as well. So we provide coverage and insights,
you know, not only for the client but also, for example, switches,
and both for fabric and non-fabric. Here’s an example of some of the
correlated insights that we are providing, right?
So we provide insights for your border/edge reachability,
essentially your control plane, your data plane, your policy plane,
client onboarding, and switching. And these are just, you know,
examples of some of the correlated insights that we can provide. – So things that an admin maybe would have
done manually, very manually, would have had to chase down.
Now we’re doing it automatically and making it a little easier,
and providing actionable insights to remediate. – And these are correlated.
These are multi-variant correlated insights, right?
Looking at different aspects of the users, the client devices, the network, the time,
and all that. So as you know, we provide insights on the wireless side
as well And you know, wireless is a complex area.
Why don’t you call the expert? – I think that’s a perfect idea.
Come on in, Jeremy. Ramit, thank you so much.
That was so awesome. – Thank you. – Jeremy, let’s talk a little bit about
those wireless insights. There are a ton. – [Jeremy] Yeah, there’s a bunch.
– Why? – Why? Well operating a wireless network
is complex. Since users expect the wireless experience to be 100% solid,
we’ve gone through all our lessons learned and added these insights into DNA Center.
So as a network operator, you can easily look through and find,
and pinpoint exactly where the issue might be. – I think that’s amazing.
Obviously wireless is complex and helping out our network admins,
our wireless admins is going to be, I think a fantastic service that we offer
through DNA Center. There are three major innovations I know starting with stream
telemetry, analytics, and sensors, right? So let’s dive into streaming telemetry.
Yes. – Yeah, so with Arrow S 8.5 code,
we introduced streaming telemetry. So it’s primarily for DNA Center where
it’s going to send client information, access point information, rogues, roaming,
all sorts of really juicy, awesome details from the wireless
controller to your DNA Center in a streaming fashion, streaming telemetry
fashion. – And that’s different than an SNMP,
right? So SNMP is pulling information. It’s not necessarily getting in
real-time-ish or as much information. Is that right? – Exactly, so with streaming telemetry,
when an important event happens on your wireless controller,
it’s sent in real-time to your collector, or your DNA Center. So unlike with SNMP
where you have to pull, and you have to know exactly which item to
pull for, now the controller actually sends all that information to you. – All right, so moving onto analytics.
I know Apple and Cisco have this great relationship. We’re doing a lot of
Fastlane optimized Wi-Fi networks, all that good stuff.
Tell me a little bit about the analytics we’re using from that relationship. – For sure, so part of the Cisco/Apple
partnership, the iOS device actually surfaces the neighbor details,
the neighborless as we call it. So this is where your iPhone,
your iPhone device, your iPad, and in the future your MacOS device will
also report back the wireless neighbors that it can hear in the RF environment.
So for example, it can tell us that there’s an access point over here,
over here, over here, and it’ll tell us how well it can receive
that, and some details about what channel it is, and the power levels, for example. – Very cool. So we have the neighborless
and then we have the… – The disassociation details.
– Yes, that’s the word I can’t say. Disassociation details, yeah.
– It’s a little bit of a tongue twister. – Yeah, so what’s that?
That tells us why the client left the network. So did the client,
did the battery die on it? Did it go to idle or sleep mode?
Did the user leave the coverage area? There’s a whole bunch of disconnect
details that are surfaced. So what we’re looking at here is the
client 360. We saw this just a little bit earlier. It’s the same user,
this Daphine user. If we scroll down we actually see the details.
So we have the device information and the RF information. But we also have the iOS
analytics. And this is where the neighbor APs and the client disassociation details
are surfaced. So for the neighbor APs we see that there is like three or four
access points, which channel it’s on, and the signal strength that it’s
receiving the access point from. So again, this is the client’s perspective of the
network. So this is not the infrastructure. This is not how we
design the wireless network to be. But this is how the user actually hears
and receives the wireless signals. And it transmits that back up to the
DNA Center. So we have insight into how well the coverage actually is. – And that, of course,
helps us maintain and troubleshoot very easily, hopefully. – Exactly, yeah, it helps us identify
coverage holes, and a whole bunch of other issues. Let’s talk a little bit
about the client disassociation details. – Okay. – So this is on the right half of the
screen where the client actually tells us when it’s leaving, why it’s leaving.
So with this user here, we see that the user triggered a
disassociation. So that means that the user turned their wireless off,
turned the device off, or just disconnected from the wireless
network. We also see that the device went idle, so that’s when it went into
sleep mode or power save mode to save battery. And that’s why it left
the network. So previously we’ve never had insights like this into why the client
left the network. – Yeah, and that gives us a lot of
information about why things may not be working or are working properly hopefully. – Or why the user doesn’t have data
connectivity anymore. Mm-hm. – Makes perfect sense. All right,
so how are we gathering all this information, right?
We’re using sensors. I think we have new hardware to show based
on this? – Yeah, we do have some new hardware to
show, actually. And this one I have right here is what we call the 1800 dedicated
sensor. So what this is is it acts as a clients, joins the wireless network,
does onboarding, DHCP, and AAA authentication.
And then it can also do some application tests. So it can do email
tests, for example, or FTP tests. It can do a test directly against your
radius server for example, as well. – So it’s actually testing the different
protocols, different ports, and doing all of that.
And this is just a sensor, right? – This is a dedicated sensor.
So we have this capability in the access point 3800 and 2800 series with the FRA,
or flexible radio assignment. This is a dedicated radio in the sensor
right here. – And if you’re using a flexible radio,
that means you’re not acknowledging clients using that one radio of the three
or whatever. – Mm-hm, and the flexible radio,
one of the radios goes into client sensor mode. This is the sensor mode
access dedicated sensor. – Well let’s show what that looks like
when we run sensor tasks, when we’re trying to figure out what’s
wrong in the network using these sensors. – Yeah, so what I have up here on the
screen for the demo is how we configure the sensor driven tests.
So we’ll put in a test suite to test just DHCP and DNS. We’ll keep it really simple.
Hit next. Here we can actually select the sensor that we’re going to use for the
testing. – Beautiful heat map there. – Exactly, yeah. This is the sensor heat
map. So we have just a couple radios, or a couple APs in here.
No dedicated sensor, the dedicated sensor is just right here.
But we do have a 3800 that we have set up just for testing here.
And that’s where we have the checkmark enabled.
– Okay, and that’s the flexible radio. – Yeah, so what’s going to happen when I
click save, it’s actually going to convert one of the flexible radios into a sensor
mode and start performing the test suites. – So everyone can connect.
This also seems like everyone could be a wireless admin now. – Yeah, anyone can be a wireless admin
with DNA Center and with the 1800 series sensor.
– I like that. Thank you so much, Jeremy. – Thanks, Lauren. – Very nice job with those demos.
I think it’s good we get back to that big question. See, everything changes for
IT operators now. – Now DNA Center is your single point of
access to the Cisco Intent Based Network. The 360 contextual view gets you from big
picture right to root cause. – And if we do miss something,
we can rewind time, go back and replay an experience, or even better,
start being more proactive and plan for those high tension events,
or high tension people. – Yeah, DNA Center is your ticket for
getting out of firefighting mode. – Learn more about Cisco’s intent based
network progress online, of course. And by the way, Lauren of course will be
covering even more detail and take questions in the techwiseTV workshop.
It’s live, it’s interactive. You can ask questions.
So look for a registration link below this video. Or as always,
you can go to techwiseTV.com at any time. And don’t forget to follow us on Twitter.
This show is @techwisetv. And also Lauren and I are on there playing
around as well. Facebook should be good. I think we keep that updated. Either way,
thank you for watching. We’ll see you on the next one. ♪ [music] ♪