Scribd
Upload
5 views10 pages

ECMS2 Admin03

The document outlines a reset process for converting an ECMS2 lab environment back to ECMS1, detailing steps for granting access to the ADMIN-PARK network, deleting existing lab networks, recreating lab pod networks, reconfiguring backbone networks, and modifying lab account privileges. Each part includes specific instructions for managing user accounts, deleting and creating networks, and ensuring proper configurations for the transition. The final steps ensure that lab participants have the correct access levels and that the environment is ready for ECMS1 sessions.

Uploaded by

Dúber Pérez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views10 pages

ECMS2 Admin03

The document outlines a reset process for converting an ECMS2 lab environment back to ECMS1, detailing steps for granting access to the ADMIN-PARK network, deleting existing lab networks, recreating lab pod networks, reconfiguring backbone networks, and modifying lab account privileges. Each part includes specific instructions for managing user accounts, deleting and creating networks, and ensuring proper configurations for the transition. The final steps ensure that lab participants have the correct access levels and that the environment is ready for ECMS1 sessions.

Uploaded by

Dúber Pérez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

Reset Process for Converting ECMS2 Back to ECMS1

The following procedure will reset the lab environment in preparation of running an ECMS1 session. The process
will take a used ECMS2 environment and reset it back to a state that is ready to be used for an ECMS1 session.
This will include the necessary configuration modifications.

Part 1: Grant Lab Accounts Access to the ADMIN-PARK Network

Please note that, in the Cisco Meraki dashboard, an administrator account will be deleted if all of the
networks for which that administrator has permissions to manage are deleted. The ADMIN-PARK network
will be used to ensure network administrators are not deleted before the lab reset process begins.
Administrators will be configured to only temporarily access the ADMIN-PARK network.

Follow the steps below to grant lab user accounts temporary access to the ADMIN-PARK network:
1. Choose Organization > CONFIGURE > Administrators.

2. Click the row of the first lab pod user account to open the Update administrator window.
3. Click + Add access privileges and select ADMIN-PARK from the Target drop-down list. Set the Access
permissions of Full.
4. Click Update admin.
5. Repeat the above process to modify the remaining 14 lab pod user accounts.
6. Click the Save changes at the bottom of the screen to complete the process and commit the permission
changes to all 15 lab pod user accounts

Part 2: Delete All Lab Networks


Once all lab pod user accounts have been given access to the ADMIN-PARK network, you will proceed to remove
all 15 of the lab pod networks.

Follow the steps below to delete the networks:


1. Choose Organization > MONITOR > Overview.

2. Check the checkbox next to each of the 15 LAB[n] networks.


3. Select Delete to remove these networks.
4. On the Delete network confirmation page, check the I acknowledge that deleting these networks is
irreversible and wish to continue check box.
5. Click Delete Networks.
Part 3: Recreate the Student Lab Pod Networks
Once all 15 student lab pod networks have been removed, you will need to recreate the fresh, unused lab stations.

Follow the steps below to build the student lab pod networks:
1. Create all 15 lab pod networks with their assigned devices.

b. Choose Organization > CONFIGURE > Inventory.

c. Search for three serial numbers (one for the Cisco Meraki MX, one for Cisco Meraki MS, and one for Cisco
Meraki MR) that are assigned to a single lab pod.
d. Add these devices into a new Lab[n] network by performing the following steps:

Select the checkbox left to the three devices noted above.


Click Add to... at the top of the table and choose New network from the drop-down list.

Set Name to Lab[n] (for example, lab pod 1 would be named: Lab1) and Configuration to Use
defaults.
Click Create network and add.
e. Repeat the above steps for all 15 student lab pods, each with their respective Cisco Meraki MX, Cisco
Meraki MS, and Cisco Meraki MR devices properly assigned.

6. Create all 15 lab pod Cisco Meraki Systems Manager networks.

g. Choose Organization > CONFIGURE > Create network.


h. Set Network name to LAB[n] - SM (for example, lab pod 1 would be named: Lab1 - SM).
i. Set Network type to EMM (Systems Manager).
j. Scroll down and click Create network.
k. Repeat the above steps for all 15 SM lab pod networks.

12. Combine the 15 lab pod networks together with their matching Cisco Meraki Systems Manager lab networks.

m. Choose Organization > MONITOR > Overview.


n. Select the checkbox next to LAB[1] and LAB[1] - SM.
o. Click Combine at the top of the table.

p. Repeat the above steps for all 15 lab pods.

Part 4: Reconfigure Backbone Networks for ECMS1


To convert the ECMS2 lab infrastructure back to the ECMS1 lab environment, you must make some configuration
to the ISP Distribution and SF Data Center backbone networks.

Follow the steps below to make the necessary configuration modifications to convert the ECMS2 lab to the ECMS1
lab:
1. Reconfigure the ISP Distribution network.

b. Select the ISP Distribution Switches network from the network drop down list.
c. Choose Switch > MONITOR > Switches.

d. Click the WAN 1 switch.


e. From the device details page, click the Configure ports on this switch link.
f. Check the check boxes next to ports 25 through 39 (15 ports total) and click Edit.
g. Change the Port enabled to Enabled.

h. Click Update.

9. Reconfigure the SF Data Center network.

j. Select the SF Data Center network from the network drop-down list.
k. Choose Security & SD-WAN > CONFIGURE > Addressing & VLANs.

Set Mode to Passthrough or VPN Concentrator.


Click Save to commit the changes.

l. Navigate to Security & SD-WAN > CONFIGURE > Site-to-site VPN.

Set Type to Hub.

In the VPN settings Local networks table, verify that the DC Shared and SF DC - DC 1 networks are
listed. If they are not listed, please refer your ECMS1 Course Administration Guide to verify that they
were created during the lab environment setup process.

m. Click Save to commit the changes.

Part 5: Remove and Modify Lab Accounts Privileges


The final step is to remove the permissions to the ADMIN-PARK network that was temporarily granted to the lab
accounts and to modify the privilege level for the shared Cameras network. This is to ensure that a participant will
only have access and see the allowed networks (their own LAB[n] network and the shared Cameras network).

Follow the steps below to make the necessary modifications to the lab user accounts:
1. Choose Organization > CONFIGURE > Administrators.
2. Click the row of the first lab pod user account to open the Update administrator window.
3. Change the Access level of the Cameras network from Read-only to Full.
4. Click X in the ADMIN-PARK network row to remove this access privilege.

5. Click Update admin.


6. Repeat the above process to modify the remaining 14 lab pod user accounts.
7. Click the Save changes at the bottom of the screen to complete the process and commit the permission
changes to all 15 lab pod user accounts.

© 2024 Cisco y/o sus filiales. Todos los derechos reservados. Contenido impreso de g.pereira

You might also like