When you land in Cisco Catalyst Center,
as you can see, we are logged in and we're at the homepage.
What is the homepage?
The homepage is the assurance summary
and the network snapshot.
And of course, assurance is really
what we're here to talk about.
I will point this out, if you're watching this
relatively soon to when I'm recording this,
you might see in the top corner here,
try the new homepage beta.
That beta is obviously going to become
the production site at some point.
So you might be interested in that. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
So you might be interested in that.
The next thing I want to say is there are some things
that you as a learner should pay close attention to.
First of all, the little I, the information.
I know this is one of the easiest buttons to overlook,
but highlight it and read what it says
because this is actually really good stuff.
I know it's kind of like hard to see.
The global client health score is a percentage
of the number of healthy client devices
divided by the total number of client devices. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
divided by the total number of client devices.
So 85% network devices,
that means 85% of our devices are healthy
as opposed to wireless clients where only 44% are healthy
as opposed to wired clients, 95% are healthy.
Remember, DNA Center,
especially from the assurance perspective
is going to break things down
between network devices and clients.
That's really the dividing line.
And then within clients, we have wireless and wired. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
And then within clients, we have wireless and wired.
These are the three main top things
that you who is using assurance
is going to focus in on first.
Now, the next thing that you need to pay attention to
because it's also one of the easiest things to overlook
is the timestamps.
When was this health score created?
Also look at critical issues.
We have four priority one, top priority issues,
six priority two issues. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
six priority two issues.
This is within the last 24 hours.
Compare that to trends and insights
like performance advisories.
We have four performance advisories
that have been discovered and generated
over the last 30 days.
These advisories again are all about machine learning.
It took 30 days worth of data and analytics
to learn what's normal for our network.
And then it can give you advice
on how to performance tune it or fix it. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
on how to performance tune it or fix it.
So without even clicking on anything,
we've already got kind of an idea
as to what we're doing when it comes to monitoring.
Now the network snapshot below,
this is where you get more into design policy and provision
like the number of sites and the number of servers,
the number of network devices,
the number of QoS policies,
the number of network profiles,
pending image updates, licensed devices, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
pending image updates, licensed devices,
certificate issues.
So this isn't really assurancy.
This is really more design-y, policy-y and provision-y.
So assurance is where we really wanna live.
Now the next thing I want you to know
is that these buttons are all clickable.
So they look blue and you've got the little clicky button.
If I wanna look at what's going on
with my wireless clients,
I can click on this 44 right here
and it takes me into a great deal of information
about my wireless clients. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
about my wireless clients.
So notice what it did is it jumped me into assurance,
into the health section of assurance.
And then from here,
it jumped me over to the client section of assurance.
So it's important to kind of understand the UX,
the user experience here.
From assurance, we have a group of dashboards.
And you should think about this.
When I click on health,
it's going to be a group of tabs for me to look into.
Like I said, I've got the main two things WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Like I said, I've got the main two things
that I have insight into are network devices and clients.
Network services are gonna be like DNS, AAA and so on.
And that really kind of is part of the network.
Applications are the apps
that my clients are trying to access.
And then what is the overall health
of the SD access fabric underlying?
We can see right here.
Well, you know what?
I'm tempted to talk about these network devices,
but I'm gonna save that for the next video.
Over here, we have clients, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Over here, we have clients,
but, but, pause, wait, look at this.
We've got kind of a chart that goes this way, right?
My wire clients are 95% healthy, 21 are wired clients,
but it's not a flat line, is it?
It's kind of bumpy like this.
So it makes me wonder,
hmm, 5% of my wired clients aren't healthy.
It does have some peaks and some valleys.
When did this happen?
This is from 1 p.m. to 1 p.m. or a 24 hour period. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
This is from 1 p.m. to 1 p.m. or a 24 hour period.
This is an interesting point.
Again, timestamps matter.
Charts, when you look at a chart,
a chart should be labeled so that you can digest
what goes on on the X axis
and what goes on on the Y axis.
Lots of times, you have quantity over time.
That's what we're usually looking at
when we look at charts.
So what timeframe are we looking at?
That's what you set right here in the top right corner. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
That's what you set right here in the top right corner.
It's the next thing that I want you to know
when it comes to managing working with Assurance.
Now, from this overall client health section,
or excuse me, from the overall health section,
you can scroll down.
We've got our network,
basically everything across the top,
network client, network services, applications, SD access.
You get kind of a dashboard summary
of each one of these things.
You also very luckily get an advertisement
for 1,000 Eyes right there. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
for 1,000 Eyes right there.
We have lots of content on 1,000 Eyes.
Jeff Kish recorded it.
Feel free to check it out.
Scroll on down here.
We have 100% coverage of our entire SD access fabric,
which is 100% in our London One location.
And then, ah, it generates issues for us to look into.
It identifies them by priority.
I see some pretty high priority things like layer two loops.
I also see something that would be curious, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
like a switch power failure.
And I also see wireless clients are failing to connect
based on AAA server rejected clients,
probably wrong passwords.
So before we move on to client things,
well, kind of having a client issue right here
with wireless issues, right?
If I see, look at this,
we've got two rejected clients
and three security parameters mismatch.
What do I know?
What can I learn about this priority three issue right here?
I can give it a click.
It pops up a new window and it says, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
It pops up a new window and it says,
okay, here's the one specific issue that you selected.
Give that a click.
Ah, now we get a lot of interesting info, don't we?
Look at this, look at this.
Description, this client failed
to complete the authentication process during onboarding
because the security parameters are mismatched.
The client was connecting to this SSID
in this location on this floor.
The AP was connected to this wireless LAN controller. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
The AP was connected to this wireless LAN controller.
We can now see which client,
or really the top operating system
that this was coming from right here.
We've got a Linux operating system for ARM devices
as well as Microsoft version 5.0.
And I know you're thinking, but who?
Who is the client that's doing this wrong?
Well, look, you click this little arrow right here.
It shows you when these authentication attempts happened,
what the issue was when it happened and how it occurred. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
what the issue was when it happened and how it occurred.
Click the arrow again.
It shows you the failed attempts
when those happened during this timestamp right here.
Click one more time, there it is.
There's your host name, there's your MAC address,
there's your operating system, there's your AP,
and this is when the most recent thing happened.
So what do you do about it?
Well, right here under Suggested Actions,
it tells you what you can do about it
with three suggested actions of what to do next. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
with three suggested actions of what to do next.
Yes, you can set up for some types of events,
you can set up assurance to automatically heal.
This isn't one of those things.
Something needs to be configured on Sargio Villa's
or Via's or however you want to say it.
You can set something up on there.
You need to go to their machine
and correct the connectivity issue there.
Okay, so let's close this for a second.
We've seen kind of what the idea is here.
You can check out these higher risk ones WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
You can check out these higher risk ones
like the Flaps and the VLANs.
This is a network.
We're gonna talk about the network devices next.
I'm jumping ahead.
We're gonna talk about network connectivity issues next.
Let's jump over to the client section
and take a look at what we have here.
Aha, all of this data, as a reminder,
comes from streaming telemetry.
This is not SNMP traps.
This is not, you know, or not a lot of NetFlow.
There is NetFlow going on.
This is not logging or syslog logging here. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
This is not logging or syslog logging here.
This, and it is collecting syslogs too, mind you.
The big thing that these dashboards generate its data from
is from streaming telemetry.
It gets the data because all of our network devices
are now streaming data into DNA Center,
living in a database,
which DNA Center can then present to you as pretty charts.
Again, most important thing to start with
is understand what your timeframe is.
When is the starting point?
When is the ending point?
Again, we see wireless clients. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Again, we see wireless clients.
We have 18 active clients.
Five are onboarded.
Three are not onboarded.
The ones that are not onboarded
are having authentication issues.
The ones that are onboarded are flipped between,
or they're split basically between good connectivity
and fair connectivity.
So this explains where the 44% healthy comes from.
Fair connectivity is not considered healthy.
It's only considered fair.
Similar chart over here for wired clients. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Similar chart over here for wired clients.
We have 21 clients, 20 are onboarded.
What's up with that other 5%?
Authentication is the problem yet again.
For our London One site, or really all of our sites,
they would all be listed here if we had them.
We can see failed onboarding attempts.
We can see onboarding duration if it took too long,
connection speed, roaming, and roaming duration.
We can see things like relative signal strength.
Scroll down just a little bit right here.
For our wireless clients in that particular location. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
For our wireless clients in that particular location.
Keep scrolling down.
We can see our client count per SSID.
They're all connected to one SSID right here.
It would look like a, well, more colorful donut chart
if we had more SSIDs and they were split up.
The client devices.
Let's scroll down some more.
Look at all these client devices right here.
We see each device by their username,
because remember, SD Access works with TrustSec, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
because remember, SD Access works with TrustSec,
works with ICE, works with AAA.
So when users connect to Wi-Fi,
they're connecting with a username,
not just, you know, a WPA password.
We see, let me ask, we see their health,
how much we trust that that's really them,
are we tracking them, what data usage looks like,
what band, what location,
when they were last seen, and so on.
If I give a click on the client itself,
we can see what that user's usage looks like over time, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
we can see what that user's usage looks like over time,
what their onboarding experience
and their IP assignment was over time.
We can see how their traffic gets routed
to the wireless LAN controller from there.
And I think importantly,
if this specific client were having issues,
you would see those listed right there.
So if a user calls in and they report an issue,
you can jump right to their device
and see if DNA Center, excuse me,
Catalyst Center has already detected an issue.
And that's pretty cool.
We can also use tools. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
We can also use tools.
So scroll down a little bit,
you can see what their event has looked like
as they got IP addresses or got onboarded and so on.
If we scroll down to tools,
we can collect data on this particular device
and what their stuff was like.
We can also see, hmm,
are they trying to connect to a device
and it's failing somewhere?
We can run a path trace to simulate what it would be like
if it runs into a policy failure
or some sort of ACL or something
trying to connect to an application or a server. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
trying to connect to an application or a server.
The path trace can tell us specifically
where that user's request is dying or failing.
All right, let's jump back, back to the client section.
So we've got these wired clients at the top.
There's a view details button.
Let's give that a click right here.
When I log into this,
you may notice that this blue box right here
is clicked for the 21 connected clients.
And I can see those 21 connected clients right here.
But I'm curious about what's going on WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
But I'm curious about what's going on
with the authentication of this one wired client
that's not working.
Well, all I have to do is click on this line
and it's camera two.
Camera two must be misconfigured.
I can see exactly where that's plugged in.
So now I know I can go to this particular switch
right there and see,
okay, well, camera two is plugged in right there.
Something must be wrong with its authentication.
So let's get to camera two and get it resolved. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
So let's get to camera two and get it resolved.
Same thing goes for wireless clients.
If I go into view details for wireless clients right here,
it automatically launches in
with the three not onboarded clients right here.
I can see Anita Cooper, Ruby York and Nia Kamal
are all having issues there.
So if I give Anita Cooper a click,
I can scroll down and see what's going on here
with Anita Cooper.
As of right now,
it looks like Anita Cooper is actually doing okay.
Her traffic analytics look pretty good. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Her traffic analytics look pretty good.
She doesn't have any issues.
But I know that there was an issue in the last 24 hours.
So what I can do is I can scroll down to the event viewer
and scroll down through these events.
And I see, ah, this is where things went wrong.
It was trying to do something with delete
and then something went wrong with onboarding too.
So when I click on onboarding right here,
the failure for onboarding pops up on the right hand side.
I wonder why it was that Anita Cooper right here WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
I wonder why it was that Anita Cooper right here
was trying to log in, scroll down, down, down, down,
log in with the Grace Smith username.
Hmm, suspicious, something we probably should look into.
So as you can tell,
the whole point of Catalyst Center
really focuses in on the clients,
the client getting connected and the client roaming
and all of their stuff following them.
Notice at no point in this content so far WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Notice at no point in this content so far
have I showed you in Catalyst Center
anything that says ISIS, VXLAN, LISP or TrustSec, right?
Because it's not the point of Catalyst Center.
Catalyst Center does that for you behind the scenes.
You're supposed to focus on the client
and getting these charts right here
to show that the client experience
is working the way you expect it to.
Now the client is a big part of the story,
the main part of the story,
but the underlying network also matters too WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
but the underlying network also matters too
and that's what we're gonna talk about in the next video.