- In a previous video, which
I've linked here and below, I showed you how to
download and install EVE-NG. I showed you how to get a basic
topology working in EVE-NG. Now that's fine but for
most of us we wanna add more complex nodes than just a VPCS. By default I can add a
VPCS device to EVE-NG, but what happens if I
wanna add another type of device such as a Cisco router? So as an example Cisco vIOS, which gives me a router image
that I can run in EVE-NG. Now in this video I'm gonna
show you how to do that. I'm gonna show you how to download Cisco IOS images from cisco.com, and show you how to get a Cisco topology working within EVE-NG. Now there's quite a few steps here, there's quite a few things
that you need to do, but if you follow along, you'll be able to get a Cisco topology working in EVE-NG. Now before we get started
please would you subscribe to my YouTube channel, please
would you Like this video if you find it useful, and please click on the
bell to get notifications when I upload a new video. Okay, so let's get started. ♪ Because we both deserved it all ♪ (upbeat music) Now the first thing I'm gonna
do is go to virl.cisco.com so that I can download
images to use in EVE-NG. Now you can find Cisco VIRL
images on the Internet. I'm not a lawyer but all I can say is it's probably not such a
good idea to use those. In my example I'm gonna get
images from Cisco's website because I already have an account. I'm gonna enter my email
address, click next, specify my password, then click sign in. I'm gonna go to my account and I'm gonna click Download VIRL. Now to download images
click on all releases, click one, scroll down
to IOSv as an example, click on the download link, click accept license agreement, and as you can see Cisco vIOS, which is our routing image, is being downloaded. I'm also gonna download IOSv Layer-2. So select that image, accept
the license agreement, and the image is now downloaded. Now as always it makes sense
to read the documentation. On the EVE-NG website,
documentation, how to's. We're told how to upload images to EVE-NG. There's a How To page share
of how to add Cisco IOS images, so VIRL images to EVE-NG. Now I want to point out something really important with regards
to the Cisco images. The Cisco IOSv image is a VMDK image, notice VMDK in the name That's important because a VMDK image is uploaded differently then a QCOW2 image. The IOSv Layer-2 image is a QCOW2 image, ends in QCOW2. So the process for uploading a QCOW2 image once again is gonna be
different to a VMDK image. ASAv as an example is a QCOW2 image. IOS XRv QCOW2. CSR 1000 V QCOW2. So again just take note of the image type because that changes the
way that we upload the image to EVE-NG. Versions in this guide
are based on these images, which are different to the
images that I've downloaded from Cisco's website, so we'll adjust the guide
based on the file names that I've downloaded versus
what they're showing here. Now here's an important
thing to take note of, there's an EVE-NG image name, and then there's the original image name. What's important to note here is vIOS, hyphen or dash, and here we've got vIOS L2-, whereas the downloaded image
has this underscore in it. That's also true for the
image that I've downloaded. vIOS underscore L2 is the name used here. So we need to adjust the file name based on what's in this guide. And they've actually got a table where they explain the naming. There's a Qemu folder name, Vendor, and then the QCOW2 image name. If I scroll down, and I'll look for Cisco, we've got vIOS- and vIOS L2 so this is the router image, this is the switch image from Cisco. Notice also here we've got the Qemu image QCOW2 name. That becomes important when
we go through this process. Again, I'm going to show you
step by step how to do this, this is probably the hardest
part about getting this set up, but if you follow these
steps it's not too difficult. We are actually told here
that VIRL has 2 image formats, A VMDK and QCOW2. QCOW2 is almost ready to be used. Process is very simple, I'm
gonna show you that in a moment. VMDK requires a few more steps. We have to do some conversions, but again I'm going to show
you all the steps in a moment. So in this document we
have steps for VMDK files, and then when I scroll down we've got separate steps for QCOW2 images. So you need to follow the steps for the specific image that you've downloaded. Have you downloaded a VMDK image or have you downloaded a QCOW2 image? I'm going to start now with a vIOS, because vIOS is a VMDK file. So again here, the vIOS, the routing image is VMDK, whereas the iOS V Layer-2
image is at QCOW2 file. All I'm going to do here
again is follow the steps in this document, and
you'll see that it'll work. I'm gonna download WinSCP, which allows us to upload files to EVE-NG. You could use FileZilla if you like, but I'd recommend that
you use WinSCP on Windows rather than FileZilla. Some people have had
problems with FileZilla, but it's really up to you actually, but I'd recommend this software. So I'm gonna download the software. In this example I'm
using a Windows laptop, so WinSCP works here. If you're using a Mac, you
may need to use FileZilla. Okay, so the software has downloaded. I'm gonna install it. And basically just stick
with all of the defaults, and click finish. Now back in the documentation, we need to create a folder within EVE-NG So on the EVE-NG server,
I'm gonna log in as root, and EVE, I'll zoom in here, because this is quite difficult to read, but basically if I go to opt LS, notice some files and folders exist there, what we're gonna do is make a directory. Now doing it through the console of VMware is perhaps not the easiest way to do it, so what I'll do is simply download Putty. That'll make things easier. So I'm just going to
download 64-bit Putty, and then start that up. And I'm gonna SSH to my server. This is the EVE-NG server. So I have config and I'll
push that to more actually. Shows me that the IP address
of the server is 192.168.1.200. So I'm gonna SSH to the server, accept the key, I'm gonna log in as root, and the password is Eve. So that's a lot easier
to see what's going on. PWD shows me where I am. I'll go to opt again. LS dash L shows me the files here. Back on the EVE-NG website
we need to create this folder and this name needs to
match the router image. So what I'll do is copy this into notepad. And the file name that I need
to use is this file name, so this is the name of the
file that's been downloaded from Cisco's website, this is vIOS, that's the name that we're gonna use. So I'll copy that into Putty, and press enter. So LS dash L, there's our unet lab, so cd unet lab, LS - L. We need to go to add-ons, LS -L Qemu CD Qemu LS. There's the folder that
we've just created. Now for all the Linux people, so that I don't get into trouble you could obviously just do it this way. So from the home directory as an example, just jump directly into that directory. But first step is we've
created this folder, and now we need to upload
the downloaded image into that folder using WinSCP. So I'm gonna use secure
File Transfer Protocol, specify the server, specify my username which
is root and password of Eve, and click Log in. Accept the keys. I'm gonna go to my downloads directory, select this file. What I need to do is go to this
directory so I'll copy that, and then paste that here. So that's where I am now. I'll upload this image. So back in Putty, if I go to vIOS, and I press tab there, LS, and I'll say LS dash L, notice this file is being uploaded. So the file has been uploaded to EVE-NG, you can see that here. So we've uploaded the image. Next step is from the Eve CLI, go to the newly created folder, and that's actually where I am. Now this is quite big so
I'll reduce the size slightly so that it's more readable. Okay, so there we are. So I'll clear the screen. So we're in this directory currently, and now we're told to
rename the original image to have VMDK as an extension at the end. So, LS shows us the file, move allows us to move the file. I press tab there, so type VI, press tab and then add VMDK at the end. So LS now shows us our file
with the VMDK extension. Next step is to convert the VMDK to QCOW. So we've got to use this command. So I'll copy the command, and to make it easier
to see what I'm doing, I'm simply following these instructions, so here's the command that I've copied, and I'm gonna simply do
that with the file name, so they say, change it to this at the end. That once again comes from the table, if I go back to their table. Notice this is the name that we using, so I'm gonna paste that in, and that will convert the image. LS shows us that there. Next step is to delete
the raw MDK image file. So I mean I suppose you
could just move that to a different directory if you wanted to, but I'll remove that image
per the instructions. So LS shows me that that image
now exists in this folder. We then need to fix the permissions, so I'm gonna copy this, clear the screen just make it easier, paste that command in, that's been done, and there's our file once again. So what I did there was prepare and load VMDK images from VIRL. You could do something
similar for QCOW2 images. So as an example notice
this vIOS Layer-2 image is a QCOW2 image. So I'm gonna copy the name
so that I've got the name. We need to make this directory. So I'm going to paste that into Notepad without the QCOW2 extension. So paste it in like this. The extension name, however,
has to be vIOS Layer-2. Once again going back to
their naming convention, this is the name of the folder. So I need to have vIOS Layer-2, and then the name that I'm gonna be using. So I'm gonna copy that. In this example I'm currently
in my home directory, but I'm gonna simply
paste that command in, per their instructions, and then I'm going to upload
the image using WinSCP. So, I have this directory for vIOS I'm gonna upload that image
to the vIOS directory. I'm gonna go to that folder,
so I'll copy this command. Paste that into Putty,
LS shows me that I've got two directories here, I'll go to the vIOS Layer-2 directory. There's the QCOW2 file. What I need to do is
change the name to this based on their table. Once again that table is shown
at the bottom of this page. So what I'll do here is clear the screen. So once again that's the
file, so MV for move, vIOS, press tab, and then I'll simply copy this to make sure I didn't make any mistakes, and paste that in. LS shows us the file. Here it is. And then I'm gonna fix the permissions, so copy that and paste that in. That's now been done. So that's probably the hardest piece. I'm gonna go back to the EVE-NG GUI. Login is admin with password Eve, use the html5 console, and click login. And what I'm going to do now
is add a node to the topology, and hopefully we should
see that these are blue, which they are because I
now have images available. So I'll select vIOS. In this example I'll add
two nodes to the topology. You can specify a whole
bunch of options here, I'll leave everything at
default and click save. So I've got two routers
added to the topology now, and what I'll do is add another node, in this case I'll add a switch. So vIOS Layer-2, I'll just
simply add one switch, and click save. What I'll do is connect the router gigabit zero zero two gigabit zero one on the switch and click save, and then I'll connect to the
switch to the second router, so gigabit zero two two zero
zero on the second router, click save. So what I'll do is start
up the first router, it started, I'll click on the
router to open up a console. You can see the routers booting up, I'll click on the switch,
start itm click on it again. Console is opened. There's my switch booting up. I just moved the tabs around, so there's the router, there's the switch. I'll click on the second
router, start it up, click on it again to get a console, or move that console across. These are fairly big devices,
they take a while to boot up, that once again depends
on how much RAM and CPU you've allocated to your server. I haven't allocated that much here, it's running on this laptop once again. But as you can see the switch
interfaces are coming up, the routers are still booting. Okay, so here's my first
router, I'll say no to bypass the initial
configuration dialog. Switch has booted up as well. I've got a prompt on the switch. Second router is still booting. On the first router press
return to get started, so I'll press enter a few times. While we're waiting for that, let's go back to the switch, type enable, type conf t, interface vLAN 1, no shut this, I'll give it an IP address
of 10.1.1. let's say 252, and no shut interface vlan1, give it a host name of,
let's say, switch 1, So ping, and notice these
are just browser tabs, so I can detach them and simply
have it available over here. So I could, as an example,
have my different devices detached and running
in different browsers, so there's router one, here's router 2, I'll put it
here, put router one here, and here's my switch,
put it in the middle. Now I've zoomed in quite a lot here, so we don't have a lot of space, but ping 10.1.1.252, switch can ping itself. On the router give it a
host name of Router 1, show IP interface brief, interfaces on the router are shut down, so I'll go into interface gigabit
two zero zero, no shut it. IP address 10.1.1.253 as an example. So show IP interface brief. We can see this interface has come up up. On the switch, show IP interface brief. All the interfaces are up. Now in later releases of EVE-NG, it'll have the ability to dynamically know if an interface is up or down. Here it's showing all interfaces up, even though there are no cables connected, but that changes in later releases. Now you may hear my fan
going crazy on that laptop, it's because I'm doing recordings and I'm running multiple devices. Now I'm pinging an
address that doesn't exist in my topology so let's try that again. Ping 10.1.1.252, now that is the switch, so I'm pinging the switch at the moment. Let's get the second
router up and running. I'll bypass the startup config. The moral of the story is the more RAM and CPU you can allocate the better. So this is struggling a little
bit on this little laptop, but let's go back to the switch, can the switch ping the first router? Yes it can, can it telnet to the router? Connection is refused, so
show run type begin vty, I need to do some changes
on the VT wire line, such as allowing traffic in. So line vty 0 4, login
password cisco transport, input all, create and enable password of cisco, and what I'll do is
save the configurations. I went fairly quickly there, but this is basic CCNA knowledge. Notice I can now telnet to
the router from the switch. If you're struggling with these basics, please have a look at my CCNA
courses or other courses that explain the basics of
device configuration. Here I'll configure router
2 of the host name of R2, go on to the gigabit interface
it's a 0 0, no shut it. IP address 10.1.1.254. In this case, hopefully that should be able
to ping the first router now. So 253. Which it can, and hopefully it'll be
able to ping the switch, which it can. So I'll exit out of the router, back on the console of the switch, here is my first router, save
the configuration switch, save the configuration. And second router, save the configuration. Let's do some CDP, show CDP neighbors, and this might be confusing
so I'll just maximize this. What you'll notice is the
router is connected to gigabit zero one. Router 2 is connected to gigabit zero two on the local switch. Show IP interface brief. No device is connected
to gigabit zero zero. The two routers are connected to these two interfaces on the switch. And that's per the
topology that I created. Now you could get these PC's
to connect to the topology, so I'll delete that connection. In EVE-NG Community Edition, you can't live connect
devices, so I'd have to shut these devices down
and then connect them, so I won't bother doing that here, just for the sake of time. But as always on Cisco devices
make sure that you save your config, and then you
can shut down the topology. Okay, so that was quite a detailed video showing you how to get Cisco IOS V, and iOS V Layer-2 VIRL
images working in EVE-NG. That's probably the hardest part about it is uploading those images,
getting the directories right. Once you're used to the process
it's not that difficult, but there you go I've
shown you how to do that for both iOS V and iOS V Layer-2. Okay, so hopefully that's helped you. If you found this video useful, please will you subscribe
to my YouTube channel, please would you like this video, and please click on the
bell to get notifications when I post a new video. [Upbeat Music]
