Cisco CCNA Cyber Ops: Pod Installation and Configuration Guide
Cisco CCNA Cyber Ops: Pod Installation and Configuration Guide
Cisco CCNA Cyber Ops: Pod Installation and Configuration Guide
NETLAB Academy Edition, NETLAB Professional Edition, NETLAB Virtual Edition, and NETLAB+ are registered trademarks of Network
Development Group, Inc.
VMware is a registered trademark of VMware, Inc. Cisco, IOS, Cisco IOS, Networking Academy, CCNA, and CCNP are registered
trademarks of Cisco Systems, Inc.
Cisco CCNA Cyber Ops Pod Installation and Configuration Guide
Contents
1 Introduction ................................................................................................................ 3
1.1 Introducing the Cisco CCNA Cyber Ops Pod......................................................... 3
2 Planning....................................................................................................................... 4
2.1 Pod Resource Requirements ................................................................................ 4
2.2 ESXi Host Server Requirements............................................................................ 5
2.3 NETLAB+ Requirements ....................................................................................... 5
2.4 NETLAB+ Virtual Machine Infrastructure Setup................................................... 5
2.4.1 Software Requirements ................................................................................ 6
2.5 Networking Requirements ................................................................................... 6
3 Software and Licenses ................................................................................................ 7
3.1 Obtaining Windows Software Licenses ................................................................ 7
3.2 Obtaining Cisco Networking Academy Access ..................................................... 8
3.3 Downloading OVF Files......................................................................................... 8
4 Master Pod Configuration........................................................................................... 9
4.1 Deploying Virtual Machine OVF/OVA Files .......................................................... 9
4.1.1 Modify Virtual Machines............................................................................. 13
4.2 NETLAB+ Virtual Machine Inventory Setup........................................................ 14
4.3 Building the Master Cisco CCNA Cyber Ops Pod ................................................ 16
4.3.1 Enabling Cisco CCNA Cyber Ops in Course Manager .................................. 16
4.3.2 Create the Master Pod ................................................................................ 16
4.3.3 Assign Virtual Machines to the Master Pod ............................................... 17
4.3.4 Snapshot the Virtual Machine .................................................................... 18
4.3.5 Set the Revert to Snapshot ......................................................................... 21
4.3.6 Bring the Master Pod online ....................................................................... 22
4.4 Create Class and Schedule the Master Pod ....................................................... 22
4.5 Make changes to the Master Pod ...................................................................... 22
4.5.1 Virtual Machine Credentials ....................................................................... 23
4.5.2 Provide Temporary Internet Access to the WinClient ................................ 23
4.5.3 License and Activate the WinClient ............................................................ 23
4.5.4 Shut down WinClient .................................................................................. 24
4.5.5 Reset the NIC to SAFETY NET ...................................................................... 24
4.5.6 Create Snapshot on the Changed Master Virtual Machines ...................... 25
4.5.7 End Reservation .......................................................................................... 25
5 Pod Cloning ............................................................................................................... 26
5.1 Linked Clones and Full Clones ............................................................................ 26
5.2 Creating User Pods ............................................................................................. 26
5.3 Copying Your Master Pod to the Second Host ................................................... 28
5.4 Creating User Pods on the Second Host ............................................................ 29
5.5 Assigning Pods to Students, Teams, or Classes .................................................. 29
1 Introduction
The Cisco CCNA Cyber Ops pod is a 100% virtual machine pod consisting of five virtual
machines. Linked together through virtual networking, these five virtual machines
provide the environment for a student or a team to perform the Cisco CCNA Cyber Ops
labs.
2 Planning
This guide provides specific information pertinent to delivering the Cisco CCNA Cyber
Ops Administration pod. The NETLAB+ Remote PC Guide Series provides the
prerequisite guidance for setting up your VMware infrastructure, including:
This document assumes that you have set up virtual machine infrastructure in
accordance with the NETLAB+ Remote PC Guide Series. The planning information
below refers to specific sections in the Remote PC Guide when applicable.
The Cisco CCNA Cyber Ops course will consume 37.1 GB of storage per each master
pod instance.
The following table provides details of the storage requirements for each of the virtual
machines in the pod.
Please refer to the NDG website for specific ESXi host requirements to support virtual
machine delivery: http://www.netdevgroup.com/content/vmita/requirements/
For current ESXi server requirements and active pod count, refer to the following
URL:
http://www.netdevgroup.com/support/remote_pc.html#vm_host_server_specificati
ons.
Installation of Cisco CCNA Cyber Ops pods, as described in this guide, requires that your
NETLAB+ system is equipped with NETLAB+ VE version 17.3.11 or later.
Previous versions of NETLAB+ do not support requirements for the Cisco CCNA
Cyber Ops course on the physical host servers.
For the purpose of software licensing, each virtual machine is treated as an individual
machine, PC or server. Please refer to the specific vendor license agreements (and
educational discount programs, if applicable) to determine licensing requirements for
your virtual machines’ software, operating system and applications.
The minimum virtual infrastructure software required for standing up this pod is in the
following table.
Please refer to the Software and Licenses section regarding the software requirements
for virtual machines in pod.
To accommodate the movement of large VMs, OVF/OVAs, and ISO disk images from one
host to another, gigabit Ethernet or better connectivity is recommended to interconnect
your NETLAB+, vCenter Server system and ESXi host systems.
The two standard networking models recommended to interconnect your servers are
described in detail in the Networking Models section of the Remote PC Guide Series,
Volume 1 - Introduction and Planning.
The following table lists the software that is required for the virtual machines inside the
Cisco CCNA Cyber Ops pod. Your organization needs to be a member of the vendor
programs listed in the Source column to obtain and use the licenses.
To enable all features of the Windows-based virtual machines, licensing will be required,
followed through with activations for the master virtual machines only. This needs to be
done before cloning.
There are two options for institutions to access Microsoft licenses. The first option is
through the Visual Studio Subscription Portal. The second option is by accessing your
institution’s Kivuto WebStore via Microsoft Imagine.
For more information about Visual Studio Subscriptions, you may visit
their FAQ page: https://www.visualstudio.com/my/myvsfaq.
Please note that activating licenses is only required on master pods. Doing a Link Clone
of the master pod will preserve the activation on the cloned VMs in the user pods. It is
important to note that when activating Windows, that the VMs have temporary Internet
access so that they can contact Microsoft Licensing Servers. There are multiple ways of
providing temporary Internet access for VMs in a vSphere environment. The most
common way is to temporarily assign the vNIC of the desired VM to connect to the
virtual switch that is connected to an outside facing physical NIC.
To obtain access to the Cisco CCNA Cyber Ops labs, your institution must be a Cisco
Networking Academy member.
You can find information about the Cisco Networking Academy at the following
link: https://www.netacad.com/get-started/educators/.
The virtual machines are made available as Open Virtualization Format (OVF) or Open
Virtualization Archive (OVA) files. These files are available for download from CSSIA.
Deploy on your host server the pod virtual machine OVF/OVA files you have
downloaded.
3. Right-click on the target ESXi Host Server and select Deploy OVF Template.
4. In the Deploy OVF Template window, on the Select source section, select the
Local File radio button and click Browse.
5. Locate and select one of the VMs for the pod, click Open.
Only one VM can be selected using this wizard. The process will have to
be repeated for the remaining VMs.
6. Verify that the VM file path and name appears next to the Browse button and
click Next.
7. In the Review details section, make sure to fill the checkbox for Accept extra
configuration options (if present) and click Next.
8. In the Select name and folder section, change the name of the virtual machine to
something that is easy to manage. You can use the names provided in the list
below as names for the virtual machines if you do not have a set naming
convention. Select the appropriate datacenter and click Next.
9. In the Select Storage section, choose the appropriate storage device and make
sure that Thin Provision is selected. Click Next.
10. In the Setup networks section, select SAFETY NET as the destination and click
Next.
11. In the Ready to complete section, make sure Power on after deployment is
unchecked and confirm the settings. Click Finish.
12. vCenter will begin deploying the virtual machine. This may take some time
depending on the speed of your connection, HDDs, etc. Repeat the previous
steps for each remaining virtual machine in the master pod.
Once the virtual machines are imported onto the host, verify the configurations. The
following steps will guide you through the process.
1. In the vSphere Web Client interface, right-click on the imported virtual machine
and select Edit Settings.
2. For all the virtual machines manually assign the MAC addresses for each NIC.
The table below identifies the MAC addresses per NIC.
3. Repeat the previous steps for each of the remaining virtual machines in the
master pod.
This section will guide you in adding your templates to the Virtual Machine Inventory of
your NETLAB+ VE system.
4. Click the Import Virtual Machines button located at the bottom of the list.
5. Select the appropriate datacenter from the list where your master VMs reside.
6. Select the check box next to the virtual machines you had just deployed and click
Import Selected Virtual Machines.
7. When the Configure VMs window loads, you can set your virtual machine
parameters.
a. Check the drop-down box for the correct operating system for each
imported virtual machine.
b. Change Role to Master for each VM.
c. Add any comments for each virtual machine in the last column.
It is advised to leave the Version and Build numbers for reference when
requesting NDG support.
d. Verify your settings and click Import (X) Virtual Machines (notice the
number in parenthesis is dynamic, depending on the amount of VMs
selected).
e. Verify all Import Statuses report back with OK and then click on the
Dismiss button.
f. Verify that your virtual machines show up in the inventory.
This section will assist you in adding the Cisco CCNA Cyber Ops pod to your NETLAB+
system.
Please refer to the Course Manager section of the NETLAB+ VE Administrator Guide on
how to enable content. Please install the Cisco CCNA Cyber Ops course.
3. Create a new pod by scrolling to the bottom and clicking the Create New Pod
button.
4. Then click on the Cisco CCNA Cyber Ops pod entry from the list of installed pod
types.
5. On the New Pod window, input a value into the Pod ID and Pod Name fields.
Click Next.
The Pod ID determines the order in which the pods will appear in the
scheduler. It is best practice to use a block of sequential ID numbers
for the Pod Id that allows for the number of pods you are going to
install.
The Pod Name identifies the pod and is unique per pod. Here we used
the name of the lab set or course in a shortened form along with a host
identifier (H120), the type and number of the pod (M1000).
Update the master pod to associate the virtual machines with the newly created pod.
1. To assign virtual machines to the master pod on your NETLAB+ system, select the
Pods icon.
2. Select the Cisco CCNA Cyber Ops master pod from the pod list.
3. Click on the Action dropdown next to the virtual machine you are about to
assign and select Attach VM.
1. In the pod list, click on the Cisco CCNA Cyber Ops master pod you just assigned
machines to.
2. In the pod view, click on a virtual machine in the list to view the properties of
that machine in NETLAB+. You will need to do this for each of the virtual
machines in the list.
3. In the pod virtual machine view, click on the Snapshots button to open the
Snapshot Manager.
4. In the Snapshot Manager window, click on the Take button. This will take a
snapshot of the current state of the virtual machine.
Any changes made after this will require a new snapshot or those
changes will not reflect in the reset state of the pod or its clones.
5. In the Take Snapshot window, type GOLDEN_MASTER in the Name field then click
the OK button.
6. In the Snapshot Manager window, notice the snapshot is created. Click the
Dismiss button.
At this point it is good to verify that you have only one snapshot on the
virtual machine. Multiple snapshots increase the likelihood of having
problems, especially if the snapshots are named the same.
6. Click the Dismiss button to return to the pod view page and repeat the previous
steps for the remaining virtual machines.
1. In the pod view, click on a virtual machine in the list to view the properties of
that machine in NETLAB+. You will need to do this for each of the virtual
machines in the list.
2. In the pod virtual machine view, click on the Settings button.
3. In the virtual machine’s Settings window, click on the Revert to Snapshot drop
box and select GOLDEN_MASTER then click the Submit button.
This sets the snapshot on the virtual machine that will get reverted to
each time the pod is scheduled.
4. Click OK to confirm.
5. Click the Dismiss button to return to the pod view page and repeat the previous
steps for the remaining virtual machines.
In the pod view, click the drop arrow under State and select Online.
Create a class as identified in Add Classes section of the NETLAB+ VE Instructor Guide
then schedule the Master Pod to license the WinClient machine.
Some pods have software that needs to be altered on the host machine before it can be
used properly. This normally happens when software requires licenses to function.
If there are changes that need to be made to the master pod prior to link cloning either
student pods or full cloning other master pods on other hosts, you will need to follow
this set of instructions to ready your master pod.
For the Cisco CCNA Cyber Ops master pod you will need to license the WinClient
machine. This process consists of:
• Scheduling the master pod
• Providing temporary internet access to the WinClient machine
• Licensing/Activating the WinClient
• Shutting down the WinClient only
• If necessary, resetting the network interface cards to SAFETY NET
• Taking a new GOLDEN_MASTER snapshot for WinClient
• Ending the reservation
For your reference, the following table provides a list of the credentials for the systems
in the pod:
1. Outside the NETLAB+ interface, navigate to your vSphere Web Client using your
management workstation, and then connect to your vCenter Server.
2. From the vSphere Web Client dashboard, select Hosts and Clusters.
1. Log on to the WinClient machine in the pod. If necessary, click the drop-down
arrow and select Send CTRL+ALT+DEL.
2. Log in as Administrator with cyberops as the password.
3. Once logged in, make sure the IP/TCP settings are temporarily configured
correctly so that the Internet is reachable. This can vary depending on how your
environment is set up.
4. Right-click on the Start menu and select System.
1. Outside the NETLAB+ interface, navigate to your vSphere Web Client using your
management workstation, and then connect to your vCenter Server.
2. From the vSphere Web Client dashboard, select Hosts and Clusters.
2. Click Delete to delete the current snapshot. Remember the name of this
snapshot as the new snapshot will need to have the exact same name.
3. Click Yes on the Confirm Delete window.
4. Click Close on the Manage Snapshots window.
5. Right-click on the Client virtual machine and select Snapshots-> Take Snapshot…
5 Pod Cloning
This section will help you create multiple student pods. The following sections describe
the NETLAB+ pod cloning feature used to create student pods on one or two host
systems.
A linked clone (or linked virtual machine) is a virtual machine that shares virtual disks
with the parent (or master) virtual machine in an ongoing manner. This conserves disk
space, and allows multiple virtual machines to use the same software installation.
Linked clones can be created very quickly because most of the disk is shared with the
parent VM.
A full clone is an independent copy of a virtual machine that shares nothing with the
parent virtual machine after the cloning operation. Ongoing operation of a full clone is
entirely separate from the parent virtual machine.
The following section describes how to create user pods on the same VMware Host
system that holds your master pod's virtual machines. In this scenario, we will create
linked virtual machines using the NETLAB+ pod cloning utility.
6. Input a new ID value into the New Pod ID field. It is advised to keep the pods in
numerical order. If the pod IDs are not in numerical order, they will not show up
in the scheduler in numerical order. Click Next.
7. Enter a name for the cloned pod into the New Pod Name field. For example,
Cisco_CCNA_CyberOps_Pod1. Click Next.
8. When the action has finished processing, you are presented with a settings
screen. Notice each VM has its own tab. Go through each tab and verify the
following:
9. When you are done changing settings, click Clone Pod. This should complete
within a minute as we are creating linked virtual machines.
The user pod can now be reserved. When the reservation becomes active, NETLAB+ will
automatically configure virtual machines and virtual networking for your new pod.
For this task, we will use the pod cloning utility to copy our master pod to the second
host.
6. Input a new ID value into the New Pod ID field. It is advised to keep the pods in
numerical order. If the pod IDs are not in numerical order, they will not show up
in the scheduler in numerical order. Click Next.
7. Enter a name for the cloned pod into the New Pod Name field. For example,
Cisco_CCNA_CyberOps_Master2. Click Next.
8. When the action has finished processing, you are presented with a settings
screen. Notice each VM has its own tab. Go through each tab and verify the
following:
9. When you are done changing settings, click Clone Pod. This may take up to 30
minutes as full copies are being made. You may navigate away from the cloning
progress screen, and then later return to the pod to check progress.
To create user pods on the second host, repeat the steps to create user pods on the first
host (see Creating User Pods), substituting the second master pod (created in the
previous section) as the cloning source.
Please refer to the NETLAB+ VE Instructor Guide for details on using the Pod ACLs
feature.