0

Setting up a Basic Network

Introduction

Hi guys, welcome to our very first lab.

In this tutorial, we are going to set up a basic network that comprises of two switches and two windows 7 machines on Eve-ng. As you all know, EVE-NG stands for Emulated Virtual Environment – Next Generation. Am using the Community Edition version that is free and can be downloaded as a VM (Ova file) or an ISO image at eve-ng’s website.

N.B This lab is for the very beginners who intend to kick start their Networking journey

Pre-requisites:

You will need:

  • 2 Layer 2 Access Switch Image (In all my labs am using IOU L2 images emulating Cisco’s Switches unless stated otherwise)
  • 2 Windows 7 Machines. (You can check how to build and add Windows and other images in eve-ng here)

That’s it guys. Without further ado, let’s jump straight into setting up our first network.

Once you have powered your EVE vm, you can login with the default credentials which is admin and eve. You can decide to change the credentials later on.

You will be presented with the below screen. In my set up I created a folder called “Blog”. You can do the same through clicking the green button labled “Add Folder”.

The next step is to Add a new lab through clicking the icon on the left near the edit icon.

Once that is done, you will be presented with a new pop up as below

Enter the details as above and click save.

Your new lab will be added and saved and an empty workspace will appear.

Its now time to add your nodes and connect them together.

Right click inside the window, or simply click the plus button on the top of the left menu to add a node(s)

Chose Cisco IOL.

You can chose the image to be layer 2 since we are going to use an Access Layer switch. The basic device settings are as follows:

  • Number of Nodes – 2
  • Name – SW
  • RAM – 256MB (You do not need a lot of RAM as the switch will be used for a basic network setup)
  • NVRAM – 128KB (This number is more than enough for saving the Switch’s basic configurations.)
  • Ethernet portgroups – 1×4
  • Serial portgroups – 0
  • Everything else can remain the same.

The Switches will appear as below.

We can then add our Windows 7 machines by right clicking inside the workspace again and adding a node. We shall add 2 of them.

We have all our devices ready. We can now connect them and build the topology then finally we are going to configure basic device settings on the switches such as banner and hostname etc as well as assign IP addresses on the windows 7 machines for them to communicate with each another.

Connect the two switches

Connect the Windows 7 machines to the switches.

Once all that is done. You can power on all the devices from the left panel menu.

Click “Start all nodes”

Once you power them, they will all appear blue. The image below shows the running nodes. It is essential that you label your topology before beginning any configurations.

We are going to configure basic switch settings before assigning IP addresses to our windows machines.

We will begin with Switch 1 (SW1)

Configure the hostname as follows:

In Cisco IOS CLI, there are 16 privilege levels beginning from 0 – 16

Once you are connected to the switch using a console cable, you go into the user exec mode when you type enable  you jump into privilege exec mode then finally when you type configure terminalyou jump into global configuration mode. This has the highest privileges which you can use to configure a Cisco device. Generally, Network Administrators and Engineers put passwords in place to prevent unauthorized access into the network device.

Next, we are going to configure a banner to our switch to inform/warn users of unauthorized access to this device.

We shall configure the banner as follows.

Since we are already into the Global configuration mode, we will continue with our banner configuration from there.

Cisco IOS CLI allows you to type a ‘?’ and it will give you the list of commands that you want to use as well as the options that are available with that command. Here we chose motd which is message of the day banner for our device and we set it as below.

Once you have completed all your configurations, you can type end or exit to go back to privilege exec mode.

After that you can save your configuration as below.

The same configuration can be used on SW2. You can test your knowledge and configure the second switch. The difference will be the hostname. In future, different switches will have different configurations but you will notice that there are basic configurations that are required before fully deploying a switch in your network.

To save the configuration, type inside the privilege exec mode the below command;

ALS-SW-I# copy running-config startup-config

Essentially we are copying the current running configuration to the startup configuration.

We can then save these configuration to our NVRAM by typing the below command;

ALS-SW-I# write

Next, we are going to assign our Windows 7 machines static IP addresses as below.

For PC-A connecting to ALS-SW-I (SW1) we set its IP as 192.168.1.10

And PC-B connecting to ALS-SW-II (SW2) we set its IP as 192.168.1.20

Remember that, we do not need a default gateway at the moment. This is very basic and we want reachability between PC-A and PC-B

Here is an example from PC-A

PC-B

From PC-A we are able to ping PC-B at 192.168.1.20

You can verify as per below.

As you can see, we are able to ping PC-B from PC-A

N.B It is not mandatory to configure the basic Switch settings as this does not play a role in ensuring reachability between the two Windows machines. We just did a basic touch on configuring a basic hostname and banner for a switch. There’s an entire article on configuring router and switch settings that include console passwords, ssh, and much more.

So, that’s it.

That’s a very basic network that we have just built.

bl4ckwidow

Co-Founder of Labing Overload. I am a Web Developer/Network Engineer turned CyberSecurity Engineer. FOSS enthusiast. Cisco Technologies enthusiast. Network Penetration Tester.

Leave a Reply

Your email address will not be published. Required fields are marked *