After you've got the feel for how working with Assurance
and the client dashboards and the client interactions work,
seeing it from the network perspective
is not going to be that earth shattering.
It's a lot of the same things,
it's just now we're looking at network devices
as opposed to our users.
And the thing is, we can configure,
like DNA Center, excuse me, Catalyst Center
is gonna configure the network devices
and the configuration itself will probably be just fine. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
and the configuration itself will probably be just fine.
There are still things in the environment
that can make a wireless access points perform worse.
We can still see switch ports fail.
We can still see PoE issues come up
because we don't have the right PoE device
get plugged into the right switch and so on.
So when we onboard our devices, DNA Center,
I keep saying DNA Center, it's Catalyst Center now,
but it'll always be a DNA Center to me. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
It still does a pretty good job of categorizing
what's a router and what's not,
what's part of a core switch,
a distribution switch and an access switch,
what's the wireless controller and what's the access point.
Notice here, we also have 85 devices.
We see what percentage of them are in good health.
Of course, that's the 85%.
And then the seven devices that we have right here
of those 85 make up the other 15%. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Even fair health is not good enough.
And of course, right here, we can see
what the breakdown is for good, fair, or even poor.
Notice you've got a little legend here
to help you figure that out as well.
So you're thinking to yourself,
well, this should be clickable
and I should be able to dig into what's fair
and what's poor, right?
Of course it is.
So I'll click on distribution here
and it's not really clicking, is it?
Well, that's a little interesting.
That's because the breakdown you're looking for
is actually just scroll down just a hair WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
is actually just scroll down just a hair
under network devices.
And then you can filter out by overall health.
We could do all.
And maybe I'm interested in those distribution devices.
So I see what my distribution devices look like right here.
The overall health score column lives right here.
And that tells me something might be going on
in the San Jose office.
So if I click off this
and click on the actual host name of the device itself, WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
and click on the actual host name of the device itself,
it brings up the host name itself
and we can see what the overall look is.
Again, keep in mind what your timeframes are.
So we're looking at a 24 hour period
up till basically now and see what's going on.
I have no current issues that we have right here.
There's none listed for this particular device,
even though it's only got fair health.
Now these buttons right here
are just so that you can jump quickly
to the following sections below.
For instance, if I'm really only interested WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
For instance, if I'm really only interested
on the interfaces of this particular device,
I can click on the interfaces
and then we can see what their current status is
for each one of these interfaces that we have here.
Also fun to note, notice look here,
this is under detail information
and then the interfaces tab.
You won't see this by default if you're just scrolling.
You'll see device info by default,
at which point you'll see things like how's the RAM,
how's the CPU usage,
and what's the temperature of this particular device. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
and what's the temperature of this particular device.
Go to the interfaces
and this is where you can actually see the interfaces here.
Now you can check the box
and it'll show you things
like what the interface availability is,
but notice there's no real configurations
that you have here.
It's just the statistics on those interface
that you selected.
You can think about it kind of like this.
If there's a show command for this particular interface,
the output of that show command
is streamed to Catalyst Center as telemetry. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
is streamed to Catalyst Center as telemetry.
And that's what ultimately gets translated
into a overtime chart that you see below.
So that's what's going on there.
Also under interfaces,
you can do filters with access ports,
auto ports, layer three routed ports, and trunk ports.
Now it does say 37 of the 42 interfaces are down.
That doesn't mean 37 of them are administratively down.
Looks like only one of them is administratively down. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
Looks like only one of them is administratively down.
The others just don't have anything plugged into them.
It's basically what that means.
Let's jump back to the network section real quick
and we can see some other interesting things.
We see that all my APs are up currently.
That's a good thing.
If we had down APs,
of course they would be listed right here
in this donut chart
in a different color other than purple.
I wanna call it purple, it's kind of blue.
We can see what the most saturated APs are,
the top X, top N number of APs by client count. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
the top X, top N number of APs by client count.
Basically that depends on how many APs you have.
It shows the top five right here by default
based on client count.
And the top APs that are experiencing high interference.
Notice here, it's again in that San Jose location, SJ1,
two of these APs are experiencing high interference.
Now let's scroll down a little bit
just past these network devices
because we already looked at the network devices
a little bit and look at the bottom here. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
a little bit and look at the bottom here.
We've got WAN link utilization.
I find this to be one of the most confusing charts
that you can see because the description,
60% of WAN links are utilized less than 80%.
Okay, you gotta think about this.
The majority of our WAN links
are not being utilized very much.
They're not even utilizing more than 20% of that link.
So that's an interesting thing to digest.
Just wish there was a better way to word this
as well as visualize it. WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
as well as visualize it.
Especially when this marker right here says greater than 80
but up here it says less than 80, it's just confusing.
Again, above we would see things like wireless access points
or wireless LAN controller issues.
Here we have a similar chart
that shows me 31 devices that are reachable.
If one wasn't reachable, it would be showing up here
in that donut chart as well.
So I think one of the interesting things WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
So I think one of the interesting things
to take away from this
is that the network assurance section
helps you to identify a device
that might not be performing well
and maybe an issue or two that's going on with it
but you don't have nearly as much to do
as you do the client section.
And that makes sense
because SD access is really all about the client
and the network devices just facilitate it.
So as long as those devices are on
and they can communicate back to the control plane WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
and they can communicate back to the control plane
which is Catalyst Center,
it's probably gonna be fine.
The majority of your network work within Catalyst Center
is gonna be around APs.
I mean, the majority of devices these days are wireless.
We know this, this is a statistic
that all the devices on a network,
the majority of them are wireless.
And wireless devices are the ones that things can go wrong.
They can get out of range,
they could have overlapping frequencies,
they could have interference WEBVTT X-TIMESTAMP-MAP=MPEGTS:0,LOCAL:00:00:00.000
they could have interference
and so on and so on and so on.
So again, similar workflow into managing
and troubleshooting your networks with Catalyst Center,
in this case, the network devices section.
I hope this has been informative for you
and I'd like to thank you for viewing.