- [Instructor] Here in DNA Center,
we're back under the main Assurance section of the GUI.
And we now we'll look at connectivity monitoring.
We've seen this in the Overall Health indicator window
that we're in now, and we've also drilled down
into the individual network and clients' health sections.
Let's click the View Client Health button,
that's in the right hand side of this window.
And if we let this load, and then we click View Details
under either one of these you see we can view the details
for the Wireless Clients or the Wired Clients.
Let's go ahead and just click View Details
for the Wired Clients on the right.
And at the bottom, we are populated with a list of devices
that are associated with this network.
If we click on one of these, we'll just choose this
10.10.20.84 device.
If we click on that, notice that again in the background
we see the Client 360 window load.
So we need to click out of this overlay tab
back into our main window.
At the top we see a historical graph
for this particular client.
If we hover the mouse over this graph,
you can see we're able to move left and right
to view metrics about the client.
So for example, we can see the onboarding status is passed
so in other words, this client was able to join our network.
We can see the port assignment and VLAN ID, the throughput,
any latency issues, lots of great information.
And again, we can move left and right
to view that from a historical perspective.
If we scroll to the bottom,
you see that we have Detail Information
expanded already here
and that defaults to the Device Info tab.
If we click the Connectivity tab
we can see Transmit and Receive Rates
and the Interface Errors.
And again, that's a great place to get a general idea
about connectivity problems happening with the clients.
We can hover over these graphs as well, move left to right
and see information correlating to historical times
so that's very helpful.
Now, one of the really great tools within Cisco DNA Center
for connectivity monitoring,
in addition to these areas that we've looked at
is the Path Trace tool.
You see that near the center of our screen.
If we're checking for connectivity between our clients
and let's say maybe we want to check connectivity
to this specific server,
we can run a Path Trace tool
to diagnose any connectivity issues.
We will be able to see the exact path
that applications and services running on the clients
will take through our network.
So let's click this Run New Path Trace button,
and we're going to get a popup tab on the right
that allows us to do this.
And you can see all of the available options here,
the Source IP address is already populated
which is the source of the client that you're working from.
And additionally, you could indicate a port number
if you'd like to do that.
If we click in the Destination IP version four box,
if you don't happen to know the exact IP address
you might notice this box a list of all known devices
on the network.
So let's go ahead and enter the IP address, 10.10.20.82
which you can see is an access switch on the network.
If we run the path trace on this,
we'll go ahead and click Start,
you'll see on the left hand side
it tells us it's Loading the Trace
so that'll take just a few moments to do that.
And now you can see that it has loaded a graphical view
of our traffic path in this window.
And of course, this is a very simple topology
in the sandbox lab
because this client happens to be connected
directly to this access switch.
If we click on one of these devices,
let's click on the access switch
notice some of the information here
is listed as not available.
So let's see how we can include that,
let's go ahead and run another Path Trace
so we'll click Run New Path Trace and this time,
let's say the same IP address,
10.10.20.80,
let's do 83 this time.
If we scroll down to the bottom,
notice that we have the option to include certain stats.
So we can include Device, Interface, and QoS stats
where those are available.
If we click Start, again our trace is going to load,
once that completes loading,
since we chose a different client
you'll see a little different path
that's visible to us here.
But again, we can see the exact path
that that takes through our network.
Now, if we click on one of these devices
you'll see we have more information available here
we have things like CPU Usage, Total Memory Usage
and we also have the stats about when this was refreshed.
Now you'll notice if I just leave this here
it's eventually going to close out this window,
and that's because, and there it went
you saw that window just close.
If I open this window again to Run New Path Trace
you'll see that by default
this Refresh Every 30 seconds is turned On,
so that's actually what's happening.
When we're running that Path Trace every 30 seconds
if we leave that turned On,
it's going to refresh that path
so that we can use that for active troubleshooting.
Let's run another Path Trace
so you can see what a failure might look like.
Let's go ahead and try to do that
to our wireless LAN controller
which we should not be able to reach
from a wireless clients, 10.10.20.51.
You can see that's listed as
our 3504_Wireless LAN Controller.
We'll go ahead and include those stats
that we just looked at, we'll click Start.
And this is going to fail
once the Path Trace finishes loading
and there we see the failure message.
So we can see how far we get,
we get to our access switch and that's it,
as far as the path can be traced.
And the message actually tells us that
a Complete layer 2 path
between the Router we're connected to,
or the layer 3 switch we're connected to
named leaf2.abc.inc,
and the wireless LAN controller
that layer 2 path could not be established.
And we see a suggested remediation step
is suggests maybe to make sure that CVP is enabled.
So that's what a Path Trace failure will look like.
That's a look at using Cisco DNA Center Assurance
for connectivity monitoring on a network.