Cloud Management and Monitoring for

Catalyst

Sameh Sackla
Global TSA
[email protected]
 Table of Contents
Learning Objectives .............................................................................................................4
Disclaimer...............................................................................................................................5
Introduction ...........................................................................................................................6
Scenario #1 – Cloud Monitoring Onboarding App .....................................................8
Task 1: Learn how to download the Onboarding App ................................................................................. 8
Step 1: Access the Lab resources............................................................................................................................ 8
Step 2: Watch the Demonstration Video ............................................................................................................ 9
Step 3 [Optional/Bonus]: Download the onboarding app ....................................................................... 10
Scenario #2 – Onboarding Catalyst devices for Cloud Monitoring .................... 16
Task 1: Onboard a Catalyst 9300 for Cloud Monitoring........................................................................... 16
Step 1: Access the Onboarding app Simulation ............................................................................................ 16
Step 2: Start with onboarding a Catalyst Switch.......................................................................................... 17
Step 3: Provide the Meraki Dashboard API Key ........................................................................................... 17
Step 4: Select the correct Organisation ............................................................................................................ 18
Step 5: Provide the device IP information ...................................................................................................... 19
Step 6: Provide the SSH credentials to access the Catalyst Switch ..................................................... 20
Step 7: Prechecking the Catalyst device........................................................................................................... 21
Step 8: Select the Dashboard network.............................................................................................................. 22
Step 9: Confirm Configuration Changes ........................................................................................................... 23
Step 10: Final Step ...................................................................................................................................................... 24
Scenario #3 – Cloud Monitoring for Catalyst ............................................................ 25
Task 1: Find the Switch in Dashboard .............................................................................................................. 25
Step 1: Login to Meraki Dashboard .................................................................................................................... 25
Step 2: Select the Dashboard Network ............................................................................................................. 27
Step 3: Navigate to the Switches Menu ............................................................................................................ 27
Task 2: Use Cloud Monitoring for Catalyst ..................................................................................................... 28
Step 1: Observe the Switch Status in Dashboard ......................................................................................... 28
Step 2: Observe the Switch Ports in Dashboard........................................................................................... 29
Step 3: Observe the Switch IP Address in Dashboard ............................................................................... 32
Step 4: Observe the Switch Firmware Version in Dashboard ............................................................... 33
Step 5: Observe the Troubleshooting Tools in Dashboard ..................................................................... 34
Step 6: Observe the Network Topology in Dashboard.............................................................................. 34
Step 7 [Optional/Bonus]: Observe other Switches in Dashboard ........................................................ 36
Scenario #4 – Catalyst Migration ................................................................................. 38
Network Diagram.............................................................................................................. 38
Task 1: Migrate the Catalyst 9300 switch ....................................................................................................... 39
Step 1: Access the Catalyst Migration Tool..................................................................................................... 39
Step 2: Select the Catalyst 9300 switch to Migrate..................................................................................... 41
Step 3: Check the Catalyst 9300 switch Compatiblity ............................................................................... 42
Check Switch Compatibility ..................................................................................................................................... 42
Step 4: Check the Catalyst 9300 Firmware version ................................................................................... 43
Check Switch Firmware............................................................................................................................................. 43
Step 5: Check the Catalyst 9300 Hardware version ................................................................................... 45
Check Switch Hardware ............................................................................................................................................ 45
Step 6: Create a SVI with a routable IP address ........................................................................................... 45
Create a SVI .................................................................................................................................................................... 46
Step 7: Add a DNS Server ........................................................................................................................................ 46
Add DNS Server ............................................................................................................................................................. 46
Step 8: Change the HTTP Client Source Interface ....................................................................................... 47
HTTP Client Source Interface ................................................................................................................................. 47

Cloud Management and Monitoring for Catalyst 2

Feb 2023
 Step 9: Test your Configuration ........................................................................................................................... 47
Test Your Configuration............................................................................................................................................ 47
Step 10: Register the switch with the Meraki Dashboard ....................................................................... 47
Register the Catalyst Switch.................................................................................................................................... 48
Step 11: Migrate the Catalyst 9300 switch ..................................................................................................... 48
Migrate the Switch ...................................................................................................................................................... 48
Scenario #5 – Cloud Management for Catalyst ........................................................ 63
Task 1: Manage a Migrated Catalyst Device in Dashboard ..................................................................... 63
Step 1: Login to Meraki Dashboard .................................................................................................................... 63
Step 2: Search for the Migrated Switch ............................................................................................................ 65
Step 3: Check the switch status in Dashboard .............................................................................................. 66
Step 4 [Optional/Bonus]: Gather Additional details about the Migrated Switch.......................... 69
Related Sessions at Ciscolive ................................................................................................................................. 70
Summary ......................................................................................................................................................................... 71

Cloud Management and Monitoring for Catalyst 3

Feb 2023
 Learning Objectives
Upon completion of this lab, you will be able to:
• Download the Cloud Monitoring onboarding tool from the Meraki Dashboard
• Onboard a Catalyst Switch to Cloud Monitoring
• Monitor a Catalyst Switch in the Meraki Dashboard
• Migrate a Catalyst Switch to Cloud Management
• Manage a Catalyst Switch in the Meraki Dashboard

Cloud Management and Monitoring for Catalyst 4

Feb 2023
 Disclaimer
• This training document is to familiarize with Cloud Management and Monitoring for
Cisco Catalyst. Although the lab design and configuration examples could be used as a
reference, it’s not a real design, thus not all recommended features are used, or
enabled optimally. For the design related questions please contact your representative
at Cisco, or a Cisco partner.

• Please note that for the purposes of this lab, you will be using a simulation software to
mimic the actual onboarding and migration process. The software allows for specific
inputs/commands to be used in the exact format presented in this document. Any
other IOS command will return the following error:

Switch#show run
% Bad IP address or host name% Unknown command or computer
name, or unable to find computer address
Switch#

• Meraki Dashboard UI can change at any time due to continuous development and
feature add-ons

Cloud Management and Monitoring for Catalyst 5

Feb 2023
 Introduction
Cloud Management and Monitoring for Catalyst is a new journey to accelerate customer
transition to the cloud. Leveraging the Meraki dashboard, Cisco is offering customers with
management capabilities across their Catalyst infrastructure.

With Cloud Management, Catalyst devices are migrated from the default DNA management
mode to the Meraki management mode and are fully managed in the Meraki Dashboard.
This offers customers with Hybrid Campus a single pane across both Meraki and Catalyst
devices which simplifies their network management and eliminates any inter-operability
issues between the migrated Catalyst and the Meraki platforms. (e.g. STP)
Migrating a Catalyst device to the Meraki Dashboard basically converts it to a Meraki device
from a management as well as a feature-set perspective. Thus, unifiying the network’s
control plane in a Hybrid Campus. With Catalyst Migration, customers can manage their
device configuration in the Meraki Dashboard just like a Meraki MS390 switch as depicted in
Figure 1

Figure 1

On the other hand; With Cloud Monitoring Catalyst devices are onboarded for Meraki
Dashboard monitoring. Customers can monitor their Catalyst devices and have insights on
their devices, applications and clients in the Meraki Dashboard and also access a number of
troubleshooting tools. This offers a number of features accorss the Catalyst hardware such
as uplink, device and port status, port configuration details, traffic analytics and a unified
Topology diagram.
Onboarding a Catalyst device for Cloud Monitoring retains the device’s feature-set and
Dashboard will only provide a Monitor-only service as depicated in Figure 2

Cloud Management and Monitoring for Catalyst 6

Feb 2023
 Figure 2

Cloud Management and Monitoring for Catalyst 7

Feb 2023
 Scenario #1 – Cloud Monitoring Onboarding App
In this lab activity, you will learn how to use the Cloud Monitoring onboarding app to enable
Dashboard monitoring for Catalyst devices. The onboarding app can be downloaded from the
Meraki dashboard and through local network access will check-in with your Catalyst device to
verify settings and configuration then it will configure the device for Cloud Monitoring and
finally provision your Dashboard account to add this Catalyst device for you as a Monitor-Only
device.

Task 1: Learn how to download the Onboarding App

In this task, you will learn how to download the onboarding app to your workstation and get
familiar with it’s different components by watching a short demonstration video.

Step 1: Access the Lab resources

Click on View to access the Lab resources as depicted in Figure 3

Figure 3

Then sign in using the following information:

Username = demo
Password = demo1234!

Cloud Management and Monitoring for Catalyst 8

Feb 2023
 Step 2: Watch the Demonstration Video

In this step, you will watch a demonstration video to show the steps required to download
the Cloud Monitoring onboarding app. Start by clicking on Download the onboarding tool as
depicated in Figure 4

Figure 4

This will open a new tab in your browser with an embedded video running in loops showing
the steps needed to download the Cloud Monitoring onboarding app as depicted in Figure
5

Cloud Management and Monitoring for Catalyst 9

Feb 2023
 Figure 5

Step 3 [Optional/Bonus]: Download the onboarding app

In this optional step, you can practice downloading the actual onboarding app from the
Meraki dashboard by following these steps:

First, As Dashboard uses Two Factor Authentication, please download the Google
Authenticator app from your app store and follow these steps to set it up:
o Download the Google Authenticator app on your smart phone
o Add the following QR code:

Cloud Management and Monitoring for Catalyst 10

Feb 2023
 Then, in a new browser tab go to https://dashboard.meraki.com and login using the
following details in Table 1 as depicted in Figure 6

Table 1

Username [email protected]
Password geztih-buTcod-mupfa8!

Figure 6

You will be prompted for the security code, please use the OTP from the Google
Authenticator app from the account that you have just added in the previous step.

Note Please note that you might be presented with a landing page that looks like this:

In this case, please click on “Use current settings” and you should be able to login

Then, click on Cloud Management & Monitoring for Catalyst to access this organisation in
Dashboard as depicted in Figure 7

Cloud Management and Monitoring for Catalyst 11

Feb 2023
 Figure 7

Then, click on the CLEUR 2023 network on the bottom of the page as depicated in Figure
8

Figure 8

Then, from the left hand-side menu navigate to Switch > Switches as depicated in Figure
9

Figure 9

Then, click on Add switches from the top right corner of the page as depicated in Figure
10

Cloud Management and Monitoring for Catalyst 12

Feb 2023
 Figure 10

Then, click on click here to add Cisco Catalyst switches as depicated in Figure 11

Figure 11

In the pop up window, download the app for your platform as depicated in Figure 12

Cloud Management and Monitoring for Catalyst 13

Feb 2023
 Figure 12

After you download the app, open the .exe file (or the equivalent for your platform) and click
on Agree and Continue to accept the terms and conditions as depicated in Figure 13

Cloud Management and Monitoring for Catalyst 14

Feb 2023
 Figure 13

By now, you have downloaded the onboarding app and it’s ready to be used. The initial step
for using the app is to provide a valid Dashboard API key as depicted in Figure 14
however this is out of scope for this WIL.

Figure 14

Cloud Management and Monitoring for Catalyst 15

Feb 2023
 Scenario #2 – Onboarding Catalyst devices for Cloud
Monitoring
In this lab activity, you will learn how to onboard a C9300 switch to be monitored in the Meraki
dashboard. By onboarding it, you will create a TLS tunnel to the Meraki Dashboard carrying
Telemetry data which facilitates the monitoring functions by enabling Netflow and several
other features.

Note Please note that this section uses a simulation software to take you through
the exact steps for onboarding a Catalyst device.

Task 1: Onboard a Catalyst 9300 for Cloud Monitoring

Step 1: Access the Onboarding app Simulation

In this step, you will access the Onboarding app simulation by clicking on Catalyst
Onboarding Simulation Lab as depicated in Figure 15

Tip If you have been asked to sign in again, please use the same information
from the previous exercise as shown below:

Username = demo
Password = demo1234!

Cloud Management and Monitoring for Catalyst 16

Feb 2023
 Figure 15

Step 2: Start with onboarding a Catalyst Switch

In this step, click on Onboard Catalyst Switch to start the process as depicted in Figure 16

Figure 16

Step 3: Provide the Meraki Dashboard API Key

In this step, you need to provide the API key. For that, Click on the top button Copy API key
then paste that into the Meraki Dashboard API key field as depicated in Figure 17 and
Figure 18 and then click on Start.

Note Please note you have to use the Dashboard API Key provided. Using any other
API key will not work.

Cloud Management and Monitoring for Catalyst 17

Feb 2023
 Figure 17

Figure 18

Step 4: Select the correct Organisation

In this step, the onboarding tool fetches a list of organizations of which this API key has
access to. You need to select the organization Cisco Meraki Platform and then click Next as
depicted in Figure 19

Cloud Management and Monitoring for Catalyst 18

Feb 2023
 Figure 19

Step 5: Provide the device IP information

this step, you need to provide the IP address of the Catalyst 9300 switch so that the
onboarding tool and connect using SSH and configure it. For that purpose, click on Copy IP4
address button on the top of the page then paste the IPv4 address into the first line then
click on Next as depicted in Figure 20 and Figure 21

Note Please note you have to use the IPv4 address provided. Using any other IP
address will not work.

Figure 20

Cloud Management and Monitoring for Catalyst 19

Feb 2023
 Figure 21

Step 6: Provide the SSH credentials to access the Catalyst Switch

In this step, you need to provide the SSH credentials to access the Catalyst 9300 switch. For
that purpose, click on Copy username button on the top of the screen and paste it in the
User name field, then click on Copy password button on the top of the screen and paste it in
the password field then click Next as depicted in Figure 22 and Figure 23

Note Please note you have to use the provided username and password in this
section. Any other credentials will not work.

Cloud Management and Monitoring for Catalyst 20

Feb 2023
 Figure 22

Figure 23

Step 7: Prechecking the Catalyst device

In this step, the onboarding tool will run some pre-checks to confirm that the Catalyst 9300
switch is suitable for onboarding. For that purpose, click on Start pre-check as depicted in
and wait for it return the results as depicted in Figure 24. The tool it will provide the
status for the Catalyst 9300 switch. Check the status (should be Ready for onboarding as
depicated in Figure 25) and then click Next

Cloud Management and Monitoring for Catalyst 21

Feb 2023
 Figure 24

Figure 25

Step 8: Select the Dashboard network

In this step, you need to specify the Dashboard network where you would like to add the
onboard the Catalyst 9300 switch. For that purpose, please select San Francisco from the
drop-down menu then click on Next as depicted in Figure 26

Cloud Management and Monitoring for Catalyst 22

Feb 2023
 Figure 26

Step 9: Confirm Configuration Changes

In this step, you need to confirm the configuration changes hat will be applied to the
Catalyst 9300 switch. For that purpose, click on the check-box and then click Next and Save
as depicted in Figure 27 and Figure 28

Figure 27

Cloud Management and Monitoring for Catalyst 23

Feb 2023
 Figure 28

Step 10: Final Step

In this step, the onboarding tool will carry on with onboarding the Catalyst 9300 switch and
it will provide a progress indicator. This involves connecting to the switch via SSH and
configuring it with the necessary changes to enable Cloud Monitoring. Once completed, it
will show Device onboarded successfully at this stage, please click on Next as depicted in
Figure 29

Figure 29

With 5 minutes, that Catalyst 9300 switch should be available in the Meraki Dashboard for
Monitor only services.

Cloud Management and Monitoring for Catalyst 24

Feb 2023
 Scenario #3 – Cloud Monitoring for Catalyst
In the previous exercise, you have successfully onboarded a C9300 switch by creating the
necessary configuration for it to be monitored in Dashboard. Now, the onboarded C9300 is
available in the Meraki Dashboard and can be monitored. In this lab activity, you will learn
how to use the Monitor-Only feature in Dashboard for Catalyst devices by accessing the
previously onboarded switch in the Meraki dashboard.

Task 1: Find the Switch in Dashboard

In this task, you will learn how to download the onboarding app to your workstation and get
familiar with it’s different components.

Step 1: Login to Meraki Dashboard

First, As Dashboard uses Two Factor Authentication, please download the Google
Authenticator app from your app store and follow these steps to set it up:

o Download the Google Authenticator app on your smart phone

o Add the following QR code:

Then, From your browser go to https://dashboard.meraki.com and login using the following
details in Table 2 as depicted in Figure 30

Note If you are still logged in dashboard, please signout and login again to be able
to access the correct organisation

Cloud Management and Monitoring for Catalyst 25

Feb 2023
 (It might be useful to use a private/ingognito browser for this purpose)

Table 2

Username [email protected]
Password geztih-buTcod-mupfa8!

Figure 30

You will be prompted for the security code, please use the OTP from the Google
Authenticator app from the account that you have just added in the previous step.

Note Please note that you might be presented with a landing page that looks like
this:

In this case, please click on “Use current settings” and you should be able
to login

Then, click on Cisco Meraki Platform to access this organisation in Dashboard as depicted in
Figure 31

Cloud Management and Monitoring for Catalyst 26

Feb 2023
 Figure 31

Step 2: Select the Dashboard Network

From the left Network drop-down menu, select the San Francisco network as depicted in
Figure 32 since this is the network that you have onboarded the Catalyst 9300 switch to
in the previous Lab exercise.

Figure 32

Step 3: Navigate to the Switches Menu

From the left hand-side menu, navigate to Switch > Switches and then search for the
onboard Catalyst 9300 switch as depicted in Figure 33 and then click on the switch to
access it as dipected in Figure 34

Cloud Management and Monitoring for Catalyst 27

Feb 2023
 Figure 33

Figure 34

Task 2: Use Cloud Monitoring for Catalyst

Step 1: Observe the Switch Status in Dashboard

In this section, you will learn how to use the Cloud Mointoring service for the onboarded
Catalyst 9300 switch in Dashboard. On the main switch page, check the status and if there
are any alarms as depicated in Figure 35

Cloud Management and Monitoring for Catalyst 28

Feb 2023
 Figure 35

Tip The following colour codes indicate the status of a device in the Meraki
dashboard:
Offline Alerting Online Dormant

Tip The Meraki dashboard has an option to enable Color Blind Assist mode. To
enable this feature, navigate to My profile by clicking on the top right corner
on the user icon and then enable the feature:

Step 2: Observe the Switch Ports in Dashboard

In this section, you will learn how to use the Cloud Mointoring service for the onboarded
Catalyst 9300 switch in Dashboard. On the main switch page, check the port status and how
many ports are connected as depicated in Figure 36

Cloud Management and Monitoring for Catalyst 29

Feb 2023
 Figure 36

Tip The following color codes indicate the status of a port in the Meraki dashboard:

Cloud Management and Monitoring for Catalyst 30

Feb 2023
Cloud Management and Monitoring for Catalyst 31
Feb 2023
 For more information, please check this KB article.

Step 3: Observe the Switch IP Address in Dashboard

In this section, you will learn how to use the Cloud Mointoring service for the onboarded
Catalyst 9300 switch in Dashboard. On the main switch page, check the Switch’s IP Address
and assignment method as depicated in Figure 37

Figure 37

Cloud Management and Monitoring for Catalyst 32

Feb 2023
 Tip The IP address is the same one that you have used to onboard the switch in
the previous exercise as depicted below:

Step 4: Observe the Switch Firmware Version in Dashboard

In this section, you will learn how to use the Cloud Mointoring service for the onboarded
Catalyst 9300 switch in Dashboard. On the main switch page, check the Switch’s Firmware
version as depicated in Figure 38

Figure 38

Cloud Management and Monitoring for Catalyst 33

Feb 2023
 Step 5: Observe the Troubleshooting Tools in Dashboard

In this section, you will learn how to use the Cloud Mointoring service for the onboarded
Catalyst 9300 switch in Dashboard. On the main switch page, check the Switch’s Firmware
version as depicated in Figure 39 and try and ping cisco.com and observe the MAC
Forwardint Table

Figure 39

Step 6: Observe the Network Topology in Dashboard

In this section, you will learn how to use the Cloud Mointoring service for the onboarded
Catalyst 9300 switch in Dashboard. On the main switch page, check the Network Topology
by clicking on Show at the bottom of the page as depicated in Figure 40 and Figure 41

Cloud Management and Monitoring for Catalyst 34

Feb 2023
 Figure 40

Figure 41

Tip Try hovering on the switch and the interconnections in the topology and see
what information is displayed:

Cloud Management and Monitoring for Catalyst 35

Feb 2023
 Step 7 [Optional/Bonus]: Observe other Switches in Dashboard

In this optional section, you can check other monitored switches in Dashboard. Navigate to
Switch > Switches and check what other switches are onboarded for Cloud Monitoring as
depicted in Figure 42 and Figure 43. Feel free to click on other switches and browse
around the main switch page.

Figure 42

Figure 43

Cloud Management and Monitoring for Catalyst 36

Feb 2023
 Tip Cloud Monitoring switches will be displayed with the following badge:

Cloud Management and Monitoring for Catalyst 37

Feb 2023
 Scenario #4 – Catalyst Migration
In the this exercise, you will learn how to migrate a C9300 switch to be fully managed in the
Meraki dashboard. By migrating it, you will change the default DNA mode to the Meraki mode.
As such, the switch will no longer run IOS XE commands or feature-set but it will be aligned to
a Meraki MS390 switch feature-set and dashboard experience.

Note Please note that Catalyst migration will wipe it’s entire configuration and
files. After migrating a switch, it will have to be configured from scratch in
Dashboard

Note Please note that Catalyst migration will change the default DNA mode to
Meraki mode. The Catalyst device running Meraki mode will not run IOS XE
feature set

Note Please note that Catalyst Migration is not yet available for customers. You
are accessing an Early Field Trial which is not available publically

Network Diagram

Figure 44

As depicated in Figure 44, the lab consists of the following devices:

Cloud Management and Monitoring for Catalyst 38

Feb 2023
 • A C9300 single Access switch running the DNA mode which you will migrate to Cloud
Management in this exercise
• A C9300 Access Stack of two switches that has already been migrated
• A C9500 Core Stack of two switches which has already been onboarded for Cloud
Monitoring
• A warm-spare MX100 (WAN Edge)

Task 1: Migrate the Catalyst 9300 switch

In this task, you will get familiar with the Catalyst Migration tool that is available for today’s
lab.

Note Please note that for the purposes of today’s lab, you will be using a simulation
software to mimic the actual migration process of a Catalyst 9300 switch

Step 1: Access the Catalyst Migration Tool

In this step, you will access the migration tool simulation by clicking on Catalyst Migration
Simulation Lab as depicated in Error! Reference source not found.

Tip If you have been asked to sign in again, please use the same information
from the previous exercise as shown below:

Username = demo
Password = demo1234!

Cloud Management and Monitoring for Catalyst 39

Feb 2023
 Figure 45

This should activate the Catalyst migration tool so please get familiar with the different
components as depicted in Figure 46

Cloud Management and Monitoring for Catalyst 40

Feb 2023
 Command
reference

Catalyst
9300
device
list
Terminal
Window
Network
topology
Migrate
this switch Figure 46

Step 2: Select the Catalyst 9300 switch to Migrate

From the top left drop-down menu, select the FCW2134L00J switch as depicted in Figure
47 to be migrated to Cloud Management

Figure 47

Note Please note that you need to click once on the serial number and do not click
on any other devices. Switching between devices/SN will reset your session
and you will have to start all over again.

Once you have selected the SN, the terminal should be activated and ready as depicated in
Figure 48

Cloud Management and Monitoring for Catalyst 41

Feb 2023
 Terminal
Ready

Figure 48

Step 3: Check the Catalyst 9300 switch Compatiblity

In this step, you will check the siwtch’s compatibility for Cloud Management:

Check Switch Compatibility

IOS Commands enable
show meraki compatibility
IOS Output
Switch>enable
Switch#
Switch#
Switch#show meraki compatibility
==================================================
Compatibility Check Status
--------------------------------------------------
Boot Mode INSTALL - Compatible
--------------------------------------------------
------------------------------------------------------------
-------------------------------
Switch# SKU Bootloader Version
Network Modules
------------------------------------------------------------
-------------------------------

Cloud Management and Monitoring for Catalyst 42

Feb 2023
 1 C9300-24UX - Compatible 17.08.00.04 -
Compatible C9300-NM-2Q - Compatible
------------------------------------------------------------
----------------------------------------------------------
Compatible SKUs: C9300-24P, C9300-24T, C9300-24U, C9300-
24UX, C9300-48P, C9300-48T, C9300-48U, C9300-48UN, C9300-
48UXM
Compatible NMs : C3850-NM-2-40G, C3850-NM-4-10G, C3850-NM-8-
10G, C9300-NM-2Q, C9300-NM-8X, MA-MOD-2X40G, MA-MOD-4X10G,
MA-MOD-8X10G
------------------------------------------------------------
----------------------------------------------------------
Switch#

Note This command will check if the switch has the minimum required firmware
for migration and if the SKU is supported. Compatible means that the switch
supports migrating to the Meraki mode. This command will also check the
HW compatibility in terms of the supported SKUs (e.g. Network modules)

Step 4: Check the Catalyst 9300 Firmware version

In this step, you will check the siwtch’s firmware:

Check Switch Firmware

IOS Commands show version
IOS Output
Switch#show version
Cisco IOS XE Software, Version 17.07.01eft07
Cisco IOS Software [Bengaluru], Catalyst L3 Switch Software
(CAT9K_IOSXE), Version 17.7.1eft07, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2021 by Cisco Systems, Inc.
Compiled Thu 14-Oct-21 12:10 by mcpre

Cisco IOS-XE software, Copyright (c) 2005-2021 by cisco

Systems, Inc.
All rights reserved. Certain components of Cisco IOS-XE
software are
licensed under the GNU General Public License ("GPL")
Version 2.0. The
software code licensed under GPL Version 2.0 is free
software that comes
with ABSOLUTELY NO WARRANTY. You can redistribute and/or
modify such
GPL code under the terms of GPL Version 2.0. For more
details, see the
documentation or "License Notice" file accompanying the IOS-
XE software,
or the applicable URL provided on the flyer accompanying the
IOS-XE
software.

ROM: IOS-XE ROMMON

Cloud Management and Monitoring for Catalyst 43

Feb 2023
 BOOTLDR: System Bootstrap, Version 17.8.0.4r, RELEASE
SOFTWARE (P)

Switch uptime is 6 hours

System returned to ROM by Reload Command
System image file is "flash:packages.conf"
Last reload reason: Reload Command

This product contains cryptographic features and is subject

to United
States and local country laws governing import, export,
transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use
encryption.
Importers, exporters, distributors and users are responsible
for
compliance with U.S. and local country laws. By using this
product you
agree to comply with applicable laws and regulations. If you
are unable
to comply with U.S. and local laws, return this product
immediately.

A summary of U.S. laws governing Cisco cryptographic

products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by

sending email to
[email protected].

Technology Package License Information:

------------------------------------------------------------
------------------
Technology-package
Technology-package
Current Type
Next reboot
------------------------------------------------------------
------------------
network-advantage Smart License
network-advantage
dna-advantage Subscription Smart License dna-
advantage
AIR License Level: AIR DNA Advantage
Next reload AIR license Level: AIR DNA Advantage

Smart Licensing Status: Registration Not Applicable/Not

Applicable

cisco C9300-24UX (X86) processor with 1319368K/6147K bytes

of memory.
Processor board ID FCW2134L00J
1 Virtual Ethernet interface
4 Gigabit Ethernet interfaces
32 Ten Gigabit Ethernet interfaces
2 TwentyFive Gigabit Ethernet interfaces
2 Forty Gigabit Ethernet interfaces
2048K bytes of non-volatile configuration memory.
8388608K bytes of physical memory.

Cloud Management and Monitoring for Catalyst 44

Feb 2023
 1638400K bytes of Crash Files at crashinfo:.
11264000K bytes of Flash at flash:.

Base Ethernet MAC Address : 74:86:0b:c5:20:80

Motherboard Assembly Number : 73-17958-06
Motherboard Serial Number : FOC21316W1G
Model Revision Number : A0
Motherboard Revision Number : A0
Model Number : C9300-24UX
System Serial Number : FCW2134L00J
CLEI Code Number : INM3Y10BRA

Switch Ports Model SW Version SW Image

Mode
------ ----- ----- ---------- ----------
----
* 1 41 C9300-24UX 17.07.01eft07
CAT9K_IOSXE INSTALL

Configuration register is 0x102

Switch#

Note This command will show you the software version running on the switch
(Recommended version 17.08.1). Please note that the firmware used in this
lab is an EFT version.

Step 5: Check the Catalyst 9300 Hardware version

In this step, you will check the siwtch’s hardware version:

Check Switch Hardware

IOS Commands show module
IOS Output
Switch#show module
Switch Ports Model Serial No. MAC
address Hw Ver. Sw Ver.
------ ----- --------- ----------- ---------
----- ------- --------
1 41 C9300-24UX FCW2134L00J
7486.0bc5.2080 V01 17.07.01eft07
Switch#

Note The command will show you the HW version of the switch. Only production
models starting with “V” are supported for migration.

Step 6: Create a SVI with a routable IP address

In this step, you will create a SVI with a routable IP address which is required for access to
the Meraki Dashboard:

Cloud Management and Monitoring for Catalyst 45

Feb 2023
 Create a SVI
IOS Commands conf t
vlan 1
exit
interface vlan 1
ip address dhcp
no shut
exit
Ip route 0.0.0.0 0.0.0.0 dhcp
IOS Output
Switch#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#vlan 1
Switch(config-vlan)#exit
Switch(config)#interface vlan 1
Switch(config-if)#ip address dhcp
Switch(config-if)#no shut
Switch(config-if)#exit
Switch(config)#ip route 0.0.0.0 0.0.0.0 dhcp
Switch(config)#

Note VLAN 1 has been used to create an SVI to facilitate zero-touch deployment
of the migrated switch. Migrated switches will have an identical
configuration as a Meraki MS390 un-provisioned switch which has all
switchports in Trunk mode with Native VLAN 1 and allowed VLANs 1-1000

Note VLAN 1 has been configured with ip address dhcp again for ZTP purposes so
that the migrated switch can reach out to the Meraki Cloud and download its
configuration and firmware without the need of static IP assignment. After
the switch comes online, a static IP address can be configured in dashboard

Note Please note that you are using a simulation software and as such commands
and order used must adhere to this guide otherwise you will get an error

Step 7: Add a DNS Server

In this step, you will add a DNS server on the switch:

Add DNS Server

IOS Commands ip name-server 208.67.222.222
IOS Output
Switch#ip name-server 208.67.222.222
Switch#

Note Whilst it is possible to configure any DNS server (e.g. 8.8.8.8) the simulation
software has been hard coded with Umbrella DNS 208.67.222.222. The DNS

Cloud Management and Monitoring for Catalyst 46

Feb 2023
 server is required as the Meraki image running on the switch will reach out
to a few resources in the Meraki Cloud and will try to resolve some FQDNs.

Step 8: Change the HTTP Client Source Interface

In this step, you will change the source interface for the IOS XE HTTP Client to the SVI that
you have created earlier

HTTP Client Source Interface

IOS Commands ip http client source-interface vlan1
IOS Output
Switch#ip http client source-interface vlan1
Switch#

Note Using the SVI configured as a the http client source interface is important as
the Meraki image running on the switch will reach out to a few resources in
the Meraki Cloud and will need a routable IP address to be able to do that

Step 9: Test your Configuration

In this step, you will test your configuration so far by pinging a host on the public internet

Test Your Configuration

IOS Commands ping www.cisco.com
IOS Output
Switch#ping www.cisco.com
Switch#ping www.cisco.com
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 23.77.71.127, timeout is 2
seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max =
4/4/5 ms
Switch#

Note Whilst it is possible to ping any destination (e.g. 8.8.8.8) the simulation
software has been hard coded with cisco.com, so please use that ping test as
part of the lab exercise

Step 10: Register the switch with the Meraki Dashboard

In this step, you will register the switch with the Meraki Dashboard as a first step before
migrating it.

Cloud Management and Monitoring for Catalyst 47

Feb 2023
 Register the Catalyst Switch
IOS Commands service meraki register
IOS Output
Switch#service meraki register
% Are you sure you want to continue?[Yes:No]y
Starting to register switch 1
Converting catalyst.meraki.com to 209.206.53.169
Successfully connect to Meraki Dashboard
Switch 1 has been successfully registered
Meraki MAC: 74860BC52080
Meraki serial number: Q5TD-WWZU-WVGZ

Device Registration Status:

---------------------------
Switch Serial
Conversion
Num PID Number Meraki SN Mac Address
Status Mode
------------------------------------------------------------
--------------------
1 C9300-24UX FCW2134L00J Q5TD-WWZU-WVGZ 7486.0bc5.2080
Registered C9K-C
Switch#

Please take a note of the following:

• Catalyst Serial Number (FCW2134L00J)
• Meraki Serial Number (Q5TD-WWZU-WVGZ)
• Switch Mac Address (7486.0bc5.2080)

Note IOS XE will use the configured SVI and DNS server to reach out to the Meraki
Cloud and register the switch.

Step 11: Migrate the Catalyst 9300 switch

In this step, you will migrate the Catalyst 9300 switch by converting its running DNA
management mode to Meraki management mode:

Warning Migrating a Catalyst switch to Cloud Management will wipe its entire
configuration and files. After migration, the device will need to be re-
configured from scratch.

Migrate the Switch

IOS service meraki start
Commands
IOS
Switch#service meraki start
Output Device Registration Status:
---------------------------
Switch Serial
Conversion
Num PID Number Meraki SN Mac Address
Status Mode

Cloud Management and Monitoring for Catalyst 48

Feb 2023
 ---------------------------------------------------------------
-----------------
1 C9300-24UX FCW2134L00J Q5TD-WWZU-WVGZ 7486.0bc5.2080
Registered C9K-C

Proceeding with conversion will permanently erase all data,

the device console will be disabled and can only be managed by
Cisco Meraki dashboard.
Continue? [Y/N][confirm]y

The console BAUD rate will be reset to 9600 bps.

The following will be deleted:
1. Crash info and logs
2. User data, startup and running configuration
3. All IOS images, excluding the current boot image
4. User added Rommon variables
5. OBFL logs
6. Data on Field Replaceable Units(USB/SSD/SATA)
DO NOT UNPLUG THE POWER OR INTERRUPT THE OPERATION until the
device shows up on the Cisco Meraki dashboard.

Continue [Y/N][confirm]y

MCU 802.3bt mode supported: True, BT mode: False

MCU will use BT mode after next reload

Set switch to meraki boot mode

Switch#
Chassis 1 reloading, reason - Converting to Meraki mode
Nov 14 05:57:11.512: %PMAN-5-EXITACTION: F0/0: pvp: Process
manager is exiting: reload fp action requested
Nov 14 05:57:13.382: %PMAN-5-EXITACTION: R0/0: pvp: Procger is
exiting: rp processes exit with reload switch code

% FACTORYRESET - finish erase

% FACTORYRESET - Making File System sd1 [0]

Creating filesystem with 409600 4k blocks and 102544 inodes
Filesystem UUID: 0f8e5a09-6873-4367-b033-7bddd7874a64
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912

Allocating group tables: 0/13

Writing inode tables: 0/13
Writing superblocks and filesystem accounting information:
0/13

% FACTORYRESET - Mounting Back sd1 [0]

% FACTORYRESET - Handling Mounted sd1
% FACTORYRESET - Factory Reset Done for sd1

% FACTORYRESET - Unmounting sd3

% FACTORYRESET - Cleaning Up sd3 [0]
% FACTORYRESET - erase In progress.. please wait for
completion...
% FACTORYRESET - write zero...
% FACTORYRESET - finish erase

% FACTORYRESET - Making File System sd3 [0]

Cloud Management and Monitoring for Catalyst 49

Feb 2023
 Creating filesystem with 2816000 4k blocks and 704512 inodes
Filesystem UUID: a0a3d6f6-64ea-457c-a3ef-48841b1c2bd9
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208

Allocating group tables: 0/86

Writing inode tables: 0/86
Writing superblocks and filesystem accounting information:
0/86

% FACTORYRESET - Mounting Back sd3 [0]

% FACTORYRESET - Handling Mounted sd3
% FACTORYRESET - Factory Reset Done for sd3

% FACTORYRESET - Unmounting sd6

% FACTORYRESET - Cleaning Up sd6 [0]
% FACTORYRESET - erase In progress.. please wait for
completion...
% FACTORYRESET - write zero...
% FACTORYRESET - finish erase

% FACTORYRESET - Making File System sd6 [0]

Creating filesystem with 131072 1k blocks and 32768 inodes
Filesystem UUID: f13d6b46-aee1-41d6-aa74-d401119e9a14
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729

Allocating group tables: 0/16

Writing inode tables: 0/16
Writing superblocks and filesystem accounting information:
0/16

% FACTORYRESET - Mounting Back sd6 [0]

% FACTORYRESET - Handling Mounted sd6
% FACTORYRESET - Factory Reset Done for sd6
% FACTORYRESET - Lic Clean UP
% FACTORYRESET - Lic Clean Successful...
% FACTORYRESET - Clean Up Successful...
% FACTORYRESET - Check if usbflash0 is mounted...
% FACTORYRESET - Check if usbflash1 is mounted...
FACTORY-RESET-RESTORE-IMAGE Copying back image from
/tmp/factory_reset onto /bootflash
ReloadReason=Converting to Meraki mode
FACTORY-RESET-RESTORE-IMAGE Copying image is successful.

Initializing Hardware...

Initializing Hardware......
No ConsoleIn Access!
BOOT_DEVICE_MODE is set to meraki

System Bootstrap, Version 17.8.0.4r, RELEASE SOFTWARE (P)

Compiled Mon 09/20/2021 20:48:48.30 by rel

Current ROMMON image : Primary

Last reset cause : PowerOn
C9300-24UX platform with 8388608 Kbytes of main memory

boot is : [ boot flash:packages.conf ]

boot: attempting to boot from [flash:packages.conf]

boot: reading file packages.conf
#

Cloud Management and Monitoring for Catalyst 50

Feb 2023
 ###############################################################
####################################################
###############################################################
####################################################
###############################################################
####################################################
###############################################################
#######################

MCU 802.3bt mode supported: True, BT mode: True

Both links down, not waiting for other switches

Switch number is 1

Restricted Rights Legend

Use, duplication, or disclosure by the Government is

subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

Cisco Systems, Inc.

170 West Tasman Drive
San Jose, California 95134-1706

Cisco IOS Software [Bengaluru], Catalyst L3 Switch Software

(CAT9K_IOSXE), Version 17.7.1eft07, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2021 by Cisco Systems, Inc.
Compiled Thu 14-Oct-21 12:10 by mcpre

PLEASE READ THE FOLLOWING TERMS CAREFULLY. INSTALLING THE

LICENSE OR
LICENSE KEY PROVIDED FOR ANY CISCO SOFTWARE PRODUCT, PRODUCT
FEATURE,
AND/OR SUBSEQUENTLY PROVIDED SOFTWARE FEATURES (COLLECTIVELY,
THE
"SOFTWARE"), AND/OR USING SUCH SOFTWARE CONSTITUTES YOUR FULL
ACCEPTANCE OF THE FOLLOWING TERMS. YOU MUST NOT PROCEED FURTHER
IF YOU
ARE NOT WILLING TO BE BOUND BY ALL THE TERMS SET FORTH HEREIN.

Your use of the Software is subject to the Cisco End User

License Agreement
(EULA) and any relevant supplemental terms (SEULA) found at
http://www.cisco.com/c/en/us/about/legal/cloud-and-
software/software-terms.html.

You hereby acknowledge and agree that certain Software and/or

features are
licensed for a particular term, that the license to such
Software and/or
features is valid only for the applicable term and that such
Software and/or
features may be shut down or otherwise terminated by Cisco
after expiration

Cloud Management and Monitoring for Catalyst 51

Feb 2023
 of the applicable license term (e.g., 90-day trial period).
Cisco reserves
the right to terminate any such Software feature electronically
or by any
other means available. While Cisco may provide alerts, it is
your sole
responsibility to monitor your usage of any such term Software
feature to
ensure that your systems and networks are prepared for a
shutdown of the
Software feature.

% Checking backup nvram

% No config present. Using default config

FIPS: Flash Key Check : Key Not Found, FIPS Mode Not Enabled
cisco C9300-24UX (X86) processor with 1319368K/6147K bytes of
memory.
Processor board ID FCW2134L00J
2048K bytes of non-volatile configuration memory.
8388608K bytes of physical memory.
1638400K bytes of Crash Files at crashinfo:.
11264000K bytes of Flash at flash:.

Base Ethernet MAC Address : 74:86:0b:c5:20:80

Motherboard Assembly Number : 73-17958-06
Motherboard Serial Number : FOC21316W1G
Model Revision Number : A0
Motherboard Revision Number : A0
Model Number : C9300-24UX
System Serial Number : FCW2134L00J
CLEI Code Number :

WARNING: Command has been added to the configuration using a

type 0 password. However, recommended to migrate to
strong type-6 encryption
SETUP: new interface Vlan1 placed in "shutdown" state
*Nov 14 06:07:14.533: %CRYPTO-5-SELF_TEST_START: Crypto
algorithms release (Rel5a)
begin self-test
*Nov 14 06:07:15.264: %CRYPTO-5-SELF_TEST_END: Crypto algoritms
self-test completed successfully
All tests passed.

", "

*Nov 14 06:07:15.867: %SMART_LIC-6-EXPORT_CONTROLLED: Usage of

export controlled features is not allowed
*Nov 14 06:07:16.207: %PLATFORM-3-NVRAM_OPEN_FAIL: Failed to
open nvram - No such file or directory.
*Nov 14 06:07:16.207: %IOSXE_RP_NV-3-NV_ACCESS_FAIL: Initial
read of NVRAM contents failed
*Nov 14 06:07:16.207: %PLATFORM-3-BACKUP_NVRAM_OPEN_FAIL:
Failed to open backup nvram - No such file or directory.
*Nov 14 06:07:16.207: %IOSXE_RP_NV-3-BACKUP_NV_ACCESS_FAIL:
Initial read of backup NVRAM contents failed
*Nov 14 06:07:18.162: %SMART_LIC-6-AGENT_READY: Smart Agent for
Licensing is initialized
*Nov 14 06:07:20.988: %PLATFORM_SYS-4-SDM: Unsupported template
detected and default template has been loaded
*Nov 14 06:07:21.540: pagp init: platform supports EC/LACP xFSU
*Nov 14 06:07:21.714: LACP-GR: infra cb, GR_NONE

*Nov 14 06:07:23.653: ISIS-GRACEFUL-RELOAD: Init State GR_NONE

Cloud Management and Monitoring for Catalyst 52

Feb 2023
 *Nov 14 06:07:23.980: %TLSCLIENT-5-TLSCLIENT_IOS: TLS Client is
IOS based
*Nov 14 06:07:24.304: %CRYPTO-4-AUDITWARN: Encryption audit
check could not be performed
*Nov 14 06:07:24.304: %CRYPTO_ENGINE-4-
CSDL_COMPLIANCE_DISABLED: Cisco PSB security compliance has
been disabled
*Nov 14 06:07:24.324: %SPANTREE-5-EXTENDED_SYSID: Extended
SysId enabled for type vlan
*Nov 14 06:07:25.079: %LINK-3-UPDOWN: Interface Lsmpi18/3,
changed state to up
*Nov 14 06:07:25.086: %LINK-3-UPDOWN: Interface EOBC18/1,
changed state to up
*Nov 14 06:07:25.087: %LINEPROTO-5-UPDOWN: Line protocol on
Interface LI-Null0, changed state to up
*Nov 14 06:07:25.087: %LINK-3-UPDOWN: Interface
GigabitEthernet0/0, changed state to down
*Nov 14 06:07:25.087: %LINEPROTO-5-UPDOWN: Line protocol on
Interface LIIN18/2, changed state to up
*Nov 14 06:07:25.088: %LINK-3-UPDOWN: Interface LIIN18/2,
changed state to up
*Nov 14 06:07:25.088: %LINK-5-CHANGED: Interface Bluetooth0/4,
changed state to administratively down
*Nov 14 06:07:25.273: %PNP-6-PNP_DISCOVERY_STARTED: PnP
Discovery started
*Nov 14 06:07:25.280: %PNP-6-PNP_GOOD_UDI_UPDATE: Good UDI
[PID:C9300-24UX,VID:,SN:FCW2134L00J] identified via (platform-
registry)
*Nov 14 06:07:25.280: %PNP-6-PNP_CDP_UPDATE: Device UDI
[PID:C9300-24UX,VID:,SN:FCW2134L00J] identified for CDP
*Nov 14 06:07:25.362: %HMANRP-6-HMAN_IOS_CHANNEL_INFO: HMAN-IOS
channel event for switch 1: EMP_RELAY: Channel UP!
*Nov 14 06:07:06.926: %STACKMGR-6-STACK_LINK_CHANGE: Switch 1
R0/0: stack_mgr: Stack port 1 on Switch 1 is cable-not-
connected
*Nov 14 06:07:06.926: %STACKMGR-6-STACK_LINK_CHANGE: Switch 1
R0/0: stack_mgr: Stack port 2 on Switch 1 is down
*Nov 14 06:07:06.926: %STACKMGR-6-STACK_LINK_CHANGE: Switch 1
R0/0: stack_mgr: Stack port 2 on Switch 1 is cable-not-
connected
*Nov 14 06:07:06.926: %STACKMGR-4-SWITCH_ADDED: Switch 1 R0/0:
stack_mgr: Switch 1 has been added to the stack.
*Nov 14 06:07:09.332: %STACKMGR-4-SWITCH_ADDED: Switch 1 R0/0:
stack_mgr: Switch 1 has been added to the stack.
*Nov 14 06:07:11.372: %STACKMGR-4-SWITCH_ADDED: Switch 1 R0/0:
stack_mgr: Switch 1 has been added to the stack.
*Nov 14 06:07:11.373: %STACKMGR-6-ACTIVE_ELECTED: Switch 1
R0/0: stack_mgr: Switch 1 has been elected ACTIVE.
*Nov 14 06:07:26.175: %LINEPROTO-5-UPDOWN: Line protocol on
Interface Lsmpi18/3, changed state to up
*Nov 14 06:07:26.176: %LINEPROTO-5-UPDOWN: Line protocol on
Interface EOBC18/1, changed state to up
*Nov 14 06:07:26.176: %LINEPROTO-5-UPDOWN: Line protocol on
Interface GigabitEthernet0/0, changed state to down
*Nov 14 06:07:26.176: %LINEPROTO-5-UPDOWN: Line protocol on
Interface Bluetooth0/4, changed state to down
*Nov 14 06:07:26.723: ILP:: switch 1 POE mode : IEEE BT
*Nov 14 06:07:26.723: ILP:: POE POST detail for switch 1: PASS
*Nov 14 06:07:26.723: ILP:: Able to get POE POST from switch
1 MCU
*Nov 14 06:07:26.835: %SYS-5-CONFIG_P: Configured
programmatically by process MGMT VRF Process from console as
vty0
*Nov 14 06:07:27.087: %IOSXE_MGMTVRF-6-CREATE_SUCCESS_INFO:
Management vrf Mgmt-vrf created with ID 1, ipv4 table-id 0x1,
ipv6 table-id 0x1E000001

Cloud Management and Monitoring for Catalyst 53

Feb 2023
 *Nov 14 06:07:27.089: %SYS-5-CONFIG_P: Configured
programmatically by process MGMT VRF Process from console as
vty0
*Nov 14 06:07:27.097: %IOSXE_MGMTVRF-6-CREATE_SUCCESS_INFO:
Management vrf Mgmt-vrf created with ID 1, ipv4 table-id 0x1,
ipv6 table-id 0x1E000001
*Nov 14 06:07:27.098: %SYS-5-CONFIG_P: Configured
programmatically by process MGMT VRF Process from console as
vty0
*Nov 14 06:07:27.545: %ONEP_BASE-6-SS_ENABLED: ONEP: Service
set Base was enabled by Default
*Nov 14 06:07:27.593: %LINEPROTO-5-UPDOWN: Line protocol on
Interface Vlan1, changed state to down
*Nov 14 06:07:27.723: %SYS-5-CONFIG_P: Configured
programmatically by process PnP Agent Discovery from console as
vty0
*Nov 14 06:07:28.344: %SYS-7-NVRAM_INIT_WAIT_TIME: Waited 0
seconds for NVRAM to be available
*Nov 14 06:07:28.344: %IOXN_APP-6-STARTUP_CONFIG_INFO: Creating
startup-config

*Nov 14 06:07:28.344: %IOXN_APP-6-STARTUP_CONFIG_CHASSIS_INFO:

Resolved global active location 1/BINOS_FRU_RP/0/0

*Nov 14 06:07:29.589: %AAAA-4-CLI_DEPRECATED: WARNING: Command

has been added to the configuration using a type 0 password.
However, recommended to migrate to strong type-6 encryption
*Nov 14 06:07:29.982: %CDP-6-TLV_LIST_GLOBALLY: Tlv-list Meraki
applied globally on all interfaces.
*Nov 14 06:07:31.016: %LINEPROTO-5-UPDOWN: Line protocol on
Interface Vlan4093, changed state to down
*Nov 14 06:07:31.116: %SYS-5-CONFIG_I: Configured from memory
by console
*Nov 14 06:07:31.248: %SYS-5-CONFIG_P: Configured
programmatically by process CPP MQC QoS Policy manager from
console as vty0
*Nov 14 06:07:31.311: %PLATFORM_FEP-6-FRU_PS_OIR: Switch 1: FRU
power supply A inserted
*Nov 14 06:07:31.334: %CRYPTO-5-SELF_TEST_START: Crypto
algorithms release (Rel5a)
begin self-test
*Nov 14 06:07:31.339: %CRYPTO-5-SELF_TEST_END: Crypto algoritms
self-test completed successfully
All tests passed.
*Nov 14 06:07:30.943: %UICFGEXP-6-SERVER_NOTIFIED_START: Switch
1 R0/0: psd: Server iox has been notified to start
*Nov 14 06:07:31.561: %IOXN_APP-6-SLOT_NOTIFICATION: Received
OIRSHIM_EV_CHASSIS_ADDED for slot 1
*Nov 14 06:07:31.771: %SYS-5-RESTART: System restarted --
Cisco IOS Software [Bengaluru], Catalyst L3 Switch Software
(CAT9K_IOSXE), Version 17.7.1eft07, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2021 by Cisco Systems, Inc.
Compiled Thu 14-Oct-21 12:10 by mcpre
*Nov 14 06:07:31.932: %SYS-5-CONFIG_P: Configured
programmatically by process NGWC_OIRSHIM_TASK from console as
console
*Nov 14 06:07:32.005: %SNMP-5-COLDSTART: SNMP agent on host
Switch is undergoing a cold start
*Nov 14 06:07:33.140: %LINK-5-CHANGED: Interface Vlan1, changed
state to administratively down
*Nov 14 06:07:33.863: %LINK-3-UPDOWN: Interface
AppGigabitEthernet1/0/1, changed state to down
*Nov 14 06:07:36.554: ILP:: switch 1 POE mode : IEEE BT
*Nov 14 06:07:36.554: ILP:: POE POST detail for switch 1: PASS

Cloud Management and Monitoring for Catalyst 54

Feb 2023
 *Nov 14 06:07:36.554: ILP:: Able to get POE POST from switch
1 MCU
*Nov 14 06:07:37.792: %PNP-6-PNP_BEST_UDI_UPDATE: Best UDI
[PID:C9300-24UX,VID:A0,SN:FCW2134L00J] identified via (master-
registry)
*Nov 14 06:07:39.797: %SYS-5-CONFIG_P: Configured
programmatically by process PnP Agent Discovery from console as
vty0
*Nov 14 06:07:39.798: %PNP-6-PNP_DISCOVERY_STOPPED: PnP
Discovery stopped (Startup Config Present)
*Nov 14 06:07:43.342: %LINK-3-UPDOWN: Interface
GigabitEthernet0/0, changed state to up
*Nov 14 06:07:44.342: %LINEPROTO-5-UPDOWN: Line protocol on
Interface GigabitEthernet0/0, changed state to up
*Nov 14 06:07:44.595: %PKI-2-NON_AUTHORITATIVE_CLOCK: PKI
functions can not be initialized until an authoritative time
source, like NTP,
can be obtained.
*Nov 14 06:07:44.628: %PKI-6-TRUSTPOINT_CREATE: Trustpoint:
TEST_CISCO_IDEVID_SUDI created succesfully
*Nov 14 06:07:44.654: %CRYPTO_ENGINE-5-KEY_ADDITION: A key
named TEST_CISCO_IDEVID_SUDI has been generated or imported by
pki-sudi
*Nov 14 06:07:44.710: %SSH-5-ENABLED: SSH 1.99 has been enabled
*Nov 14 06:07:44.773: %PKI-6-TRUSTPOINT_CREATE: Trustpoint:
TEST_CISCO_IDEVID_SUDI0 created succesfully
*Nov 14 06:07:44.776: %CRYPTO_ENGINE-5-KEY_DELETED: A key named
TEST_CISCO_IDEVID_SUDI has been removed from key storage
*Nov 14 06:07:44.793: %PKI-6-TRUSTPOINT_DELETE: Trustpoint:
TEST_CISCO_IDEVID_SUDI deleted succesfully
*Nov 14 06:07:44.810: %PKI-6-TRUSTPOINT_DELETE: Trustpoint:
TEST_CISCO_IDEVID_SUDI0 deleted succesfully
*Nov 14 06:07:44.810: %PKI-6-TRUSTPOINT_CREATE: Trustpoint:
TEST_CISCO_IDEVID_SUDI created succesfully
*Nov 14 06:07:44.820: %CRYPTO_ENGINE-5-KEY_ADDITION: A key
named TEST_CISCO_IDEVID_SUDI has been generated or imported by
pki-sudi
*Nov 14 06:07:44.821: %SSH-5-DISABLED: SSH 1.99 has been
disabled
*Nov 14 06:07:44.826: %SSH-5-ENABLED: SSH 1.99 has been enabled
*Nov 14 06:07:44.849: %PKI-6-TRUSTPOINT_CREATE: Trustpoint:
TEST_CISCO_IDEVID_SUDI0 created succesfully
*Nov 14 06:07:44.852: %CRYPTO_ENGINE-5-KEY_DELETED: A key named
TEST_CISCO_IDEVID_SUDI has been removed from key storage
*Nov 14 06:07:44.852: %PKI-6-TRUSTPOINT_DELETE: Trustpoint:
TEST_CISCO_IDEVID_SUDI deleted succesfully
*Nov 14 06:07:44.854: %PKI-6-TRUSTPOINT_DELETE: Trustpoint:
TEST_CISCO_IDEVID_SUDI0 deleted succesfully
*Nov 14 06:07:44.855: %PKI-6-TRUSTPOINT_CREATE: Trustpoint:
CISCO_IDEVID_SUDI created succesfully
*Nov 14 06:07:44.863: %CRYPTO_ENGINE-5-KEY_ADDITION: A key
named CISCO_IDEVID_SUDI has been generated or imported by pki-
sudi
*Nov 14 06:07:44.869: %SSH-5-DISABLED: SSH 1.99 has been
disabled
*Nov 14 06:07:44.913: %PKI-6-TRUSTPOINT_CREATE: Trustpoint:
CISCO_IDEVID_SUDI0 created succesfully
*Nov 14 06:07:44.916: %PKI-6-TRUSTPOINT_CREATE: Trustpoint:
CISCO_IDEVID_SUDI_LEGACY created succesfully
*Nov 14 06:07:44.925: %CRYPTO_ENGINE-5-KEY_ADDITION: A key
named CISCO_IDEVID_SUDI_LEGACY has been generated or imported
by pki-sudi
*Nov 14 06:07:44.950: %PKI-6-TRUSTPOINT_CREATE: Trustpoint:
CISCO_IDEVID_SUDI_LEGACY0 created succesfully
*Nov 14 06:07:44.904: %IOSXE-6-PLATFORM: Switch 1 R0/0: IOx:
App verification successful

Cloud Management and Monitoring for Catalyst 55

Feb 2023
 *Nov 14 06:07:46.772: %CRYPTO_ENGINE-5-KEY_ADDITION: A key
named TEST_CISCO_IDEVID_SUDI.server has been generated or
imported by crypto-engine
*Nov 14 06:07:46.781: %SSH-5-ENABLED: SSH 1.99 has been enabled
*Nov 14 06:07:48.571: %CRYPTO_ENGINE-5-KEY_REPLACE: A key named
TEST_CISCO_IDEVID_SUDI.server has been replaced by crypto-
engine with new key data
*Nov 14 06:07:48.572: %SSH-5-DISABLED: SSH 1.99 has been
disabled
*Nov 14 06:07:48.579: %SSH-5-ENABLED: SSH 1.99 has been enabled
*Nov 14 06:07:49.867: %CRYPTO_ENGINE-5-KEY_ADDITION: A key
named TEST_CISCO_IDEVID_SUDI.server.server has been generated
or imported by crypto-engine
*Nov 14 06:07:49.243: %IOSXE-6-PLATFORM: Switch 1 R0/0: IOx:
App verification successful
*Nov 14 06:07:51.171: %CRYPTO_ENGINE-5-KEY_REPLACE: A key named
TEST_CISCO_IDEVID_SUDI.server.server has been replaced by
crypto-engine with new key data
*Nov 14 06:07:51.798: %CRYPTO_ENGINE-5-KEY_REPLACE: A key named
TEST_CISCO_IDEVID_SUDI.server.server has been replaced by
crypto-engine with new key data
*Nov 14 06:07:52.983: %CRYPTO_ENGINE-5-KEY_REPLACE: A key named
TEST_CISCO_IDEVID_SUDI.server.server has been replaced by
crypto-engine with new key data
*Nov 14 06:08:09.589: %IM-6-START_MSG: Switch 1 R0/0: ioxman:
app-hosting: Start succeeded: meraki is started Current is in
RUNNING
*Nov 14 06:08:09.591: %IM-6-IOX_ENABLEMENT: Switch 1 R0/0:
ioxman: IOX is ready.
*Nov 14 06:08:11.696: %EVENT_TRACE-6-ENABLE: Trace already
enabled.
*Nov 14 06:08:11.696: %EVENT_TRACE-6-ENABLE: Trace already
enabled.
*Nov 14 06:08:11.696: %EVENT_TRACE-6-ENABLE: Trace already
enabled.
*Nov 14 06:08:11.696: %EVENT_TRACE-6-ENABLE: Trace already
enabled.
*Nov 14 06:08:15.009: %LINK-3-UPDOWN: Interface
AppGigabitEthernet1/0/1, changed state to up
*Nov 14 06:08:16.009: %LINEPROTO-5-UPDOWN: Line protocol on
Interface AppGigabitEthernet1/0/1, changed state to up
*Nov 14 06:08:16.076: %LINEPROTO-5-UPDOWN: Line protocol on
Interface Vlan4093, changed state to up

Starting Meraki app...

*Nov 14 06:08:27.541: %IOSXE-3-PLATFORM: Switch 1 R0/0: kernel:

ip_local_port_range: prefer different parity for start/end
values.
*Nov 14 06:08:28.916: %PLATFORM_LED-6-BEACON_LED_BLINK: Switch
1 Beacon LED Blinking turned ON
*Nov 14 06:08:31.841: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_622844454DC7DE6B82000001_conn_100006_vty_100001 from
console as iox on vty76
*Nov 14 06:08:34.377: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_622844454DC7DE6B82000001_conn_100006_vty_100001 from
console as iox on vty76
*Nov 14 06:08:34.991: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_622844454DC7DE6B82000001_conn_100006_vty_100001 from
console as iox on vty76

Cloud Management and Monitoring for Catalyst 56

Feb 2023
 *Nov 14 06:08:34.995: %PKI-6-TRUSTPOINT_CREATE: Trustpoint: TP-
self-signed-4289820356 created succesfully
*Nov 14 06:08:35.040: %PSD_MOD-5-DMI_NOTIFY_NETCONF_START:
Switch 1 R0/0: psd: PSD/DMI: netconf-yang server has been
notified to start
*Nov 14 06:08:35.956: %PLATFORM_PM-6-FRULINK_INSERTED: 2x40G
uplink module inserted in the switch 1 slot 1
*Nov 14 06:08:37.653: %CRYPTO_ENGINE-5-KEY_ADDITION: A key
named TP-self-signed-4289820356 has been generated or imported
by crypto-engine
*Nov 14 06:08:37.708: %PKI-4-NOCONFIGAUTOSAVE: Configuration
was modified. Issue "write memory" to save new IOS PKI
configuration
*Nov 14 06:08:37.708: yang-infra: PKI no mismatch found
*Nov 14 06:09:20.911: %NDBMAN-5-ACTIVE: Switch 1 R0/0: ndbmand:
All data providers active.
*Nov 14 06:09:29.498: %DMI-5-NACM_INIT: Switch 1 R0/0:
dmiauthd: NACM configuration has been set to its initial
configuration.
*Nov 14 06:09:33.148: %DMI-5-SYNC_NEEDED: Switch 1 R0/0:
dmiauthd: Configuration change requiring running configuration
sync detected - 'Initial sync'
The running configuration will be synchronized to the NETCONF
running data store.
*Nov 14 06:09:33.326: %DMI-5-SYNC_START: Switch 1 R0/0:
dmiauthd: Synchronization of the running configuration to the
NETCONF running
data store has started.
*Nov 14 06:09:40.760: %DMI-5-SYNC_COMPLETE: Switch 1 R0/0:
dmiauthd: The running configuration has been synchronized to
the NETCONF running data store
*Nov 14 06:09:44.764: %DMI-5-AUTH_PASSED: Switch 1 R0/0:
dmiauthd: User 'miles' authenticated successfully from
1.1.3.2:40926 for netconf over ssh.
External groups: PRIV15
*Nov 14 06:09:46.662: %CLEAR-5-COUNTERS: Clear counter on all
interfaces by NETCONF on vty63
*Nov 14 06:09:48.042: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:09:48.161: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:09:48.439: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:09:48.037: %DMI-5-CONFIG_I: Switch 1 R0/0: dmiauthd:
Configured from NETCONF/RESTCONF by miles, transaction-id 36
*Nov 14 06:09:48.558: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:09:48.694: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:09:48.682: %DMI-5-SYNC_NEEDED: Switch 1 R0/0:
dmiauthd: Configuration change requiring running configuration
sync detected - 'ip
http secure-server'. The running configuration will be
synchronized to the NETCONF running data store.

Cloud Management and Monitoring for Catalyst 57

Feb 2023
 *Nov 14 06:09:48.928: %DMI-5-SYNC_START: Switch 1 R0/0:
dmiauthd: Synchronization of the running configuration to the
NETCONF running
data store has started.
*Nov 14 06:10:11.921: %DMI-5-SYNC_COMPLETE: Switch 1 R0/0:
dmiauthd: The running configuration has been synchronized to
the NETCONF running
data store.
*Nov 14 06:10:14.755: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:14.867: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:14.986: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:15.100: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:14.750: %DMI-5-CONFIG_I: Switch 1 R0/0: dmiauthd:
Configured from NETCONF/RESTCONF by miles, transaction-id 80
*Nov 14 06:10:15.214: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:15.325: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:15.428: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:15.626: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:15.737: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:15.991: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:16.133: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:16.251: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:16.383: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:16.488: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63

Cloud Management and Monitoring for Catalyst 58

Feb 2023
 *Nov 14 06:10:16.608: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:16.977: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:21.362: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:21.658: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:21.306: %DMI-5-CONFIG_I: Switch 1 R0/0: dmiauthd:
Configured from NETCONF/RESTCONF by miles, transaction-id 147
*Nov 14 06:10:21.857: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:22.052: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:22.345: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:22.266: %DMI-5-SYNC_NEEDED: Switch 1 R0/0:
dmiauthd: Configuration change requiring running configuration
sync detected - 'line vty 0 4'
The running configuration will be synchronized to the NETCONF
running data store.
*Nov 14 06:10:22.975: %DMI-5-SYNC_START: Switch 1 R0/0:
dmiauthd: Synchronization of the running configuration to the
NETCONF running
data store has started.
*Nov 14 06:10:37.167: %DMI-5-SYNC_COMPLETE: Switch 1 R0/0:
dmiauthd: The running configuration has been synchronized to
the NETCONF running
data store.
*Nov 14 06:10:40.182: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:40.117: %DMI-5-CONFIG_I: Switch 1 R0/0: dmiauthd:
Configured from NETCONF/RESTCONF by miles, transaction-id 177
*Nov 14 06:10:41.413: %LINEPROTO-5-UPDOWN: Line protocol on
Interface Tunnel1000000000, changed state to down
*Nov 14 06:10:41.570: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:42.392: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:44.510: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:44.617: %SYS-5-CONFIG_P: Configured
programmatically by process

Cloud Management and Monitoring for Catalyst 59

Feb 2023
 iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:45.626: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:45.621: %DMI-5-CONFIG_I: Switch 1 R0/0: dmiauthd:
Configured from NETCONF/RESTCONF by miles, transaction-id 209
*Nov 14 06:10:45.719: %IM-5-IOX_INST_NOTICE: Switch 1 R0/0:
ioxman: IOX SERVICE meraki LOG: brain finished initial IOS
setup
*Nov 14 06:10:46.296: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_622844454DC7DE6B82000001_conn_100006_vty_100001 from
console as
iox on vty76
*Nov 14 06:10:46.749: LLDP-Local-Chassi-ID: Global stack mac
address retreival succeeded chassis_mac is 74:86:B :C5:20:80

*Nov 14 06:10:46.757: %SYS-5-CONFIG_P: Configured

programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:47.081: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_622844454DC7DE6B82000001_conn_100006_vty_100001 from
console as
iox on vty76
*Nov 14 06:10:47.833: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_622844454DC7DE6B82000001_conn_100006_vty_100001 from
console as
iox on vty76
*Nov 14 06:10:48.245: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:48.576: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:48.711: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:49.033: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:49.666: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:49.831: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:50.327: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:51.494: %LINEPROTO-5-UPDOWN: Line protocol on
Interface Tunnel1000000000, changed state to down
*Nov 14 06:10:51.592: %SYS-5-CONFIG_P: Configured
programmatically by process

Cloud Management and Monitoring for Catalyst 60

Feb 2023
 iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:51.586: %DMI-5-CONFIG_I: Switch 1 R0/0: dmiauthd:
Configured from NETCONF/RESTCONF by miles, transaction-id 265
*Nov 14 06:10:51.960: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_622844454DC7DE6B82000001_conn_100012_vty_100001 from
console as
iox on vty74
*Nov 14 06:10:52.076: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:52.206: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:52.336: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:52.459: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:52.578: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:53.901: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:54.084: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:54.275: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:54.495: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:54.697: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:10:55.018: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_622844454DC7DE6B82000001_conn_100012_vty_100001 from
console as
iox on vty74
*Nov 14 06:10:55.335: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_622844454DC7DE6B82000001_conn_100012_vty_100001 from
console as
iox on vty74
*Nov 14 06:10:55.696: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_622844454DC7DE6B82000001_conn_100012_vty_100001 from
console as
iox on vty74

Cloud Management and Monitoring for Catalyst 61

Feb 2023
 *Nov 14 06:10:55.800: %DMI-5-SYNC_NEEDED: Switch 1 R0/0:
dmiauthd: Configuration change requiring running configuration
sync detected - '
ip igmp snooping '.
The running configuration will be synchronized to the NETCONF
running data store.
*Nov 14 06:10:56.069: %DMI-5-SYNC_START: Switch 1 R0/0:
dmiauthd: Synchronization of the running configuration to the
NETCONF running
data store has started.

Meraki app is up and connecting to Dashboard ...

*Nov 14 06:10:59.554: %PLATFORM_LED-6-BEACON_LED_TURNED: Switch

1 Beacon LED turned ON
*Nov 14 06:11:11.730: %DMI-5-SYNC_COMPLETE: Switch 1 R0/0:
dmiauthd: The running configuration has been synchronized to
the NETCONF running
data store.
*Nov 14 06:11:12.899: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:11:13.193: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_dmiauthd_conn_100007_vty_100001 from console as miles on
vty63
*Nov 14 06:11:12.895: %DMI-5-CONFIG_I: Switch 1 R0/0: dmiauthd:
Configured from NETCONF/RESTCONF by miles, transaction-id 333
*Nov 14 06:11:13.703: %SYS-5-CONFIG_P: Configured
programmatically by process
iosp_622844454DC7DE6B82000001_conn_100012_vty_100001 from
console as
iox on vty74
<<<< output omitted

Note At this stage, the C9300 switch has been successfully migrated by switching
modes and running the Meraki image on top of IOS XE

Note At this stage, the terminal will be locked (to mimic an actual migrated switch)
and will only display logs

Congratulations! You have successfully migrated a Catalyst 9300 switch by converting its
running DNA management mode to Meraki management mode which enables full
management in the Meraki Dashboard. From this moment, the switch will operate as a
Meraki MS390 switch from a feature-set and dashboard experience perspective.

Cloud Management and Monitoring for Catalyst 62

Feb 2023
 Scenario #5 – Cloud Management for Catalyst
In the previous exercise, you have successfully migrated a Catalyst 9300 switch by converting
the default running DNA management mode to Meraki management mode. In this lab activity,
you will learn how to manage a device in Dashboard by accessing the previously migrated
switch in the Meraki dashboard.

Task 1: Manage a Migrated Catalyst Device in Dashboard

In this task, you will learn how to download the onboarding app to your workstation and get
familiar with it’s different components.

Step 1: Login to Meraki Dashboard

First, As Dashboard uses Two Factor Authentication, please download the Google
Authenticator app from your app store and follow these steps to set it up:

o Download the Google Authenticator app on your smart phone

o Add the following QR code:

Then, From your browser go to https://dashboard.meraki.com and login using the following
details in Table 3 as depicted in Figure 49

Note If you are still logged in dashboard, please signout and login again to be able
to access the correct organization

Cloud Management and Monitoring for Catalyst 63

Feb 2023
 You will be prompted for the security code, please use the OTP from the Google
Authenticator app from the account that you have just added in the previous step.

Note Please note that you might be presented with a landing page that looks like
this:

In this case, please click on “Use current settings” and you should be able
to login

Table 3

Username [email protected]
Password geztih-buTcod-mupfa8!

Figure 49

Then, click on Cloud Management & Monitoring for Catalyst to access this organisation in
Dashboard as depicted in Figure 50

Cloud Management and Monitoring for Catalyst 64

Feb 2023
 Figure 50

Step 2: Search for the Migrated Switch

Tip The migrated switch information as per the previous section:

• Catalyst Serial Number (FCW2134L00J)

• Meraki Serial Number (Q5TD-WWZU-WVGZ)
• Switch Mac Address (7486.0bc5.2080)

From the left menu, Navigate to Organization > Overview as depicted in Figure 51

Figure 51

Then, click on the devices tab and search for the switch serial number as depicted in Figure
52 and Figure 53

Cloud Management and Monitoring for Catalyst 65

Feb 2023
 Figure 52

Figure 53

Tip You can search for the migrated switch by either the Meraki serial number or, the
switch Mac address as shown in the below figures

Step 3: Check the switch status in Dashboard

After you have found the switch in the previous step, click on it to access the switch details
page as depicated in Figure 54

Figure 54

Here you can see the switch details page as depicated in Figure 55

Cloud Management and Monitoring for Catalyst 66

Feb 2023
 Figure 55

Now, find the following details from that page (You can find the answers in the second
column in Table 4)
Table 4

Item Value Figure

Network name Tasman Campus C

Switch name C9300-Single

Switch Model C9300-24UX

Switch mac 74:86:0b:c5:20:80

address

LAN IP 10.16.93.112

Cloud Management and Monitoring for Catalyst 67

Feb 2023
 Management VLAN 1

Public IP 173.36.197.118

Gateway 10.16.93.97

DNS 10.16.1.10

Catalyst SN FCW2134L00J

Meraki SN Q5TD-WWZU-
WVGZ

Tags 9300 Migrated

STP Root This switch

Firmware version MS 15.12.1

Uplink port 22

Cloud Management and Monitoring for Catalyst 68

Feb 2023
 Core Switch details C9500SV-CORE-RIO
[1]

C9500-24Y4C

a0:b4:39:77:38:80

CAT2345L1MJ
(Catalyst)

Q2ZZ-58Y2-FREJ

Step 4 [Optional/Bonus]: Gather Additional details about the Migrated Switch

Can you find the following items in Table 5 by navigating dashboard for the migrated
switch? (Please ask your proctor if you have any questions)

Table 5

Item Value
How many PSUs are
installed on the
C9300 switch?
Is Layer 3 routing
enabled on the
switch?
How many ports are
tagged with “xyz6”
What is the VLAN
configured on port
15?
How many stacks
are there in this
network?
What is the
firmware running
on the upstream
core switch?

Cloud Management and Monitoring for Catalyst 69

Feb 2023
 Can you ping a
downstream client
(10.16.93.68) from
the upstream core
switch?
What is the core
switch port used to
connect to the
C9300 switch
uplink?
Is the core switch
part of a stack?
What is the stack
name?
How many switches
are in the core
stack?
How many ports are
connected on this
stack?
What is the uplink
port in this stack?

Related Sessions at Ciscolive

Here are some related sessions at Cisco Live Amsterdam that might be of interest to you:

Session Title Session Code

Monitor your Catalyst 9000 switch from Meraki Dashboard BRKENS-2201
One Day in the Life of Catalyst and Access Point in the Meraki BRKMER-2020
Cloud
Scalable Meraki Access Switching BRKMER-1415
Simplifying network management with Meraki API BRKOPS-2810
Automate Meraki Alerting & Response with Webhooks and AWS DEVWKS-2845
Lambda
Introduction to the Meraki Dashboard API DEVWKS-1494
Meraki Wireless from a Troubleshooter Perspective BRKMER-2399
10 Things You Don't Know About Meraki Wireless BRKMER-2514
9100 Wi-Fi 6E APs Managed from Cloud or On Premises? We've got LTREWN-2034
you Covered!

Content Catalog Link

Cloud Management and Monitoring for Catalyst 70

Feb 2023
 Summary
We hope that you’ve enjoyed the lab and learned how to onboard a Catalyst device for
Cloud Monitoring and migrate a Catalyst device for Cloud Management. Here are some
useful resources should you wish to get more details:
• Cloud Monitoring Overview & FAQ (link)

• Cloud Monitoring Onboarding Guide (link)

• Cloud Monitoring SKUs (link)

• Meraki Community for Cloud Management and Monitoring (link)

• Cloud Monitoring Quick Start Guide (link)

• Cloud Monitoring for Catalyst Guided Resources (link)

• Cisco Catalyst Cloud Monitoring – Cisco Learning (link)

Cloud Management and Monitoring for Catalyst 71

Feb 2023