DNA Center 1.2.

10 - Assurance Lab

Enterprise SEVT – April 2019

Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883

Page 1 of 54
LAB PREPARATION ............................................................................................................................ 2
LAB TOPOLOGY ..................................................................................................................................... 3
CONNECTING TO DNA CENTER ................................................................................................................. 3
GETTING STARTED ................................................................................................................................. 8

LAB EXERCISE 1: DESIGN .................................................................................................................. 10

LAB EXERCISE 2: DEVICE DISCOVERY AND INVENTORY .................................................................... 13

EXERCISE DESCRIPTION AND OBJECTIVE .................................................................................................... 13
LAB EXERCISE STEPS.............................................................................................................................. 13

LAB EXERCISE 3: ASSIGN DEVICES TO SITES AND SET UP DEVICE TELEMETRY .................................. 19
LAB EXERCISE STEPS.............................................................................................................................. 19

LAB EXERCISE 4: ASSURANCE USE CASE #1: NETWORK VISIBILITY ................................................... 23

LAB EXERCISE STEPS.............................................................................................................................. 23

LAB EXERCISE 5: ASSURANCE USE CASE #2: TROUBLESHOOTING .................................................... 44

LAB EXERCISE STEPS.............................................................................................................................. 45

LAB EXERCISE 6: ASSURANCE USE CASE #3: PROACTIVE MONITORING - SENSOR ........................... 51
LAB EXERCISE STEPS.............................................................................................................................. 51

LAB Preparation
Each POD includes:

1. Multiple network devices (refer to the topology diagram)

2. DNA Center appliance

The Lab proctor will provide the specific topology for the POD together with POD IP Address Assignments and
credentials.

Page 2 of 54
 Lab Topology

Refer to the topology diagram below, for lab use.

Connecting to DNA Center

Step 1 Connect to your Jump PC via RDP (Remote Desktop Client). Use the IP address
assignment and credentials provided by the instructor. You will now be
connected to a Windows PC. From this Windows PC use your Chrome Browser to
access your DNA Center UI (User Interface) and enter the credentials.

DNA Center: https://10.1.3.230

Username: admin
Password: Cisco123

Once you enter the credentials you’ll access the DNA Center dashboard. In the
latest release the overall health summary of your network is what you see first.
Below that you will see the four main steps for configuring and managing your
network in an abstracted and simplified way:

Page 3 of 54
Step 2 Scroll down and you can then see the tools available in DNA Center. These tools
will support and integrate with the DNA Center workflow:

Page 4 of 54
Step 3 Verify the version of DNA Center that is running

The DNA Center version should be reported as 1.2.10

Page 5 of 54
To verify the version of installed packages, click “Show packages”

Page 6 of 54
Step 4 Verify if packages are ready to install or if new packages are available on the
cloud to be downloaded, click the setting icon, then “System Settings” and
“Software Updates”.

Page 7 of 54
Verify that all packages are in the Running or Not Deployed state without errors.

NOTE: If you see some available updates or packages that are not deployed (not the case in screenshot
above), please do not install them for this lab.

Getting Started

This hand on lab consists of the exercises below:

• Lab Exercise 1: Design

• Lab Exercise 2: Device Discovery, and Inventory

• Lab Exercise 3: Assign Devices to Sites and set up Device Telemetry

• Lab Exercise 4: Assurance Use Case #1: Network/Client visibility

o Network Health, Client Health, Application Experience

• Lab Exercise 5: Assurance Use Case #2: Troubleshooting

o Path trace and Global issue

Page 8 of 54
• Lab Exercise 6: Assurance Use Case #3: Proactive Monitoring – Sensor – How to setup

Page 9 of 54
Lab Exercise 1: Design
In this section we will be creating the Network Hierarchy of our network which includes
creating Sites, Buildings and Floors. After that we will be adding CLI and SNMP credentials so
that we can perform the device discovery in Lab Exercise 2.

Go back to the main DNA Center page by clicking on the Cisco logo or the DNA Center in the
top left corner.

Lab Exercise Steps

The Network Hierarchy and Device Credentials have been set up for you. In the next steps
we will review the settings.

Step 1 Scroll down on the main page to find the Network Configurations and
Operations section. Then click on Design.

On the “Network Hierarchy” page, review what sites, buildings and floors have been
created.

Page 10 of 54
The next step will be adding the device credentials. This step is key because DNA Center will
be using these credentials to discover our network. Select Network Settings and then Device
Credentials as shown. Make sure you are on the Global Area.

Verify that the following credentials have been configured.

Name/Description: Devices
Username: admin
Password: Cisco123
Enable Password: lab-cert
SNMPV2 read only community: cisco (use “RO” as Name/Description)
SNMPV2 write community: cisco123 (use “RW” as Name/Description)

Page 11 of 54
þ End of Exercise: You have successfully completed this exercise!
Proceed to the next section…

Page 12 of 54
Lab Exercise 2: Device Discovery and Inventory
Exercise Description and objective

In this exercise, we will review the discovery settings of our existing network and see how the
DNA Center network information base is populated.

DNA Center supports two methods for discovery: Cisco Discovery Protocol - CDP and IP Range.
CDP discovery mechanism has been used for this lab. Optionally, DNA Center allows to
manually enter device information or import the inventory from other applications using a
.csv file.

We will then examine the contents of the Inventory in DNA Center.

Lab Exercise Steps

Step 1 From the main Dashboard, scroll down to the “Tools” section. Select the “Discovery”
tab:

Step 2 Confirm that all of the devices have been successfully discovered.

Settings that were used in the discovery:

Discovery Name: Network-Wide
IP Address: 10.1.8.1
Preferred Management IP: Use Loopback
CLI credentials: admin
SNMP V2 READ credentials: RO
SNMP V2 WRITE credentials: RW
Protocols: SSH, Telnet

Page 13 of 54
 Verify that 7 devices were discovered successfully. Click on the discovery “Network-
Wide” on the left and then scroll to the bottom of the page to review the results of
the discovery. Confirm that the settings are all correct.

What happens when a device is discovered?

• Inventory Collection
• Configuration pushed to devices to allow DNA Center manageability
• Establish Streaming Telemetry over secure connection

We will verify these changes in the next steps.

Step 3 Now that all devices have been successfully discovered, we will look at the inventory
tool. From the DNA Center dashboard, scroll down to the “Tools” section and select
“Inventory”

Step 4 The inventory allows us to get comprehensive information on each device in our
network.

Page 14 of 54
 NOTE: Make sure that all devices in the inventory are in “Managed” state. If not, you need to fix the problem
before moving to the next step. You should see six network devices and one access points. Device IP address
in the snapshots might be different from the ones in your POD

Step 5 The snapshot above shows the inventory in a preset view called “Status”. This preset
view shows specific fields associated with the status of each device. We can manually
select other fields or other preset views. Select “Hardware Preset”:

DNA Center has information on each device individually and also about how each
device is connected to other devices in the network. Based on this information, DNA
Page 15 of 54
 Center assigns a role for each device. This role can be modified manually. In this lab,
you do not need to change any of the roles.

Step 6 There are several changes that DNA Center automatically makes to routers and
switches during discovery:
• Configure PKI for DNA Center
• Enable IP Device Tracking (IPDT) so that we can track Wired clients (Switches
only)
• HTTP Server source
• SNMP RO & RW communities (If not already configured)

Using “Putty” you can log into one of the branch switches and confirm that the
configuration has been pushed correctly:
SSH to BR-SW2 (10.10.64.7)
Username: admin
Password: Cisco123
Enable: lab-cert

Configuration that should have been pushed:

Page 16 of 54
Step 7 The WLC supports streaming telemetry over a REST based https API. Each time there
is an event on the Wireless infrastructure, such as a client associating, the WLC will
push this information to DNA Center.

There are several changes that DNA Center automatically makes to WLCs during
discovery:
• Install Certificate for Streaming Telemetry
• Configure streaming telemetry service (WSA)

Log on to the WLC to confirm that streaming telemetry has been configured and is
operational. Using “Putty” you can log on to the WLC (10.1.5.50 - admin/Cisco123)
and execute “show network assurance summary”

We need to ensure:
• The correct DNA Center IP is configured (10.1.3.230)
• The WSA service is enabled
• The “Last Success” is newer than “Last Error”; and
• The “JWT Last Success” is newer than “JWT Last Failure”

Page 17 of 54
 NOTE: Streaming telemetry is configured on the WLC once it is discovered by DNA Center. Therefore, you will
see this configuration on the WLC before you push any Telemetry Profiles.

þ End of Exercise: You have successfully completed this exercise!

Proceed to the next section…

Page 18 of 54
Lab Exercise 3: Assign Devices to Sites and set up Device Telemetry
The next step in setting up DNA Center for Assurance is to assign the devices that were
discovered to sites and set up device telemetry.

Lab Exercise Steps

Step 1 In the previous exercises, we designed our network from a high-level perspective and
discovered our devices. We will now be assigning the devices we discovered in
exercise 2 to the sites we created in exercise 1. Select the “Provision” section in DNA
Center dashboard:

Step 2 This step has been completed for you. Verify that all of the devices have been
assigned to a building or floor. Take note that the APs have been assigned to a floor,
it is not possible to assign them to a building.

If any devices have not been assigned to a site, please feel free to assign them to a
site by selecting the device, click “Actions”, and then click “Assign Device to Site”.

Page 19 of 54
Step 3 DNA Center supports the collection of multiple types of device telemetry including:
Syslog, SNMP poll, SNMP traps, Netflow and streaming telemetry via a REST based
API. Streaming telemetry is currently only available for the Wireless LAN Controller.

Please note: Streaming telemetry for the WLC was automatically configured during
the discovery phase. No Telemetry profiles need to be assigned to the WLC.

In DNAC 1.2.10 there are some differences in how telemetry gets pushed to the wired
devices. Under Design-àNetwork settings there is a new setting for SYSLOG and
SNMP Server. Configure Cisco DNA Center as syslog server and as SNMP server. Those
settings are enabled by default as you can see from the screenshot below. When a
device is discovered like a switch or router and then assigned to a site the setting for
the SYSLOG and SNMP servers gets pushed to the device. For syslog the level is set to
informational when it is pushed from the network settings. If you want to change the
syslog setting then you can use the telemetry app.

Step 4 DNA Center will log on to the selected devices and configure the telemetry options
defined in the profile. The configuration will look this this:

logging host <DNAC-IP>

!
snmp-server enable traps
snmp-server host <DNAC-IP> version 2c tesseract-traps

Using “Putty” you can log into one of the branch switches and confirm that the
configuration has been pushed correctly:

Page 20 of 54
 SSH to BR-SW2 (10.10.64.7)
Username: admin
Password: Cisco123
Enable: lab-cert

The DNA Center IP address that telemetry should be sent to is 10.1.3.230.

The system has also enabled a variety of SNMP traps.

Step 5 As stated above, telemetry profiles in DNA Center can only configure Netflow on
routers running IOS 16.x and newer. If the router supports ezPM, it is possible to
configure Netflow manually.

In this lab, we have already enabled Netflow for DNA Center on HQ-R1 which is a
ISR4331 so that we can get the application traffic in DNA Center. So you don’t have
to push it in this lab. You can verify the settings as below by doing a show run.

Using “Putty” you can log into the router:

SSH to HQ-R1 (10.1.254.2)
Username: admin

Page 21 of 54
 Password: Cisco123
Enable: lab-cert

performance monitor context tesseract profile application-performance

exporter destination 10.1.3.230 source Loopback0 transport udp port 6007
traffic-monitor application-client-server-stats
traffic-monitor application-response-time
!
interface Gi0/1
performance monitor context tesseract
!
interface Gi0/2
performance monitor context tesseract

Netflow data enabled Application Experience which you will see in the next exercise.

þ End of Exercise: You have successfully completed this exercise!

Proceed to the next section…

Page 22 of 54
Lab Exercise 4: Assurance Use Case #1: Network Visibility

NOTE: Please browse around different screens in this exercise to explore the different screens to see what
information is available for network, clients and applications. We may not have covered all the information
available below but would like you to explore the screens as much as possible to understand what is available.

DNA Assurance aims at providing a compact, easy to leverage, yet multi-level view into the
network. This view is divided into three main areas, Client Health, Network Health and
Application Health.

Client Health - When hundreds or thousands of clients are present in the network at any
time, providing a view to each client is often considered as noise. You need to know the
general state of the clients, which includes visibility into the number of clients that are in
good health and a way to determine which clients’ health has degraded and require
attention.

In client health, you can review client onboarding statistics, wireless experience and
application experience.

Network Health - You are likely not only concerned with the health of clients connecting to
their network, but also with the health of the network infrastructure itself. Every network
device has KPI details including CPU, memory, temperature, control plane and data plane
statistics, monitored. The result of these KPIs is a generated health score in DNA Assurance
to help you easily identify issues.

Application Health – Application Health provides information on what applications are

running in your network and how they are being treated over the network. The application
dashboard provides information on business-relevant and business-irrelevant applications
as well. Application Health provides both quantitative and qualitative stats. Quantitative
stats are BW, Usage, etc while qualitative stats are packet loss, jitter, latency, delay etc. DNA
Center gets this information vis NBAR2 (identify application by unique signatures) and
Netflow (quantitative and qualitative stats) from the routers.

The aim of this exercise is to orient you around the DNA Assurance interface
Lab Exercise Steps

Step 1 Select the “Assurance” section in DNA Center dashboard.

Page 23 of 54
Step 2 Review the Overall Health page. Wired and wireless clients are shown
separately.

The Overall Health page gives you a quick view into the health of the Clients and
Network devices.
(1) You can hide or unhide the Hierarchical Site View view as well as switch between
table and map view

(1) Network health score provides an indication of how many healthy network
infrastructure devices are on the network
(2) Client health score provides an indication of how many healthy client devices are
on the network. Hover over the “i” Icon to see how the health score is calculated.
(3) If there is a major issue that has occurred on the network, it will be listed under
Top 10 issues. Priorities are also added for the issues based on the impact the issue
has on the network.

Page 24 of 54
Step 3 Select “View Client Health” under client in the Overall Health Summary

Page 25 of 54
Step 4 It is possible to filter the view based on time which allows you to zoom in to periods of
reduced health scores so that you can understand what caused the score to dip. Move the
slider to see the data at the bottom change to reflect the time.

Step 5You may view the health scores on previous days by clicking the arrow button as shown
below.

Page 26 of 54
Step 6 Review the Client Health page.

The Client Health Summary is divided into Wireless and Wired clients

Page 27 of 54
 (1) Client roaming Times shows how long it takes for roaming clients to rejoin another
AP. Here since we have only 1 client you don’t see any data. You can check our TME
demo servers to see the roaming data later.
(2) Client Onboarding Times monitor how long it takes for a wireless client to go
through the Association, AAA, and DHCP process, and for a dot1x enabled wired
client to go through AAA and DHCP. If there was a threshold breach or onboarding
failure, this allows you to identify which one of these onboarding steps caused it.
(3) Connectivity RSSI displays the RSSI data for wireless clients on the network and
highlights clients with poor RF
(4) Connectivity SNR provides an insight into whether wireless clients have any SNR
issues.
(5) You can also see the client count per band and connectivity link for the wired
clients and client counts per SSID.

Feel free to click on “View Details” to explore any of these further.

Step 7 Click on View Details on the RSSI or SNR dashlet. This will open the details screen. Then
click on the bar in the graph. This will now display the mid level analytics which you can
use to filter the data more. For example you can filter on Top locations where the clients
are having bad RSSI or Top AP’s on which the clients are having bad RSSI. You may select
the different filters to view the results.

Click on the bar to see

the midlevel analytics.

Page 28 of 54
Step 8Change the Client Devices table filter so that you can see all the wired devices on the
network. Click on Type: Wired Health: All and then Apply.

Here you can see the devices on the lab network with their corresponding health
score. UserID is only available on wired ports and SSIDs with 802.1x authentication
enabled and Device Type is available for wireless clients profiled by the WLC, or
Wired clients if ISE integration is configured.

Page 29 of 54
In this release you can add extra columns to the client table like usage, Tx, Rx etc.

Select the Usage, Tx and Rx columns and click Apply. You should see some client usage
details for one of the clients which is running some traffic.

Step 9Hover over the health score to get details of the KPI’s used to calculate the score for
the clients. Try it on both the wired and wireless clients to see the difference.

Page 30 of 54
 Select the wireless client that is not the sensor in your pod to go to Client 360. You may
Step 10
have to select the Wireless filter and click Apply to see the wireless clients.

Step 11 Client 360 shows client details like OS, IP address, Mac address and location

Step 12Hover over the timeline as shown to see the client KPI’s at that time. If there is a dip
in the health score this can help identify which KPI caused the score to dip. Major events
for the client are also shown in the timeline. These could be events like roaming and
onboarding.

Page 31 of 54
Step 13Scroll down on the Client 360 to see if there are any issues and the onboarding
topology.

Step 14 Client onboarding events viewer. We get onboarding events from the WLC which you
can see in the client 360 page. Select an event to see the details.

Step 15 Client device, connectivity and RF information. You can browse through the
tabs and look at the information provided under each tab.

Page 32 of 54
Step 16 Go back to client health page as shown.

Step 17Scroll down on the Client health page to the clients table and select the wired clients
as shown. The click on the wired client 10.10.64.11.

Page 33 of 54
Step 18 Now let us explore the wired client 360 view. Hover over the timeline to see all the
new KPI’s provided for the wired client like Tx, Rx and Port information where the client
is connected.

Step 19Scroll down on the client 360 screen to see the applications the client is running. Select
the other tabs like Business Irrelevant and Default to see what other applications the client
is using. For the TCP applications you can see the performance metrics like packet loss and
latency. You can see the throughput for all the applications.

Scroll down to see the Detail information for the device and select the Connectivity
Step 20
tab. Here you can see the Tx/Rx and errors for the port the client is connected to. Hover
over any part of the graph to see the data.

Page 34 of 54
Step 21 Navigate to the Network Health screen by clicking on Health Menu and then Network.

Step 22 Review the Network Health page.

Information on the Network Health page is divided into the device role – Core,
Access, Distribution, Router and Wireless. The Latest and Trend charts allow you to
get an idea what the health is now, and what is was for the past day.

Page 35 of 54
Scroll down further on network health page to see the Total AP’s up/down, Top N AP’s by
client count and Top N AP’s with high interference. You can select the 2.4 GHz or 5 GHz in
the drop down for the AP’s with high interference dashlet.

Change the Network Devices table filter so that you can see all the devices on the
Step 23
network. Click on Overall Health: All, and then Apply as shown.

Now you can see all the network devices on the lab network with their corresponding
health score. If there is a device with a health score lower than 10, please feel free to

Page 36 of 54
 explore and see if you can find out why. You can hover over the health score to get
more data.

Click on the devices and explore the 360 views for the network devices. The data in
Step 24
the 360 view is specific to the device type. Please check out the WLC, AP and a switch to
see what gets shown for each.

Check if any issues are there for the device. Click on an issue to see what suggested actions
are provided to resolve the issue.

Page 37 of 54
Click on a link in the topology to see the detailed connectivity information.

Scroll down further to see the new Event viewer for wired devices where you can
Step 25
view the Syslog and traps for that device. Select an event to see the details for that
event.

If it is router and if Netflow is enabled on the router then you can see the
Step 26
applications going through that router.

Page 38 of 54
Select an application to see the application performance.

Scroll down further to see the Detailed device information. Select the new Interface
Step 27
tab to see the interface information on that device.

Step 28Select a few interfaces and then scroll down to see the detailed interface information
for those devices.

Page 39 of 54
 Application Health – Go to HealthàApplication as shown to get to the Application
Step 29
health dashboard. Here you can see the health of the business relevant applications
running in your network.

Page 40 of 54
Step 30You can see the health of your business relevant applications and application usage in
this dashboard. Play around with the timeline in case you don’t see any data as we
sometimes run into issues with the scripts that are generating the applications.

Scroll further to see the list of applications and their details. Select All under Type and
Step 31
Health as shown and hit Apply.

Page 41 of 54
Step 32Now you can see all the applications and their health listed.
Note: You might not see all these same applications because of the way the pods are setup.

Click on the ssh application above to see the Application 360 page. At the top you will
Step 33
see the timeline for the health of this application.

Scroll down to see the locations which are running this application. Select the router
Step 34
shown under the location from which DNA Center is getting the Netflow. This will display
the application performance in that site and also the clients using that application.

Page 42 of 54
þ End of Exercise: You have successfully completed this exrcise!
Proceed to the next section…

Page 43 of 54
Lab Exercise 5: Assurance Use Case #2: Troubleshooting

NOTE: Please browse around different screens in this exercise to explore the different screens in this section
to see what information is available. We may not have covered all the information available below but would
like you to explore the screens as much as possible to understand what is available.

One of the primary goals of Assurance is to help you quickly identify the root cause of issues.
This is achieved by providing an end to end visibility of the network, highlight potential issues,
and when an issue is identified, provide a list of suggested actions to help resolve the issue.
In this exercise we will go over some of the tools available to troubleshoot network and client
issues.

Step 1 Go to Issues à All Issues as shown

Step 2 This will give you a list of all the issues that can be generated by DNA Center for various
categories like Onboarding, Connectivity, Device, Application etc. Go ahead and browse
through the categories and the issues. Select any issue to get more details. This page will
also show how many times an issue has occurred as well.

Page 44 of 54
Step 3 Go to ManageàIssue Settings

Step 4In this screen you can click on an issue and disable it or change its priority. Go ahead
and click on an issue to see how this looks like.

There will be two scenarios which you will go through today:

• Global Issue
• Client not able to reach a website
Lab Exercise Steps

Step 1 The first issue we are going to troubleshoot is a Global issue which is listed in the Top
10 Issues on the Overall Health page. Click on Interface issue to open the Issue Detail.

Page 45 of 54
Step 2 In Issue Detail, suggested actions are provided to help you troubleshoot the issue. On
certain issues, such as this one, guided remediation is possible directly in the DNA Center
interface, without having to log on to any network devices. In DNAC 1.2.10 similar issues
are grouped together. As you can see below there are 2 similar issues which are grouped
together. Click on the first one.

Step 3 You will see the suggested actions and the Run commands to check the configurations
as part of the check list. Click on run to test out the feature. And go through the suggested
actions to understand what it looks like.

Page 46 of 54
 If a user for example “John Snow” is having an issue reaching the HR team’s secure
Step 4
website at https://10.10.64.11 then we can do the following.

The first step is to go into the Client 360 for John’s laptop. Find the wired client
10.1.20.11.

This is the Client 360 page which is available for all clients on the network. In this
example, John’s laptop currently has a score of 10/10 and no issues are logged.

Page 47 of 54
Step 5Since no issues are logged, we are going to test the end to end network reachability
between John’s laptop and the secure HR team website using Path Trace. Click on “Run
New Path Trace”

Step 6 To set up the path trace, enter the values from the snapshot below. When finished,
click “Start”.

Source IP: (configured for you)

Destination IP: 10.10.64.11
Destination Port: 443
Protocol: TCP
Refresh: off
ACL Trace: on
Include Stats: Device and Interface

Page 48 of 54
The result of the path trace will show you the end to end path between the source
and destination and will highlight potential problems such as interface errors/drops
and ACLs. If there was a deny ACL you would be able to see that in red and see the
details to see if that was causing an issue.

Page 49 of 54
Step 7To find out more information about the ACL that the trace is permitted by, click on the
ACL icon, and then you can see the ACL details.

þ End of Exercise: You have successfully completed this exercise!

Page 50 of 54
Lab Exercise 6: Assurance Use Case #3: Proactive Monitoring - Sensor
On a typical network, clients are not always using all the services that the network provides,
and are not always in all locations. Sensors can represent clients in times or locations where
clients are not present, or test services that clients are not currently using. This allows you to
proactively test the network to ensure that there are no issues or catch issues early.

When a sensor connects to the network to perform the tests configured, it first needs to go
through the onboarding process which is comprised of Association, AAA, and DHCP. This step
proactively tests the availability of the network’s wireless infrastructure at that location, AAA
services, and DHCP services. Once the sensor is on boarded, it can test the reachability to
other services on the network.

The aim of this exercise is run through the steps required to configure a sensor test.

Lab Exercise Steps

Step 1 In any Assurance page, click on “Manage” and then “Sensor-Driven Tests”. If you see
a test that is already there you can edit and see how it looks like. Then just delete the
test and re-create it as part of the exercise.

Step 2 Click on “Add Test”.

Step 3 We need to define some of the settings and select the SSID that we will run tests on.
Enter the values from the snapshot below. When finished, click “Next”.

Page 51 of 54
 Test Name: sensor
Location: Select the floor in Branch
Interval-Hours: 30 minutes
Radios to Test: select both the radios
Credentials: Cisco123

Step 4 On this page, we can see the types of tests that we can run.

Select only the following tests for now:

Host Reachability Tests - 10.1.3.254
Speed Test - Just click the check box
IPSLA Test - Bronze for Service Level

Then click Next.

Step 5 In the following page select the Sensor as shown. Then click Save. This will save the
tests on the Sensor. It takes a few minutes to run it and get the results the first time.
So wait 5 minutes and then you can go back to this page to see the results.

Page 52 of 54
Step 6 Go to DashboardsàSensor to see the Sensor Dashboard where you can view the
results in detail.

Page 53 of 54
! You have completed the lab

Page 54 of 54