ccs372 Vir Manual

CONTENTS
Ex. No. Experiment Name
Create type 2 virtualization in VMWARE or any equivalent

1
Open Source Tool.
shrink virtual hard disks in Hyper-V and How to compact
2
virtual hard disks in Hyper-V
3 Create RAID 5 volume
4 Desktop Virtualization using VNC
5 Desktop Virtualization using Chrome remote Desktop
6 Create type 2 virtualization on ESXI 6.5 server
7 Create a VLAN in CISCO packet tracer
8 Install KVM in Linux
9 Create Nested Virtual Machine(VM under another VM)
1
Ex No : 1 Install Operating System Like Linux Using Date:
Date: VMware.
AIM:
How to install operating system like linux using vmware.
Steps:
1. Click Create a New Virtual Machine

2. Select the default option, Installer disc image file (iso)
3. Click Browse to find the ISO file
4. With "guest" OS selected, click Next
2
5. Select Linux as the Guest operating system type
3
6. Under Version, scroll through the list and select the OS
7. Click Next to proceed and if necessary, input a Virtual machine name
8. Confirm the storage Location and change if needed
With the operating system selected and configured, it's time to build the virtual machine.
1. Under Specify Disk Capacity adjust Maximum disk size if required (the default should be enough)
2. Select Split virtual disk into multiple files as this makes moving the VM to a new PC easy
3. Click Next then confirm the details on the next screen
4. If anything seems wrong click Back, otherwise click Finish
4
Result:
Thus we have install operating system like linux using vmware.
5
6
Ex No-2 Shrink Virtual Hard Disks In Hyper-V
Date:
Aim:
In Hyper-V environment, you can shrink, convert, expand, merge, reconnect or compact a
virtual hard disk by editing the corresponding file using either the GUI or CLI tools.
Steps:
1. In Hyper-V Manager, connect to the VM
2. After logging into the VM, launch the Disk Management utility by typing msc in the
search bar.
7
3. Right-click the disk volume you would like to shrink, and select the Shrink Volume
option
.
8
4. The next step is to enter the amount of space you wish to shrink in MB.
As you fill out this property, the Total size after shrink in MB value will change
automatically, thus showing you what the disk storage capacity will be after the shrink
operation is complete.
9
5. Click Shrink to start shrinking the disk volume. As a result, you will have roughly 25
GB of unallocated disk space.
6. After that, shut down the VM.
10
7. In Hyper-V Manager, right-click the VM and select Settings.
11
8. In the Hardware section, click Hard Drive to get access to the virtual hard disk settings.
Select Edit to launch the Edit Virtual Hard Disk Wizard.
12
9. You can skip the Locate Disk step, as you have already selected which disk you would
like to shrink. Click Next.
13
10. In the Choose Action section, select Shrink and click Next.
14
11. The next step is to configure the new size of the virtual hard disk.
As you may notice, the difference between the current disk size and the minimum size is equal to
the amount of extra disk space we have previously created inside the VM.
15
12. In the Summary section, you can look through the changes you are about to implement.
Click Finish to complete the action and close the wizard.
16
13. Click Inspect to verify that the disk size has actually changed and you have successfully
shrunk the virtual hard disk.
Result:
As you can see, the maximum disk size has been successfully reduced
17
Ex No-2 Create RAID 5 Volume
Date:
Aim:
In Hyper-V environment, Create RAID 5 volume
Steps:
18
Following are the key points to remember for RAID level 5.
 Minimum 3 disks.
 Good performance ( as blocks are striped ).
 Good redundancy ( distributed parity ).
 Best cost effective option providing both performance and redundancy. Use this for DB that
is heavily read oriented. Write operations will be slow.
RAID LEVEL 10
Following are the key points to remember for RAID level 10.
 Minimum 4 disks.
 This is also called as “stripe of mirrors”
 Excellent redundancy ( as blocks are mirrored )
 Excellent performance ( as blocks are striped )
 If you can afford the dollar, this is the BEST option for any mission critical applications
(especially databases).
19
3 . A. Desktop Virtualization using VNC Introduction:
VNC or Virtual Network Computing is a platform-independent protocol that enables users to connect to a remote
computer system and use its resources from a Graphical User Interface (GUI).
It’s like remote controlling an application: the client computer’s keystrokes or mouse clicks are
transmitted over the network to the remote computer. VNC also allows clipboard sharing between both
computers. If you come from a Microsoft Windows server background, VNC is much like the Remote
Desktop Service, except it’s also available for OS X, Linux, and other operating systems.
Like everything else in the networking world, VNC is based on the client server model: VNC server runs
on a remote computer — your Droplet — which serves incoming client requests.
Goals:
In this tutorial we will learn how to install and configure a VNC server on CentOS
7. We will install the TigerVNC server which is freely available from the TigerVNC GitHub repository.
To demonstrate how VNC works, we will also install the GNOME desktop on your CentOS server. We
will create two user accounts and configure VNC access for them. We will then test their connectivity to
the remote desktop, and finally, learn how to secure the remote connection through an SSH tunnel.
The commands, packages, and files shown in this tutorial were tested on a minimal installation of
CentOS 7. We would recommend the following:
 Distro: CentOS 7, 64-bit

 Resource Requirements: A Droplet with 2 GB RAM
 To follow this tutorial, you should use a sudo user. To understand how sudo privileges work, you can
refer to this DigitalOcean tutorial
Warning: You should not run any commands, queries, or configurations from this tutorial
on a production Linux server. This could result in security issues and downtime.
Step 1 Creating Two User Accounts
First, we will create two user accounts. These accounts will remotely connect to our CentOS 7 server
from VNC clients.
 joevnc
20
 janevnc
Run the following command to add a user account for joevnc:
21
sudo useradd -c "User Joe Configured for VNC Access" joevnc
Then run the passwd command to change joevnc’s password:
sudo passwd joevnc
The output will ask us for new password. Once supplied, the account will be ready for login:
Changing password for user joevnc.

New password:
Retype new password:
passwd: all authentication tokens updated successfully.
Next, create an account for janevnc:
sudo useradd -c "User Jane Configured for VNC Access" janevnc
Step2: Installing GNOME Desktop
Now we will install GNOME desktop. GNOME is a collaborative effort: it’s a collection of free and
open source software that makes up a very popular desktop environment.
There are other desktop environments like KDE, but GNOME is more popular. Our VNC users will use
GNOME to interact with the server from its desktop:
sudo yum groupinstall -y "GNOME Desktop"
Depending on the speed of your network, this can take a few minutes. Once the package group is
installed, reboot the server:
sudo reboot
Troubleshooting –Server Stuck at boot Phase
Depending on how your server has been set up, when the machine starts up it may remain in the boot
22
phase showing a message like this:
Initial setup of CentOS Linux 7 (core)

1) [!] License information (Licence not accepted)
Please make your choice from above ['q' to quit | 'c' to continue |
'r' to refresh]:
23
To get past this, press 1 (license read), then 2 (accept licence), and then C (to continue). You may have
to press C two or more times. The image below shows this:
If you don’t see this error and the boot process is smooth, all the better – you can move on to the next
step.
Step3:
TigerVNC is the software that will allow us to make a remote desktop connection. Install the Tiger VNC
server:
sudo yum install -y tigervnc-server
This should show output like the following:
Loaded plugins: fastestmirror, langpacks

Loading mirror speeds from cached hostfile
. . .
Running transaction
Installing : tigervnc-server-1.2.80-0.30.20130314svn5065.el7.x86_64
1/1
24
Verifying : tigervnc-server-1.2.80-0.30.20130314svn5065.el7.x86_64
1/1
Installed:
tigervnc-server.x86_64 0:1.2.80-0.30.20130314svn5065.el7
Complete!
Now we have VNC server and the GNOME desktop installed. We have also created two user accounts
for connecting through VNC.
Step4: Configuring VNC Service for Two Clients:
VNC server doesn’t start automatically when it’s first installed. To check this, run the
following command:
sudo systemctl status vncserver@:.service
The output will be like this:
vncserver@:.service - Remote desktop service (VNC)

Loaded: loaded (/usr/lib/systemd/system/[email protected]; disabled)
Active: inactive (dead)
You can also run this command:
udo systemctl is-enabled [email protected]
This should show output like this:
disabled
Note:
So why is it disabled? That’s because each user will start a separate instance of the VNC service
daemon. In other words, VNC doesn’t run as one single process that serves every user request.
Each user connecting via VNC will have to start a new instance of the daemon (or the system
25
administrator can automate this).
CentOS 7 uses the systemd daemon to initiate other services. Each service that natively runs
under systemd has a service unit file that’s placed under
the /lib/systemd/system directory by the yum installer. Processes that get started
automatically at boot time have a link to this service unit file placed in the
/etc/systemd/system/ directory.
26
In our case, a generic service unit file was created in
the /lib/systemd/system/ directory, but no link was made
under /etc/systemd/system/. To test this, run the following commands:
sudo ls -l /lib/systemd/system/vnc*
You should see:
-rw-r--r--. 1 root root 1744 Jun 10

16:15/lib/systemd/system/[email protected]
Then check under /etc/systemd/system/:
sudo ls -l /etc/systemd/system/*.wants/vnc*
This one doesn’t exist:
ls: cannot access /etc/systemd/system/*.wants/vnc*: No such file or

directory
So, the first step is to start two new instances of VNC server for our two users. To do this, we
will need to make two copies of the generic VNC service unit file under /etc/system/system.
In the code snippet below, you’re making two copies with two different names:
sudo cp /lib/systemd/system/[email protected]
/etc/systemd/system/vncserver@:4.service
sudo cp /lib/systemd/system/[email protected]
/etc/systemd/system/vncserver@:5.service
So why did we add two numbers (along with the colon) in the copied file names?
Again, that comes back to the concept of individual VNC services. VNC by itself runs on port 5900.
27
Since each user will run their own VNC server, each user will have to connect via a separate port. The
addition of a number in the file name tells VNC to run that service as a sub-port of 5900. So in our case,
joevnc’s VNC service will run on
port 5904 (5900 + 4) and janevnc’s will run on 5905 (5900 + 5).
Next edit the service unit file for each client. Open
the /etc/systemd/system/vncserver@:4.service file with the vi editor:
sudo vi /etc/systemd/system/vncserver@:4.service
28
A look at the “Quick HowTo” section tells us we have already completed the first step. Now we need to
go through the remaining steps. The comments also tell us that VNC is a non-trusted connection. We
will talk about this later.
For now, edit the [Service] section of the file, replacing instances
of <USER> with joevnc. Also, add the -geometry 1280x1024 clause at the end of
the ExecStart parameter. This just tells VNC the screen size it should start in. You will modify two
lines in total. Here’s what the edited file should look like (note that the entire file is not shown):
# The vncserver service unit file

#
# Quick HowTo:
# 1. Copy this file to /etc/systemd/system/vncserver@:<display>.service
# 2. Edit <USER> and vncserver parameters appropriately
# ("runuser -l <USER> -c /usr/bin/vncserver %i -arg1 -arg2")
# 3. Run `systemctl daemon-reload`
# 4. Run `systemctl enable vncserver@:<display>.service`
#
. . .
[Unit]
Description=Remote desktop service (VNC)
After=syslog.target network.target
[Service]
Type=forking
# Clean any existing files in /tmp/.X11-unix environment
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 ||
:'
ExecStart=/sbin/runuser -l joevnc -c "/usr/bin/vncserver %i -geometry
1280x1024"
PIDFile=/home/joevnc/.vnc/%H%i.pid
ExecStop=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'
[Install]
Save the file and exit vi.
29
Similarly, open the /etc/systemd/system/vncserver@:5.service file in vi and make the changes
for user janevnc:
sudo vi /etc/systemd/system/vncserver@:5.service
Here’s just the [Service] section with the changes marked:
[Service]
Type=forking
# Clean any existing files in /tmp/.X11-unix environment
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 ||
:'
ExecStart=/sbin/runuser -l janevnc -c "/usr/bin/vncserver %i -geometry
1280x1024"
PIDFile=/home/janevnc/.vnc/%H%i.pid
ExecStop=/bin/sh -c '/usr/bin/vncserver -kill %i > /dev/null 2>&1 || :'
Next, run the following commands to reload the systemd daemon and also to make sure VNC starts up
for two users at boot time.
sudo systemctl daemon-reload
Enable the first server instance:
sudo systemctl enable vncserver@:4.service
Output:
ln -s '/etc/systemd/system/vncserver@:4.service'
'/etc/systemd/system/multi-user.target.wants/vncserver@:4.service'
Enable the second server instance:
sudo systemctl enable vncserver@:5.service
Output:
ln -s '/etc/systemd/system/vncserver@:5.service'
'/etc/systemd/system/multi-user.target.wants/vncserver@:5.service'
30
Now you’ve configured two VNC server instances. Step 5: Configuring your firewall
31
Next, we will need to configure the firewall to allow VNC traffic through ports 5904 and 5905 only.
CentOS 7 uses Dynamic Firewall through
the firewalld daemon; the service doesn’t need to restart for changes to take effect.
The firewalld service should start automatically at system boot time, but it’s always good
to check:
sudo firewall-cmd --state
This should show:
running
If the state is “not running” for any reason, execute the following command to make sure
it’s running:
sudo systemctl start firewalld
Now add the rules for ports 5904 and 5905:
sudo firewall-cmd --permanent --zone=public --add-port=5904-5905/tcp
Output:
success
Reload the firewall:
sudo firewall-cmd --reload
Output:
success
Step6
32
Setting VNC Password
We are one step away from seeing VNC in action. In this step, the users will need to set their
VNC passwords. These are not the users’ Linux passwords, but the passwords to log in to the
VNC sessions.
Open another terminal connection to the CentOS 7 server, and this time log in as joevnc.
ssh joevnc@your_server_ip
33
Execute the following command:
vncserver
As shown in the output below, the server will ask joevnc to set up a VNC password. After
typing in the password, the program also shows a number of files being created in the user’s
home directory:
you will require a password to access your desktops.
Password:
Verify:
xauth: file /home/joevnc/.Xauthority does not exist
New 'localhost.localdomain:1 (joevnc)' desktop is localhost.localdomain:1
Creating default startup script /home/joevnc/.vnc/xstartup

Starting applications specified in /home/joevnc/.vnc/xstartup
Log file is /home/joevnc/.vnc/localhost.localdomain:1.log
Let’s look at the line New 'localhost.localdomain:1 (joevnc)' desktop is

localhost.localdomain:1. localhost.localdomain was the server name in our example; in your
case it could be different. Note the number after the server name: (1, separated by a colon). It’s not the
number in joevnc’s service unit file (which was 4). That’s because this is the display number
joevnc’s session will run on in this server, not the port number of the service (5904) itself.
Next open a new terminal session and log in as janevnc. Here as well, start the VNC server and set a
password for janevnc:
vncserver
You should see similar output showing that janevnc’s session will run on display 2. Finally, reload the
services from the main terminal session:
34
sudo systemctl daemon-reload
sudo systemctl restart vncserver@:4.service
sudo systemctl restart vncserver@:5.service
35
Ex.No 3 B.
Desktop Virtualization using Chrome remote Desktop Step1:

Connecting a Remote Desktops with a VNC client.
For this tutorial, we will assume users joevnc and janevnc are trying to connect to the CentOS
7 server from their Windows computers.
They will each need a VNC client for Windows to log into the remote desktop. This client is just
like a terminal client like PuTTY, except it shows graphical output. There are various VNC
client available, but the one we will use is RealVNC, available here. VNC Viewer for Mac OS X
is available for download on the same page, and the Mac version is fairly similar to the Windows
one.
When VNC Viewer is started, it shows a dialogue box like this:
In the VNC Server field, add the IP address of your CentOS 7 server. Specify the port number 5904
after the server’s IP, separate by a colon (:). We used 5904 because that’s the VNC service port for
joevnc.
We have also decided to let VNC Viewer choose the encryption method. This option will only encrypt
the password sent across the network. Any subsequent communication with the server will be
unencrypted. (We’ll set up a secure SSH tunnel in the final step.)
36
In fact, a warning message shows just that:
Accept the warning for now. A password prompt is displayed:
Enter joevnc’s VNC password that you set earlier.
37
A new window opens showing the GNOME desktop for our remote CentOS server:
38
Accept the default welcome message.
Now joevnc can start a graphical tool like the GNOME calculator:
39
40
You can leave this desktop connection open.
Now janevnc can also start another VNC session with the CentOS server. The IP address is the
same, and the port is 5905:
When janevnc logs in via VNC Viewer, an empty desktop with a welcome message is shown,
just like it was shown for joevnc. In other words, the two users are not sharing the desktop
instances. joevnc’s desktop should still be showing the calculator.
To close the remote desktop session, simply closing the window will do. However, this doesn’t
stop the user’s VNC service in the background on the server. If the service is not stopped or
restarted and the machine had no reboots, the same desktop session would be presented at the
next logon.
Close the VNC Viewer windows for joevnc and janevnc. Close their terminal sessions, too.
From the main terminal window, check to see if the VNC services are still running:
sudo systemctl status vncserver@:4.service
The output shows that the remote desktop is still running:
vncserver@:4.service - Remote desktop service (VNC)

Loaded: loaded (/etc/systemd/system/vncserver@:4.service; enabled)
Active: active (running) since Sat 2014-11-01 12:06:49 EST; 58min ago
Process: 2014 ExecStart=/sbin/runuser -l joevnc -c /usr/bin/vncserver %i
-geometry 1280x1024 (code=exited, status=0/SUCCESS)
. . . 41
Check the second service:
42
This one is running, too:

Loaded: loaded (/etc/systemd/system/vncserver@:5.service; enabled)
Active: active (running) since Sat 2014-11-01 12:42:56 EST; 22min ago
Process: 3748 ExecStart=/sbin/runuser -l janevnc -c /usr/bin/vncserver
%i -geometry 1280x1024 (code=exited, status=0/SUCCESS)
. . .
If you wanted to log back into joevnc’s desktop at this point, you’d see the same
calculator app open.
This presents some interesting challenges for system administrators. If you have a number of users
connecting to the server via VNC, you may want to devise some way to stop their VNC services when
no longer needed. This may save some valuable system resources.
Troubleshooting — VNC Service Crashes
As you test and play around with VNC, you may sometimes find the service has crashed and is
unrecoverable. When you try to check the status:

This long error message may come up:

Loaded: loaded (/etc/systemd/system/vncserver@:4.service;
enabled)
Active: failed (Result: exit-code) since Fri 2014-11-07 00:02:38
EST; 2min 20s ago
Process: 2221 ExecStart=/sbin/runuser -l joevnc -c
/usr/bin/vncserver %i -geometry 1280x1024 (code=exited, status=2)
Process: 1257 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i
> /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)
Trying to start the service doesn’t work:
sudo systemctl start vncserver@:4.service
43
Failed startup:
Job for vncserver@:4.service failed. See 'systemctl status

vncserver@:4.service' and 'journalctl -xn' for details.
Usually the reason is simple enough. Check /var/log/messages:
44
sudo tail /var/log/messages
The related error will look like this:
Nov 7 00:08:36 localhost runuser: Warning: localhost.localdomain:4

is taken because of /tmp/.X11-unix/X4
Nov 7 00:08:36 localhost runuser: Remove this file if there is no
X server localhost.localdomain:4
Nov 7 00:08:36 localhost runuser: A VNC server is already running
as :4
Nov 7 00:08:36 localhost systemd: vncserver@:4.service: control
process exited, code=exited status=2
Nov 7 00:08:36 localhost systemd: Failed to start Remote desktop
service (VNC).
Nov 7 00:08:36 localhost systemd: Unit vncserver@:4.service
entered failed state.
Nov 7 00:08:36 localhost systemd: Failed to mark scope session-
The remedy is to delete the file under /tmp folder:
sudo rm -i /tmp/.X11-unix/X4
Output:
rm: remove socket ‘/tmp/.X11-unix/X4’? y
Then start the VNC service:
sudo systemctl start vncserver@:4.service
General Troubleshooting
Although relatively rare, you may encounter other errors when working with VNC. For example,
your remote desktop screen can go blank or hang, the session might crash with a cryptic error
message, VNC Viewer may not connect properly or transmit commands to the GUI to launch
45
applications, etc.
We recommend checking the /var/log/messages file to get a better understanding. At times

you may need to reboot your server, or in extreme cases recreate the VNC service.
46
System resources can also be a culprit; you may have to add extra RAM to your Droplet, etc.
Step 2:
Securing VNC Sessions Through SSH Tunneling
So far both joevnc and janevnc have been accessing their remote desktops through
unencrypted channels. As we saw before, VNC Viewer warns us about this at connection time;
only the password is encrypted as the sessions begins. Any subsequent network traffic and data
transfer is open for anyone to intercept in the middle.
About SSH Tunnelling

This is where Secure Shell (SSH) sessions can help. With SSH, VNC can run within the context of an
SSH encrypted session. This is known as tunnelling. In effect, VNC traffic piggybacks on the SSH
protocol, resulting in all of its communication with the server being encrypted. It’s called tunnelling
because SSH is providing wraparound protection over VNC and VNC is running as if in a tunnel within
SSH. SSH tunnelling can be used for other protocols like POP, X, or IMAP as well.
SSH tunnelling works with port forwarding which is basically a means of translating access from one
particular port to a different port on another machine. With port forwarding, when a client application
connects to Port A running on machine A, it’s transparently forwarded to port B running on machine B.
The client application is unaware of this translation and thinks it’s connecting to the original port. Port
forwarding is one of the features of SSH protocol.
With port forwarding, we can set our local VNC client to connect to port 5900 on the local client
computer, and this can be mapped to port 5905 on the remote server. This is example is for janevnc’s
connection, but you could easily follow the same steps for any other clients.
When the VNC client application starts, it can be pointed to port 5900 on localhost, and our port
forwarding will transparently transport it to port 5905 on the remote server.
Note: You’ll have to start an SSH section each time to make the connection secure.
OS X
On your Mac, open Terminal.
Enter the following connection information, being sure to replace your_server_ip with your
remote server’s IP address:
47
ssh -L 5900:your_server_ip:5905 janevnc@your_server_ip -N Enter
janevnc’s UNIX password. The connection will appear to hang; you can keep it running for as long as
you use the remote desktop.
Now skip ahead to the VNC Viewer instructions.
48
Windows
For securing janevnc’s VNC session, we will assume the local Windows computer has
PuTTY installed. PuTTY is free and can be downloaded from here.
If janevnc’s VNC and terminal sessions are not closed already, close them now.
Start PuTTY. In the session screen, ensure you specify the server IP address and give a descriptive name
to the connection, then click the Save button to save the connection details. Note how we have specified
username@your_server_ip in the Hostname field:
Next, expand the SSH menu item in the left navigation pane, and select the X11 item. This shows the X11
forwarding properties for the session. Ensure the checkbox for Enable X11 forwarding is checked. This
ensures that SSH encrypts X Windows traffic that flows between the server and client:
49
Finally, select SSH > Tunnels. Type 5900 in the Source port field. In
the Destination field, specify your server’s name or IP address, followed by a colon and the
VNC port number for the intended user. In our case, we have specified your_server_ip:5905.
Alternately, you could use port 5902. The 2 in this case would be the display
number for janevnc (remember the message displayed when janevnc ran the vncserver
command).
Click the Add button and the mapping will be added under Forwarded ports.
This is where we are adding port forwarding for the SSH session; when the user connects to
localhost at port 5900, the connection will be automatically tunnelled through SSH to the remote
server’s port 5905.
50
Go back to the Sessions items and save the session for janevnc. Click the Open button and a new terminal
session will open for janevnc. Log in as janevnc with the appropriate UNIX password:
51
VNC Viewer
Next start VNC Viewer again. This time, in the VNC Server address, type <^> and let VNC server
choose the encryption method:
Click the Connect button.
You will still get the dialogue box warning you about an unencrypted session, but this time you can
safely ignore it. VNC Viewer doesn’t know about the port it’s being forwarded to (this was set in the
SSH session just started) and assumes you are trying to connect to the local machine.
Accepting this warning will show the familiar password prompt. Enter janevnc’s VNC
password to access the remote desktop.
So how do you know the session was encrypted? If you think about it, we had set port forwarding in the
52
SSH session. If an SSH session wasn’t established, port forwarding wouldn’t have worked. In fact, if you
close the terminal window and log out of the PuTTY
53
session then try to connect with VNC Viewer alone, a connection attempt to localhost:5900 would
show the following error message:
So, if the localhost:5900 connection works, you can be confident that the connection is
encrypted.
Remember that you will want to establish the SSH connection first every time you use VNC, to
make sure your connection is always encrypted.
Conclusion
Accessing your CentOS Linux system from a GUI front end can make system administration much
simpler. You can connect from any client operating system and don’t have to depend on web-based
hosting control panels. VNC has a much smaller footprint compared to most control panels.
Although we have shown how two ordinary users can connect with their VNC clients, that’s hardly
practical in serious production environments. In reality, users will have customized applications or
browsers for accessing the server. Running a number of VNC services for each user also creates an
unnecessary burden on system resources, not to mention the inherent risks associated with it.
If you decide to install and run VNC on your production Linux server, we strongly recommend using it
for administrative purposes only.
54
OR
3A&B
Important Terminology
Here are some key terms to remember when connecting with VNC
 VNC session password – this password is used only with VNC. This is not tied to your MCECS
login. Because the encryption on this password is extremely weak, do not use a password that you
want to keep private as your session password.
 Display Number – when you start a VNC session, it will be assigned a number between 1 and 99
that will identify it on the Linux system you are remotely connected to.
 Port Number – This is equal to your Display Number plus 5900. This number is used by the VNC
viewer software to remotely connect with the VNC session running on MCECS Linux systems.
 Host Address – this is the full domain name of the system you want to remotely connect with. This is
usually in the form of somecomputer.cs.pdx.edu, somecomputer.ece.pdx.edu, or
somecomputer.cecs.pdx.edu
Starting the VNC session
Step 1 – Opening a terminal
Open MobaXterm and click on the Start local terminal button, as highlighted in the image below.
55
Step 2 – Connecting to Linux system with SSH
In the command line, enter the following command
ssh your_username@host_name
Replace your_username with your MCECS username and replace host_name with the address of the
MCECS Linux machine or server you want to connect with (for example, mo.ece.pdx.edu or
rita.cecs.pdx.edu).
Enter your MCECS account password when prompted, and log in to the host system.
Step 3 – Starting VNC session process
Start a VNC session by entering the command vncserver
56
57
NOTE: If you see the following message after entering vncserver, this means you have a VNC
session already running on this system. Go to the end of this article for more information on how
to check for existing VNC sessions and also how to terminate them.
Step 4 – Creating VNC session password
You should now see a prompt to enter a password like in the image below. This will be your VNC session
password.
Be aware of the following:
 The session password needs to be at least 6 characters long.

 This password is only used to log in to your VNC session and is not tied to your MCECS account
password.
 This password is stored with very poor encryption, so it is advised that you do not use a sensitive
password for your VNC session password.
You will also be prompted to enter a view-only password, which can be used by other people to observe
your VNC session. If you are unsure about this feature, enter n for “no” and avoid creating one.
NOTE: It is possible you may not see a password prompt. If you have previously used VNC, the new process
58
will sometimes use your previous session password. If you have forgotten your previous session password,
run the command vncpasswd to change it.
59
Step 5 – Getting Display/Port numbers
Your VNC session has been created, and you should see a message similar to the sample output below
The number that appears after the host address is the display number (it is underlined in red in the
image above). By adding this number to 5900, this will give you the port number used to connect your
VNC viewer to the VNC session.
For example, if your display number is 4, your port number is 5904. If your display number is 12, your
port number is 5912.
NOTE: Your display number may not be the same as the sample image above. Make sure to
read the output message in your terminal and look for the number after the semicolon for your
true display number.
The VNC session is now running on the remote Linux host system and is ready to connect with your
VNC viewing software. You can exit and close this terminal if you want, as the VNC session will
continue to run in the background. Be aware that the CAT will kill any VNC session that has been idle
for more than 48 hours.
Connecting with your VNC session with MobaXterm’s

VNC viewer
Step 1 – Opening new VNC viewer session
60
In MobaXterm, click on the Session button in the upper left hand corner
61
Step 2 – VNC viewer setup
In the window that pops up, look for the VNC icon in the top row and click on it
 In the Remote hostname or IP address box, enter localhost

 In the Port box, enter your Port Number. Recall that this is 5900 plus the Display Number that
appeared after running the vncserver command
62
Step 3 – SSH Gateway setup
In the lower area, click on the Network Settings tab, and then click on the SSH gateway (jumphost)
button. The button is highlighted in the blue box in the image above.
In the window that pops up, enter the following
 In the Gateway host box, enter the address of the host machine that your VNC session is running on (e.g.
ada.cs.pdx.edu, mo.ece.pdx.edu, etc).
 In the Username box, enter your MCECS username.
 In Port, leave it set at 22
 Do not check off the box for Use SSH key.
Afterwards, click the OK button with the green checkmark to save these settings and close this
configuration window.
When you return to the previous menu, click the OK button again and connect MobaXterm’s VNC
Viewer with the remote VNC session
63
Step 4 – VNC password guide
When you see the following window asking for the password for MCECS username on the host address,
enter your MCECS login password. This window may or may not appear, depending on how recently you
used MobaXterm to view a VNC session previously.
When you see the following window asking for the password for localhost, enter your VNC session
password.
64
A new tab should now appear in MobaXterm with a Linux graphical interface. Congratulations! You are
now remotely connected with a Linux system via VNC.
65
Disconnecting vs. Terminating your VNC session
It is possible to disconnect from your VNC session and reconnect with it later on to pick up where you left
off. In MobaXterm, if you close the tab or click on the Disconnect button, your VNC session will not end and
will continue to run on the host system. To reconnect with your session, simply follow the instructions above
for Connecting with your VNC session with MobaXterm’s VNC viewer using the same session password
and port number as before.
Be aware that on CAT-supported systems, VNC sessions are terminated if they have been idle for more than
48 hours.
66
If you want to kill the VNC session, you can use the Log Off or Shutdown option in the Linux graphical
interface. The location of these options will vary depending on the version of Linux on the host system and
your personal settings.
Alternatively, you can kill VNC sessions using the command vncserver -kill :X, where X is
replaced with your session’s Display Number.
67
Checking for existing VNC sessions
If you want to check for existing VNC sessions or find its display number, run the command vncserver -list
If there is an existing session, you will see the following output
If there are no sessions running, you will see the following output
Changing your VNC password

If you want to change your VNC session password, run the command vncpasswd and follow the
prompts. The session password can be changed even if you have VNC currently running, allowing you to
use the new password even after starting a session.
68
Ex No:4
VMware 01 Dec
ESXi 6.5 2016
Network 145109
Server
VMware,
Inc.
YES CERTIFIED with the following products: Virtual Machines (Guests OS):
2 SUSE® Linux Enterprise Server 11 for AMD64 & Intel64
SP: Service Pack 4 for Arch: 64 Mode: Fully
SUSE SLES 11 Virtualized
2 SUSE® Linux Enterprise Server 11 for AMD64 & Intel64
SP: Service Pack 4 for A Mode: Fully Virtualized
SUSE SLES 11 r
c
h
:
3
2
p
a
e
Product Description
VMware ESXi is a complete, scalable and robust virtualization platform. Designed to
reduce capital and operation costs. Maximize IT efficiency while giving you agility
69
through automation and the freedom to choose applications, SUSE® Linux Enterprise OS
and hardware.
Tested Configuration:
Computer Type: Virtual Machine
Mother Intel 440 BX Desktop Reference Platform / Motherboard Rev B0
Board
Revision
:
BIOS/uEFI: BIOS: 6.00 (04/05/2016)
CPU: 8 Intel Xeon® Processor E7-8890 v2 2.80 GHz
RAM: Host platform: 6 TB, multiple 64-bit VM guests: 3000 GB, 32-bit
guests: 16 GB, single max VM guest: 6128 GB
Ports Serial Parallel Port
and Bus 3 PCI-ISA
Types: 4 32-Bit PCI
70
PCI Express X8
Video Adapter: VMware® VMware SVGA II
Host Bus Adapter: VMware® Paravirtual SCSI (PVSCSI) adapter ,
SCSI
VMware® Virtual IDE Device for SUSE Linux , IDE
Hard Disk Drive: VMware® Virtual Hard Disk rev:1.0 (SCSI) ,
SCSI
CD/DVD: VMware® Virtual IDE CDR10 , IDE
Test Kit: System Certification Kit 7.6.0-44.1
Config Notes
1. VMware recommends to install deployPkg with open-vm-tools if creating a
Template http://kb.vmware.com/kb/2075048.
2. Virtual machine guest: System certification testing was performed with a virtual
machine configured with up to 6128 GB of memory on a SLES 11 SP4 x86-64
guest.
3. Virtual machine guest: System certification testing was performed with a SLES 11
SP4 64-bit virtual machine configured with up to 128 CPUs.
4. VMware recommends using the Open VM Tools redistributed by the operating
system vendors. For additional information, see knowledge base article 2073803 at
http://kb.vmware.com/kb/2073803. VMware guest OS installation information can
be found at:http://partnerweb.vmware.com/GOSIG/SLE_11.html
5. The VMware Memory Ballooning driver included in SLES 11 SP4 is auto loaded
to improve the virtual machine memory performance.
71
Adapters and Drivers VMware® VMware SVGA II
Driver Type: Driver Name: vmware_drv.so
Video
Driver
Driver Date: 17-Jun- Driver Size: 5716
72
2015
Driver Version:
11.0.3 Driver
Driver Name: vmware_drv.so Driver Size: 10560
Type: Video
Driver
Driver Date: 17-
Jun- 2015
Driver Version:
11.0.3
VMware® VMXNET3 Ethernet Adapter
Driver Type:
Driver Name: vmxnet3.ko
LAN Driver
Driver Date:
Driver Size: 77407
24-Jun- 2015
Driver Version: 1.1.30.0-k
Driver Type:
Driver Name: vmxnet3.ko
LAN Driver
Driver Date:
Driver Size: 58587
24-Jun- 2015
VMware® Paravirtual SCSI (PVSCSI) adapter
Driver Type:
Driver Name: vmw_pvscsi.ko
HBA Driver
Driver Date:
Driver Size: 39527
24-Jun- 2015
73
Driver Type:
Driver Name: vmw_pvscsi.ko
HBA Driver
Driver Date:
Driver Size: 28699
24-Jun- 2015
VMware® Virtual IDE Device for SUSE Linux
Driver Type:
Driver Name: ata_piix.ko Driver Size: 51119
HBA Driver
Driver Date:
24-Jun- 2015
Driver
Version: 2.13
Driver Type: HBA Driver Name: ata_generic.ko
74
Driver
Driver Date: 24-
Driver Size: 13383
Jun- 2015
Driver Version:
0.2.15 Driver
Driver Name: ata_generic.ko Driver Size: 10087
Type: HBA
Driver
Driver Name: ata_piix.ko Driver Size: 39751
Driver Date: 24-
Jun- 2015
Driver Version:
0.2.15 Driver
Type: HBA
Driver
Driver Date: 24-
Jun- 2015
Driver Version:
2.13
The term YES CERTIFIED applies only to the exact configuration documented in
this bulletin. For more information on hardware exchange policies, please access the
following document and view the Hardware Component Exchange Guide.
Supported virtual installations and virtualization

products
75
You can install
Symantec Endpoint Protection
on the supported operating systems that run in virtual environments. Install Symantec Endpoint
Protection
on the guest operating system, and not the host. The following virtualization products support the
Symantec Endpoint Protection Manager
, console, and
client software for Windows and Linux:
 Microsoft Azure
 Amazon Web Service ( AWS) EC2
 Amazon WorkSpaces
76
 Citrix Studio Version 2009.0.0
 Nutanix AOS 5.15 (LTS)
 Oracle Cloud Infrastructure (OCI)
 VMware WS 5.0 (workstation) or later
 VMware GSX 3.2 (enterprise) or later
 VMware ESX 2.5 (workstation) or later
 VMware ESXi 4.1 - 5.5
 VMware ESXi 6.0
 VMware ESXi 6.0 Update 1
 VMware ESXi 6.0 Update 2
 VMware ESXi 6.0 Update 3 (As of 14.0.1)
 VMware ESXi 6.5 (As of 14.0.1)
 VMware ESXi 6.5U1 (As of 14.2)
 VMware ESXi 6.5U2 (As of 14.2)
 VMware ESXi 6.7 (As of 14.2)
 VMware ESXi 7.0 Update 2 (As of 14.3 RU2)
 Microsoft Virtual Server 2005
 Windows Server 2008 Hyper-V
 Windows Server 2008 R2 Hyper-V
 Windows Server 2012 Hyper-V
 Windows Server 2012 R2 Hyper-V
 Windows Server 2016 Hyper-V (As of 14.2 MP1)
 Windows Server 2019 Hyper-V Core Edition (As of 14.2 MP1)
 Citrix XenServer 5.6 or later
 Virtual Box, supplied by Oracle

includes many features that enhance performance in virtual environments.
77
78
79
80
OR
81
ddressing Table
82
Switch(S0,S1,S2)
83
84
85
86
87
88
Lab 5: Basic VLAN Configuration
Topology Diagram
Addressing Table
D
evic Interf IP Address Subnet Mask Default
e ace Gateway
(Hos
tnam
e)
S1 VLA 172.17.99.11 255.255.255.0 N/A

N 99
S2 VLA 172.17.99.12 255.255.255.0 N/A

N 99
S3 VLA 172.17.99.13 255.255.255.0 N/A

N 99
PC1 NIC 172.17.10.21 255.255.255.0 172.17.10.1
PC2 NIC 172.17.20.22 255.255.255.0 172.17.20.1
PC3 NIC 172.17.30.23 255.255.255.0 172.17.30.1
PC4 NIC 172.17.10.24 255.255.255.0 172.17.10.1
PC5 NIC 172.17.20.25 255.255.255.0 172.17.20.1
PC6 NIC 172.17.30.26 255.255.255.0 172.17.30.1

Initial Port Assignments (Switches 2 and 3)
Ports Assignment Network
Fa0/1 – 0/5 802.1q Trunks (Native VLAN 99) 172.17.99.0 /24
Fa0/6 – 0/10 VLAN 30 – Guest (Default) 172.17.30.0 /24
Fa0/11 – 0/17 VLAN 10 – Faculty/Staff 172.17.10.0 /24
Fa0/18 – 0/24 VLAN 20 – Students 172.17.20.0 /24

Page 1 of 13
Learning Objectives
All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Upon completion of this lab, you will be able to:
• Cable a network according to the topology diagram
• Erase the startup configuration and reload a switch to the default state
• Perform basic configuration tasks on a switch
• Create VLANs
• Assign switch ports to a VLAN
• Add, move, and change ports
• Verify VLAN configuration
• Enable trunking on inter-switch connections
• Verify trunk configuration
• Save the VLAN configuration
Task 1: Prepare the Network
Step 1: Cable a network that is similar to the one in the topology diagram.
You can use any current switch in your lab as long as it has the required interfaces shown in the topology.
Note: If you use 2900 or 2950 switches, the outputs may appear different. Also, certain commands may be different or
unavailable.
Step 2: Clear any existing configurations on the switches, and initialize all ports in the shutdown state.
If necessary, refer to Lab 2.5.1, Appendix 1, for the procedure to clear switch configurations.
It is a good practice to disable any unused ports on the switches by putting them in shutdown. Disable all ports on the
switches:
Switch#config term Switch(config)#interface range faO/1-24 Switch(config-if-

range)#shutdown
Switch(config-if-range)#interface range giO/1-2
Switch(config-if-range)#shutdown
Task 2: Perform Basic Switch Configurations
Step 1: Configure the switches according to the following guidelines.
• Configure the switch hostname.
• Disable DNS lookup.
• Configure an EXEC mode password of class.
• Configure a password of cisco for console connections.

• Configure a password of cisco for vty connections.
Step 2: Re-enable the user ports on S2 and S3.
S2(config)#interface range faO/6, faO/11, faO/18 S2(config-if-range)#switchport mode

access S2(config-if-range)#no shutdown
S3(config)#interface range faO/6, faO/11, faO/18 S3(config-if-range)#switchport mode

access S3(config-if-range)#no shutdown
All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 11
Task 3: Configure and Activate Ethernet Interfaces
Step 1: Configure the PCs.
You can complete this lab using only two PCs by simply changing the IP addressing for the two PCs specific to a test you
want to conduct. For example, if you want to test connectivity between PC1 and PC2, then configure the IP addresses for
those PCs by referring to the addressing table at the beginning of the lab.
Alternatively, you can configure all six PCs with the IP addresses and default gateways.
Task 4: Configure VLANs on the Switch
Step 1: Create VLANs on switch S1.
Use the vlan vlan-id command in global configuration mode to add a VLAN to switch S1. There are four VLANS
configured for this lab: VLAN 10 (faculty/staff); VLAN 20 (students); VLAN 30 (guest); and VLAN 99 (management). After
you create the VLAN, you will be in vlan configuration mode, where you can assign a name to the VLAN with the name
vlan name command.
S1(config)#vlan 1O
S1(config-vlan)#name faculty/staff
S1(config-vlan)#vlan 2O S1(config-vlan)#name students S1(config-vlan)#vlan 3O
S1(config-vlan)#name guest S1(config-vlan)#vlan 99 S1(config-vlan)#name management
S1(config-vlan)#end
S1#
Step 2: Verify that the VLANs have been created on S1.
Use the show vlan brief command to verify that the VLANs have been created.
S1#show vlan brief
VLAN Name Status Ports
1 default active FaO/1, FaO/2, FaO/4, FaO/5 FaO/6,

FaO/7, FaO/8, FaO/9
FaO/1O, FaO/11, FaO/12, FaO/13
FaO/14, FaO/15, FaO/16, FaO/17
FaO/18, FaO/19, FaO/2O, FaO/21
FaO/22, FaO/23, FaO/24, GiO/1 GiO/2
1 faculty/staff active
O
2 students active
O
3 guest active
O
9 management active
9
Step 3: Configure and name VLANs on switches S2 and S3.
Create and name VLANs 10, 20, 30, and 99 on S2 and S3 using the commands from Step 1. Verify the correct configuration
with the show vlan brief command.
What ports are currently assigned to the four VLANs you have created?
Step 4: Assign switch ports to VLANs on S2 and S3.
Refer to the port assignment table on page 1. Ports are assigned to VLANs in interface configuration mode, using the
switchport access vlan vlan-id command. You can assign each port individually or you can use the interface range
command to simplify this task, as shown here. The commands are shown for S3 only, but you should configure both S2 and
S3 similarly. Save your configuration when done.
S3(config)#interface range faO/6-1O

S3(config-if-range)#switchport access vlan 3O S3(config-if-range)#interface range
faO/11-17 S3(config-if-range)#switchport access vlan 1O S3(config-if-range)#interface
range faO/18-24 S3(config-if-range)#switchport access vlan 2O S3(config-if-range)#end
S3#copy running-config startup-config Destination filename [startup-config]? [enter]
Building configuration... [OK]
Step 5: Determine which ports have been added.
Use the show vlan id vlan-number command on S2 to see which ports are assigned to VLAN 10. Which ports are assigned
to VLAN 10?
Note: The show vlan name vlan-name displays the same output.
You can also view VLAN assignment information using the show interfaces interface switchport
command.
Step 6: Assign the management VLAN.
A management VLAN is any VLAN that you configure to access the management capabilities of a switch. VLAN 1 serves as
the management VLAN if you did not specifically define another VLAN. You assign the management VLAN an IP address
and subnet mask. A switch can be managed via HTTP, Telnet, SSH, or SNMP. Because the out-of-the-box configuration of a
Cisco switch has VLAN 1 as the default VLAN, VLAN 1 is a bad choice as the management VLAN. You do not want an
arbitrary user who is connecting to a switch to default to the management VLAN. Recall that you configured the management
VLAN as VLAN 99 earlier in this lab.
From interface configuration mode, use the ip address command to assign the management IP address to the switches.
S1(config)#interface vlan 99
S1(config-if)#ip address 172.17.99.11 255.255.255.O
S1(config-if)#no shutdown
Assigning a management address allows IP communication between the switches, and also allows any host connected to a
port assigned to VLAN 99 to connect to the switches. Because VLAN 99 is configured as the management VLAN, any ports
assigned to this VLAN are considered management ports and should be secured to control which devices can connect to these
ports.
Step 7: Configure trunking and the native VLAN for the trunking ports on all switches.
Trunks are connections between the switches that allow the switches to exchange information for all VLANS. By default, a
trunk port belongs to all VLANs, as opposed to an access port, which can only belong to a single VLAN. If the switch
supports both ISL and 802.1Q VLAN encapsulation, the trunks must specify which method is being used. Because the 2960
switch only supports 802.1Q trunking, it is not specified in this lab.
A native VLAN is assigned to an 802.1Q trunk port. In the topology, the native VLAN is VLAN 99. An 802.1Q trunk port
supports traffic coming from many VLANs (tagged traffic) as well as traffic that does not come from a VLAN (untagged
traffic). The 802.1Q trunk port places untagged traffic on the native VLAN. Untagged traffic is generated by a computer
attached to a switch port that is configured with the native
VLAN. One of the IEEE 802.1Q specifications for Native VLANs is to maintain backward compatibility with untagged
traffic common to legacy LAN scenarios. For the purposes of this lab, a native VLAN serves as a common identifier on
opposing ends of a trunk link. It is a best practice to use a VLAN other than VLAN 1 as the native VLAN.
Use the interface range command in global configuration mode to simplify configuring trunking.
S1(config)#interface range faO/1-5

S1(config-if-range)#switchport mode trunk
S1(config-if-range)#switchport trunk v 9
native l 9
S1(config-if-range)#no shutdown a
S1(config-if-range)#end n
S2(config)# interface range faO/1-5

S2(config-if-range)#switchport mode
trunk v 9
S2(config-if-range)#switchport trunk l 9
native a
n
S2(config-if-range)#no shutdown
S2(config-if-range)#end
S3(config)# interface range faO/1-5

S3(config-if-range)#switchport mode
trunk S3(config-if-range)#switchport v 9
trunk native l 9
a
n
S3(config-if-range)#no shutdown
S3(config-if-range)#end
Verify that the trunks have been configured with the show interface trunk command.
S1#show interface trunk
Po Mo Encapsul Statu Nativ

rt de ation s e
vlan
Fa on 8O2.1q trunk 99
O/ ing
1
Fa on 8O2.1q trunk 99
O/ ing
2
Port Vlans allowed on trunk FaO/1 1-4O94 FaO/2
1-4O94
Port Vlans allowed and active in management domain FaO/1 1,1O,2O,3O,99

FaO/2 1,1O,2O,3O,99
Port Vlans in spanning tree forwarding state and not pruned FaO/1
1,1O,2O,3O,99
FaO/2 1,1O,2O,3O,99
Step 8: Verify that the switches can communicate.
From S1, ping the management address on both S2 and S3.
S1#ping 172.17.99.12
Type escape sequence to abort.
Sending 5, 1OO-byte ICMP Echos to 172.17.99.12, timeout is 2 seconds:
!!!!!
Success rate is 1OO percent (5/5), round-trip min/avg/max = 1/2/9 ms
S1#ping 172.17.99.13
Type escape sequence to abort.
Sending 5, 1OO-byte ICMP Echos to 172.17.99.13, timeout is 2 seconds:
.!!!!
Success rate is 8O percent (4/5), round-trip min/avg/max = 1/1/1 ms
Step 9: Ping several hosts from PC2.
Ping from host PC2 to host PC1 (172.17.10.21). Is the ping attempt successful?
Ping from host PC2 to the switch VLAN 99 IP address 172.17.99.12. Is the ping attempt successful? Ping from host PC2 to
host PC5. Is the ping attempt successful?
Step 10: Move PC1 into the same VLAN as PC2.
The port connected to PC2 (S2 Fa0/18) is assigned to VLAN 20, and the port connected to PC1 (S2 Fa0/11) is assigned to
VLAN 10. Reassign the S2 Fa0/11 port to VLAN 20. You do not need to first remove a port from a VLAN to change its
VLAN membership. After you reassign a port to a new VLAN, that port is automatically removed from its previous VLAN.
S2#configure terminal
Enter configuration commands, one per line. End with CNTL/Z. S2(config)#interface
fastethernet O/11
S2(config-if)#switchport access vlan 2O
S2(config-if)#end
Ping from host PC2 to host PC1. Is the ping attempt successful?
Even though the ports used by PC1 and PC2 are in the same VLAN, they are still in different subnetworks, so they cannot
communicate directly.
Step 11: Change the IP address and network on PC1.
Change the IP address on PC1 to 172.17.20.22. The subnet mask and default gateway can remain the same. Once again, ping
from host PC2 to host PC1, using the newly assigned IP address.
Is the ping attempt successful? Why was this attempt successful?
Task 5: Document the Switch Configurations
On each switch, capture the running configuration to a text file and save it for future reference.
Task 6: Clean Up
Erase the configurations and reload the switches. Disconnect and store the cabling. For PC hosts that are normally connected
to other networks (such as the school LAN or to the Internet), reconnect the appropriate cabling and restore the TCP/IP
settings.
Final Switch Configurations

S1
hostname S1 !
enable secret class no ip domain-lookup
! interface FastEthernetO/1 switchport trunk native vlan 99 switchport mode trunk

!
interface FastEthernetO/4 switchport trunk native vlan 99 switchport mode trunk
! interface FastEthernetO/5 switchport trunk native vlan 99 switchport mode trunk !
interface FastEthernetO/6 shutdown
!
<all remaining FastEthernet and GigabitEthernet interface are shutdown>
!
interface Vlan1 no ip address no ip route-cache
! interface Vlan99
ip address 172.17.99.11 255.255.255.O no ip route-cache
! line con O exec- timeout O O password cisco logging synchronous login line vty O 4
exec-timeout O O password cisco logging synchronous login line vty 5 15 exec-timeout O O
password cisco logging synchronous login ! end
S2
hostname S2 !
enable secret class no ip domain-lookup
!
!
!
!
!

!
interface FastEthernetO/6 switchport access vlan 3O switchport mode access
!
interface FastEthernetO/7 switchport access vlan 3O switchport mode access shutdown
!
!
!
interface FastEthernetO/1O switchport access vlan 3O switchport mode access
shutdown
!
!
shutdown
!
shutdown
!
shutdown
!
shutdown
!
shutdown
!
shutdown
!
!

shutdown
!
interface FastEthernetO/2O switchport access vlan 2O switchport mode access
shutdown
!
shutdown
!
shutdown
!
shutdown
!
shutdown
! interface GigabitEthernetO/1 shutdown
!
interface GigabitEthernetO/2 shutdown
!
interface Vlan1 no ip address no ip route-cache shutdown
!
interface Vlan99 ip address 172.17.99.12 255.255.255.O no ip
route-cache ! ip http server ! control-plane
! !
line con O exec- timeout O O password cisco logging synchronous login line vty O 4
exec-timeout O O password cisco logging synchronous login
line vty 5 15 exec- timeout O O password cisco logging synchronous login ! ! end
S3 hostname S3 no ip domain-lookup enable secret class

!
!
!
!
!
!
!
interface FastEthernetO/7 switchport access vlan 3O
!
!
!
interface FastEthernetO/1O switchport access vlan 3O
!
!
!
!
!
!
!
!
!
!
interface FastEthernetO/2O switchport access vlan 2O
!
!
!
!
!
interface GigabitEthernetO/1
!
interface GigabitEthernetO/2
!
interface Vlan1 no ip address no ip route-cache shutdown
!
interface Vlan99 ip address 172.17.99.13 255.255.255.O no ip
route-cache
!
line con O password cisco login line vty O 4 password cisco login line
vty 5 15 password cisco login ! end
Experiment No. 6
1. Aim: Installation and Configuration of virtualization using KVM
2. Objectives: From this experiment, the student will be able to,

 Understand the concepts of virtualization.
 Understand KVM architecture and its configuration.
3. Outcomes: The learner will be able,
 To analyze user models and develop user centric interfaces
 To analyze the local and global impact of computing on individuals,

organizations, and society.
 To engage in life-long learning development and higher studies.
 To understand, identify, analyze and design the problem, implement and

validate the solution including both hardware and software.
4. Hardware / Software Required: Ubuntu operating system, open source software

KVM, Internet.
5. Theory: Virtualization is software that separates physical infrastructures to create

various dedicated resources. It is the fundamental technology that powers cloud
computing.
The technology behind virtualization is known as a virtual machine monitor
(VMM) or virtual manager, which separates compute environments from the
actual physical infrastructure.
Virtualization makes servers, workstations, storage and other systems
independent of the physical hardware layer. This is done by installing a
Hypervisor on top of the hardware layer, where the systems are then installed.
There are three areas of IT where virtualization is making headroads, network
virtualization, storage virtualization and server virtualization:
106
• Network virtualization is a method of combining the available resources
in a network by splitting up the available bandwidth into channels, each of
which is independent from the others, and each of which can be assigned (or
reassigned) to a particular server or device in real time. The idea is that
virtualization disguises the true complexity of the network by separating it into
manageable parts, much like your partitioned hard drive makes it easier to
manage your files.
• Storage virtualization is the pooling of physical storage from multiple
network storage devices into what appears to be a single storage device that
is
107
managed from a central console. Storage virtualization is commonly used in
storage area networks (SANs).
• Server virtualization is the masking of server resources (including
the number and identity of individual physical servers, processors, and
operating systems) from server users. The intention is to spare the user
from having to understand and manage complicated details of server resources
while increasing resource sharing and utilization and maintaining the capacity to
expand later. Virtualization can be viewed as part of an overall trend in
enterprise IT that includes autonomic computing, a scenario in which the IT
environment will be able to manage itself based on perceived activity, and
utility computing, in which computer processing power is seen as a utility
that clients can pay for only as needed. The usual goal of virtualization is to
centralize administrative tasks while improving scalability and work loads.
6. Procedure:
Installation Steps :
1. #sudo grep -c "svm\|vmx" /proc/cpuinfo
2. #sudo apt-get install qemu-kvm libvirt-bin bridge-utils virt-manager
3. #sudoadduserrait #sudoadduserraitlibvirtd
After running this command, log out and log back in as rait
4. Run following command after logging back in as rait and you should see
an empty list of virtual machines. This indicates that everything is working correctly.
#virsh -c qemu:///system list
5. Open Virtual Machine Manager application and Create Virtual Machine #virt-
manager
7. Result:
SNAPSHOTS
108
Step 1 : #sudo grep -c "svm\|vmx" /proc/cpuinfo
109
Step 2 : #sudo apt-get install qemu-kvm libvirt-bin bridge-utils virt-manager
Step 3 : #sudoadduserrait
Step 4 : #sudoadduserraitlibvirtd
110
Step 5 : Open Virtual Machine Manager application and Create Virtual Machine #virt-
manager as shown below
Step 6 : Create a new virtual machine as shown below
111
Step 7 : Install windows operating system on virtual machine
112
Step 8: Installation of windows on virtual machine
Step 9: Installation of windows 7 on virtual machine
113
Step 10: Initialization of windows on virtual machine
8. Conclusion:
Installation and configuration of KVM have been done successfully onto Ubantu and
users added. Like this we can create as many virtual machines as possible on OS and
can install any windows onto it
9. Viva Questions:
 What is virtualization ?
114
 What is the benefit of desktop virtualization?
 What are the different virtual machines available?
115
10. References:
1. Enterprise Cloud Computing by Gautam Shroff, Cambridge,2010

2. Cloud Security by Ronald Krutz and Russell Dean Vines, Wiley - India, 2010
ISBN:978-0-470-58987-8
3. Getting Started with OwnCloud by Aditya Patawar , Packt Publishing Ltd, 2013
116
Ex No:7 Create Nested Virtual Machine(VM under another VM) Aim:
Enable Nested Virtualization
How to Set Up Hyper-V Nested Virtualization [Step-by-Step]
1. Creating A NAT-Enabled Virtual Switch.

2. Creating the First-Level Guest Virtual Machine. ...
3. Enabling Nested Virtualization.
4. Installing The Guest Operating System.
5. Connecting To The Network.
6. Installing Hyper-V On The First-Level Virtual Machine.
7. Conclusion.
Enable Nested Virtualization in

Windows 10 Hyper-V
Hyper-V is the built-in hypervisor that comes free in Windows and Windows Server. It is used
to run on Windows. Virtualization is also used for other features, like Virtualization-
Based Security (VBS), Windows Sandbox, and Windows Defender Application Guard
(WDAG). Developers sometimes use virtualization with Visual Studio to run device emulators.
Microsoft introduced support for nested virtualization in Windows Server 2016. Nested
virtualization lets you turn on . So, you can think of it like a VM running inside a VM.
There are a few prerequisites that you need to meet before you can use nested virtualization.
The VM configuration must be version 8.0 or higher. And nested virtualization is only
supported on Intel CPUs with virtualization (VT-x) and Extended Page Tables (EPT).
117
Stop-VM -Name 'Windows 11'
118
119
120

ccs372 Vir Manual

Uploaded by

Copyright:

Available Formats

ccs372 Vir Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ccs372 Vir Manual

Uploaded by

Copyright:

Available Formats

CONTENTS

Ex. No. Experiment Name

Create type 2 virtualization in VMWARE or any equivalent

3 Create RAID 5 volume

4 Desktop Virtualization using VNC

5 Desktop Virtualization using Chrome remote Desktop

6 Create type 2 virtualization on ESXI 6.5 server

7 Create a VLAN in CISCO packet tracer

8 Install KVM in Linux

9 Create Nested Virtual Machine(VM under another VM)

How to install operating system like linux using vmware.

1. Click Create a New Virtual Machine

4. With "guest" OS selected, click Next

6. After that, shut down the VM.

Select Edit to launch the Edit Virtual Hard Disk Wizard.

 Distro: CentOS 7, 64-bit

Step 1 Creating Two User Accounts

Then run the passwd command to change joevnc’s password:

sudo passwd joevnc

Changing password for user joevnc.

Next, create an account for janevnc:

sudo useradd -c "User Jane Configured for VNC Access" janevnc

Step2: Installing GNOME Desktop

sudo yum groupinstall -y "GNOME Desktop"

Troubleshooting –Server Stuck at boot Phase

Initial setup of CentOS Linux 7 (core)

sudo yum install -y tigervnc-server

This should show output like the following:

Loaded plugins: fastestmirror, langpacks

Step4: Configuring VNC Service for Two Clients:

sudo systemctl status vncserver@:.service

The output will be like this:

vncserver@:.service - Remote desktop service (VNC)

You can also run this command:

udo systemctl is-enabled [email protected]

This should show output like this:

You should see:

-rw-r--r--. 1 root root 1744 Jun 10

Then check under /etc/systemd/system/:

This one doesn’t exist:

ls: cannot access /etc/systemd/system/*.wants/vnc*: No such file or

# The vncserver service unit file

Save the file and exit vi.

Here’s just the [Service] section with the changes marked:

sudo systemctl daemon-reload

Enable the first server instance:

sudo systemctl enable vncserver@:4.service

Enable the second server instance:

sudo systemctl enable vncserver@:5.service

sudo firewall-cmd --state

This should show:

sudo systemctl start firewalld

Now add the rules for ports 5904 and 5905:

sudo firewall-cmd --permanent --zone=public --add-port=5904-5905/tcp

Reload the firewall:

sudo firewall-cmd --reload

you will require a password to access your desktops.

New 'localhost.localdomain:1 (joevnc)' desktop is localhost.localdomain:1

Creating default startup script /home/joevnc/.vnc/xstartup

ls: cannot access /etc/systemd/system/.wants/vnc: No such file or