Day 26
This commit is contained in:
Michael Cade
parent
a06a2c0ca4
commit
1677511e6e
BIN
Days/Images/Day26_Networking1.png
Normal file
BIN
Days/Images/Day26_Networking1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 51 KiB |
BIN
Days/Images/Day26_Networking2.png
Normal file
BIN
Days/Images/Day26_Networking2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 57 KiB |
BIN
Days/Images/Day26_Networking3.png
Normal file
BIN
Days/Images/Day26_Networking3.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 46 KiB |
BIN
Days/Images/Day26_Networking4.png
Normal file
BIN
Days/Images/Day26_Networking4.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 40 KiB |
BIN
Days/Images/Day26_Networking5.png
Normal file
BIN
Days/Images/Day26_Networking5.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
BIN
Days/Images/Day26_Networking6.png
Normal file
BIN
Days/Images/Day26_Networking6.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 12 KiB |
BIN
Days/Images/Day26_Networking7.png
Normal file
BIN
Days/Images/Day26_Networking7.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 56 KiB |
BIN
Days/Images/Day26_Networking8.png
Normal file
BIN
Days/Images/Day26_Networking8.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 90 KiB |
53
Days/Networking/R1
Normal file
53
Days/Networking/R1
Normal file
@ -0,0 +1,53 @@
|
||||
enable
|
||||
configure terminal
|
||||
|
||||
hostname R1
|
||||
int gig0/0
|
||||
no shutdown
|
||||
ip add 10.10.88.110 255.255.255.0
|
||||
|
||||
aaa new-model
|
||||
aaa session-id unique
|
||||
aaa authentication login default local
|
||||
aaa authorization exec default local none
|
||||
|
||||
enable password access123
|
||||
username admin password access123
|
||||
no ip domain-lookup
|
||||
|
||||
lldp run
|
||||
|
||||
ip domain-name PythonTraining.net
|
||||
ip ssh version 2
|
||||
ip scp server enable
|
||||
crypto key generate rsa general-keys modulus 1024
|
||||
|
||||
snmp-server community public RW
|
||||
snmp-server trap link ietf
|
||||
snmp-server enable traps snmp linkdown linkup
|
||||
snmp-server enable traps syslog
|
||||
snmp-server manager
|
||||
|
||||
logging history debugging
|
||||
logging snmp-trap emergencies
|
||||
logging snmp-trap alerts
|
||||
logging snmp-trap critical
|
||||
logging snmp-trap errors
|
||||
logging snmp-trap warnings
|
||||
logging snmp-trap notifications
|
||||
logging snmp-trap informational
|
||||
logging snmp-trap debugging
|
||||
line con 0
|
||||
exec-timeout 0 0
|
||||
privilege level 15
|
||||
logging synchronous
|
||||
|
||||
line vty 0 15
|
||||
exec-timeout 0 0
|
||||
logging synchronous
|
||||
login local
|
||||
transport input all
|
||||
privilege level 15
|
||||
|
||||
do copy run start
|
||||
end
|
||||
57
Days/Networking/SW1
Normal file
57
Days/Networking/SW1
Normal file
@ -0,0 +1,57 @@
|
||||
enable
|
||||
configure terminal
|
||||
|
||||
hostname SW1
|
||||
|
||||
aaa new-model
|
||||
aaa session-id unique
|
||||
aaa authentication login default local
|
||||
aaa authorization exec default local none
|
||||
vtp mode transparent
|
||||
|
||||
int gig0/0
|
||||
no switchport
|
||||
no shut
|
||||
ip address 10.10.88.111 255.255.255.0
|
||||
|
||||
lldp run
|
||||
|
||||
enable password access123
|
||||
username admin password access123
|
||||
no ip domain-lookup
|
||||
|
||||
ip domain-name PythonTraining.net
|
||||
ip ssh version 2
|
||||
ip scp server enable
|
||||
crypto key generate rsa general-keys modulus 1024
|
||||
|
||||
snmp-server community public RW
|
||||
snmp-server trap link ietf
|
||||
snmp-server enable traps snmp linkdown linkup
|
||||
snmp-server enable traps syslog
|
||||
snmp-server manager
|
||||
|
||||
logging history debugging
|
||||
logging snmp-trap emergencies
|
||||
logging snmp-trap alerts
|
||||
logging snmp-trap critical
|
||||
logging snmp-trap errors
|
||||
logging snmp-trap warnings
|
||||
logging snmp-trap notifications
|
||||
logging snmp-trap informational
|
||||
logging snmp-trap debugging
|
||||
|
||||
line con 0
|
||||
exec-timeout 0 0
|
||||
privilege level 15
|
||||
logging synchronous
|
||||
|
||||
line vty 0 15
|
||||
exec-timeout 0 0
|
||||
logging synchronous
|
||||
login local
|
||||
transport input all
|
||||
privilege level 15
|
||||
|
||||
do copy run start
|
||||
end
|
||||
57
Days/Networking/SW2
Normal file
57
Days/Networking/SW2
Normal file
@ -0,0 +1,57 @@
|
||||
enable
|
||||
configure terminal
|
||||
|
||||
hostname SW2
|
||||
|
||||
aaa new-model
|
||||
aaa session-id unique
|
||||
aaa authentication login default local
|
||||
aaa authorization exec default local none
|
||||
vtp mode transparent
|
||||
|
||||
int gig0/0
|
||||
no switchport
|
||||
no shut
|
||||
ip address 10.10.88.112 255.255.255.0
|
||||
|
||||
lldp run
|
||||
|
||||
enable password access123
|
||||
username admin password access123
|
||||
no ip domain-lookup
|
||||
|
||||
ip domain-name PythonTraining.net
|
||||
ip ssh version 2
|
||||
ip scp server enable
|
||||
crypto key generate rsa general-keys modulus 1024
|
||||
|
||||
snmp-server community public RW
|
||||
snmp-server trap link ietf
|
||||
snmp-server enable traps snmp linkdown linkup
|
||||
snmp-server enable traps syslog
|
||||
snmp-server manager
|
||||
|
||||
logging history debugging
|
||||
logging snmp-trap emergencies
|
||||
logging snmp-trap alerts
|
||||
logging snmp-trap critical
|
||||
logging snmp-trap errors
|
||||
logging snmp-trap warnings
|
||||
logging snmp-trap notifications
|
||||
logging snmp-trap informational
|
||||
logging snmp-trap debugging
|
||||
|
||||
line con 0
|
||||
exec-timeout 0 0
|
||||
privilege level 15
|
||||
logging synchronous
|
||||
|
||||
line vty 0 15
|
||||
exec-timeout 0 0
|
||||
logging synchronous
|
||||
login local
|
||||
transport input all
|
||||
privilege level 15
|
||||
|
||||
do copy run start
|
||||
end
|
||||
57
Days/Networking/SW3
Normal file
57
Days/Networking/SW3
Normal file
@ -0,0 +1,57 @@
|
||||
enable
|
||||
configure terminal
|
||||
|
||||
hostname SW3
|
||||
|
||||
aaa new-model
|
||||
aaa session-id unique
|
||||
aaa authentication login default local
|
||||
aaa authorization exec default local none
|
||||
vtp mode transparent
|
||||
|
||||
int gig0/0
|
||||
no switchport
|
||||
no shut
|
||||
ip address 10.10.88.113 255.255.255.0
|
||||
|
||||
lldp run
|
||||
|
||||
enable password access123
|
||||
username admin password access123
|
||||
no ip domain-lookup
|
||||
|
||||
ip domain-name PythonTraining.net
|
||||
ip ssh version 2
|
||||
ip scp server enable
|
||||
crypto key generate rsa general-keys modulus 1024
|
||||
|
||||
snmp-server community public RW
|
||||
snmp-server trap link ietf
|
||||
snmp-server enable traps snmp linkdown linkup
|
||||
snmp-server enable traps syslog
|
||||
snmp-server manager
|
||||
|
||||
logging history debugging
|
||||
logging snmp-trap emergencies
|
||||
logging snmp-trap alerts
|
||||
logging snmp-trap critical
|
||||
logging snmp-trap errors
|
||||
logging snmp-trap warnings
|
||||
logging snmp-trap notifications
|
||||
logging snmp-trap informational
|
||||
logging snmp-trap debugging
|
||||
|
||||
line con 0
|
||||
exec-timeout 0 0
|
||||
privilege level 15
|
||||
logging synchronous
|
||||
|
||||
line vty 0 15
|
||||
exec-timeout 0 0
|
||||
logging synchronous
|
||||
login local
|
||||
transport input all
|
||||
privilege level 15
|
||||
|
||||
do copy run start
|
||||
end
|
||||
58
Days/Networking/SW4
Normal file
58
Days/Networking/SW4
Normal file
@ -0,0 +1,58 @@
|
||||
enable
|
||||
configure terminal
|
||||
|
||||
hostname SW4
|
||||
|
||||
aaa new-model
|
||||
aaa session-id unique
|
||||
aaa authentication login default local
|
||||
aaa authorization exec default local none
|
||||
vtp mode transparent
|
||||
vlan 10,20,30,40,50,60,70,80,90,100,200
|
||||
|
||||
int gig0/0
|
||||
no switchport
|
||||
no shut
|
||||
ip address 10.10.88.114 255.255.255.0
|
||||
|
||||
lldp run
|
||||
|
||||
enable password access123
|
||||
username admin password access123
|
||||
no ip domain-lookup
|
||||
|
||||
ip domain-name PythonTraining.net
|
||||
ip ssh version 2
|
||||
ip scp server enable
|
||||
crypto key generate rsa general-keys modulus 1024
|
||||
|
||||
snmp-server community public RW
|
||||
snmp-server trap link ietf
|
||||
snmp-server enable traps snmp linkdown linkup
|
||||
snmp-server enable traps syslog
|
||||
snmp-server manager
|
||||
|
||||
logging history debugging
|
||||
logging snmp-trap emergencies
|
||||
logging snmp-trap alerts
|
||||
logging snmp-trap critical
|
||||
logging snmp-trap errors
|
||||
logging snmp-trap warnings
|
||||
logging snmp-trap notifications
|
||||
logging snmp-trap informational
|
||||
logging snmp-trap debugging
|
||||
|
||||
line con 0
|
||||
exec-timeout 0 0
|
||||
privilege level 15
|
||||
logging synchronous
|
||||
|
||||
line vty 0 15
|
||||
exec-timeout 0 0
|
||||
logging synchronous
|
||||
login local
|
||||
transport input all
|
||||
privilege level 15
|
||||
|
||||
do copy run start
|
||||
end
|
||||
@ -2,7 +2,7 @@
|
||||
|
||||
Python is the standard language used for automated network operations.
|
||||
|
||||
Whilst it is not only for network automation it seems to be everywhere when you are looking for resources and as previously mentioned if it's not Python then its generally Ansible which is in fact written also in Python.
|
||||
Whilst it is not only for network automation it seems to be everywhere when you are looking for resources and as previously mentioned if it's not Python then it's generally Ansible which is written also in Python.
|
||||
|
||||
I think I have mentioned this already but during the "Learn a programming language" section I chose Golang over Python for reasons around my company are developing in Go so that was a good reason for me to learn but if that was not the case then Python would have taken that time.
|
||||
|
||||
@ -10,11 +10,11 @@ I think I have mentioned this already but during the "Learn a programming langua
|
||||
|
||||
Pycharm might be another IDE worth mentioning here.
|
||||
|
||||
- Libaries - The exensibility of Python is the real gold mine here, I mentioned before that this is not just for Network Automation but in fact there are libraries a plenty for all sorts of devices and configurations. You can see the vast amount here [PyPi](https://pypi.python.org/pypi)
|
||||
- Libraries - The extensibility of Python is the real gold mine here, I mentioned before that this is not just for Network Automation but in fact, there are libraries plenty for all sorts of devices and configurations. You can see the vast amount here [PyPi](https://pypi.python.org/pypi)
|
||||
|
||||
When you want to download the library to your workstation, then you use a tool called `pip` to connect to PyPI and download it locally. Network vendors such as Cisco, Juniper, and Arista developed libraries to facilitate access to their devices.
|
||||
|
||||
- Powerful & Effcient - Remember during the Go days I went through the "Hello World" scenario and we went through I think 6 lines of code? In Python it is
|
||||
- Powerful & Efficient - Remember during the Go days I went through the "Hello World" scenario and we went through I think 6 lines of code? In Python it is
|
||||
|
||||
```
|
||||
print('hello world')
|
||||
@ -22,19 +22,19 @@ print('hello world')
|
||||
|
||||
Put all of the above points together and it should be easy to see why Python is generally mentioned as the de-facto tool when working on automating.
|
||||
|
||||
I think it's important to note that it's possible that a number of years back there were scripts that might have interacted with your network devices to maybe automate the backup of configuration or to gather logs and other insights into your devices. The automation we are talking here is a little different and thats because the overall networking landscape has also changed to suit this way of thinking better and enabled more automation.
|
||||
I think it's important to note that it's possible that several years back there were scripts that might have interacted with your network devices to maybe automate the backup of configuration or to gather logs and other insights into your devices. The automation we are talking about here is a little different and that's because the overall networking landscape has also changed to suit this way of thinking better and enabled more automation.
|
||||
|
||||
- Software Defined Network - SDN Controllers take the responsibility of delivering the control plane configuration to all devices on the network, meaning just a single point of contact for any network changes, no longer having to telnet or SSH into each and every device and also rely on humans to do this which has a repeatable chance of failure or misconfiguration.
|
||||
- Software-Defined Network - SDN Controllers take the responsibility of delivering the control plane configuration to all devices on the network, meaning just a single point of contact for any network changes, no longer having to telnet or SSH into every device and also relying on humans to do this which has a repeatable chance of failure or misconfiguration.
|
||||
|
||||
- High Level Orchestration - Go up a level from those SDN controllers and this allows for orchestration of service levels then there is the integration of this orchestration layer into your platforms of choice, VMware, Kubernetes, Public Clouds etc.
|
||||
- High-Level Orchestration - Go up a level from those SDN controllers and this allows for orchestration of service levels then there is the integration of this orchestration layer into your platforms of choice, VMware, Kubernetes, Public Clouds etc.
|
||||
|
||||
- Policy based management - What do you want to have? What is the desired state? You describe this and the system has all the details on how to figure it out to become the desired state.
|
||||
- Policy-based management - What do you want to have? What is the desired state? You describe this and the system has all the details on how to figure it out to become the desired state.
|
||||
|
||||
## Setting up lab environment
|
||||
## Setting up the lab environment
|
||||
|
||||
Not everyone has access to physical routers, switches and other networking devices.
|
||||
|
||||
I wanted to make it possible for us to actually look at some of the tooling pre mentioned but also getting hands on and learn how to automate the configuration of our networks.
|
||||
I wanted to make it possible for us to look at some of the tooling pre-mentioned but also get hands-on and learn how to automate the configuration of our networks.
|
||||
|
||||
When it comes to options there are a few that we can choose from.
|
||||
|
||||
@ -42,7 +42,7 @@ When it comes to options there are a few that we can choose from.
|
||||
- [Eve-ng](https://www.eve-ng.net/)
|
||||
- [Unimus](https://unimus.net/) Not a lab environment but an interesting concept.
|
||||
|
||||
We will build our lab out using [Eve-ng](https://www.eve-ng.net/) as mentioned before you can use a phsyical device but to be honest a virtual environment means that we can have a sandbox environment to test many different scenarios. Plus being able to play with different devices and topoligies might be of interest.
|
||||
We will build our lab out using [Eve-ng](https://www.eve-ng.net/) as mentioned before you can use a physical device but to be honest a virtual environment means that we can have a sandbox environment to test many different scenarios. Plus being able to play with different devices and topologies might be of interest.
|
||||
|
||||
We are going to do everything on EVE-NG with the community edition.
|
||||
|
||||
@ -54,13 +54,13 @@ We will be using the OVF download but with the ISO there is the option to build
|
||||
|
||||
|
||||
|
||||
For the purposes of our walkthrough we will be using VMware Workstation as I have a license via my vExpert but you can equally use VMware Player or many of the other options mentioned in the [documentation](https://www.eve-ng.net/index.php/documentation/installation/system-requirement/)Unfortunatly we cannot use our previously used Virtual box!
|
||||
For our walkthrough, we will be using VMware Workstation as I have a license via my vExpert but you can equally use VMware Player or any of the other options mentioned in the [documentation](https://www.eve-ng.net/index.php/documentation/installation/system-requirement/)Unfortunately we cannot use our previously used Virtual box!
|
||||
|
||||
This is also where I had an issue with GNS3 with Virtual Box even though supported.
|
||||
|
||||
[Download VMware Workstation Player - FREE](https://www.vmware.com/uk/products/workstation-player.html)
|
||||
|
||||
[VMware Workstation PRO](https://www.vmware.com/uk/products/workstation-pro.html) Also noted that there is an evalutation period for free!
|
||||
[VMware Workstation PRO](https://www.vmware.com/uk/products/workstation-pro.html) Also noted that there is an evaluation period for free!
|
||||
|
||||
### Installation on VMware Workstation PRO
|
||||
|
||||
@ -68,11 +68,11 @@ Now we have our hypervisor software downloaded and installed, and we have the EV
|
||||
|
||||
We are now ready to get things configured.
|
||||
|
||||
Open VMware workstation and then select `file` and `open`
|
||||
Open VMware Workstation and then select `file` and `open`
|
||||
|
||||
|
||||
|
||||
When you download the EVE-NG OVF Image it is going to be within a compressed file. Extract the contents out into its own folder so it looks like.
|
||||
When you download the EVE-NG OVF Image it is going to be within a compressed file. Extract the contents out into its folder so it looks like.
|
||||
|
||||
|
||||
|
||||
@ -82,9 +82,9 @@ Give it a recognisable name and store the virtual machine somewhere on your syst
|
||||
|
||||
|
||||
|
||||
When the import is complete increase the number of processors to 4 and the memory allocated to 8 GB. (This should be the case after import with the latest version if not then edit vm settings)
|
||||
When the import is complete increase the number of processors to 4 and the memory allocated to 8 GB. (This should be the case after import with the latest version if not then edit VM settings)
|
||||
|
||||
Also make sure the Virtualise Intel VT-x/EPT or AMD-V/RVI checkbox is enabled. This option instructs VMware workstation to pass the virtualisation flags to the guest OS (nested virtualisation) This was the issue I was having with GNS3 with Virtual Box even though clearly my CPU allows this.
|
||||
Also, make sure the Virtualise Intel VT-x/EPT or AMD-V/RVI checkbox is enabled. This option instructs VMware workstation to pass the virtualisation flags to the guest OS (nested virtualisation) This was the issue I was having with GNS3 with Virtual Box even though my CPU allows this.
|
||||
|
||||
|
||||
|
||||
@ -92,7 +92,7 @@ Also make sure the Virtualise Intel VT-x/EPT or AMD-V/RVI checkbox is enabled. T
|
||||
|
||||
Sidenote & Rabbit hole: Remember I mentioned that this would not work with VirtualBox! Well yeah had the same issue with VMware Workstation and EVE-NG but it was not the fault of the virtualisation platform!
|
||||
|
||||
I have WSL2 running on my Windows Machine and this seems to remove the capability of being able to run anything nested inside of your environment. I am actually really confused as to why the Ubuntu VM does run as it seems to take out the Intel VT-d virtualisation aspect of the CPU when using WSL2.
|
||||
I have WSL2 running on my Windows Machine and this seems to remove the capability of being able to run anything nested inside of your environment. I am confused as to why the Ubuntu VM does run as it seems to take out the Intel VT-d virtualisation aspect of the CPU when using WSL2.
|
||||
|
||||
To resolve this we can run the following command on our Windows machine and reboot the system, note that whilst this is off then you will not be able to use WSL2.
|
||||
|
||||
@ -104,7 +104,7 @@ When you want to go back and use WSL2 then you will need to run this command and
|
||||
|
||||
Both of these commands should be ran as administrator!
|
||||
|
||||
Ok back to the show, You should now have a powered on machine in VMware Workstation and you should have a prompt looking similar to this.
|
||||
Ok back to the show, You should now have a powered-on machine in VMware Workstation and you should have a prompt looking similar to this.
|
||||
|
||||
|
||||
|
||||
@ -113,13 +113,13 @@ On the prompt above you can use:
|
||||
username = root
|
||||
password = eve
|
||||
|
||||
You will then be asked to provide root password again, this will be used to SSH into the host later on.
|
||||
You will then be asked to provide the root password again, this will be used to SSH into the host later on.
|
||||
|
||||
We then can change the hostname.
|
||||
|
||||
|
||||
|
||||
Next we define a DNS Domain Name, I have used the one below but I am not sure if this will need to be changed later on.
|
||||
Next, we define a DNS Domain Name, I have used the one below but I am not sure if this will need to be changed later on.
|
||||
|
||||
|
||||
|
||||
@ -127,7 +127,7 @@ We then configure networking, I am selecting static so that the IP address given
|
||||
|
||||
|
||||
|
||||
Final step, provide a static IP address from a network that is reachable from your workstation.
|
||||
The final step, provide a static IP address from a network that is reachable from your workstation.
|
||||
|
||||
|
||||
|
||||
@ -162,7 +162,4 @@ Next up we are going to:
|
||||
- [Practical Networking](http://www.practicalnetworking.net/)
|
||||
- [Python Network Automation](https://www.youtube.com/watch?v=xKPzLplPECU&list=WL&index=126)
|
||||
|
||||
See you on [Day 26](day26.md)
|
||||
|
||||
|
||||
|
||||
See you on [Day 26](day26.md)
|
||||
111
Days/day26.md
111
Days/day26.md
@ -0,0 +1,111 @@
|
||||
## Building our Lab
|
||||
|
||||
We are going to continue our setup of our emulated network using EVE-NG and then hopefully get some devices deployed and start thinking about how we can automate the configuration of these devices. On [Day 25](day25.md) we covered the installation of EVE-NG onto our machine using VMware Workstation.
|
||||
|
||||
### Installing EVE-NG Client
|
||||
|
||||
There is also a client pack that allows us to choose which application is used when we SSH to the devices. It will also set up Wireshark for packet captures between links. You can grab the client pack for your OS (Windows, macOS, Linux).
|
||||
|
||||
[EVE-NG Client Download](https://www.eve-ng.net/index.php/download/)
|
||||
|
||||
|
||||
|
||||
Quick Tip: If you are using Linux as your client then there is this [client pack](https://github.com/SmartFinn/eve-ng-integration).
|
||||
|
||||
The install is a straightforward next,next and I would suggest leaving the defaults.
|
||||
|
||||
### Obtaining network images
|
||||
|
||||
This step has been a challenge, I have followed some videos that I will link at the end that links to some resources and downloads for our router and switch images whilst telling us how and where to upload them.
|
||||
|
||||
It is important to note that I using everything for education purposes. I would suggest downloading official images from network vendors.
|
||||
|
||||
[Blog & Links to YouTube videos](https://loopedback.com/2019/11/15/setting-up-eve-ng-for-ccna-ccnp-ccie-level-studies-includes-multiple-vendor-node-support-an-absolutely-amazing-study-tool-to-check-out-asap/)
|
||||
|
||||
[How To Add Cisco VIRL vIOS image to Eve-ng](https://networkhunt.com/how-to-add-cisco-virl-vios-image-to-eve-ng/)
|
||||
|
||||
Overall the steps here are a little complicated and could be much easier but the above blogs and videos walk through the process of adding the images to your EVE-NG box.
|
||||
|
||||
I used FileZilla to transfer the qcow2 to the VM over SFTP.
|
||||
|
||||
For our lab, we need Cisco vIOS L2 (switches) and Cisco vIOS (router)
|
||||
|
||||
### Create a Lab
|
||||
|
||||
Inside the EVE-NG web interface, we are going to create our new network topology. We will have four switches and one router that will act as our gateway to outside networks.
|
||||
|
||||
| Node | IP Address |
|
||||
| ----------- | ----------- |
|
||||
| Router | 10.10.88.110|
|
||||
| Switch1 | 10.10.88.111|
|
||||
| Switch2 | 10.10.88.112|
|
||||
| Switch3 | 10.10.88.113|
|
||||
| Switch4 | 10.10.88.114|
|
||||
|
||||
#### Adding our Nodes to EVE-NG
|
||||
|
||||
When you first log in to EVE-NG you will see a screen like below, we want to start by creating our first lab.
|
||||
|
||||
|
||||
|
||||
Give your lab a name and the other fields are optional.
|
||||
|
||||
|
||||
|
||||
You will be then greeted with a blank canvas to start creating your network. Right-click on your canvas and choose add node.
|
||||
|
||||
From here you will have a long list of node options, If you have followed along above you will have the two in blue shown below and the others are going to be grey and unselectable.
|
||||
|
||||
|
||||
|
||||
We want to add the following to our lab:
|
||||
|
||||
- 1 x Cisco vIOS Router
|
||||
- 4 x Cisco vIOS Switch
|
||||
|
||||
Run through the simple wizard to add them to your lab and it should look something like this.
|
||||
|
||||
|
||||
|
||||
#### Connecting our nodes
|
||||
|
||||
We now need to add our connectivity between our routers and switches. We can do this quite easily by hovering over the device and seeing the connection icon as per below and then connecting that to the device we wish to connect to.
|
||||
|
||||
|
||||
|
||||
When you have finished connecting your environment you may also want to add some way to define physical boundaries or locations using boxes or circles which can also be found in the right-click menu. You can also add text which is useful when we want to define our naming or IP addresses in our labs.
|
||||
|
||||
I went ahead and made my lab look like the below.
|
||||
|
||||
|
||||
|
||||
You will also notice that the lab above is all powered off, we can start our lab by selecting everything and right-clicking and selecting start selected.
|
||||
|
||||
|
||||
|
||||
Once we have our lab up and running you will be able to console into each device and you will notice at this stage they are pretty dumb with no configuration. We can add some configuration to each node by copying or creating your own in each terminal.
|
||||
|
||||
I will leave my configuration in the Networking folder of the repository for reference.
|
||||
|
||||
| Node | Configuration |
|
||||
| ----------- | ----------- |
|
||||
| Router | [R1](Networking/R1) |
|
||||
| Switch1 | [SW1](Networking/SW1) |
|
||||
| Switch2 | [SW2](Networking/SW2) |
|
||||
| Switch3 | [SW3](Networking/SW3) |
|
||||
| Switch4 | [SW4](Networking/SW4) |
|
||||
|
||||
## Resources
|
||||
|
||||
- [Free Course: Introduction to EVE-NG](https://www.youtube.com/watch?v=g6B0f_E0NMg)
|
||||
- [EVE-NG - Creating your first lab](https://www.youtube.com/watch?v=9dPWARirtK8)
|
||||
- [3 Necessary Skills for Network Automation](https://www.youtube.com/watch?v=KhiJ7Fu9kKA&list=WL&index=122&t=89s)
|
||||
- [Computer Networking full course](https://www.youtube.com/watch?v=IPvYjXCsTg8)
|
||||
- [Practical Networking](http://www.practicalnetworking.net/)
|
||||
- [Python Network Automation](https://www.youtube.com/watch?v=xKPzLplPECU&list=WL&index=126)
|
||||
|
||||
Most of the examples I am using here as I am not a Network Engineer have come from this extensive book which is not free but I am using some of the scenarios to help understand Network Automation.
|
||||
|
||||
- [Hands-On Enterprise Automation with Python (Book)](https://www.packtpub.com/product/hands-on-enterprise-automation-with-python/9781788998512)
|
||||
|
||||
See you on [Day 27](day27.md)
|
||||
@ -47,8 +47,8 @@ This will not cover all things DevOps but it will cover the areas that I feel wi
|
||||
- [✔️] 🌐 23 > [Network Protocols](Days/day23.md)
|
||||
- [✔️] 🌐 24 > [Network Automation](Days/day24.md)
|
||||
- [✔️] 🌐 25 > [Python for Network Automation](Days/day25.md)
|
||||
- [🚧] 🌐 26 > [](Days/day26.md)
|
||||
- [] 🌐 27 > [](Days/day27.md)
|
||||
- [✔️] 🌐 26 > [Building our Lab](Days/day26.md)
|
||||
- [🚧] 🌐 27 > [](Days/day27.md)
|
||||
|
||||
### Stick to one Cloud Provider
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user